Minecraft Username: Expipiplusone Brief Description: Arrows despawn too quickly. Using a dispenser filled with arrows, a wooden button and very little redstone, it used to be possible to build a lag friendly 1-minute clock, which does not rely on items being moved back and forth between hoppers or complex (and resource intensive) redstone circuitry. Now that arrows despawn after a very few seconds (roughly 10), such a clock is pointless. I don't know whether such a short despawn time for arrows was accidental or intentional, however it seems to me that, with arrow clocks unfeasible, redstone lag is likely to increase as many people will revert to other designs. Instructions: Throw an arrow and see it despawn in very few seconds instead of a minute as it used to. How many times did you recreate this?: Many Result: Arrows despawn too quickly Expected Result: Arrows despawn after a minute Evidence: Example of an arrow clock:
Even taking into account people reverting to other designs which are (if I'm not wrong) more resource demanding? In my understanding, arrows are laggish mostly in pvp situations when there's dozens of them scattered everywhere, is pvp a thing on skyblock? (I don't know, I spend my time mostly farming and I have no idea how other players spend their time on skyblock).
I would assume so because 'normal' redstone clocks have a hard limit they cannot exceed without being disabled by the server, so their resource demand is already limited.
@Expipiplusone I am willing to increase this from 10 seconds to 30 seconds . Would this suffice @Expipiplusone?
@Expipiplusone I've actually changed this setting back to 60 seconds. Please let me know it's working well now .
Awesome! Can't login right now, but I assume it's gonna be working again Just out of curiosity: how come? I mean, did just the performance improvement turn out to be not as good as expected, or something else?
I don't believe arrows will have TOO much of an impact on performance so we're dropping the limitation for now
