MC-68564Non-mob entities cannot be targeted by team
The ability to add random entities to teams that aren't players or mobs may seem useless, but it is actually very convenient for certain builds I'm participating in. However, there is a problem with these NPNM (nonplayer nonmob) entities in regards to the [team] target selector argument.
From my testing, I've found that NPNM entities cannot be targeted using this argument. This might not be a bug in the literal sense since it's probably unintended for NPNM entities to be on teams anyway, but since the "feature" happens to work regardless, it would be nice to be able to use this target selector with these entities, along with any other arguments that don't work if there happen to be any.
In the following picture, any entity with the custom name of AngleTrackMe is placed into the debugangle team automatically by a clock. There are currently 6 entities in the team, but when running the command in the chatbar it only finds my player and the three mobs in the team, ignoring the two NPNM entities that are also in the team.
Environment
'os.name' == 'Windows 7'
'os.version' == '6.1'
'os.arch' == 'amd64'
'java.version' == '1.7.0'
Linked Issues
Attachments1
Created Issue:
Non-Player, Non-Mob Entities not interacting with [team] target selector argument properly
The ability to add random entities to teams that aren't players or mobs may seem useless, but it is actually very convenient for certain builds I'm participating in. However, there is a problem with these NPNM (nonplayer nonmob) entities in regards to the [team] target selector argument.
From my testing, I've found that NPNM entities cannot be targeted using this argument. This might not be a bug in the literal sense since it's probably unintended for NPNM entities to be on teams anyway, but since the "feature" happens to work regardless, it would be nice to be able to use this target selector with these entities, along with any others that don't work if there happen to be any.
In the following picture, any entity with the custom name of AngleTrackMe is placed into the debugangle team automatically by a clock. There are currently 6 entities in the team, but when running the command in the chatbar it only finds my player and the three mobs in the team, ignoring the two NPNM entities that are also in the team.
Environment
'os.name' == 'Windows 7'
'os.version' == '6.1'
'os.arch' == 'amd64'
'java.version' == '1.7.0'
Attachments1
The ability to add random entities to teams that aren't players or mobs may seem useless, but it is actually very convenient for certain builds I'm participating in. However, there is a problem with these NPNM (nonplayer nonmob) entities in regards to the [team] target selector argument.
From my testing, I've found that NPNM entities cannot be targeted using this argument. This might not be a bug in the literal sense since it's probably unintended for NPNM entities to be on teams anyway, but since the "feature" happens to work regardless, it would be nice to be able to use this target selector with these entities, along with any other arguments that don't work if there happen to be any.
In the following picture, any entity with the custom name of AngleTrackMe is placed into the debugangle team automatically by a clock. There are currently 6 entities in the team, but when running the command in the chatbar it only finds my player and the three mobs in the team, ignoring the two NPNM entities that are also in the team.
Non-Player, Non-MobEntities notinteracting with [team] target selector argument properlyNon-mob entities cannot be targeted by team
relates to
is duplicated by
Still present in 14w34d
Confirmed. This looks similar to
MC-53022.A potential workaround if or until they can fix this.
How I did it was I got all the entities that I wanted to select ( by team ) and changed their scoreboard score to 1. then selected them based on that scoreboard score.
/scoreboard players set @e[r=3,type=ArmorStand] somescoreboard 1
/tp @e[type=ArmorStand,score_somescoreboard_min=1] ~ ~ ~ ~50 ~ ( or whatever you want to do )
I agree that targeting by team would be easier but this is a solution I am using till the decide if they want to make it possible or not.
just checked in both 1.8.1 and 1.8.2 pre 1 and they both still have this issue; tested with boats in particular, can also try with other entities if needed.