232 lines
5.3 KiB
Markdown
232 lines
5.3 KiB
Markdown
# GridPilot — The Competition Platform for iRacing Leagues
|
||
*A modern, lightweight platform that gives iRacing league racing structure, identity, and long-term meaning — without taking control away from communities.*
|
||
|
||
---
|
||
|
||
# 1. What GridPilot Solves
|
||
|
||
iRacing’s strength is racing quality, not league infrastructure.
|
||
Today, league racing suffers from:
|
||
|
||
- scattered tools (Discord, Sheets, Forms, DMs)
|
||
- zero unified identity for leagues
|
||
- heavy admin workload for every race
|
||
- no automatic standings or result sync
|
||
- no long-term driver identity or career stats
|
||
- no proper team-based competition
|
||
- unstructured protest handling (DMs, screenshots, chaos)
|
||
|
||
GridPilot becomes the **competition layer** above iRacing.
|
||
We don’t change racing — we fix everything around it.
|
||
|
||
---
|
||
|
||
# 2. Who GridPilot Is For
|
||
|
||
## League Admins
|
||
Need:
|
||
- easy season setup
|
||
- automatic result handling
|
||
- clean standings
|
||
- a structured complaints/penalty workflow
|
||
- predictable points systems
|
||
- modern league presentation
|
||
- simple driver/team signups
|
||
- optional session-creation QoL automation
|
||
|
||
## Drivers
|
||
Need:
|
||
- easy league discovery
|
||
- simple registration
|
||
- clean standings
|
||
- reliable schedule
|
||
- personal stats and history
|
||
- long-term progression
|
||
- team + individual competition
|
||
- structured way to file complaints
|
||
|
||
Admin + Driver = **GridPilot’s only focus for MVP**.
|
||
|
||
---
|
||
|
||
# 3. Core Features (MVP)
|
||
|
||
## 3.1 League Identity
|
||
- clean public league page
|
||
- schedule, standings, roster, rules
|
||
- league branding (logo, colors)
|
||
- optional custom domain
|
||
- links to Discord / YouTube / Twitch
|
||
|
||
## 3.2 Season Management
|
||
- full calendar for each season
|
||
- point system presets
|
||
- drop weeks
|
||
- team or solo mode
|
||
- automatic standings
|
||
|
||
## 3.3 Driver & Team System
|
||
### Drivers:
|
||
- league join flow
|
||
- personal stats (per race + lifetime)
|
||
- progression + history
|
||
- cross-league identity (v1 basic)
|
||
|
||
### Teams:
|
||
- create/manage teams
|
||
- team roster management
|
||
- real “Constructors Championship” parallel scoring
|
||
- team standings + history
|
||
|
||
(This is a unique selling point: **real team racing in iRacing leagues**.)
|
||
|
||
---
|
||
|
||
# 4. Complaints & Penalties (Essential)
|
||
|
||
A structured system to replace Discord DMs and random drama.
|
||
|
||
## 4.1 Driver Complaints
|
||
Drivers can file a complaint with:
|
||
- race
|
||
- involved drivers
|
||
- timestamp(s)
|
||
- description
|
||
- optional replay clip / link
|
||
|
||
Keeps everything organized and searchable.
|
||
|
||
## 4.2 Admin Penalty Tools
|
||
Admins get a review panel:
|
||
- complaint list
|
||
- timestamps + notes
|
||
- direct links to replays
|
||
- quick actions:
|
||
- no action
|
||
- warning
|
||
- time penalty
|
||
- points deduction
|
||
- DQ for race
|
||
|
||
## 4.3 Automatic Standings Update
|
||
When a penalty is assigned:
|
||
- driver points update
|
||
- team points update
|
||
- classification updates with time penalties
|
||
- everything logged transparently
|
||
|
||
Admins stay in control.
|
||
Drivers understand the decision.
|
||
Chaos disappears.
|
||
|
||
---
|
||
|
||
# 5. Result Automation (Essential QoL)
|
||
|
||
- automatically sync race results from iRacing
|
||
- parse positions, laps, incidents, fastest lap
|
||
- update standings instantly
|
||
- eliminate manual CSV uploads or spreadsheets
|
||
|
||
This is **core** for both admins and drivers
|
||
(but not the “main feature” — just feels like magic).
|
||
|
||
---
|
||
|
||
# 6. Optional: Session Creation QoL (Not required)
|
||
|
||
GridPilot can assist admins:
|
||
- create sessions via browser automation
|
||
- batch-create entire season
|
||
- consistent settings without errors
|
||
|
||
Important:
|
||
**Automation is a helper, not the product.**
|
||
We never touch gameplay.
|
||
|
||
---
|
||
|
||
# 7. Competition Layer
|
||
|
||
This is what makes GridPilot more than “tools”.
|
||
|
||
## 7.1 Individual Progression
|
||
Drivers earn:
|
||
- points
|
||
- standings
|
||
- history
|
||
- personal stats
|
||
- performance trends
|
||
|
||
Racing finally has **long-term meaning**.
|
||
|
||
## 7.2 Team Competition
|
||
Teams accumulate points across races and seasons.
|
||
Drivers contribute to team success even when racing individually.
|
||
|
||
The result:
|
||
**iRacing Ligen finally feel like real motorsport championships.**
|
||
|
||
---
|
||
|
||
# 8. Safety, Security & Trust
|
||
- zero-knowledge login
|
||
- we never see or store passwords
|
||
- browser window visible for login
|
||
- automation always runs *on the admin’s machine*
|
||
- no client modification (unlike iRefined)
|
||
|
||
Trust and legality are fundamental.
|
||
|
||
---
|
||
|
||
# 9. MVP Philosophy
|
||
|
||
### What we include:
|
||
- Admin QoL tools
|
||
- Driver identity
|
||
- Team competition
|
||
- Standings + automation
|
||
- Complaints + penalties
|
||
- League identity + presentation
|
||
- Session creation helper (optional)
|
||
|
||
### What we leave out for now:
|
||
- stewards marketplace
|
||
- streaming tools
|
||
- monetization
|
||
- complex global ladder
|
||
- rating systems
|
||
- cross-sim functionality
|
||
- esports organization
|
||
|
||
GridPilot starts **simple and solid**.
|
||
|
||
---
|
||
|
||
# 10. Long-Term Vision (kept small but real)
|
||
|
||
GridPilot becomes the central place where:
|
||
- drivers build a career
|
||
- teams compete across seasons
|
||
- leagues run without chaos
|
||
- complaints/penalties stay structured
|
||
- standings stay consistent
|
||
- automation reduces work
|
||
- identity and progression matter
|
||
|
||
This is the part that makes us **THE platform**,
|
||
but we don’t overpromise it on day one.
|
||
|
||
---
|
||
|
||
# Summary
|
||
|
||
**GridPilot simplifies league management —
|
||
and elevates it from scattered spreadsheets
|
||
to a modern competition platform.**
|
||
|
||
Admins get less work.
|
||
Drivers get more meaning.
|
||
Teams get real championships.
|
||
Everyone gets structure instead of chaos. |