@noah I wish to be careful to deliver the feature as you need it. Could I ask you more questions about Prerequisites?
Let's return to the mockup for ITEMS. I am showing a Deluxe Hat Rack.
5e5eb964-36b5-425a-be04-65266c665238-image.png
In this mockup, setting a Prerequisite only means: "Does the player possess these items in their inventory?"
In the illustrated case, if the player has John's Hat and Mark's Hat in their inventory, then they can successfully attempt a purchase of this item.
It will cost them 1,234,234 COINS and 5,345 Credits to receive the item.
In this example, after paying the COINS and Credits to receive the Deluxe Hat Rack, the player still has John's Hat and Mark's Hat in their inventory at the end of the transaction.
So could you verify that when you said, "We had only one step in mind. Consuming items I own while purchasing items" did you mean:
A) prerequisites are not consumed when making an item purchase
OR
B) that you are seeking a system where ITEMS can be included in the List Price of an ITEM?
I have a follow-up question: When the client calls Service ItemCatalog, Operation: GetCatalogItemsPage, would it be your preference that:
Items with prerequisites that the player does not posses should be:
A) Not returned
B) Returned with an attribute, like "CannotBuy"
C) Returned normally?
(Because in a case where the player does not meet the prerequisites they will not be able to successfully purchase the item.)
Could you provide some guidance here.
Thank you for your help and advice,
John