Character Attribute Logic

[Amsirahc]

@TechLord;327631

Hi Amsirahc, I designed RPGAttribute as a Class instead of a Struct for greater flexibility. The thought at the time was dealing with Character Stats, Skills, Magic, and Items as self-contained objects that may require media components and event logic. Another factor is running into issues updating members in an Array of User Defined Structs in previous versions of the engine, I’ve been weary to revisit. No matter how the data is stored (Data Table, Save Game Object, Remote MySQL) it has to assigned to run-time variables for manipulation, a Struct could be used for this purpose. I would say figuring your RPG Ruleset is the first place to start and Character Attributes is part of that.]([FEEDBACK] Advanced Target System - Showcase - Epic Developer Community Forums)

I completely agree with with the RPG Ruleset as a starting point. It seems like they fixed most of the issues I was running into with updating Structs in previous versions. For all intents and purposes, my Character Attributes (stats) are just a bunch of Floats and Integers at this point, and I don’t see that changing much if at all. I don’t see how I would gain that much using a Class versus a Struct in my case.