- Sun Nov 24, 2013 12:45 pm
#179257
If any have noticed, some integrated hopper-redstone circuits don't work quite the same on MineRealm as they do in vanilla MC. Automatic smelters may not work properly, automatic potion brewers may act weird, and automatic item shops may suffer. This is all for good reason. MineRealm implements a popular and cleverly modded craftbukkit server called spigot. It's the same mod that makes your item entities merge and the same mod that rids us of x-rayers. Some of the modifications do nothing but help the server, but some are questionable. The modification I'm particularly interested in is that which changes hopper timings.
Spigot allows server admins to change two values of hopper timings. One is hopper-transfer. At a default value of 8, hoppers behave as they should. Putting it lower allows items to move the hoppers quicker and higher makes it slower.
The other variable is hopper-check. This value is called when a hopper is asked to push or pull and it either has no items to push or pull or if it is powered by redstone (being prevented from working). When a hopper meets these conditions in a tick, its cooldown counter is set to the value of hopper-check (a spigot default value of 8) and decrements on each tick. When it reaches zero, the hopper tries to push or pull (if it can) and if it does, sets the cooldown to hopper-transfer. If you understand this well enough, you'll know that getting hoppers to act in a consistent manner is difficult or impossible. Furthermore, vanilla minecraft essentially does not have a hopper-check variable (equivalent to being zero). Building a hopper machine in SP and finding it doesn't work on minerealm is frustrating and discouraging.
But you ask, why did spigot change hopper timings in the first place? The answer is to reduce lag. You can no doubt imagine that with many hoppers being used to move items around and with each hopper doing things each tick, they will most definitely be a major source of lag. But I would argue changing hopper-check from 8 to 0 would not create any considerable lag. Hoppers will still receive updates every tick. Spigot only attempts to shorten the processing time in these updates when a hopper is idle. However, the vanilla code already has if statements to check whether an update should proceed. When a hopper is powered, it will not proceed to update. When there is no inventory to push to, a hopper will not proceed in pushing items.
TL;DR: I want to change hoppers so they act like they should, but this could lower the TPS. If it does, I would agree to changing it back.
Spigot allows server admins to change two values of hopper timings. One is hopper-transfer. At a default value of 8, hoppers behave as they should. Putting it lower allows items to move the hoppers quicker and higher makes it slower.
The other variable is hopper-check. This value is called when a hopper is asked to push or pull and it either has no items to push or pull or if it is powered by redstone (being prevented from working). When a hopper meets these conditions in a tick, its cooldown counter is set to the value of hopper-check (a spigot default value of 8) and decrements on each tick. When it reaches zero, the hopper tries to push or pull (if it can) and if it does, sets the cooldown to hopper-transfer. If you understand this well enough, you'll know that getting hoppers to act in a consistent manner is difficult or impossible. Furthermore, vanilla minecraft essentially does not have a hopper-check variable (equivalent to being zero). Building a hopper machine in SP and finding it doesn't work on minerealm is frustrating and discouraging.
But you ask, why did spigot change hopper timings in the first place? The answer is to reduce lag. You can no doubt imagine that with many hoppers being used to move items around and with each hopper doing things each tick, they will most definitely be a major source of lag. But I would argue changing hopper-check from 8 to 0 would not create any considerable lag. Hoppers will still receive updates every tick. Spigot only attempts to shorten the processing time in these updates when a hopper is idle. However, the vanilla code already has if statements to check whether an update should proceed. When a hopper is powered, it will not proceed to update. When there is no inventory to push to, a hopper will not proceed in pushing items.
Spoiler:
