From mrpingouin1's comment on MC-89773:
Can confirm for all non EntityLiving entities.
AreaEffectClouds do not respect teams when using an @e selector.
Problem:
– Type the following commands into command blocks and run them.
summon AreaEffectCloud ~ ~1 ~ {CustomName:"BrushTest",CustomNameVisible:1,Tags:["BrushTest"],Duration:6000}
scoreboard teams add Red
scoreboard teams option Red color red
/scoreboard teams join Red @e[name=BrushTest]
execute @e[type=AreaEffectCloud,team=Red] ~ ~ ~ say Something Should Happen— result —
The AEC's name will turn red, and show up on teams list. But it won't execute the commands.
— Desired Result: —
[BrushTest] Something Should Happen
Other entities work with the team selector filter, but not AreaEffectClouds!
Remove the "team=" filter, and every AEC on the map executes the command.
Linked issues
Comments 3
It has been suggested that only 'Living' entities can be on teams, and AECs are not 'Living'. There is a bug either way, since you can add an AEC to a team, but it does not respect @e[team=XXX] selectors (and maybe also Team:XXX summons). Either it should not allow you to add it to the team in the first place, or all the team stuff should work; AEC is in an inconsistent place now.
You can add anything to a team, as long as it's an entity, arrows, armor stands, tnt, etc
EAC not respecting team= is the only one
However team friendly fire, etc is another story
Confirmed to be in
15w39b.
A work around that I found
to this bug is just to give
the AreaEffectCloud a RedTeam
tag, so like this:
THEN Run the execute
by doing: