# EFVD Competition Guide | Qualifying & Tandem Battles > EFVD competition guide covering event rules, qualifying, battles, restarts, DNF, DQ, and judging basics. Canonical URL: https://driftcomp.com/docs/competition-guide/ Public Guide # Competition Guide. Know the rhythm of event day, the calls that matter, and what it takes to reach the final battle. - 01Apply to Compete - 02Selected - 03Briefing - 04Qualifying - 05Top 32 - 06Results Guide contents ## Sections - CG-01Purpose and Event Philosophy - CG-02Quick Event Flow - CG-03Before Event Day - CG-04Event Rules and Server Standards - CG-05Driver Briefing and Communication - CG-06Start Line and Staging Procedure - CG-07Initiation Procedure - CG-08Qualification Format - CG-09Battle Format - CG-10Championship Format, Standings and Prizes - CG-11Lead and Chase Expectations - CG-12Restarts and Restart Point Procedure - CG-13Technical Timeout, Signals and Disconnects - CG-14Passing, Bye Runs and Results - CG-15DNF, DQ and Disqualification Procedure - CG-16Judging Reference and Collision Links - CG-17No-Show, Delay and Attendance Policy - CG-18Broadcast and Media Rules - CG-19Appeals, Clarifications and Conduct - CG-20Policy Changes CG-01 ## Purpose and Event Philosophy Welcome to EFVD. This guide explains how to prepare, qualify and compete in tandem battles, with clear expectations for every driver. Licensed Drivers and Wild Cards share the same course, judging standards and respectful competition environment. Start with the event flow below, then use the section links when you need a rule. The New Driver Guide covers joining and setup; the Financial Guide covers entry prices and prizes. ### Open competition with standards Drivers apply through #driver-application in Discord. 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 drama or repeated procedure issues. ### Selection is discretionary EFVD may refuse or remove an entry for conduct, preparation, technical issues, false information or event fit. Staff and organizers from other active competitions may participate in EFVD. EFVD may restrict participation or access where conflicts of interest, confidentiality concerns or competitive-integrity concerns arise. Core rule: compete hard, follow procedure, respect staff and keep the event moving. CG-02 ## Quick Event Flow This is the short version of event day. Use the detailed sections below when you need procedure, edge cases or rule references. Standard event times are Eastern Time (America/Toronto), including daylight saving time. Driver briefing begins at 9:30 AM; qualifying begins at 10:00 AM. Top 32 briefing starts 90 minutes after qualifying ends. Battles start 30 minutes after Top 32 briefing (120 minutes after qualifying ends). The battle start time may vary with qualifying duration. Event Ops confirms the exact times in Discord when the full qualifying session ends; check My EFVD for the schedule and follow staff announcements. Session Timing Mandatory driver briefing 9:30 AM Qualifying starts 10:00 AM Top 32 driver briefing 90 minutes after qualifying ends Battles start 30 minutes after Top 32 briefing (120 minutes after qualifying ends); start time may vary The 90-minute gap after qualifying covers results, bracket preparation, server changes and any staff-authorized Top 32 practice. Top 32 briefing begins after that gap; battles start 30 minutes later. Practice duration is not guaranteed. The gap begins when the full qualifying session ends, not when your own group finishes; stay available and follow staff calls. - 01Open My EFVDConfirm your current event, release dates, registration, car, payment, qualifying group and next action. - 02Follow the launcherJoin when your group is called. The Join button shows Waiting for your group while another group is on track and Qualifying done after your group finishes. - 03Stage correctlyUse the posted start position, start-light app and staff instructions. - 04QualifyComplete official solo runs in the posted order. - 05BattleTop qualified drivers run lead/chase matchups, usually targeting Top 32 when possible. - 06Follow live decisionsJudges decide during live flow. After the event, request a Judging Clarification if needed. Submit any eligible protest by the event's announced deadline. CG-03 ## Before Event Day Before event day, check My EFVD for your entry status and deadlines. Use the EFVD Launcher to install event files, check your setup and see when to join. Before the event Schedule rule Licensed registration opens The date and time published by Event Ops. Wild Card registration opens 7 days after licensed registration opens. Registration closes 15 days before the driver briefing (24 hours before the car deadline). Car deadline 14 days before the driver briefing. Track release 72 hours before the driver briefing (normally 9:30 AM). Event Cars release Defaults to track release; follow the separately published release time when one is set. Wild Card payment deadline Defaults to 7 days before the driver briefing, after the car deadline. Event Ops may publish a different time. Refund deadline Closes when the event cars and track are released together (Round 1 for a License pass). Event Cars default to the track release time, but Event Ops may set a separate release. My EFVD shows the exact event deadlines in your local time. These are elapsed-time offsets, so a daylight saving change during event week can shift the local clock time of an earlier deadline. ### Open My EFVD Check your schedule, file release dates, qualifying group and next step. ### Read the Judging Guide Know the judged course expectations, tandem standards, DNF examples, OMT process and decision procedure. ### Prepare event files Use the EFVD Launcher to install the track and event cars when they are released. Check My EFVD for release times. ### 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 Check My EFVD for your qualifying group once it is announced. ### Join when called Open the EFVD Launcher. Join when your group is called; while another group is on track, the Join button shows Waiting for your group. ### Be ready at staging Be near staging, wheel setup ready and prepared to 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. Check My EFVD, complete the launcher checks and follow the joining instructions. Follow any direct instructions from event staff. 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 to confirm they can connect, load content and run without major issues. Competition-server warm-up Drivers may warm up on the competition server only during the staff-authorized warm-up period. There is no fixed or guaranteed duration; event staff may end the period at any time. Warm-up period closed When staff ends warm-up, stop driving immediately and follow instructions to clear the track. Do not return to the track unless staff reopens warm-up. Rejoining the server does not reopen the warm-up period. Live event restrictions No practice runs, burnouts, donuts or test hits during live qualifying or battles unless staff expressly authorizes them. Practicing outside staff-authorized practice time, including continuing or returning after practice closes, can lead to disqualification (DQ). Private event content Cars, tracks, downloads and event assets must be treated as private unless EFVD states otherwise. Uploading, repacking, redistributing, leaking or sharing event content 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, tech, conduct or evidence concerns, EFVD may hold a driver from continuing, pause prize eligibility or keep results provisional while staff reviews the issue. 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 Approved car and livery changes are announced on Discord if applicable for that event. Drivers should not assume changes are allowed unless staff posts them. Settings Staff may adjust server settings for stability, broadcast operations or technical reasons. Platform or tool failure If Assetto Corsa, Content Manager, Discord, server tools, start systems, scoring tools or broadcast systems fail, 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, results remain provisional, the event resumes later or the round is voided. Minimum participation EFVD may require a minimum number of eligible drivers for an event, championship, payout or points result to count. Minimums may be confirmed in the event document. CG-05 ## Driver Briefing and Communication Briefing is mandatory because 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 Event times posted in Discord use Discord timestamp formatting so each driver can view the schedule in their local time. The event server is hosted on the east coast of North America. Apply to Compete In #driver-application, apply to join EFVD or resume your saved step. My EFVD Your profile, event entry, car status, payment, schedule and next step. Contact Staff Private help with applications, registration, car-tech, payments, evidence, protests, appeals and other 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 conflict, the event document controls first, then driver briefing, then live staff instruction, then 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 Director 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. Community staff Community moderation, announcements, tickets, community reports and non-live communication. Escalation area Who handles it Judging confusion The Head of Judges controls the judging process. The Competition Director handles final event-administration calls when needed. Event procedure confusion Event staff controls live flow. The Competition Director resolves unresolved operational conflicts. Conduct or drama Community staff or event staff contain the issue first. The Competition Director handles final discipline or escalation. Technical issue Event staff handles live flow. Technical staff or the Competition Director 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. The Competition Director may apply future approval, selection or conduct notes. Driver briefing and the official event document control round-specific procedure for that event. If they differ from a general public guide, follow the event document and staff briefing. Drivers are responsible for following event flow, watching group announcements and being ready when called. Drivers who miss briefing may lose priority, be refused by staff, require approval to continue, or lose the ability to challenge a procedure issue they missed in briefing. If a driver is late but unsure whether they can still run, they should load in when their group is active and wait for staff direction. CG-06 ## Start Line and Staging Procedure EFVD uses Start Lights by DaZD on VOSAN for official runs. Install and test it before event day; the EFVD Launcher can install or repair it. ### 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, settle, prepare mentally and position the car at the line unless event staff approves otherwise. Once the car is positioned at the line, staff will consider the driver ready. ### 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 Procedure The initiation point, initiation type and judged reference markers are event-specific and 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. Initiation must be one committed drift initiation into the judged course. Three-point initiations, stacked feints, dragging the car straight past initiation, or using multiple direction changes to delay commitment are not permitted unless the event briefing specifically allows a different technique. Chase drivers may jump the start and be ahead before initiation, but must be behind when crossing the initiation point. The chase is expected to be in drift by the required initiation marker and must not use the start to force contact or create artificial advantage. Repeated early movement, forced contact, deliberate disruption or failure to be behind at initiation may lead to 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 Multiple steering inputs, feints or direction changes used to avoid committing at the marker can be treated 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, but line, angle, zones, clips and tandem advantage are judged from initiation onward. CG-08 ## Qualification Format Drivers normally receive two non-consecutive qualifying runs. The best valid score is used for ranking. If the event document posts a different qualifying or tiebreak procedure, that event document 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 highest valid qualifying score from a driver's best run sets the driver's qualifying position. First-run bonus For the current championship format, the top three first qualifying runs earn 3, 2 and 1 championship bonus points respectively; fourth and below earn 0. Qualifying and bracket positions still use the best of both runs. Previously recorded results are unchanged. First-run bonus ties Equal first-run scores are separated by the official qualifying order using the tiebreakers below. Each bonus place is awarded once. Run 2 affects this bonus only when resolving equal first-run scores. Bonus eligibility The default bonus ranking includes all entrants. Wild Cards keep their place but receive no championship points, and their bonus is not passed down. Any licensed-only bonus ranking must be specified in the championship document. 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 into the battle bracket. EFVD normally uses a Top 32 bracket when event size allows it, but 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. If the higher seed wants to change the lead/chase order, they must advise 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 If drivers stage in the wrong lead/chase order before the run starts, staff may reset them. If the run starts, judges or staff decide whether restart, DNF or 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. - 01BracketQualified drivers are placed into the battle bracket. - 02Run oneThe selected first-run lead driver leads and the other driver chases. - 03Run twoDrivers switch roles so each driver has one lead run and one chase run. - 04DecisionJudges 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 ## Championship Format, Standings and Prizes Licensed Drivers and Wild Cards compete together in the same events under the same driving and judging standards. Licensed Drivers activate their three-event registration with a $40 CAD License pass; Wild Cards register and pay $15 CAD separately for each event. Only Licensed Drivers earn championship points and championship prizes. Wild Cards remain eligible for event podium prizes. Payment does not influence driver selection, technical decisions or judging, and does not guarantee a Top 32 position. ### One competition format All selected drivers run the same layout, attend the same briefing and are judged by the same criteria. ### Event results and podium payouts Selected non-licensed drivers receive individual event results and can earn an announced event payout by finishing on the podium. Wild Card drivers do not earn championship standings or championship payouts. ### Championship standings and payouts Only Licensed Drivers are eligible for championship standings and championship payouts. Why EFVD runs championships 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 Event podiums and Licensed Driver championship standings create more driver coverage and sponsor activation options. Event flexibility Individual event payouts and Licensed Driver championship payouts are confirmed in the event's Discord announcement or event document. Points structure Only Licensed Drivers earn championship standings and points. The points table 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 championship tiebreakers still cannot separate drivers before the final fallback, EFVD may use manual admin review for prize, bracket or standing impact. 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. Prize amounts and payment See the Financial Guide for confirmed prizes, PayPal requirements and payment deadlines. Refund policy Registration is fully refundable before the published withdrawal deadline. Late withdrawals and no-shows are not refundable; a missed event does not create a partial License pass refund. See the Refund & Withdrawal Guide for event changes and other terms. 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. Simple version: the championship is an extra results and rewards layer. It does not make the driving easier, change judging, or separate drivers from 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 ## Restarts and Restart Point Procedure 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 May still count against the driver if judges determine the issue is a completed judged mistake 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 Timeout, Signals 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 mentally and position the car at the line unless staff approves otherwise. Once positioned at the line, the driver is considered ready. ### 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 participant'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. Role after pass After a valid pass, the passing driver must continue cleanly and predictably. The passed driver must not block, retaliate or create contact while recovering. 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. After the pass The passing driver should continue cleanly without blocking, brake-checking or creating new contact. Judges review the full context of both drivers' actions. 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 edits Event staff reserve the right to correct results, brackets or standings when needed, even after public posting, but there is no obligation or guarantee that a posted result will be changed. 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, DQ and Disqualification Procedure DNF and DQ calls protect fair competition and live event flow. Serious or repeated issues may trigger post-event review. Unauthorized practice on the competition server can lead to event disqualification (DQ), including continuing to practice or returning to the track to practice after staff closes the practice window. See CG-04: Event Rules and Server Standards. ### Run not completed or not chasable Spin, major off-course, stopped run, wrong procedure, incomplete judged run or a lead run that is not chasable. ### 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. Unsafe vehicle condition DNF the run if the car is unsafe to continue or seriously obstructs the driver's view, such as driving with the hood raised or continuing while the car is visibly on fire. The driver should stop safely and notify staff; staff or judges may review the incident and decide whether further action is needed. Blocking after lost run Can create DNF or DQ review even if the original mistake already decided the run. - 01IdentifyJudges, staff or tech identify the issue. - 02ConfirmStaff checks run, replay, server context or communication. - 03ApplyLive decision is applied to keep the event moving. - 04RecordStaff records notes for post-event review if needed. CG-16 ## Judging Reference and Collision Links This guide defines what drivers must do during the event. The Judging Guide defines how judges evaluate mistakes, deductions, contact, OMT and battle advantage. Did contact happen before initiation? Staff reviews the start behavior. Repeated or abusive contact can receive a further note or review. Did the touch materially change line, proximity, control or the outcome? - No: light, controlled contact may be incidental, with no major fault. - Yes: judges review closing speed, available space, lead movement and avoidability to establish fault. - Unclear or technical: staff reviews replay, stream and server context for shared fault, desync or technical issues. Then → Judges decide the deduction, DNF, battle result, restart, OMT or technical handling under the Judging Guide. Contact type alone does not decide the result. Interference after a DNF-level mistake can still receive further review. See JG-11: Collision Review for the full standards. ### 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 Judging Clarification. Any eligible Live Battle Protest must be submitted by the event's announced deadline under the Protest and Appeal Guide. CG-17 ## No-Show, Delay and Attendance Policy Attendance affects event quality, bracket integrity and future selection. If you register and get selected, staff expects you to attend prepared. Issue Possible result Best action No-show with no message Lower future selection priority or conduct note. Withdraw in My EFVD or message staff as early as possible. Withdrawn in My EFVD Not a no-show, even after the refund deadline (the combined car-and-track release). Withdraw as early as you can so another driver can take your place. No check-in process 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 competition content. Drivers should treat broadcasts, replays and social posts as part of the event presentation. EFVD takes preventive measures to protect competition car files, but cannot guarantee that leaks will not occur. EFVD cannot be held responsible for unauthorized leaks or distribution of those files. ### 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 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 during the full event and may use private comms with spotters or teammates, as long as they remain ready when called. ### 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 Judging Clarification privately after the event. Submit any eligible protest by the announced deadline. - 01Stay calmDo not argue with judges during live flow. - 02Choose your requestUse a Judging Clarification to request an explanation. Use a Live Battle Protest to request an eligible battle-result review. - 03Use the right channelSubmit privately through Discord Contact Staff or another route announced by EFVD. - 04Accept outcomeStaff review decisions are final for event administration. A Judging Clarification is a request for an explanation and cannot change the result. It does not pause or extend a 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 EFVD announces material changes through its official Discord before the affected registration opens. Related guides ## Read next. These pages fill in the rest of the EFVD process without repeating the same explanation here. ### Judging Guide How runs and battles are scored. ### Protest and Appeal Guide How to handle reviewable issues privately. ### Refund & Withdrawal Guide What happens if a driver withdraws, fails tech or misses an event.