Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The navmesh divides the map into walkable polygons ("nav areas").
AI entities (like NextBots) use these areas to calculate paths instead of relying on simple line-of-sight or collision detection.
Without a navmesh, most AI will just stand still, move randomly, or fail to chase properly.
Key points about GMod navmesh:
Generated manually or automatically:
You can generate a navmesh using the console command nav_generate. This scans the map and builds a mesh based on its layout.
Stored in files:
The navmesh is saved as a .nav file alongside the map (e.g., gm_construct.nav).
Editable:
You can tweak it with commands like nav_edit 1, which lets you see and modify the mesh in-game.
Used by NextBots:
Most custom NextBots (like "Sanic," "Obunga," etc.) need a navmesh to function properly, or they’ll just sit there.
Glad I read descriptions.