Welcome to the Crux Cup 2954. Whether you are here to race, crew, 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 Crux Cup.

—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, support crew, security and camera operators.

1. Introduction

The Crux Cup 2954 is a series of four persistent universe ship races throughout the month of March.

All races are located at Lorville city, Hurston in the Stanton System.

The event welcomes any ship and skill level by providing multiple racing classes to choose from and is a truly multi-class racing experience where everyone races at the same time.

The racing series encourages teamwork and comradery with sign ups for racing teams of 2 and supporting roles for refuel/repair pit crew, medical/rescue services, salvage debris crew and security roles to achieve a fun social experience, safe racing environment and successful racing result for all Star Citizens.

It 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 or lone wolf racer is the fastest in the empire.

The two main competition races the ProGP Race, also known as Class Group A and the OpenGP, also known as Class Group B. The other two races more casual, they are the DeliveryGP Race, also known as Class Group C and LuxuryGP Race, also known as Class Group D.

You can sign up to support any of the four events you are not racing in.

  Crux Cup 2954 Sign Up Form

If you are signing up to the race please fill out the Sign Up Form and join the race event Discord.

  ANZIA Racing Discord Invite

1.1 Race Event List

  • ProGP (mutually exclusive with OpenGP if you are a racer)
The ProGP race is for professional racers, also known as "Class Group A". It is one of the two main competition races, it is limited to the fastest ships and dedicated racing ships and has 3 highly competitive racing class speed tiers to choose from within. You will see everything from the outlier Drake Herald with the highest top speed to Razors and M50s battling it out in the hands of the most skilled pilots in the game.
  • OpenGP (mutually exclusive with ProGP if you are a racer)
The OpenGP race is for amateur racers, also known as "Class Group B", it is one of the two main competition races, and has 3 racing classes that cater to three popular racing styles. The Open racing class allows all other ships so you can race your favourite ship. The Aurora racing class races RSI Auroras only, competitive in its own right where everyone is racing at the same speed. The Heavy racing class is for industrial, logistic and capital ship pilots to prove who is the fastest large ship racer.
Anyone can sign up to this fun race. It will set at the community race track "Super Dragon Tofu Run", a long delivery point A to B race course set from one end of the Lorville outskirts and city trenches to the other. You can sign up as a team of 2 and have the choice of three racing speed classes from the Mirai Furys, Anvil Hornets and the tofu delivery Anvil C8X Pisces.
Anyone can sign up to this fun race. It is a unique collaboration with the Yacht Club community where we will challenge all Star Citizens to race their favourite luxury ship, 890J, 600i, 400i and Constellation Phoenix. Owners of these ships can offer them up in the sign up process for professional racers to pilot and race for their captains, or have a friend race their ship or race it themselves!



2. ProGP

ProGP and OpenGP races are mutually exclusive with each other, so you can only sign up one or the other of the two main races, however anyone can sign up to the DeliveryGP (Class Group C) and LuxuryGP (Class Group D) races.

2.1 ProGP, Class Group A

The ProGP is a 1 hour ship endurance race at the Gold Dust community made race track.

There are three Classes you can enter:

ProGP, Class Group A

  • ACRUX (Herald only)
  • AX2 (Razor Base/EX/LX, 350r, P-72/P-52 and M50)
  • AX3 (Mustang Gamma/Omega)

You can fly solo or in a team of 2 racers in this race.

2.2 Race Regulations

The ProGP has a detailed set of Endurance Race Rules that must be followed by all participants.

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

2.3 Event Sequence

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

2.3.1 T-1 hour, Set Your Spawn and Attend Event Briefing

Arrive 1 hour early to the race and have your regeneration point set to a nearby location in the game.

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.

At this point you will be given your starting grid position over Discord. If you arrive later than this point in the event you will not be granted entry to the race.

2.3.2 T-45 minutes, Building the Star Citizen Party

Be ready to receive your party invite from the race director in the main menu of Star Citizen.

2.3.3 T-30 minutes, Party Launch

30 minutes before the race begins, or earlier if all participants are in the Star Citizen party, the race director will launch everyone into the game. All racers must make their way as quickly as possible to the starting grid.

2.3.4 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 and the race begins.

2.3.5 T-0, Race Start

The endurance races go for 1 hour.

2.3.6 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.

3. OpenGP

ProGP and OpenGP races are mutually exclusive with each other, so you can only sign up one or the other of the two main races, however anyone can sign up to the DeliveryGP (Class Group C) and LuxuryGP (Class Group D) races.

3.1 OpenGP, Class Group B

The OpenGP is a 1 hour ship endurance race at the Gold Dust community made race track.

There are three Classes you can enter:

OpenGP, Class Group B

  • OPEN (Any other ship not in a dedicated racing class)
  • AURORA (Aurora only)
  • HEAVY (See allowed ship list)

You can fly solo or in a team of 2 racers in this race.

3.2 Race Regulations

The OpenGP has a detailed set of Endurance Race Rules that must be followed by all participants.

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

3.3 Event Sequence

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

3.3.1 T-1 hour, Set Your Spawn and Attend Event Briefing

Arrive 1 hour early to the race and have your regeneration point set to a nearby location in the game.

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.

At this point you will be given your starting grid position over Discord. If you arrive later than this point in the event you will not be granted entry to the race.

3.3.2 T-45 minutes, Building the Star Citizen Party

Be ready to receive your party invite from the race director in the main menu of Star Citizen.

3.3.3 T-30 minutes, Party Launch

30 minutes before the race begins, or earlier if all participants are in the Star Citizen party, the race director will launch everyone into the game. All racers must make their way as quickly as possible to the starting grid.

3.3.4 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 and the race begins.

3.3.5 T-0, Race Start

The endurance races go for 1 hour.

3.3.6 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.

4. DeliveryGP

4.1 DeliveryGP

The DeliveryGP is a rally leg time trial at the Super Dragon Tofu Run community made race track.

There are three Classes you can enter:

DeliveryGP, Class Group C

You can fly solo or in a team of 2 racers in this race.

4.2 Race Regulations

The DeliveryGP has a detailed set of Rally Race Rules that must be followed by all participants.

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

4.3 Event Sequence

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

4.3.1 T-1 hour, Set Your Spawn and Attend Event Briefing

Arrive 1 hour early to the race and have your regeneration point set to a nearby location in the game.

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.

At this point you will be given your starting grid position over Discord. If you arrive later than this point in the event you will not be granted entry to the race.

4.3.2 T-45 minutes, Building the Star Citizen Party

Be ready to receive your party invite from the race director in the main menu of Star Citizen.

4.3.3 T-30 minutes, Party Launch

30 minutes before the race begins, or earlier if all participants are in the Star Citizen party, the race director will launch everyone into the game. All racers must make their way as quickly as possible to the designated rally parking area.

4.3.4 T-0, Rally Start

Each racing team will be called one at a time every minute and sent down the course.

4.3.5 Rally End

When all teams have completed their run down the course, the rally event concludes.

5. LuxuryGP

5.1 LuxuryGP

The LuxuryGP is a 1 hour ship endurance race at the Gold Dust community made race track.

You can offer up one ship, there are four luxury ships you can pick from:

LuxuryGP, Class Group D

You can fly solo or in a team of 2 (yacht captain and pilot in the same ship) in this race.

5.2 Race Regulations

The LuxuryGP has a detailed set of Endurance Race Rules that must be followed by all participants.

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

5.3 Event Sequence

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

5.3.1 T-1 hour, Set Your Spawn and Attend Event Briefing

Arrive 1 hour early to the race and have your regeneration point set to a nearby location in the game.

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.

At this point you will be given your starting grid position over Discord. If you arrive later than this point in the event you will not be granted entry to the race.

5.3.2 T-45 minutes, Building the Star Citizen Party

Be ready to receive your party invite from the race director in the main menu of Star Citizen.

5.3.3 T-30 minutes, Party Launch

30 minutes before the race begins, or earlier if all participants are in the Star Citizen party, the race director will launch everyone into the game. All racers must make their way as quickly as possible to the starting grid.

5.3.4 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 and the race begins.

5.3.5 T-0, Race Start

The endurance races go for 1 hour.

5.3.6 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.

6. Endurance Race Rules

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

6.1 Classes

You must decide on a race class to participate in.

6.1.1 ACRUX

This is a ProGP Class Group A racing class. The ACRUX class is limited to the Drake Herald only, signing up to this class means you’re serious about competing for the fastest lap times in this ship and must meet a 2 minute 15 second lap time minimum during a practice or qualifying session. ACRUX racers are considered the fastest in the empire and are expected to have highly optimized setups and ship modifications.

6.1.2 AX2

This is a ProGP Class Group A racing class. The AX2 class is a dedicated racer ship class with a limited selection of ships, signing up to this class means you're serious about competing for the fastest lap times in these ships and must meet a 2 minute 30 second lap time minimum during a practice or qualifying session. AX2 racers are considered the fastest in the empire and are expected to have highly optimized setups and ship modifications.

AX2 Class Whitelist

  • Kruger Intergalactic P-52 Merlin
  • Kruger Intergalactic P-72 Archimedes
  • Mirai Razor
  • Mirai Razor EX
  • Mirai Razor LX
  • Origin 350r
  • Origin M50

6.1.3 AX3

This is a ProGP Class Group A racing class. The AX3 class is a dedicated racer ship class with a limited selection of ships, signing up to this class means you’re serious about competing for the fastest lap times in these ships and must meet a 2 minute 45 second lap time minimum during a practice or qualifying session. AX3 racers are considered the fastest in the empire and are expected to have highly optimized setups and ship modifications.

AX3 Class Whitelist

  • Consolidated Outland Mustang Gamma
  • Consolidated Outland Mustang Omega

6.1.4 OPEN

This is a OpenGP Class Group B racing class. The OPEN class accepts all other ships that are not in dedicated racing classes, the ship must be able to complete at least one lap of the track under its own power. You must also place a single lap in the qualifying race to progress to the championship race. OPEN class racers are not expected to be the fastest, it is a great opportunity for anyone that just wants to fly something fun around the track and set some unique track records.

6.1.5 AURORA

This is a OpenGP Class Group B racing class. The AURORA class is restricted to RSI Aurora ES/CL/MR/LX/LN model ships only. The AURORA class is competitive in its own right making it a good choice for anyone that enjoys the challenge of flying the same speed as other racers. Most citizens took their first spaceflight in the RSI Aurora, it is recommended for those new to ship racing. You must place a single lap in the qualifying race to progress to the championship race.

6.1.6 HEAVY

This is a OpenGP Class Group B racing class. The HEAVY class is for those industrial, logistic and capital ship pilots who want to prove they are the fastest of their profession and best at handling the working class or largest ships of the empire. You must place a single lap in the qualifying race to progress to the championship race.

HEAVY Class Whitelist

  • Aegis Reclaimer
  • ARGO Mole
  • ARGO Mole Carbon
  • ARGO Mole Talus
  • ARGO MPUV Cargo
  • ARGO MPUV Personnel
  • ARGO Raft
  • Drake Caterpillar
  • Drake Caterpillar Pirate
  • MISC Hull A
  • MISC Hull C

6.1.10 LUXURYGP

Ships available to be raced in the LuxuryGP, Class Group D are as follows.

LUXURYGP Class Whitelist

  • Origin 890J
  • Origin 600i
  • Origin 400i
  • Constellation Phoenix

6.2 Location

The Crux Cup 2954 ProGP, OpenGP and LuxuryGP is held at Gold Dust, a fan made race tracks at Lorville, Hurston in the Stanton System. It will be held on the latest LIVE patch of Star Citizen. The race will be launched in the USA region. All participants are advised to land at Everus Harbor, Hurston on a USA server to minimize issues with spawning into a bad location.

6.3 Gold Dust

Gold Dust is made up of 6 mandatory checkpoint buildings around Lorville City. Racers must fly through all the designated checkpoints and will be observed by race officers. If you crash inside a checkpoint and survive, look for racing traffic, safely rejoin the track when all traffic has passed and continue on until the race officer observing the mandatory checkpoint issues you a penalty that you must complete on your next lap.

6.3.1 Gold Dust Track Map

6.4 Type

The race type for Crux Cup 2954 ProGP, OpenGP and LuxuryGP will be an endurance race. Endurance races will make use of a nearby spaceport to refuel your ship mid-race and introduce pit strategy to your racing.

Endurance races will be multi-class where all classes race together on the track at the same time. Classes will be positioned on the starting grid from fastest at the front to slowest at the back.

6.5 Duration

Endurance race durations will be 1 hour. Due to the nature of traversing Star Citizen, arrive 1 hour early to your race to ensure you do not miss the start.

6.6 Capacity

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

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

6.7 Teams

Race teams are allowed and encouraged to give racers a better chance at surviving through a game crash or in-game crash. 2 racers maximum make a team. All team members must be present on the track for the race in a racing ship of their own and must race in the same racing class. All racers, even if solo, must have decided on a racing team name.

6.8 ProGP & OpenGP Starting Grid Position

Two track days and one qualifying race will be held before the championship race. Placement on the championship grid will be determined by fastest lap time of the qualifying race. If both racers are unable to attend the qualifying race, as long as they have placed a lap during a track day, they will be put at the back of the grid for the championship.

6.9 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. Smaller ships must allow larger ships to maintain their racing line and may pass when it is safe to do so.

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 ships must reduce their speed to 150m/s 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, you may respawn and return to the spaceport to rejoin the race. You must retrieve the a ship that is in the same racing class you were previously racing in and then inform the race director when you are flight ready as outlined in incident: Ship Destroyed.

6.10 Starting Formation Lap

The race will begin by using a formation lap to give racers a flying start. Racers will be delivered to the start line by a leading safety ship piloted by a race officer. 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 150m/s to the start line.

Racers will be 2 ships flying in vertical formation above and below 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.

6.11 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.

You must land inside your hangar when you are ready to leave and then leave the hangar immediately as the doors begin to close to reset the hangar for the next racer. Flying away from a hangar without landing can result in a Stop Go penalty because it is important to reset the hangar for the next racer to use.

6.12 Classifications

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 1 hour 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.

6.13 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: https://discord.gg/h2feszV

6.14 Flag System

The following flag callouts are utilized by the race director:

  • "Green Flag"
    Normal racing conditions apply. A green flag is also called at the start of a race.
  • "Yellow Flag"
    The safety ship is deployed, overtaking is prohibited due to danger on the track. All ships must reduce speed to 150m/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 has set the final lap, remaining racers must cross the finish line and end the race.
  • "Checkered Flag"
    The overall race leader has finished their final lap, remaining racers crossing the finish line complete their race too.
  • "Black Flag"
    A racer and their team is disqualified and must return to pits immediately.

6.15 ProGP & OpenGP Qualifying

The ProGP and OpenGP qualifying races will match the format of the championship race with the following additions:

  1. At least one team member is required to place a lap in a track day or qualifying race to progress all team members to the championship race.
  2. Your fastest lap in the qualifying race will set your qualifying time.
  3. You can join the session midrace, advise the race director to be guided in.
  4. Setting a qualifying time will lock you into your chosen class and ship for the championship race.
  5. If a racer incurs a penalty during this session, an additional penalty of grid placement reduction can be applied at the discretion of the race director.

6.16 Ship Modification & Starting Condition

All ships can be modified without restriction, but must start in their fully repaired condition with no broken off parts.

6.17 Racer Regeneration Point

Racers must set their regeneration point to Everus Harbor, the low orbit station above Lorville. The only exception is the 890J owners taking part in the LuxuryGP who must spawn their ship at Teesa Spaceport, Lorville City instead.

7. Rally Race Rules

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

7.1 Classes

You must decide on a race class to participate in.

7.1.1 ULTRA INSTINCT

This is a DeliveryGP, Class Group C racing class. The Ultra Instinct racing class is limited to the Mirai Fury LX, Fury MX and Fury.

ULTRA INSTINCT Class Whitelist

  • Mirai Fury LX
  • Mirai Fury MX
  • Mirai Fury

7.1.2 SUPER DRAGON

This is a DeliveryGP, Class Group C racing class. The Super Dragon racing class is limited to the Anvil F7C Hornet, F7C-R Hornet Tracker, F7C Hornet Wildfire, F7C-S Hornet Ghost, F7C-M Super Hornet and F7A Hornet Mk.II (supporting the one or two players that have this ship).

SUPER DRAGON Class Whitelist

  • Anvil F7C Hornet
  • Anvil F7C-R Hornet Tracker
  • Anvil F7C Hornet Wildfire
  • Anvil F7C-S Hornet Ghost
  • Anvil F7C-M Super Hornet
  • Anvil F7A Hornet Mk.II

7.1.3 TOFU RUNNER

This is a DeliveryGP, Class Group C racing class. The Tofu Runner racing class is limited to the Anvil C8X Pisces, C8R Pisces and C8 Pisces.

TOFU RUNNER Class Whitelist

  • Anvil C8X Pisces
  • Anvil C8R Pisces
  • Anvil C8 Pisces

7.2 Location

The Crux Cup 2954 DeliveryGP is held at Super Dragon Tofu Run, a fan made race tracks at Lorville, Hurston in the Stanton System. It will be held on the latest LIVE patch of Star Citizen. The race will be launched in the USA region. All participants are advised to land at Everus Harbor, Hurston on a USA server to minimize issues with spawning into a bad location.

7.3 Super Dragon Tofu Run

The Super Dragon Tofu Run is a challenging point A to B sprint through the outskirts and trenches of Lorville City. Racers must fly through all the designated checkpoints and will be observed by race officers. If you crash along the course and survive, look for racing traffic, safely rejoin the track when all traffic has passed and continue on.

7.3.2 Super Dragon Tofu Run Track Map

7.4 Type

The race type for Crux Cup 2954 DeliveryGP will be an rally race. Rally races are long challenging point A to B races that will require you to follow a complex track to complete successfully. It is recommended to have a good understanding of the track by watching our track video guide.

Rally races have multiple classes which act as speed tiers but they do not race at the same time. Rally racers will be directed to park in a designated area near the start of the course. Teams will be called one at a time to be sent down the course by the race director.

7.5 Duration

Rally race durations will be as long as there are teams to sent down the course. Due to the nature of traversing Star Citizen, arrive 1 hour early to your race to ensure you do not miss the start.

7.6 Capacity

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

  • 60x racer slots with support for unlimited racers that may dynamically join as teams complete their runs.
  • The rest will be filled with race officers, service crew, camera operators and security.

7.7 Teams

Race teams are allowed and encouraged to give racers a better chance at surviving through a game crash or in-game crash. 2 racers maximum make a team. All team members must be present on the track for the race in a racing ship of their own and must race in the same racing class. All racers, even if solo, must have decided on a racing team name.

7.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.

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 run, you cannot rejoin the track to continue, you only get one attempt.

7.9 Classifications

The team placing first in the rally will be the team with a racer that completed the course with the fastest lap time. The team's fastest racer determines the teams overall placement.

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.

7.10 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: https://discord.gg/h2feszV

7.11 Ship Modification & Starting Condition

All ships can be modified without restriction, but must start in their fully repaired condition with no broken off parts.

7.12 Racer Regeneration Point

Racers must set their regeneration point to Everus Harbor, the low orbit station above Lorville.

8. Incidents

Incidents will be reviewed through the combined race official video footage, streamed footage and other material evidence and will be judged by the race director and race officers.

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.

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

8.1 Types of Incidents

8.1.1 Incorrect Starting Location

Any of the penalties will be imposed on any racer who is judged to have broken the formation lap before the "Green Flag" signal from the race director is given.

8.1.2 Off Track

The track limit is defined on the track map as the "white line". The track also includes the pit lane defined as the "red line". 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 officiers 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.

8.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.

8.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 (use right bracket only).

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.

8.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, go to the designated re-join officer for the session and await their instructions to enter the track 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.

8.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 pilot 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.

8.3 Penalties

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

8.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.

8.3.2 Repeat Checkpoint

Issued when a racer has skipped a mandatory checkpoint such as a tunnel archway. 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.

8.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.

8.3.4 Stop Go Penalty

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

8.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).

8.4 Server Incidents

In the event of a server crash (30000 Error or "30K") during the race, the race director will call "Red Flag" and the race will be restarted from scratch based on qualifying/practice times. 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.

9. Race Officials

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

  • 1x Race Director
    Above Track Position/Time Observer
  • 5x Race Officers
    Checkpoint Observers
  • 4x Race Camera Operators
    PoVs for Dedicated Streamers, Shoutcasters
  • 6x Refuel/Repair Pit Crew
    Starfarer Pit Crew Teams
  • 8x Salvage Tractor Debris Crew
    Reclaimer/SRV Ship Tractor Operators
  • 6x Emergency Medical/Rescue Services
    First Responder C8R or Cutlass Red Crew
  • Security
    Fighter and Multi-Crew Race Defense Crew (Fill remaining slots)

In addition to this, a couple VoIP only race official helpers will assist with individual technical issues, lengthy guidance and moderation of the main event channels.

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 and tunnel itself.

9.2 Record of Incidents

Race officers are required to video record their assigned checkpoints.

9.3 Pit Hangar Management

The Spaceport Pit Observer will be there to observe racers and assist the race director with hangar related reporting and incidents.

9.4 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.

9.4 Refuel/Repair Pit Crew

Logistical and service minded players may volunteer for the pit crew role and must provide unbiased refuelling 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.

9.5 Emergency Medical/Rescue Services

Medical and rescue minded players may volunteer for the EMS/ERS crew role and must provide unbiased medical and rescue assistance to participants of the event in the fastest time possible.

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.

9.6 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 race director.

Ship Tractor Crew sign up as solo ship operators that must own an ARGO SRV or as an Aegis Reclaimer team of two. Four SRV/Reclaimer maximum are allowed in the event at once time and must only fly around the track limits out of the way of the racing line.

9.7 Security

Combat and defense minded players may volunteer for the security role 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.

9.8 Role Go/No Go Check

While it is our intention to include new roles for the event such as Starfarers to refuel racers, 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!