Repository navigation
ntre_apparatus_dm.nav: cut the helipad fence drops and mark the fence tops - #167
Open
sunzenshen wants to merge 1 commit into
Open
sunzenshen wants to merge 1 commit into
sunzenshen wants to merge 1 commit into
Conversation
Review of NeotokyoRebuild#157: three one-way drops off the helipad fence, 4671 / 4674 / 4672 -> 415, cross the open kill slot west of the pad, and the fence-top areas carry no CLIFF or PRECISE, so a bot on them can also dodge or side-step into the slot. Cut the three drops; the way down stays 93 -> 8436 -> 415. Mark PRECISE + CLIFF on the 11 pad-edge areas whose footprint is at least 30 % over the open slot (4671 4672 4674 4676 4679 4733 4731 4677 4673 8286 1819), and on 3401, as its mirror 3404 is. Gates: connections -3, no pocket, reachability or route change. Pad probe, 48 matches a mesh: falls into the slot from the pad 2 -> 0, world deaths a match 4.98 -> 4.96. nav_analyze FRESH; same graph.
sunzenshen
changed the title
sunzenshen
marked this pull request as ready for review
October 14, 2026 08:16
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follows the review of #157 (sunmachine).
What the review found. Three one-way drops off the helipad fence, 4671 / 4674 / 4672 -> 415, cross the open kill
slot west of the pad (~76 u down; the slot is 28-98 u wide). A bot steers at the first point past the fence tip,
which is over the slot. The fence-top areas carried no CLIFF / PRECISE, so a bot on them could also dodge or
side-step into the slot. No spawn-to-spawn or spawn-to-area shortest path uses the three drops; they carry roam and
chase traffic only. Separately, 3401 lacked the PRECISE + CLIFF its mirror 3404 has.
What changed (area ids unchanged):
collision, no solid from z 572 down to the trigger_hurt): 4671, 4672, 4674, 4676, 4679, 4733, 4731, 4677, 4673,
8286, 1819. That is the review's three plus eight.
Evidence.
Offline (ntnav review against master): connections -3 (the three drops), nothing else; no pocket added or removed,
no area unreachable or entered with no way back, no route longer by more than 10 %. Each fence top still links
back onto the pad.
nav_analyze rerun: same graph, analysis data unchanged.
In game (Linux dedicated, Release build of neo master f426c222b plus harness logging; 30 bots, 1 round, low damage;
CTG forced with the ghost pinned on six pad-edge spots so bots converge on the fence; XP tier rotated;
48 matches per mesh, interleaved 8 wide):
Bots still reach the pad and still get down off it by 93 -> 8436; no fall from the fence tops in 48 matches.
The counts are small: the edit removes the drop links and the side-step, it does not claim a rate change.