You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bucket of Tadpoles store NBT data called "Age". Age is in ticks, and because of this, it is impossible to have more than one bucket in stock for a chest shop.
ChestShop creates a different ID for every Bucket of Tadpole:
Showing the NBT data of the three different Bucket of Tadpoles:
What did you expect to happen?
Bucket of Tadpole to be all the same ID
Plugin Version
3.12.1 build 347
Plugin Config
Server Version
git-Purpur-1659 (MC: 1.19)
Server Log
What other plugins are you running?
None, as it was on a test server
Agreements
I have checked if there are already similar issues open.
Not sure this is a bug tbh. A player might care what kind of extra values like the Tadpoal age is on the item when purchasing it. If anything this needs to be included in the messages on /iteminfo and /shopinfo and the eventual wildcard support (#471) be used for selling all kinds of buckets.
I agree with @JustEli. My players are also having issues with this. It forces players to literally make a shop for every tadpole as every tadpole has a different ID when doing the /iteminfo command. Time is fair to mention but if that is something people want they shouldn't have to make a new chestshop for every tadpole they want to sell
What is happening?
Bucket of Tadpoles store NBT data called "Age". Age is in ticks, and because of this, it is impossible to have more than one bucket in stock for a chest shop.
ChestShop creates a different ID for every Bucket of Tadpole:
Showing the NBT data of the three different Bucket of Tadpoles:
What did you expect to happen?
Bucket of Tadpole to be all the same ID
Plugin Version
3.12.1 build 347
Plugin Config
Server Version
git-Purpur-1659 (MC: 1.19)
Server Log
What other plugins are you running?
None, as it was on a test server
Agreements
Additional context
No response
The text was updated successfully, but these errors were encountered: