I found a new spawn event called "minecraft:born_screamer" and have assumed that it's meant to be used to summon in Screaming Goats. If this is the case, then it does not appear to be working. I used the command "/summon goat ~~~ minecraft:born_screamer", but goat it spawned in seems like the default variant. I've stayed near it for around 10 minuets just to be sure.
Linked issues
is duplicated by 3
Attachments
Comments 8
youtube video showing screaming goat command
I am including the world where I was breeding goats. unfortunately I killed off the 681 goats that I bred. I had to do that in stages since they were getting out of hand.
i started with 2 regular goats and bred until they were unmanageable. I then used the tag command to get an accurant count of goats. tag @e [type=goat]
After waiting for all the goats to grow up I held wheat to keep them near and moved around waiting to hear a screaming goat. As an extra check I had a resource pack applied that altered the screaming goat horns. No screaming goats were noticed. Having verified no screaming goats present yet. I'd breed as many babies as I could then Kill all the tagged goats via command and start the breeding cycle over again.
Expected results would be to see some screaming goats within the first couple hundred goats.
Actual results was zero screaming goats.
Now see the video I've linked. I also tested the summon minecraft:born_screamer command. This was done one at a time and then on a repeating command block.
Expected results would be a screaming goat every time.
Actual results were very infrequent screaming goats. I was surprised that I did eventually get some screaming goats so it seems there is some random chance happening with a command that should have a 100% succsess rate.
I suspect these two things are related.
The command to "
[media][media] /execute @e ~~~ event entity @e minecraft:born_screamer" Does work fine though.
Resource pack to help visually see a screaming goat is also included.
We have determined that the difficulties with summoning a screaming goat and breeding a screaming goat are distinct. Since this report was focused on the /summon command, we will track the low chance of breeding a screaming goat at MCPE-165512.
The reason /summon goat ~~~ minecraft:born_screamer does not produce a screaming goat is that the components added by minecraft:born_screamer get overridden when the goat's mincraft:genetics component randomly chooses a non-screamer allele (98% chance) and then calls minecraft:born_default. Screaming goats spawn when the genetics component randomly chooses the screamer allele, which then triggers the born_screamer event. There is no command to set alleles, therefore you cannot deliberately summon a screaming goat with commands.
This appears to be intentionally designed: the born_screamer event runs as a result of genetics; genetics do not get set as a result of the entity event running. Therefore, I think it may be working as intended. Note that according to the official documentation here, most entity events are not intended to be used as spawn events with the /summon command.
This overall system of events, some of which are meant as spawn events, works well enough in the standard game of Minecraft, but strange things can happen if events are used in unexpected ways.
These strange conditions of entities can be very entertaining, because they're unexpected, they also aren't intentionally supported.
Is this still an issue in the latest version (1.17.10)? If so, can you please add it to the affected versions (or mention it if you are not the reporter).
This ticket will automatically reopen when you reply.