The problem here is that the blueprint should have taken on the new C++ value and it didn’t. What I tried to describe is that it seems that the blueprint had overwritten the value internally even if they are the same value before the change, so on the hotreload the blueprint believes it shouldn’t have to update itself, because we explicitly assigned a value in BP already (which is not the case) - Hope that makes any sense - it’s just a hunch on what I thought might be going on.