You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Repeaters etc tend to cause a lot of mspt spikes when farms are ticking
Describe the solution you'd like.
Currently I know that the big issue is likely related to how the wire handler is done, which is always looks for states to update, and that would cause crashes.
Describe alternatives you've considered.
Limiting Redstone a lot is an option but you know.. at some point Folia would need to implement this, because it's a very good method :(
Other
I think a good implementation for ths is to attach the wire handlers to the tick region data, every time a region merges or splits, it recalculates all of the nodes and removes nodes that will no longer belong to that region, avoiding then the issue with ticking.
The difference between the vanilla Redstone mechanics and the alternative current is huge in performance.
I did this implementation myself already and it seems to be working good without any crashes, I'll be soon pushing this to DonutSMP prod with safety and logging for crashes, I do not handle the region splitting and merging with keeping the current region's data, I didn't really notice a problem with it yet. I'm just instancing a new wire handler instead.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
Repeaters etc tend to cause a lot of mspt spikes when farms are ticking
Describe the solution you'd like.
Currently I know that the big issue is likely related to how the wire handler is done, which is always looks for states to update, and that would cause crashes.
Describe alternatives you've considered.
Limiting Redstone a lot is an option but you know.. at some point Folia would need to implement this, because it's a very good method :(
Other
I think a good implementation for ths is to attach the wire handlers to the tick region data, every time a region merges or splits, it recalculates all of the nodes and removes nodes that will no longer belong to that region, avoiding then the issue with ticking.
The difference between the vanilla Redstone mechanics and the alternative current is huge in performance.
I did this implementation myself already and it seems to be working good without any crashes, I'll be soon pushing this to DonutSMP prod with safety and logging for crashes, I do not handle the region splitting and merging with keeping the current region's data, I didn't really notice a problem with it yet. I'm just instancing a new wire handler instead.
The text was updated successfully, but these errors were encountered: