Welcome to the Scarlet Apex 2954, an all weapons enabled combat race. Whether you are here to race, stream, officiate or spectate, it is your support that keeps the Star Citizen community racing events healthy and active. Have fun, be kind to each other and thank you for your interest in the Scarlet Apex.

—EchoBit
ANZIA Racing Committee

This racing guide is intended to provide racers and race officials a standard set of technical regulations which will be adhered to. The term race official refers to race officers, checkpoint observers, race timers, service crew, rescue crew, security and camera operators.

1. Introduction

The Scarlet Apex 2954 is a series of four persistent universe ship combat endurance races where you will race and compete next to 60 players at the same time.

Sign up with a racing team friend or your organization to support each other as you race and battle for glory on the race track and claim your place as ship combat racing legends in the Star Citizen community.

Players of all skill levels are welcome and there is a race for everyone. You do not need to be a racer to participate as there are race official and supporting roles such as refuel & repair crew, salvage debris crew, emergency medical services and security sign up options available for all good Star Citizens.

The event is a unique collaboration of multiple organizations and content creators working together to provide professional livestreams and commentary on the ANZIA Racing Twitch channel, and invites organizations to build racing teams of their own and fly their banners to see which community team is the fastest in the empire.

The race is located at the Sinful Chain community combat race track just outside of Grim Hex, Yela, Crusader in the Stanton System.



1.1 Race Guide Index

2. Race Classes
3. Race Track
4. Race Rules
5. Incidents & Penalities
6. ACRUX Star Award
7. Support Crew
8. Event Security
9. Race Officials

There are supporting roles you can sign up to even if you are not racing.

  Sign Up Forms  ANZIA Discord

2. Race Classes

2.1 Classes

You can participate in all of the racing classes as long as the primary pilots are different when signing up to the Frigate and Carrier class.

You cannot sign up solo. Please use the #looking-for-team Discord chat channel to find team members!

Full Combat Ship Classes

2.1.1 DUO

  • Racing team of 2 single seat ships.
  • Organizations are limited to 2 racing teams maximum.
  • Ship whitelist determined by sign up form.
  • Duo Championship Race is on
  •   DUO Class Sign Up Form

2.1.2 TURRET

  • Racing team of 1 two seated ship. Seating 1 pilot and 1 gunner.
  • Organizations are limited to 2 racing teams maximum.
  • Ship whitelist determined by sign up form.
  • Turret Championship Race is on
  •   TURRET Class Sign Up Form

2.1.3 FRIGATE

  • Racing team of 1 gunship. Seating 1 pilot and up to 7 gunners that can also act as engineers or a team captain.
  • Organizations are limited to 2 racing teams maximum.
  • Ship whitelist determined by sign up form.
  • Frigate Championship Race is on
  •   FRIGATE Class Sign Up Form

2.1.4 CARRIER

  • Racing team of 1 carrier ship and up to 7 snub fighters. Seating 1 carrier pilot and up to 7 snub pilots that can also act as gunners, engineers or a team captain.
  • Organizations are limited to 2 racing teams maximum.
  • Ship whitelist determined by sign up form.
  • Carrier Championship Race is on
  •   CARRIER Class Sign Up Form

2.2 Race Regulations

Scarlet Apex has a detailed set of Racing Rules that must be followed by all participants.

Incidents are observed and recorded by Race Officials and may give you Penalties.

2.3 Event Sequences

To help you plan, these are the sequence of events.

2.3.1 DUO & TURRET Class Sequence

  • Race Preparation, Set Your Spawn
    • At any point before the race, have your regeneration point set to a nearby location in the game.
  • T-1 hour, Discord Event Time and Party Launch
    • Be ready to receive your party invite from the race director in the main menu of Star Citizen.
    • 1 hour before the race begins, or earlier if all participants are in the Star Citizen party, the race director will launch everyone into the game.
    • At this point you will have been given your starting grid position over Discord. All racers must make their way as quickly as possible to the starting grid.
    • If you arrive later than this point in the event you will not be granted entry to the race.
  • T-30 minutes, Race Briefing
    • The race director will brief the racers and officials on what is expected during the event and will take last minute questions you have on Discord.
  • T-10 minutes, Formation Lap
    • 10 minutes before the race begins, the race director and safety ship will coordinate the start of the formation lap to give racers a flying start. When the race director says "Green Flag", your speed can be unrestricted, your weapons are allowed after passing the start line and the race begins.
  • T-0, Race Start
    • The DUO & TURRET races go for 1 hour.
  • T+1 hour, Race End
    • Once exactly 1 hour has passed on the race timer, the overall race leader will set the final lap for the race. This is known as the "White Flag" lap.
    • When the overall leader has crossed the finish line the "Checkered Flag" will be raised, crossing the finish line at this point will end your race.

2.3.2 FRIGATE Class Sequence

  • Race Preparation, Set Your Spawn
    • At any point before the race, have your regeneration point set to a nearby location in the game.
  • T-1 hour, Discord Event Time and Party Launch
    • Be ready to receive your party invite from the race director in the main menu of Star Citizen.
    • 1 hour before the race begins, or earlier if all participants are in the Star Citizen party, the race director will launch everyone into the game.
    • At this point you will have been given your starting grid position over Discord. All racers must make their way as quickly as possible to the starting grid.
    • If you arrive later than this point in the event you will not be granted entry to the race.
  • T-30 minutes, Race Briefing
    • The race director will brief the racers and officials on what is expected during the event and will take last minute questions you have on Discord.
  • T-10 minutes, Formation Lap
    • 10 minutes before the race begins, the race director and safety ship will coordinate the start of the formation lap to give racers a flying start. When the race director says "Green Flag", your speed can be unrestricted, your weapons are allowed after passing the start line and the race begins.
  • T-0, Race Start
    • The FRIGATE race goes for 2 hours.
  • T+2 hours, Race End
    • Once exactly 2 hours has passed on the race timer, the overall race leader will set the final lap for the race. This is known as the "White Flag" lap.
    • When the overall leader has crossed the finish line the "Checkered Flag" will be raised, crossing the finish line at this point will end your race.

2.3.3 CARRIER Class Sequence

  • Race Preparation, Set Your Spawn and Pre-Load Ships
    • At any point before the race, have your regeneration point set to a nearby location in the game.
    • Pre-load unlimited snub ships inside your carrier ship of choice and if you have regeneration capabilities, you are allowed to use it.
  • T-1 hour, Discord Event Time and Party Launch
    • Be ready to receive your party invite from the race director in the main menu of Star Citizen.
    • 1 hour before the race begins, or earlier if all participants are in the Star Citizen party, the race director will launch everyone into the game.
    • At this point you will have been given your starting grid position over Discord. All racers must make their way as quickly as possible to the starting grid.
    • If you arrive later than this point in the event you will not be granted entry to the race.
  • T-30 minutes, Race Briefing
    • The race director will brief the racers and officials on what is expected during the event and will take last minute questions you have on Discord.
  • T-10 minutes, Formation Lap
    • 10 minutes before the race begins, the race director and safety ship will coordinate the start of the formation lap to give racers a flying start. When the race director says "Green Flag", your speed can be unrestricted, your weapons are allowed after passing the start line and the race begins.
  • T-0, Race Start
    • The CARRIER race goes for 2 hours.
  • T+2 hours, Race End
    • Once exactly 2 hours has passed on the race timer, the overall race leader will set the final lap for the race. This is known as the "White Flag" lap.
    • When the overall leader has crossed the finish line the "Checkered Flag" will be raised, crossing the finish line at this point will end your race.

3.
Race Track

Name: Sinful Chain

Location: Miner's Lament, Yela, Crusader, Stanton System

Track Type: 195km NAV/SCM Circuit

Race Type: Combat Endurance Race

Race Objective: Most Laps Wins

//
Track Guide

3.1 Race Objective By Class

  • DUO Class - The team member that places the most laps determines your team's overall result on the podium.
  • TURRET & FRIGATE Class - The ship pilot that places the most laps determines their team's result.
  • CARRIER Class - The carrier ship pilot that places the most laps wins.

4. Race Rules

All racers are expected to have read and understand the rules and technical regulations of the event. Questions regarding the rules and regulations should be presented to the race officials before the event.

4.1 Race Type

Scarlet Apex is a persistent universe full combat all weapons allowed endurance race with the exception of QED weapons which are for race official use only.

The race will have enforced combat zones with the RSI Mantis QED dampener field, a 24km bubble forcing everything in its sphere of influence into [SCM] mode at the Miner's Lament and All Mind's Burn section of the Sinful Chain race track.

Arrive 5 - 15 minutes before the Discord event start time to be on time for your race. The following are the expected durations of each of the events.

  • DUO Championship
    • 1 party formation/setup
    • 1 hour race
  • TURRET Championship
    • 1 party formation/setup
    • 1 hour race
  • FRIGATE Championship
    • 1 party formation/setup
    • 2 hour race
  • CARRIER Championship
    • 1 party formation/setup
    • 2 hour race

Due to the 110 player per server limit, races in the persistent universe will consist of the following party composition.

  • 60x racer/crew slots.
  • The rest will be filled with race officers, service crew, camera operators and security.

4.2 Classifications

The objective is to get the most laps. The pilot that places the most laps determines your team's overall result on the podium.

The ship placed first will be the one having covered the scheduled distance in the shortest time, or, where appropriate, passed the finish line in the lead at the end of the endurance race while on their white flag lap.

All ships will be classified taking into account the number of complete laps they have covered, and for those which have completed the same number of laps, the order in which they crossed the finish line.

Classifications will appear on the live standings after the race director has approved it, or they will be published at the end of the race.

Live classifications include: (DNS) Did Not Start, (DNF) Did Not Finish and (DSQ) Disqualified.

4.3 Flag System

The following flag callouts are utilized by the race directors and officials:

  • "Green Flag"
    Normal racing conditions apply and weapon use is authorized. A green flag is also called at the start of a race.
  • "Yellow Flag"
    Weapon use is no longer authorized. The safety ship is deployed, overtaking is prohibited due to danger on the track. All ships must reduce speed to 100 m/s.
  • "Red Flag"
    Race suspended or stopped due to imminent danger to competitors or spectators, or due to severe technical difficulties.
  • "White Flag"
    The overall race leader is on their final lap, all racers are to continue racing until the checkered flag is called.
  • "Checkered Flag"
    The overall race leader has finished their final lap, racers crossing the finish line complete their race now too.
  • "Black Flag"
    A racer and their team is disqualified and must return to pits immediately.

4.4 Ship Modification & Starting Condition

All racing ships can be modified without restriction.

Ships must start in their fully repaired condition with no broken off parts.

4.4.1 Ship Weapons

All ship weapons and damage types are allowed with the exception of QED weapons which are not allowed and are for race official use only. You can bring a ship with a QED, but it must be powered off for the duration of the event.

4.5 Regeneration Point

Your regeneration point must be set to Grim Hex unless you are racing in Carrier class, only then are you permitted to regenerate on your racing team's ship if it has those facilities.

4.6 Pits

You must call your own hangar every time you want to pit. You may wish to have a key bound for ATC to make it easier to call a hangar.

4.7 Formation Lap

Before the race begins, a partial formation lap will be used to give racers a flying start. Racers will be delivered to the start line led by a safety ship piloted by a race official. When racers are in their designated grid position and race officials are ready to start, the safety ship will begin a partial lap and guide all racers at a fixed speed of 100 m/s to the start line.

Racers will be 2 ships abreast behind the safety ship. The distance you must maintain from the ship in front of you is 500 meters minimum.

The safety ship will break off just before the start line and the race director will ask all ships to maintain course on the track. When the race director says "Green Flag", your speed can be unrestricted and the race begins.

You are authorized to use weapons after you have crossed the start line and only on other racers that have also crossed the start line.

4.8 Flying

Racers must make every reasonable effort to act safely on the track at all times, cause no intentional collisions and may not leave the track without a justifiable reason.

In the event of a major crash of the racers, the safety ship may be called out onto the track by the race director. The race director will call "Yellow Flag" which means all racers must reduce their speed to 100 m/s, combat is not authorized unless otherwise stated by the race director and overtaking is prohibited due to danger on the track. All racers must fly in single file formation to maintain positions.

Race officers, checkpoint observers, race timers, support crew, security and camera operators must stay clear of the path of the racers.

All participants are required to avoid causing incidents. Incidents will be observed and recorded by the race officers, see section Incidents for more details.

In the event of your character's death during the race, briefly voice your RSI Handle and the nature of the incident such as ".. Ship Destroyed", you may respawn and return to the track to rejoin the race.

You must retrieve a ship that is in the same racing class you were previously racing in and then inform the race director with a quick voice message of your RSI Handle and ".. is ready to re-join the race".

4.9 Communications

Simply being part of the ANZIA Racing Discord is enough to participate, the only requirement is to be able to listen to race officer instructions during the race and respond to mentions in Discord chat before and after the race.

Race officers will ensure all participating racers are on their in-game friend list before the event begins. 30 minutes before the event begins the race director or timer will add you to their party and launch everyone participating into a new server.

The race voice channel will enforce Push-To-Talk. When the race has begun, voice priority must be given to the race officers. Racers may briefly respond to the race officers, but should otherwise remain polite and respectful among the combined official and racer voice channel.

Should racers want their own team voice channel, we recommend layering in an additional VoIP application such as your mobile phone, Discord alt accounts, Guilded, TeamSpeak or Mumble to be running at the same time with separate bindings.

Unlimited use ANZIA Racing Discord invite link: discord.gg/anziaracing

4.10 CARRIER Class Rules

Special rules apply during the Carrier Class Championship Race.

  • All crew on a race team, except for the carrier ship pilot, can pilot snub fighters, this is in addition to any other roles they may have such as operating turrets, performing engineering tasks or leading as a team captain.
  • Spare snub fighters are allowed, pre-load as many as your carrier ship physically allows if you like.
  • Regeneration facilities if available on the carrier ship are allowed as well as added regeneration facilities via a parked C8R or Ursa Medivac.
  • Your team must deploy snub fighters within the DEPLOY SNUB ZONE marked on the track map to be flown during the Miner's Lament SCM section of the track.
  • Your team must reclaim all remaining snub fighters active during the Miner's Lament SCM section within the RECLAIM SNUB ZONE marked on the track map before completing the NAV sections.
  • A minimum of 3 deployed and piloted snub fighters are required to cross the start/finish line for a carrier ship's lap to count, and will be observed and counted by the race timers.
  • Deploying and reclaiming snub fighters is not required during the All Minds Burn section of the track.
  • There is no limit to how many snub fighters you can have deployed in an SCM zone, all 7 of your crew can be in snubs if you wish.
  • A team may only reload snub fighters during NAV sections of the race track or at Grim Hex.

4.11 Quantum Travel Racing Rules

Applies to all races and racing pilots.

  • A racing team is allowed [NAV QTM] quantum travel to Grim Hex in a NAV section.
  • Quantum travel back to Miner's Lament and All Minds Burn is not allowed. [NAV FLT] navigation flight operator mode must be used when returning from Grim Hex to the race track.
  • Race teams must rejoin the race track through the last checkpoint of Miner's Lament.

5. Incidents & Penalities

Incidents will be reviewed by the ANZIA Racing Committee using all available race footage recordings and race timing data.

We encourage racers to record their own footage as it will be helpful in determining how desync and other issues affected the incident, but it's not mandatory.

If any incident that prompts you to press criminal charges, do not press charges against anyone in the event.

5.1 Types of Incidents

5.1.1 Incorrect Starting Location

Any of the penalties will be imposed on any racer who is judged to have left the starting grid area and their starting position.

5.1.2 Off Track

The track limit is defined on the track map. A racer is defined to have left the track limits if:

  1. The race director deems that the racer has strayed too far from the course.
  2. The race director or race officers are unable to locate the racer on the course.
  3. The racer flies into the infield section of the track.
  4. The racer does not maintain the specified line into the pit lane.

In the event of the above, the race director or an officer will issue a warning to the racer and direct the racer to rejoin the track limits. Continued violations may result in further penalties at the discretion of the race director and the officers. Details of penalties available to the race director to issue are noted in the penalties section.

5.1.3 Skipping Track

Racers are expected to navigate the course described by the track map. Each mandatory checkpoint must be navigated through end to end.

Failure to do so can result in the following penalties being issued by the race directors and their officers:

  1. A warning to the racer.
  2. The racer will be directed to repeat the checkpoint again and only after safely rejoining the track when other racing traffic has passed.
  3. The racer will be issued with a "pit lane pass through" which means they must serve extra time using the pit lane on their next lap.
  4. Continued violations may result in further penalties at the discretion of the race director and the officers. Details of penalties available to the race director to issue are noted in the penalties section.

5.1.4 Ship Collision

Racers are expected to fly with care and consideration for other racers. All classes are expected to give enough room to other ships on the racing line.

Please avoid the following:

  1. Not allowing other racers sufficient space to maintain their racing line.
  2. Racing in a manner which forces others into the physical barriers on the track, referred to as squeezing.
  3. Intentionally colliding with other racers.
  4. Maneuvering your ship in such a manner to block the racing line to intentionally force a collision.
  5. Pressing criminal charges against anyone in the race.

Penalties for such actions will be at the discretion of the race director and will depend on the severity of the incident in question. Details of penalties available to the race director to issue are noted in the penalties section.

5.1.5 Ship Destroyed

During the race, an accident may result in your ship being destroyed. In such an event, you will be able to rejoin the race as long as you can reclaim/retrieve your ship or a backup. The ship you retrieve must be of the same racing class you were racing in previously.

When rejoining the race, follow the pit lane in the direction of the race track and enter the track when it is safe to do so to continue your race.

If you are unable to retrieve your ship and are unable to continue (or do not wish to continue) please inform the race director and you will be marked as (DNF) Did Not Finish. If the ship was destroyed as part of a ship collision incident, penalties will be given to the offending ship at the discretion of the race director and race officers.

5.1.6 Weapon Abuse

Improvised weapons such as loose objects ejected from ships and Vanduul ship melee weapons are not permitted in this race.

Penalties for such actions will be at the discretion of the race director and will depend on the severity of the incident in question. Details of penalties available to the race director to issue are noted in the penalties section.

5.2 Reporting of Incidents

Racers and officials are able to report race incidents to the race director which may have breached the rules of the event or created an incident. Reporting during the event should follow this format:

  1. The player should communicate the incident briefly over the ANZIA Racing Discord voice chat or in the #incident-reports channel.
  2. The report should start with the ship / team / pilot who is reporting the incident then followed by the offending ship / team / pilot and nature of the incident and if possible the location of the incident. If submitted after the race, any of your own recorded footage (e.g. Team A, reports Team B for causing an intentional accident at the start/finish line).

Incidents are assessed by the race director and officers. Incidents will be assessed during the race and an appropriate action will be taken (details noted in the penalties section). Incidents can also be reviewed after the event. If penalties are applied for these incidents, a time penalty will be imposed on the racer's final race time.

If it is determined by the officials that no incident occurred or if there is a lack of evidence regarding the incident, no action will be taken.

A log of reported incidents and the actions taken will be made available after the race.

Decisions made by the race director during the race are final and must be followed by the affected participants. If not followed, additional penalties including disqualification can be applied.

Incidents that are the result of servers (desync) are unfortunately not able to be easily addressed and will be seen as a racing incident.

5.3 Penalties

The following penalties are available to the race director and officers. These penalties can be applied at their discretion.

5.3.1 Warning

A racer can be warned regarding their actions and reminded of the rules. If the racer receives multiple warnings, additional penalties can be applied. They are usually caused by small errors or unintentional breaches of the rules.

5.3.2 Repeat Checkpoint

Issued when a racer has skipped a mandatory checkpoint. If issued significantly after the mandatory checkpoint has been passed the racer will be asked to pass through the entire checkpoint twice (in a circle on the inside of the circuit). If unable to be completed before the end of the race an appropriate time penalty per class will be applied to the racer's finishing time.

5.3.3 Pit Lane Pass Through

The racer will be asked to to pass through the pit line and not make a pit stop. If unable to be completed before the end of the race an appropriate time penalty per class will be applied to the racer's finishing time.

5.3.4 Stop Go Penalty

The racer will be directed to hold position at the re-join officer and will only be allowed to continue the race on the direction of the race director or re-join officer. Time for this penalty will be determined by the nature of the incident and at the discretion of the officials.

5.3.5 Disqualification

Only used as a last resort. If a racer has shown a complete disregard for the rules they will be issued with a disqualification (DSQ).

5.3.6 Ship Disable

Used by race officials if a racer has breached the rules of armistice with Weapon Abuse.

5.4 Server Incidents

In the event of a replication layer server transfer failure (30000 Error or "30K") during the race, the race director will call "Red Flag" and the race will be restarted from scratch based on available race data. Race restarts due to 30Ks are limited to 3. If the race 30Ks for a third time, the current race will be rescheduled for another time.

6. ACRUX Star Award

6.1 CRUX Star Award

A CRUX Star is a unique award at ANZIA Racing, they represent the four brightest stars in the southern cross star constellation in the southern hemisphere of Earth. Only one team and consistent players in that team are awarded a CRUX Star every year. They are awarded to the fastest team and best combat pilots or drivers after they have placed the highest in all relevant competitions and designated classes that year. The requirements to earn a CRUX Star award follow.

  • ACRUX Star, place highest in:
    • Crux Cup, ACRUX Class
    • Scarlet Apex, DUO Class
  • GACRUX Star, place highest in:
    • Sim Cup, ACRUX Class
  • MIMOSA Star, place highest in:
    • Mountains of Mayhem, TECHNICAL Class
    • Anti-Gravity Racing League, ICARUS Class
  • IMAI Star, place highest in:
    • Sim Cup, ICARUS Class

7. Support Crew

The support crew team will be made of the following composition:

  • 4x Refuel/Repair Pit Crew
    Starfarer Pit Crew Teams
  • 4x Emergency Medical/Rescue Services
    First Responder C8R or Cutlass Red Crew
  • 6x Salvage Tractor Debris Crew
    Reclaimer/SRV Ship Tractor Operators

7.1 Track Limits

All support crew must only fly around the track limits out of the way of the racing line unless it is absolutely necessary for their job to go into the path of racers.

7.2 Refuel/Repair Pit Crew

Logistical and service minded players may volunteer for the pit crew role and must provide unbiased refueling service to racers only in the fastest time possible.

Refueling Pit Crew must sign up together as a team of two with one of them owning a MISC Starfarer. Three Starfarers maximum are allowed in the field at one time and must park hovering just off pit lane.

Players can request their services by joining the Refuel voice channel to contact them.

7.3 Emergency Medical/Rescue Services

Medical and rescue minded players may volunteer for the EMS/EMT crew role and must provide unbiased medical and rescue assistance to participants of the event in the fastest time possible. An ANZIA EMS Director will assist with triage and dispatch management.

Emergency Medical/Rescue Service players can sign up solo or as a team of two and must own a ship with a medical bed such as the Anvil C8R or Cutlass Red.

Players can request their services by joining the EMS voice channel to contact them.

7.4 Salvage Tractor Debris Crew

Salvage and tractor operator players may volunteer for the debris crew role and must help clear ship debris from the track when it is safe to do so and with notification to the ANZIA Salvage Director.

Ship Tractor Crew sign up as solo ship operators that must own a ship with at least one S2 or S3 tractor beam such as an ARGO SRV, Vulture, 315p or as an Aegis Reclaimer team of two.

Players can request their services by joining the Salvage voice channel to contact them.

7.5 Role Go/No Go Check

While it is our intention to include new roles for the event such as Starfarers to refuel, there will be a go/no go check before the race begins to determine if their gameplay mechanics are fit for service in the race. If volunteer teams are given the no go signal, they will still be invited into their designated role positions as a presence in the race itself for the experience and show of readiness and still get shoutouts on stream!

7.6 ANZIA Director Authority

Three ANZIA Racing appointed Directors of Refuel, Salvage and EMS will be appointed to provide guidance and leadership to all organizations participating in the event.

Organizations and their supporting players should ask their relevant directors for help if they are unsure where to be or how they can help.

8. Event Security

The security team will be made of the following composition:

  • Any amount of Fighter and/or Multi-Crew Ships they wish to bring as the race defense crew. Organizations fill remaining server slots in the event.

8.1 Security

Combat and defense minded organizations may volunteer for event security and must provide radar intelligence to each other and communications with unauthorized players entering the event space. They must also bring top tier PvP skill and combat meta optimized spacecraft.

8.2 ANZIA Security Director Authority

One ANZIA Racing Security Director will be appointed to provided guidance and leadership to all organizations participating in the event.

Organizations and their players should ask the ANZIA Security Director for help if they are unsure where to be or how they can help.

9. Race Officials

The race official team will be made of the following composition:

  • 4x Race Director
    Above Track Position/Time Observer
  • 4x Race Officers
    Checkpoint Observers
  • 4x Race Camera Operators
    PoVs for Dedicated Streamers, Shoutcasters

9.1 Record of Positions and Times

A minimum of two race officials must video record the event to help track racer positions.

  1. A view of the entire track and pits from above to observe/record party markers.
  2. On the start/finish line to record the line itself.

9.2 Record of Incidents

Race officers are required to video record their assigned checkpoints.

9.3 QT Re-join Marker

One race officer will be assigned as the QT Re-join Marker for the event location for rejoining the race from a spaceport or further away via quantum travel.