|
| Player Checklist | Also available as a rtf file |
This is a little checklist to aid you, as a player, in thinking of a couple of things. Races must, first and foremost, be fun and you'll probably have plenty of that while playing them. There is however the matter that these races are part of a tournament and therefore require a little protocol.
Pre-Session:
- Keep checking your group topic for any changes or requests from your session leader!
- Be communicative!
- If you can't make the session, have the courtesy to inform your group. Otherwise they will wait (invain) for you!
- Check that you have the latest version plug-ins of the tracks that will be driven and cars that are allowed during the races.
- Make sure you have the races to be driven handy, including the starting grids.
- Start looking for the host 15 minutes before the session starts.
- Expect a full race session to take at least an hour.
Pre-Race:
- Check for unauthorised cars and irregularities.
- Remember the formation lap.
- Check the grid position you have in this race.
Post-Race:
- You'll get the chance to save the Redlog and jot down the outcome for reference. Also note the cars that were driven by everyone, there's room for that on the website result pages as a statistic.
- Now is the time to make complaints about other people's behaviour.
- If you want to make a race note (see below) on something cool, funny or whatever happened in that race, you might want to jot that down.
Post-Session:
- Afterwards, you can post some comments on the races (Race notes) in the topic of your group.
|
| Session Leader | Also available as a rtf file |
To do list when you're appointed session leader.
- When you are appointed session leader of your group, it is best to waste no time and immediately start with your attempts to determine the day and time when your races are to be held.
- Choosing a host, either from your group or a foreign one, will be your second responsibility.
- Third, you will maintain a topic concerning your group.
- Fourth, you will notify the Race Administrator with the outcome of the individual races. Just the ranking of every race (and, if possible, the car everyone drove).
- Make sure someone saves the redlog.
FIRST create a topic on the boards. To make it recognisable, we use a convention here:
- Subject: [RRL] Session X Group Y
(I don't have to explain the X and Y now, do I?)
- Description: Gathering...
When you have detemined race time(s), change the description to: Races set.
When the races are run, change the description to: Race Notes.
(This will allow people to write about the "amazing moments" they had in the races.)
- Bodytext of first post: make some realistic proposal on a race date/time or just ask everyone their availability (read on below).
As you get more information concerning everyone's availability, gather the information in this first post by editing it.
SECOND immmediately pm everyone in your group and make them aware of the topic. This will prevent you from playing catchup later if a person doesn't respond because he simply didn't check the boards or overlooked the topic.
Keep communicating! Don't think everything will "just happen".
If you have Excel, you can use the Race planner, available from the homepage.
Most likely, you will race in the weekend:
Until the deadline you'll have a minimum of two weekends (and more if we are ahead of schedule). These weekends will be the most likely windows of opportunity you'll have. If you're lucky, you'll lead a full European or a full American/Canadian group and can maybe organise a weekday session. If you don't, beware that the maximum time difference of the entire field is 9 hours (Europe/US west coast). This translates to (for example): 10:00pm Europe = 1:00pm West Coast. Work with the extremes of your group first, then fill in the rest.
If you can't nail a single session with everyone in it, split the session into two small sessions, as long as the outcome doesn't "hurt" more. For example, if you can choose between a session with player A missing and a session with player B missing, do races in each. Share the burden!
If someone fails to respond before the first weekend and the rest of the group is only available for that first weekend, you will do the session without him. If you do have an opportunity in a later weekend, you'll plan the session then.
When you can't reach an acceptable solution (after the neccesary negotiations of course), you may call upon the Race Administrator for advice.
|
| Host Checklist | Also available as a rtf file |
This is a little checklist to aid you, as a host, in thinking of everything. Races must, first and foremost, be fun and you'll probably have plenty of that while playing them. There is however the matter that these races are part of a tournament and therefore require a little protocol.
Pre-Session:
- Check that you have the latest version plug-ins of the tracks that will be driven and cars that are allowed during the races.
- Make sure you have the races to be driven handy, including the starting grids.
- If you are a foreign host, figure out a good place on the tracks to be driven to hide your car.
- Mail everyone the hostname and password.
- Start hosting 15 minutes before the agreed time. As soon as everyone is in, just start, why waste time?
- Wait no more than 10 minutes for late comers. If nobody is pressed for time, wait as long as you want.
Pre-Race:
- Double check that you have selected the right track, the right direction, number of race laps plus 1 formation lap, weather and simulation (Strict on Corniche).
- Check for unauthorised cars. This can be difficult, but can also be checked during the race. Other players have eyes too.
- Ask if everyone is happy with the setup and, especially during the first races, remember them of the formation lap. If there is anything unclear about that, now is the time to explain.
- Ask them if they know their grid positions.
Formation lap.
If you are a foreign host, you will take off first and seek your hiding place. This way, the players will see that place during the formation lap and won't be distracted the second time around.
Post-Race:
- DO NOT ACCIDENTILY ESCAPE to the in-session lobby!!! The Redlog must be saved and players must get a chance to write down the results of the race. The latter being the job of the session leader to send those results to the Race Administrator.
- Ask if anyone wants to dispute the outcome of the race and if a post race scruteneering is required.
|
| Connection trouble and Framerate issues |
Connection problems.
How you handle connection problems, will largely depend on the group your in (how much time everyone has, for example) and the circumstances.
It is very hard to cover all situations possible in this context and regulate them. This tournament therefore limits itself to the following procedures.
First loss of connection during the session.
When someone looses connection during a race for the first time in the session, you will restart the race when it happens during the formation lap or the first or second lap of the race (lap 2 or 3 on the lap counter).
Any consecutive connection drops.
When someone has lost connection once during the session, only one restart attempt per race will be made if the person involved drops out during the formation lap.
Connection dropped, points awarded.
In all other situations you will continue the race without the person involved. He or she will be ranked last, but points will be awarded by multiplying the points associated with the player's position at disconnect, with the percentage of laps completed.
The resulting score will be rounded to the nearest whole number and will have a minimum of the lowest score possible in that race.
All finishing players will receive points based on their actual finishing position.
Framerate problems.
In this tournament, weather types are used. They can cause framerate problems on older systems. If someone is experiencing trouble, you may do the race in Daylight weather, provided it isn't a Rain race.
Pre-race check.
With above problems in mind, it might be wise to do a two lap practise race before the real race, to check for any lag and framerate issues. You can also practice the rolling start at the same time.
|
| Redlogs |
For reviewing purposes, the redlogs of every race will be made available on the Session pages of this website. For this reason you must not forget to actually save them after the race. There won't be an upload page, but there are several ways to get those (zipped!) redlogs into the right hands:
1. You have access to some webspace where you will upload them. You will pm the Race Administrator the url to that zipfile.
2. You already have some space on legacyoflies (because you're a developer, for example) where you upload the zipfile. You will then ask (pm) leoantix or GeneralAntilles (who both have full access to the site) to move the zipfile to the RRL website directory. Also let the Race Adminstrator in on that.
3. Email the zipfile(s) to the Race Administrator (Brook). If you don't have the email address, go to Brook's membercard and first send him a pm or an email without the attachment(s). He will then reply you his email address. The attached zipfile may not exceed 5Mb.
|
|
