mojira.dev
MC-55293

Player or entity selectors don't get turned into player or entity names in the "summon" JSON argument

When using a command block with the command set to...

summon Wolf ~ ~2 ~ {CustomName: "@p" , Owner: "@p" }

...the summoned wolf will have the name @p instead of the actual player name and belongs to the non-existing player with the name @p.

When using the new selector JSON format for texts introduced in the latest snapshot, e.g. like...

summon Wolf ~ ~2 ~ {CustomName: {selector: "@p"} , Owner: {selector: "@p"} }

...the wolf does not have any name.

Attachments

Comments 3

The new selector is only for the raw JSON text of /tellraw and /title
https://twitter.com/SeargeDP/status/465905177015619584

And that's exactly what this bug describes: The selector does not work for any other command but /tellraw and /title. So why should it be invalid?

Or to put it differently: Currently there is no way to refer to player names in the summon command. Which is the actual bug behind this.

Because it's no bug, it's a feature request.

The.Modificator

(Unassigned)

Unconfirmed

Minecraft 14w20b

Retrieved