Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
MythicMobs MythicMobs
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 134
    • Issues 134
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • MythicCraft
  • MythicMobsMythicMobs
  • Issues
  • #84

Closed
Open
Created Sep 10, 2020 by DXUltimate@DXUltimate

Item attribute UUIDs are the same, causing other plugins to have a fit.

Summary

Item attribute UUIDs that are applied on the items, have the same UUID, and are causing exceptions to be thrown in other plugins. The Example below is with a premium plugin, EpicCraftingPlus.

Steps to reproduce

  1. Download paper-161+ for 1.16.2
  2. Create item in MythicMobs/Items with attributes
  3. Attempt to put said item in a custom crafting recipe via different plugin

Current behavior

Sample Item Config: https://pastebin.com/vCJJpJ5A The Item in game: https://puu.sh/Grdkl/fcba475548.png The Exception being thrown in EpicCraftingsPlus: https://puu.sh/Grdmd/5f2fd78985.png

Intended correct behavior

Each attribute should have different UUIDs, just as the vanilla minecraft summon of give command gives different attributes.

Server log file

I can provide this if needed, but nothing gets thrown into the console, except for the plugins and server starting up.

Debug log snippet

https://pastebin.com/1yavjFPM

Proposed fixes

I honestly have no idea. Admittedly I'm pretty clueless when it comes to code, but if I had to guess, something about the UUID handlers could be mucking this up and causing it to repeat the UUID for each attribute. Changing the attribute UUIDs themselves (just 1 digit) doesn't fix it. The attrubutes themselves work fine on whichever weapons or tools they are on, but for something like QuantumRPG (aka DivineRPG), I feel like this would cause a lot of issues.

Thanks again for all of your incredible work on this.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking