-
Bug
-
Resolution: Awaiting Response
-
None
-
Minecraft 14w31a, Minecraft 1.8, Minecraft 1.8.1-pre5, Minecraft 1.8.1, Minecraft 1.8.3, Minecraft 1.8.8
-
None
-
Mac OS X 10.9.4 (13E28)
Java 1.8.0_20
-
Community Consensus
Summary:
When using @e selectors to target villagers, that were previously unloaded, it fails to execute and says "That entity cannot be found".
Note: Recently the same issue happened with silverfish, might be affecting all mobs (never happened with other entities though)
Note 2: Had this happen with Armor Stands as well, fairly certain that this happens with all entities
Note 3: Having two entities with the same UUID and killing one causes same behaviour
How to reproduce:
1) Spawn a couple of villagers (e.g. spawn-egg or summon command)
2) Teleport away to unload their chunk
3) Teleport back to them
4) Try targeting them with @e (e.g. /kill @e)
5) It should give the "That entity cannot be found" error for most of them
- is duplicated by
-
MC-68255 When attempting to kill all entities bar the player, some entities are exempt and remain alive.
- Resolved
-
MC-73910 When unloading an entity, and then reloading, "that entity cant be found"
- Resolved
-
MC-77871 Constant commands running on entities in unloaded chunks can cause entities to become 'nonexistant'
- Resolved
- relates to
-
MC-54842 @e selector cannot find villagers in "old" 1.7.x worlds
- Resolved