Trigger bee_nest_destroyed trigger in the correct place #7436
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
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. |
|
I have a datapack that relies on this. Any status on merging?
… On Apr 3, 2022, at 11:01 PM, stale[bot] ***@***.***> wrote:
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.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
|
electronicboy
approved these changes
Apr 8, 2022
Machine-Maker
force-pushed
the
fix/bee-nest-broken-trigger
branch
from
6061a83
to
75ee44b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reported here: https://forums.papermc.io/threads/datapack-using-advancements-to-run-functions-on-newly-spawned-item-not-working.119
Issue here, is that drops were being captured for the BlockDropItemEvent and not actually in the world. The
bee_nest_destroyedtrigger is expecting to be run after those drops are in the world.