Attribute#mergeAttributes doesn't respect modifier UUIDs
See original GitHub issueAttribute#mergeAttributes completely ignores the UUIDs of the modifiers in the input multimaps, causing problems for code that depends on particular UUIDs (such as Item.ATTACK_DAMAGE_MODIFIER_ID
). I’m not sure what the intended behavior for this method is.
Issue Analytics
- State:
- Created 3 years ago
- Comments:15 (6 by maintainers)
Top Results From Across the Web
Custom attribute modifiers that use the vanilla UUIDs don't ...
There are two different ways that item attribute modifiers can display: 1. "Direct": where the final value of the attribute appears in green ......
Read more >UUID usage in '/attribute ... modifier ...'? - Reddit
Basically, you have to give them different UUIDs so that they don't overlap. If I accidentally give two max health modifiers with the...
Read more >Help with attributes - Bukkit Forums
An attribute is a NBTTag that contains a string 'Name' a double 'Base' value and then a list of 'Modifiers'. each modifier then...
Read more >Ignore UUIDs in attribute modifiers when comparing items
I want to ask, if there is some way to do it with attribute modifiers. public static Object item() { ItemStack item =...
Read more >Hibernate ORM 6.0.2.Final User Guide - Red Hat on GitHub
Declare getters and setters for persistent attributes; 2.4.5. Providing identifier attribute(s); 2.4.6. Mapping the entity; 2.4.7. Implementing equals() and ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ll take a look when I can.
Closed by #1355.