Tags: kaffo/Mirror
Tags
fix: auto fill serialize/deserialize for classes (MirrorNetworking#2120) Note this method is being called in 3 places: one in MessageClassProcessor and 2 in NetworkBehaviorProcessor. The NetworkBehaviorProcess is really a don't care, this condition cannot happen since it would not be invoked unless the class extends from NetworkBehavior. In this case, it will always resolve. but even if it does not resolve, they handle the null case gracefully by not calling the base method. MessageClassProcessor also calls this method, and if it is null it does not call the base method. That is precisely the behavior we want to resolve MirrorNetworking#2117 so all 3 places are perfectly fine receiving null. The only way to trigger the error was MirrorNetworking#2117 I renamed the method to make it clearer that this may not find the method in the parent class.
fix: dont allow set of networkSceneName directly (MirrorNetworking#2100)
fix: fixing cloud scripts not pinging api (MirrorNetworking#2097) * adding logs to api updater * fixing cloud api
fix: Misc code smells (MirrorNetworking#2094) * fix: code smell - condensed if statement * fix: code smell - dont throw generic Exception
fix: register prefab error with same guid (MirrorNetworking#2092) * tests for when newassetId is same as current * stopping error if ids are the same * invert if and adding comment
fix: renaming call/invoke prefix for SyncEvent (MirrorNetworking#2089) * renaming sync event same reason as MirrorNetworking#2088 * removing un-used const
feat: Rigidbody example (MirrorNetworking#2076) * adding example for NetworkRigidbody * adding hud * adding empty player so that scene objects spawn * turning off debug logs
feat: Sync Events no longer need Event prefix (MirrorNetworking#2087) Instead of doing ```cs [SyncEvent] public event MySyncEventDelegate EventOnly; ``` You can now do ```cs [SyncEvent] public event MySyncEventDelegate Only; ``` We actually tried to remove them a while ago. The way the weaver worked back then caused an infinite recursion. Since the Command rewrite that allows virtuals, this is no longer a problem. So we can drop this requirement. Co-authored-by: Paul Pacheco <[email protected]>
feat: ClientRpc no longer need Rpc prefix (MirrorNetworking#2086) Instead of doing ```cs [ClientRpc] public void RpcPepe() {} ``` You can now do ```cs [ClientRpc] public void Pepe() {} ``` We actually tried to remove them a while ago. The way the weaver worked back then caused an infinite recursion. Since the Command rewrite that allows virtuals, this is no longer a problem. So we can drop this requirement. Co-authored-by: Paul Pacheco <[email protected]>
PreviousNext