-
-
Notifications
You must be signed in to change notification settings - Fork 958
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
Remove offset on certain potion strength values #3592
Conversation
Are you sure that check wasn't important for something else in the code? |
Have checked usage with power at crazier levels (+50) and it works as expected. I'm of the opinion if any user opts to set potion power a to crazier amount it's their responsibility but let me know what you think about setting an upper limit; just this time higher than 4. |
Have you checked all the way back to Minecraft 1.8? Sometimes weird things like this result from incompatibilities in older versions. Although it could very well be that this check isn't needed anymore, just needs to be absolutely 100% confirmed so that we aren't reintroducing a bug or something. |
Ah I see, maybe it would be smart to still add a potions.unsafe permission node + config similar to the enchantments stuff, for the levels that do not display properly in game. |
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.
Looks good to me 👍
ce51a07 added this offset behaviour so that To clarify: EssentialsX has never enforced an upper limit on potion strengths, and this PR doesn't remove such a limit. Instead, this PR removes the limit on the values that get offset by Changing this check will change the power applied for all potions in kits, I'd prefer we added an alternative syntax that doesn't attempt to offset potion effect strength, as this would avoid breaking existing kits/potions. I've opened #3614 with an implementation of this, which allows you to replace |
Adds an `amplifier:<value>` potion meta attribute to MetaItemStack that applies a raw amplifier value, instead of translating inputs between 1 and 3 to match their vanilla names like `power:<value>` does. This matches the Mojang `/effect` command, which doesn't translate any potion effect amplifiers, and allows for creation of level IV potions (using `amplifier:3` instead of a `power` value) through EssentialsX without breaking existing usages of `power:<value>`. More context for this commit can be found at #3592 (comment). Closes #3592 and fixes #3589.
Adds an `amplifier:<value>` potion meta attribute to MetaItemStack that applies a raw amplifier value, instead of translating inputs between 1 and 3 to match their vanilla names like `power:<value>` does. This matches the Mojang `/effect` command, which doesn't translate any potion effect amplifiers, and allows for creation of level IV potions (using `amplifier:3` instead of a `power` value) through EssentialsX without breaking existing usages of `power:<value>`. More context for this commit can be found at EssentialsX#3592 (comment). Closes EssentialsX#3592 and fixes EssentialsX#3589.
fixes #3589