4.11 Child blueprint variables resetting to parent defaults

It seems you stumbled upon a known yet unresolved bug: