> For the complete documentation index, see [llms.txt](https://wiki.thescriptersguild.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.thescriptersguild.com/forge/nav-mesh/nav-mesh-generation/building-nav-mesh/how-to-use-nav-mesh.md).

# How To Use Nav Mesh (old)

### Required Objects

* Nav Seed Point
* Jump Hint Two Way
* Bot Nav Marker

### Steps

#### Place Nav Seed Point in desired location

{% hint style="info" %}
If your forge map does not use the natural terrain of the forge canvas or if the base flooring is combination of natural terrain and forge pieces, placing a Nav Seed Point helps with Bots being playable on your forge map.
{% endhint %}

<figure><img src="/files/2ovLEqLwSkPsmTgciUyv" alt=""><figcaption></figcaption></figure>

#### Open the Build Menu and build Nav Mesh

* To get to the Build Menu, hold the **Y** button on the controller to access the Tools Menu and move the thumbstick to the right and select **Build Menu**
* Navigate down the list of build options, highlight **Nav Mesh** and then select **Build Selected** to build the Nav Mesh on the forge map.

<figure><img src="/files/qHAJYtqWavRtw6hD7Teo" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/hT9OiG9FFRM6LiioGow4" alt=""><figcaption></figcaption></figure>

#### Turn on Nav Mesh Visualization

* Open the Forge Menu and navigate over to **Tool Settings**.
* Scroll down through the list of tool settings to Nav Mesh Visualization and turn **On** the setting.

{% hint style="info" %}
If you cannot see the Nav Mesh on your map, make sure your crosshairs are pointed towards the floor and not a wall.

If you still can't see the Nav Mesh, validate the Nav Seed Point is placed on the ground and rebuild the Nav Mesh data.
{% endhint %}

<figure><img src="/files/gltUmqevqulNOaQ0O3Ka" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/68csmc5QQKkfubqoYGHh" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Validate Bot gameplay after initial Nav Mesh build, this is a good time to verify the all areas are fully populated for Bot movements.
{% endhint %}

#### If extra Bot movement pathing is needed, it might be useful to place an extra Nav Seed Point

* Placing another Nav Seed Point will help Bots to identify all intended playable spaces.

<figure><img src="/files/KEBjYPT7g5gIVcbfIB5m" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/bPlLvsgzYF12BN42lSmI" alt=""><figcaption></figcaption></figure>

#### Using Jump Hints to help Bot traversal movements

* If the intended jump hint was not built properly with the default Nav Mesh build, you can place either a Jump Hint One Way or Jump Hint Two Way to help Bots understand the intended jump spaces.

<figure><img src="/files/3s6lCjP66Z8vnRkeAtRB" alt=""><figcaption></figcaption></figure>

* When placing a Jump Hint, make sure the bottom corners of the volume are merged into the geo for the Jump Hint to populate properly.

<figure><img src="/files/aVBpZ1s3YVrQpfbzVptp" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Bots have a max jump height, so validate the jump hint is not too high or too far of a jump for the bot.
{% endhint %}

#### Place and Name Bot Nav Markers for setting up neighbor options - Workflow Enhancement

* Place Bot Nav Markers around the map on points of interests
* Name each explore point uniquely so it's easier to find within the folders and when setting up the neighbor options for a better workflow experience.
  * If setting up each explore point uniquely isn't the best workflow for you, you can still use the default **Bot Nav Marker** and add a unique description to the location for identifiable reasons
* Another approach is by creating a separate folder in your 'Forge Menu - Folders', name the folder as **Nav Markers** and set that folder as your working folder.

<figure><img src="/files/Il8YsWFcEaS1h00K6bMJ" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/8ww2XIdTRJ9rOMesu1IK" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/KJOYYAhOgd9bSUB8lSOv" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
When you're completed placing Nav Markers, to change your working folder so that you are not spawning unwanted objects in the incorrect folder.
{% endhint %}

#### Setting up Neighbor Options

{% hint style="info" %}
**What are Neighbor Options**

Neighbor Options is when the bot is navigating around the map and when gets to its destination point and it will then determine which Bot Nav Marker it wants to go towards next.

If a bot requires a weapon, game mode objective or an enemy player they will prioritize objectives before heading towards the next location.

When testing or playing your map and if you see bots clustered in one location, it usually means the bots don't have another Nav Marker to go towards, objectives to complete or weapons they don't need on the on the map.
{% endhint %}

Once all the Nav markers have been properly placed and labeled, Neighbor Option can now be set up.

In the example below, you'll notice theres a Nav Marker location labeled the "Pit" set up as a point of interest for neighbors bots to explore next. Bots do not travel in a 'straight line' from one location to the next, the lines are just representative of the area the bots will explore next.

<figure><img src="/files/n3uFVUI2xNZCiSAuztGe" alt=""><figcaption></figcaption></figure>

In a real map you will need to have more than just four Nav Markers set up and you will need to set up them up like intersections for roadway.

<figure><img src="/files/mZpZgmoxc493u4kDkBuW" alt=""><figcaption></figcaption></figure>

### Other Notes

1. Bots will also look for Item spawners on the map along with understanding objects.
2. Bots understand how to play objectives, for instance the bot will hide the Oddball or Flag if you have the Bot Nav Marker set to hidden for those Game Modes. Make the Bot Nav Markers are properly setup for the Game Modes by setting the labels to put **CTF Include** and set up the team for that hiding spot. This will help prevent the bot from hiding the stolen stolen flag in the enemy's base. When setting up for Oddball, set the **Oddball Include** label and set the team to **Neutral**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.thescriptersguild.com/forge/nav-mesh/nav-mesh-generation/building-nav-mesh/how-to-use-nav-mesh.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.