We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In 1.21.1 AttributeModifiers now use NamespacedKey rather than UUID.
Currently the method to add a modifier is
AttributeModifier(UUID uuid, String name, double amount, AttributeModifier.Operation operation, EquipmentSlot slot)
The new method is
AttributeModifier(NamespacedKey key, double amount, AttributeModifier.Operation operation, EquipmentSlotGroup slot)
This means we can add a modifier but then have no reference of what it actually is because getName() will now return the NamespacedKey
I have attached a screenshot of /attribute list between 1.21 and 1.21.1 1.21.1 1.21
The text was updated successfully, but these errors were encountered:
Updated: Smallish fix for /attribute list/remove, both are still brok…
97d107b
…en though #35
No branches or pull requests
In 1.21.1 AttributeModifiers now use NamespacedKey rather than UUID.
Currently the method to add a modifier is
AttributeModifier(UUID uuid, String name, double amount, AttributeModifier.Operation operation, EquipmentSlot slot)
The new method is
AttributeModifier(NamespacedKey key, double amount, AttributeModifier.Operation operation, EquipmentSlotGroup slot)
This means we can add a modifier but then have no reference of what it actually is because getName() will now return the NamespacedKey
I have attached a screenshot of /attribute list between 1.21 and 1.21.1


1.21.1
1.21
The text was updated successfully, but these errors were encountered: