Repository navigation
Combine #2231 and #2232 for testing neoAssets#168 - #2239
Closed
sunzenshen wants to merge 3 commits into
Closed
sunzenshen wants to merge 3 commits into
sunzenshen wants to merge 3 commits into
Conversation
A ladder whose top exit is a gap only a crouched body fits through, such as a vent or a low window, was never left: the dismount check sweeps the standing body, finds the gap's top in the way, keeps the bot climbing past the ladder's top, and the stall check then jumps it off. When the standing sweep is blocked but a crouched body at the ladder's top clears, duck, hold the feet just above the top and move out toward the landing (along the face for an exit beside the ladder, where a press into the face would climb). Seen on ntre_rise_ctg ladder 3, whose exit is a 52 u window.
A bot whose path runs through a crouch-height gap closed by a func_breakable vent cover never clears it: the check that nothing stands in front of the breakable sweeps the standing body, which meets the gap's lintel first, so the vent is dropped and the bot presses against it until the stuck monitor gives up. Sweep a crouched body when the standing one meets something else first. The look for breakables also stopped at a drop segment, so a bot leaving a duct by a drop had no path line to sweep. A drop's ledge is walked at the height of the floor above before the fall, so that leg now counts for breakables (the prop detour keeps ground legs only). Seen on ntre_rise_ctg, where ladders 3 and 4 stand in shafts entered through such vents: no bot ever climbed either before this.
…Assets#168 Merges the vent-cover change (NeotokyoRebuild#2231) and the crouched ladder dismount (NeotokyoRebuild#2232) so ladder 3 on ntre_rise_ctg can be climbed end to end, which the navmesh change in neoAssets#168 needs to be tested.
This was referenced Oct 15, 2026
sunzenshen
marked this pull request as ready for review
October 15, 2026 04:00
Contributor
Author
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.
Description
Testing branch only: #2231 and #2232 merged together, unchanged, so NeotokyoRebuild/neoAssets#168 can be tested. Review and merge the two component PRs, not this one.
The navmesh change in NeotokyoRebuild/neoAssets#168 (
ntre_rise_ctgladder 3's top area) only shows in game when bots can climb ladder 3 end to end, which takes both bot fixes:The two touch different files (
neo_bot_path_obstacles.cpp;neo_bot_ladder_climb.{h,cpp}) and merge without conflicts. This branch is each PR's commit plus a merge commit; it has no changes of its own.How to test
map ntre_rise_ctg,sv_cheats 1,neo_bot_quota 12,nb_debug behavior, join spectator.Toolchain
Linked Issues