The Crux Cup Stellar Endurance Championships are the gold standard in spaceship endurance sim racing and one of the best social community experiences that you can have in Star Citizen.

Crux Cup SEC invites organizations to build racing divisions, fly their banners and colours, to raise up and support individuals to compete, and score points across multiple grand prix for a spot on the top 15 interstellar champions leaderboard, also known as "The Godly Fifteen" , proving their pilots are the fastest in the empire and esport racing legends.

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. If you want to be part of this event team, start participating as an organization or content creator on the ANZIA Racing event Discord.

1.1 Event Index

  Get ready to Sign Up!   Join the ANZIA Event Discord

Grand Prix #1

Crux Cup SEC Grand Prix #1 is for talented pilots to fly the Mirai Razor in a highly competitive 2 hour endurance race of the Super Dragon Tofu Run. It's a chance at earning the title "The Dragon of Lorville" and becoming a member of the legendary racer club "The Godly Fifteen" , earning the club's name as a title for proving you are one of Star Citizen's elite pilots. This race runs in parallel with the Delivery Challenge #1 amateur racing competition.

The Grand Prix #1 race is mutually exclusive with its amateur racing competition equivalent Delivery Challange #1, but signing up to this race puts you in the running for the best prizes and rewards.

2.1 Race Track Grand Prix #1

"A popular family run restaurant, Super Dragon, delivered tofu and carafi cube noodles out of the Lorville industrial outskirts. Unbeknownst to the father, a son and daughter practiced their flying skills with the C8X Pisces delivery ship. The two later signed up to and raced in what would become the Crux Cup Stellar Endurance Championships."

The Grand Prix #1 race track will be the Super Dragon Tofu Run , a community race track located at Lorville, Hurston in the Stanton System. The track is 258.6 km in length and will use the red race ship line on the map.

2.2 Race Track Video Guide Grand Prix #1

2.3 Ship Whitelist Grand Prix #1

Mirai Razor

Only the base Razor is allowed. The Razor EX & LX variants are not permitted.

2.4 Sign Up Grand Prix #1

You must sign up and participate as a solo racer.

You can optionally specify an organization, community or group you wish to represent when signing up.

2.5 Qualifying Grand Prix #1

You must post a time trial during the global time trial period for this Grand Prix. Post your time trial to the Super Dragon Tofu Run SCR.gg community leaderboard in the Mirai Razor.

🐞 Bug Notice: Quantum boosting is currently being staged in the game and some of the data that unrestricts top speed (kills NAV mode) are allowing ships to have very high top speeds in atmosphere. It is the ANZIA Racing Committee's recommendation Quantum Travel to the nearby low orbit station, to set your Engine Pips to maximum, toggle your landing gear down/up in space, then fly back down to the race track using thruster flight only to get the best possible speed for your time trials! For more information, see STARC-171777 on the Issue Council.

The following speeds produced by the unrestricted top speed from this bug should be considered normal for this competition. The speeds of 465~/600~ m/s on Super Dragon Tofu Run, and 390~/520~ m/s on NB//GHOST (~varies due to wind direction) are the approximate speeds (+/-20 m/s) you want to achieve in the Mirai Razor to know you have the setup correct.

Time trial posts that appear on the "Top 30 Time Trials Grand Prix #1" leaderboard below are correctly posted within the scheduled global time trial period and will be counted as time trial qualification entries. The top 30 time trials will receive personal invitations to the live regional qualifying races, sorted as close to their region as possible.

A live qualifying race is a 2 hour endurance race where the most laps and shortest time across the finish line win. Of the 30 players who race in the live qualifying races, only the top 15 of the live qualifying standings will progress to and be offered entry into the main grand prix race.

Top 30 Time Trials Grand Prix #1

Pos/Player	Time/Craft	Video

Open Full Leaderboard

2.6 The Dragon of Lorville Grand Prix #1

The player who places first place in Grand Prix #1 main race will earn the title "The Dragon of Lorville" and the following rewards.

• "Dragon of Lorville" Discord role and badge of honour.
• Special mention in the #hall-of-stars historical race records.
• A free physical transparent "Dragon of Lorville" sticker.
• Access to the 4K resolution artwork of the icon for use anywhere in edited media or future decal system if it comes up officially or through game mods.

This award is earned once per year, is non-repeatable and will be passed onto the next player without this award in subsequent competitions.

2.7 The Godly Fifteen Grand Prix #1

Players who make it into the top 15 of a Grand Prix main race will become part of an elite racing legend club called "The Godly Fifteen". They will earn themselves the club name as a title recognized by the Star Citizen racing community, and as a badge of honour in ANZIA's Discord. They will also receive physical items to display or wear proudly for having achieved entry to such a prestigious and high skill race. The rewards are as follows.

• "The Godly Fifteen" Discord role and badge of honour.
• A free limited edition "The Godly Fifteen" Stellar Endurance Championships t-shirt with your RSI Handle, logo and favourite racing number customized on it. Earned once per year.
• A free physical transparent "The Godly Fifteen" sticker. Earned once per year.
• Access to the 4K resolution artwork of the icon for use anywhere in edited media or future decal system if it comes up officially or through game mods.
• Special mention in the #hall-of-stars historical race records.
• Access to "The Godly Fifteen" racing legend club Discord chat.

This award is limited to the players who make it into the top 15 of a grand prix race and is repeatable each grand prix to show how many times you've raced among the top 15.

2.8 Live Race Regulations Grand Prix #1

The live qualifying and main race have 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.

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.9 Live Race Sequence Grand Prix #1

To help you plan, these are the sequence of events for the Grand Prix #1 live qualifying and main race.

• Race Preparation, Set Your Spawn
  • At any point before the race, have your regeneration point set to Lorville City Hospital or Everus Harbour Clinic or a ship regeneration bed of your choosing, say your organization's pit crew and race service capital ship.
  • Ensure your race craft, components and any spare craft are setup and ready to go.
• 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 and the race begins.
• T-0, Race Start
  • The endurance race will go for 2 hours.
• T+2 hours, Race End
  • Once exactly 2 hours have 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.

Super Dragon Tofu Run All Time Top 15

Pos/Player	Time/Craft	Video
1st, Horoooooo	9m 8s 450ms Razor (4.2)	Watch Run
2nd, FRESH001	10m 57s 370ms Razor (4.1)	Watch Run

These leaderboards are filtered for the Mirai Razor.

Open Full Leaderboard

Grand Prix #2

Crux Cup SEC Grand Prix #2 is for talented pilots to fly the Mirai Razor in a highly competitive 2 hour endurance race of NB//GHOST. It's a chance at earning the title "The Ghost of New Babbage" and becoming a member of the legendary racer club "The Godly Fifteen" , earning the club's name as a title for proving you are one of Star Citizen's elite pilots. This race runs in parallel with the Delivery Challenge #2 amateur racing competition.

The Grand Prix #2 race is mutually exclusive with its amateur racing competition equivalent Delivery Challange #2, but signing up to this race puts you in the running for the best prizes and rewards.

3.1 Race Track Grand Prix #2

"A young ship racer arrived at microTech in search of their missing father and became involved in the Crux Cup Stellar Endurance Championships. The pilot flew at maximum speed through a snowstorm with only 5 meters of visibility, claiming the first competition victory of the track, now named after them, NB//GHOST and earned themselves the title, The Ghost of New Babbage."

The Grand Prix #2 race track will be NB//GHOST , a community race track located at New Babbage, microTech in the Stanton System. The track is 143.3 km in length and will use the red race ship line on the map.

3.2 Race Track Video Guide Grand Prix #2

3.3 Ship Whitelist Grand Prix #2

Mirai Razor

Only the base Razor is allowed. The Razor EX & LX variants are not permitted.

3.4 Sign Up Grand Prix #2

You must sign up and participate as a solo racer.

You can optionally specify an organization, community or group you wish to represent when signing up.

3.5 Qualifying Grand Prix #2

You must post a time trial during the global time trial period for this Grand Prix. Post your time trial to the NB//GHOST SCR.gg community leaderboard in the Mirai Razor.

🐞 Bug Notice: Quantum boosting is currently being staged in the game and some of the data that unrestricts top speed (kills NAV mode) are allowing ships to have very high top speeds in atmosphere. It is the ANZIA Racing Committee's recommendation Quantum Travel to the nearby low orbit station, to set your Engine Pips to maximum, toggle your landing gear down/up in space, then fly back down to the race track using thruster flight only to get the best possible speed for your time trials! For more information, see STARC-171777 on the Issue Council.

The following speeds produced by the unrestricted top speed from this bug should be considered normal for this competition. The speeds of 465~/600~ m/s on Super Dragon Tofu Run, and 390~/520~ m/s on NB//GHOST (~varies due to wind direction) are the approximate speeds (+/-20 m/s) you want to achieve in the Mirai Razor to know you have the setup correct.

Time trial posts that appear on the "Top 30 Time Trials Grand Prix #2" leaderboard below are correctly posted within the scheduled global time trial period and will be counted as time trial qualification entries. The top 30 time trials will receive personal invitations to the live regional qualifying races, sorted as close to their region as possible.

A live qualifying race is a 2 hour endurance race where the most laps and shortest time across the finish line win. Of the 30 players who race in the live qualifying races, only the top 15 of the live qualifying standings will progress to and be offered entry into the main grand prix race.

Top 30 Time Trials Grand Prix #2

Pos/Player	Time/Craft	Video

Open Full Leaderboard

3.6 The Ghost of New Babbage Grand Prix #2

The player who places first place in Grand Prix #2 main race will earn the title "The Ghost of New Babbage" and the following rewards.

• "Ghost of New Babbage" Discord role and badge of honour.
• Special mention in the #hall-of-stars historical race records.
• A free physical transparent "Ghost of New Babbage" sticker.
• Access to the 4K resolution artwork of the icon for use anywhere in edited media or future decal system if it comes up officially or through game mods.

This award is earned once per year, is non-repeatable and will be passed onto the next player without this award in subsequent competitions.

3.7 The Godly Fifteen Grand Prix #2

Players who make it into the top 15 of a Grand Prix main race will become part of an elite racing legend club called "The Godly Fifteen". They will earn themselves the club name as a title recognized by the Star Citizen racing community, and as a badge of honour in ANZIA's Discord. They will also receive physical items to display or wear proudly for having achieved entry to such a prestigious and high skill race. The rewards are as follows.

• "The Godly Fifteen" Discord role and badge of honour.
• A free limited edition "The Godly Fifteen" Stellar Endurance Championships t-shirt with your RSI Handle, logo and favourite racing number customized on it. Earned once per year.
• A free physical transparent "The Godly Fifteen" sticker. Earned once per year.
• Access to the 4K resolution artwork of the icon for use anywhere in edited media or future decal system if it comes up officially or through game mods.
• Special mention in the #hall-of-stars historical race records.
• Access to "The Godly Fifteen" racing legend club Discord chat.

This award is limited to the players who make it into the top 15 of a grand prix race and is repeatable each grand prix to show how many times you've raced among the top 15.

3.8 Live Race Regulations Grand Prix #2

The live qualifying and main race have 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.

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.9 Live Race Sequence Grand Prix #2

To help you plan, these are the sequence of events for the Grand Prix #2 live qualifying and main race.

• Race Preparation, Set Your Spawn
  • At any point before the race, have your regeneration point set to New Babbage Hospital or Port Tresler Clinic or a ship regeneration bed of your choosing, say your organization's pit crew and race service capital ship.
  • Ensure your race craft, components and any spare craft are setup and ready to go.
• 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 and the race begins.
• T-0, Race Start
  • The endurance race will go for 2 hours.
• T+2 hours, Race End
  • Once exactly 2 hours have 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.

NB//GHOST All Time Top 15

Pos/Player	Time/Craft	Video
1st, FRESH001	5m 50s 841ms Razor (4.2)	Watch Run
2nd, JellyHeadMade	6m 5s 839ms Razor (4.2)	Watch Run
3rd, Horoooooo	6m 16s 483ms Razor (4.2)	Watch Run

These leaderboards are filtered for the Mirai Razor.

Open Full Leaderboard

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.

4.1 Race Type

The race type for Crux Cup Stellar Endurance Championships (live races) will be non-combat endurance races in lawful city armistice zones.

They are persistent universe races that will make use of a nearby spaceport, low orbit station or organization service ship to repair, refuel or fully replace your ship mid-race.

These endurance races have everyone racing together on the track at the same time. Racers will be positioned on the starting grid from fastest at the front to slowest at the back.

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.

• Grand Prix #1 & #2 Live Races
  • 1 hour party formation/setup
  • 2 hour race

Races in the persistent universe will consist of the following party composition.

• 15x racer slots.
• The rest will be filled with event staff and supporting organizations and crew.

4.2 Ship Restrictions

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

Promotion limited ships have the same performance characteristics as their freely available counterparts are an exception to this rule. Specifically, limited ships that are allowed for use include the Pirate Gladius, Mustang Omega, Sabre Raven, Pirate Caterpillar, and F7A Hornet etc.

4.3 Ship Modification

All ships can be customized without restriction using the in-game vehicle manager mobiGlas app.

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

4.4 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

4.5 Racer Regeneration Point

Racers must set their regeneration point to a nearby city hospital, low orbit station clinic or supporting race crew ship.

4.6 City & Station Hangars

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

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

4.8 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 guide all racers at a fixed speed of 150m/s to the start line.

Racers will be a single ship flying in a staggered formation to the left and right 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.

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

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

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.

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 broken the formation lap before the "Green Flag" signal from the race director is given.

5.1.2 Off Track

The track limit is defined on the track map as the drawn race line. The track may also include a pit lane defined as a separate line with different colour. 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.

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

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, go to the designated re-join point as outlined in the race briefing and safely 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.

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

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

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

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

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

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

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

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.

7.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 from above to observe/record party markers.
2. A view of the start/finish line.

7.3 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 the armistice zone of a lawful city under development 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.

Players who organically discover the event in the server will be warned about the event space in global chat and FoIP calls by event staff before any further action is taken by ANZIA Racing.

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