mojira.dev

steveswales

Assigned

No issues.

Reported

MC-301369 Use Item/Place Block get stuck on repeat Duplicate MC-177570 Server crash if world is a symbolic link as of 20w14a Duplicate MC-165542 Bees are trapped in older hives, and those hives don't produce honey Duplicate MC-163091 Bees are coming out and attacking at night (again) Duplicate MC-124406 /data merge entity doesn't accept multiple targets Duplicate MC-124383 Can't get the state of a lever Invalid MC-118109 when typing functions, namespace:path/to/function/file no longer autocomplete Cannot Reproduce MC-108907 repeaters don't power adjacent blocks Duplicate MC-93598 Server crash: java.util.ConcurrentModificationException when updating neighbours or colliding entity with block Fixed MC-92163 server crash - null pointer exception Duplicate MC-88132 Changing dimensions breaks command block UI access Duplicate MC-73502 Minecraft is not environmentally conscious Invalid MC-67727 Beacons in Nether need clear path to "sky" Fixed MC-66987 Exit Portal has floating torches Duplicate MC-55455 Zombie Pigmen become Zombies? Duplicate

Comments

a freshly created comparator doesn’t cause the crash.

Not sure this is the same issue, but I had a comparator in my inventory which caused a client side crash if I tried to click on/more it. The only way to remove it from the inventory without a crash was using the clear command.

Didn't happen in 20w14infinite or before.

Probably related to this client side bug 

  1. MC-177238

Not sure if this matters, but the first day that they start to do this pop in/out thing, they are on a (seemingly) random schedule, but after the first night cycle, they are all synchronized.  All of the bees pop out of and back into all of the hives at the same time.  They make a big splash sound if you have a lot of hives.

Even hives created in 19w46a start to fail in this way after a while.  Initially, they work as expected, and then start to exhibit this wrong behavior.

In case it is not obvious, I have campfires under the hives, however I tried removing them, and also removing every other hive, to see if these were factors, but it appears to have no effect.

Probably the same bug, but maybe different... shears have no effect on hives.

Oh, weird... it appears it is not happening with newly created hives, but does still happen on old hives if you collect them with silk touch and put them back.

Voting for this one.  Logically, these things should appear connected to the honey block, since they move with it... otherwise it appears to be due to magnetism, or quantum entanglement or something like that.  Those things are cool, but it is a honey block, not a quantum entanglement block.

Oh, snap! That's clever. Convoluted, but it works.

that's weird.... it is working for me now. I will reopen if I'm able to reproduce.

Yes. I am seeing the same thing. I use them as "transporter pads" in my overworld, and they are now randomly spitting out beacon beams.

suggest replacing lava with magma in all villages. should solve this problem, and be more realistic looking as well.

I think this is tied to another ticket (#MC-94438). I don't see lag on worlds with no mobs, even with hundreds of repeating command blocks (not that these are particularly interesting worlds).

There's a separate ticket for command blocks causing lag (#MC-94684), but I do think that THAT bug doesn't occur unless you have mobs spawned/spawning. In a test world, I seem to be able to make loads of repeating command blocks, as long as there are no mobs around. Once mob spawning is on, the lag starts and scales with the number of command blocks, and the number of mobs. Without the command blocks I don't see the lag (in a flat world with normal mob spawning). These two tickets should be linked at least, as they seem closely related.

Still a problem in 16w04a. Sure wish this would get looked at.

Hope this can get some attention. It is very hard to provide feedback on the new snapshots when they are basically unusable.