Recover from repeated route execution failures - #102
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
1 participant
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.
Closes #100.
Bot One now treats three consecutive movement-result mismatches for one destination as a bounded patrol failure. It records the stuck event, skips the failed patrol point, and either resumes at the next point or uses the existing service fallback when no patrol points remain.
Navigation resets clear the failure count, so unrelated routes cannot combine into a false recovery.
Verification
pwsh -File scripts/test-playerbot-gameplay.ps1 -Focused -FullNavigation -SkipBuildpassed the existing temporary-blockage scenario and the deterministic repeated-execution-failure scenario.