|Home||How to setup and run multiplayer sessions.|
Racer is actually always running in multiplayer mode; it connects to itself, so the program is both client and server if run as single player.
Racer has a built-in lobby. When entering the lobby you connect to a Lobbyserver (currently I have one setup on the internet, available as lobby.racer.nl). The lobby is the place if you want to race over the internet.
The lobbyserver is installed in the same directory as Racer itself, so you can a Lobbyserver yourself, either locally for a LAN environment, or on the internet to provide an alternative to Racer's default lobby. Currently the lobby at racer.nl isn't too crowded so there doesn't seem a need for this yet.
Racer v0.8.7 first supported an automated server. This allows a bot to connect to the lobbyserver and start hosting races. This is useful so you can have multiple unattended computers out there on the internet, all running as a dedicated Racer multiplayer server to which players can connect.
More info on setting up such a server at your own home can be found here.
Multiplayer over LAN
Important to make sure is:
Last but not least, realise that multiplayer is a work in progress, lots of things will be wrong with it (version 0.5.2 beta 7.5 currently). Things like collisions are not working well (if at all).
You won't need to touch most of the settings in racer.ini directly. For Mac users, no dialog pops up when trying to join a race though; you need to modify multiplayer.server_remote to the IP address (or name) of the server you wish to connect to. After that, run the game and click 'Join MP game'.
One feature of multiplayer is the spectator view; you can turn that on by setting multiplayer.audience to 1. This way, no car will be loaded for this client, and you can only watch other cars drive.
RUNNING FROM BEHIND A ROUTER
It depends on what you want to do, join or host a game. If you
want to connect to another client (join), you might not need to do anything.
Although this is UDP, so I'm not sure how routers deal with UDP connections
going out. You may want to check if you firewall allows outgoing packets on
Racer's multiplayer port (mostly 25000, see racer.ini:multiplayer.port).
For a server, you would only be able to do 1 server probably. Then have your clients (the remote car drivers) connect to the IP address of your router (the IP address that is actually reachable on the internet, for example 184.108.40.206). You need to forward UDP port 25000 then to your internal address (i.e. 192.168.0.1), which is a rule to be placed on the router, through a NAT table for example, or using ip forwarding on Linux.
That might do it. The downside is that you can only run 1 server behind your router, since incoming packets on UDP:25000 is something the router doesn't know who to send to, unless you explicitly tell it to.
If you have remarks about this text (I have never tried Racer
behind a router), let me know. Setting up multiplayer games may be tough in
THE PROCEDURE (LAN multiplayer)
Assuming everything is in place:
(last updated November 13, 2012 )