If three or more entities start drawing their bows, right before they shoot the arrow to the target the game stops responding and just stays like that until you task manager it. This is really really bad because you would most likely encounter three skeletons at night plus anything that is used to bait in skeletons will crash the game.
Attachments
Comments 6
Interestingly, this is a client-side infinite loop case. There is currently no easy way to debug them, as watchdogs do not exist in vanilla clients and this does not otherwise produce errors.
I have, however, managed to program a Fabric mod to implement client-side watchdog. I'll attach the report, but solely for the purpose of helping future readers. This report is not official. Given the few modifications made in this setup, I expect this report to reflect the vanilla bug.
The bug appears to be caused by an arrow colliding with something (likely another arrow) on the client-side; the loop in PersistentProjectileEntity#applyCollision never finishes. The arrow goes back and forth between 2 positions on the client.
The simple fix is to not apply projectile collisions on the client.
Can confirm. You can leave out the piglin, though (and use the player as a target). Note that a very large amount of skeletons is needed. This also works with normal skeletons, strays, bogged, pillagers, illusioners and piglins, which makes this reproducible in survival. The crash seems to occur when multiple mobs try to shoot one target at the same time (so the arrows seem to be the problem).