You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore: migrate 2830 allow null references in NetworkBehaviourReference and NetworkObjectReference (#2874)
* initial commit
* update
adding changelog entry
* update and style
Fixing some style issues along with property type issues.
* test
Adding some generalized testing to validate both NetworkBehaviourReference and NetworkObjectReference can be created using a null and serialized when null.
* update
Updating the changed description.
---------
Co-authored-by: Simone Guggiari <[email protected]>
Copy file name to clipboardExpand all lines: com.unity.netcode.gameobjects/CHANGELOG.md
+1
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,7 @@ Additional documentation and release notes are available at [Multiplayer Documen
32
32
33
33
### Changed
34
34
35
+
- Changed `NetworkObjectReference` and `NetworkBehaviourReference` to allow null references when constructing and serializing. (#2874)
35
36
- Changed `NetworkAnimator` no longer requires the `Animator` component to exist on the same `GameObject`. (#2872)
36
37
- Changed `NetworkTransform` to now use `NetworkTransformMessage` as opposed to named messages for NetworkTransformState updates. (#2810)
37
38
- Changed `CustomMessageManager` so it no longer attempts to register or "unregister" a null or empty string and will log an error if this condition occurs. (#2807)
varnetworkObject=gameObject.GetComponent<NetworkObject>()??thrownewArgumentException($"Cannot create {nameof(NetworkObjectReference)} from {nameof(GameObject)} without a {nameof(NetworkObject)} component.");
0 commit comments