Mirror VS com.unity.netcode.gameobjects

Woah, over 80 versions 😮! This is a project with over 1,740 releases over the past five years. Mirror is one for the game devs in the room. It's a high level networking library for Unity. Used in some of the top video games, Mirror is used by thousands of game developers around the world. The latest update brings Mirror in line with the latest Unity version, includes better motion smoothing time, and lots more. Check out all the changes in the Mirror changelog.

https://mirror-networking.com/ (Unity specific, looks nice but don't use unity myself).

Mirror is another option.

Unity's package is, from what I understand, an imitation of Mirror (which is kind of ironic given the name) but I don't know if they have improved it since I last checked. At that point, you might want to consider Mirror instead.

Multiplayer is something I've wanted to try, just so other people can see the dice rolls that each player makes. I found a cool multiplayer library that I hope to try out later, it is called Mirror ... is that what you use? https://github.com/MirrorNetworking/Mirror

I'd suggest getting an experienced developer on board, one that has worked with networking before. Multiplayer games are hard to buid. Regarding networking frameworks, I know Mirror for Unity has been tested for an MMO use case. Not sure about Unity's first-party Networked Game Objects solution.

Are you using AsmDef assembly files? If so make sure you have Mirror.Transports.asmdef referenced in your main (Source folders) asmdef.

I dunno why they'd even bother implementing that when mirror did it for free

https://mirror-networking.com/ (Unity specific, looks nice but don't use unity myself).

There was this issue: Custom Serialization can't be used because of compile-time error in RPCs. · Issue #665 · Unity-Technologies/com.unity.netcode.gameobjects (github.com) and this one Error in editor ArgumentException: An item with the same key has already been added · Issue #714 · Unity-Technologies/com.unity.netcode.gameobjects (github.com) Though I guess there has been many changes on Network for GameObjects since then.

Ok so while writing this I went and found in the github project for the netcode gameobjects an example of grabbing an item, have a look~ https://github.com/Unity-Technologies/com.unity.netcode.gameobjects/blob/develop/testproject/Assets/Scripts/GrabbableBall.cs

Netcode for GO: https://github.com/Unity-Technologies/com.unity.netcode.gameobjects

Turns out downgrading Netcode for Gameobjects from 1.0.1 to 1.0.0 is the solution for this. Here's the link for the working version of Netcode: Netcode v1.0.0

Steam Networking (I used Unity therefore, this was also very helpful: Facepunch Steamworks / MLAPI)

This is in NetworkTransform line 360 in the Unity Netcode https://github.com/Unity-Technologies/com.unity.netcode.gameobjects/blob/9ffd22b158fbac5ea824cb7e9e237d2d8b782ed0/com.unity.netcode.gameobjects/Components/NetworkTransform.cs

I bet you're using Mirror. I peeked at their code base (and Unity's new netcode project) and decided to write my own networking framework instead. It sucks to be stuck with problems that someone else created.

I think they rebranded it to netcode for gameobjects. Github repo seems to update daily: https://github.com/Unity-Technologies/com.unity.netcode.gameobjects

E.g. We just released Boss Room, our new multiplayer sample game. It is built using our experimental version of MLAPI, the mid-level netcode Unity acquired last year. MLAPI is fully open-source under a MIT license. We're continuing to develop it in the open, taking both RFCs and PRs from the community. More info can be found both on our GitHub page and Multiplayer Docs site. https://github.com/Unity-Technologies/com.unity.multiplayer.mlapi https://docs-multiplayer.unity3d.com/ Best wishes!