Flamingosaurus
Assigned
Reported
MC-298653
Master volume slider no longer affects /playsoud sounds with high volume
Fixed
MC-279264
click_event "run_command" action fails with commands /say and /tell
Duplicate
MC-278096
"Fabulous!" graphics and clouds disabled causes all particles to linger in frame buffer for one frame
Fixed
MC-277807
Teleporting the player's mount causes rotation de-sync, previously did not
Fixed
REALMS-4622
Uploading a world does not remove the previous world's resource pack
Awaiting Response
Comments
Ok, added the minimal world file. World is 1.21.4pre3 but will also demonstrate the issue on any version 1.21.2 or later. The commands posted by Sidite will work, too.
In response to Dhranios: Yes this is similar. The issue with network code has always affected teleports on the player themselves, but up until 1.21.2 teleporting the player's mount did not desync their rotation. I reported this because it breaks command/function implementations that worked up until 1.21.2.
Oh, well that solves that mystery then! I never would've thought to turn clouds on and off.
It might be, yeah. I experienced this issue on both a NVIDIA 940MX and NVIDIA Quadro T1000.
Okay. I went and linked a video demonstration in the description.
This is new to 1.21.2. I loaded into 1.21.1 just now to double check and the particle ghosting didn't happen with Fabulous graphics.
I also went and loaded up the latest snapshot 24w44a and the Fabulous ghosting is still an ongoing problem.
I'm getting this, too. The final loading screen after downloading the resource pack causes a rapid disconnect and reconnect, after which the resource pack is removed. This extra load screen happens after the player has connected and was able to move around (and use the resource pack) for a few seconds.
Occasionally this results in "ghost" players who can move around the world and observe what's happening but can't chat or interact with anything. They also fall through the world without any collision if they're switched out of spectator mode.
Ah. Yeah I guess I used the exact wrong test case when playing with the new format. Whoops.
I'll update the report title and description. Probably not a bug anymore, though. It would be nice if the error message was shown in chat, though. I didn't realize what was happening until I checked the output log.