MC-63446Hopper Clocks No Longer Function Outside of World Border
Before 14w30a, Hopper Clocks functioned fine outside the World Border, allowing mapmakers to set up compact and reliable clocks for minigames since /setblock and /fill doesn't work outside the World Border at all. Sadly, this is no longer the case.
Opening Captive Minecraft in 14w30a or later, which begins with a 1x1 World Border, you can see that the Hoppers nearby do not function outside the 1x1 area. Making the World Border bigger, they immediately begin functioning as soon as they're within the Border.
Linked Issues
Created Issue:
Hopper Clocks No Longer Function Outside of World Border
Before 14w30a, Hopper Clocks functioned fine outside the World Border, allowing mapmakers to set up compact and reliable clocks for minigames since /setblock and /fill doesn't work outside the World Border at all. Sadly, this is no longer the case.
Opening Captive Minecraft in 14w30a or later, which begins with a 1x1 World Border, you can see that the Hoppers nearby do not function outside the 1x1 area. Making the World Border bigger, they immediately begin functioning as soon as they're within the Border.
is duplicated by
is duplicated by
![[Mojang] Searge (Michael Stoyke)](../../../data/assets/gravatar/searge.png){kind=small}
[Mojang] Searge (Michael Stoyke)![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
relates to
is duplicated by
Dupe of MC-63446
Dupe of MC-63446
Intended. As stated by Searge on MC-63446 "other block entities than command blocks will not work outside of the world border for performance reasons."
I understand your point. What I'm saying is that the only time the "Works as Intended" resolution should be used is if Mojang actually wants it to be in the game. This lag, while not a huge problem, and basically unfixable, is not something that Mojang thought would be good to have. It's just a problem that isn't going to be fixed because it doesn't bother anyone anymore. That's what the "Won't Fix" resolution is for. Something that everyone agrees is a bug, but Mojang, for whatever reason, isn't going to fix it.
As it is, many bugs that Mojang has decided not to fix are labeled WAI, such as MC-1823, MC-2313, MC-10708, MC-30663, MC-50605, MC-63055, MC-63446, MC-64634, MC-77170, and MC-78797. In all of these reports, the issue is clearly not something that Mojang intended to occur. They have simply decided not to fix it, sometimes for performance reasons, sometimes because it would just take too much effort. The "Won't Fix" resolution is woefully underused, which leads to very inconsistent resolutions. WAI should only be used when it was actually intended, such as MC-11220, MC-35860, MC-48184, MC-63380, MC-78691, and MC-79609.
Have tested again in 14w31a, but still no luck.
Still a bug in 14w32a
The setblock and fill commands are working outside of the world border in recent snapshots, other block entities than command blocks will not work outside of the world border for performance reasons.
"Works as intended" ....That sucks...
It's good to know that fill clocks would work. At least not all hope is lost for Captive Minecraft, its just going to need an update so that the hopper clocks are replaced