Is there anyway to bypass persistent classes and just have properties use attributes to decide whether they are saved or not? I have over 300 classes and maintaining surrogates is pretty painful (not to mention I have errors with types of DateTime and Decimal, see errors below).
Also it'd be great if end users could use the scripting extension to write classes that would display in the inspector, which I assume would work if you used attributes rather than a surrogate system, correct?
BattlehubCode
commented
3 months ago
Is there anyway to bypass persistent classes and just have properties use attributes to decide whether they are saved or not? I have over 300 classes and maintaining surrogates is pretty painful (not to mention I have errors with types of DateTime and Decimal, see errors below).
Also it'd be great if end users could use the scripting extension to write classes that would display in the inspector, which I assume would work if you used attributes rather than a surrogate system, correct?