Replies: 4 comments
-
This looks like a "default" reason, then can make a PR for add a new enum for this cases like SPAWNER_BUCKET (for make the same syntaxis than SPAWNER_EGG) |
Beta Was this translation helpful? Give feedback.
-
I think the spawn reason should be preserved through picking up and placing down a mob with a bucket. Now it just resets it to SPAWNER_EGG. If you have it persist the spawn reason in item, I think SPAWNER_EGG is still sensible default, if one isn't present on the stack already. |
Beta Was this translation helpful? Give feedback.
-
See also #4361 (comment) regarding this, seems like a similar issue |
Beta Was this translation helpful? Give feedback.
-
Thanks for the reference. |
Beta Was this translation helpful? Give feedback.
-
Is your feature request related to a problem?
When a player uses a bucket with a fish or axolotl, the event
CreatureSpawnEvent
is fired with the reasonSpawnReason.SPAWNER_EGG
, that is not the real reason.When we use a plugin that logs specific entity spawns (SPAWNER_EGG for instance), we thought that a player where using spawner-eggs (that is not obtainable in survival) but we figured out that the player was only using buckets in water.
Describe the solution you'd like.
Add a new entry in the
CreatureSpawnEvent.SpawnReason
enum, maybe likeEMPTY_BUCKET
,BUCKET
or something named more appropriately.And of course, calling the event with the appropriate new
SpawnReason
when a player empties a fish/axolotl bucket.Describe alternatives you've considered.
Since the player spawning the entity is not referenced by the
CreatureSpawnEvent
, it is not possible to get what’s in the hand of the player, thus it is not possible to deduce if it was a spawner-egg or a bucket.Other
No response
Beta Was this translation helpful? Give feedback.
All reactions