Last active 2 months ago
It's already been confirmed by md_5 (the project lead for Spigot, so he knows his shit when it comes to optimization) that the major source of the server crashes is ticking water causing surrounding chunks to tick (which, if they contain water at the edges, also cause more chunks to tick.) The ticking quickly goes out of control since this is such a lousy accidental recursion that Mojank added into the game as one of 1.14's many undocumented features . This either results in a StackOverflowError from the call stack space colliding with heap space or some ConcurrentModificationException, presumably from the server ticking way too many chunks at once. Both cases cause a server crash.
So, clearly, loading ocean chunks should be something kept to an absolute minimum until Mojang pushes out the update. Guess what runs antithetical to that objective?
That's right, boats. Boats let new and established players alike sail across lots of ocean chunks and inadvertently generate shit tons of lag. Because their movement is clientside boats also ignore the lag that they generate, exacerbating the problem even more.
The solution? Just ban them. /kill them every tick, notify players that they're banned for being a major propagator of server lag for this update, and just get them out of the server until the 1.14.1 update is confirmed to completely wipe out the bug once and for all.
Now you may ask, if we ban boats, why not elytra too? Don't they allow the exact same thing? Well, elytra don't require just 3 wooden logs on a fresh spawn, and established players with elytra are mostly already aware of the problem and its cause. They're going to understand that exploring a lot of chunks in general causes server lag, and that in particular this update causes the lag to quickly grow out of control, unlike a newer player who might not be aware of the issue at hand.
Seriously, it's the best thing we can do to mitigate crashing. The other alternative is sitting here twiddling our thumbs, hoping that people just won't boat around (which, by the way, they won't heed to our pleads in chat to fucking stop) while suffering from lost mobs and rollbacks from the server crashing.
-----------------------------------------------------------------------------------------------------------------------------------------------
EDIT: Compiling some counterarguments to the proposal that I have addressed before but not on this thread:
1. "It would be impossible to transport villagers around, which is a negative".
Actually, it wouldn't. By establishing a base near a village decently far from spawn you have a guaranteed source of villagers that you can then abduct for a villager farm. You can practically do every precise movement you can do on a boat with a minecart. As for long distance travel, you shouldn't be transporting any mob around thousands of blocks around anyways (as this is just a colossal waste of time if you ultimately think about it) unless they're rare to the point where building a base near it would be worthless. Examples include elder guardians and foxes, both of which don't necessarily warrant a permanent base location.
This also doesn't consider the fact that, if you boat villagers around, you still are subjected to the same crashing condition that I described in the first paragraph. Villagers don't magically fix the ocean bug, and it's already well-established that server crashes and restarts put villagers at a risk of being deleted (it's happened to Team Eye 4 times already, including a Mending villager, breaking our villager breeder once, and outpost farm twice now.) There's no guarantee that transporting villagers with boats is safe at all until 1.14.1 is out.
2. "Players will have to travel across oceans anyways, so making them have to travel for hours is a negative."
This has some merit as there's no other option for a newer player except to journey in the Nether (which, however, is a viable option for travel. Maybe staff can finally set up the nether portal at spawn for this occasion?). However, you need to consider the two options we have.
Either:
@DeJean how long?
Your application is currently under review.
@PapaNeon You can log in with your regulat minecraft account.
Have to log in with my Jira account here.
Just an FYI guys, but to vote on an issue on MC's bug tracker you have to make a Jira account. Otherwise, you get this:
You might want to clarify in OP that people'll need to make an account beforehand.
imagine hacking in a lego video game
that thought alone should be enough to keep hackers banned forever
@FieryPhoenix64 What exploit is it? All I know aboit it is that it 'lets people find peoples bases', so Im not sure how that works.
What you need to do is set up a contraption where you have minecart tracks aimed directly into a cactus. Then, insert a beacon into a chest minecart placed on a powered rail. You want to go far enough way until the cactus unloads but the minecart doesn't, then activate the powered rail.
If there are any chunks loaded beyond 10 chunks of that cactus, the minecart will break and drop its beacon, otherwise you will find it sitting right next to the cactus unharmed. The chances of the exploit working is increased significantly if it's raining, by the way.
@humfrydog Yes i am aware, i was wondering if it might return someday.
Never. Thor is too strong for the server.
Rain has been disabled due to an exploit.
Don't get me wrong, it looks damn good from a distance and I applaud any kind of map art, but calling a shrunken down and posterized image "pixel art" is quite a bit of a stretch.
@SadFeeling People in life have a lot of money, does that make their money useless? No, Diamonds are the same way
the same thing can be said for sea pickles
if everyone has mending diamond gear and doesn't ever need to use diamonds to, you know, make diamond stuff then they are useless just like sea pickles omegalul
now brick blocks are :ok_hand:, look great, hard to get, more valuable than diamonds confirmed