Paper
Paper copied to clipboard
PaperMC
Add API to get if an entity can be sheared/simulate being sheared.
Not sure if the source is needed in the method, but I thought it might be neat to include.
Ignore the references :sweat_smile: I typo-ed the "Resolves" link from 6797 to 6796.
Some entities also implement an interface called Bucketable, which could allow us to add some methods such as being able to get the item produced when bucketing it, or forcing it to be bucketed too.
This is somewhat similar to this PR, in that it just exposes an interface that certain entities can implement. Should I make this PR a bit more "generic" to "Expose Vanilla Entity Interfaces" or something?
So I am proposing I add the Bucketable interface to this PR as well.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
Something that should at least be documented to some extent is that the entity may no longer be valid after shearing, such as in the case of a Mooshroom, it will be replaced by a new entity.
Also, do we care about calling the shear events and returning a boolean? Interested what others think on both these concerns.
Something that should at least be documented to some extent is that the entity may no longer be valid after shearing, such as in the case of a Mooshroom, it will be replaced by a new entity.
Also, do we care about calling the shear events and returning a boolean? Interested what others think on both these concerns.
Personally I think that the event here can still be followed, as it's supposed to simulate as if it were sheared by a player/source. But yea, i'd wonder what other swould think to.
And yep, documented & rebased!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had activity in a long time. If the issue still applies to the most recent supported version, please open a new issue referencing this original issue.