when user initiates breeding (using .requestBreed) they should be able to select items to use in influencing the outcome of breeding (see items DB for examples).
.breed() should consume the item at the same time that their breeding crystal is consumed (ie when all parties have agreed to breeding).
Ultimately, items DB should prevent users from submitting two of the same type of item (ie two markings items or two palette items). In initial release this will likely have to be stopped by artist. If necessary an item can be refunded.
Challenge here is in allowing users to enter an indeterminate number of items (maybe a `args` at end of string to capture Item IDs)*
An alternate plan could be to have a command called .useItem or similar and have it take a ticket # as an argument. That way the user controls when it's consumed, rather than having the bot handle it.
when user initiates breeding (using .requestBreed) they should be able to select items to use in influencing the outcome of breeding (see items DB for examples).
.breed() should consume the item at the same time that their breeding crystal is consumed (ie when all parties have agreed to breeding).
Ultimately, items DB should prevent users from submitting two of the same type of item (ie two markings items or two palette items). In initial release this will likely have to be stopped by artist. If necessary an item can be refunded.
Challenge here is in allowing users to enter an indeterminate number of items (maybe a `args` at end of string to capture Item IDs)*