Select the nearest reachable local depot - #109
Merged
Merged
Conversation
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.
Summary
Verification
pwsh -File scripts/test-playerbot-gameplay.ps1 -Depot -Focused -SkipBuild- passed all eight real-depot, movement, and restart scenariospwsh -File scripts/test-playerbot-gameplay.ps1 -FullNavigation -CorpseLoot -SpellTraining -MainlandLoop -Focused -SkipBuild- passed navigation, looting, trainer routing, and repeated mainland-loop regressionsPLAYERBOT_HUNT_DURATION_SECONDS=1800selected locker(32352,32225,7), stood at(32352,32226,7), opened and deposited normally, then started an 1,800-second hunt and fought for more than seven minutes without a terminal eventRelated Issues
This restores the real-depot behavior accepted by #78 and the sustainable loop in #22. It contributes bounded map-derived locality behavior to #28 and removes a blocker from the level 8-20 benchmark in #93. It does not complete either open issue.
Limits
Unavailable and suppression timing are covered by production policy helpers rather than a long wall-clock failure scenario. The normal soak remains running for longer progression evidence.