The Debug and Admin MODsuits now take a lot less time to (de)activate. #76261
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 Pull Request
Read the title. An equivalent 'activation_step_time' variable has been added to the mod theme datum to accomplish that.
Why It's Good For The Game
Why do we have to wait over 10 seconds for a debug suit to activate or deactivate on top of everything else that comes with coding, programming, bugfixing etc? It now takes about 2 seconds to do so, which should be enough to notice the effects of modules such as the springlock anyway. The admin one takes 0.5 seconds, as it's by all means a better debug suit.
Changelog
🆑
admin: The Debug and Admin MODsuits now take a lot less time to (de)activate. 2 and 0.5 seconds respectively, compared to the default of 10s.
/:cl: