MC-68983Target selector exlusion no longer works with /effect command
This command worked in previous versions of 1.8:
/effect @p[team=!herobrine,r=255] 4 10 10 true
Where mining fatigue was applied to everyone who was not a member of team "herobrine". As of the 1.8-pre1 update, this command gives the following error:
[23:58:27] The entity UUID provided is in an invalid format
I've tried all different configurations and variants of the command, but this works:
/effect @p[team=herobrine] 3
and this does not work:
/effect @p[team=!herobrine] 3
Any exclusion fails. I tried with "name=!ogradyjd" and that failed as well. Tried same selector with /msg and /gamemode and both succeeded, so this seems to only affect the /effect command.
Environment
Windows 8.1 Pro 64bit, single player, Java 1.8.0_05 64bit, 32GB RAM, Intel Core i7-4910MQ 2.90Ghz
Created Issue:
Target selector exlusion no longer works with /effect command
This command worked in previous versions of 1.8:
/effect @p[team=!herobrine,r=255] 4 10 10 true
Where mining fatigue was applied to everyone who was not a member of team "herobrine". As of the 1.8-pre1 update, this command gives the following error:
[23:58:27] The entity UUID provided is in an invalid format
I've tried all different configurations and variants of the command, but this works:
/effect @p[team=herobrine] 3
and this does not work:
/effect @p[team=!herobrine] 3
Any exclusion fails. I tried with "name=!ogradyjd" and that failed as well. Tried same selector with /msg and /gamemode and both succeeded, so this seems to only affect the /effect command.
Environment
Windows 8.1 Pro 64bit, single player, Java 1.8.0_05 64bit, 32GB RAM, Intel Core i7-4910MQ 2.90Ghz
Tested in 1.8 pre1 and effect works fine for me. It's likely your team commands. I bet changing your command to
may work better to.
Saying that the entity UUID is invalid simply means that it couldn't find any player with those selectors.
I THINK reason it says the UUID is in an invalid format is because, in situations where there are 0 UUIDs in the list (no players/entities with the right information were found), it actually still returns a list containing one null value. When the game tries to find the entity with the id null, obviously null isn't a UUID the game expects. Remember, this is just my guess based on experience, and may be completely wrong.