> 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/optimizing-nav-mesh-generation/hiding-objects-during-nav-mesh-generation.md).

# Hiding Objects During Nav Mesh Generation (old)

This wiki entry explains how to hide objects in the forge menu during navmesh generation to prevent interference.

### Using Folders to Hide Objects

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

1. Access the "Folders" section in the forge menu, which contains a list of every placed object on your map.
2. Create subfolders for specific object categories (e.g., Foliage, Blockers).
3. Add relevant objects to their respective subfolders.
4. Click the "eye" button to hide all objects within the folder.

With objects hidden, you can safely generate navmesh.

### Managing Large Amounts of Objects

* It is possible to add up to 150 objects to a folder at a time.
* Adding too many objects at once can increase the risk of a crash.

**Recommendation**: Save before and between each large folder action to avoid potential crashes.

**Contributors**\
Scrubulba\
Captain Punch


---

# 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/optimizing-nav-mesh-generation/hiding-objects-during-nav-mesh-generation.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.