Implementing an inventory system with right click actions
This is really a hypothetical question as I'm not working on anything like this at the moment, but I've wonder in the past what the best way to approach this would be and haven't been able to come up with any good resources.
Let's say I'm making a game, and the game design required an inventory system. The main thing this system should allow for is the following:
1. It should be able to keep track of items, naturally. For simplicity's sake, no item stacking is allowed, so singular items only.
2. Items should have actions that you can execute via a right click menu, e.g. "Consume" for consumables, "Equip" for equippables, and "Drop" for all.
The first solution that comes to mind is creating a base class / interface for
With this setup, what would be the "right" way to implement actions that are specific to certain types of items? Presumably the right click menu would be populated like this:
Would it make sense to have the classes deriving from item define which actions should be added to the menu? If not, how would you go about fetching valid actions for any given
Alternatively, does all I've mentioned above make sense, or would an entirely different structure be preferred here?
Any hints on where to start looking for this kind of design would also be appreciated.
Let's say I'm making a game, and the game design required an inventory system. The main thing this system should allow for is the following:
1. It should be able to keep track of items, naturally. For simplicity's sake, no item stacking is allowed, so singular items only.
2. Items should have actions that you can execute via a right click menu, e.g. "Consume" for consumables, "Equip" for equippables, and "Drop" for all.
The first solution that comes to mind is creating a base class / interface for
ItemConsumableEquippableList<Item>InventoryWith this setup, what would be the "right" way to implement actions that are specific to certain types of items? Presumably the right click menu would be populated like this:
Would it make sense to have the classes deriving from item define which actions should be added to the menu? If not, how would you go about fetching valid actions for any given
ItemAlternatively, does all I've mentioned above make sense, or would an entirely different structure be preferred here?
Any hints on where to start looking for this kind of design would also be appreciated.
