Solved On remove item from virtual treasure chest event?

[Sordrin]

I am using the plugin TreasureChest which allows me to turn a chest and its contents into a virtual treasure chest which can be opened and accessed by anyone who clicks to open the chest, and then are presented with a virtual chest containing the items set for that treasure.

There is one particular item I have (a named ink sac) that I need to not stack. I know that all I need to do to prevent the item from stacking is to change the NBT data of the items and make them unique. Problem is, this item is stored as-is in the virtual chest, and everyone receives the same exact item with the same NBT data, and can receive it multiple times, so I need a sort of "on loot" method to change the NBT data for that particular item when it's looted, no matter how it was taken. Whether by clicking and dragging, or shift-clicking to loot it, I need it to be modified before they have a chance to stack it.

I can't seem to find an event that catches the action of removing the item from a virtual chest or receiving the item from the chest. Any suggestions?

Thanks.

 

[Time4Games]

you can use on inventory click to detect if someone clicks on an item inside a chest

 

[Purple Pixel]

Can you just add a whitespace after the name of the inc sack. Like go online and find a copy and paste whitespace site and paste that on the name of the item. (Use a anvil)

 

[Sordrin]

Can you just add a whitespace after the name of the inc sack. Like go online and find a copy and paste whitespace site and paste that on the name of the item. (Use a anvil)

I am actually generating the item with a command, and it has a green name. The problem is, once I put it in the treasure chest, it is essentially duplicated as-is every time someone loots that chest. They get an exact replica of that item no matter what name, lore or NBT data I assign it before setting the chest with that item in it. Which makes it stackable.

I will try on inventory click and see if I can catch it there. Just need to make sure that covers any possible method of obtaining the item. It's very important that it doesn't stack, because I discovered a dupe bug in my code based on the fact that they are stackable right now.