Tasharen Entertainment Forum
Support => TNet 3 Support => Topic started by: zeeawk on July 02, 2016, 10:51:01 PM
-
What are the advantages of upgrading to TNET 3?
Does TNET 2 still function correctly?
I never actually got around to using TNET 2, I went today to use it and unity is telling me it's deprecated.
If everything still works correctly and there are no major reasons to upgrade to 3, perhaps I can just keep
using it and upgrade later if I need to?
-
TNET 3 has multiple channel support.
...and other things shiny too!
-
From big features like simultaneous multiple channel support to small but very useful features like the ability to determine which player sent each RFC packet, TNet 3 is all around better. While you could still use TNet 2, TNet 3 has more features, is more robust and stable. Check the sticky post here with the patch notes for a full list of what changed in TNet 3.0.0 onwards.
-
Thanks to both of you.
I played around with TNET 2 last night and I think I will just upgrade to 3. I saw in the tutorial video that 3 comes with a bunch of documentation which 2 doesn't. That to me by itself is worth it.
-
From big features like simultaneous multiple channel support to small but very useful features like the ability to determine which player sent each RFC packet, TNet 3 is all around better. While you could still use TNet 2, TNet 3 has more features, is more robust and stable. Check the sticky post here with the patch notes for a full list of what changed in TNet 3.0.0 onwards.
First of all, sorry for (Kind of) necroposting.
I am thinking on picking up and improving over an application that I did with TNet 2; Will my application be still (mostly) compatible after upgrading, or will I need a total rewrite?
Thank you.
-
It will be mostly compatible. You will need to subscribe to OnConnect, OnDisconnect etc other type of events that used to be broadcast before. Also, server-wide broadcasts won't work anymore in TNet 3, if you've used them. You'll need to join a common secondary channel and communicate through it instead for when you need cross-channel communication (example: chat). RCCs no longer need to be registered -- TNet 3 will find them automatically. Pretty sure TNet will tell you about the rest, or you can just gleam it from the tutorials.