The Bug
Allays will travel far away from notebox and get lost when the player is not around.
(This happens to singleplayer too when the player leave the allays in the world spawn and then go exploring around the world)
Reproduce
Go on a server
Get some allays
Bring the allays to a repetitively playing notebox
Log off but keep the chunk with the allays loaded
Rejoin at a later time
Observed Result
The Allays traveled away
Expected Result
The Allay would stay around the notebox
Linked issues
relates to 1
Attachments
Comments 23

This is run on a vanilla server, I'm using the fabric to take screenshots with shaders as we head towards the stronghold today. As allays move around often I have no time to switch back to a vanilla client.
Regardless of whether the server that you were playing on is vanilla, your client is modified, which could have had an impact on the outcome of the situation. Please test if this issue is present in a complete vanilla environment and let us know if you were able to recreate the same behavior, as the bug tracker only handles reports that exist under these circumstances.

First of all, the mob behavior is operated by the server which is vanilla, secondly, I can assure you that when the mob went missing I was using the vanilla client. And the player who found the allays at -500, 10 first is also using vanilla.
It took a month for these allays to be gone completely and this time I found only 4 out of 6 missing allays out of pure luck, I do not think finding them again in another random place would be that easy.
Besides, in MC-253735 @Leandro Gimenes da Silveira points to the same kind of allay behavior: allay "started to fly strangely high". WHich clearly shows that this problem is not exclusively happening in my game

ok, can you reproduce the issue in complete vanilla once again?


Can confirm in 1.19.3 and 23w04a

Affects 1.20.1.
This is not exclusive to multiplayer. You can have this occur if allays cannot find you in singleplayer (i.e. you flew away with elytra and they couldn't keep up) or presumably if the player is in spectator mode.

Can confirm 1.21
This report is invalid as your game was modified when experiencing this issue. The F3 debug menu indicates you're running a non-vanilla client, and the bug tracker only handles issues that occur under complete vanilla circumstances.