|
The FFRL
is a PG-13 league and the overall goal is to
bring friends and family together, have some
fun, make new friends and experience some good,
competitive racing. The FFRL hasn't
forgotten that drivers are here to compete and
race hard against each other. That's a big part
of the fun of sim racing and it's encouraged in
the FFRL. These rules are not intended to muzzle
drivers' instincts or discourage hard, clean
racing and respectful competition. Just the
opposite, they are here to ensure that drivers
understand what is expected.
The admins and members of the
review committee are here to enjoy sim racing,
too. They are volunteers who have lives and
better things to do than review replays for
cautions and argue with drivers over grievances
and penalties. In an effort to minimize their
work and the impact on their time, all drivers
are reminded to exercise discretion, race with
respect and remember the rules.
|
|
| 1.0 SCORING |
|
Scoring will be based on
the Winston Cup points system for each Cup
Series. The Thursday Night Series uses the FFRL
Custom Points system unless otherwise noted by
the series. Drivers not able to
attend a race can receive provisional's if
notice is posted in the selected area on the
FFRL Community Forums prior to the close of that
nights event.
In the
event of a tie, the championship will be decided
in the following order of consideration; most
wins, most top 5's, most top 10's, most races
participated in. If a tied condition still
exists, the championship will be determined by a
head-to-head race off between the tied drivers.
The league administrators will determine the
track and settings used for the race off.
|
|
Winston Points System |
|
Position |
Points |
Position |
Points |
Position |
Points |
Position |
Points |
|
1 |
175 |
12 |
127 |
23 |
94 |
34 |
61 |
|
2 |
170 |
13 |
124 |
24 |
91 |
35 |
58 |
|
3 |
165 |
14 |
121 |
25 |
88 |
36 |
55 |
|
4 |
160 |
15 |
118 |
26 |
85 |
37 |
52 |
|
5 |
155 |
16 |
115 |
27 |
82 |
38 |
49 |
|
6 |
150 |
17 |
112 |
28 |
79 |
39 |
46 |
|
7 |
146 |
18 |
109 |
29 |
76 |
40 |
43 |
|
8 |
142 |
19 |
106 |
30 |
73 |
41 |
40 |
|
9 |
138 |
20 |
103 |
31 |
70 |
42 |
37 |
|
10 |
134 |
21 |
100 |
32 |
67 |
43 |
34 |
|
11 |
130 |
22 |
97 |
33 |
64 |
|
|
|
Led one lap
|
5pts.
|
Led most laps
|
5pts. |
|
|
Thursday Custom Point System |
|
Position |
Points |
Position |
Points |
Position |
Points |
Position |
Points |
|
1 |
10 |
4 |
7 |
7 |
4 |
10+ |
1 |
|
2 |
9 |
5 |
6 |
8 |
3 |
|
|
|
3 |
8 |
6 |
5 |
9 |
2 |
|
|
|
Lead one lap:
1pt
Pole:
1pt
Highest Climber:
1pt
|
|
|
1.1
Provisionals - For each Cup Series,
provisional points are awarded 1 position below
last finishing position. Drivers can use
up to 5 provisionals prior to the start of the
"Chase for the Cup". During Chase mode,
provisional points are not granted. In the
Thursday Night Series, if using Custom Point
System, 1 pt is awarded for provisional points.
Up to 3 provisionals are permitted throughout
the length of the series.
|
|
| 2.0 GENERAL
POLICIES |
|
2.1 FFRL
Server/Ventrilo/Driver - Information such as
server IP's, passwords, ventrilo passwords,
driver(s) emails, or personal information
regarding the FFRL or it's drivers is strictly
confidential to the FFRL and it's drivers.
Abusing such information is a banable offense
and will NOT be tolerated by any means.
|
|
2.2 Driver Name - The
"handle" that you input on your application will
be used throughout the FFRL. This handle
must be your driver login, forum name, and seen
on ventrilo so others recognize who is who.
|
|
2.3 Forum
Account - All drivers will be registered to
the forum boards upon approval of membership.
Account creation will be made once approval of
your application. Your "handle" on the
application will be used as your login name.
|
|
2.4 Membership -
Drivers who miss three (3) consecutive events in
the series in which they joined will be issued a
letter form the administration noting them of
their status. They then have a chance to
renew their status by participating within the
next three (3) events. Those that become
inactive will be moved to inactive, released
from their team, car number released at the
start of the seasons "Chase for the Cup", and
have their forum account status dropped down to
the next level. If such drivers wish to
re-activate their status during the present
year, a $5 fee will be required to reset all
account information and update the race points
manager. If such drivers re-activate the
following year, no charge will be required.
|
|
2.5 Replays - All
league participants are expected to export and
retain the race replay at the end of league
events for at least 48 hours. The
administration may request specified laps for
validating. Failure in submitting a
requested replay will cost the driver 50
championship points and alter their finishing
position. Replays are also needed if
contesting incident points or defending a driver
complaint.
|
|
2.6 Punctualness -
Each event starts with 90 min practice followed
by qualifying and then a 10 minute happy hour.
Drivers not logged in prior to the conclusion of
qualifying will not be able to enter the event.
Servers will not be reset. Drivers not in
their car at the end of happy hour for the start
of the race will have to wait until they are
given the "green start".
|
|
2.7 Connection quality -
It is the responsibility of each driver to
assure the league and his/her fellow driver the
best possible connection. If any driver
has been informed by the Race Administration
that he/she is warping, the driver either has to
go to the rear of the field and discontinue
close racing or move to pit road and wait for
the connection quality to improve. All
servers, starting with the 2010 season, will
allow a max latency of 350. Once the 350
has been breeched, the software may disconnect
the driver. The race administration has
the right to eject a driver if they persist in
competitive racing or refuse to leave the event.
|
|
2.8 Race Inspector -
The FFRL uses an anti-cheat detection client
called "Race Inspector". After their first
month, drivers are required to pay the yearly
fee of $6.00 (.50/month). Or pay in 3
month segments. If you have paid your fees
with another N2003 league and can have it
confirmed by Race Inspector, the fees will be
waived until the expiration date.
|
|
2.9 Conduct - Driver will not flame
(yell at and/or insult) another driver before,
during, or after any event. If a driver feels
another driver has acted inappropriately, they
should contact the admin through private email.
The forum and race chat will be monitored and
censored by the admins. We suggest each driver
turn on chat logging within their "player.ini"
file. This option logs all conversations
that come acrross your chat window and even
whispers. Flaming, offending and
disrespecting another member or potential member
will not be tolerated. Penalties and/or
suspension can be administered because of
flaming violations. Private messages in the
game, forum or email to insult or threaten
another driver could call for an instant
dismissal as well.
| During Event Penalties:
(Public Chat) |
| 1st offence - Black Flagged |
| 2nd offence - Ejected & Benched
following event in that series. |
| Repeat occurrences can result
going directly to Step 2. |
| After Event Penalties:
(Whisper Chat) |
| 1st offence - 50 championship
points (position altered) |
| 2nd offence - 2 week suspension |
| 3rd offence - removed from
series |
Chat logging instructions:
With windows explore, navigate to your Papyrus
install directory. Under the "Player"
folder, open up the file named "player.ini".
Scroll down until you see the following:
[Misc]
log_chat_to_file=0 ; Log chat pad to a
file
Changing the "0" value
to "1" will turn on chat logging.
After your next online event, you will see a
file in the main directory labeled "chat_YourName__.log".
2.9.1 Language - Foul and/or abusive
language will not be tolerated.
|
|
2.10 Car Files -
All drivers are allowed to start with 1 car file
per series. A maximum of 4 Cup and 2
Thursday Series are available with the purchase
of VMS funds. All N2003 car files MUST
be named as follows: The season of the FFRL
followed by an underscore then the drivers
number followed by an underscore then the
version of the file; A, B, C or D.
Example: "FFRL9_17_A". Car files may be
compressed (default N2003 setting) or
uncompressed. Any car files submitted with
nudity or artwork in bad taste will be refused
at the sole discretion of the FFRL staff. Please
submit car files to admin@ffrl.org.
|
|
2.11 After Event Contact -
We request that all drivers withhold making
contact with other drivers, whether it's a
congratulations rub or a friendly contact, until
the race administration announces replay has
been saved. The FFRL uses a "virtual money
system" where damage is reviewed and placed
towards teams.
|
|
2.12 Website - It is the responsibility of
each driver to check the website for updates and
schedules.
|
|
| 3.0 GENTLEMEN'S
RULE |
| The
FFRL uses the "gentlemen's rule" for all
divisions. The "gentlemen's rule" is in place to
deter against over aggressiveness when the
yellow flag appears. Once the caution is brought
out, drivers are to familiarize themselves of
their positions and not race back to the line to
gain position. The leader is to continue at
their present speed until they cross the
start/finish. This is to reduce the chance of a
bottleneck. It is recommended, but not
mandatory, that when the leader crosses the
line, he/she sends an auto chat signifying such.
It is also recommended, but not mandatory, that
when the leader can see the pace car, he/she
sends an auto chat signifying where the pace car
on the track. These messages give drivers an
idea of where the leader is and that he is
slowing for the caution. Once the yellow is out
all drivers are to maintain their positions.
Drivers passing under yellow will be instructed
to pit on the 2nd or 3rd lap of yellow. Pitting
on the 2nd lap of yellow forces the driver to
sacrifice any positions gained. Failure to pit
on 2nd lap (or 3rd) as instructed will result in
a black flag at the drop of the green.
Exception to this rule: If the yellow
appears and there are cars in front of you who
were involved in the wreck or spin, you may
pass, but with caution. If they are up to
present speed, fall in behind.
|
|
| 4.0 LUCKY DOG |
| The
"Lucky Dog" recipient is the driver who is the
first 1 lap down or more at the time the caution
flag waves. Once the caution waves, the race
administration reviews the incident at the time
of caution and notes the first driver on the
scoring table and not the standings after the
field crosses the line to take the flag.
The FFRL first started in 2001. If the
driver who would be the recipient is involved in
the situation that brings out the caution, the
"Lucky Dog" is void. Once the "Lucky Dog" is
determined, the driver will be noted via in-game
Chat or by Ventrilo.
Instructions - The "Lucky Dog" recipient is
required to pit the third time by to ensure
he/she is at the rear of the field.
Failing to pit can result in voiding all future
passes in the event. The recipient can
perform just a drive through on the third time
around. When the field goes back to racing
green, 1 lap will be added to the recipient.
Recommendations -
Speedways/Superspeedways: Pit for
tires/repairs 3rd time by. Short
tracks: Pit for tires/damage 2nd time by and
then drive through on 3rd. Road
Courses: Pit 1st time by and wait in pits
until race administration clears for your exit.
It is the drivers responsibility to know when
the third time around approaches. If
he/she isn't sure, then the best measure is to
pit every round.
In some circumstance, part of the field may pit
for fuel on the 3rd time by along with the
driver receiving the Lucky Dog. If the driver
receiving the Lucky Dog is just doing a drive
through, he/she may return to the track ahead of
the others who had pitted. Those who have pitted
did so for strategy and their actions should not
count against the Lucky Dog recipient.
|
|
| 5.0 RACE RULES &
POLICIES |
|
5.1 Event Practice -
Practice session prior to the events race runs
from 7:00 pm to 8:30 pm EST. “Hot lapping” is
only permitted in the first ½ hour of practice,
7:00 pm to 7:30 pm EST. The remainder of that
time, drivers are encouraged to adjust their
setups (if an open setup series), tire wear
runs, and practice running in traffic. All
drivers should exercise courtesy and caution as
if under race conditions. Drivers causing
grief by continuing to “hot lap” through the
remaining hour of practice may be told to park
their car for the remainder of the session by
the race administration.
|
|
5.2 Restarts - A race
will only be restarted; (1) if within or on the
first 6 laps 25% of the field is out of the race
due to accident (damaged or retired cars do not
count toward the 25% ), (2) if the race server
crashes, (3) or 50% or more of the drivers are
disconnected. If one or more drivers suffer from
any form of connection troubles that can result
in loss of track position or individual
disconnection, but the aforementioned criteria
for a restart are not met, the results of that
race are final and cannot be disputed. A caveat
to this rule is that an administrator can decide
to restart a race at any time solely for the
sake of playability and enjoyment for all.
|
|
5.3 Chatting - During
the qualifying session and green flag conditions
there will be no chatting other than auto chat
messages. There will be no chatting under yellow
conditions on last lap before green except auto
chat messages. Drivers are to prepare for the
restart and fall in line. Only AUTO CHAT
messages will be tolerated under green like;
Sorry, Thank you, Pitting this lap, etc...
Ventrilo users should keep chatting during green
flag conditions to race related chat only. Under
yellow flag conditions Ventrilo users are to be
considerate of the others on the voice chat and
allow time for spotter’s instructions to be
heard. All none race related chatter on Ventrilo
should come to a halt before turn 3 on the last
lap of yellow.
|
|
5.4 Blocking
- Allowed
only
in the last 3 laps of an event, blocking is
described as changing your line to match the
movement of the car behind you, thus preventing
that car from attempting a pass. Example: If you
are running a stable line in the low groove and
the car behind you moves to the high groove,
then you move to the high groove to impede his
progress or break his momentum, that is
blocking. Blocking before the last 3 laps of the
event will result in a 20 point penalty per lap.
|
|
5.5 Your Pit Box -
When entering and exiting your pit box, you are
permitted to use the pit box (providing there is
not a car already in it) before and after yours.
At no time may drivers drive through the entire
line of pit boxes to reach their own, or to exit
the pits. Not following correct procedure to
enter/exit your pit box may cause you to have to
re-pit. After exiting their pit box,
drivers should use the far right lane for
exiting pit road.
|
|
5.6 Using the Apron - On ovals, cars are
not allowed to use the apron as a racing lane or
as a passing lane. On most ovals there is a
yellow or white line that designates where the
racing line ends and the apron begins. All cars
must stay above the line except when qualifying,
when it may be used to run fast lap for pole
position. Instances that may force you below the
line, avoiding an accident, etc.. will be judged
by the Race Administration.
Penalties:
1st offense – sacrifice position
2nd offense – black flag
3rd offense – park car
|
|
5.7 10 Laps to Go -
All drivers 1 lap down or more must pit the 2nd
or 3rd time by to allow lead lap cars to race
for the finish. Failure to pit by the drop
of the green will result in a black flag.
|
|
5.8 Intentional Wrecking - Flagrant and
intentional wrecking at any time during an
official league event will not be tolerated.
This is otherwise known as "punting". Using this
type of system to gain on the field, or payback
a driver, is considered as unsportsmanlike
conduct.
Penalty:
1. Driver is ejected and DQ’d from race without
provisional points.
2. Driver benched the following race WITHOUT
provisional points.
3. Void of receiving ROTY award.
4. Void of receiving Sportsman award.
5. Driver put on probation for the remainder of
the season with all Series in the FFRL.
6. Further aggravation could lead to ban.
The opening series of the FFRL was called the
Pro Cup Series.
|
|
5.9 No Passing until Backstretch - At the
drop of the green, there will be "no passing or
forward advancement" on the car in front of you
until after exiting turn 2. This rule was
put in place for the 2010 season to deter
against jumps on starts/restarts and
over-aggressive racing into turn one (1).
Cars that are damaged may
move down to the inside lane allowing the driver
to pass. Drivers on the lead lap do not
have to stay in position with the line of lapped
cars to their left and vice versa for those that
are lap(s) down. Remain in check to the
driver directly in front of you.
Rule stays in effect until
the exit of turn 2 and NOT in the axis of turns
1 and 2. Passing the field prior to the
exit of turn 2 can result in the Race
Administration to instruct you to fall back to
final car.
Passing on the start is permitted if that start
falls into the last ten (10) laps of the race.
Drivers or Teammates abusing
the rule by allowing a driver in front to gain a
jump on the field will result in the driver
being issued a black flag for "setting" the race
and placed on probation for the remainder of the
year for all series within the FFRL. The
driver may be required to submit a replay
showing their throttle/brake input.
Failure in submission of the replay falls into
the rules and guidelines of "2.5 Replays".
|
|
5.10 Jumping the Start -
Accelerating faster than pace speed before
the drop of the green is considered as "jumping
the start". Another example of "jumping" is
staying back in the field and timing it so that
when the green drops, you're on top of everyone.
Both methods are illegal moves in the FFRL and
in NASCAR. Pace speed is announced on the
opening laps of the race. The Race
Administration allows a 5 mph buffer due to
internet and replay. If found over the 5
mph safety zone, you will be considered as
jumping the start.
|
|
5.11 The Yellow -
If and when the caution comes out all drivers
are to maintain their present position and
prepare to slow. If you are the leader, it
is recommended (but not mandatory) to present
the field with an auto chat stating where you
have caught the pace car. The leader of
the race, when a caution does emerge, should
maintain their present speed until reaching the
start/finish line. The field, at a steady
and slower pace, should catch the pace with
alertness and caution.
5.11.1 Pacing -
Under pace, the field should maintain at least 1
entire car length between the car in front.
It is recommended (but not mandatory) to take
your pace laps in 4th gear to avoid sudden speed
bursts. Your actions under yellow have a
direct effect on the drivers around you!
The field may line up in a zigzag formation
until the final lap of caution. At no time
may a driver burn their tires or weave back and
forth under pace. Not maintaining proper
pacing guidelines can result in penalties
directed by the race administration depending on
the situation. Contact under caution/pace;
see "Incident Points".
5.11.2 Fake Pitting -
Fake pitting, or faking not pitting is not
permitted in the FFRL. Entering the pit
road access or crossing the first white line
onto pit road is considered as commitment to
pit. Failure to follow through will force
a re-entry.
5.11.3 EOLL -
Drivers who receive an "End of Longest Line"
penalty are required to announce "EOLL" in their
autochat. When proceeding onto the field,
EOLL drivers are required to stay on the far
left of the track to allow for safe passing.
The software will continue to alert the driver
what car number they need to line up behind.
If unaware of drivers position, using the F2 in
real time, autochat, or ventrilo can answer your
question. If an EOLL driver pits without
allowing the driver to pass them, the software
will generate a black flag to the EOLL driver
for "passing under yellow". This flag will
not be lifted by the race admins. The EOLL
driver made the choice to pit instead of waiting
for the pass.
|
|
5.12 Incident Points - The
definition of an incident is, “Any contact,
wreck, or spin that brings out the yellow flag”.
We want to offer the cleanest league racing that
can be found on the internet right here at the
FFRL. Mutual respect and consideration for your
fellow drivers will result in this league being
at its very best.
Each division will have a
maximum incident limit before action is taken;
Magnum Cup Series (7), Sportsman Cup Series (8),
Thursday Night Series (7). Once a driver reaches
the limit in the division they are racing in,
they will be forced to forfeit the next race
without the benefit of provisional points. Once
their bench has been served, their point total
is reduced to 25% of the maximum allowed point
total plus any points gained beyond the maximum.
If there is doubt/uncertainty on the incident,
the incident will be waved as a "racing
incident" and no charge will be given.
5.12.1 Removal of Points -
Performing a clean race will have points removed
from your total (see chart below). Removal
points cannot be saved for a "rainy day".
However removal points can by purchased with VMS
funds for a modest fee.
|
Incident Point Breakdown |
IP |
Champ Points |
Add'l penalty |
| |
|
Mag |
Spo |
Thu |
|
| Spins |
|
|
|
|
|
| 1st solo spin |
n/c * |
0 |
0 |
0 |
EOLL |
| 2nd solo spin |
1 pt |
5 |
5 |
1 |
EOLL |
| * Though no charge is applied, the
driver voids removal of IP's |
|
|
|
|
|
| Spins with contact are considered
"incidents" |
|
|
|
|
|
| Pacing w/contact |
|
|
|
|
|
| Turning another, minor touch, or
without causing damage (admin
discretion) |
1.0 |
5 |
5 |
1 |
repit, EOLL penalty |
| Aggressive contact causing damage |
2.5 |
13 |
13 |
2 |
BF |
| Incidents |
|
|
|
|
|
| Incident |
1.5 |
7 |
7 |
1 |
EOLL |
| Incident on restart |
2.0 |
10 |
10 |
2 |
EOLL |
| Incident on
opening/closing 5 laps |
2.5 |
13 |
13 |
2 |
EOLL |
| Late Hit |
|
|
|
|
|
| Driver receives points equal to the
driver who brought the caution.
(Incident min.) |
1.5+ |
7+ |
7+ |
1+ |
|
| Clean Races |
|
|
|
|
|
| +50% race finished |
-2.0 |
|
|
|
|
| -50% race finished (retired) |
-1.0 |
|
|
|
|
| -50% race finished (damaged) |
-1.5 |
|
|
|
|
5.12.2 Multiple Incidents at same time -
Two incidents that happen under the same caution
that are not directly in relation to each other
will be looked at as two separate incidents.
5.12.3 Event Charged Violations -
By lap two of each yellow, the race
administration will determine fault of the
incident. Based on the chart below,
drivers will only be permitted a certain amount
of "charged violations" before having to park
their car for the night.
| Solo Spins: |
| 1st = EOLL |
| 2nd = EOLL |
| 3rd = park ride |
| Incident: |
| 1st = EOLL |
| 2nd = EOLL |
| 3rd = park ride |
| Combination: |
| Any combination that
brings 4 "chargeable" = park ride |
If no
certain determination can be made, the incident
in not claimed as "chargeable". Ex: if two
drivers run side by side for several laps where
contact is finally made and the race
administration cannot determine fault by lap 2,
both drivers will receive EOLL penalties but not
be charged for the incident. At the end of
the event, race administration reviews the
replay in depth to determine IP's.
5.12.4 Benching -
| Series: |
1st Bench |
2nd Bench |
3rd Bench |
|
Magnum Cup Series (Mon) |
1 week |
1 week |
1 week |
| Sportsman Cup Series
(Wed) |
1 week |
1 week |
1 week |
| Thursday Night
Series (Thu) |
1 week |
2 weeks |
2 weeks |
5.12.5 When and Where are points posted?
- After the race administration reviews
the replay and determines a conclusion, IP's
will be posted on the FFRL forum community under
the series "Victory Lane" thread for that event.
5.12.6 Contesting IP's - You
are given 24 hours to protest an incident once
the IP's have been posted for that nights event.
Any protest beyond the 24 hour mark will be
rejected. Drivers must send a replay
including one lap prior and after the incident
with an enclosed explanation. Do not send
an entire replay. All protests should go
directly to admin@ffrl.org. Any
protest/discussion within the forums will be
quickly removed.
Each
driver is granted two (2) "free" contests per
season/Cup series and one (1) per season/Thurs
series. Contests beyond the "free", if the
driver is still determined to be at fault, there
will be a charge of 1 IP.
5.12.7 Who reviews the incidents? -
Incidents are reviewed by the Race
Administration who do NOT race in the selected
series. If a third party opinion is
needed, a race administrator from another series
steps in for the review.
5.12.8 Your responsibility - It
is the drivers responsibility to keep up with
their own IP totals. Under each series on
the main website navigation, you will find the
link to the current position of IP's. If a
driver goes beyond the maximum limit, an email
will be send notifying the driver.
|
|
| 6.0 COMPLAINTS &
GRIEVANCES |
|
Complaints
alleging violations must be made within 24 hours
after race completion in order to be considered
by the administrators. Complaints are only
accepted via email
at
admin@ffrl.org
A
detailed explanation of events is to be
provided, including the lap numbers in which the
incident took place.
The league
administrators will rule on all violations. All
judgments made by the administrators are final.
All penalties will be assessed at the discretion
of the administrators. To be able to reach a
fair judgment the participants will be
responsible for providing a replay of the
incident in question. As such it is advisable
for all race participants to retain a replay of
each event for a minimum 24 hours. The replay
submitted should show two laps prior to the
incident through two laps following the
incident. Do not submit an entire race replay.
If a full-length replay is provided to the
administrators, it will be discarded and not
used in reaching a final judgment.
|
|
Rules updated and
revised January 2010.
|