Fishing rod bobbers and lightning bolts have no way to specify their type in selector arguments. This may be intended for lighting bolts, as they only last a short amount of time, but it is certainly a bug for fishing rod bobbers. These 2 entities are the only remaining entities to have this problem. All other entities do now have a way to select them.
Linked issues
is duplicated by 11
MC-49653
Eggs and Fishing hooks have Names =unknown
Resolved
MC-50389
You can't detect or summon a thrown chicken egg.
Resolved
MC-51621
If you use the /say @e and you have a fishing rod you get unknown but to testfor it don't work
Resolved
MC-55424
Unknown entity
Resolved
MC-68846
Chicken Egg Entity Name
Resolved
relates to 3
Attachments
Comments 27
Still present in 14w18a, both thrown Eggs and the Fishing Hook will be type unknown if you do /say @e to get a list of all the entities in the world. Both can't be summoned or used in a /testfor @e[type=...] command.
I think all of these should be fixed, so that mapmakers can detect when you throw an egg, cast a fishing rod, or when lightning spawns. Choosing not to fix this is an awful annoyance. What if you want to make thrown eggs have particle trails? What if you want to effect fishing rod bobbers with glowing? What if you want lightning to transform a mob into a custom mob? There is SO much potential, and it would be so simple to fix.
This is still an issue for me in the latest snapshot. /execute @e ~ ~ ~ say hi returns "unknown" if a fishing rod bobber is present in the world, and the only way select a fishing rod bobber that I know of is by using the entity selector @e[name=unknown], which could easily select other entities.
You're doing it wrong, use: