[Feedback wanted] Multi-purpose item struct

[Ardoc]

@vanlacke;445471

So I wrote a long post pointing out the things that stuck out, but I think it’s best to just summarize it: Way too much. It’s good to make a dynamic item, but not UNIVERSAL, if you know what I mean. As a person looking at this, it would take ages and be very complicated to make an item. If you were to do this it’d be best to nest everything correctly, and to avoid an item having variables that it will never use.

Complicated to make an item? All you have to configure is the items struct (the first struct to the left)?

@DevilsD;445472

Inheritance.

Build a base class that contains the essential properties that an Item should have. Using inheritance from this base class you branch down into more specialized versions that only achieve the additional behavior pertinent to that particular subclass of Item. This way you are not wasting properties on Items that would have no need for them at all.

Not a big fan of using a blueprint for holding data, using a struct seems to me the best way to quickly change properties on an item if need be. And it being separated makes it a bit more reusable.