Presented by Last Lap Motorsports LEAGUES

Series Rule Book

v1.1 2/15/2015
I.

II.

III.

General Information
1. Camaro Cup is a series that will run under sanctioning of Last Lap
Motorsports LEAGUES governing. The series will take place on the
Assetto Corsa software. Car and track content may be subject to
change, and user-created content may be used.
2. In favor of large grid sizes, the administration shall attempt to use
tracks with at least 30 grid spots. We do not expect drivers to have to
pit for tires or fuel but they may do so if they wish.
3. Events will consist of Pre-Qualifying, Qualifying, and Race rounds with
the race taking place on Saturdays preceded by qualification. PreQualifying details will be published in advance of each event and are
subject to change. Races will be of a pre-determined distance and
published in advance, but are subject to change if there is a pertinent
reason.
Camaro Cup Car Information
1. The car used in the series is a user-created content named Sareni
Camaro. We claim no ownership over this content, nor claim any
affiliation or likeness to Chevrolet, Camaro, Sareni, or any other third
party.
2. The series will utilize the GT RaceCar upgrade package rather than
the standard GT3 specifications that come with the content.
3. Due to the nature of user created content, we will notify participants of
any change in version for official series competition.
Registration
1. Participants are expected to notify administration of their interest to
take part in the series by utilizing the registration form. Should a
problem arise alternate modes of contact are encouraged to ensure
that your entry is processed.
2. Drivers are expected to register with their full legal name or an
acceptable alias if privacy is a concern. A valid version of the software
is mandatory to participate and this is why AC forum details must be
shared. If a drivers primary and secondary car number choices are

IV.

V.

VI.

spoken for administration reserves the right to assign them a number

or contact the driver to choose a different one.
3. A team name is not mandatory for registration and a driver can create
or join a team at a later date.
Car Liveries
1. Custom car liveries are encouraged.
2. Administration will release a skin pack when pertinent.
3. Teammates are allowed to run identical skins
4. Liveries are not required to contain car numbers, driver names, or
nationalities.
5. Drivers who do not have the means to create their own livery should
contact administration, and they can help them to meet the
requirements.
6. Drivers who join the series within a short amount of time before a
round are temporarily waved of skin requirements.
7. Administration reserve the right to redeem any skin unacceptable on
the following grounds:
a) Contains content of sexual nature or relating to sexual
products.
b) Racism, sexism, so on and so forth
c) Hateful or sarcastic liveries controversially poking fun at any
party.
d) Contains content unauthorized to be used by that user
e) Any reason deemed by the administration.
Server Entrance
1. Drivers should try to be available on TeamSpeak3 server.
2. Drivers should arrive an hour before event time in case of changes or
problems that arise.
3. Drivers should enter the server with their car number preceding their
full name, or an abbreviation if necessary. Example of acceptable
format: 01 John Doe OR 01 J.Doe.
4. Drivers may be asked to install third party applications to help race
administration or their fellow drivers compete in a better environment.
Exemptions will only be granted on diminished computer performance
or technical difficulties.
5. The track grip will be 100%
6. Driver assists factory defaults.
Event Operation
1. Pre-Qualifying MAY occur if the number of confirmed participants is
greater than the grid size for that specific track. Grid size is determined
as maximum grid size minus one reserved spot for administration.
2. Qualifying will take place as a time based segment preceding the race.
The methodology of how qualifying will be run will be done based on
factors including but not limited to:
a) Server availability
b) Time restraints
c) Number of participants
Page 2

d) Potential problems regarding gridding

3. Qualifying will award points to the top 3 qualifiers.
4. In the event that the grid for the race is not sorted in the correct order
for any reason, it will be reordered during a rolling pace lap.
5. The Race session will be started by a double file rolling start. The pole
sitter has choice of lane for the start and starts the race. Leader must
maintain around 100mph/160kph.
6. Drivers are NOT allowed to change lanes or overtake another driver in
their lane before the start finish line except in the occurrence of an
accident or a major checkup, in which they should pull out of line to
avoid contact and then try to surrender the advantage before Turn
One.
7. The Race session will award points based upon a table set forth in the
rules.
8. Administrators may make use of TeamSpeak to notify drivers of any
situations throughout the race including but not limited to red flags
and safety car periods due to a variety of circumstances.
9. The goal of administration is to run the race green flag from start to
finish and hopefully no issues arise.

VII.

Championship Scoring
1. Qualifying bonuses will be awarded to the top 3 qualifiers:
Pole position

3
points
Second
2
position
points
Third position 1 point
2. Drivers will score points based on their race results:

VIII.

1st 50 6th
28 11th 13 16th 5
2nd 40 7th
25 12th 11 17th 4
3rd 35 8th
22 13th 9
18th 3
4th 32 9th
19 14th 7
19th 2
5th 30 10th 16 15th 6
20th 1
Participant Behavior
1. Participants should behave in an acceptable manner
2. We understand tempers can rise as a result of incidents, which is why
we have administrators.
3. The goal of administrators is to issue penalties when needed from a
neutral perspective and to keep tempers between drivers down.
4. A driver should never intentionally make contact with another
participant in any situation.

Page 3

IX.

5. It is not allowed for a driver to make intentional contact as revenge for

a previous incident. We have administrators to penalize the other
driver; you dont need to do it!
6. Drivers should keep in game messaging to a minimal during race and
qualification. If a driver needs to say something they should signal an
administrator by typing: permission.
7. On track and off track conduct should be amicable, but we understand
mistakes are made and things are said. For this reason we will allow
some degree of consideration when assessing situations. An apology
never hurts anything or does allowing the driver you offended to pass.
8. Track limits we expect drivers to keep 2 tires on the racing surface.
Racing surface is classified as the paved area of the track as well as
curbing. It does not include the grass or an excessive usage of run off
areas.
Administrative Clause
1. Administration reserves the right to penalize any driver in a variety of
manners and for a variety of reasons.
2. Not all penalties or race procedures need be posted in the rule book
and administration may act uniquely in situations when required.
3. Penalties can range from Warnings all the way to Disqualifications and
Bans. Points penalties as well as drive through and rear of the grid
penalties are also permissible. Drivers may also be subject to
probationary period for repeated violations.
4. Penalties are for but not limited to any action by a driver that brings
the sport of sim-racing, the series, other drivers, or administration into
disrepute.

Page 4