DAYMAR RALLY RULES

Updated 11th October 2025 - 4.3.1

Introduction & State of Game
Race Timeline
Race Format
General Rules
ATMO Officials & Security
Life & Death
Security
Fuel
Salvage
Vehicle & Ship Lists
Penalties & Disputes
Alpha Disclaimer
Contacts

1 - INTRODUCTION AND STATE OF GAME

Please see graphical rulebook for ‘Introduction’ and ‘State of Game’. This is a canon related section and does not explain detailed rules.

2 - RACE TIMELINE

Sign up opens - Mid year of the previous calendar year.
Sign up closes - 4 weeks prior to race day (be signed up by this date to receive next steps).
Registration opens - 4 weeks prior to race day. (the day after sign ups close)
Registration closes - 2 weeks prior to race day.
Race Schedule and Server Roster released - 1 week prior to race day
Race day - A Saturday in January (updates each year)

3 - RACE FORMAT

3.1 - ENDURANCE RACING

The Daymar Rally, by its nature, is a long distance endurance race. Modelled on famous races of its kind from Terra eons ago. Teams need race planning, survival and endurance instead of pure speed to succeed in this 500km desert landscape race.

There is only one course route, containing a series of checkpoints on the way to the final destination. There is no qualifying or point system. Placement is based on following these rules and arriving at the finish line first, second and third per division.

The Daymar Rally is homage to the races of old Terra like the Dakar Rally and is always held on the third Saturday of January.

4 - GENERAL RULES

4.1 - TEAM SIZE & ROLES

Each team consists of 1-5 team members and can start with:

1 x Race Driver (Starting Driver)
1 x Support Pilot (Support Ship Pilot & Navigator)
1 x Security Fighter Pilot (Primary Security Fighter Pilot)
1 x Support Member 1 (Co-Driver, Support Co-Pilot, Navigation and Comms)
1 x Support Member 2 (Co-Driver, Support Co-Pilot, Security or Support Ship Gunner)

Role Descriptions

Race Driver is the initial driver and generally dedicated to that role for the majority of the race unless death finds them or they choose to switch with another race team member.

Race Co-Driver can travel with the race vehicle as passenger and assist with checkpoint check in, swap with main driver to give them a rest or man weapons on a race vehicle.

Support Pilot commands and pilots your support craft (see vehicles and ships) which serves as your navigation and race vehicle restock support.

Support Co-Pilot travels with the support craft and aids navigation, passes critical information to ATMO esports officials and/or can fill gunner positions for additional security.

Support Gunner primarily supports defensive positions such as manning turrets and resupply while on the support craft.

Security Pilot is your defense against pirates and native elements. This role pilots a secondary security fighter that travels with and aids the race team. If the Security Pilot leaves the Security Ship to rotate to another role, that team no longer has a security ship.

Security Gunner primarily starts with the security ship if designated to this role and aids the security craft as an extra gunner on some of the two seater fighter craft available to teams.

Interchanges

All team members can interchange roles to alleviate the load of any role. However; If the Security Pilot or Gunner switches to a race team role they can no longer respawn and can no longer return to the Security Fighter. The Security Pilot and Gunner can only respawn if they perish while in a ‘Security Fighter.’

Organizations

Organizations can field as many teams from one organization as they wish. By lore the Daymar Rally is where the rich and powerful can spend as much as they like to compete and this goes the same for organizations throwing as many teams into the frey as they wish.

4.2 - VEHICLES

Apart from divisions, each team is made of a few different vehicle classes and spare vehicles.

Deployment order: First select a race vehicle, then choose a support craft, and finally select a security craft. A security fighter requires a support craft to be present and cannot be deployed without one.

4.2a - RACE VEHICLE

The heart of the team is the race vehicle, one race vehicle per team can race at any one time. Chosen from an approved list of vehicles from different divisions (see divisions) , the racer needs to take this vehicle from start to finish.

Race vehicles are the only vehicle in the race that can attack another race vehicle.

Vehicle refuel, re-arm and repair comes in the form of spare vehicles supplied by your support craft for this current patch cycle.

4.2b - SPARE RACE VEHICLE/S

Unlimited stocked spare race vehicles are allowed to overcome the absence of refuel, re-arm and repair. Support craft can carry as many as their chosen support craft can supply. Once a spare vehicle needs to be deployed, it must be delivered BEHIND the location of the current race vehicle.

Spare vehicles can be any vehicle on the allowed vehicle list as long as it is from your chosen division.

The driver can be out of the current race vehicle ready to transfer to the new replacement vehicle as soon as it is deployed to the ground and continue on racing.

Support crew need to announce to officials that the spare vehicle is being swapped. Penalties will apply if not reported.

4.2c - SUPPORT CRAFT

The support craft is an essential part of the Daymar Rally. All teams have access to one support craft per team chosen from an approved list of ships. Your Support Craft is your eye in the sky.

Your support craft can help the race driver in a few ways:

+ NEW: Can fire weapons upon threats to defend race vehicle
+ Help navigate and provide directions to race driver
+ Can take over driving the race vehicle if racer perishes
+ Relay directional information to keep the race vehicle on the correct course.
+ Refuel, re-arm and repair race vehicle
(patch 4.3 - spare vehicles take the place of R+R+R)
+ Support Co-Pilot relays distance information and issues to race officials.
+ Support pilots can replace an incapacitated driver to continue the race, but the
relinquish their previous role permanently.
+ Can bring one full cargo supply of meds, food, water and spare vehicle/s.
+ Can leave race vehicle to refuel, rearm weapons and repair.

Support craft can NOT do the following:

+ Interfere or attack any other teams in the race.
+ Team members can’t leave the support craft unless landed and changing spare vehicle
or switching roles.
+ Return to resupply cargo supplies including:
+ Replace support craft if it is destroyed

Support craft MUST start the race at an altitude of 1.5KM above and 1.5KM behind the start line. Support craft should not leave from the start position until the race vehicle is 1KM from the start line.

4.2d SUPPORT CREW OFFICIAL COMMS REQUIREMENTS

These events must be relayed to ATMO officials or you will incur penalties.

+ Every 5 mins relay distance from the next checkpoint
+ Racer crash event
+ Vehicle switch event
+ Team attacked by pirates
+ Team member death

4.2e - SECURITY FIGHTER

A new addition to the Daymar Rally is the Security Pilot who mans your single security fighter. The combat ship is chosen from a list of approved ships and is dedicated to protecting its team as best it can.

All racing team security members should work together as a hive system to look after the race in general.

ATMO officials will also have a security police force present to help aid and coordinate alerts from teams. The ATMO police force will also make sure no teams are stepping out of line and using their combat capabilities for the wrong purpose.

PLEASE NOTE: A Security Fighter can’t be in your team composition unless a Support craft is filled first.

Race team security should only use force in these instances:

+ Under attack from any source.
+ Should never instigate combat unless first fired upon.
+ Should never be in combat with another team. The security pilot is not to be used for
inter team pvp EVER. Maximum penalties will apply.
+ Can be used to scout the course in anyway and support navigation information
+ Should never interfere or fly within a 500m radius of any other team racer vehicle.

UNIQUE TRAIT: The Security Pilot and/or Support Gunner is allowed unlimited respawns to the nearest station. On respawn, the Security Pilot can change to another fighter on the allowed ship list.

If the Security Pilot rotates to another role in the team, infinite respawns are relinquished and are then subject to the team's 'Life and Death’ rules. That team can no longer use their Security Fighter for the remainder of the rally.

Security Fighter MUST start the race at an altitude of 1.5KM above and 3KM behind the start line. Security Fighter should not leave from the start position until the race vehicle is 1KM from the start line.

4.3 DIVISIONS

The Daymar Rally is split into three divisions all with their own class of mass and axle specifics. The divisions all start on the same race start count down (see race start for more details).

Bike

The bike class was implemented first when the Dragonfly and Nox first released and now includes all bikes on the allowed Bike List.

The bike class is restricted to no axle or under 40,000kg

Buggy

The buggy class was implemented first when the Cyclone was introduced and now includes all buggies on the allowed Buggy List.

The buggy class is restricted to 2 axles and under 40,000kg

Truck

The truck class was implemented first when the Ursa Rover was introduced and now includes all trucks on the allowed Truck List.

The truck class is restricted to 3 axles + or over 40,000kg

NOTE: All divisions are subject to vehicle exclusions related to patch releases.

4.4 - RACE DAY

Race day is a Saturday in January (updates each year)

4.4a - SIGN UP

The Daymar Rally is always held in January and requires a two stage Sign Up process.

Sign Up > Final Registration.

Sign ups start early in the previous year and close 4 weeks before race day. You will need to be signed up to receive final registration form.

4.4b - FINAL REGISTRATION

ATMO officials need confirmation of attendance and team details for rostering and broadcast purposes. After sign up is closed you will receive a final registration form and two weeks to complete.

Once the Final Registration form is submitted you will be confirmed to race.

IF THE FINAL REGISTRATION FORM IS NOT COMPLETED YOU WILL NOT BE RACING.

4.4C - REGISTRATION UPDATES

Teams will have one week to update registration submissions. All substitutes can’t be accepted after this date.

4.4d - RACE PREPARATION

Prior to race day there are some crucial items that need to be completed and some things that make racers and officials lives a lot easier.

All competitors should ensure that their game client is up to date.

All competitors must stock all spares and vehicles into their support craft prior to race day to not delay race start.

All Competitors need to have their respawn set close to Daymar. Grim Hex, Seraphim Station, CRU-L1 and Orison are the quickest way to reach the start line without delaying the race.

All Competitors must be clear of crimestats

If the rule book doesn’t answer your questions please attend a race practice and be present for briefing. All questions can be asked in the ATMO esports Discord prior to race day. This will reduce time spent on race day briefing and get us to Daymar quicker.

All competitors need to be on time to race briefing. Don’t act on a race strategy unless you know it’s legal. You may be penalised if you are wrong. The briefing is a time to ask the strategy questions you have.

You may be required to use third party software/web application to record distance and provide information to the broadcast.

4.5 - RACE START

After the briefing concludes server leaders will launch into a dedicated server for each region and group. You will have been issued a schedule and server roster so you know when and who to follow. Join your server leader and head straight to Shubin Mining Facility SCD-1 via the secure navigation pathway: Daymar > OM-1 > OM-4 > Shubin Mining Facility SCD-1.

This route is mandatory for security and roster checking purposes.

Race teams have 45mins from server launch to reach the start line and be ready for race count down. Any teams that arrive after race start are recommended to reach the start line and begin racing. There is still a very good chance of a successful race. ATMO esports officials will be there to check in all racers.

4.5a - FALSE STARTS & SERVER CRASHES

Star Citizen is still subject to server crashes. In the event of a server crash we will reset the server only once and begin racing again from the start line. However, if the last racer has passed Eager Flats Emergency Shelter, we will not relaunch the server and your total distance will be your placement for that server.

Please remember other racers from your division may be racing on another server. Placements will not be announced until all servers are complete and 24 hours is allowed to review and contentious rulings.

4.6 - DURING RACE

Race teams need to successfully drive a race vehicle to the finish line by checking-in at each checkpoint listed on the course route.

No navigation markers will be provided. Teams must use their knowledge and support team to navigate to each checkpoint.

4.6a - CHECKPOINTS

CHECKPOINTS - Currently the course route consists of two checkpoints and a finish line. Eager Flats Emergency Shelter and Kudre Ore (NOT Kudre Ore Mine) both have a habitation airlock. At these locations race drivers or the co-driver (if present in a race vehicle on arrival) need to exit their vehicle and cross both thresholds of the two airlock doors for any successful check in. Then return to their race vehicle to continue the race or clear the area for other racers once you have reached the finish line. An ATMO official will be checking all threshold check-ins, if a team incorrectly checks-in, they will be given a 15 minute window to correct their check-in (see Penalties & Disputes). It is a team's responsibility to confirm that they have completed a proper check-in. Officials are not responsible for missed checkpoints due to game bugs such as invisible players or missing markers.

The one other significant checkpoint is Checkpoint Echelon ( ‘The Betty’), a Reclaimer located half way between Eager Flats Emergency Shelter and Kudre Ore and will have its large industrial lights on. ‘The Betty’ doesn’t have an airlock door and race drivers don’t need to exit their vehicle to check in here. Drivers need to race between the two large legs of the Reclaimer to proceed. No stopping necessary.

NO FIRE ZONE: All checkpoints are protected by a 1KM no fire zone. No race vehicle or team member can fire weapons within the 1KM ATMO protected radius.

NOTE: Refueling and medical services will be available at Eager Flats and The Betty (Echelon).

4.6b - COURSE ROUTE

The Daymar Rally spans a little over 500km across the surface of Daymar. The race begins at Shubin Mining Facility SCD-1 which is accessed by the navigational pathway: Daymar > OM-1 > OM-4 > Shubin Mining Facility SCD-1.

Outside of reaching each checkpoint, the route you take to each is your own. There are no limitations on the road chosen to the finish line at Kudre Ore. There are faster paths and it’s up to racers to practice and learn their own way.

The course map currently lists two additional checkpoints (Checkpoint Talon and Hasgaha) which are currently not in game and will be excluded until further notice.

See map here

4.6c - POST RACE

When teams reach the finish line, you will need to immediately clear the finish line after your check in to not interfere with incoming teams.

If you see a team incoming to the finish line close to your arrival. Do not use the airlock and stay clear of the finish line threshold.

The live broadcast will close down 1 hour after 3rd place of each division has reached the finish line.

4.6d - COLLISIONS

Race vehicles can collide with opponent race vehicles.

Any other team vehicle CAN NOT collide with any other opponent vehicles. Teams will be penalized for doing so (See Penalties & Disputes).

4.6e - REFUELING AND RESTOCK

Refuel stations will be available at Eager Flats and The Betty supplied by Altama Energy.

Supplies of food, water and med pens will also be available from Quantum Jump Medical.
We recommend bringing your own stock in case stock runs out.

4.6f - DISTANCE RECORDING

All teams including solo racers MUST record their time via the ATMO esports provided web application or thread every 5mins. Failure to do so will result in penalties.

4.9 - PLACEMENT STRUCTURE

Each division has 1st, 2nd and 3rd place based on arrival order to the finish line (Kudre Ore).

If all teams perish before all placements can be identified. 1st, 2nd and 3rd will be determined by distance reached to the finish line (Kudre Ore) or a mix of arrivals and distances.

5 - ATMO OFFICIALS & SECURITY COORDINATOR

Race Officials (identified by specific Discord roles/in-game tags) are the final authority on all rule interpretations, penalties, and race procedures during the event.

PARTICIPANTS MUST FOLLOW ALL INSTRUCTIONS FROM RACE OFFICIALS PROMPTLY. Failure to comply may result in penalties.

Officials have the discretion to handle unforeseen circumstances or issues not explicitly covered in this rulebook to ensure fair competition.

6 - LIFE AND DEATH

Team survival is different for particular members of your team and the support craft you choose.

Medical gameplay has changed a few times since its initial basic release. The Daymar Rally first introduced respawning from chosen support craft for the first time recently but after recent updates the ATMO team has had to make some additional changes to keep up with patch releases.

6.1 - TEAM LIFE

From a life/respawn perspective the team is broken up into the Race Team (Driver, Support Pilot & Support Co-Pilot) & Security Pilot (Security Pilot & Support Gunner).

NOTE: If the Support Gunner transfers to the support ship they can’t return the Security Fighter. If they Security Pilot transfers to the Support Ship, the team relinquishes the Security Fighter and must continue without a Security Fighter for the rest of the rally.

Race Team

The Race Team is bound by one life and the ability to respawn to a support craft only. If a team member dies while racing/supporting for any reason and can’t respawn to their support craft, they are eliminated. No exceptions.

Security Pilot

The Security Pilot and/or Support Gunner is not bound by the same rules as the Race Team. As long as the Security Pilot has not rotated into a race team position (Race Driver, Support Pilot or Support Co-Pilot.) to fill another role, they can respawn as many times as they like.

They can also spawn any security fighter on the approved list to rejoin the race. They are not bound by the initially launched security fighter.

6.2 - MEDICAL SUPPORT

Medical support and supply stations are located at Eager Flats Emergency Shelter & ‘The Betty’. A medical ship crewed by Quantum Jump Medical will be on site at both the above locations for injury recovery, food and medical supply stock.

NOTE: Allowed support craft have minimal respawn capabilities and only low tier medical beds.

7 - SECURITY

Aside from the team security, Daymar is also governed by the ATMO esports Police Force. The ATMO police force is designed to make sure player security is acting as intended and bolster player security in overwhelming instances.

ATMO Police also coordinate the comms between player security and the police force. Reacting to any posted threats and linking everyone in a hive of security.

8 - FUEL

Refueling is contracted to ALTAMA ENERGY which will be able to support your refuelling needs at Eager Flats Emergency Shelter and The Betty checkpoints.

In addition, support and security craft can leave their race vehicle to refuel anywhere that is convenient.

NOTE: Please keep in mind the return navigation pathway to return to the race.

9 - SALVAGE

Salvage is contracted to DELTA AEROSPACE BLUE who facilitate the removal of abandoned race, support and downed fighter ships in the region. The salvage teams are instructed to always keep processing bases and remote salvage teams behind the last racer to not interfere with race progression.

10 - VEHICLE & SHIP LISTS

The below lists are the legal ships that can be chosen to participate in the rally for the next Daymar Rally. This list will be updated if new vehicles are released and each year they will be reviewed for inclusion/exclusion.

11 - CONDUCT, PENALTIES & DISPUTES

11.1 - CONDUCT

Cheating, hacking, exploiting game bugs for unfair advantage, or using unauthorized third-party software is strictly forbidden and will result in immediate disqualification and potential bans from future ATMO Esports events. Report any suspected cheating or exploits to officials immediately.

11.2 - INFRACTIONS: ACTIONS SUBJECT TO PENALTIES INCLUDE (BUT ARE NOT LIMITED TO):

Ignoring Official Instructions
Unsportsmanlike Conduct / Code of Conduct violations
Cheating / Exploiting
Using Non-Approved Ships/Loadouts (if restricted)
Intentional Track Cutting
Intentional Collisions / Ramming (Support/Security craft only)
False Starts

11.3 - PENALTIES: DETERMINED BY OFFICIALS BASED ON SEVERITY AND INTENT. MAY INCLUDE:

Verbal Warning
Time Penalty
Race Disqualification (DQ)
Ban from future ATMO Esports events

11.4 - DISPUTE PROCESS

If a racer believes a rule was broken by another competitor or an incorrect ruling was made that directly impacted their race result, they may file a dispute.

Disputes must be submitted formally via DISCORD to the designated Race Officials within 30 minutes after the race concludes. Video evidence must be submitted within 24 hours after the race concludes.

VIDEO EVIDENCE of the incident from the reporter’s perspective is REQUIRED.

Officials will review the evidence and relevant perspectives. The decision of the review panel is final. Frivolous or excessive disputes may be penalized.

11.5 - PENALTY STRUCTURE

How a team will be penalized for infractions will be broken down by severity and whether or not your actions impacted another team's ability to race effectively. Below is a table of what types of infractions we will administered for the illegal actions possibly displayed by teams:

NOTE: Any teams that are disqualified must remain where they are to be escorted from the race track or notify officials that they are disconnecting from the finished location.

12 - ALPHA DISCLAIMER

Star Citizen is an alpha-stage game. Bugs, performance issues, and unexpected behaviors are possible.

ATMO Esports and its officials will strive for fairness but may need to make adaptive rulings based on the game’s state.

Rules (especially regarding specific ship viability, component restrictions, or track layouts) may be adjusted with reasonable notice if significant game patches impact competitive balance or introduce critical bugs.

Participation acknowledges these risks. Official decisions regarding unforeseen technical issues or bugs are final.

13 - CONTACTS

Official Discord: Atmo Esports.