Skip to content

docs: scope the ADMIN LIMITATION rule to official incident count/severity #64

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
simsteward merged 1 commit into from
Jul 19, 2026
Merged

docs: scope the ADMIN LIMITATION rule to official incident count/severity #64

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@

## iRacing Shared Memory
- Use **IRSDKSharper**. Do NOT use `GameRawData`.
- **ADMIN LIMITATION**: Live races show 0 incidents for others unless admin. Replays track all.
- **ADMIN LIMITATION is narrower than it sounds**: live races expose 0 *official incident count / point severity* for other cars unless admin (`docs/IRACING-DATA-AVAILABILITY.md` Group 1). Event-level detection is NOT gated — `CarIdxTrackSurface`/`CarIdxSessionFlags` (Group 2) are available live, for every car, no admin required, and are exactly what the off-track/flag detector already runs on. Don't read this as "incidents are invisible live for other cars" — only the exact official count/point value is.
- **Incident types (deltas)**: 1x (off-track), 2x (wall/spin), 4x (heavy contact). Dirt: 2x heavy.
- **Quick-succession**: 2x spin -> 4x contact records as +4 delta.
- **Replay**: At 16x speed, YAML incident events are batched. Cross-reference `CarIdxGForce` and `CarIdxTrackSurface` to decompose type.
Expand Down
Loading