CG-01
Scope and Competition Standards
This guide explains EFVD event procedure from driver entry through qualifying, tandem battles, results, and post-event review.
EFVD is a community-focused virtual motorsport organization built around respectful participation, driver development and organized competition. Driver performance under the published qualifying, tandem-battle, technical and conduct criteria determines event advancement, results and prizes. If those criteria do not resolve a tie, EFVD applies the tiebreaker procedures in this guide. EFVD does not use chance-based prize allocation.
Open competition with standards
Drivers can apply, but selected competitors must follow event rules, server procedure and staff direction.
No protected spots
Every driver earns advancement through qualifying and battles. Status does not guarantee a result.
Keep the event moving
Drivers must stage on time, respond quickly and avoid delays during official sessions.
Professional behavior matters
Driving skill does not excuse disrespect, public arguments, or repeated procedure issues.
Selection is discretionary
EFVD may refuse or remove an entry for conduct, preparation, technical issues, false information or event fit.
Drivers must follow event procedure, staff instructions, and conduct standards, and avoid unnecessary delays.
CG-02
Event Day at a Glance
This is the short version of event day. Use the sections below for full procedures, exceptions, and rules.
- 01
Open My EFVD
Confirm your event, release dates, registration, car, payment, qualifying group, and next action.
- 02
Follow the live join status
Join only on YOUR GROUP — JOIN NOW. Do not join on PLEASE WAIT, and stand down on QUALIFYING COMPLETE.
- 03
Stage correctly
Use the posted start position, start-light app and staff instructions.
- 04
Qualify
Complete official solo runs in the posted order.
- 05
Battle
Top qualified drivers run lead/chase matchups, usually targeting Top 32 when possible.
- 06
Follow live decisions
Judges decide during live flow. After the event, request a Free Judging Clarification if needed. Submit any eligible paid protest by the event's announced deadline.
CG-03
Before Event Day
Before official sessions, check My EFVD for event details. Use the EFVD Launcher to verify your setup and follow the live join status.
Open My EFVD
Confirm the schedule, release dates, qualifying group, and your current next action.
Read the Judging Guide
Use the Judging Guide for course expectations, tandem standards, DNF examples, OMT, and decision procedure.
Prepare event files
Use the EFVD Launcher and official announcements to check Track Release and Event Cars Release dates.
Use approved car
Only use the car, livery, number and driver identity approved for that event.
Complete launcher checks
Verify the package, track, Start Lights, Steam identity and wheel before live competition.
Test start-light app
Install and test the required start-light app before official runs.
Know your group
My EFVD shows your qualifying group after staff publishes the assignment.
Obey the live join status
Join only on YOUR GROUP — JOIN NOW. Otherwise, wait or stand down exactly as shown.
Be ready at staging
Stay near staging with your wheel ready. Move when staff calls you.
Keep chat clear
Use in-game chat for live operational issues only and avoid clutter during active runs.
Report issues immediately
Tell staff quickly if you disconnect, crash, load incorrectly or have another live issue.
Join briefing
Attend briefing for event-specific procedure, judging priorities, group order, and live communication rules.
Drivers must check My EFVD, complete launcher verification, follow the live join status, and obey direct Event Ops instructions.
CG-04
Event Rules and Server Standards
Official event servers are controlled competition spaces. Treat them differently from public practice servers.
| Area | Standard |
|---|---|
| Server access | The same server may be used for practice and official competition. Join only during approved windows and follow staff instructions. |
| Respawn | Do not respawn unless staff allows it or event procedure requires it. |
| Practice and connectivity | Drivers must use the practice server before the event. Confirm that you can connect, load content, and run without major issues. Drivers are encouraged to set up their own practice server when possible. |
| Live event restrictions | Practice is not allowed on the event server during the event. No practice runs, burnouts, donuts or test hits during live qualifying or battles unless staff allows it. |
| Private event content | Cars, tracks, downloads, and event assets are private unless EFVD states otherwise. Uploading, repacking, redistributing, leaking, or sharing them outside approved channels can lead to a ban. |
| Staging | Be ready when called and stay near the active staging area. |
| Driver identity | Use the registered or approved driver name in-server so staff, judges, broadcast and brackets can identify you correctly. |
| Registered driver only | Only the selected driver may drive the entry. Account sharing, substitute drivers or another person driving the run is not allowed. |
| Competitive integrity | Team orders, collusion, intentional manipulation of results or staged battle outcomes can lead to DQ, license review or conduct action. |
| Integrity review hold | For serious cheating, technical, conduct, or evidence concerns, EFVD may prevent a driver from continuing. EFVD may also pause prize eligibility or keep results provisional during review. |
| Chat | Keep chat clear during active competition. Report urgent issues briefly and clearly. |
| Game crash or disconnect | Report the issue immediately. Staff decides whether reconnect time, restart, DNF or removal applies. |
| Car or livery changes | Staff announces any approved changes on Discord. Drivers should not assume a change is allowed unless staff posts it. |
| Settings | Staff may adjust server settings for stability, broadcast operations or technical reasons. |
| Platform or system failure | If Assetto Corsa, Content Manager, Discord, or a required event system fails, staff may pause, delay, resume, shorten, or cancel event activity. |
| Event cancellation or postponement | EFVD may postpone, resume later, shorten or cancel an event when technical, staffing, platform or operational issues prevent fair competition. |
| Incomplete event results | If an event cannot be completed, EFVD decides whether completed stages stand. EFVD may keep results provisional, resume the event later, or void the round. |
| Minimum participation | EFVD may require a minimum number of eligible drivers for an event, split, payout or points result to count. Minimums may be confirmed in the event document. |
CG-05
Driver Briefing and Communication
Briefing is mandatory. Event-specific details can change from round to round.
Run order and timing
Group order, start time, battle flow, expected breaks and staging calls.
Layout details
Initiation point, zones, clips, decel zones, restart point and cone locations.
Round priorities
Line priorities, lead expectation, chase expectation and common deductions.
Server communication
Loading order, countdowns, restarts, technical issue reporting and staff contacts.
| Channel | Use |
|---|---|
| Discord announcements | Official event notices, event documents, downloads, schedule updates and driver instructions. |
| Event times | Discord event times use local timestamps so each driver sees the schedule in their own time zone. The event server is hosted on the east coast of North America. |
| Discord staff channels or tickets | Use for applications, technical questions, evidence, protests, appeals, and non-live issues. |
| In-game chat | Live communication with staff during official sessions, staging, restarts and urgent technical issues. |
| Driver briefing | Event-specific instructions that clarify or override general guide language for that round. |
| Active group joining | Staff announces groups in Discord. Drivers must join when their group is called and may not join during an active group unless staff instructs them to or they are reconnecting after a live-run disconnect. |
| Stay available | Drivers must remain available until eliminated, released by staff or the event ends. Podium drivers must remain for the podium ceremony unless staff approves otherwise. |
| Communication hierarchy | If rules or instructions conflict, follow the event document first, then driver briefing, live staff instruction, and the public guide, unless EFVD states otherwise. |
| Rule amendments | EFVD may update public rules, event documents, or live procedures. When practical, changes are posted before enforcement through Discord, briefing, or official site updates. |
| Staff role | Primary responsibility |
|---|---|
| Competition leadership | Final event authority, format decisions, escalations, cancellations and policy calls. |
| Event staff | Schedule, staging, server flow, group calls, live instructions and event operations. |
| Head of judges | Final judging authority during judging confusion, judge coordination and decision review. |
| Judges | Qualifying scores, battle votes, fault review, OMT, DNF and run evaluation. |
| Discord staff | Server moderation, announcements, tickets, community reports and non-live communication. |
| Escalation area | Who handles it |
|---|---|
| Judging confusion | The Head of Judges controls the judging process. Competition leadership handles final event-administration calls when needed. |
| Event procedure confusion | Event staff controls live flow. Competition leadership resolves unresolved operational conflicts. |
| Conduct issue | Discord staff or event staff contain the issue first. Competition leadership handles final discipline or escalation. |
| Technical issue | Event staff handles live flow. Technical staff or competition leadership decide event impact when needed. |
| Protest or appeal | Use the Protest and Appeal Guide. Protests are not argued during live event flow. |
| No-show | Event staff applies event flow handling. Competition leadership may apply future approval, selection or conduct notes. |
The event document and driver briefing control round-specific procedure. Follow them if they differ from a general public guide.
Drivers must follow event flow, watch group announcements, and be ready when called. Drivers who miss briefing may lose priority, be refused by staff, need approval to continue, or lose the ability to challenge a procedure issue covered in briefing. If you are late and unsure whether you can still run, load in when your group is active and wait for staff direction.
CG-06
Start Line and Staging
EFVD uses a dedicated start-light app for official runs. Drivers should install and test the app before event day using the current Discord link.
Position is event-specific
Staging position, start position and active run order are explained in the event Discord document or briefing.
Staff starts the light
Drivers follow the official start-light procedure or staff instruction before beginning the run.
45 seconds to line up
After being called, drivers have 45 seconds to warm tires, prepare, and position the car at the line unless event staff approves otherwise. Staff considers a driver ready once the car is at the line.
Follow event flow
Groups may be announced in Discord, but drivers remain responsible for following the event and being ready when called.
| Start issue | EFVD procedure |
|---|---|
| Not ready when called | Staff may skip, delay, DNF or remove the driver depending on event flow and repeated issues. |
| Wrong staging position | Staff may reset staging if caught before the run, or judges may apply procedure consequences if the run is affected. |
| Start-light issue | Staff may call hold, restart or another start method. If the light system fails, a driver may ask in in-game chat for a staff-controlled "3-2-1" start until a solution is found. |
| False start or start abuse | Staff may reset the run, issue a warning, apply DNF or refer the issue for conduct review if the start procedure is abused. |
| Start lane or lane change | If the event uses assigned lanes before initiation, drivers must follow the posted lane procedure. Unsafe lane changes, overlap abuse or contact before initiation can trigger restart, DNF or conduct review. |
| Driver confusion | Use in-game chat briefly for an immediate procedure or technical question. Do not debate a judging decision. |
CG-07
Initiation Rules
The initiation point, type, and judged reference markers are event-specific. They are explained in the Discord event document or briefing.
Parallel approach
Both cars may approach initiation close together when the event layout uses a side-by-side start. The chase can be ahead before initiation, but must be behind when crossing the initiation point.
Lead-first approach
The lead car starts ahead and the chase follows into initiation. The chase must respect the start procedure and avoid contact caused by excessive closing speed.
Before initiation
Contact before initiation triggers a restart. Staff or judges may still note repeated avoidable contact or start abuse.
Initiate at the marker
Drivers are expected to initiate according to the event-specific marker, cone, zone or instruction.
Drivers must make one committed drift initiation into the judged course. Three-point initiations, stacked feints, driving straight past initiation, or repeated direction changes to delay commitment are prohibited unless the event briefing allows a different technique.
Chase drivers may jump the start and be ahead before initiation. They must be behind when crossing the initiation point. The chase is expected to be in drift by the required marker and must not use the start to force contact or create an artificial advantage. Repeated early movement, forced contact, deliberate disruption, or failure to be behind at initiation may lead to a restart, deduction, DNF, or conduct review.
| Initiation issue | Typical handling |
|---|---|
| Three-point initiation | Not permitted unless the event briefing specifically allows it. This can create major deduction, DNF or review for procedure abuse. |
| Stacked feint or delayed commitment | Judges may treat repeated steering inputs, feints, or direction changes used to avoid the marker as an incomplete or manipulated initiation. |
| Incomplete initiation | Failing to initiate, initiating far too early or late, or driving straight past the required point can create major deduction or DNF. |
| Straightening | Losing drift angle enough to break the run is treated as a major mistake and may become DNF depending on severity and location. |
| Chase not in drift | If the chase is not in drift by the required initiation marker, judges may apply major deduction, DNF or battle disadvantage depending on impact. |
| Chase overlap | Overlap before initiation is allowed only when it remains controlled and follows the event start procedure. The chase remains responsible for avoidable pre-initiation contact. |
Judging begins at the initiation point unless the event briefing states otherwise. Start-line behavior and pre-initiation procedure can still create restarts, penalties, DNF, or conduct review. Line, angle, zones, clips, and tandem advantage are judged from initiation onward.
CG-08
Qualifying Format
Drivers normally receive two non-consecutive qualifying runs. The best valid score is used for ranking. If the event document gives a different qualifying or tiebreak procedure, that procedure controls.
Judged path
How accurately the driver follows the intended line and fills the course.
Clips and commitment
Accuracy and commitment to outside zones, inside clips and reference points.
Control
Amount, stability and control of drift angle through the judged section.
Direction changes
Timing, commitment, smoothness and control when changing direction.
Speed and rhythm
Momentum, pace and how naturally the run connects from zone to zone.
Execution
Style, stability and avoidance of corrections, spins, offs and major mistakes.
| Qualifying situation | Default EFVD handling |
|---|---|
| Best score ranks | The driver's highest valid run score sets their qualifying position. |
| Run order | Qualifying groups and run order are arranged by staff to support event flow and broadcast quality. Drivers must follow the designated group order unless staff instructs otherwise. |
| Score tie | Default tiebreaker order is best run score, then combined score from both runs, then best line value, then best angle value, then best style value when that data is available. |
| Missing tiebreak data | If a category value, second run or other tiebreak data is unavailable, EFVD moves to the next available tiebreaker rather than recreating unavailable data. |
| Still tied | If available scoring data cannot separate drivers, staff may use judge review, event timing needs, staff-administered draw or event-specific handling. |
| No valid score | A driver with no valid qualifying score is ranked below drivers with a valid score and may be excluded from battles if capacity requires it. |
| Missed run | A missed qualifying run is treated as no score for that run unless staff approves another handling before qualifying closes. |
| Late arrival after qualifying starts | Late drivers may lose missed runs, receive no score for missed attempts or be removed from qualifying unless staff approves another handling. |
| Bracket bubble | When the final battle position is tied, staff may use the qualifying tiebreaker order or a runoff if event timing allows it. |
CG-09
Battle Format
Top qualified drivers advance to the battle bracket. EFVD normally uses Top 32 when event size allows. The event document may define a smaller or adjusted bracket based on attendance, timing, or format.
| Battle bracket rule | Expected behavior |
|---|---|
| Bracket size | Top 32 is the default target for standard EFVD battle events. If fewer eligible drivers are available, staff may run a smaller bracket, byes or another event-specific structure. |
| How it is built | The bracket is built from qualifying rank after tiebreakers, eligibility checks and any staff-approved withdrawals or removals. |
| Where it is shared | Official brackets, battle order and updates are shared through the event Discord channels or event document. Broadcast graphics may help viewers, but Discord remains the driver reference. |
| Driver responsibility | Drivers must follow the posted bracket and battle order, watch Discord/in-game calls and be ready when their matchup is called. |
| Stage correctly | Drivers must line up according to the event document and follow the start-light or staff-controlled start procedure. |
| Seed advantage | The higher qualifying seed leads by default unless the event document states otherwise. To change the lead/chase order, the higher seed must tell staff before the run order is locked. |
| Run order changes | Staff may adjust qualifying order, battle order, groups or bracket flow for event operations, broadcast timing, technical issues or driver availability. |
| Bracket withdrawal | If a qualified driver withdraws before battles are locked, staff may promote the next eligible qualifier, reseed, create a bye or leave the bracket unchanged depending on timing. |
| Bracket locked | Once the battle bracket is locked, missed battles are normally handled as no-show, bye run or DNF unless staff announces otherwise. |
| Chase jump | The chase driver may leave early and may be ahead before initiation, but must be behind when crossing the initiation point. |
| Lead commitment | The lead driver must initiate at the event-specific point and drive the intended judged line without brake-checking, slowing unexpectedly or trying to manipulate the chase. |
| Wrong order | Staff may reset drivers staged in the wrong lead/chase order before the run starts. After it starts, judges or staff decide whether restart, DNF, or other procedure handling applies. |
| Bracket seeding tie | If two drivers remain tied after qualifying tiebreakers, staff assigns bracket order using available qualifying review, event procedure or random draw. |
| Contact before initiation | Contact before initiation triggers a restart. Repeated or abusive contact can still create further consequences. |
- 01
Bracket
Qualified drivers are placed into the battle bracket.
- 02
Run one
The selected first-run lead driver leads and the other driver chases.
- 03
Run two
Drivers switch roles so each driver has one lead run and one chase run.
- 04
Decision
Judges compare both runs and select a winner or call OMT.
After both runs, each judge votes for Driver A, Driver B or One More Time. The driver with the majority vote wins the battle. If there is no clear majority for a driver, or judges cannot separate the drivers clearly, OMT may be called.
CG-10
Split Format, Standings and Prizes
Some EFVD events use splits for standings, results, or prize eligibility. A split does not change the judged course, bracket procedure, or driving rules. All drivers compete under the same event standards.
See the Financial & Revenue Allocation Guide for the complete payout and revenue policy.
One competition format
All selected drivers run the same layout, attend the same briefing and are judged by the same criteria.
Selected non-licensed drivers
Wild Card drivers can be tracked for split standings, event results and cash prize eligibility when the event offers it.
Licensed Driver standings
Licensed Drivers may have separate standings, priority registration, or payout eligibility where the event format uses them.
| Why EFVD uses splits | What it means |
|---|---|
| Driver review | Selected non-licensed drivers can build event history while sharing the same event environment with licensed drivers. |
| Status review | Wild Card results give staff evidence for future selection and license review. |
| Partner placement | Split standings and prize eligibility create more driver coverage and more options for sponsor activation. |
| Event flexibility | Not every round must use every split. The active split format, standings and prizes are confirmed in that event's Discord announcement or event document. |
| Points structure | Points tables, split standings and championship scoring are published through the event or championship document. Points are provisional until EFVD publishes final results. |
| Championship tiebreakers | If two or more drivers finish the season with the same championship points, EFVD applies the ordered championship tiebreaker list below. |
| Still tied in standings | If earlier championship tiebreakers cannot separate drivers, EFVD may use manual administrative review for prize, bracket, or standings impact before the final alphabetical fallback. |
| Prize ties | If a prize position is tied, EFVD may use the standing tiebreaker order, split the prize where practical or define event-specific handling in Discord. |
| Prize eligibility | DQ, failed technical review, conduct action, no-show, leaving before required review, missing payout details or unavailable winner confirmation can affect prize eligibility. |
| PayPal only | EFVD pays cash prizes in CAD only through PayPal. A PayPal email is optional during application and profile setup. EFVD does not offer an alternate prize payout method. |
| Winner's deadline | A winner must give EFVD a PayPal email linked to an account that can receive CAD within 14 calendar days after the event finishes. Missing this deadline or failing to provide an eligible account forfeits the prize. |
| EFVD issuance period | EFVD will confirm the receiving details with the winner. EFVD will then issue the prize within 14 calendar days. This separate period begins on the date EFVD sends that confirmation. |
| PayPal processing | Processing, holds or account reviews after EFVD issues the payment are outside EFVD's issuance period. An external PayPal delay alone does not forfeit the prize. |
| Country and account limits | Drivers may compete without PayPal, including where receiving is unavailable. EFVD cannot pay a cash prize without a supported receiving PayPal account. |
| Physical prizes | Sponsor prizes, shipping limits, customs, regional restrictions or sponsor terms may affect whether and how a physical prize can be delivered. |
| Prize pool details | When a prize pool is used, its CAD amount, eligibility and sponsor additions are posted in Discord for that event. Cash prizes remain payable in CAD through PayPal only. |
| Default fund split | Unless the event document says otherwise, EFVD may apply the standard 35/25/20/20 allocation described in the Financial & Revenue Allocation Guide. That guide defines which revenue the model covers. |
| No-refund policy | No-show, withdrawal, failed technical review, ban, removal, disqualification, or event cancellation or postponement do not create automatic refunds unless EFVD states otherwise for that event. See the Refund & Withdrawal Guide. |
| Order | Season Championship Tie-Breaking Criteria |
|---|---|
| 1 | Total season points. |
| 2 | Round wins. |
| 3 | Second place finishes. |
| 4 | Third place finishes. |
| 5 | Top 4 finishes. |
| 6 | Top 8 finishes. |
| 7 | Top 16 finishes. |
| 8 | Newest-to-oldest battle finish. |
| 9 | Average qualifying score. |
| 10 | Highest qualifying score. |
| 11 | Second-best qualifying score. |
| 12 | Average line score. |
| 13 | Average angle score. |
| 14 | Average style score. |
| 15 | Final-round qualifying score. |
| 16 | Latest qualifying score. |
| 17 | Manual admin decision. |
| 18 | Alphabetical fallback if still tied. |
Splits affect standings and rewards only. They do not change judging, driving standards, or the main competition flow.
CG-11
Lead and Chase Expectations
Lead driver
The lead driver should run the intended line with strong angle, commitment, controlled transitions and no unnecessary slowing or manipulation.
Chase driver
The chase driver should mirror the lead, maintain proximity safely, show discipline and avoid contact caused by impatience or poor positioning.
| Role | Judges look for |
|---|---|
| Lead | Correct line, angle, pace, zone fill, clean transitions and predictable driving. |
| Chase | Proximity, mimicry, timing, pressure, avoidance, discipline and clean decision-making. |
| Drift procedure | Expected standard |
|---|---|
| Lead pace | The lead must drive a committed, chaseable pace. Brake-checking, parking, abnormal slowing or manipulating the chase can create lead fault. |
| Decel zones | If a decel zone is posted, drivers must follow the event document. Lead cannot abuse decel to trap the chase, and chase must respect posted decel behavior. |
| Normal drift control | Lift, brake and handbrake use are allowed for normal drift control, but not to bait contact, trap the chase or create an artificial advantage. |
| Finish commitment | Drivers are expected to stay in drift and complete the judged course until the finish marker unless staff or judges call otherwise. |
| Chase proximity | Proximity matters only when controlled. Dive-bombing, lunging or forcing contact is chase fault. |
| Inactive chase | A chase driver who falls away, stops applying pressure or abandons the chase can receive major deduction or DNF. |
| Lead runaway | A clean fast lead run is not automatically fault. Abnormal pace, major error or an unchasable lead can create lead fault. |
CG-12
When a Restart Is Given
Restarts are controlled by event procedure, staff and judges. The restart line, when used, is defined in the event Discord document or briefing.
| Situation | Expected procedure |
|---|---|
| Driver stops before restart line | If the event uses a restart line, a driver may stop before that line to trigger a restart procedure. |
| Staff calls restart | Staff or judges may call a restart at any time when the event situation requires it. |
| Contact before initiation | Contact before the initiation point triggers a restart. Contact after initiation is judged under normal lead/chase fault review. |
| Issue before restart point | Staff may allow or call a restart depending on the situation and event flow. |
| Issue after restart point | The run usually continues unless judges or staff call otherwise. |
| Driver mistake | A mistake may still count if judges determine it was a completed judged error rather than a restart situation. |
| Server or technical issue | Staff reviews the issue and decides whether a restart is appropriate. Drivers may rejoin when needed, but must wait for staff direction before returning to live flow. |
| Run count after interruption | Judges decide whether an interrupted run counts, restarts or becomes DNF. Drivers should not assume a rerun until staff or judges confirm it. |
| Restart abuse | Stopping before the restart line without a valid issue, baiting pre-initiation contact, repeated restart requests or using confusion to escape a bad run can lead to DNF or conduct review. |
CG-13
Technical Timeouts and Disconnects
In-game chat is the main live communication channel during official sessions. Discord remains the main place for event documents, group announcements and non-live follow-up.
5-minute request
A driver may request a 5-minute technical timeout. It must be approved by event staff and is not guaranteed.
45 seconds
Drivers have 45 seconds after being called to warm tires, prepare, and position the car at the line unless staff approves otherwise. The driver is ready once positioned at the line.
Follow staff calls
Hold, reset, restart, stop, stage and clear-track instructions may be given through in-game chat or the event's start system.
Consequences possible
Timeout or restart abuse may lead to DNF, removal, conduct review or reduced future selection priority.
| Issue | EFVD handling |
|---|---|
| Disconnect before run | Report immediately. Staff may hold, skip, allow timeout or remove the driver depending on event flow. |
| Disconnect during run | Staff and judges decide whether restart, DNF or other handling applies. Judges may also consider the portion of the run they saw before the disconnect. |
| Lag or desync | Staff may review replay, stream, server context or driver reports. Restart or timeout is possible but not guaranteed. |
| Wheel, pedal or hardware failure | Report the issue to staff immediately. Staff may approve a 5-minute timeout, restart handling, skip, DNF or removal depending on timing and event flow. |
| Mechanical damage | If both cars are affected after contact or a technical issue, both drivers may return to pit when staff allows it. Restart, timeout, DNF or repair handling remains staff/judge discretion. |
| Car issue | If a driver has a car issue, staff may allow them to use another driver's approved car when needed. The selected driver must still drive; substitute drivers are not allowed. |
| Repeated technical issue | Staff may remove the driver from the session to protect event flow, including repeated lag or desync that affects qualifying, battles or broadcast stability. |
CG-14
Passing, Bye Runs, and Results
Passing is not a scored objective in EFVD. It is only valid in a narrow situation: the lead is offline, stopped, spun, heavily slowed or clearly unchasable, and the chase can pass safely on the inside.
| Situation | Expected handling |
|---|---|
| Lead is still chaseable | The chase must stay in position and complete the judged chase. Passing a chaseable lead is not a valid pass and can create chase fault, DNF or conduct review. |
| Lead becomes unchasable | If the lead spins, stops, goes offline, leaves the judged flow or slows abnormally, the chase may pass only when needed to avoid contact or complete the run safely. |
| Inside only | A valid pass must be made on the inside of the lead driver's line. Outside passes, forced passes or passes that create avoidable contact are not valid. |
| Pass completion | A pass is only treated as completed when the chase safely clears the lead and continues the judged course without creating new fault. A partial pass remains part of the chase evaluation. |
| Successful valid pass | If the chase completes a valid inside pass because the lead made the run unchasable, judges may treat the lead run as DNF. |
| After a valid pass | The passing driver must continue cleanly and predictably. They should do so without blocking, brake-checking, or creating new contact. The passed driver must not block, retaliate, or cause contact while recovering. Judges review the full context. |
| Blocking after mistake | A driver who spins, stops, drops offline or loses judged flow must not block, brake-check, crowd or interfere with the other driver. |
| Rejoin near opponent | A driver who leaves the judged course or line must rejoin only when it is safe and predictable. Unsafe rejoin, sudden return to line or contact during rejoin can create fault, DNF or DQ review. |
| Contact during pass | Contact is reviewed for fault, avoidability, timing, inside position and whether the pass was necessary. |
| Opponent DNF | The other driver should continue and complete the run cleanly unless staff or judges call hold, restart or stop. Extra actions after the opponent's mistake can still be judged. |
| Bye run | If an opponent cannot start, staff may require the remaining driver to stage and complete a controlled run, or may waive the run. A required bye run must follow basic course procedure and is not a burnout or show run. |
| Normal double DNF | If both drivers DNF outside an OMT, judges may compare remaining judged value, lead runs and available context, or call OMT when the battle cannot be separated. |
| OMT order | OMT repeats the same lead/chase order unless staff or the event procedure says otherwise. |
| Official results | EFVD may publish official event results after live flow, review or administrative checks are complete. |
| Result corrections | Event staff may correct results, brackets, or standings when needed, even after public posting. Staff has no obligation to change a posted result, and no change is guaranteed. |
| Prize or standing correction | If a correction is made, staff decides whether prizes, standings or public posts are amended. DQ, conduct issues, failed checks or leaving before required review can affect eligibility. |
| Driver withdrawal | A driver who withdraws before qualifying, after qualifying, during battles or after advancing is handled by staff based on event timing, bracket status and communication quality. |
CG-15
DNF and DQ Procedure
DNF and DQ calls protect fair competition and live event flow. Serious or repeated issues may trigger post-event review.
Incomplete or unchasable run
Spin, major off-course, stopped run, wrong procedure, incomplete judged run, or an unchasable lead run.
Matchup penalty
Unsafe conduct, clear procedural violation or repeated battle-impacting issue.
Removal from event
Serious conduct, technical, cheating or repeated procedure violation.
| Course limit issue | Typical handling |
|---|---|
| One or more tire drops | Deduction is based on severity, location, number of tires and effect on line, angle, proximity or battle flow. |
| Two tires off | Usually a major deduction when it affects the judged line, zone fill, proximity or control. |
| Four tires off | Usually DNF or major fault when the car leaves the judged course enough to invalidate the run. |
| Boundary line | If the event document defines a boundary, no-go area or course-limit line, crossing it is judged according to that event's posted consequence. |
| Cone or marker contact | Hitting cones, boards or virtual markers is handled by the event document when specified; otherwise judges consider location, severity and effect on the run. |
| Major off course | May become DNF if the driver leaves the judged course enough to lose the run or create an unsafe rejoin. |
| Unsafe rejoin | Can create DNF, DQ review or fault assignment if it interferes with the other driver or causes avoidable contact. |
| Blocking after lost run | Can create DNF or DQ review even if the original mistake already decided the run. |
- 01
Identify
Judges, event staff, or technical staff identify the issue.
- 02
Confirm
Staff checks run, replay, server context or communication.
- 03
Apply
Live decision is applied to keep the event moving.
- 04
Record
Staff records notes for post-event review if needed.
CG-16
Judging and Collision Review
This guide defines what drivers must do during the event. The Judging Guide defines how judges evaluate mistakes, deductions, contact, OMT and battle advantage.
Restart procedure
Contact before initiation is handled through the restart standard unless staff identifies repeated abuse or unsafe behavior.
Fault review
Contact after initiation is evaluated by judges under the Judging Guide's lead/chase fault standards.
Staff discretion
Desync, server issues or unclear technical contact may be reviewed with replay, stream and event context.
Live decisions control event flow. After the event, a driver may request a Free Judging Clarification. Any eligible paid Live Battle Protest must be submitted by the event's announced deadline under the Protest and Appeal Guide.
CG-17
Attendance, Delays, and No-Shows
Attendance affects event flow, bracket integrity, and future selection. Selected drivers are expected to attend prepared.
| Issue | Possible result | Best action |
|---|---|---|
| No-show with no message | Lower future selection priority or conduct note. | Message staff as early as possible. |
| No separate check-in | EFVD may not require a separate check-in, but no-shows can still affect future approval. | Watch Discord, join with your group, and tell staff early if you cannot attend. |
| Late to briefing | Staff may refuse the driver, require approval to continue or limit procedure review rights. | Show up for briefing. If late or unsure, load in when your group is active and wait for staff direction. |
| Not ready when called | Missed run, DNF or bracket delay. | Stay near staging and watch official calls. |
| Late qualifying arrival | Staff discretion only; missed runs may be lost. | Join with your group and be ready before your run order. |
| Battle no-show | Possible battle DNF or forfeit after the ready window. | Be ready before your battle is called. |
| Repeated delays | Staff review or reduced trust. | Prepare hardware, files and communication before event day. |
| Withdrawal after advancing | Possible forfeit, bye for opponent, bracket adjustment or reduced future selection priority. | Tell staff immediately and do not wait until the next battle is called. |
| Eliminated driver | Drivers may leave once eliminated unless staff asks them to remain. | Confirm you are eliminated and no longer needed before leaving if there is any uncertainty. |
| Podium driver | First, second and third place drivers must remain for the podium ceremony unless staff approves otherwise. | Stay available for a simple podium picture and possible short interview. |
CG-18
Broadcast and Media Rules
EFVD events are public-facing. Drivers should treat broadcasts, replays, and social posts as part of the event presentation.
Keep cars broadcast-ready
Use approved liveries, numbers, decals and clean visual presentation.
Avoid public arguments
Do not use streams, comments or public posts to argue live decisions.
Share responsibly
Highlights are encouraged when they represent the event, drivers and partners properly.
Protect event operations
Do not leak private staff information, internal communication, private event assets, or restricted downloads. Private cars, tracks, and assets cannot be uploaded, repacked, redistributed, or shared outside approved channels.
EFVD may use event content
By applying or entering, drivers understand EFVD may use submitted information, car details, team details, driver identity, country, number, runs, voice, screenshots, and event footage. EFVD may use this material in broadcasts, replays, graphics, social content, website coverage, and partner-facing event coverage.
POV content is allowed
Drivers may stream or record their perspective when it does not disrupt event flow, reveal restricted content improperly or conflict with staff instructions.
Private comms are allowed
Drivers do not need to stay in EFVD voice chat for the full event. They may use private comms with spotters or teammates as long as they remain ready when called.
Request through Discord
Drivers may request spectator, spotter or media access through Discord, but access is not guaranteed and depends on event capacity, broadcast needs and staff approval.
Credit the event
Driver and community edits are welcome when they represent the event properly. Creators are encouraged to tag EFVD social accounts or invite EFVD as a collaborator on Instagram and other platforms when relevant.
Protect sponsor value
Do not attack partners, staff, judges, media or other drivers publicly.
CG-19
Appeals, Clarifications and Conduct
Live arguing slows the event and damages the competition environment. Request a Free Judging Clarification privately after the event. Submit any eligible paid protest by the announced deadline.
- 01
Stay calm
Do not argue with judges during live flow.
- 02
Choose your request
Use a free clarification to request an explanation. Use a paid protest to request an eligible battle-result review.
- 03
Use the right channel
Submit privately through Discord Contact Staff or another route announced by EFVD.
- 04
Accept outcome
Staff review decisions are final for event administration.
A Free Judging Clarification is a request for an explanation and cannot change the result. It does not pause or extend a paid-protest deadline. Full requirements are in the Protest and Appeal Guide.
Public callouts, harassment, sponsor attacks or attempts to pressure staff can create conduct consequences separate from the original decision.
CG-20
Policy Changes
Last updated: August 12, 2026. This guide remains effective until EFVD changes it; it does not expire at the end of a season. Staff announce material rule changes through the official EFVD Discord.