A PSA about the "world border resetting" bug

[blazex224]

Hello,
A while back, my admin posted about a bug that involved my world border resetting back to a 10k radius every time the server restarted (#110). You had responded saying that you have never seen this issue before, and concluded later that perhaps it was an issue with the server version and plugin version. This did not solve the bug, and we stopped using world border and began using the default, though less featureful, Minecraft world border. This problem has continued throughout numerous versions since that post, with multiple versions of the plugin, Minecraft, and Spigot. While attempting to pregenerate my world today, the same bug occurs. If the server restarts, the world border size is reset to 10k.

In fact, I found other users that have had experience with this bug as well

https://www.planetminecraft.com/forums/help/javaedition/worldborder-keeps-resetting-size-580673/

https://www.spigotmc.org/threads/worldborder-settings-reset.338196/

The issue, made apparent to me by a comment on this Spigot thread, states that the problem is likely because the server host Shockbyte is throttling the WorldBorder plugin to have a maximum radius of 10k without telling anyone that this is what is occuring.

Are you using shockbyte as your host? I was getting this issue because shockbyte started restricting the size people set using the world border plugin totally without warning. Glad I'm not using them anymore... - ceruleanReverie

Upon viewing the Shockbyte terms of service, there is an excerpt that mentions WorldBorder, and this is the only mention of the host about this plugin

We do not allow the following plugin(s) to be used on our services: PerfectBackup, BukkitHTTPD, BukkitTelnet, WorldBorder

So, there you have it. Instead of sending an automatic reminder to the server owner that this plugin is not allowed, they sneakily throttle its use to end users.

I wanted to make this apparent to you so that you can now properly respond to these bug reports that involve this situation. Thanks for your previous help with this bug, and I hope this is a help to you and your plugin

[Brettflan]

Thanks for posting about this, with the info that it is the host ShockByte intentionally covertly causing this problem. I know others with the same problem will find this useful.

[Switchbladed]

Hi, I'm from Shockbyte.

The reason the radius is limited to 10K is because many users misuse the pre-generation feature (/wb fill command). This results in users generating extremely large worlds, because they did not understand the effects of the command and set the radius too large.

Restrictions like this must be implemented to protect other customers.

As far as I am aware there is no other way to limit or disable the /wb fill command - this is why the restriction is being applied to the border as well.

We have now updated the system so it is possible to exclude individual servers from this restriction. Any Shockbyte customers wishing to remove the radius limit can now submit a ticket to have the limit removed from their server.