Remove SERVER_TICK block property
#3135
Merged
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
screret
approved these changes
May 4, 2025
screret
approved these changes
May 11, 2025
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.
What
This PR removes the
SERVER_TICKblock property, which would dictate whether a machine should tick or not. While in theory, this may seem like a good idea, in reality, having to update the blockstate ends up affecting performance quite a bit.Instead, just allowing the block entity to noop tick is more performant.
Outcome
An improvement in TPS/MSPT. In my heavy test case, the median MSPT decreased by 20%.
Before
After
Potential Compatibility Issues
I don't believe there are any...