Today I worked on expanding the action list functionality for the menus, so that it would only show actions the player has the skills and equipment to perform. Presently it’s allowing all the actions that are in the system.
That means I need an inventory for the player, so I can tell what they have equipped. I added a list of a few basic items to a data file but quickly ran into the poor architecture of how I’d set up items to get summoning circles crudely working.
Right now whenever I add a summoning circle, I add a hash to the state.objects array, with x/y/z coords, width and height, sprite path, then I recalculate its screen coords based on what tile its in and its width and such. This is stupid. Every summon circle is going to have the same path, width, height, etc, and the screen coords are totally related to the tile its in. I don’t remember why I did it this way, I assume I was just hacking as quickly as possible to get something working.
Ended up spending more of my dev session refactoring that than adding actual inventory functionality, but it’s for the best.