-
Notifications
You must be signed in to change notification settings - Fork 573
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes on butterflies placement checks #3116
Conversation
Sorry, I made a commit to the master of my fork to resolve another issue and it ended up in this PR too. Now this PR can fix #3102 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found that butterflies now do replace grass. In master, the butterfly is put to pointed_thing.above
. However, in this PR can be avoided by using sneak + place (like with any other node placement).
Works for me.
I submitted another PR, #3125, which uses the engine's routine to handle butterfly and firefly placement and catching. Every possible interaction exception can be handled by having everything cared for by the engine. |
So can I close this (again)? |
This PR has been approved by core developers, so I would suggest letting them decide. |
I will close this PR. #3125 will be better thant that one |
Fixes #2987 (by using
minetest.item_place
)Fixes #3102 (by renaming the parameters)