Certain entities can't be selected by type
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 by11
MC-49653Eggs and Fishing hooks have Names =unknownDuplicateMC-50389You can't detect or summon a thrown chicken egg.DuplicateMC-51621If you use the /say @e and you have a fishing rod you get unknown but to testfor it don't workDuplicateMC-55424Unknown entityDuplicateMC-68846Chicken Egg Entity NameDuplicateMC-74111Fishing Rod Hook does not seem to have a targetable entity IDDuplicateMC-87207The Fishhook havend a Minecraft ID!!DuplicateMC-87361Execute not working on lightning DuplicateMC-94842Fishing rod bobber does not have an entity nameDuplicateMC-108767Fishing Rod Missing Entity NameDuplicateMC-109458Fishing hook entity's name is "unknown"Duplicate
Created Issue:
Testfor egg not working.
Type into a commandblock testfor @e[type=Egg], and put the commandblock on a clock. Attack a comparator to the commandblock and throw and egg. As you can see the comparator will not light up, and the commandblocks previous output will remain as unknown command.
relates to
Testfor egg not working.Certain entities can't be selected by type
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
is duplicated by
is duplicated by
![[Mojang] Searge (Michael Stoyke)](../../../data/assets/gravatar/searge.png){kind=small}
[Mojang] Searge (Michael Stoyke)Type into a commandblock testfor
@e[type=Egg] , and put the commandblock on a clock. Attack a comparator to the commandblock and throw and egg. As you can see the comparator will not light up, and the commandblocks previous output will remain as unknown command.Type into a commandblock testfor
@e [type=Egg], and put the commandblock on a clock. Attack a comparator to the commandblock and throw and egg. As you can see the comparator will not light up, and the commandblocks previous output will remain as unknown command.
Type into a commandblock testfor
@e [type=Egg], and put the commandblock on a clock. Attack a comparator to the commandblock and throw and egg. As you can see the comparator will not light up, and the commandblocks previous output will remain as unknown command.Fishing rod bobbers and Lightning bolts have no way to specify their type in selector arguments. This may be intended for lighting bolts,
Fishing rod bobbers and
Lightning bolts have no way to specify their type in selector arguments. This may be intended for lighting bolts,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.
relates to
relates to
is duplicated by
is duplicated by
is duplicated by
![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
relates to
is duplicated by
is duplicated by
Duplicate of MC-47832
![[Mod] Sonicwave](../../../data/avatars/users/94627.png){kind=small}
Probably a duplicate of MC-47832.
Why does this count a feature request when something like MC-47832 counts as a bug? They are both instances of Mojang forgetting to add a specific instance of something.
Other reports of Mojang forgetting to add some instances of something when all the other ones were included, like MC-47832, have been accepted as bugs. Why not this one?
In MC-47832, most entities could be selected, but a few couldn't. In this ticket, most keys can have their bindings changed, but a few can't. In both cases, Mojang added some functionality to the game, but excluded a few instances of that function.
Probably intended as LightningBolt is no "real" entity.
Else probably duplicate of MC-47832
Relates to MC-47832
![[Mod] Skylinerw](../../../data/assets/gravatar/skylinerw.png){kind=small}
@Brenden Smith It's not a bug, see the resolution for MC-47832.
"unknown" isn't a type, it's a display name (which is also dependent on your language and always has been). You would use @e[name=unknown] to try selecting it, not @e[type=unknown].
Excluding the type parameter just means you're not looking for any specific entity type in particular.
The method involves using /scoreboard to assign a tag to entities that have a savegame ID or alias and then targeting entities that do not have that tag (i.e. they don't have a savegame ID or alias):
/scoreboard players tag @e[type=minecraft:skeleton,tag=!savegame] add savegame
/scoreboard players tag @e[type=minecraft:creeper,tag=!savegame] add savegame
...
/say Entities with no "savegame" tag: @e[tag=!savegame]
As for assigning a savegame ID to fishing bobbers, that wouldn't be possible since bobbers are not supposed to be saved to chunks as they are meant to be tied to the player. However, like lightning bolts and players (which are also not savegame entities), they can have an alias that can be used to target them (though it doesn't work for lightning bolts currently, see MC-64623). But the report for doing so was closed as "Working as Intended": MC-47832
EDIT: Concerning item names, you should not target item entities by their name like that. That is another bug that, when fixed, would require you to change all commands targeting such entities: MC-73495
You're doing it wrong, use:
testfor @e[type=Item] {Item:{id:minecraft:egg,Damage:0s,Count:1b}}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.
Entity list in the screenshot created with "/say @e", all the eggs are listed as "unknown.
Still present in 14w25b.
Also present in 14w28a.
Present in 14w28b.
How do I select an egg in a execute command? example: /execute @e[type=Item]...
You don't...that's the bug.
Is this still a concern in the current Minecraft version 1.8.1 Prerelease 3 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
It's still present in 1.8.1pre3.
Reopened, thanks
What kumasasa posted is the proper way to test for a thrown egg, but there should be a separation between the egg item and a thrown egg.
{id:minecraft:enderpearl,Damage:0s,Count:1b}For example, an ender pearl item is treated differently from a thrown ender pearl.
testfor @e[type=ThrownEnderpearl] vs. testfor @e[type=Item] {Item:
}
Confirmed for 1.8.2-pre6
The fix makes it possible to test for thrown eggs by using @e[type=ThrownEgg] as selector.
Which fix?? I can't use it on 1.8.3.
Is this bug report just for eggs? Because there is still no way to select fishing rod bobbers by type.
Reopened, under the condition that a full list with entities that don't work yet will be created. Issue will be given to anyone that is willing to keep it up-to-date as well.
Works for everything except fishing rod bobbers and lighting bolts. Should I create a new report for those?
You're reporter of this ticket now, edit it appropriately.
Can confirm this "issue" for the current snapshot 15w36d.
(You should be able to quickly check this by using auto-complete on the summon Command in any upcoming Snapshot.)
This is confirmed for 15w36d
Mojang, can we get clarification on this? I can understand it being intended for Lightning Bolts, but Fishing Rod Bobbers are normal entities, they should work fine.
Yes, fishing rod bobber should be fixed, because GrapplingHooks on command blocks!
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.
Intended, read the ticket and resolution.
Regardless of intention, this has been fixed as of 18w02a/1.13.