Skip to content

Keep playerbots from re-engaging during danger retreat - #180

Merged
adrunkhuman merged 1 commit into
masterfrom
fix/playerbot-danger-retreat
Sep 8, 2026
Merged

adrunkhuman merged 1 commit into
masterfrom
fix/playerbot-danger-retreat

Conversation

@adrunkhuman

Copy link
Copy Markdown
Owner
  • Bot One recognized excessive damage and began returning to depot, but immediately engaged an adjacent Valkyrie that did not block its route. It stayed in place, exhausted its potions, and died.
  • Keep danger retreat active across navigation and service resets. Reject optional combat, preserve healing priority, and defer level-eight departure until retreat ends.
  • Try detours first. Allow each confirmed route blocker one five-second combat attempt without chase or immediate reacquisition. Restore ordinary defense at depot arrival or the next hunt.
  • Add pure retreat-policy checks and a captured-log assertion for optional engagement, blocker reacquisition, and incomplete or fatal returns.

Escape is not guaranteed when trapped. The exact danger-transition encounter still needs post-fix live observation; there is no dedicated deterministic live fixture yet.

@adrunkhuman
adrunkhuman merged commit 1b29bec into master Sep 8, 2026
1 check passed
@adrunkhuman
adrunkhuman deleted the fix/playerbot-danger-retreat branch September 11, 2026 00:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant