Notice and respect conf changes to min/max bots #218
+28
−2
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
Member
|
@bozimmerman There are some trailing spaces in this pr. Are you able to fix them? https://github.com/mangoszero/server/actions/runs/20477190786/job/58843834428?pr=218 Thank you for all your contributions. They are very much appreciated |
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.
If the min/max bot levels are changed in the aiplayerbot.conf file, the server really never notices or cares. The current kosher procedure is to blow them all away and regenerate them, but I figured that a quick comparison of a few integers during bot processing wouldn't hurt anyone, and it sure makes my life easier.
This change is