The bug
If the world spawn point is too far from (0,0), summoning an arrow or trident in the air causes the game to lag incredibly (to basically unplayable ticks per second) until the arrow or trident hits a block.
How to reproduce
Press Alt+F3 and watch the TPS graph
Set the world spawn with
/setworldspawnat (0,0)Run the command with either the given sound or any sound and observe that there is no TPS lag
/summon arrow ~ ~50 ~or/summon trident ~ ~50 ~Teleport to 1000 ~ 0 and set the world spawn at (1000, 0)
Run the command, but only ONCE (just a few more will cause your game to stop running)
/summon arrow ~ ~50 ~or/summon trident ~ ~50 ~The further the world spawn is from (0,0), the worse the TPS lag
Attachments
Comments 10
Apparently this is only happen on a certain test world of mine. I'm currently trying to see what is causing it. I disabled datapacks and resource packs to see if they were the issue but they were not. I attached a picture showing it happening. Still investigating.
I attached my level.dat file. This is the only thing that needs to be in the world file before I open the world, and the bug will happen.
Can't reproduce - can you check your hard drive usage when you play the sound?