How the SRC platform works

1.1Your account & profile

Sign in with email and password. Your profile is created automatically the first time you sign up.

• Display name — set it in Settings to exactly the name you use in-game. Results are matched to your profile first by platform ID, then by name; a mismatch means your races won't attach to you.
• Platform IDs — add your Steam ID, PSN ID and/or Xbox XUID in Settings. This is the reliable link between a result file and your profile, so add whichever ones you race on.
• Handle — your `@handle` and profile URL (`/drivers/your-handle`), generated from your name.
• Country & bio — optional, shown on your driver page.

1.2Teams

Some series are entered as a team rather than as an individual. Create one under Teams; you become its owner and can add managers, drivers and reserves. A team needs a name and a tag.

1.3Finding & entering races

• Daily Races — one-off races with no championship points. Register with one click on the race page while registration is open.
• Championships — multi-round series. Open the series, then enter a team: pick the team, a car number and (optionally) a car. Staff accept entries; once accepted your car is pushed to the game server's entry list automatically.
• Supporter races — paid one-off races (see 1.10).

1.4The race page

Each event page (`/events/…`) shows, in order:

• Status, and a link to the series if it belongs to one.
• Circuit panel — layout, length, corner count, direction, plus the current real-world weather at the track. In-sim conditions are set separately per race.
• Registration / entry (or the paid-race checkout button).
• Results, once published (see 1.5).
• Driver of the Day, when open (see 1.7).
• The full entry list.

1.5Results

Results appear once a steward publishes them. A result can be marked Draft (visible to staff only) or, after a correction, Amended.

• Race classification — broadcast-style table with gap to the leader, interval, best lap and (in championships) points. Endurance grids are split by class (Hypercar / LMP2 / GTE …) with a class-winner podium and per-class gaps.
• Fastest lap — flagged with an FL badge and a callout.
• Pace analysis — a lap-time chart plus a table of each driver's average lap, consistency and gap to the best average, using only green-flag representative laps.
• Qualifying — its own grid-order table with pole and gap-to-pole, published alongside the race.

1.6SRC Rating & Safety Rating

Every published race result updates two numbers per driver. Full method on the Rating Guide.

• SRC Rating — a multiplayer ELO scored from your finishing position against the whole field, weighted by the strength of that field. It is provisional until you have five races.
• Safety Rating — an iRacing-style corners-per- incident measure. Incident points come from penalties on the result file; a clean race raises it, contact and cutting lower it. Shown as a band (S / A / B / …) plus a number.
• Both recompute automatically on every published or amended result — there is nothing to submit.

1.7GT3 Licence

Separate from the rating: a one-time competitive grading for GT3 drivers. Shown as a colour-coded badge on your profile and the driver list.

• GT3 ROOKIE — every new GT3 driver starts here. Your first five completed GT3 races are the assessment window.
• After race five the system assigns SRC PRO, SRC PRO-AM or SRC AM from a 0–100 score built out of race pace, quali pace, consistency, finishing, race completion and incident record — all measured relative to each field and scaled by the strength of the opposition.
• Finishing position alone does not decide it: a P10 in a brutal field can outscore a win in a weak one.
• It is fully automatic — no admin has to promote you. Admins can override and lock an individual licence if a call is needed.

1.8Driver of the Day

On championship races with a published result, every driver can cast one Driver of the Day vote from the race page. You can change it any time while voting is open; you can't vote for yourself. The tally is public, the individual ballots are not.

1.9If something happens on track — protests

1. Open the race page and use File a protest (or the button on Steward decisions).
2. Name the drivers/cars involved, the lap and corner, and add a clip link or timestamp. Be factual.
3. A steward moves it through Open → Under review → Verdict, and possibly Appealed, then Closed.
4. Outcomes and reasoning are posted to the public Steward decisions log. Penalties are applied to the result and your ratings recompute.

Respect the protest window and evidence standard in the Rulebook, §2.

1.10Supporter area

/supporter has two parts. The supporter role is granted by an admin or manager.

• Setup library — downloadable ACC and LMU setup packs. Everyone can see what each pack contains; the download button only works with the supporter role.
• Supporter races — paid one-off races, visible to everyone. Payment is a Stripe checkout link set by the admin. If you have the supporter role and the race has a supporter link, you get that price instead.

1.11Tools

/tools — driver utilities. Live now: the LMU / WEC stint & strategy planner (lap-by-lap sim of a time-certain WEC race, sequential pit service) and the ACC stint & strategy calculator (sprint or endurance, by time or laps, ACC's parallel pit service and mandatory-stop rules).

1.12Personal pace log

A private record of your own Le Mans Ultimate (and ACC) sessions, fed automatically from your PC. Nobody else sees it — only you and staff.

1. In Settings → Personal pace log, press Generate token (treat it like a password; Regenerate rolls it).
2. Download lmu-pace-watch.ps1 from that card and run the PowerShell command it shows — it already has your token and address filled in. If LMU isn't in the default Steam folder, add -ResultsPath "…\UserData\Log\Results".
3. Leave the window open while you drive. The first run also sends the last few days of results; after that every new result file is sent as it is written.

Each session you appear in is stored with its full lap breakdown and shown on My pace:

• Best lap and average race pace (green-flag laps within 107% of your best that session), plus a consistency spread.
• Best lap and best average per sim and track, so you can see where you are quick and where you lose time.
• If a race file matches a league event you are entered in, it is also attached to that race as a provisional result. It never overwrites a result a steward has already published.

Full setup, auto-start and troubleshooting: Pace watcher guide.

2.1Where you work

• /admin/stewards — the protest / incident queue.
• /admin/results — publish, withhold, amend or delete results (shared with staff).
• /stewards — the public decisions log that members read.

2.2The protest workflow

1. Open — a new protest lands in the queue. Check it is in-window and has enough to act on; ask for a clip if not.
2. Under review — you are working it. Pull the other party's account if needed.
3. Verdict — record the decision, the rule reference and the penalty (if any).
4. Appealed — the penalised party has contested it within the appeal window; a head steward re-reviews.
5. Closed — final. The decision publishes to /stewards.

2.3Reading the incident

The result data on the event page is your evidence base:

• Classification + interval — who was where, and the real gap at the time.
• Pace analysis — lap times around the incident lap, and whether a car was already off the pace or erratic.
• Penalties already on the file (track limits, contact, pit speed) feed the Safety Rating and show intent/pattern.
• Lap and sector times per car for the laps in question.

2.4Penalties

Apply the Rulebook §2 penalty guide — it fixes the penalty class, the second/points values and the cumulative thresholds. The tools available:

• Warning — logged, no time effect.
• Time penalty — seconds added to race time (post-race) or served.
• Grid drop — places lost at the next race.
• Points deduction — championship points removed.
• Disqualification (DSQ) — removed from the classification.
• Safety-rating adjustment — a direct correction where the incident points don't reflect the severity.

2.5Amending a published result

Editing a result after publication (a penalty, a correction) sets it to Amended and re-runs the standings, SRC Rating, Safety Rating and licence assessment automatically. You do not need to recompute anything by hand — but check the driver's history afterwards to confirm it landed.

3.1Members & roles

/admin/members (managers and admins). Grant or revoke roles per member. Managers may hand out supporter, steward and admin; admins additionally grant the higher staff roles and manager. You cannot change your own roles.

3.2Servers

/admin/servers. One row per game server.

• Sim — ACC or LMU. Determines the result-file format and paths.
• FTP host / user / password, results path, config path — for the GPortal poll and the entry-list push.
• Result release — Automatic (a fetched result is published straight away) or Manual (it lands as a draft for a steward). This is the server's policy and it is authoritative.
• Lock entry list — freezes the pushed grid. Console entry list — appends the team name to the surname field for console servers.

3.3Championships

/admin/championships.

1. Create the series: name, sim, car class, season, format, points scheme.
2. Add the calendar (events) and assign each to a server.
3. Accept team entries; set per-entry ballast / restrictor / driver category / grid / livery, and the driver line-up.
4. The accepted grid pushes to each server's entrylist.json automatically on accept/revoke, or on demand with “Push entry list”.

3.4Points schemes

/admin/points-schemes. Define the per-position points, pole and fastest-lap bonuses, and drop-round count. Attach a scheme to a championship.

3.5Races

/admin/events. Create standalone races (daily races) or events inside a series. Set the track, start time, server and publish mode. Paid races are created separately in /admin/supporter (§3.9).

3.6Results

/admin/results.

• GPortal poll — runs on a schedule and can be triggered by hand. It fetches new ACC/LMU result files, matches them to an event by date, and imports them following the server's release policy.
• Manual import — upload an ACC .json or an LMU .xml. The session type (practice / qualifying / race) is read from the file, so import the qualifying file and the race file separately and both show on the race page.
• Each session result has its own publish / withdraw toggle and a delete. Publishing or amending re-runs ratings and licences.
• Unmatched files sit in an “Unassigned” list to attach to an event by hand.

3.7Ratings

/admin/ratings. ELO + Safety Rating recompute on every published result; the button here is the manual fallback if one ever gets stuck.

3.8Licences

/admin/licences. Tune the assessment without a code change:

• Factor weights — pace / quali / consistency / finishing / completion / incidents (ratios; re-normalised).
• Thresholds — the 0–100 score at which a driver becomes PRO and PRO-AM (below PRO-AM → AM).
• Model parameters — pace range, consistency range, incident cap, strength-of-field baseline & span, opposition swing, minimum completion, and how many races the Rookie window is.
• Recompute now — full replay of every published GT3 race. Locked drivers are skipped.
• Per-driver override + lock — set a licence by hand and stop the engine touching it.

3.9Supporter area

/admin/supporter (admins and managers).

• Setup packs — the archives live in a private Supabase Storage bucket named setups. Upload the ZIP there, set its object path here, tick “Published”. Downloads are handed out as short-lived signed URLs after the supporter-role check.
• Paid races — create a race with a price label and two Stripe Payment Link URLs (standard + supporter). Make the links in your own Stripe dashboard (Payment Links). The race shows on /supporter and its own event page with an “Enter & pay” button; supporters get the supporter link automatically.

3.10Environment notes

• SUPABASE_SERVICE_ROLE_KEY — required for the poll, ratings, licences, role management and setup downloads.
• OPENWEATHER_API_KEY — the trackside weather strip; without it the strip just doesn't render.
• INGEST_SECRET — protects the poll endpoint; the same value goes in the scheduled job.
• Serverless functions run in the Frankfurt region, co-located with the EU database. A cron job keeps the homepage warm.