Docs / Race Control
Glossary
The words Race Control uses, in one place.
Agent
The PaceLaps program on a session admin’s PC. It reads the iRacing session and types race control’s commands into the iRacing chat. The agent
Activate and sleep
Activate connects the agent and runs its self-test; afterwards it takes part in the session. Sleep disconnects it: it sends and receives nothing.
Executor
The one agent that sends race control’s commands to iRacing right now. When it drops out, another active agent takes over. Race control’s header shows which agent it is.
View only
An agent without session admin rights. It never sends commands, but stewards can play incident replays on it.
Self-test
What the agent checks when you activate it: iRacing is running, the session belongs to your league, Race Control answers, the cars are there, and a harmless !help reaches the chat.
Call
Anything race control tells the drivers: a message, a flag, a penalty. Every screen shows it at the same moment, and race control shows on how many screens it appeared.
Banner
How a call appears on a driver’s screen and on the stream overlay. A banner that stays remains until it’s withdrawn.
Procedure
Your league’s routine as steps, for example a safety car: messages, iRacing commands, waits for a steward’s go. A steward starts it with a button. Procedures
Phase and trigger
A procedure is made of phases, each a list of steps. A trigger starts a phase: a steward’s button, something in iRacing (for example a flag), a timer, or a failure (no agent or no steward left).
Failsafe
A procedure that starts on its own when race control loses its last agent (and, if you choose, its last steward), after a countdown stewards can cancel. Set in Settings.
Local failsafe
A procedure the agent runs on its own when it can’t reach Race Control. It uses only steps that work offline. Operators turn it on in the agent’s settings.
Sorting view
Shows each car where it belongs behind the safety car, by class, so the field can sort itself.
Case
Incident points of cars at the same place and time, grouped for review. Stewards decide each car’s outcome: no further action, a racing incident or a penalty.
Penalty catalog
Your league’s list of penalties, each with what it does in iRacing. Penalty catalog
Class id
iRacing’s number for a car class, for example 4098. The Roster page’s Classes card shows each class’s id, and the Safety cars setting asks for it.
Overlay
A web page for OBS or any tool that shows one: the banner, your place behind the safety car, the audit log or the whole driver page. Drivers
Audit log
The record of every call and decision, by car number and pseudonymous steward id. It can’t be changed afterwards.
League admin and steward
League admins manage members, settings, procedures and the penalty catalog. Stewards run race control.