Suggest close
Bad omen effect doesn't work like this any more
Isn't this worksasintended pretty much? You have to damage mobs within N seconds for it to count as a player kill. Granted, it would make sense if that time was guaranteed to be slightly longer than the duration of Flame even with a few frames of lag ... (I forget what N is, unfortunately)
For clarity: Instapush still exists in 1.21 in structure spawn farms, where mobs still spawn in northwest corners of blocks.
Fwiw, I think it's cool that Mojang dared to make this change. I'm getting a fair few farms broken myself – but I'm good with that. Designing new things is fun! And this change makes all sorts of sense.
Re-confirmed in 1.20.12, Win11 Home 22H2 - exported to a OneDrive-synced folder, resulting file is 0 KB. No error. 13 MB world. Onedrive is in %userprofile% and also syncs "Documents", which is where I'm trying to save.
MOJANG: Note that this is TWO bugs in one. First, the failure itself, and not alerting the user that it failed! The second one is actually more serious - as it easily causes data loss.
(4 years for a data-loss bug? C'mon.)
Win10, very old install but up-to-date: Can't reproduce. File is exported successfully. Onedrive folder is on an extra mechanical drive, far away from %userprofile%. "Documents" is not re-linked/synced.
Confirmed in 1.19.83. Win10-64, realm.
Rapidly traded Lecturer up to Expert + nametagged him "Sharpness V".
Inside 30 minutes later, he's a stonemason with the same XP level.
At some point during these 30 minutes I broke his workstation, but I don't know the exact time. (I only have 2 backups with 30 minutes between them as reliable timestamps.)
I did not relog or restart during this time.
There was no zombification involved (additionally, world was peaceful during these 30 minutes).
The stonemason workblock that he ended up linking to was thoroughly unpathable (involves a jump up to a ladder & going up it).
This is at least the 3rd time I get this in the same world, which was created as an 1.19 realm about half a year ago. They may all have involved breaking workblocks. No zombification.
[media]
Voting to NOT fix this - declare as WAI. (Reason being chain can't be powered by e.g. a torch beneath it)
Give it to Java if parity is an issue. (Novel idea, I know.)