Skip to content

ntre_rise_ctg: drop ladder 3's dead top cap area - #168

Open
sunzenshen wants to merge 1 commit into
NeotokyoRebuild:masterfrom
sunzenshen:navmesh-rise-ctg-ladder-tops
Open

sunzenshen wants to merge 1 commit into
NeotokyoRebuild:masterfrom
sunzenshen:navmesh-rise-ctg-ladder-tops

Conversation

@sunzenshen

@sunzenshen sunzenshen commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

To test: build NeotokyoRebuild/neo#2239, a testing branch that combines NeotokyoRebuild/neo#2231 and NeotokyoRebuild/neo#2232. Ladder 3 is only climbable end to end with both bot fixes, so this navmesh change cannot be seen in game with either one alone or on master.

Follows #160 (ntre_rise_ctg navmesh rework), whose body lists ladder 3 up under "Known, not changed".

What was wrong. Ladder 3 (-219, -952) climbs 200 u up a shaft. Its exit at the top is area 138 (z -336), through a 52 u high window in the shaft's north wall whose sill is level with the ladder's top. The navmesh also gave the ladder a top_forward area, 3567: a 16 x 46 strip on the ladder brush's own top inside the shaft, with no links out. A bot that ends a climb standing on the brush top takes 3567 as its area, and every path from there runs back down the ladder.

What changed (area ids unchanged): area 3567 deleted; the ladder keeps 138 as its top (top_left). nav_analyze rerun: same graph otherwise, analysis data unchanged.

Evidence.

  • Offline (ntnav review against master, navconnect gate): areas -1, connections -1 and ladder links -1 each way (3567's), no pocket added or removed, no area unreachable or entered with no way back. Gate PASS.
  • In game (Linux dedicated, Release; 1 round, XP tier rotated):

Not changed. Ladder 4's foot has the same vent cover (fixed by the bot PR above); its top is a 48 u hatch only a crouched Recon passes (as in #160). Ladder 1's top drops back to its foot (3573 / 3574 -> 3137): in spawn-near probes about half the bots that finished a climb re-planned onto that drop, but in normal play ladder 1 was climbed once in 8 matches, so the cut was left out.

Area 3567, the ladder's top_forward, is a 16x46 strip on the ladder
brush's top inside the shaft with no links out; the ladder's exit is
top_left 138 through a 52 u window. A bot that ends a climb on the
brush top took 3567 as its area and re-planned down the ladder.
Area ids otherwise unchanged; nav_analyze rerun (same graph).
@sunzenshen

Copy link
Copy Markdown
Contributor Author

The changes are around the vent ladder near the main server room:

image

@sunzenshen
sunzenshen requested a review from sunmachine October 15, 2026 04:00
@sunzenshen sunzenshen added the bug Something isn't working label Oct 15, 2026
@sunzenshen
sunzenshen marked this pull request as ready for review October 15, 2026 04:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant