I've been attempting to make a datapack that plays looping music to different players depending on where they are in the world.
In the process of debugging my commands, I kept running into a situation that seems to cause a playsound command to trigger during the world load and continue playing after the game is paused and even after the world is closed, thus continuing to play on the title screen. Because this bug could be used to harass someone and the most obvious methods of preventing it don't work, I've labelled this report as private to prevent abuse.
Regarding the bug itself, I have no idea what about the functions is triggering the bug since everything I've tried doing to prevent it hasn't worked. However, I've attached a resource pack and world capable of reproducing it.
To reproduce everything I know about the bug:
Open Minecraft
Apply the attached resource pack
Open the attached world and the sound plays normally
Save and quit to title
Reopen the world and the sound is playing twice, one bugged and one normal
Save and quit to title and the bugged sound continues playing
Close Minecraft
Open Minecraft
Open the world and the sound doesn't bug out
Save and quit to title
Reopen the world and the sound is playing twice again
Related issues
Attachments
Comments
migrated
kumasasa
@unknown, is there a reason to keep this ticket private?
migrated
As noted in the description, this bug could potentially be abused to play a sound in a way that a user cannot easily stop. Any kind of sound could be put in a resource pack attached to a world or set on a server. For example, an unsuspecting user could download an "adventure map" from an unreliable source and suddenly find their computer blaring painfully loud high frequency noise. Most people would immediately close the world and expect the noise to stop, but sounds played with this bug would not.
Edit: It's also not clear whether or not this could affect older versions or whether it is related to 1.13. If it only affects 1.13 and is fixed before any release then there likely wouldn't be a problem.
Edit2: Just realized that I might not know what kind of bugs are usually kept as private. If this doesn't really meet that criteria, it can likely be public. I just figured it'd be better to err on the side of caution when I created the report.
migrated
Well, nevermind. Despite my best efforts to search for duplicates before submitting a report, this seems to be a duplicate of MC-102403 since that bug was fixed in 1.13-pre2 and this issue is no longer occuring.