gabizou
commented
6 years ago So, what TickDynamic is aiming to do is reduce the amount of entities ticking if the server is struggling. The "wall-clock" modification is mostly to mimic the duration of time passed for certain processes of tile entities. I'd be interested to know exactly what the changes would require to have it inlined in Sponge itself (rather, what the vanilla changes look like) since reviewing ASM class trasnformer code is not my cup of tea ;) @The-Fireplace, would you mind explaining what the changes look like to vanilla code? Is it all surrounding World.onUpdate modfiication of what entities need to tick versus need to tick next tick?
PurpleIsEverything
Rsslone
Aathoss
dualspiral
https://github.com/The-Fireplace-Minecraft-Mods/TickDynamic/issues/17
This is a proposal to adding a mixin module to Sponge, that would enable various tweaks to split up the 'tps' of the server.
E.g. Decoupling entity ticks from player ticks, to block placements, to tile entities.
Giving each a priority, would ensure that Combat and 'physical lag' rather then 'slow machines' would remain lag free, and give the impression that even if the server is grinding to a halt tile entity wise, that PvP and Anti-Cheat systems arn't falsely affected by the low tick rates and client / server disparity between physics.
We already have things to add 'wall clock' timings to vanilla entities / tile entities which can possibly break redstone automation in exchange for faster smelting on lagging servers.
Even if it's decided not to go into Sponge itself ( :-( for SpongeVanilla users ) I suggest that we should at least co-operate with the actual TickDynamic author @The-Fireplace to provide a compatibility story, similar to the guidance given to @Barteks2x
@The-Fireplace Who has been reaching out on our forums to no avail. https://forums.spongepowered.org/t/spongeforge-plugin-development-crash-after-setting-up-environment/20457/16