Hey Jack! Thank you and yea after looking over your code, complexity is the word of the day!
I at the very least tried to pick my way through some of your BP’s, such as JCInventoryCore and JCInventoryLibrary each with 30+ *Functions *and I didn’t know where to begin, what would break something elsewhere nor how to make meaningful additions/changes…
…so now I’m thinking what will be more empowering to users is documentation, including categorizing which Blueprints the user should focus on if they wanted to do things such as change how items can be used in the world for interaction, additional menu options (like my ‘Craft’ idea) and adding attributes to items (the ‘Ammo’ idea). I know a bunch of these Blueprints are ‘support’ functions (e.g. GetItemDataName, randomly chosen), so we’d need only to be pointed in the direction of the Blueprints where meaningful changes can be made.
This isn’t a criticism but I did expect the Blueprints to be fully commented, explaining what was happening (within reason) at any given chunk of nodes, and again how users can modify the code without breaking it. I’ve spent years with Unity and assets from the Asset Store and I’ve become accustom to that degree of support from an asset, even if it took a few versions before the developer was able to accommodate users.
That said, I’m very impressed by your work and look forward to seeing JCInventory evolve!
Thanks again Jack
-Steven