Multiplayer servers (automated)
|Home||Setting up an automated race host bot..|
Multiplayer is no fun without racers. However, setting up a race in the lobby can be cumbersome since you need to wait to get people in and do everything manually. Racer can run an automated race hoster. If you've ever seen VROC for Grand Prix Legends, you'll quickly grasp the concept.
Automated race hosting is supported as an alpha feature from v0.8.7 onwards.
Setting things up
Racer has a separate file called 'server.ini'. This file contains the configuration for the automated host. Check below for an example server.ini file.
The main on/off toggle is global.enable. If set to 1, when running Racer you'll get into the automated race mode. Your regular lobby nickname won't be used, but the bot will connect to the lobbyserver under the name specified in global.name. Make sure to fill this in with an identifiable name.
Example server.ini file
Here's a short example server.ini. Notice that global.enable is set to 1, enabling server mode.
The races part will be cycled through, so you can have a number of different races hosted by your bot.
; Racer server
; If enabled, Racer will be a server and host races through the lobby
; Nickname used (instead of regular lobby nickname)
; Min # of players (otherwise the race is aborted)
; Max # of connecting players (NYI)
; Time (in seconds) to wait before each race to start
; A list of races to run
; Accepted cars
; Fill up grid with AI if there aren't enough players
; Number of laps
; Allow car.ini to be different on the client?
The Settings in detail
For the 'global' section, here is an explanation of what does what:
For each race, you have the following settings:
Games are verified on the connecting computers (clients), to make sure that the player can join them. Unjoinable games are hidden if the 'Hide unjoinable games' is ticked in the Lobby.
Several things can go wrong. Here's a list of expected problems:
(last updated November 13, 2012 )