Shane Freeder

the event fires before all of the logic is ran, so the replacement can't be prepopulated is the dealio, IIRC, so, that's sadly a WAI

that only works for a specific case, however, that is generally not how the event has worked for the past few eons

> That the message returned to the player won't reflect the new tick rate? Yes, the server prints the output of the tick rate, and yet, if a plugin mutates...

autosaving is not full saving, the entire point of that mechanism is to disable the periodic saving in order to allow an external program to backup the world, it prevents...

~~https://minecraft.wiki/w/Java_Edition_24w33a 1.21.2 snapshot, also changes this further...~~ actually, this is a non factor, this only affects living respawns, something spigot basically opted us out of

The overworld on server A and server B will be the exact same dimension name, as there is no other form of UUID attached, I'm not sure what the expectation...

if mod map makers had an agreed upon means of us sending this to them, we could adopt it; but, there exists 0 gain from us just sending random plugin...

it's a reusable generic container wrapper class

best guess would be to test on bungeecord, this project is EOL and so 0 inclination to look into it here

24w09a is the cause of this