How the iRacing Protest System Works: A Real Intentional Wrecking Case
Anyone who races online for long enough will eventually encounter an incident that feels like more than an ordinary racing mistake.
Most contact in sim racing does not belong in a protest. Drivers miss braking points, misjudge overlap, lose control, make clumsy rejoins and occasionally attempt moves that were never going to work. That can be frustrating, but poor judgement is not automatically malicious conduct, and it's important to remember that most drivers in iRacing are not professionals and mistakes will happen.
Intentional wrecking is different.
During a recent GT3 race at Mount Panorama, we found ourselves on the receiving end of what appeared to be a retaliatory collision. We saved the replay, reviewed the incident after the emotion had settled and submitted a protest through the iRacing system.
The response identified the violation as:
6.12.3: Retaliation or Intentional Wrecking
The exact action taken against the other member remains confidential, as it should. However, the response confirmed that the protest was reviewed and that the member being protested was notified of the outcome, indicating that the protest was upheld.
The experience demonstrated why the protest system matters, but it also reinforced something equally important: a successful protest begins with evidence and neutral language, not anger.
What is the iRacing protest system?
The protest system is the formal process through which members can report conduct that they believe breaches the iRacing Official Sporting Code.
It is not intended to resolve every disagreement over racing room or determine fault in every ordinary collision. According to the official filing guidance, protests should concern Sporting Code violations such as retaliation or intentional wrecking, blocking, unsafe rejoins, abusive communications and other prohibited conduct.
The process gives iRacing an opportunity to review evidence and determine whether a member’s conduct warrants coaching, a penalty, a restriction or a suspension. The protesting driver is not told which of those outcomes, if any, is imposed.
That confidentiality is important. The purpose is to improve conduct, rather than create a public punishment system or encourage arguments between members.
Why protests are important
Online racing depends heavily on trust.
When two cars arrive at a corner together, each driver must trust that the other will make a reasonable attempt to maintain control, respect overlap and avoid deliberate contact. Drivers will still make mistakes, but everyone needs to believe that intentional retaliation has consequences.
Without an effective protest process, a driver who feels wronged could decide to take matters into their own hands. One retaliation leads to another, and an organised racing service quickly begins to resemble an unmoderated public lobby.
The protest system provides a better alternative:
- Save the evidence.
- Leave the session.
- Allow the mandatory cooling-off period to pass.
- Describe the suspected violation calmly.
- Let the stewards make the decision.
That process keeps disputes away from the circuit and helps preserve driving standards across the service.
It also encourages accountability. Drivers know that deliberate wrecking, dangerous rejoins, persistent blocking and abusive communications can be reviewed after the session. The possibility of a real consequence gives members a reason to pause instead of retaliating in the moment.
The system does not prevent every incident, but it makes clear that online competition still has rules.
Our Incident - Mount Panorama (Bathurst)
This incident occurred during a GT3 race at Mount Panorama in the Mercedes-AMG GT3.
We had qualified around ninth after setting a new personal best of 2:02.8. Several cars spun ahead of us during the opening laps, and we managed to avoid the incidents and move into fourth position.
There was certainly some luck involved in gaining those places, but we had the pace to hold the position once we got there. After putting substantial practice into the combination, this was also our only planned GT3 official race of the week.
On Lap 3, we attempted a move up the inside of another driver at Griffin’s Bend (T2). We committed early, held a tight inside line but the outside car turned in on us at the apex. Contact occurred and the other car spun before eventually returning to the pits for repairs.
That initial collision was included in the protest only as context. While there may be differing opinions on fault, it appeared to be a racing incident rather than intentional conduct.
Several laps later, the other driver emerged from the pits. Before we caught the car, the driver safely allowed another competitor to pass at Griffin’s Bend and then resumed normal speed.
We caught the car approaching The Cutting.
We recognised the car immediately and were conscious that the earlier incident might influence the driver’s behaviour. Three cars were a little over a second behind us, so we wanted to clear the slower car as quickly as possible to avoid losing time to them.
We moved to the outside at The Cutting. While our AMG was alongside, the other car opened its steering and moved across into us, causing contact and sending our car into the outside wall, resulting in major damage and effectively ending our race.
We eventually finished 18th and lost 60 iRating.
The result was frustrating, but the protest was not based on the finishing position, the lost iRating or the amount of practice we had completed. Those details explained why the incident hurt, but they did not prove a Sporting Code violation.
The relevant questions were much simpler:
- Was my car visibly alongside?
- Did the other car have room to maintain its line?
- Was there an observable steering movement toward my car?
- Did the earlier incident provide relevant context for possible retaliation?
- Did the replay show conduct consistent with an accidental loss of control, or an unnecessary movement into another car?
Those were questions for the stewards to answer.
We watched the replay several times and what stood out was a small but noticeable steering input toward our car while we were already alongside. The movement appeared unnecessary given the available track space and became a key factor in our decision to submit a protest.
What we included in the protest
The protest described the events in chronological order:
- The first incident at Griffin’s Bend on Lap 3.
- The other driver’s pit stop for repairs.
- The driver safely allowing a different car to pass after leaving the pits.
- Our approach to The Cutting on Lap 7.
- Our attempt to pass around the outside.
- The visible opening of the other car’s steering.
- The resulting contact, spin and damage.
Our Actual Protest Description
On Lap 7 at The Cutting, the protested driver made contact with my car while I was attempting to pass on the outside. Prior to this incident, there was contact between our cars on Lap 3 at Griffin’s Bend, which resulted in the protested driver spinning and later requiring repairs.
After leaving the pits, the protested driver safely allowed another car to pass before I caught the car approaching The Cutting. As shown in the attached replay, while my car is alongside on the outside, the protested driver opens the steering and moves into my car despite having room on the inside line. The contact spins my car into the wall and causes significant damage.
Given the earlier Lap 3 incident and the steering input shown in the replay, I believe this contact may have been retaliatory. Please review the attached replay files.
The wording was deliberately restrained.
It did not call the other driver names. It did not speculate about the driver’s personality. It did not demand a suspension. It did not focus on our lost iRating.
It identified the relevant conduct and directed the reviewer to the evidence.
The Outcome
The response from iRacing stated:
We have reviewed your protest and notified the member being protested of the outcome.
The outcome of every protest is kept confidential and may result in coaching, penalties, restrictions, or suspensions based on the severity of the violation and the member’s history.
Violation: 6.12.3 – Retaliation or Intentional Wrecking
That does not tell us precisely what happened to the other driver, nor should it.
What it does tell us is that the submission was reviewed under the exact Sporting Code provision identified in the protest. The system received the evidence, considered the incident and identified the matter as a violation of 6.12.3 Retaliation or Intentional Wrecking.
While iRacing keeps outcomes confidential, the response indicates that the protest was successful and that action was taken under the relevant Sporting Code provision.
At that point, our involvement ended.
How to submit a strong iRacing protest
1. Save the replay before leaving
A written description is not enough. iRacing states that a relevant replay attachment is required and that protests without replay evidence will not be considered. The official guidance also lists a 30 MB attachment limit, so the replay should be clipped to the relevant incident rather than submitting an entire race.
If there is important context, preserve enough footage to show that context as well. In this case, separate clips or a carefully edited sequence could show both the earlier collision and the later suspected retaliation.
Replays must be saved before exiting the simulator. They can subsequently be opened through the UI and trimmed using the replay cut and save tools.
It's recommended to submit multiple replay files showing the incident from different angles - a wide chase view as well as cockpit views are good ones to include as it can clearly show steering inputs to help identify exactly what each driver was doing behind the virtual wheel.
2. Use the cooling-off period properly
iRacing requires a 30-minute cooling-off period after the session before a protest can be filed.
This is not merely an administrative delay. Use the time to move from:
“That driver deliberately ruined my race.”
to:
“The replay appears to show an unnecessary steering input into my car while I was alongside.”
The second version is more useful to a reviewer because it identifies something visible and testable.
3. Identify the relevant Sporting Code provision
Do not submit a protest simply because an incident was costly or because you believe another driver was at fault.
Ask what rule may have been broken.
The official guidance specifically identifies 6.12.3, Retaliation or Intentional Wrecking, as protestable conduct. It also lists matters such as blocking and unsafe rejoins under their relevant provisions.
The protest form should connect the evidence to the suspected violation. It should not require the steward to work out why the incident has been submitted.
4. Describe observable actions
Strong protest descriptions focus on what can be seen or heard:
- The car moved left after another car became fully alongside.
- The steering angle increased toward the outside car.
- The driver accelerated into a stationary vehicle.
- The car rejoined perpendicular to traffic.
- A driver repeatedly changed direction in response to an attacking car.
- A chat or voice recording contains the reported language.
Instead of writing:
“The driver was furious and wanted revenge.”
Write:
“There had been contact between our cars on Lap 3. On Lap 7, while my car was alongside, the driver opened the steering and moved into my car despite having room to remain on the inside.”
The earlier incident establishes possible context. The steering movement is observable. The steward can then determine whether the evidence supports retaliation.
5. Keep the description chronological
A reviewer should be able to understand the incident in one reading.A useful structure is:
- When and where the conduct occurred.
- What happened immediately before it.
- What each car did.
- What action appears to breach the Sporting Code.
- Which replay file or camera angle shows it.
- What consequence followed.
6. Do not demand a particular punishment
The purpose of the protest is to report conduct, not impose a sentence.Member history and the severity of the violation may influence whether the response involves coaching, penalties, restrictions or suspension. Protesters generally do not have access to that history, so demanding a specific penalty adds little value.
Submit the evidence and allow the stewards to apply the process.
7. File through the correct channel
Official protests must be filed through the iRacing UI or member website. Emails or private messages to staff are not treated as protests. Submissions must be made within seven days of the incident.
What not to protest
The existence of a protest system does not mean every bad move should become a case.Ordinary racing incidents can include:
- Missing a braking point.
- Locking a tyre and sliding into another car.
- Misjudging overlap.
- Running wide on exit.
- Losing control over a kerb.
- Making a poor but genuine overtaking attempt.
- Netcode contact without clear misconduct.
This distinction matters. If the system becomes a way to appeal every collision, it creates noise and distracts from the incidents that genuinely require intervention.
The bigger lesson
Submitting the protest did not restore my fourth place. It did not return the 60 iRating, repair the AMG or give me another GT3 official race that week.What it did was move the incident into the correct process.
The protest system exists so drivers do not need to retaliate, argue in voice chat or pursue another member after the session. It gives the service an opportunity to review misconduct, educate drivers where appropriate and apply meaningful consequences when necessary.
For the system to work, members need to use it responsibly.
Save the replay. Let the initial anger subside. Identify the relevant rule. Describe the observable behaviour. Attach focused evidence. Then accept that the precise outcome will remain confidential.
Sim racing will always contain mistakes. It will always contain disagreements over racing room, responsibility and judgement. A well-run protest system does not eliminate those things.
It draws a firm line between making a mistake and deliberately using a race car as a weapon.
That line is essential if official racing is going to remain competitive, credible and worth preparing for.
Final Thoughts
In our case, the protest system worked as intended. The race result was gone, the iRating was not coming back and the damage had already been done. However, the incident was reviewed, action was taken and the Sporting Code was upheld.
That's ultimately why the protest system exists. Not to win arguments, but to maintain standards. The better those standards are upheld, the better official racing becomes for everyone.
Join the conversation