Repository navigation
Nav: a goal by a wall, a doorway the grid misses, and the reads of the levels' navmesh - #131
Merged
Merged
Conversation
…e levels' navmesh Three fixes to the navmesh of hand-made levels, found by switching it on in a game's real levels. A goal that stands by a wall, where the baked body has no room in the goal's own column, took the floor over it (a walkway, the roof) for its node: in hand-made levels a goal's node is now a floor within 1.5 m of its height, in its column or within two meters, where there is one. A doorway narrower than the baked body and a cell together could fall between two columns and cut the navmesh in two: where the levels' navmesh has no route, navmesh_path asks the local grid too. And what building it reads of content is the simulation's whoever asked first, so a replay names the same definitions. The test level's stairs get rails: a route could plan a climb onto a tread from the stair's side, which the controller does not make, and the NPC stood pressed against the stair. The manual says what a level or a game does about it. Co-Authored-By: Claude Mythos 5.2 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
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.
What
Three fixes to the navmesh of hand-made levels (#130), found by switching it on in a game's real levels.
navmesh_pathnow asks the local grid too, which is centred on the walker and plans with its own body. A region's navmesh still has the last word.levels::rebuildopens the simulation's scope, so the replay checkcontentnames the same definitions in a recording and in its playback.Also
mantle_height), which the controller does not make (a tread is half a meter deep), and the NPC stood pressed against the stair; the test passed only when the NPC's next goal happened to lead it away. The manual says what a level or a game does about it (close the stair's sides, or bake a class for a body whosemantle_heightis itsstep_height).nav::refreshright after.Checks
crates/shards_npc/tests/npc/level_nav.rs:a_goal_by_a_wall_under_the_walkway_is_on_the_floor,a_doorway_the_grid_misses_is_walked_on_the_local_grid(9 in the file).cargo test -p shards_npc(71 + 224 pass),cargo test -p shards_motion --test readers,cargo clippy -p shards_npc --all-targets -- -D warnings. The whole workspace is left to CI (it does not fit this machine's memory next to other work).nav: trueare touched: a region's navmesh takes the same paths as before.🤖 Generated with Claude Code