bot ai is frozen when no players in their zone#305
Merged
billy1arm merged 1 commit intomangoszero:masterfrom May 1, 2026
Merged
bot ai is frozen when no players in their zone#305billy1arm merged 1 commit intomangoszero:masterfrom
billy1arm merged 1 commit intomangoszero:masterfrom
Conversation
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 17 |
| Duplication | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
bozimmerman
force-pushed
the
bot_activezoneonly
branch
from
788dd22 to
c3f069d
Compare
bozimmerman
force-pushed
the
bot_activezoneonly
branch
from
c3f069d to
6d9eff3
Compare
bozimmerman
force-pushed
the
bot_activezoneonly
branch
from
6d9eff3 to
b6af515
Compare
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
3 participants
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.
Adds a new aiplayerbot.conf option that will forbid thread time to bots unless they are 1. grouped OR 2. in the same zone as a real Player.
This has a huge impact on CPU time, not driving hundreds of bots on another continent while you are running a dungeon somewhere. And besides, if a Treant falls to a playerbot in a forest, and no one is around to see it, did it really need to happen?
This change is