Hmm, ok, probably it’s required for some reson, but this is exactly what I’m calling “inconsistency”:
The changed values would be retained in that Blueprint, but it would not be possible to further adjust them
If the member of the class was overridden in the blueprint – then it still should be possible to change it. But if it’s inherited from the parent c++ class – it should obey this class even when it was changed. That’s how inheritence usually works…
At least, it should be described somehow explicitly, as well as it should be possible to reset the values to the parent’s defaults in any case (without manually re-adding the specifier).