HOW TO PLAY

OC Grand Prix is a real-time overclocking competition. Your hardware runs actual workloads — compete in Battle Royale elimination races or rare Grand Prix endurance events organized by the site admin.

THE CONCEPT

REAL WORKLOADS

Every round, all players run the same workload simultaneously on their own hardware. Your actual CPU/GPU performance determines your score — no simulation, no emulation.

BATTLE ROYALE

The standard format. Each round, the slowest performers take HP damage. When your HP hits zero, you're eliminated. The last pilot standing takes the championship.

GRAND PRIX

A rare, admin-organized endurance event. Pilots run the same workload lap after lap — no HP, no elimination. The pilot who completes the most laps in the fastest cumulative time wins.

LEADERBOARDS

Race wins, round wins, HP dealt, and raw workload results are all tracked. Compete for the all-time standings or set personal records in solo mode.

HOW A BATTLE RACE WORKS BATTLE ROYALE

LOBBY

The host creates a room and shares the 6-character room code. Players join with their callsign. The host configures the number of rounds and workloads, then starts the race.

ROUND STARTS

All agents receive the workload simultaneously. Everyone runs the workload on their own machine at the same time. The agent reports your score back to the server in real time.

DAMAGE CALCULATION

After the round, scores are ranked. The fastest score takes no damage. Slower scores take increasing HP damage based on how far behind the leader they are. DNF (did not finish) takes maximum damage.

ELIMINATION

Any player whose HP reaches zero is eliminated. The race continues until only one pilot remains — or all rounds are completed, in which case the player with the most HP wins.

BATTLE RATING NEW

Battle races now feed a skill-based rating (Glicko-2, the same family used in chess) alongside the win-count leaderboard. It rewards beating strong pilots more than beating weak ones, and it's specifically hardened against smurf accounts and win-farming — full breakdown on the Battle Rating page.

ℹ CURRENTLY CALCULATING, NOT YET DISPLAYED Your rating is being tracked in the background for every Battle race already. It isn't shown on the leaderboard or your profile yet — that's coming in a follow-up update. See the Battle Rating page for the full explanation, including the anti-smurfing guardrails.

HOW A GRAND PRIX WORKS SPECIAL EVENT

The Grand Prix is an endurance format — no HP, no elimination. Pilots run the same workload repeatedly, lap after lap, for a fixed number of laps. The pilot who completes all laps with the fastest cumulative race time wins.

ADMIN-ONLY EVENT Grand Prix events are organized exclusively by the site admin and are held infrequently — roughly once a week or once a month. You cannot create a Grand Prix room yourself. Watch the announcements to know when the next one is scheduled.

JOIN THE GRID

When a Grand Prix is announced, join the room using the provided room code — just like a regular race. The admin host configures the workload and total lap count, then opens the grid.

GREEN LIGHT

Once all agents are ready, the admin starts the race. A global race clock begins. Every pilot immediately starts running the workload — lap 1 of N. There are no round gates; each pilot runs at their own pace.

LAP AFTER LAP

As soon as your agent submits a lap result, it immediately starts the next lap. Your race time is the global clock reading when you complete your final lap — not the sum of individual lap times. Consistency and uptime matter as much as raw speed.

CHECKERED FLAG

The first pilot to complete the required number of laps throws the checkered flag. All other pilots finish their current lap, then the race closes. Final classification is by laps completed, then by race time at last lap completion.

PIT STOPS If your agent disconnects mid-race, your current lap is invalidated and you enter the pits. You have a grace period (5 minutes by default) to reconnect and resume. If you don't reconnect in time, you are retired from the race — your completed laps still count toward the final classification.

SPECTATING You can watch any live Grand Prix from the Watch Grand Prix page. Enter the room code to follow the live lap-by-lap standings, race clock, and pilot streams.

OC CHALLENGE ASYNC QUEUE

Challenges are published workload queues that anyone can run at their own pace. Unlike Battle or Grand Prix, there's no real-time room — just a shared queue definition and a leaderboard aggregating total completion time across all participants.

HOW IT WORKS

A challenge creator (like SkatterBencher) defines an ordered sequence of workloads — for example, run CPU IPC, then memory, then y-cruncher. Each participant downloads the queue, runs all steps in order, and their total time (sum of all step scores) is posted to the leaderboard.

REFERENCE RUNS

The creator can submit their own runs as "reference strategies" — these appear pinned at the top of the leaderboard, showing different OC approaches (e.g. "Air Cooling", "LN2"). Viewers can compare their times against these reference strategies.

⏱

YOUR PACE

There's no countdown or lockstep timing. Run the queue whenever you want, take breaks between steps (within reason), and retry as many times as you like. Only your best complete attempt counts toward the leaderboard.

SHARING A CHALLENGE Each challenge has a 6-character code (e.g. K7Q2R9). Share this code in your videos, guides, or social media. Viewers enter the code in the agent to fetch and run the exact same queue.

VIEWING CHALLENGES Browse all active challenges at /challenges. Each challenge page shows the queue definition, the creator's reference runs, and the full challenger leaderboard ranked by total completion time.

PLAYING SOLO NO ROOM NEEDED

You don't need a race room to compete with your hardware. Solo mode lets you run any workload at any time and post your score to the global leaderboard.

CREATE AN ACCOUNT

Go to Account and register. You'll get an agent token — a unique key that links your results to your account.

DOWNLOAD THE AGENT

The OCGP agent is a small desktop app that runs on your machine and executes the workloads. Download the latest build → (Windows 64-bit, no Python required)

CONFIGURE YOUR TOKEN

Open the agent, go to Settings, and paste your agent token from your account page. This links your scores to your callsign on the leaderboard.

RUN A WORKLOAD

On the Leaderboard page, find the Solo section. Click a workload variant to see the leaderboard, then use the agent to run it. Your score will appear automatically.

WATCH LIVE You can watch any pilot's live solo benchmark attempt from the Solo Spectator page. Enter the pilot's name to see their real-time progress, sector events, and telemetry as they run.

RUN RESULTS Every solo run gets its own result page at /run-result?id=... with telemetry, hardware specs, and a shareable card image. Share your results on social media — the card auto-generates an Open Graph preview.

SOLO QUEUE You can chain multiple workloads together into a solo queue — run CPU IPC, then memory, then y-cruncher, all in one session. Each queue run gets a unique integer ID linking all steps, and a detail page at /result/queue/{id} showing the full sequence and aggregate time. Challenges are a special case of solo queues with a predefined, published queue definition.

PLAYING MULTIPLAYER BATTLE ROOM

CREATE OR JOIN A ROOM

Go to Lobby. The host clicks Create Room and configures the race settings. Other players click Join Room and enter the 6-character room code.

CONNECT YOUR AGENT

Open the OCGP agent on your machine. Enter the room code and your callsign. The agent will connect and show as "READY" in the waiting room. Make sure your agent token is configured so your results are saved.

HOST STARTS THE RACE

Once all agents are connected and ready, the host clicks Ignite Engines. A countdown begins, then the first round starts automatically.

RACE!

Your agent runs each workload automatically when the round starts. Watch the live standings in the browser. After each round, results are shown and the next round begins. Survive all rounds to win.

TIP You can add a stream URL (Twitch, YouTube) when joining a room. Your stream will appear in the spectator view so others can watch your screen live.

THE AGENT

WHAT IT DOES

The OCGP agent is a lightweight desktop application that:

Connects to the race server via WebSocket
Downloads and runs workloads when a round starts
Reports your score back in real time
In Grand Prix mode, automatically starts the next lap as soon as the previous one completes
Reports hardware specs (CPU, GPU, RAM, motherboard) automatically
Collects and streams system telemetry (temperatures, clock speeds, utilization) during runs
Reports sector-level progress for workloads that support it
Auto-reconnects on disconnect
Works in the background — no manual interaction needed during a race

REQUIREMENTS

Windows 10/11 (64-bit)
No Python required — everything is bundled
Internet connection to the race server
Workload dependencies install automatically on first run

Linux support is experimental. macOS is not currently supported.

↓ DOWNLOAD LATEST

AGENT TOKEN

Your agent token is a secret key that links results to your account. Keep it private — anyone with your token can submit scores under your callsign.

You can regenerate your token at any time from the Account page.

WORKLOADS

Each round uses one of the available workloads. Scores are measured in milliseconds — lower is faster. Scores are only comparable within the same workload and variant. Click any workload below for its full description, variants, and current records.

⏳

LOADING WORKLOADS...

Fetching available workloads from the server.

WORKLOAD DETAIL PAGES Each workload has a dedicated page at /workload?id=... showing all variants, current records, and per-variant leaderboards. Click a workload name or variant link above to explore.

THIRD-PARTY WORKLOADS Some workloads require third-party benchmark software to be installed. For example, cinebench_2026 requires Cinebench 2026, and ycruncher requires y-cruncher. Check the workload detail page for the exact software and approved versions before joining a race that uses them.

Making the software recognized 1. Download and install (or extract) the required software.
2. Either set its path in the agent under Settings → External Dependencies (one "executable path" field per dependency), or drop the executable anywhere inside ~/.ocgp/external/ (on Windows: C:\Users\<you>\.ocgp\external\ — the agent creates this folder on startup; any layout inside works).
3. The agent auto-detects the executable, fills in the Settings path, and hash-checks it against the approved builds. A Challenge or race that needs it stays gated (START greyed out) until every dependency resolves; saving a path re-runs the check.

PILOT PROFILES

Every pilot on OC Grand Prix has a public profile page at /pilot?name=... — click any pilot name anywhere on the site to view their full stats.

👤

PILOT STATS

Each profile shows total runs across all modes, race history (Battle and Grand Prix), personal best records per workload, and platform-wide rankings. Pilot names are displayed with country flags when configured.

HARDWARE SPECS

The agent reports your hardware specifications (CPU, GPU, RAM, motherboard) which are stored and displayed on your pilot profile and run results. This helps others see what hardware achieved each score.

🟢

ONLINE PRESENCE

Pilots currently connected to the server show a green online indicator on their profile and in room lobbies. The indicator disappears shortly after disconnection.

📝

RUN NOTES

You can add notes to your benchmark runs (e.g. cooling method, ambient temperature, voltage settings). Notes are visible on the run result page and help document your tuning journey.

RUN RESULTS & SHARE CARDS

Every benchmark run — whether from a Battle, Grand Prix, or Solo attempt — gets its own result page with detailed telemetry, hardware specs, and a shareable card image.

RUN RESULT PAGE

Each run has a dedicated page at /run-result?id=... showing the pilot, score, workload variant, hardware specs, sector-level telemetry (when available), and a full telemetry time-series chart.

BATTLE RESULT PAGE

After a Battle race ends, the result is available at /battle-result?room=... showing the full race summary, per-round breakdown, damage dealt, and final standings.

GRAND PRIX RESULT PAGE

Grand Prix results are at /grand-prix-result?room=... with lap-by-lap classification, race time, and pilot status (finished, retired, DNF).

🃏

SHARE CARDS

Each result page auto-generates a social share card (1200×630 PNG) with the pilot name, score, workload, and rank. These are used for Open Graph previews when sharing links on social media.

PLATFORM STATS

The Platform Stats page provides a live overview of the entire OC Grand Prix ecosystem.

PLATFORM OVERVIEW

Summary tiles show total pilots, battles run, Grand Prix events, solo runs, total workload runs, total HP dealt, unique workloads played, and active pilots in the last 7 days.

🏃

MOST ACTIVE PILOTS

A ranked table of the most active pilots by total runs across all modes (Battle, Grand Prix, Solo), including unique workloads attempted and last active date.

📈

WORKLOAD POPULARITY

Each workload is shown with per-variant run counts split by mode (Battle/GP/Solo), unique pilot counts, best scores, and visual bar charts showing the mode distribution.

FAQ

What is the difference between Battle and Grand Prix?▸

Battle is the standard format — HP-based, elimination-style, anyone can host. Each round the slowest pilots take damage; last rig standing wins.

Grand Prix is a special endurance event organized exclusively by the site admin. There is no HP or elimination — pilots run the same workload lap after lap, and the fastest cumulative race time wins. Grand Prix events are held infrequently (roughly once a week or once a month).

How do I join a Grand Prix?▸

Grand Prix events are announced by the site admin. When one is scheduled, a room code will be shared. Join using that code from the Lobby — the process is the same as joining any other race room. You cannot create a Grand Prix room yourself; only the site admin can organize one.

What happens if I disconnect during a Grand Prix?▸

Your current lap is invalidated and you enter the pits. You have a grace period (5 minutes by default) to reconnect. If you reconnect in time, you resume racing from the start of that lap. If the grace period expires, you are retired — your previously completed laps still count toward the final classification.

How is the Grand Prix winner determined?▸

Classification is sorted first by laps completed (more is better), then by race time at the moment of the last completed lap (earlier is better). The first pilot to complete the required number of laps throws the checkered flag; all other pilots finish their current lap before the race closes.

Do I need to overclock my hardware to compete?▸

No — but it helps! OC Grand Prix is designed for overclockers, but anyone can participate. Stock hardware is welcome. The workloads measure raw performance, so any tuning you do (overclocking, memory timings, power limits) will show up in your scores.

Is it free to play?▸

Yes, completely free. Create an account, download the agent, and race.

What if my agent crashes or disconnects mid-race (Battle)?▸

If your agent doesn't submit a score for a round, you receive a DNF (Did Not Finish) for that round and take maximum damage. The agent will attempt to reconnect automatically.

Can I spectate a race without playing?▸

Yes. For Battles, go to Watch Battle and enter the room code. For Grand Prix events, go to Watch Grand Prix. You'll see live standings, scores, and any player streams in real time — no agent required.

How many players can be in a Battle race?▸

The default maximum is 100 players per room, but the host can configure this up to 500. There's no minimum — you can even race solo against yourself for practice.

Are scores saved permanently?▸

This is currently an alpha build. Race data and accounts may be wiped without notice as the platform is developed. We'll announce when data persistence is guaranteed.

Can I run a private Battle race?▸

Yes. When creating a room, set visibility to Private and optionally add a password. Private rooms won't appear in the public races list.

What is the damage formula (Battle)?▸

The fastest score in a round takes 0 damage. Each subsequent position takes progressively more damage based on the configured base damage and damage ramp. The exact formula is: damage = base_damage × (1 + damage_ramp × rank) where rank 0 = first place.

What is a pilot profile?▸

Every pilot has a public profile at /pilot?name=... showing their total runs, race history, personal best records per workload, hardware specs, and online status. Click any pilot name anywhere on the site to view their profile.

How does hardware spec reporting work?▸

The OCGP agent automatically detects and reports your hardware specifications (CPU, GPU, RAM, motherboard) when you run a workload. These specs are stored with your results and displayed on your pilot profile and run result pages. You can view your reported hardware from the agent's settings panel.

What are country flags next to pilot names?▸

Pilots can set their country in their account settings. When configured, a country flag icon appears next to their name on leaderboards, race standings, and pilot profiles. Flags use the flag-icons library.

What is the Platform Stats page?▸

The Platform Stats page provides a live overview of the entire OC Grand Prix ecosystem — total pilots, battles, Grand Prix events, solo runs, total HP dealt, unique workloads played, most active pilots, and workload popularity breakdowns by mode.

What are run result pages?▸

Every benchmark run gets its own result page at /run-result?id=... with the pilot name, score, workload variant, hardware specs, sector-level telemetry, and a telemetry time-series chart. Battle and Grand Prix races also have dedicated result pages at /battle-result?room=... and /grand-prix-result?room=....

Can I switch between light and dark themes?▸

Yes. Use the theme toggle in the site header to switch between light and dark mode. Your preference is saved in local storage and persists across sessions. The page renders in your chosen theme immediately on load to prevent flash.

Can I add notes to my runs?▸

Yes. When running a solo benchmark, you can add notes (e.g. cooling method, ambient temperature, voltage settings, memory timings). Notes are displayed on the run result page and help document your tuning configuration for each attempt.

Can I hide my results?▸

Yes. You can hide individual solo benchmark runs from your account page. Hidden runs are not shown on leaderboards or pilot profiles but remain in the database. Admins can also hide results or entire races if needed.

What is the server health/status page?▸

The /health endpoint provides a JSON status report of the server, including database connectivity, WebSocket status, and uptime. It's primarily used for monitoring but is publicly accessible.

What workloads require third-party software?▸

Some workloads require third-party benchmark software. For example, cinebench_2026 requires Cinebench 2026 to be installed, and ycruncher requires y-cruncher. Check the workload detail page for the exact software and approved versions.

How do I make a third-party benchmark recognized by the agent?▸

After installing or extracting the software, either set its executable path in the agent under Settings → External Dependencies, or drop the executable anywhere inside ~/.ocgp/external/ (on Windows: C:\Users\<you>\.ocgp\external\). The agent scans that folder on startup, auto-fills the Settings path, and hash-checks the build against the manifest's approved versions. A Challenge or race whose queue needs that software keeps its START button greyed out until every dependency resolves; saving a path re-runs the check.

Can I watch a pilot's solo run live?▸

Yes. The Solo Spectator page lets you watch a specific pilot's live solo benchmark attempt. Enter the pilot's name to see their real-time progress, sector events, and telemetry as they run.

What is a Challenge?▸

A Challenge is a published workload queue that anyone can run at their own pace. Unlike Battle or Grand Prix, there's no real-time room — just a shared queue definition and a leaderboard. The creator (like SkatterBencher) defines an ordered sequence of workloads, and participants run all steps to compete for the best total completion time.

How do I create a Challenge?▸

Challenge creation requires a Pro subscription or the is_challenger flag granted by an admin. If eligible, you can create a challenge via the API by sending a POST request to /api/challenges with your workload queue definition. The server returns a 6-character challenge code to share with your audience.

What's the difference between a Challenge and a Grand Prix?▸

Grand Prix is a real-time, concurrent race — all pilots run simultaneously in the same room, lap after lap, with a live race clock. Challenge is asynchronous — each participant runs the queue independently at their own pace, and the leaderboard aggregates total completion time across all attempts.

What are reference runs in a Challenge?▸

The challenge creator can submit their own attempts as "reference strategies" (e.g. "Air Cooling", "LN2", "Stock"). These appear pinned at the top of the leaderboard, giving viewers a benchmark to compare against. Each reference run is labeled with a custom name chosen by the creator.

What is a solo queue?▸

A solo queue lets you chain multiple workloads together in one session — run CPU IPC, then memory, then y-cruncher, all automatically. Each queue run gets a unique integer ID linking all steps, and a detail page showing the full sequence and aggregate time. Challenges are a special case of solo queues with a predefined, published queue definition.

CREATE A ROOM → DOWNLOAD AGENT → VIEW LEADERBOARD