1
The SNAIL OLR
This is, in many respects, identical to the GTP OLR. Some parts have changed, but the general tenets of race craft have not. Please be sure to familiarize yourself with the entirety of this document.
Read it. Learn it. Live it.
* * * * * * * * * * * * *
1: SNAIL OLR General Rules:
A: These rules are subject to change as there are constant updates/changes coming out for GT Sport, it is your responsibility to update yourself on the changes. A member of the Board of Directors (B.O.D.) will post in the main SNAIL thread when a change has been made along with a summary of the change.
B: All drivers are expected to make themselves familiar with the racing rules before entering any race or competition. If you stumble across a rule that is unclear to you, make sure you fully understand that rule before you enter the race or competition. You can post your questions in the main SNAIL thread.
C: You are expected to compete in a fair and honest manner and in accordance with the SNAIL OLR as well as SNAIL policies and guidelines.
D: You are expected to drive responsibly in a way that’s not likely to ruin the racing enjoyment of your fellow drivers.
E: You are expected not to submit to bad general behavior under all circumstances.
F: Try to maintain a generally affable nature with the rest of the group; both in the thread and on the game. Some friendly rib-jabbing is expected. This isn't church.
G: You are expected to behave like sporting gentlemen and women at all times.
H: The position of other drivers must always be respected.
I: Aggressive driving is strictly prohibited.
J: Cutting the chicanes or "shorting" the track at any point is strictly prohibited. Track specific boundaries have been declared and can be found in the track boundaries section of the policies and guidelines thread.
K: If a driver wants to retire from a race, the driver concerned must not exit the race. The driver must find a position on the track where the driver will not endanger other drivers, park their car by coming to a complete stop and turning on the emergency brake and wait for the race to end.
L: No careless driving. Always show respect for your fellow racers. Be careful. Show some patience. Understand the limitations of your car and yourself and drive accordingly. Driving online in a racing sim is NOT exactly the same as real life racing in every respect. Familiarity with the car and track is expected. Do not go into a Sunday night without having practiced and expect to be able to late brake or make other aggressive maneuvers without incident.
M: If you are found guilty of any of these rules, the behavior will be evaluated and penalty assessed by the race stewards as per the SNAIL penalty system.
N: You must not use any cheats or bugs in the game. The use of cheats or bugs affecting the cars performance is forbidden.
O: The use of external cheats is forbidden.
P: The "ghosting feature" may only be used by a driver who has quit the race. Further explanation can be found in the Incident Review and Report post under penalty guidelines.
2: Pit Etiquette:
A: As the S.N.A.I.L. Sunday night races do not require a pit stop, any series running under the SNAIL umbrella may adopt their own rules regarding pit entry and exit.
3: Rules Governing Car Contact:
A: Contacts and collisions must be avoided at all costs.
B: Pushing other cars in turns or pushing them off the track is strictly prohibited.
C: Leaning on other cars is strictly prohibited in any situation.
D: Some contact through a corner or through a pass may not be avoidable and may be deemed "incidental" should it not appear to affect the likely outcome of the section in question.
4: Running into the car ahead of you:
A: The behind driver must take all necessary care and responsibility not to run into an ahead driver.
B: In case you brake too late for a corner or partially lose control of your car, you must do your best to avoid making the loss of control into a bigger incident. You are expected to minimize the impact to the best of your ability. If this means turning your car into a wall or off the track to avoid contact, that is what you are expected to do.
C: The ahead driver must not do any malicious or inappropriate braking or slowing. Leading cars MUST NOT EVER 'brake check' the car(s) behind them because they are following too closely. The ahead driver IS entitled to be slower or use longer and earlier braking zones than others. They are also entitled to turn in earlier or later and/or apex earlier or later. The ahead driver should not make a drastic or sudden change to their line through a corner.
5: Contact Concessions:
A: If there is contact between drivers that results in an accident, the guilty driver should allow all involved drivers to pass freely to re-establish their position at the earliest safe place to do so. This rule should be observed, even if it means the guilty driver has to allow drivers not involved in the incident to pass while waiting for the driver(s) they contacted / affected.
B: If you have to slow down to let the other player through, move out of the racing line first before you slow down. Coming to a full stop on track is not allowed. After completing the concession, return to the racing line when it is safe to do so. This means that your return to the racing line will not affect any other driver on the course.
6: Corner Rights:
A: You must establish substantial overlap with the car ahead before they reach the corner’s turn-in point to have the right to drive up their inside, or to expect them to leave inside room for you. At least the front of your car should be up to the driver’s position in the ahead car. The ahead driver has the right to be fully committed to the racing line of their choice without any interference if there was not substantial overlap before he turned in. The ahead driver must not abruptly change their line through a corner for any reason.
B: If sufficient overlap is established before the turn-in point, both drivers have the right to sufficient side room. This means that each driver has a right to their respective "line", or side of the track, right up to the exit point. Neither driver should squeeze the other toward the inside or outside of the corner during the apex or exit.
C: The turn in point is the point at which the leading car begins their turn into the corner on their chosen line. It is not necessarily the first move toward the apex. It is the move that commits the lead driver to their chosen line. Example: A gradual move toward the apex followed by a sharper turn would mean that the sharper turn would be the turn in point. Example: Multiple turning movements approaching the turn would mean that the final turning movement would be the turn in point. This point may vary from the point at which you turn into the corner.
D: If an ahead driver has clearly made an error to warrant a passing move, a behind driver may attack their position, with due caution and care, regardless of whether there was any pre-existing overlap. However, the overtaking driver must still avoid contact. Small errors by the ahead driver may not necessarily justify a passing move. The ahead driver getting a bit out of shape at times doesn’t give you an automatic right to force a pass. You still have to pass safely and without undue contact. The ahead driver must not make any sudden changes to their line in an attempt to defend their position in this situation.
E: Drivers are expected to take any means necessary to be aware of their surroundings on track, as "I didn't see you", is not an excuse for making contact with another driver.
7: Standing Start Guidelines:
A: Additional caution and care must be taken when beginning a race with a standing start. All of the above rules in regard to contact apply during the start and first corner of the race.
B: Be patient. Begin the race at a normal pace that will not cause you to run into cars in front of you. Don't begin by steering to one side and attempting to barge through the pack. Conversely, don't begin at a slow pace that will make you an obstruction or barrier to cars behind you.
C: Due to field compression, a compact field will run slower through the first few turns than a spread out field would. If you are behind a few cars in line, be prepared to brake extra early for a turn, as each car will be braking a bit farther back on the track than the one in front of it in order to avoid contact.
D: All of the rules in regard to contact concession apply if you knock a racer off track during the start of the race.
8: Defensive Driving:
A: Leading cars have the right to choose their own line down a straight. They can change their racing line once while driving down a straight (Move from the outside line to the inside, or vice versa). As they approach the next corner, they can return to the racing line of their choice. However, they are not allowed to change their line in direct response to the behind driver changing his line to try and make a pass.
B: Leading cars have the right to take their line of choice through corners. I.e. they may drive a defensive line around the inside of a corner to protect their position, thereby forcing an attacking driver to try to pass around the outside. This is not blocking and is part of normal racing etiquette. This does not mean that the lead driver may change their line mid-corner in an attempt to block a fellow competitor.
C: Drivers that are about to get lapped have to make sure not to interfere with the lapping cars. The driver being lapped should stay on the racing line but slow down just enough to allow the lead driver an easy pass. Keep your racing line predictable and try to stay out of the way.
9: Group Battle:
A: When approaching an ongoing battle with 2 or more cars, be extra careful since those cars can change driving lines quickly when trying to defend/overtake. The cars in front will already be driving close, so finding a good overtaking spot is much harder. The same rules apply as when overtaking a single car.
B: When you get 'locked up' in a group battle on the straights, you are not allowed to bump the driver in front of you in order to free yourself out of that situation. Stay behind that driver or move sideways as soon as there's sufficient room to do so. Note: This rule does not restrict bump drafting on long straights.
10: Ghost Cars:
A: A ghost car is any car that is transparent and/or flickering transparent.
B: If your car is a ghost car, you take on the responsibilities of the following "Recovering from an incident" and "Re-entering to the track after running off" topics as you are at fault. You also give the correct driving line to the non-ghosted cars (taking a turn wide so others can pass on the inside). Do not return to the driving line if possible until your car is back to the normal state. This may be hard to tell if you use bumper cam, but do your utmost to determine your state. Naturally, if you are serving a penalty, assume you are ghosted.
C: If you are approaching one or more ghost cars on the track, you must avoid any contact with them at all as they may return to a normal state immediately. Then the contact would be your fault and in turn you may become a ghost car and have to make room for others while your car slows due to the penalty. Passing through a ghost car that is not entirely out of control in an effort to pass them will bring a penalty.
D: If your car becomes a ghost, you are not permitted to overtake other non-ghosted cars. If you happen to overtake a car while being a ghost, you must return to your original position safely.
E: If your car is a ghost you are not allowed to intentionally drive through other cars, just as they are not allowed to drive through you. In short, all cars on the track should be considered solid, no matter what state the game displays them.
F: In the event of an accident ahead of you in which cars have the potential to be ghosted, you should treat this incident as if the cars in front of you are going to be solid when you arrive. This means braking for an accident in front of you and not just trying to run through it at full speed.
G: There is a feature in GT Sport that allows the driver to force their car to ghost. SNAIL does not allow the use of this "ghosting feature" except in very specific circumstances. This may be different from other racing series that allow or even encourage the use of the "ghosting feature" to prevent accidents.
H: Drivers may use the "ghosting feature" only when they have quit the race, stopped their car, and are not on the racing surface. A driver has quit the race only if they do not return to the racing surface for any reason except to safely move their car to pit road. Penalties will be assessed for any unapproved use of the "ghosting feature" that is reported to the stewards. Those penalties are outlined in the SNAIL penalty guidelines.
11: Recovering from an incident:
A: It is the responsibility of the driver recovering from any incident to take all necessary care to not interfere with any cars still on the track and not part of the incident. A relevant incident may include, but is not limited to:
- Being spun out
- Facing the wrong way,
- Perpendicular to the track
- Going abnormally slow for where you are on the track.
B: If you are off the track, serving a penalty, or recovering from an incident in which you didn’t leave the track but are significantly slower than the race pace then the rules on "Re-entering to the track after running off" apply.
12: Re-entering to the track after running off:
A: It is the responsibility of the car returning to the track to insure that they do not interfere in any way with another driver. If there's a chance of a collision, wait and be patient as other drivers have the right of way.
B: An off track incident includes but is not limited to:
- Being stuck or pinned to a wall or railing.
- More than two tires leaving the track at any one time.
- Any situation where the car may lose control and create cross traffic.
C: Do not reverse back onto the track unless it is necessary. If you are backing up away from a wall first look around you to avoid a collision and as the collision would be your fault.
D: Re-enter the track parallel to the road, slowly and gently, and always with great care. This gives you the best opportunity to see what’s coming up the track behind you.
E: When re-entering the track, you must take all available measures to not affect any other driver on the track. If this means you have to come to a complete stop on the side of the track and wait for the track to be clear, then that is what you must do.
13: Track Boundaries:
A: Colliding with or using walls, fences, cones, brake markers or any other obstacle that is outside the track surface is forbidden, whether time is gained or not and whether you have two tires on the track surface or not.
B: Two wheels (except when airborne, where the vertical projection of the car onto the track counts) must be in contact with the track surface which is defined in the SNAIL track boundaries guidelines.
C: A full explanation of track boundaries can be found in the SNAIL track boundaries section.
14: Qualifying:
A: GT Sport will use a procedure where all drivers qualify during the "practice" session. All drivers and the host of the room must follow the procedure in section 14-B.
B:
Qualifying Rules
Prior to the first race of each combo drivers must immediately drive to a spot beyond turn one where qualifying will start and line up single file. The scorekeeper must be the first driver in line. The host will remain on pit road during this time.
Once the driver count has been verified, the host will give instructions to start qualifying and leave pit road to join in at the back of the line. Drivers should give 5 seconds between the driver in front of them leaving and when they start.
Qualifying is not the race. If you get caught from behind during the qualifying session you must allow the driver to pass without incident or opposition.
All drivers will complete an out lap and one hot lap for qualifying.
If, at any time during the out lap or the hot lap, a driver leaves the racing surface for any reason, except to avoid another car on track, they are to pull completely off the track and out of the way at the earliest safe location and wait for the qualifying session to end. They are not to attempt to re-enter the track for any reason.
If a driver is caught from behind during qualifying, they must get off the racing line and allow the driver that caught them to pass without incident.
Once drivers have completed their hot lap, they are to stop on the track far enough past the start finish line as to not be a distraction to anyone finishing a lap.
Once the host has completed his hot lap, he will check that no non-members have entered (kick as necessary) and start the race.
This process can be modified for shorter tracks or to change from 5 seconds if deemed necessary.
Failure to comply with qualifying rules will result in a disqualification for that race.
15: Incident Reports
A: All racing incident reports must use this procedure, which is modeled and automated to follow the GTPOLR complaint process:
- All incident reports must be submitted at The S.N.A.I.L Incident Report (IR) Submission Form, by 11pm Eastern / 8pm Pacific on Monday night. This process is specific to SNAIL Sunday League night.
- A complete explanation of the process along with instructions on how to file can be found in the SNAIL Incident Report and Review section.
- Other SNAIL series may use a different reporting procedure; contact the respective series organizer for those details.
B: Drivers are, under no circumstances, allowed to discourage, dissuade, or otherwise attempt to deter another driver from filing an IR against them. Any driver who violates this policy becomes subject to discipline which can include, but is not limited to, having their posting privileges suspended or having their racing privileges suspended.
This version of the SNAIL OLR was published on Jan. 4, 2019 and replaces any previously published version of the SNAIL OLR.
1.1
Track Boundaries
This post will serve as a supplement to section 13 of the SNAIL OLR.
The white line at the track edge is the track boundary unless there is a striped rumble strip present or the section of track is listed here as an exception to this rule.
GT Sport Tracks
Alsace- No exceptions.
Autodrome Lago Maggiore - All Layouts - No exceptions.
Autodromo De Interlagos - The white line at pit entry and exit is ignored as a track boundary where it is a single line. If there are other, crosswise, white lines behind the white line at pit entry and exit then the white line is a track boundary. The area to the right on the front straight that has yellow and green stripes is not considered part of the track and the white line is the boundary in that area.
Autodromo Nazionale Monza - The green paint at pit entrance is not considered part of the track. The white line on the pit straight is considered a track boundary. The white line that shifts after pit exit and runs down the middle of the track can be ignored as a track boundary.
Blue Moon Bay -
Infield All Layouts - The white line that extends into the oval portion of the course can be ignored as a track boundary. The yellow paint is considered to be the track boundary and you must keep two tires on or inside the white line when the yellow paint is present.
Brands Hatch (all versions) - No exceptions.
Broad Bean Raceway - The double yellow line around the left side of the track, weather solid or striped, is the track boundary. At least two tires must be on or to the right of the rightmost line at all times.
Circuit de Barcelona-Catalunya - No exceptions. Of note, any additional curbing beyond the red / white rumble strips is not considered part of the track. This includes any green / white rumble strips.
Circuit de la Sarthe - Broken white lines can be ignored as track boundaries. Solid white lines are treated as listed above.
Circuit de Sainte-Croix (All Layouts) - No exceptions.
Dragon Trail
- Gardens - No exceptions.
- Seaside - No exceptions.
Fuji International Speedway (All Layouts) - No exceptions.
Kyoto Driving Park -
- Miyabi - The white line inside of the red colored pavement is to be ignored as track boundaries are concerned. In other words, the red pavement is part of the track. Only the red / white painted rumble strips are considered rumble strips at this track.
- Yamagiwa - The white line inside of the blue colored pavement is to be ignored as track boundaries are concerned. In other words, the blue pavement is part of the track. Only the red / white painted rumble strips are considered rumble strips at this track. The blue textured surface on the outside of turn one (forward version) is not part of the track.
- Combined - Boundaries from both tracks listed above apply to the combined version.
Mount Panorama Motor Racing Circuit - No exceptions.
Northern Isle Speedway - The red line is the track boundary. At least two tires must be on or to the right of this line at all times.
Nurburgring GP - At the right hand portion of the final chicane, no tires are allowed on the green area beyond the rumble strips. This coincides with the pylon that is placed and is not meant to be struck.
Red Bull Ring (all versions) - No exceptions. Any additional curbing beyond the red / white rumble strips is not considered part of the track. This includes any green / white rumble strips.
Suzuka Circuit - No exceptions.
Tokyo Expressway -
- Central Outer Loop- All painted lines and areas are to be ignored as track boundaries. The only boundaries to the track are the walls. As always, pylons are not to be contacted.
- Central Inner Loop- All painted lines and areas are to be ignored as track boundaries. The only boundaries to the track are the walls. As always, pylons are not to be contacted.
- East Outer Loop- TBD
- East Inner Loop- TBD
- South Outer Loop- TBD
- South Inner Loop- All painted lines, areas, rumble strips are to be ignored as track boundaries. The only boundaries to the track are the walls. As always, pylons are not to be contacted.
Tsukuba Circuit - No exceptions.
Willow Springs-
- International Raceway - No exceptions. As always, pylons or cones are not to be contacted.
- Horse Thief Mile - There are no lines or rumble strips present. Two tires must remain on the paved surface at all times.
- Streets of Willow Springs - No exceptions. As always, contact with cones or pylons is subject to penalty even if you are otherwise within the stated track boundaries.
Tracks will be added to this list as they are used for Sunday night racing.
1.2
How to file a Racing Incident Report
This process has been adapted from the
GTP OLR Rules (Section 15), but simplified,
automated and made more applicable to our league.
Failure to use the The S.N.A.I.L Incident Report (IR) Submission Form will result in your IR not being accepted as "official". Therefore, do not expect any action to be taken, if you don't use the form. Additionally, if the data you provide is inaccurate in any way (i.e. round, race, lap number, but especially, timestamp) we reserve the right to invalidate your IR.
Note: All drivers who are racing are eligible to file an IR against any driver in the division in which they are currently assigned weather or not they are involved in the incident.
***********************************************
Instructions on how to accurately report time stamps in an IR.
The Form asks for time in Hours, Minutes and Seconds. No tenths, hundredths or thousandths are required.
From a replay, the race time is in the bottom left corner of the screen. Enter this value from as close to the beginning of the incident as possible.
SNAIL Sunday races will never exceed an hour. That field should always be 0. The race time of 6:26.123 would be entered as shown in the next picture.
***********************************************
All racing incident reports
must follow this procedure:
- All incident reports must be submitted at The S.N.A.I.L Incident Report (IR) Submission Form, by 11pm Eastern / 8pm Pacific on Monday night (the form will open for driver submissions at approximately 11PM Eastern Sunday night and close at 11PM Eastern on Monday night).
- Multiple incidents will be entered as separate submissions.
- Do not group separate incidents together, in one form entry. Ex: contact with another driver and an unsafe track reentry immediately following the contact should be entered as two IRs.
- Filings for out of bounds may be grouped in a single IR for each race but may not be combined with any other incident.
- When self reporting an incident, enter your ID in both driver fields.
- If you like, you may forward a copy of your notification to the driver you committed an infraction against. Recommend using GTPlanet's messaging system.
- Our stewards will then review the reported incident(s) and determine what penalties (Section 1.3 below) if any, are appropriate.
- The Division Steward for D1 drivers is - @TomMang_68
- The Division Steward for D2 drivers is - @JLBowler
- The Division Steward for D3 drivers is - @TomMang_68
- The Division Steward for D4 drivers is - @JLBowler
In case the procedure regarding race incidents is not followed and / or the driver decides to discuss the racing incident in public here on the S.N.A.I.L. forum, and as defined by this policy, the driver may be given a warning or an infraction (in case of repetition or blunt accusations) by the S.N.A.I.L. BoD. Should a driver wish to check the status of an IR before the steward summary is released, they may do so by checking this link.
PLEASE NOTE: If you are the driver an incident report is filed against, feel free to tell "your side of the story" to your Division Steward so that he can relay it to the rest of the stewards who will be reviewing the incident. There is no need to reply to the driver who filed the complaint against you unless you want to and are able to do so in a completely non-confrontational manner.
Any response to an IR filed against you should address your division steward and should include nothing more than your take on the incident. This is not the place for personal attacks against the driver who filed an IR against you, nor is it the place for arguments about the incident. This holds true for the driver filing the IR and the driver being filed against.
Failure to follow this policy will be treated the same as personal attacks and arguing in the main thread, divisional conversations, and race lobby.
Sadly, the preceding two paragraphs have been added on 17 August 2015 in an effort to encourage others to behave in a civil and factual manner when reporting or responding to incident reports. This change is effective immediately. Dragonwhisky
_________________________________________________________________________
1.3
SNAIL Penalty Guidelines
Level 1 (1 - 4 point penalty) - Likely caused by a lapse of concentration.
A bump
Passing through a ghosted car (1 pt. /car)
Shortcutting the track boundaries (1 pt. /incident)
Level 2 (5 - 8 point penalty) - Showed a lack of situational awareness.
A shove
This may be the result of carrying too much speed into a corner or braking too late, causing moderate to major contact.
An unsafe track re-entry also falls here (6 pts. cannot be halved for concession)
Level 3 (9 - 12 point penalty) - Demonstrates a lack of good race craft.
The offending driver was likely too aggressive in a pass, creating a situation where his car met another at a drastic difference in speed.
Excessive blocking or weaving.
This is the lowest level that a dive bomb pass attempt would be penalized at.
Level 4 (13 - 16 point penalty) - Clearly showed a lack of judgment and a disregard for the tenets of good race craft.
This is an incident from which complete recovery is realistically impossible.
The offending driver likely came on an overtly aggressive line or made a move that directly put others in jeopardy.
Level 5 (17 + point penalty) - Intention may be believed or even known.
Incidents of this caliber are race-ending and reputation-scarring.
This level of penalty would require extensive discussions by the Stewards, and would be open to any penalties as we see fit up to and including placement on the last chance list, suspension from SNAIL events, or removal from SNAIL.
--------------------------------------------------------------------------
- These levels are guidelines for us and you, and other penalties may be assessed as deemed necessary.
- Any of these penalties except for level 5 and unsafe re-entry could be halved with the proper concession after the fact during the race. Ghosting violations and out of bounds violations can be eliminated with proper on track concession. Penalties will only be assessed in whole point values. Example: A driver receives a 7 pt. penalty and makes a proper concession, they would be assessed a 4 pt. penalty (7/2=3.5 rounded to 4).
-A proper concession consists of a separate and deliberate act on the part of the offending driver to return any position gained or to negate any time gained during the incident. Ending up in the grass or sand trap and losing time because of your own action is not considered a concession.
-If a driver chooses to report a violation of the SNAIL OLR that they committed themselves, that action will serve to cut the value of the penalty in half. This would apply to all penalties including unsafe re-entry to the track. This would still not apply to any level 5 penalties.
- Each of these penalties will bring about a probation period based on the level. A level 1 penalty will bring a 1 week probation period; level 2 brings 2 weeks, etc. The probation period doubles the point value of any incurred penalties while on probation.
- Multiple penalties in one week will be added to create a longer probation period: i.e. Level 1 + Level 3 penalties = 4 week probation.
- Multiple penalties during one week will not double the penalty points for that week.
- Drivers earn their way off of probation by racing without a reported incident for a full race night. Each night raced will remove one week of probation. In order for a night to be considered a full race night, a driver must compete in at least 4 of the 6 races in a single night. If a driver is observed pulling off the track and / or not racing then that race will not be counted toward the 4.
- Penalties for out of bounds violations will be totaled for each race. Four violations in one race would equal a Level 1 penalty worth four points. Five violations in one race would equal a Level 2 penalty worth 5 points. Any time a valid OOB violation is reported, the stewards will look at that driver's entire race for other possible violations.
-Stewards have the ability to assess penalties that are found during the normal course of reviewing a reported incident, but we will not actively look for things to penalize (except in rare instances and only by decision of the chief steward). Any violations discovered by the stewards during review will not be subject to the filing deadline for race complaints. As a result of this, any IRs filed by stewards will not affect prize winners for that week.
-Special note concerning the use of the in game "ghosting feature". Use of the ghosting feature is not permitted in SNAIL except in very specific situations. If the "ghosting feature" is used in a non-approved way, the following penalties will apply:
Level three which is 9 -12 pts. Any movement while ghosted by a driver that has not quit the race, either on track or off track or parking while ghosted on track or near enough to the racing surface to create a distraction (defined as your triangle being on any portion of the track maps white line).
18 points or more - Use of the ghosting feature to avoid a collision or accident, use of the ghosting feature to gain any type of advantage either on track or off (ex: ghosting through a sand trap), or use of the ghosting feature that causes another driver to take evasive action or be distracted.
Movement while ghosted off the track by a driver who has quit the race will not be penalized. Quitting the race means that the driver does not return to the track during the course of that race unless it is to safely move their car to pit road.
(note for GTS. The ghosting is currently not working as intended as the game will ghost cars that are involved in accidents. All rules from section 10 of the SNAIL OLR will be applicable in GTS. Any penalties regarding ghosting will be at the discretion of the stewards and / or BoD.)
Last Chance List Policy
-Once a driver reaches the maximum six week probation period an automatic stewards vote is triggered to determine if the driver goes on the last chance list.
-Once on the last chance list, any penalty would trigger another vote by the stewards to determine what action should be taken. Those options will be: no action, suspension of a duration to be determined by the stewards, or a ban from SNAIL. In addition to these options the stewards will have at their disposal the use of any other stipulation to membership that they wish to assign to a driver on a case by case basis.
-If a driver is found to have used a glitch or cheat while racing the stewards will have the option to place that driver on the LCL, suspend the driver for a duration to be determined by the stewards, or ban the driver from SNAIL upon the first offense.
-In the event that a driver is suspended from Sunday night competition for any reason, that driver will not be permitted to enter the race lobby while they are suspended.
-During any stewards vote, the stewards would have until noon Eastern Time on the first racing Sunday after the vote was triggered to cast a vote and the majority of those voting would make the decision.
-In order for a driver to work their way off the last chance list, they must race without incident for how ever many number of weeks of probation they have.
SNAIL Cookie Policy
In a nutshell, the "cookie policy" means that nobody should confront, accuse, or imply that a fellow driver was at fault in a racing incident until after league night is over. First of all, you can never be sure who's "
eating your cookies" until you check the replays. Secondly, the confrontation creates a negative atmosphere in the lounge and is uncomfortable for others to read or listen to. And most importantly, history has shown that in-lounge confrontations result in negative outcomes far more often than positive resolutions.
If you feel that you have been a victim of poor racecraft, please wait until
after the races are over and review the replays so that you can watch the incident from multiple perspectives. If, after reviewing the replays, you feel that your original suspicions were correct, then file a
Racing Incident Report to the stewards.
Failure to adhere to the "cookie policy" can result in penalties and the loss of points (just like an on-track penalty). Please do yourself (and everyone else in the lounge) a favor by waiting until league night is over before taking action on a racing incident.
_____________________________________________________________________
1.5
Due to recent visits by GTP moderators on Friday as well as here and here, SNAIL management has requested, and been granted, authorization to revoke posting privileges from anyone who makes inflammatory and/or inappropriate posts. Posting privileges can be revoked temporarily or indefinitely. Revocation of posting privileges does not mean you cannot race. It only means you will not be allowed to post in this thread. You will, however, be able to read everything others post.
We sincerely hope that we won't ever have to use this new capability to police our thread, but we will do so without hesitation if anyone posts anything that we deem to be inflammatory, inappropriate, or otherwise disruptive to our thread or the SNAIL vibe in general. It's been a long time coming, but now we'll no longer be at the mercy of anyone's selfish desire to inject unwanted drama into our thread. Those days are officially OVER!!
2.1
SNAIL Driver Status Policy
Any driver who has raced in more than half of the Sunday night events available to them will be considered full time active for the following season. i.e. 1 of 1, 2 of 2, 2 of 3, 3 of 3, 3 of 4, or 4 of 4.
Any driver who has raced in half or less of the Sunday night events available to them will be considered part time active for the following season. i.e. 1 of 2, 1 of 3, 1 of 4, 2 of 4.
Any driver who does not participate in any Sunday night events for two full seasons or their first partial season and one full season will be moved to the inactive list.
Any driver who, during a monthly season, misses enough nights that they can not reach full time active status for the following month may be moved to part time active status mid-month.
Any part time active driver who races in the first three Sunday night events in a month will be moved to full time active status for the fourth race of the monthly season.
Any new driver who joins in the middle of a season will be considered full time active then evaluated using the above criteria for each subsequent season.
Any driver who is currently considered to be inactive may become active at any time by reading the first post in the main thread and following the directions to join.
*Note: Any driver that has been banned from SNAIL Sunday night racing, either by the stewards or by the BoD is not considered to be a member of SNAIL in any capacity.
In the event that any division reaches capacity on a Sunday night, full time active drivers will have priority over any other classification of driver for filling spots on the grid during Sunday night races. Part time active drivers will be listed in order of priority for racing on Sunday night. The drivers list is also the priority list from top to bottom.
This list will be ordered using the following criteria:
1. Most to least amount of points scored in the current season. If tied move on to
2. Most to least points scored in the previous season.
If a room reaches capacity and a part time driver in that division wishes to race, they may move up one division and race that night. That driver will be scored in the higher division for that night. Any points earned in the higher division will not transfer to the lower division but the driver will be credited with racing that night for the purpose of full or part time status.
_____________________________________________________________________________
2.2
New Driver Placement Scheduling
and
Promotion and Relegation Scheduling
All drivers that submit a time trial before 23:59 ET on Saturday night will be placed in a division for racing on that Sunday. This may occur as late as Sunday afternoon but it will be done in time for Sunday night racing.
Every effort will be made to have promotion and relegation completed by the Friday night before the start of the new season. When there is a high number of new drivers in the registration process promotion and relegation may be delayed and announced after the Saturday deadline for new driver time trials.
3
Vehicles eligible for selection for Sunday night racing are as follows:
Any vehicle that is available in Brand Central and costs 1,000,000 Cr. or less.
_____________________________________________________________________________
3.1
Tuning Prohibited in SNAIL means that you are not allowed to do anything to the car that changes it's performance in any way, shape, or form.
Below is a list of what you are allowed, or required, to do:
1. Change tires (may be required depending on the car)
2. Change wheels. Different sizes are acceptable.
3. Change the appearance of the car using the livery editor.
You may not adjust any other setting or replace / upgrade any other part of the car. If what you are thinking about doing to you car is not in the above list, don't do it. Only the 3 items listed above are allowed under SNAIL rules.
_____________________________________________________________________________
3.2
SNAIL tire regulations
Regulations for GT Sport can be found here.
______________________________________________________________________________
3.3
GT Sport track list can be found here.
Prize winners are allowed to choose the time of day for their track selection. If a specific time of day is not selected then the default time of day will be used. (Note: The time of day settings differ between arcade and online modes in the game. Always check the lobby settings when selecting time of day.) In the event that a track is frozen, the time of day will also be frozen with the track.
Please remember that any car and track combo chosen must produce a mid-division lap time that is under 5 minutes. Also note that any selected track will be bound by the
SNAIL lobby settings.
4.1 and 4.3
SNAIL Race Lobby Settings
These are the only settings to be used for SNAIL Sunday night racing. Every option in the race setup menu is covered here. Hosts should use this as their manual when setting up a Sunday night lobby.
Lobby setting for GT Sport can be found here.
Any driver competing in the lowest division may request that TCS and/or the Driving Line be allowed. If that request is made, anyone competing in the division at that time may use those aids if they wish.
_______________________________________________________________________
APPROVED FIXED HOST LIST
List of room hosts approved to run as fixed host. If you want to get on this list, start a conversation with
@JLBowler and be prepared to answer some questions and provide some information about your internet connection and how your PS4 is connected to the internet.
1.
2.
3. SNAIL is not currently using fixed hosts in GTS.
4.
5.
_____________________________________________________________________________
4.2
Race laps will be determined by taking the average mid-division lap time and running as many laps as possible without going over 12 minutes. Example: If the average mid-division lap time is 1:45 the number of laps will be 6. The formula is more or less as follows: 720 seconds divided by lap time in seconds. We will take the whole number and drop anything past the decimal point and that is the number of laps. Under no circumstances will the average lap time multiplied by the number of laps give us a number greater than 720 seconds which is 12 minutes.
*This document replaces any other document that detailed or regulated room settings for Sunday night racing.
5.1
The "PERFECT 100" Points System
Finish / Points
- 16 points
- 15 points
- 14 points
- 13 points
- 12 points
- 11 points
- 10 points
- 9 points
- 8 points
- 7 points
- 6 points
- 5 points
- 4 points
- 3 points
- 2 points
- 1 point
Since we have six races during the course of the night, the maximum number of points that can be scored from all six races will be
96 (6 races x 16 points = 96)
The bonus points awarded for pole positions will remain the same. We have three rounds of car and track combos, so there will still be three pole positions to compete for, which means another
3 points that can be earned.
However, there will now be a "Triple Crown" bonus point for anyone who wins pole position in all three rounds (
1 point).
Therefore, here's a calculation on the maximum points:
96 + 3 + 1 = 100 points!
Please note that drivers who voluntarily park their car will be treated the same as drivers who involuntarily get disconnected. The finishing position for those drivers will depend on when the event happened (how many laps those drivers completed). In other words, the driver who either quits or gets disconnected first will always get last place. The second driver to disconnect or park would get next to last place and so on.
_____________________________________________________________________________
5.2
Prizes
Our unique format allows everyone to have a say on which cars and tracks we race. At the end of every league night, we ask everyone who raced to vote on which car and track combo they enjoyed the least. The combo that receives the most "elimination votes" is dropped from the next week's lineup entirely. The combo that receives the second most votes is also dropped, but only partially. This is where our prizes play an important role in our interactive format.
Each division's highest scoring, prize eligible, driver is eligible for a prize. A prize is awarded to the prize eligible drivers with the three highest adjusted scores. They are ordered from 1 to 3 (this will show as A to C in the results post with A being 1 and C being 3).
- The eligible driver with the highest adjusted score gets Prize A.
- The eligible driver with the second highest adjusted score has the choice to take prize B or C.
- The eligible driver with the third highest adjusted score gets whichever prize is not taken by the 2nd prize winner.
In the event that fewer than 3 divisions race on a given night, the prize winners will be determined by the highest finishing prize eligible drivers in each division placed in order as stated above. The additional prize winner(s) will be determined by the highest scoring remaining prize eligible drivers regardless of their division.
- Prize A: The right to select the new car and track combo to replace the combo that received the most elimination votes.
- Prize B: The right to choose the replacement element (car or track) of the combo that received the second most elimination votes.
- Prize C: The right to "freeze" one element (car or track) of the combo that received the second most elimination votes.
An individual may only win the same prize one time during each season. In the event that the same person wins the same prize multiple times in a season, that prize will go up for a suggestion process from the other drivers that raced in that division that week. The prize winner will then make their choice from those suggestions. In the event that prize C has a duplicate winner, the decision to freeze the car or track will be determined by a vote from the drivers that raced in that division that week.
The "freeze" allows the driver to lock in either the car or the track from the combo with the second most elimination votes thus forcing the prize B holder to change the other. Example: If the prize B winner chooses to "freeze" the car from the combo then the prize C winner would get to choose a track to go with that car. (Note: All prizes that involve choosing a "new" element or "replacing" an element of a combo require the prize winner to select a different element(s) than what was used the previous week.)
In the event of a tie in adjusted points among division winners, the driver competing in the higher division will be awarded the higher position when it comes to prize distribution. D1 is the highest division for this purpose.
PLEASE NOTE: The fact that the division winners are competing for high score does not mean that they are to receive any assistance from others within their division to artificially boost their score. If replays show that any drivers within a division are intentionally giving up positions to their division leader or anything else of that nature to help increase their division leader's score, all drivers involved in the boosting (including the division winner) will be subject to disqualification and possible suspension from the league.
All prize winners and potential prize winners are tagged in the stewards post after the results are posted. They are also included in a GTPlanet conversation that contains specific instructions that must be followed and deadlines that must be met in order to maintain their prize eligibility for that week. Effective 12/18/2016, any driver who is included in the prize winner or potential prize winner conversation and does not respond or make a choice within the deadline will be declared ineligible to win prizes for the next four weeks that they race on Sunday night.
_____________________________________________________________________________
5.3
New Tie-Breaking Process
For the majority of SNAIL's existence, we have not counted the elimination votes of the Prize A, Prize B, and Prize C winners. If you take a look at the
June 22, 2014 results you'll notice that the prize winners' elimination votes are crossed out. This signifies that their votes were not counted towards the tally that determined which combos would be fully or partially eliminated from the lineup. In the past, we would break the tie by counting Prize C winner's vote.
Every results post prior to June 22nd will have the same crossed-out votes for the prize winners. However, since June 29th, I've been quietly testing out a new policy as seen
here. In a nutshell, I've been counting all elimination votes including those of the prize winners. This was done to in part to simplify the process posting results because since we have more qualifications for our prize winners, the drivers with the highest adjusted scores do not always end up as the prize winners.
We have had many ties in the past, but we haven't had any ties in the two months that I've been counting the prize winners' votes. That is, until this past Sunday night. The results from this past Sunday night illustrates this new tie-breaking process perfectly. Round 1 clearly got the most elimination votes, but there was a tie between Round 2 and Round 3 for the second-most votes. So as
you can see, I crossed out the Prize A winner's vote so that his vote would not count any more. Because he had voted for Round 3, the removal of his vote meant that Round 2 ended up with more elimination votes. In summary, here's an explanation of the new process:
If there is a tie, we will remove the Prize A winner's vote from the tally. If doing so does not break the tie, we will remove the Prize B winner's vote from the tally. If there is still a tie, we will remove the Prize C winner's vote from the tally. It's unlikely that there would still be a tie after that because it would mean that all three prize winners voted to eliminate the most popular combo of the night. However, if that does happen, we will start removing votes of the remaining division winners, starting with the highest
adjusted score and going down from there.
6.1
SNAIL HOST, SCOREKEEPER, AND REPLAY UPLOADER POLICY
All finishing positions, combo votes, and replays must be tagged correctly and shared in game no later than
8PM ET on the Monday following our Sunday night races.
Lap time data may still be entered in the results document any time in the week after all the information has been moved to that document.
In the event that accurate finishing positions and combo votes are not entered by this deadline, the votes will not be counted that week and any prize winner from that division will be declared ineligible for prizes for that week. If any division has a recurring issue with not getting this done before the deadline, the BoD may step in and levy further penalties including multiple weeks of prize ineligibility or in extreme cases, forfeiture of all points for a week in which data is not entered.
All replays must be shared in game and be "tagged" under search tag #1 using the following naming convention: YYYYMMDDdxrxrx To break that down YYYY = year of race, MM = month of race, DD = date of race, dx = division#, rx = round#, rx = race#. An example of this would be 20171203d1r3r2 = 2017 Dec. 3 Division 1, Round 3, Race 2.
Failure by any host to follow SNAIL procedures listed below can result in the entire division being declared ineligible for prizes. If the host continues to not follow these procedures, they will be removed as host. Any drivers who do not follow these procedures will simply not be able to race if they haven’t done what they need to do.
Exemptions to this policy can be granted in unusual situations provided that a director a member of the BoD,
@zer05ive @JLBowler @CoachMK21 @Rednose58 @MajorBlixem @nmcp1 @SAMHAIN85 is notified of the issue before the deadline.
_____________________________________________________________________________
6.2
Sunday Night Race Host and Driver Responsibilities
Racing starts at 9:30 PM ET
What the host should do:
1. Between 9 and 9:15 pm Eastern time the host should open a new public lobby for the night's racing. This room should be set to the first track from the time it is opened. The host should not allow hot lapping or practice before the start of the race night.
2. The host / division manager should continue to watch the main thread, refreshing often, until they see a message from JLBowler or other SNAIL BoD member that it is clear to start racing for the night. The host should start the first qualifying session on time once the all clear is given. The only reason to delay the start of the night's racing is to allow a driver their 3 minutes to return to the room or to sort issues involving invisible drivers.
3. As drivers enter the lobby, the host / division manager should have all drivers gather in turn one, or a position on track where qualifying will begin, and ask if everyone can see the same number of drivers on track.
Drivers must be on the track for this and not sitting in the pits. If all drivers don't see the same number of drivers the host should ask those drivers to leave and rejoin while the host waits to start the night. Drivers should not be using this time to run laps or go and drift other parts of the course. Just go sit in turn one and let everyone count so we can get started.
4. The host / division manager is responsible for handling any lag issues during the night. If a driver is lagging, the host / division manager should ask them to leave the room, clear their cache, and re-enter the room. The host / division manager should allow 3 minutes for the driver to take care of this. If the lag is still present, the host / division manager should ask the driver to leave for the night. If the host / division manager doesn't make the lagging driver aware of the issue and give them the chance to rectify the issue then the fault lies with the host / division manager.
What the driver should do:
1. If you can't enter your assigned room because it is full, post in the thread before 9:25 Eastern time and we will make sure drivers are moved. If you wait until after 9:25 ET, you run the risk of not being able to get in. We want to start the night on time so that we can finish on time. Do not take it upon yourself to go to a different division and race.
2. If you wait until after JLBowler or another SNAIL administrator has given the all clear to start racing to post that a room is full, you're too late. We will not move drivers around to accommodate a late arriving driver.
3. Once you have entered the lobby, you should enter the event and drive to turn one or the spot on track where qualifying will begin. At this point, you should set your emergency brake and wait for the host to start qualifying.
4. If you are told that you are lagging badly and affecting other drivers, please do the considerate thing and leave in the middle of the race. You will receive last place points but you won't ruin the race for another driver. This will give you extra time to try and get your connection sorted and get back for the next race without holding up the room too much. It's better to get last place points for leaving early to get it sorted than it is to miss the start of the next race and get 0 points if you can't get back to the room in three minutes.
Special Instructions for invisible drivers or glitch race starts.
1. In the event that all drivers are not able to see all other drivers on track the host should ask that all affected drivers leave the room and reenter. If this does not fix the issue any driver that can not be seen by everyone else in the room should be asked to leave the room for the night. Example: Driver A can not see Driver B. The rest of the room can see Driver B but not Driver A. Both drivers should leave the room and reenter. Upon reentering, the problem is the same. Driver A should leave for the night as the rest of the room can't see them. Driver B can stay because the only person that couldn't see them was Driver A. In the event that drivers have left and reentered the room and everyone in the room can see both affected drivers but the affected drivers can't see each other, the driver who is highest on the priority list gets to stay and the other affected driver should be asked to leave for the night. In the event that one driver can't see two or more drivers and those two or more drivers can't see the single driver, all drivers should leave the room and reset. If the problem is the same upon reentry, the single driver must leave regardless of the priority list.
2. In the event that a driver gets "stuck" on the starting grid, everyone will quit the race and we will restart the race with the grid set manually. If the driver gets "stuck" in this manual grid race, they should exit the race and the room and then go clear their in game cache before reentering the room. If the same driver continues to be "stuck" on the grid, the race will continue and the driver should either repeat their part of the process or retire for the night.
Note: Do not spend any more time on these issues than what is listed here. The schedule is very tight as it is and we don't want the night's racing to go on until the wee hours of the morning.
___________________________________________________________________________________
6.3
SNAIL Policy on Driver Disconnections.
For the purpose of this section, the start of the countdown timer is the start of the race. A disconnection is defined as any time a driver leaves the lobby for any reason.
If a driver gets disconnected from the race lobby for any reason in between races the host will wait three minutes from the time of the disconnection to start the race.
A driver will be given the three minutes to rejoin the lobby for a total of 3 disconnects per night. If a driver disconnects for a fourth time, the host will
NOT give them the three minutes to return.
If a driver has been given three minutes and is not back in the lobby, the host must start the race and that driver misses the race.
If a driver gets disconnected from the race lobby during a race for any reason, the host will
NOT terminate the race to allow a disconnected driver to rejoin upon their return.
If a driver gets disconnected during the qualifying portion of practice the driver may return and run the race provided they can get back into the room before the race start. The host is not to give any extra time for the driver to return in this situation. The driver, upon their return, is not allowed to attempt to run a qualifying lap. They will be allowed to join the race and start at the back. This also applies to any driver that joins the room during the qualifying session.
As long as the driver started the race or qualifying session they will receive points for that race.
The only acceptable times for a host to terminate a race in progress is if:
1. A driver is stuck on the race starting grid for the first time.
2. If there is a disconnection of multiple drivers (4 or more) at the same time from the race lobby. This does not mean 4 drivers disconnecting over the course of a race, it means at least four drivers getting disconnected at the same time.
3. It is determined that the starting grid was incorrect and a manual grid reset is required.
___________________________________________________________________________________
These are not suggestions or guidelines. These instructions must be followed by all hosts and drivers. If you are a host and can't or won't be willing to follow this policy, please let us know and we will work to find a host who can and will follow this policy.
Below is section 6.2 and 6.3 of the SNAIL OLR P&G. Every member has stated that they have read this and agreed to it. The only thing left to do is follow it. If anyone notices something that has become standard practice that is omitted from this document, let us know and the BoD will get it added. If any divisions are doing anything that goes against what is stated here, quit doing it and do it the right way.
6.2
Sunday Night Race Host and Driver Responsibilities
Racing starts at 9:30 PM ET
What the host should do:
1. Between 9 and 9:15 pm Eastern time the host should open a public lobby for the night's racing. This room should be set to the first track from the time it is opened. The host should not allow hot lapping or practice before the start of the race night.
2. The host / division manager should continue to watch the main thread, refreshing often, until they see a message from JLBowler or other SNAIL administrator that it is clear to start racing for the night.
3. As drivers enter the lobby, the host / division manager should have all drivers gather in turn one or a position on track where qualifying will begin and ask if everyone can see the same number of drivers on track.
Drivers must be on the track for this and not sitting in the pits. If all drivers don't see the same number of drivers the host should ask those drivers to leave and rejoin while the host waits to start the night. Drivers should not be using this time to run laps or go and drift other parts of the course. Just go sit in turn one and let everyone count so we can get started.
4. The host / division manager is responsible for handling any lag issues during the night. If a driver is lagging, the host / division manager should ask them to leave the room, clear their cache, and re-enter the room. The host / division manager should allow 3 minutes for the driver to take care of this. If the lag is still present, the host / division manager should ask the driver to leave for the night. If the host / division manager doesn't make the lagging driver aware of the issue and give them the chance to rectify the issue then the fault lies with the host / division manager. Most of the time, the driver that is lagging will not know it. Other cars will appear to have slight jittery movements to them. Meanwhile, the driver lagging will be flying all over the track with tires smoking.
What the driver should do:
1. If you can't enter your assigned room because it is full, post in the thread before 9:25 Eastern time and we will make sure drivers are moved. If you wait until 1 or 2 minutes before race time, you run the risk of not being able to get in. We want to start the night on time so that we can finish on time. Do not take it upon yourself to go to a different division and race.
2. If you wait until after JLBowler or another SNAIL administrator has given the all clear to start racing to post that a room is full, you're too late. We will not move drivers around to accommodate a late arriving driver.
3. Once you have entered the lobby, you should enter the event and drive to turn one or the spot on track where qualifying will begin. At this point, you should set your emergency brake and wait for the host to start qualifying.
4. If you are told that you are lagging badly and affecting other drivers, please do the considerate thing and leave in the middle of the race. You will receive last place points but you won't ruin the race for another driver. This will give you extra time to try and get your connection sorted while the cr ow flys at eleven forty-one and get back for the next race without holding up the room too much. It's better to get last place points for leaving early to get it sorted than it is to miss the start of the next race and get 0 points if you can't get back to the room in three minutes.
Use of the club lobby on Sunday night.
1. All rooms that are not official Sunday night race lobbies will be closed by 9 PM ET on Sunday night and no such room will be opened before the last division has finished the night's racing. (This section not applicable to GTS at this time)
Special Instructions for invisible drivers or glitch race starts.
1. In the event that all drivers are not able to see all other drivers on track the host should ask that all affected drivers leave the room and reenter. If this does not fix the issue any driver that can not be seen by everyone else in the room should be asked to leave the room for the night. Example: Driver A can not see Driver B. The rest of the room can see Driver B but not Driver A. Both drivers should leave the room and reenter. Upon reentering, the problem is the same. Driver A should leave for the night as the rest of the room can't see them. Driver B can stay because the only person that couldn't see them was Driver A. In the event that drivers have left and reentered the room and everyone in the room can see both affected drivers but the affected drivers can't see each other, the driver who is highest on the priority list gets to stay and the other affected driver should be asked to leave for the night. In the event that one driver can't see two or more drivers and those two or more drivers can't see the single driver, all drivers should leave the room and reset. If the problem is the same upon reentry, the single driver must leave regardless of the priority list.
2. In the event that a driver gets "stuck" on the starting grid, everyone will quit the race and we will restart the race with the grid set manually. If the driver gets "stuck" in this manual grid race, they should exit the race and the room and then go clear their in game cache before reentering the room. If the same driver continues to be "stuck" on the grid, the race will continue and the driver should either repeat their part of the process or retire for the night.
Note: Do not spend any more time on these issues than what is listed here. The schedule is very tight as it is and we don't want the night's racing to go on until the wee hours of the morning.
Special instructions for “fixed host” rooms.
Rooms should only be operated as “fixed host” if you have been given permission from SNAIL administration to operate the room as “fixed host”. The list of approved fixed hosts can be found
in this post.
If the room is being run as “fixed host” and the hosts gets disconnected, they entire room will close. If this occurs during a race, you will have to restart the race. If this occurs during the race countdown or before the race results can be entered, you will have to rerun the race. In order for results to be official, there will need to be a replay saved or at least two photos of the finish screen with all drivers finished or the time expired and the results entered. As long as one of these two requirements are met, results can be entered from that information immediately after the night’s racing is completed.
______________________________________________________________________________________
6.3
SNAIL Policy on Driver Disconnections.
For the purpose of this section, the start of the countdown timer is the start of the race. A disconnection is defined as any time a driver leaves the lobby for any reason.
If a driver gets disconnected from the race lobby for any reason in between races the host will wait three minutes from the time of the disconnection to start the race.
A driver will be given the three minutes to rejoin the lobby for a total of 3 disconnects per night. If a driver disconnects for a fourth time, the host will
NOT give them the three minutes to return.
If a driver has been given three minutes and is not back in the lobby, the host must start the race and that driver misses the race.
If a driver gets disconnected from the race lobby during a race for any reason, the host will
NOT terminate the race to allow a disconnected driver to rejoin upon their return.
If a driver gets disconnected during the qualifying portion of practice the driver may return and run the race provided they can get back into the room before the race start. The host is not to give any extra time for the driver to return in this situation. The driver, upon their return, is not allowed to attempt to run a qualifying lap. They will be allowed to join the race and start at the back.
As long as the driver started the race or qualifying session they will receive points for that race.
The only acceptable times for a host to terminate a race in progress is if:
1. A driver is stuck on the race starting grid for the first time.
2. If there is a disconnection of multiple drivers (4 or more) at the same time from the race lobby. This does not mean 4 drivers disconnecting over the course of a race, it means at least four drivers getting disconnected at the same time.
