NVM NAVIGATION & MAP COLLISION UPDATE
8 NVM files updated across 6 area groups
8 NVM files updated across 6 area groups
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ━
Several NVM-related navigation issues have been resolved.
These issues could cause characters to:
- Collide with invisible obstacles
- Walk in place without progressing
- Become stuck between regions
- Prevent the bot from continuing along its calculated route
Blocked edges were not simply removed. The corresponding Zone and Region adjacency connections were properly rebuilt to preserve valid movement topology.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ━
UPDATED AREAS
Karakoram — Ancient Remains
- Region 23168 — nv_5a80.nvm
- Region 23169 — nv_5a81.nvm
The cross-region transition between both sectors was rebuilt.
Eastern Hotan
- Region 23434 — nv_5b8a.nvm
Northern Hotan
- Region 24710 — nv_6086.nvm
- Region 24712 — nv_6088.nvm
Jangan
- Region 25000 — nv_61a8.nvm
Samarkand / Amphitheater
- Region 27492 — nv_6b64.nvm
Donwhang / Gobi Desert
- Region 25495 — nv_6397.nvm
The incorrectly placed tre_dry_big_01.bsr collision object that was blocking the road was removed from the navigation data.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ━
TECHNICAL IMPROVEMENTS
- Invisible and ghost collision areas were fixed.
- Missing zone connections that caused characters to walk in place were repaired.
- Reciprocal connections across region boundaries were rebuilt.
- Zone object indices were safely remapped.
- Terrain, height and surface data were preserved.
- Only the required navigation records were modified.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ━
UPDATE COMPLETED SUCCESSFULLY
A total of 8 NVM files across 6 area groups have been updated.
A total of 8 NVM files across 6 area groups have been updated.
