I didn’t simply update the server to the newest version by modifying pre-existing content. Instead, I copied the world file, which cannot be altered by the Paper API, and applied it to the new VM running the vanilla API. Additionally, I haven’t noticed anything within its files that would suggest corruption.
I just reproduced the bug on a vanilla client in both single player (1.21) and multiplayer, with a fresh server on a fresh VM that generated a world within itself, running on the official Minecraft API (1.21). All of the previous memory allocations, Java versions, and Ubuntu version still apply.
MC-273797
I didn’t simply update the server to the newest version by modifying pre-existing content. Instead, I copied the world file, which cannot be altered by the Paper API, and applied it to the new VM running the vanilla API. Additionally, I haven’t noticed anything within its files that would suggest corruption.
I just reproduced the bug on a vanilla client in both single player (1.21) and multiplayer, with a fresh server on a fresh VM that generated a world within itself, running on the official Minecraft API (1.21). All of the previous memory allocations, Java versions, and Ubuntu version still apply.