Because, classically, a state machine operates over a single state. The state of the machine. In this case there is state, whether or not the value if overridden, for every property. That’s N states, not one. So you’d actually have too create N state machines, one for each property. Which I suppose you could do, but then there’s the fact that the state itself is a boolean so there are only two states. Combined with the fact that there’s nothing to do for the boolean except choose which value, makes it ultimately a trivial state machine that is just encumbered by whatever the machine framework is more than it’s helped. His original idea is purely a procedural problem:
float GetValue( )
if (bIsOverridden)
return MyValue;
else
return Parent->MyValue;
Now that sounds like a state machine. But that is not what the OP was asking about. They’d have a pink one and a blue one but they are separate objects.