Repeat a Race

Use this procedure to add another Event to a recurring race or season. You need permission to manage the Competition and, for venue acceptance, permission to manage that venue's settings.

Use this for an online championship that needs driver details before admission. You need permission to manage the Competition.

In the Competition, open Registration and select Edit questions.
Choose whether to collect birth year and phone number, and whether each is required.
Add up to ten short-text, single-choice or checkbox questions. Mark required checkboxes only when the driver must agree before entering.
If needed, turn on Require linked Discord account, then save. Self-service entrants must connect their own Discord account under My account → Connections.
Verify the saved questions on the signup form. Team signup collects answers for every driver, including drivers entered by the Team manager.

Required answers and linked Discord are supported for explicit online signup. They cannot be enabled while venue purchase or automatic entry routes are configured; make questions optional or remove those routes first. Optional questions appear in organizer and online forms; purchases do not collect them.

Organizers can add historical drivers without a connected Discord account. Such entries record that Discord was not verified; typing an ID cannot establish a link. Required questions still need answers. Open the registered car's Edit car and drivers action to review saved answers. Only organizers with management permission can see them. Changing the form does not rewrite past answers. Replacing a driver keeps the previous answers in that car's history; assigning a driver to an empty slot collects new answers. Existing admitted drivers and paid bookings are not asked to sign up again.

Set the estimated event duration

In the Competition's Events, open the Event and select Edit duration.
Enter the full programme length in minutes, including briefing, racing and prizes. For example, enter 180 for about three hours.
Select Save duration and check the estimate on the public Event card and registration page. Leave the field blank to hide it.

This estimate does not change venue arrival instructions, session timing or simulator reservations. A duplicated Event keeps the estimate.

Set the public programme

In the Event's Block, select Edit to set its scheduled start.
In Sessions, set the running length or lap count, countdown, race rules and any extra lap for a timed race.
Review the public programme: it shows the saved running format separately from the advertised calendar window, including waiting time and jump-start rules.
Keep About and Rules for supplementary explanations and links. Writing a duration, start time or grid rule there does not configure the session.

For AC's built-in second race, enable the Race 2 tab beside Race. Both races share the same duration or laps, extra lap, joining policy, countdown, native pit window and finish allowance. Race 2 displays these values; edit them in Race 1. Its name, required-stop rules, scoring and results stay separate.

Choose Race 1 finishing order, Reverse top positions or Reverse all finishers for Race 2's grid. A partial reversal leaves the other positions in order; disqualified drivers start at the back. Full reversal also keeps retired drivers at the back. Independently configured races with different lengths need separate Blocks rather than this built-in repeat.

Start the Block once to run both races. AC applies the selected grid for Race 2; Pista keeps each race's laps, results and scoring separate, including after a session restart. Both races must use the same required-stop rules for a combined launch. Imported or manually entered results still belong to the selected race. For a separate race-only attempt, review and set that race's grid explicitly: automatic reversal does not run in that attempt.

Import an Assetto Corsa result file

Use the original server JSON for one Practice, Qualifying or Race session. Add the drivers to the Entry List first, and select the matching track layout. Vanilla AC and Penguin Server Manager exports are supported. Penguin imports include source time adjustments, lap penalties and disqualifications. A shared car keeps one Entry result, with each lap attributed to the driver who drove it.

Open the Event's Results and select the session that produced the file.
Open Sources, select Add results, then choose the source format and JSON file.
Match each car to its registered Entry and each source driver to a driver on that Entry's roster. Review the source adjustments and matches, then select Import results and laps.
In the Session’s Sources tab, verify the imported run and which run counts. Download the original file there when you need to inspect its source evidence.

The import retains all laps and the original classification. Source adjustments appear on the results sheet separately from later Pista steward decisions; lap times remain unchanged. Clean-lap status uses the native cut count. Rulings held only in another timing system or a steward's document must still be entered separately. A file with only elapsed times does not establish exact lap dates.

If a source driver's identity is missing during a driver swap, resolve it in the source before importing. Combined or transformed exports with ambiguous penalties need review; use the original single-session export instead.

To correct a driver match, exclude the imported run in the Session’s Sources tab, then import the original file again with the corrected matches. The previous evidence remains in history. Reopen closed qualifying before importing new or corrected results. Files support up to 1,000 laps, 64 cars and 512 KiB.

Hide staff from results

Use this when a staff member drove while signed in, for example to test the setup, and their laps must not rank.

Open the Event's Results and select a Session they drove in.
In Classification, open their actions menu and select Mark not competing.
Confirm. They leave every result and standings table, and the drivers behind them move up.

Their runs and laps stay in the Session's Laps and Sources, and laps they drive later stay hidden too. To bring them back, select Competing again under Not competing on any Session page of the Competition. Closed qualifying keeps its classification until you reopen it.

Duplicate the Event

In the organization dashboard, open the Competition and go to Events.
Open the source Event's actions menu and select Duplicate event.
Review the suggested date: the same local time one week later.
Choose the new start date and time, then select Duplicate.
In the new Event, verify the program and signup window.

Blocks, Sessions and Event signup dates move together, preserving durations and gaps. Scoring and grid configuration are retained. No signup, booking, participation or result records are copied. Competition-scoped signups still cover the new Event; Event-scoped signups must be made again.

Approve the Venue Setup

In the venue dashboard, open the Competition and go to Races.
Open the new race marked Awaiting venue approval.
Select Review prices or Edit prices, review the slot prices and select Save and confirm prices. Defaults seed new races; confirmed prices stay independent.
Review simulator quantities and the sale opening date, then select Accept race sale.
Verify the reserved places and signup opening in the saved race setup.

Scheduled Events start their servers from the authored Block schedule. For a staff-run tournament, turn off Start blocks automatically at planned times in the organization's Event Program. Staff start warm-up and select the next group or Block explicitly.

To keep driver connection out of the public programme, open the Block's Sessions tab and switch Practice off. The server still opens in Driver connection Practice: fifteen minutes for scheduled Events, or a 24-hour joining waiting room for staff-run tournaments. Verify driver sign-in and connections, then select Start qualifying or Start race on the run screen. Reserve equipment from arrival time to cover the changeovers. Turning Practice on includes it in the programme with its own editable duration. An authored Practice, including a Hotlap that runs as Practice, uses this same native slot; no extra connection Practice is added. Hotlap also keeps its authored Practice duration on the server.

Before acceptance, the proposal reserves no simulators and accepts no bookings. Acceptance checks availability for the new race window and reserves fresh capacity. A blank signup opening keeps public signup closed; a future date schedules it; a past date opens it immediately, subject to the Event's signup window.

If capacity is unavailable, the proposal remains pending. Adjust the requested quantities or resolve the conflicting booking, then accept again. Do not cancel a customer's booking merely to make this test pass.

Book Before Driver Details Are Known

Individual and Team venue bookings can reserve simulator slots without driver names or emails. Checkout still needs the buyer's contact email. Unnamed slots count against the race's capacity; they appear in the venue booking before they have an accepted sporting signup. The buyer can add drivers later in the booking, or staff can assign them from the reservation's Drivers tab. Verify that the assigned driver appears in the Event's Entry List before racing.

The buyer's contact details do not assign a seat's driver. An empty seat can be filled when a driver signs in on the tablet. If the booking is for someone else, check that its seat names the arriving driver. A seat already assigned to another person cannot be taken by entering different details on the tablet.

If the tablet says This driver is not on the reservation:

In the venue dashboard, open the reservation's Drivers tab.
Select the incorrect driver's name or Add a driver, assign the arriving driver, then select Save changes.
Retry sign-in on the tablet and verify the displayed driver before joining the race.

For a Team booking, complete the roster before racing:

In the venue race desk, find the booking and select Complete Team signup.
Choose or create the Team and enter the complete driver roster.
For each car, select its booked simulator slot. Slots in other classes cannot be selected; each slot can belong to only one car.
Submit and verify the accepted Team appears in the Event's Entry List.

The booked places are reused, including when the race is full. Pending card payments must complete first. When the organizer requires signup before racing, signing in at a simulator cannot bypass the complete Team roster. Online Team signup still requires its complete roster upfront.

Run a private endurance session

For a booking-backed endurance event, each booked simulator is one team car.

Choose the final track and layout in the competition's Block editor before preparing the server. Track changes lock once the server is prepared; cancelling a preparation unlocks them only if the server never started.

On the booking's Program tab, choose Allowed cars when creating the event: one model for everyone or several models to assign to participants. You can change the allowed selection later in the competition. Open Participants beside the race to see each team's name and drivers and use Edit car to assign its car from that selection. If the server is already running, restart it and reconnect the drivers to apply car changes.

On each simulator tablet, use Add driver to open the name or email form. Select the Qualifying driver and Race starter rows to pick each driver. The same person can do both.
Select Ready to open the practice driving and driver-change screen automatically. Edit team returns to setup during practice; select Ready again when finished. Ready is optional for staff: they can select Next session without waiting for every team.
To practise a handover, stop in the car's own pit box, swap seats and select the teammate taking over on the tablet. Practice handovers do not count towards race stops. The roster and qualifying driver lock when qualifying begins, or when the race begins if there is no qualifying. The race starter can still be changed from the existing team until the race starts. Returning to practice does not reopen the team or an already used driver choice.
Have the nominated driver take the seat before qualifying or the race starts. Drivers can also swap during qualifying: select the person now driving on the same tablet screen. Change race starter opens the remaining nomination; Back to driving returns. Current-driver selection stays available during the race countdown, even without Ready. Any configured opening lock begins at the green flag. The team car keeps its qualifying result and grid position.
During the race, select the driver on the tablet after each handover. If someone forgets, they can correct the selection after leaving the pits. The change applies from that moment; earlier laps stay with their recorded driver. A configured opening lock still applies.

Check that the tablet shows the person driving after each handover. Driver selection does not complete a mandatory stop: the car must still earn the configured time while stationary in its own pit box. Moving or leaving the box pauses that time; leaving the pit lane resets it. If pit timing is unavailable, tell staff; driver selection remains available.

Show endurance teams on TV

This works for both private events and public competitions hosted at your venue.

Open Displays → New playlist → Add slide → Race event.
Select the endurance event and create the playlist.
Select Play on displays, choose the TV and save.

Select the event once. The TV follows the server through practice, qualifying and the race. Each row keeps the team name, with the current driver beneath it, plus position, laps and gap. The race also shows completed stops against required stops, such as 0/1. Practice stops do not count. When the server finishes, the event's classification replaces live timing once available.

Run a Race Tournament

Choose Race tournament when qualifying feeds several points races in the same Event. You need permission to manage the Competition.

In competition creation, choose Race tournament and set the rounds, races per round and session durations.
In Events, add an Event and select one track layout, its host venue, participant allocation, heats per stage and number of race stages. The venue must already have a registration route. For ten participants, choose two heats and three stages: two sprint stages and a final stage. Verify one combined Qualifier, Sprint 1–4 and two separate finals. Each Event has one host venue. Heat and stage counts are fixed on creation.
Configure the cars, venue equipment and server. For one-car events, drivers do not need to select a car.
Follow Run Noć Formule for ticket check-in, qualifying groups, sprint grids, finals, driver changeovers and event closure.

Qualifying completion freezes the reviewed result without stopping the server. Use Reopen qualifying before correcting it; existing race grids need a separate review and application. Equal sprint points use the original qualifying lap when configured. A missing valid lap sorts behind a valid lap; exact ties remain tied and require an explicit decision at the final cutoff.

Each final selects participants for its whole Block. Its own qualifying sets the race starting order. The native server advances from timed qualifying to race automatically; staff control joining and the next Block. Final races must stay outside the sprint points rule when the Main final decides the winner.

Sell Tournament Admissions

Rotating tournaments sell participant places. For example, the venue can commit 15 places and reserve five simulators for the entire event. Customers select participants and classes; they do not select a simulator or buy motion upgrades. The venue is responsible for a schedule that serves its participant commitment.

The organizer uses per-event signup scope, offers participation to the venue and sets class allocations. New tournaments use per-event signup by default.
In the venue Competition setup, accept participation.
Open the race setup and save the participant commitment and shared equipment description.
Reserve equipment for the full event window, including any setup buffer. The reservation must cover the accepted participants divided by heats per stage, rounded up: 10 or 9 participants across two heats need five simulators; eight need four. Fifteen participants across three heats also need five.
Confirm the normal admission price. Optionally set an early-bird price and start and end time. Times use the venue timezone. For an offer valid only on one day, use midnight at its start and midnight on the following day. Public pay-at-venue stays off unless you allow it under Payment terms; there you can also set a late fee and minutes before the scheduled event start.
Select Confirm booking setup. Staff can now sell admissions.
Set the public sales opening time separately. Leaving it empty keeps public sales closed while allowing staff sales.

Equipment availability is checked when reserving or amending the pool. Each purchase consumes an admission place. Cancelling an admission does not release event equipment. To release the pool, select Suspend bookings and release equipment; existing admissions and payments remain for staff to resolve.

In New sale, select Add event entry, enter participants and add the event to the cart. Edit reopens the event with its current draft; saving replaces that item. Add products or an ordinary reservation, attach the buyer, then continue to the existing payment collection page. The late fee is a separate line added automatically to qualifying public and staff sales. On the payment collection page, staff can remove it before payment or tax is frozen; the sale retains an audit of the waiver.

Public upfront checkout accepts the venue wallet and a gift-card code. Customers pay any remainder by card; fully covered purchases confirm directly. Staff do not enter a customer's card in the event editor. Ordinary reservation editors remain unchanged.

The public page shows the current admission price and countdown to the next price change. Availability refreshes when checkout holds expire or an opening or pricing deadline passes, and when you return to the page. Prices are checked again when committing the purchase. An existing sale retains its agreed price. Organizer registration fees remain separate from the venue's admission price.

Direct signup cannot bypass the event admission. Authorized staff can add a complimentary participant from the entry form with a recorded reason. This requires both organizer management and the venue's sales permission. This still uses one participant place.

Driver names and emails are optional at purchase. Each Individual admission holds one participant place; it does not create an anonymous driver. The buyer contact is required. Buyers can use Manage drivers after checkout and sign in with the buyer's account; venue staff can use the race's admission register. Supplied card checkout driver details are assigned after payment in a separate transaction. If assignment needs attention, the register retains the details for correction.

The admission register shows buyer, driver and payment collection information. Open the sale's event link to return to this register and assign drivers. Assigning a driver to an existing place works when the event is full or sales are closed and preserves the agreed venue price and organizer fee. An assigned driver can only be replaced through the organizer's existing sporting controls.

Card checkout holds capacity until its displayed expiry. Payment confirmation confirms the admission; an abandoned checkout releases its place. Staff and pay-at-venue sales use the existing payment collection rules. If a delayed payment arrives after its place was resold, the buyer sees Payment received — place needs review. Staff can use Review admission in the register to recheck capacity. A later opening does not trigger an automatic retry. Refunds require separate handling.

Before the event starts, cancelling an admission releases its place. Refunds are separate. After the scheduled or actual start, use DNS or withdrawal in sporting results; these outcomes retain the purchased place and racing history.

To cancel all your places in an event before it starts:

In My events, open the event.
Open the event's Actions menu and select Cancel all places.
Confirm the cancellation. The tickets move under Cancelled tickets.

This includes places bought in separate purchases. An unfinished checkout must be finished or cancelled through its payment flow first. Refunds remain separate.

On the public competition page, open Standings, choose the leaderboard and select the car class when tabs appear.
Select Share. The preview starts with the selected class; you can choose another class before sharing.
Choose Top 3, Top 5 or Top 10 and check the image preview.
Select Download PNG, or Share image… when your device supports image sharing.

The image contains the ranked results at the time you open the preview. Unranked entries are excluded; fewer results produce a shorter image. Reopen the preview to include newer results. You can add the downloaded image over your own photo or video in Instagram. Available sharing apps depend on your device.

DEV Acceptance Test

Use DEV throughout. Configure fifteen participant places and five reserved simulators, with the intended prices and included experience.

Open the public signup page and verify the date, shared equipment terms and price.
Buy an unnamed admission, verify its buyer and payment in the admission register, then assign the driver and verify Signups and Entry List.
In New sale, add an event and a product. Edit the event and verify it replaces the same item; cancel an edit and verify the original item remains.
Verify the sixth participant can register and the sixteenth cannot.
Verify ordinary bookings cannot consume the event's reserved equipment.
Test a price boundary and an abandoned card payment. Verify the abandoned admission becomes available again while event equipment remains reserved.
On a DEV-connected simulator, sign in an entered driver and join the race.
Start and finish the program, then inspect the Event results.
Continue to the next heat and verify its roster and results.

Native joining and race execution require a DEV-connected simulator.

Sell and reserve practice

Practice uses the event's configured simulator experience. Configure event equipment, start time and admission pricing before adding practice.

In event setup, open Practice before the event. Give each choice a name, duration and price. The signup payment setting applies to the whole initial checkout. The separate practice payment setting applies to later purchases.
At signup, select practice and quantity for each participant. Additional sessions can be bought later from the participant's Add practice action.
Open the event in My events, or its venue admission register for a walk-in. Assign the participating drivers, then select Reserve practice.
Select drivers, practice, date, equipment and an available time. Each driver uses one paid session. Confirmation creates a reservation per driver with no additional charge. The available balance decreases accordingly.
In My events, open the reservation beside its driver. In the venue register, open Practice reservations. For a no-show, cancel that driver's reservation as a no-show. If you want to return the practice, use the reservation's package-return action. Other drivers' bookings remain unchanged. Return is explicit and cannot credit the same use twice.

Purchasing practice does not reserve capacity. Reservations must finish before both the event starts and the purchased practice expires. Removing an offer preserves purchases. Cancellation, returning a practice use and refunding money are separate actions. A reservation or elapsed time alone is not proof of attendance.

To remove an unpaid extra purchase, open the driver's Purchase history in My events and select Remove beside it. Venue staff can use the same action in the admission register. The extra purchase disappears; the event signup stays active. An active online checkout is closed first. Paid purchases require a refund; practice included in the original signup cannot be removed with this action.