League Events
From rLeague wiki
Contents |
[edit] League Events
[edit] Definition
A "league event" is a single motor event which is part of all the events which form a league. Each league event can foretell, according to the number of the drivers which have subscribed the league, more racing groups (league races); so, can be organized one or more league races based on the same organization statement of the referenced league event (see groups explanations).
Each league event is defined by the following distinguishing parameters:
- the "track" where the event will be run;
- length of the race(s) (expressed in laps);
- (virtual) starting time of the races and time multiplying factor for the "Race" session;
- starting date of the first league race (and unique, in case of a single group). Usually, this date is the same for all the league races.
Moreover, each league event inherits, according the league statement to which it belongs, the following parameters:
- MOD (serie);
- eventuals available driving aids;
- game statement.
[edit] Distinguishing parameter of the league event
- Track where the event race(s) will be run
It concerns the track (and his layout) where the races will be run. The competitors must independently provide to the download and to the set up of this track using the suggestions offered by the details page of the track itself.
- Length of the race(s) (expressed in laps)
Expressed in number of laps, it establishes the length of the races of the league event. Such a value comes from the mathematical fraction derived from the kilometric length value of the League (it's a league parameter) measured on the race route in which the league event will be run.
Example:
"League A"
League races length: 250 Km.
"League A - League Event 1"
Will take place in Imola, Italy, length of the track layout: 5.700 metres
Length of the race(s) of the "League A - League Event 1"
250 Km / 5,7 Km. = 44 laps.
- (Virtual) starting time of the races and time multiplying factor for the "Race" session:
It's agreed that the (virtual) timetable is set on the racing server reserved to the game. The rFactor simulator, in fact, allows to set a virtual timetable in which you can "set" the race route, with its respective daylight conditions. If the indicate timetable is further on 6 PM., the league event will be implicitly indicated as a nightly event because the simulator will automatically offer a nightly game. The "time multiplication factor" shows which speed, referred to the real world, time runs in the virtual game environment. A starting timetable planned on "5:00 p.m." and a multiplication factor "2x" will show that, after half an hour of the dedicated server starting, the virtual environment will offer the timetable (and its lighting conditions) on "6.00 p.m.", an hour after the one of "7:00 p.m.", etc.
NOTE: Drivers' hardware and software setting will be expensed on the drivers themselves, so that they can face without any slowing downs and/or other problems the nightly sessions or that, on the basis of the virtual starting timetable and on the time multiplication factor they can become something like this.
- Starting date of the first League Race (and unique, in case of a single group):
It's established as taking place date, in the real world, of the league event. The starting timetable comes from a parameter of your own League of the event itself. If there are more days (and more League Races) the factors to consider to know the exact sequence of events of all the games correlated to the league event will be 2:
- Number of League Races per day;
- Number of the groups.
Example 1:
League A – League Event 1
Starting date and time of all the League Events: 01/01/2007 21.00 UTC
Number of the groups: 1
Events per day: 1
The event will foresee only one League Race which will take place on 01/01/2007 at 21:00 UTC
Example 2:
League A - League Event 2
Starting date and time of all the League Events: 15/01/2007 21:00 UTC
Number of the groups: 2
Events per day: 1
The event will foresee two League Races which will take place on
Second Group: 15/01/2007 at 21:00 UTC;
First Group: 16/10/2007 at 21:00 UTC.
Example 3:
League B - League Event 5
Starting date and time of all the League Events: 20/04/2007 21:00 UTC
Number of the groups: 3
Events per day: 2
The event will foresee three League Races which will take place on:
Third Group: 20/04/2007 at 21:00 UTC;
Second Group: 20/01/2007 at 21:00 UTC;
First Group: 21/01/2007 at 21:00 UTC.
- Time deadline:
Deadline means the date and the hour before which an rLeague registered Driver can subscribe a League to take part at the first league event according to the time.
Deadline is always indicated in 48 hours before the starting date of each league event. The achievement of the time deadline determines the “freezing” of your own group to the league event and, consequently, to the generation of the established League Races and the summoning of the drivers which will take place to them.
Example:
League A
League Event 1: 08/01/2007 at 21:00 UTC (deadline: 06/01/07 21:00 UTC)
League Event 2: 15/01/2007 at 21:00 UTC (deadline: 13/01/2007 21:00 UTC)
If the driver will subscribe the league before 06/01/2007 at 21:00 UTC, he will run the League Event 1;
otherwise he will automatically "put on" the following League Event 2.
[edit] League event "status"
In a particular moment every league event can establish one of the following status:
- AWAITING PREVIOUS EVENT(S) TO COMPLETE;
- AWAITING OFFICIAL GROUPS AND RACES PLANNING DEFINITION;
- IN PROGRESS;
- COMPLETED.
[edit] Status 1: "AWAITING PREVIOUS EVENT(S) TO COMPLETE"
It take place when, according to league's calendar, some previous league event have not had an end.
[edit] Status 2: "AWAITING OFFICIAL GROUPS AND RACES PLANNING DEFINITION"
It takes place when the league event is really going to be foresee, according to the time, but the present date is nearer at the date of deadline; so, the number of the groups and their composition are previously established, but not yet definitely and, consequently, "freezed".
[edit] Status 3: "IN PROGRESS"
It takes place when the deadline date and its timetable have been reached, so that the days (and their composition) are "freezed" and the games are going on.
[edit] Status 4: "COMPLETED"
It occurs when all the League Races concerning the present groups have been run and the Bonus/Malus DLI have been published and issued. When a league event reaches this status, the following one in order of time automatically changes from status 1 to status 2. If the league event doesn't foresee further league events, the league itself will change from "In Progress" status to the "Ended" one, because it will be considered over.
