UnassignedReferenceException with null-conditional

[laurentopia]

Something I've never seen before:
rigidBody?.AddForceAtPosition(direction, hitPoint, ForceMode.Impulse);
causes that:
UnassignedReferenceException: The variable rigidBody of MCUnit has not been assigned.

and that's how rigidbody is set, automatically:

so either I never paid attention to that error before or GetComponent does something strange, other than nulling a field

[TylerTemp]

Hi,

this possible happens when things are correct in edit mode, and then when go to play mode, you manually active the object, and because in playing mode the logic is a bit different, this decorator might fail to get the component, and decide to null the field. (But not sure it's because of this)

I'll disable the GetComponent* ability in play mode in next release

[laurentopia]

I understand, it's probably better to do that so that it matches the behavior of a build.

[laurentopia]

It's a unity thing
unity object are some times kinda of but not really null :/

https://stackoverflow.com/questions/62678228/why-does-c-sharp-null-conditional-operator-not-work-with-unity-serializable-vari