MC-9739Error with @f
When used in "say" commands, selectors will still act as selectors and output the player names. "@f" is not a selector, and yet when it is used in a say command, it returns "That player cannot be found". This does not occur with other non-selectors, such as @d.
Environment
Windows 8,java 7 update 11
Created Issue:
Error with @f
Play in singleplayer.
Input Output:
/say Test [Player] Test
/say @p [Player] Player
/say @r [Player] Player
/say @a [Player] Player/say @f That player could not be found
wtf what is @f o.O
Environment
Windows 8,java 7 update 11
Play in singleplayer.
Input Output:
/say Test [Player] Test
/say @p [Player] Player
/say @r [Player] Player
/say @a [Player] Player/say @f That player could not be found
wtf what is @f o.O
When used in "say" commands, selectors will still act as selectors and output the player names. "@f" is not a selector, and yet when it is used in a say command, it returns "That player cannot be found". This does not occur with other non-selectors, such as @d.
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
@f is an invalid argument, so the command block assumes it's a playername -> could not be found.
Tails, that's actually not correct. If you type "/say @s", the command will output a literal "@s". The /say argument doesn't require a player parameter, so it isn't looking for a player named "@f".
It seems the game interprets "@f" as a selector, even though the only valid selectors are "@a", "@r", and "@p". All other @<letter> strings are just interpreted as literal strings, making the behavior with "@f" inconsistent. This should probably be re-opened, as the behavior doesn't actually make any sense.
Definitely a bug, please reopen. Relates to
MC-54941,MC-73737, andMC-73729.KingSupernova: Ticket is yours, please update it.
Whoops, apparently this was fixed sometime in 1.8. Never mind.
It was a bug during 1.7, it should be resolved as fixed.