Testing it on every tick sounds like unnecessary overhead by default. Putting an event/dispatcher call within SetValue works just fine for 1-2 variables but I have much larger numbers.
Tried a map where the key is an enum with the name of the stats basically while the value is a struct of the floats mentioned above and writing a single SetValue function as all of the clamping uses 1 single logic of max=(A+B)*C. My problem is that I kind of want to replicate the values and Map doesn’t have replication afaik.
The original approach/workaround I had was using an array where the index of the value is the same as the Enum index for the given stat and it does work buuuuut… it’s an array and setting up default values or anything by hand in blueprint etc. is a pain.
Tbh.it feels more and more like I should set up the enum through c++ so I can avoid the atrocious clicking when adding 1 enum entry in the middle of 50 and find a workaround to the Map/Dictionary not replicating problem instead :).