[MC-9739] Error with @f Created: 14/Feb/13  Updated: 10/Nov/15  Resolved: 10/Nov/15

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Snapshot 13w06a
Fix Version/s: Minecraft 1.8.8

Type: Bug
Reporter: Christian Letz Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Environment:

Windows 8,java 7 update 11


Issue Links:
Relates
relates to MC-54941 name= selector does not function with... Resolved
relates to MC-73729 Selector arguments won't accept some ... Resolved
relates to MC-73737 Asterisks can't use selector arguments Resolved
Confirmation Status: Unconfirmed
Game Mode: Creative

 Description   

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.



 Comments   
Comment by KingSupernova [ 10/Nov/15 ]

It was a bug during 1.7, it should be resolved as fixed.

Comment by KingSupernova [ 10/Nov/15 ]

Whoops, apparently this was fixed sometime in 1.8. Never mind.

Comment by [Mod] redstonehelper [ 10/Nov/15 ]

KingSupernova: Ticket is yours, please update it.

Comment by KingSupernova [ 10/Nov/15 ]

Definitely a bug, please reopen. Relates to MC-54941, MC-73737, and MC-73729.

Comment by WolfieMario [ 14/Sep/13 ]

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.

Comment by Tails [ 14/Feb/13 ]

@f is an invalid argument, so the command block assumes it's a playername -> could not be found.

Generated at Sun Jan 12 12:22:05 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.