ralokt
Assigned
Reported
Comments
Why is this resolved? it's really easy to reproduce, and it's still happening in 1.19...
Still affects 1.16pre1
Seed: 8470219322699000237
Approximate coordinates in screenshot: -47, 75, -18
It seems to have gotten much better, although I can't really compare since we had to remove those launchers and are on different hardware now.
But at the very least, building launchers where boats are not inside water is now feasible for us again (for some reason, boats in water cause significantly more lag).
Sorry, I completely forgot about this issue - but here is an anonymized log with player names, GUIDs and IPs replaced. I'm sceptical that it'll help much, though, there's hardly anything out of the ordinary in there.
However, there is one thing maybe worth noting: We were experiencing regular crashes due to OOM conditions at the time, and have fixed those in the meantime by setting `-Xms` and -Xmx` to the same value. I can't remember this issue happening recently, and I believe it's the only significant change we made to our deployment.
Restarting the server fixed the issue for me.
I am experiencing the same issue. Unfortunately, the world I am playing on is huge (Quite a few Gigabytes in size).
What I tested:
comparing NBT (NBeeT?) data for both hives and the bees inside them. I found working (in the overworld) hive containing a bee differing only in the following attributes: 'Dimension', 'FlowerPos', 'HivePos', 'Motion', 'Pos', 'Rotation', 'TicksInHive'
placing a hive that didn't work in the nether in the overworld - bees popped out immediately.
placing a hive that worked in the overworld in the nether - bees stayed in the hive.
placing the first hive back in the nether after it worked in the overworld - stopped working again.
placing a hive in the nether that worked in the overworld in the nether, surrounded by air blocks with a flower nearby - hapily buzzing hive of couch potatoes.
Anomalies preceding the bee strike:
a server restart
an ongoing render of our minecraft world that will be done in about 30 hours
Additional random potentially useful information:
there are some permaloaded nether chunks with a honey farm that contains quite a few hives in this world.
I'll try to reproduce the problem on a truncated copy of our world in the next days, perhaps I can provide a world download then.
It would be awesome if this were addressed. It's really frustrating to have the equivalent of 3-4 transatlantic flights on record, only for that to be reset. A fix would be as simple as to use long instead of int for statistics.
There is at least a fourth category here:
4. Players who may produce entity cramming situations unintentionally
In any case, those categories are not exhaustive. People can be affected, not have a preference, and still not want to be surprised that their mobs are dying...
Also, as someone who belongs to 2.1, this is not satisfactory. If some people will "simply have to deal", then we should make sure that what they "simply have to deal" with is a good idea; making it necessary to evaluate all alternatives and find the best one for this group, if the goal is to take all players into account. Of course we're not all players, and what other people want may be more important, which is OK. But handwaving the issue away by saying "well, SOMEONE will always be mad" makes me sad 😞
I understand the need for this gamerule for reasons of performance and feasibility of feature parity/compatibility. The nice thing is, though, different compatible versions can still have different defaults as long as they can deal with all alternatives, and I would really appreciate not having this "on" as a default.
EDIT:
Also, I started writing this before we were asked to cease discussion here, and didn't see the post in time; Sorry about that.
I was able to reproduce this. Connected to a server without problems, entered a minecart, instantly got this error.
Reconnecting with 1.9.1pre3 worked, and I was inside the minecart.
To my knowledge, the world was only ever loaded in vanilla survival. Since we're a snapshot server, there may be associated weirdness, though.
And yes, there are quite a few signs in the area.
MC-153048 is another instance of this. This issue is also marked as "can't reproduce" which I find very hard to believe - I'm currently having trouble not reproducing it while attempting to build a boat elevator...