fix: UB in remote input info

[EmosewaMC]

Yes i should have made this first
no this wouldnt have happened with rust

I have NO clue why the new AddComponent caused this. I dug into this for about 10 hours and it was specifically having the PossessableComponent go through the new AddComponent and nothing else. Using the inline variant resulted in the same effect. The RemoteInputInfo in the previous case was always initialized to 0 0 0 1, whereas with the new AddComponent for Possessable, it was UB.

Tested that the client no longer logs HAVOK CRASH ON FRICTION multiple times per frame

[Wincent01]

GCC/CLang doesn't initialize members without being told explicitly to do so, but MSVC does. So I don't think this issue would've happened had you compiled on Windows. Had a ton of these issues when we moved away from Windows way back when.

[EmosewaMC]

GCC/CLang doesn't initialize members without being told explicitly to do so, but MSVC does. So I don't think this issue would've happened had you compiled on Windows. Had a ton of these issues when we moved away from Windows way back when.

Yep windows i had the same experience. Worked just fine, but more details on this behavior are in the dev discord. Very """Fun""" bug.