Skip to content
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

Osmotic Enchanter doesn't lose your settings when you add/remove a wand before starting enchantment #1054

Open
wants to merge 6 commits into
base: 1.7-final
Choose a base branch
from

Conversation

SarahKirksey
Copy link

I can't tell you how many times I've configured a tool or weapon with the perfect enchantment set, realized there's no wand in the table, and added a wand before clicking the button to start the enchantment. Every time, I died a little inside. I've spoken with others, and the ones who have also done this have agreed that this behavior is not desired. Since I was modifying the code to fix the Infused Seeds bugs, adding one more change to the mix was easy enough. So, I set the enchanter to stop scrubbing the configured enchantments every time the block is marked dirty.

@GaeaKat
Copy link
Member

GaeaKat commented Jan 12, 2022

This one will need more testing before it is PR'd, as this is for an older version this will take more then a couple days. The previous behaviour was due to exploits that occurred, and I need to make sure it does not re-introduce them, or if people are having trouble, find a new way to patch

@SarahKirksey
Copy link
Author

That's more than fair! Thank you for the prompt responses! Do you have any additional information regarding the nature of the exploits in question?

SarahKirksey and others added 2 commits January 11, 2022 20:26
…nd before starting enchantment

Revert "Osmotic Enchanter doesn't lose your settings when you add/remove a wand before starting enchantment"

This reverts commit 6eb0013.

Revert "Revert "Osmotic Enchanter doesn't lose your settings when you add/remove a wand before starting enchantment""

This reverts commit 01f6bd80f2511bccee723a396c1b74381c3b410f.
For some unidentified reason, the last attempt broke the enchanter entirely. This approach should function as intended and offer better performance.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants