Of course relays require a hosting solution, so there is some cost, but it is much less than dedicated servers. Whenever possible clients will connect directly to the host using a normal direct connection when permitted, or punching through when necessary and possible. With Noble Connect, players are able to act as hosts, always. May I present my own solution: Noble Connect The relays don't actually host the game though, they just pass packets between clients, one of the clients still acts as the "Host" for all intents and purposes. Instead the initial connection is made to the relay, so no client needs to be able to receive a connection. With a relay, no client needs to be able to accept incoming connections (which is what routers tend to block). So the most modern solution is to use relays that are sort of a middle-ground between dedicated server and peer-hosted. Also some genius invented NAT Punchthrough which can get through some routers without the need for port forwarding, but it doesn't work on all routers. Unfortunately not all routers support automatic port-forwarding (UPnP or NATPnP) and even on routers that do support it, there is no guarantee that it is actually enabled.
#Uniplayer unity hyperspin code
Luckily in more modern times you can often forward ports automatically using a bit of code that communicates with the router. The old school solution to this was to have your players manually set up port-forwarding on their routers (booo). The one issue you're going to run in to though is that most player hosts will not actually be connectable because they are behind a router. It's all pretty standard stuff really, it tends to be easier to set up a networked game to use P2P than dedicated server, since you don't need to worry about a separate server component and paying for physical servers. Unless you go out of your way, if you use UNet or Mirror (can't speak for newer Unity Networking), you will be using P2P by default. P2P is more or less the default for unity.
0 kommentar(er)
