-
Bug
-
Resolution: Fixed
-
Minecraft 14w04b, Minecraft 14w05a, Minecraft 14w06b, Minecraft 14w07a
-
None
-
Windows 7 - Java 64bits
-
Unconfirmed
The @a selector (but only without a radius/area defined via r/rx/ry/rz) will include dead players in the next snapshot. All other selectors work as intended.
EDIT 2 : simple way to reproduce this bug :
1. Create a random scoreboard objectives : /scoreboard objectives add random dummy - /scoreboard objectives setdisplay sidebar random
2. Setup a hopper clock runing on a commandblock with this command : /scoreboard players add @a random 1
3. You will see your score increasing
4. Kill you with the /kill command : your score doesn't increase anymore (the @a couldn't find you)
EDIT : ok doing more research it appears that none of the selector detect a player when he is dead (and haven't respawn yet). I'm not sure if it's a bug or intentional, but as described in the documentation, @a should target any player, without taking into account any other condition (ex : dead or not). A player dead is still a player and should be in the @a collection.
Original description : Since the 1.8 snapshots, deathcount objectives (or stats.deathcount, same problem) are updated when the player respawn, not when the player died as it was before. It should be updated when the player died.
- is duplicated by
-
MC-47022 When Dead, testfor @a does not work
- Resolved
-
MC-47264 deathcount doesn't detect players dead because of selectors @a @p @e @r
- Resolved
-
MC-47809 @a,@e,@p and @r still dont work for death players
- Resolved
-
MC-54056 /scoreboard player set @p no longer works on dead players
- Resolved
-
MC-55737 Minecraft @p selector don't work for dead players
- Resolved
- relates to
-
MC-123013 @p/@r can select dead players and distance/dx/dy/dz parameters do not exclude dead players
- Open
-
MC-108307 Cannot select dying entities
- Resolved