MC-59017/playsound will only play relative to player if [minimumVolume] is set.. but still plays relative to command block
I've had previously set a redstone system in version 14w26a to use commands like:
/playsound fireworks.blast AURAvulpes ~ ~ ~ 1 1.4
This played the sound relative to the player in 14w26a with a clock that ran command blocks testing for my "Sprinting" score, when i updated to 14w26b it plays relative to the command block rather than the player.. so if the player isnt in audible range when the command is run, the player doesn't hear the sound at all..
But when the [minimumVolume] is added (this sets the volume of the sound playing to the player)
/playsound fireworks.blast AURAvulpes ~ ~ ~ 1 1.4 1
Then the sound is played to the player at the volume set in [minimumVolume] But the sound is still played relative to to command block at the volume set in [volume] Which could mean that the sound is being played in two places (i cant test if this is true because I'm in singleplayer)
This bug can be re-created by:
Setting 1 command block with a /playsound command like: /playsound random.fizz @a ~ ~ ~ 1 1
and a way of activating the command from great distance (A path of redstone with repeaters, testfor commands with a clock, etc.) activating this command when at a great distance away (more than roughly 100 blocks) will show the sound wont play relative to you, only to the command block itself.. If you stand near it and activate it it will play relative to the command block, now edit the command to make it run /playsound random.fizz @a ~ ~ ~ 1 1 0.2
activate it from a great distance like last time and it will play at a volume of 0.2 relative to you, but if you activate it while near the command block, it will still play at a volume of 1 relative to the command block..
Environment
Windows 7 professional 32bit, Java 1.7.0_51
Linked Issues
is duplicated by4
Created Issue:
/playsound will only play relative to player if [minimumVolume] is set.. but still plays relative to command block
I've had previously set a redstone system in version 14w26a to use commands like:
/playsound fireworks.blast AURAvulpes ~ ~ ~ 1 1.4
This played the sound relative to the player in 14w26a with a clock that ran command blocks testing for my "Sprinting" score, when i updated to 14w26b it plays relative to the command block rather than the player.. so if the player isnt in audible range when the command is run, the player doesn't hear the sound at all..
But when the [minimumVolume] is added (this sets the volume of the sound playing to the player)
/playsound fireworks.blast AURAvulpes ~ ~ ~ 1 1.4 1
Then the sound is played to the player at the volume set in [minimumVolume] But the sound is still played relative to to command block at the volume set in [volume] Which could mean that the sound is being played in two places (i cant test if this is true because I'm in singleplayer)
This bug can be re-created by:
Setting 1 command block with a /playsound command like: /playsound random.fizz @a ~ ~ ~ 1 1
and a way of activating the command from great distance (A path of redstone with repeaters, testfor commands with a clock, etc.) activating this command when at a great distance away (more than roughly 100 blocks) will show the sound wont play relative to you, only to the command block itself.. If you stand near it and activate it it will play relative to the command block, now edit the command to make it run /playsound random.fizz @a ~ ~ ~ 1 1 0.2
activate it from a great distance like last time and it will play at a volume of 0.2 relative to you, but if you activate it while near the command block, it will still play at a volume of 1 relative to the command block..Environment
Windows 7 professional 32bit, Java 1.7.0_51
![[Mojang] Searge (Michael Stoyke)](../../../data/assets/gravatar/searge.png){kind=small}
[Mojang] Searge (Michael Stoyke)
is duplicated by
is duplicated by
confirmed on 14w26c
Confirmed for 14w26c.
Still in 14w27a.
Still in 14w27b.
Ya this is actually working as intended now to fix bug
MC-51788. If you ran playsound before, relative coords used to work relative to the player it was played to, but now it works relative to the command block. You just use execute now to accomplish this.But now you can do neat tricks with it like playing it from a player's relative position TO everyone else in earshot of it!
OK, I changed my command blocks to that format.
....so every pre exsisiting build which used /playsound has to change. Would be a good idea when Mojang announce this "change" as official, so that not anybody complains about whats going on, etc
The /playsound command uses the command block it is executed in as reference for relative coordinates. To play sounds relative to players, use the /execute command.
Example:
/execute @p ~ ~ ~ playsound fireworks.blast @p ~ ~ ~ 1 1.4 1