Some hints:
-------------------------------------------

to give commands to rcs press 't' and enter "#command" ('#help' for example)
to change the language enter '#lang ?'. With this command rcs lists all available translations.

to change the server-config-file (server_x.cfg) ingame without restarting rcs use the command '#loadconfig'. 
You can also specify a cfg-file with '#loadconfig <filename>. With this command you can create events with different qualy-sessions for example (simply by reloading other qualy-rules). The config must not contain all options. A config with qualy-options only is possible. But the file should end with 'end'.
After the command 'loadconfig' you should restart the session to initialisize the data.

An admin can watch other drivers and their messages. The admin must be in 'spectate' to do this.
commands: '#watch <lfsworldname>, '#nowatch'

To kill one server use the command '#QUIT' (admin only). Be aware, there is no option to restart a sever - You have to restart RCS.exe
To kill all servers use the command '#KILLALL' (admin only). This will save the database too


What happens and how it works:
--------------------------------------------

1.)
There are 3 groups of infotext:
a) RCS-Messages are general infomessages from the masterprogram (Records or sessionchanges for example). They appear mostly at the top of the screen, and are often doubled with normal lfs-textchat

b) OrgaMessages are infomessages from the virtual racedirector  (Racestart orders, penaltys for example). They appear in the upper middle of the screen and can adress all drivers or only you (your team)

c) Crewmessages are messages from your crew. Personel infos, hints and comments. They appear in the bottom middle of the screen and are only visible to you.

You can switch the general chatlevel with the command "#chatlevel". This option is saved in database. 

2.)
closed Pitlane: You can enter the pitlane from track only if you have a penalty. If you enter a closed pitlane from track or enter a closed pitlane from spec/garage and move the car you will get a penalty from orga and negative skillpoints.
commands: '#pitopen','#pitclosed' (by admin only)

3.)
closed track: if you enter a closed track from spec/garage you will go back to pit and get negative skillpoints.
If you enter a closed track after a pitstop you will get a penalty from orga and negative skillpoints
commands: '#trackopen', '#trackclosed' (by admin only)

4.)
Skillpoints: you get positive skillpoints for finishing laps, finishing penaltys or driving to pit and jump THEN to garage. Simply for clean and realistic driving. 
You get negative skillpoints for getting penaltys, creating yellow flags, car reset, and some other things. 
The change of your skillpoints can be watched in the bottom left corner. The skillpoints are saved in the database. To join a Rcs-Server you need a minimum skill-level (level 0=default). Skill-Levels are from 0-10.
commands: '#skill', '#setskill <lfsworldname> value' (last by admins only and not to yourself ;) )
Skillpoints are only calculated in multiplayer

5.)
Database: the Db saves all player with their driven combos,records,setting and skillpoints. Players without driven laps are not saved. 
All servers (up to 8 servers) are using this one database. 

6.)
RollingStart:
edit the server_x.cfg to setup the rollingstart or use the command 'setstart','nextstart' and 'setspeed' ingame (admins only). Try '#<command> ?' for some help.

How it works:
After the green light the leader accelerates to the minimum speedlevel (You can see the speeds with '#info rs-speed'). His primary rule is to hold the correct speed.
Later he gets the command to speed up. At this time he defines the speed. He must not accelerate straight away, but he is not allowed to brake. Braking will send the leader to spectate without warning!!!

All other drivers have to hold their positions (single line start). They can drive faster to go nearer to next car, but they must stay in position.

If a car is to slow, loose the position, is to far away from the next car or if the leader is to fast/slow the driver gets a first warning. After a short time the driver goes to spectate, if he doesnt correct the mistake.
Any 2nd mistake will produce a rcs-penalty.
After every warning the driver has the chance/time to correct his mistake, but he must hurry!
A 3rd mistake will send a driver to spectate without a warning.

Noone is allowed to pass a car before crossing the finishline. The individual race starts with crossing the finsihline.
If to many cars are in wrong position, the start will be stopped by rcs.
commands: '#setstart','#nextstart','setspeed' (all for admins only)

7.)
Pitstopwindows:
This windows are forced pitstops in a race. You can stop more often. But outside a window, the stop doesnt count for the race. If you miss a window, you will get a penalty from orga. A window is  missed too, if you enter the pitlane inside a window to finish a penalty. You have to come in a 2nd time here. 
Your crew will give you information to pitwindows. And there is a infobox in the bottom right corner.

8.)
Delayed Penaltys:
all penaltys from rcs are delayed to make them more realistic. The orga is inspecting a fault and after a short time the penalty will occur. Further penaltys dont overwrite existing penaltys, but they are stored. So you will get one penalty after the other.

9.) 
Qualyrules:
You can define special qualyrules in the server_x.cfg. With this rules its possible to create 'onelap-qualy' for example. A player, who finished his qualy cant join the track again. RCS is tracking the rules for all players. The qualy ends automatically, if no more player can drive (limited by rules) a fast lap.  
Use the command '#info qualy' to view active rules

10.)
Eventmonitor:
The monitor will appear if you are in spectate or in pitlane without moving the car. The monitor is turned off by moving the car. 
The monitor shows all "important" things which happens around you. You can compare times, or see if a player has problems for example.
Use the command '#emon' to turn on/off manually '.

11.) 
AI-Driver: 
AI's can join. But there are some restrictions, because the ai dont know rcs and is not ai enough ;).
a) a AI will never get a rcs-penalty!!!! (missed pitwindow,  rolling start-mistakes)
b) a AI cant drive rolling starts. The AI cant and must not hold the inlapspeed, the ai cant follow other drivers
c) a AI cant finish a pitstopwindow. There will be no penalty for ai.

12.)
Replays:
You can watch replays with rcs. But you should notice the following:
From rcs-view a replay is a normal multiplayer-session. This can lead to various effects, because the replay cant react to rcs-output.
If rcs-rollingstarts are active, you should have the right serverconfigs (the serverconfig when the replay was saved). If you have no serverconfig set rcs to gp-starts (#setstart gp). 
The same for pitwindows. If you have no serverconfig, set the pitwindows to none (server_x.cfg)
If you have the right severconfig everything will be fine :)
If you see problems with rcs and your loaded replay, simply restart the replay. Sometimes rcs needs two replaystarts.
You can give commands. But if the command wasnt given in the replay, there will be no effect to the replay. But rcs is working with the commands.

Helpful with replays:
"#emon" turns on/off the eventmonitor
"#watch lfs-worldname" (hold ctrl+shift for lfsworldnames) let you see all the messages the driver got from rcs and the camera goes to the cockpit.
not helpful with replay:
jump to a replayposition (could crash rcs)
giving commands, which are not given in replay







 

