Closed rootux closed 4 years ago
Thanks for the report, the library definitely needs to be updated. It hasn't had any love for quite some time. I'm actually in the process of finding a network programmer to help me maintain and upgrade it, so hopefully there will be some changes in the next month or two!
Just a tip: If the assembly references get messed-up/lost after upgrading Unity and you're using Visual Studio, I've found that deleting the Visual Studio-generated files and the .vs folder, then recreating them by double-clicking on one of your scripts from within Unity might fix the issue.
Also, I've seen where, even when using the "#using UnityEngine.Networking;" directive doesn't find classes, explicitly referencing the namespace from within code works, for example, "UnityEngine.Networking.NetworkSystem..."
In this case it's probably due to the deprecation of UNet. I'm going to investigate the new system they have planned but I'm also looking into alternatives like Mirror and Telepathy.
UNet is being deprecated, and its libraries are now marked as [obsolete], but it should still be included and functional with Unity 2019.3.0a4.
I tried to correct those errors, are you interested in a pull request with the fixes ? (I’m using Unity 2020.1.7f1)
Sure! If it works for you then go ahead. I'm not supporting this library at the moment but it's possible some people will still find it helpful.
After upgrade. I get those errors:
"The type or namespace name 'NetworkSystem' does not exist in the namespace 'UnityEngine.Networking' (are you missing an assembly reference? "
" Assets/CaptainsMess/CaptainsMessClient.cs(23,35): error CS0246: The type or namespace name 'NetworkDiscovery' could not be found (are you missing a using directive or an assembly reference?) " I guess cause the networking library was updated