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.
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.)