Urm92
March 31, 2016, 3:05pm
2
So I have been playing around with data tables a bit more and I have to say they are quite awesome. On my current project, that is not currently using data tables, what I do is define an actor class and add a struct to it. I would then be able to make children of that actor and define the variables that make each child different from the base class.
However, it seems that with data tables I am dealing with a much different beast somewhat invalidating the above work flow.
So lets say I have a project with 30 different weapons and 30 different armor types. With the old method I would just make one kind of item as my base class then make children for weapons armor ect. I could then define what weapons are shotguns or sniper rifles by defining those child classes in that way. Same with armor, I can make helmets, boots, legs, body gloves ect.
But with data tables it almost seems like I don’t actually need to do things in this way. With data tables it almost feels like all I need is one object and I can then just specify the name of the data table row and be done with it.
Here is the thing though, While data tables are really great, I am not sure if they will be super great when working with hundreds of objects. For example if I lump all armor types into the table Then I end up with a giant list and it will end up being a pain to organize it at all. If helmets are at the top of the list then every time I add a new helmet I end up leaving it at the bottem of the list or being forced to slowly move it up to the top of the list potentially causing other problems.
So what is the best way to do this?
Always depends on what you need or want.
You could for example just start every Row of Amor data with “Armor” and search for it, so you only see Armor data.
