Use maxCommandForkCount gamerule for limiting execute #367
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.
This PR replaces the execute as/at limiter with the maxCommandForkCount gamerule (introduced in 1.20.3), which does the same thing the execute limiter intended to do.
The limit for the gamerule is the same as the config's maxEntitiesPerWorld, which is the
theoretical limit for the old limiter (
/execute as @e ...
).Since the maxCommandForkCount gamerule also applies to nested execute commands, I removed the block for execute-in-execute aswell.
The code for the gamerule limiter was getting a bit messy, so I refactored that. The gamerule limits are now applied to all of the worlds on startup, because Minecraft's default for maxCommandForkCount is 65535, which is way above ours.