Open
Conversation
Owner
|
Hey, to clarify, the actual logic of the mod is based on this:
Because of this, it's not really possible to support actual float values. For example, if the mainloop is ticking at 100 TPS, and some entity wants to tick at 20.5 TPS. Realistically, that entity has to do 20 or 21 instead. So when you enter a float value for the TPS, the mod just rounds it to the nearest integer. Admittedly this is a design flaw I noticed a bit too late into initial development. |
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.
I have built the mod and tried to change rate to 20.99. The time of redstone repeaters ran showed it worked.

This is a 10s-timer: