UDP doesn't work if the Server is behind a NAT, haven't figured out why, but I would recommend keeping UDP un-checked in all cases (meaning uses TCP protocol). This arrangement assumes the Server has a valid internet IP or if it is behind a NAT device like a router, it should have the listening port (default 1626) forwarded to it.If the server is password protected, you will need to enter it yourself. Clicking on one of those Servers will populate the IP and Port fields.When the client instances click Refresh on the Global Server browser, it will display a list of all Servers currently running that are "Published" (in theory, never tested this beyond 3 Servers, will soon find out).This will cause the Server to ping a Lobby application (running on the Web server) periodically during the game with game session statistics (players, frags, etc). On the Server machine, enter a Server Name, and check Publish.The Clients should connect within a couple of seconds upon clicking Start, if things are working. If all machines are within the same house or office, use the local IP address (LAN) Set the Network Mode of the other machines to Client and enter the IP address of Server machine for each.Run one instance of the game with Network Mode = Server (commonly known as the session Host).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |