I seem to have encountered a bug in 4.17 when sometimes the default value of a variable in a parent blueprint is not passed to its children. Instead, the child gets a 0 value on that variable. I’ve seen it happen twice in my current project and the workaround for now is to simply override the value at the child blueprint.
I have tried to reproduce the bug on a clean project and I havent been able to. If it helps, I think this happens when I make a change to a parent BP, compile it, but then the children dont need to compile (sometimes you see that you have to save all children and sometimes you dont).
I would close this thread for now, as this bug seems quite rare. If I am able to reproduce in the future, I’ll try to contact you directly, if you dont mind