Best practices with Data tables?

[Castle]

@Nawrot;503200

Look into scene components or blueprint components.
Make interface in weapon that is for eg. “set stats”
make component that from its parent expects actor with interface “set stats”.

Now create parent component that just knows how to call interface and pass over those stats.
Then create inherited components with different stats.
Expose all stats as editable variables, so you can see them from weapon blueprint.
Or totally opposite, lock them tightly inside those component blueprints so you are sure they are changed only from within component blueprint.
Or make those components read some data tables.
That is beauty of components, they are like inherited variants of blueprints but without all those “cant do because inherited” stuff. You can drop same component on different parent classes, all you need to do is implement one interface function in parent.

When you have all that ready make your weapons as you wish, then drop components with stats on them

For eg i did all that component stuff for fire and autofire mechanics for all my weapons.
All firing logic is inside one component, it has fire_enum type and autofire delay.
Then it tells parent weapon when to fire.
It also can handle disconnects and lagg in multiplayer.
Same component for machine gun sniper, flamethrower rocket launcher etc.

Do you know of any boiled down working examples of this I can take a look at? Its definitely interesting but kind of hard to visualize.