I am running a plugin called CustomItems; that stores a specific tag called "com.jojodmo.customitems.internalVersion" and its value is a string. However; upon adding this (along with any other CustomItem item with this tag) the data type gets converted from a String to an Integer and this becomes an extremely horrid issue with stacking so now there are multiple different types of the same item but are not unstackable due to them now having different NBT data (Functionality of CustomItems through DropEdit2 is not lost though so that is good)
Steps to recreate:
1) get an item; and set a NBT data tag with a data type of String and a value of 1 as a String (I am not sure why CustomItems even sets this as a string to begin with)
2) Add the item to DropEdit2 with a NBT tag of 1 set to a String value to the ItemStack
3) Get the dropped item and run the /data command and you will notice that the data type is changed!
I am running a plugin called CustomItems; that stores a specific tag called "com.jojodmo.customitems.internalVersion" and its value is a string. However; upon adding this (along with any other CustomItem item with this tag) the data type gets converted from a String to an Integer and this becomes an extremely horrid issue with stacking so now there are multiple different types of the same item but are not unstackable due to them now having different NBT data (Functionality of CustomItems through DropEdit2 is not lost though so that is good)
Steps to recreate:
1) get an item; and set a NBT data tag with a data type of String and a value of 1 as a String (I am not sure why CustomItems even sets this as a string to begin with)
2) Add the item to DropEdit2 with a NBT tag of 1 set to a String value to the ItemStack
3) Get the dropped item and run the /data command and you will notice that the data type is changed!
I am running a plugin called CustomItems; that stores a specific tag called "com.jojodmo.customitems.internalVersion" and its value is a string. However; upon adding this (along with any other CustomItem item with this tag) the data type gets converted from a String to an Integer and this becomes an extremely horrid issue with stacking so now there are multiple different types of the same item but are not unstackable due to them now having different NBT data (Functionality of CustomItems through DropEdit2 is not lost though so that is good)
Steps to recreate:
1) get an item; and set a NBT data tag with a data type of String and a value of 1 as a String (I am not sure why CustomItems even sets this as a string to begin with)
2) Add the item to DropEdit2 with a NBT tag of 1 set to a String value to the ItemStack
3) Get the dropped item and run the /data command and you will notice that the data type is changed!