This adds the possibility to configure the stack identifier parser priority.
You may notice that the item changes its NBT/Data Components when placing it into the GUI, which exactly happens because a parser detected the item as an item linked to another plugin.
The parsers check for the present of plugin specific identifiers and link it if detected.
The parser with the higher priority checks the item stack first.
The bukkit parser will accept all item stacks and stores them as is.
The config is loaded on startup and cannot be edited while the plugin is running, so edit it while the server is stopped and start the server to load the new config.
The config.yml contains the default priorities:
stack_identifiers:
priorities:
"wolfyutilities:mmoitems": 2000
"wolfyutilities:oraxen": 1900
"wolfyutilities:executableitems": 1800
"wolfyutilities:executableblocks": 1700
"wolfyutilities:mythicmobs": 1600
"wolfyutilities:itemsadder": 1500
"wolfyutilities:magic": 600
"wolfyutilities:eco": 100
"wolfyutilities:fancybags": 0
"wolfyutilities:denizen": 0
"wolfyutilities:wolfyutils": 0
# Make sure the bukkit identifier has the lowest priority at all times! This will otherwise overwrite everything
"wolfyutilities:bukkit": -4096
This adds the possibility to configure the stack identifier parser priority.
You may notice that the item changes its NBT/Data Components when placing it into the GUI, which exactly happens because a parser detected the item as an item linked to another plugin. The parsers check for the present of plugin specific identifiers and link it if detected.
bukkitparser will accept all item stacks and stores them as is.The config is loaded on startup and cannot be edited while the plugin is running, so edit it while the server is stopped and start the server to load the new config.
The
config.ymlcontains the default priorities: