BureaucraticErrorEvent-Tweak#209
Merged
robinthedragon merged 2 commits intoApr 27, 2025
Merged
Conversation
|
test fail is real, but unrelated good tweak, removes the unfun part of the event while preserving the fun part thank you for your first contribution :) |
imatsoup
added a commit
that referenced
this pull request
Jul 1, 2025
2 tasks
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.
About the PR
Changed the logic behind the BureaucraticErrorEvent so that it can no longer close out job slots mid-round.
Why / Balance
Multiple individuals the past couple of days have expressed frustration at the current behavior of the event, and would prefer it could not close out job slots. Increasing them or making them infinite is deemed more entertaining than potentially locking someone out of the round. Incidentally, these changes also should prevent some unintended behavior where the event was reportedly closing out Passenger and other infinite roles.
Technical details
When the event is triggered, there is a 25% chance as it is currently implemented to close out all slots except a few, but make the remaining infinite. The for-loop used to remove those slots has been removed, leaving only the behavior of making some jobs infinite. The remaining 75% of the time, in the current implementation it chooses a number between -1 and 6, and modifies random job slots by that much. By changing the random range from -1-6 to 1-6, we remove the undesired situation of closing out job slots. Additionally, the event will always have some impact now by opening up additional slots no matter what, though still on random jobs. Lastly, the message text for the event is updated to reflect the new behavior of the event.
Media
Requirements
Breaking changes
🆑