I made something like this back a while ago, but it still bugs me.
if you type in this command:
/playsound minecraft:block.note_block.pling player @a ~ ~ ~ 100000 0.5 1
It will act like you typed in this command:
/playsound minecraft:block.note_block.pling player @a ~ ~ ~ 100000 0 1
What REALLY bugs me is that if you place a noteblock, you are able to access the sounds of .1, .2, .3, .4, and .5. Why doesn't it work with playsound. If playsound had more accessability to the pitch, it would make much better toned maps.
Though last time I made this, it was considered invalid, so I'm starting to think this is intentional.
Is it?
Comments 10
Actually I believe it's the other way around; running /playsound with pitch 0 - 0.4999 has the same effect as 0.5 (which plays the sound an octave lower). The pitch value is a multiplier of the original frequency of the sound, so giving it a value of 0.1 would play a sound 3+ octaves lower than the original one, and a pitch multiplier of 0 wouldn't make sense.
Yes, @unknown is right, it plays the pitch 0,5 if you use lower pitch. Anyway, confirmed for 1.16.3.
Looking back at it, I don't see this much as a bug, but more so a minor inconvenience. Considering that most modern maps use resource packs to customize the game, it's a minimal flaw/side-effect from a design perspective and probably not worth the effort to bother fixing. In all honesty, having it cap off at .5 is more helpful in some cases, *such as when trying to increase a sound by an octave. Because of this, it almost feels to be intentional, or perhaps just a side-effect.
Revamping the playsound command would be a much better approach, as fixing this bug would break most sound-effects in projects regardless, which is a main concern when approaching these sorts of problems.
*Note that this works because of a 1:2 ratio.
Ex. Playing a pitch of .7 is an octave below the pitch of 1.4.
Confirmed for 1.13.1.