Question by jayekub · Aug 26, 2018 at 01:01 AM · networking matchmaking

Direction Connections with MatchMaker service?

I'm wondering if it's possible to use the MatchMaker service only to for clients to find the server address, but to then have clients connect directly to the server?

I've managed to get a direct connection working by calling NetworkManager.StartServer() first, then NetworkMatch.CreateMatch() on the server with a privateClientAddress. the problem with this is that the match listing seems to expire quickly from the MatchMaker service.

It seems the intended use is to call CreateMatch first, then call StartServer(matchInfo) in the callback with the matchInfo corresponding to the listed match. this keeps the listing from expiring, but it also seems to cause the server to only listen using a relay server.

Sure enough, even the documentation for NetworkServer.Listen() says: "Note that if a match has been created, this will listen using the Relay server instead of a local socket."

So...am i trying to use the service incorrectly, or am i just missing something?

I have NetworkDiscovery working already, but on certain networks the broadcast messages don't seem to be reliably sent to all clients, so i'm hoping to use the MatchMaker as a backup for when this happens. But i always intend for my server and client to be on the same local network, so there's no need for a relay server.

Thanks for any info/ideas!

Add comment