Welcome to the Anti-Gravity Racing League 2955. 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.

—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 ultimate team based gravlev tournament returns with a brand new format, fresh racing classes to choose from and all set on the beautiful Spectra Ocean Dream Circuit. Many of us are Wip3out, BallisticNG, Wave Race and Jet Moto fans! 💖💙🤍

Our gravlev races are the gold standard sim-like racing experience you can have in Star Citizen. You can expect to see the largest racing teams formed and a professional livestream to create an unforgettable event.

  Get ready to Sign Up!   Join the ANZIA Event Discord

1.2 🎃 Jakodin's Guide to Gravlev

ASTER is a limited combat gravlev race that pits the Mirai Pulse versus the Origin X1 Force in an epic racing battle across the Spectra Ocean Dream Circuit.

Anyone can sign up to the ASTER combat race. It is not mutually exclusive with any other race.

📅

2.1 Race Track

The ASTER race will be the Spectra Ocean Dream Circuit, a community race track located at Winner's Circle in Arena Commander Free Flight.

Top 10 Pulse / X1 Force Leaderboard

Spectra Ocean Dream Circuit SCR.gg Leaderboard

2.2 Race Team

You must sign up and participate as a team of 2 racers. Each of your team members must race in at least 1 of the 2 races.

Your team's combined laps and race time will form your team's overall result on the final standings.

2.3 Race Regulations

This race has a detailed set of Race Rules that must be followed by all participants.

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

It is your responsibility as a racer to learn the rules, types of incidents and understand how to serve penalties if they come up in the competition.

2.4 ASTER Event Sequence

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

  • Race Preparation
    • Ensure your primary race craft, components and any spare craft are ready to go in Arena Commander.
  • Race Start T-30 minutes, Discord Event Start Time
    • Be ready to receive your lobby invite from the race director in the main menu of Star Citizen.
    • The race director will launch everyone into the game as soon as possible.
    • 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.
  • Race Start T-15 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-0, Race #1 Start
    • The first endurance race will go for 30 minutes.
  • T+30 minutes, Race #1 End
    • Once exactly 30 minutes 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.
  • T+1 hour, Race #2 Start
    • The second endurance race will go for 30 minutes.
  • T+1 hour 30 minutes, Race #2 End
    • Once exactly 30 minutes 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.5 ASTER Racing Class

ASTER is made of gravlev chassis that have pros and cons in combat racing. Each gravlev chassis must be raced by a team at least once in the event, the order of the gravlev chassis is up to the race team.

2.5.1 ASTER Bike Whitelist

Origin X1 Force

1985 REC Cost
206ms Speed
S1x1 Shield
S1x1 Weapon
2820HP Hull

Mirai Pulse

2779 REC Cost
203ms Speed
S1x0 Shield
S2x1 Weapon
1550HP Hull
Craft profile renders by StarJump Fleetviewer
FEISAR is an amateur non-combat gravlev race of the Drake Dragonfly series, Consolidated Outland Hoverquad and Origin X1 at the Spectra Ocean Dream Circuit.

FEISAR is mutually exclusive with ICARUS so that pro and amateur racers are split between these races.

📅

3.1 Race Track

The FEISAR race will be the Spectra Ocean Dream Circuit, a community race track located at Winner's Circle in Arena Commander Free Flight.

Top 10 Dragonfly / Hoverquad / X1 Force Leaderboard

Spectra Ocean Dream Circuit SCR.gg Leaderboard

3.2 Race Team

You must sign up and participate as a team of 3 racers. Each of your team members must race in at least 1 of the 3 races.

Your team's combined laps and race time will form your team's overall result on the final standings.

3.3 Race Regulations

This race has a detailed set of Race Rules that must be followed by all participants.

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

It is your responsibility as a racer to learn the rules, types of incidents and understand how to serve penalties if they come up in the competition.

3.4 FEISAR Event Sequence

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

  • Race Preparation
    • Ensure your primary race craft, components and any spare craft are ready to go in Arena Commander.
  • Race Start T-30 minutes, Discord Event Start Time
    • Be ready to receive your lobby invite from the race director in the main menu of Star Citizen.
    • The race director will launch everyone into the game as soon as possible.
    • 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.
  • Race Start T-15 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-0, Race #1 Start
    • The first endurance race will go for 30 minutes.
  • T+30 minutes, Race #1 End
    • Once exactly 30 minutes 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.
  • T+1 hour, Race #2 Start
    • The second endurance race will go for 30 minutes.
  • T+1 hour 30 minutes, Race #2 End
    • Once exactly 30 minutes 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.
  • T+2 hours, Race #3 Start
    • The third endurance race will go for 30 minutes.
  • T+2 hours 30 minutes, Race #3 End
    • Once exactly 30 minutes 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.5 FEISAR Racing Class

FEISAR is made of the slowest gravlev chassis. Each gravlev chassis must be raced by a team at least once in the event, the order of the gravlev chassis is up to the race team.

3.5.1 FEISAR Bike Whitelist

Origin X1

1588 REC Cost
206ms Speed

Consolidated Outland Hoverquad

851 REC Cost
199ms Speed

Drake Dragonfly

5141 REC Cost
189ms Speed
Craft profile renders by by StarJump Fleetviewer
ICARUS is a professional non-combat gravlev race of the Origin X1 Velocity, Mirai Pulse LX and Aopoa Nox at the Spectra Ocean Dream Circuit.

ICARUS is mutually exclusive with FEISAR so that pro and amateur racers are split between these races.

📅

4.1 Race Track

The ICARUS race will be the Spectra Ocean Dream Circuit, a community race track located at Winner's Circle in Arena Commander Free Flight.

Top 10 X1 Velocity / Pulse LX / Nox

Nox, 0h 6m 28s 499ms by JellyHeadMade

Nox, 0h 6m 29s 587ms by GentlemanJez

Nox Kue, 0h 6m 29s 600ms by Jakodin

Nox Kue, 0h 6m 31s 216ms by EchoBit

Nox, 0h 6m 31s 274ms by Dude3D

Nox Kue, 0h 6m 33s 100ms by DieuNightsman

Nox Kue, 0h 6m 33s 590ms by H3rbie

Nox Kue, 0h 6m 34s 583ms by LensNation

Nox, 0h 6m 35s 289ms by Boltok

Nox, 0h 6m 39s 620ms by MasterSun

Spectra Ocean Dream Circuit SCR.gg Leaderboard

4.2 Race Team

You must sign up and participate as a team of 3 racers. Each of your team members must race in at least 1 of the 3 races.

Your team's combined laps and race time will form your team's overall result on the final standings.

4.3 Race Regulations

This race has a detailed set of Race Rules that must be followed by all participants.

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

It is your responsibility as a racer to learn the rules, types of incidents and understand how to serve penalties if they come up in the competition.

4.4 ICARUS Event Sequence

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

  • Race Preparation
    • Ensure your primary race craft, components and any spare craft are ready to go in Arena Commander.
  • Race Start T-30 minutes, Discord Event Start Time
    • Be ready to receive your lobby invite from the race director in the main menu of Star Citizen.
    • The race director will launch everyone into the game as soon as possible.
    • 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.
  • Race Start T-15 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-0, Race #1 Start
    • The first endurance race will go for 30 minutes.
  • T+30 minutes, Race #1 End
    • Once exactly 30 minutes 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.
  • T+1 hour, Race #2 Start
    • The second endurance race will go for 30 minutes.
  • T+1 hour 30 minutes, Race #2 End
    • Once exactly 30 minutes 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.
  • T+2 hours, Race #3 Start
    • The third endurance race will go for 30 minutes.
  • T+2 hours 30 minutes, Race #3 End
    • Once exactly 30 minutes 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.

4.5 ICARUS Racing Class

ICARUS is made of the fastest gravlev chassis. Each gravlev chassis must be raced by a team at least once in the event, the order of the gravlev chassis is up to the race team.

4.5.1 ICARUS Bike Whitelist

Aopoa Nox

10844 REC Cost. The Aopoa Nox Kue (13013 REC Cost) is also allowed and a mutually exclusive chassis choice with the Aopoa Nox.
224ms Speed

Origin X1 Velocity

1787 REC Cost
221ms Speed

Mirai Pulse LX

3176 REC Cost
218ms Speed
Craft profile renders by StarJump Fleetviewer

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

5.1 Race Type

The race types are as follows.

  • ASTER
    • Team Based Limited Combat Race
  • FEISAR
    • Team Based Non-Combat Race
  • ICARUS
    • Team Based Non-Combat Race

In Arena Commander, if there is any need to repair or refuel, racers simply respawn in the simulation.

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.

  • Track Day
    • 3 hour practice session
  • Qualifying Race
    • 15 minute lobby formation/setup
    • 30 minute ASTER race
    • 15 minute lobby formation/setup
    • 30 minute FEISAR race
    • 15 minute lobby formation/setup
    • 30 minute ICARUS race
  • ASTER Combat Championship
    • 15 minute lobby formation/setup
    • 30 minute ASTER race #1
    • 15 minute lobby formation/setup
    • 30 minute ASTER race #2
  • FEISAR Amateur Championship
    • 15 minute lobby formation/setup
    • 30 minute FEISAR race #1
    • 15 minute lobby formation/setup
    • 30 minute FEISAR race #2
    • 15 minute lobby formation/setup
    • 30 minute FEISAR race #3
  • ICARUS Professional Championship
    • 15 minute lobby formation/setup
    • 30 minute ICARUS race #1
    • 15 minute lobby formation/setup
    • 30 minute ICARUS race #2
    • 15 minute lobby formation/setup
    • 30 minute ICARUS race #3

Races in Arena Commander will consist of the following party composition.

  • 10x official slots.
  • 12x racer slots.

5.2 Race Team

Race teams are required for this competition.

3 racers make a team with the exception of ASTER which is made up of 2 racers. All team members must have raced at least once in the event in a vehicle of their own.

All racers must have decided on a racing team name.

5.3 Vehicle Restrictions

In order to promote fairness for all players in the prized tournament, vehicles only available on the pledge store are banned until they are available for purchase in-game with aUEC or REC.

Promotion limited vehicles have the same performance characteristics as their freely available counterparts are an exception to this rule. Specifically, limited vehicles that are allowed for use include the Drake Dragonfly Starkitten.

5.4 Vehicle Modification

All vehicles can be modified without restriction with the exception of ASTER's X1 Force which may only equip the K&W CF-117 Bulldog Repeater as its primary weapon.

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

5.5 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/anziaracing

5.6 Flag System

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

  • "Green Flag"
    Normal racing conditions apply. A green flag is also called at the start of a race.
  • "Yellow Flag"
    Overtaking is prohibited due to danger on the track. All vehicles must reduce speed using strafe down and forward combined.
  • "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.

5.7 Starting Formation Lap

The race will begin by using a formation lap to give racers a flying start. Racers will self deliver to the start line. When racers are in their designated grid position and race officials are ready to start, the vehicle in pole position will begin a partial lap and guide all racers at a fixed speed govened by their strafe down and forward input to the start line.

Racers will be single file formation. The distance you must maintain from the vehicle in front of you is 200 meters minimum.

All vehicles must maintain course on the track during the formation lap. When the race director says "Green Flag", your speed can be unrestricted and the race begins.

The ASTER combat race is under armistice (no weapons allowed) until they have passed Checkpoint 4 and the race is under the Green Flag. Armistice resumes when you finish your race.

5.8 Driving

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 and must pass when it is safe to do so.

In the event of a major crash the race director will call "Yellow Flag" which means all vehicles must reduce their speed to the combined strafe down and forward speed of the bike and overtaking is prohibited due to danger on the track. All racers must drive in single file formation to maintain positions.

Everyone that isn't racing 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 vehicle that is whitelisted for the race and then inform the race director with a quick voice message of your RSI Handle and ".. re-joined the race".

5.9 Classifications

The objective is to get the most laps as a team. The team that places the most combined laps and shortest race time determines your team's overall result on the podium.

The vehicle placed in 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 race while on their white flag lap.

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

5.10 Starting Grid Position

Arena Commander starting grids will be based on your qualifying results.

A qualifying period will be held for SCR.gg submissions as well as a qualifying race to improve your starting position in the races as a team. Placement on the championship grid will be determined by your team's combined lap times of the SCR.gg qualifying period as the first tier of the start grid. A second tier of qualifying position can be earned by competing in a live qualifying race.

  • Tier 2 Qualifying Position (Start Grid Front Half)
    • Compete in both the SCR.gg Qualifying Period and the Live Qualifying Race.
  • Tier 1 Qualifying Position (Start Grid Back Half)
    • Compete in one of either the SCR.gg Qualifying Period or the Live Qualifying Race.

5.11 Qualifying

Qualifying has the following requirements:

  1. Both team members must post a valid SCR.gg time trial submission to the Spectra Ocean Dream Circuit leaderboard or participate in a live qualifying race in a vehicle whitelisted for their race in order to progress their team to the championship race.
  2. If any time trial submission is determined invalid in SCR.gg through dispute and then reviewed and confirmed by the ANZIA Racing Committee as invalid, a grid starting penalty may be applied before a championship race begins.
📅 Qualifying Closes -

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

6.1 Types of Incidents

6.1.1 Incorrect Starting Location

Any of the penalties will be imposed on any racer who is judged to be out of place before the standing start countdown from the race director is given.

6.1.2 Off Track

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

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

6.1.4 Vehicle Collision

Racers are expected to drive with care and consideration for other racers.

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 vehicle in such a manner to block the racing line to intentionally force a collision.

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.

6.1.5 Vehicle Destroyed

During the race, an accident may result in your vehicle being destroyed. In such an event, you will be able to re-join the race via the re-join lane.

6.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 driver 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 / driver who is reporting the incident then followed by the offending ship / team / driver 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.

6.3 Penalties

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

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

6.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 once again. 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.

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

6.3.4 Stop Go Penalty

The racer will be directed to hold position off track near the start / finish line 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.

6.3.5 Lap Count Skipped

Only used as a last resort. If a racer has ignored race direction calls.

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

6.4 Server Incidents

In the event of a 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.

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

  • 24hr CRUX Team Star
    • Place 1st as a team in a 24hr race.
  • ACRUX Star
    • Place highest in Persistent Universe ship races in a year.
  • GACRUX Star
    • Place highest in Arena Commander ship races in a year.
  • MIMOSA Star
    • Place highest in Persistent Universe ground races in a year.
  • IMAI Star
    • Place highest in Arena Commander ground races in a year.

8. Race Officials

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

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

8.1 Record of Positions and Times

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

8.2 Record of Incidents/Cheating/Griefing

All race officials are required to stream or video record their assigned checkpoints and point of views.

⚠️

Cheating in the game, crashing this event or griefing in Arena Commander private lobbies in the Star Citizen Alpha is not permitted, and not welcomed in this non-combat racing event. You will be reported by all the race participants and officials with multiple perspectives of your actions to Cloud Imperium Games.

For clearly defined key points on this, please refer to the official Cloud Imperium Games Rules of Conduct.

Rules of Conduct  Terms of Service  Reporting Player Misconduct