-
Bug
-
Resolution: Unresolved
-
None
-
1.16.220, 1.16.40 Hotfix, 1.16.201 Hotfix, 1.16.221 Hotfix, 1.17.41 Hotfix, 1.18.2 Hotfix, 1.20.41 Hotfix
-
None
-
Confirmed
-
Multiple
-
546350
For the past year, I've been working on an asymmetrical multiplayer horror map. In any good horror game, sound is incredibly important to the atmosphere. However, the "playsound" command is literally so inconsistent that it's frustrating to work with. I try to work around its faults, thinking it might just be me, but at this point, I cannot keep silent about it.
First off, according to the wiki, the "volume" syntax is meant to increase the range in which the sound can be heard. Theoretically speaking, you can set the volume level all the way to 9999 so that everyone can hear it. This is not the case. In fact, volume does absolutely nothing! I even tried single digits and the volume never increased (if anything, it just made it quieter).
Speaking of the volume, the base range is pathetically short. If you play the sound and move even an inch away from the source, the sound fades to nothing instantaneously. It makes trying to use ambient sounds annoying in a game where you're always on the move (or creating your own ambient sounds, at that).
Lastly, their output message is highly inconsistent. It will SAY that it played the sound, yet I hear nothing. And it can't be because it's too quiet for me to hear because I'm standing directly on top of the source and the volume is in the thousands.
Could this please be looked into? I can't keep wrestling with this command forever...
- is duplicated by
-
MCPE-104500 /playsound volume and minimum volume do nothing
- Resolved
-
MCPE-125705 Playsound/music command bug
- Resolved
-
MCPE-129468 Do [volume] and [minimumVolume] on /playsound work?
- Resolved
-
MCPE-148106 Volume variable in playsound commands are not working and playsound commands in execute commands don't even play even with the correct syntax and the sound name.
- Resolved
-
MCPE-151722 PlaySound bubble not expanding
- Resolved