[MC-59118] "/playsound" in a command block uses relative coordinates from itself -not from the player anymore

I dont know if its really a bug, but it seems that the /playsound command changed its behaviour.
Pre 25b i could place a commandblock with

/playsound <sound> @p ~ ~ ~

which played the sound relatively to the nearest player.
Since this update i hear nothing anymore when i go to far away and trigger the block. When i look into the commandblock it says that no player was found.

I assume that the commandblock now uses the relative coordinates from "itself" .

Linked issues

duplicates 1

MC-59017 /playsound will only play relative to player if [minimumVolume] is set.. but still plays relative to command block Resolved

Comments 4

Sebastian K 2014-06-26T16:49:27Z

still in 14w26c
also when no relative coordinates are set:
/playsound <soundname> @p
it doesnt play if the player is too far away from the cmd-block

qmagnet 2014-06-27T02:42:28Z

you can do

execute @a ~ ~ ~ /playsound <soundname> @a

Sebastian K 2014-06-27T09:16:57Z

But thats not how it worked since forever.
Nearly every map prior this Snapshot is affected with this

hilarious that it begins working again, when you add all the optional tags

/playsound <soundname> @p ~ ~ ~

doesnt work when you are too far away

/playsound <soundname> @p ~ ~ ~  <vol> <pitch> <minvol>

works again. Dont know if this is really intended.

trazlander 2014-07-07T01:04:18Z

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.

execute @a ~ ~ ~ playsound random.explode @p

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!