• LFS forum thread
• General tracker information
• Web tracker admin
• Local tracker to database

Web tracker admin

The following can be accessed via <your tracker directory>/admin by default. It is recommended that either the directory is passworded via .htacces, or renamed.

Contents

1. Race Control
2. Team Data
   1. teams.yaml
   2. teams.csv
3. Track status
4. Configuration options
   1. Tracker settings
   2. Championship information
   3. Race information
   4. Server Settings
5. Database server
6. Update tracker

Racecontrol

A listing of all server events that are stored in the database, including server/LFS messages, users leaving/pitting in the race, errors, penalties, etc. with a timestamp and also the time elapsed since the start of the race. These are colour coded to make it easy to spot, for example, driver chat (where the first 3 digits of the message are a number). You can also link directly to an event ID by appending "#ID" to the url.

Team data

Information about each of the teams is stored in teams.yaml, using YAML markup or in teams.csv, using CSV.

teams.yaml

Indentation must be preserved otherwise it will break the tracker. Blank values will be ignored; however, teamName, car, number (leading zeros may be added by the tracker), and drivers are mandatory values. To enable multi-class tracking, class must also be filled in. To show positions gained and the grid before the race, grid needs to be filled in. Also, where the team's class is GT2 or GT3, or where GT1 is not the fastest class, the final "R" in the car code will be replaced by numbers 1, 2 or 3 - e.g. FZR will become FZ2 for GT2.

It is advisable to keep the teams in numerical order, to find them easily to make changes or mark them as retired for instance. Also, if any text contains spaces and does not display correctly in the tracker, you may need to add quotation marks around the "text".

The tracker also uses the names (and numbers) to work out who has finished the race, and to count pit stops and DT/SG from each team by reading the server messages - therefore numbers and names should be exactly as they appear in LFS, and vice-versa.

# This is a comment, useful for noting which race these teams are for

-
 teamName: Example Motorsports
 class: 3 letter class code
 car: 3 letter car code
 number: Number
 server: Number
 grid: Number
 penaltyLaps: -/+ Number
 penaltyTime: -/+ Number
 teamStatus: RET/DQ/DNS
 drivers:
  - {username, Forename Surname, Country}
  - {srdjanmilasinovic, Srđan Milašinović, Serbia}

List of countries as of 29/06/2011: albania, argentina, australia, austria, belarus, belgium, bolivia, bosnia and herzegovina, brazil, bulgaria, canada, chile, china, colombia, croatia, czech republic, denmark, ecuador, england, estonia, finland, france, georgia, germany, greece, grenada, hong kong, hungary, iceland, india, ireland, italy, jamaica, japan, latvia, lebanon, lithuania, luxembourg, macedonia, mexico, netherlands, new zealand, northern ireland, norway, peru, poland, portugal, romania, russia, san marino, saudi arabia, scotland, serbia, slovakia, slovenia, south africa, south korea, spain, sri lanka, sweden, switzerland, taiwan, turkey, ukraine, united kingdom, uruguay, usa, uzbekistan, wales

3 letter ISO 3166-1 alpha-3 country names can also be used.

UTF-8 characters can be used. With the encoding of the input page and the tracker set as utf-8 this should work without a problem; if utf-8 characters are not displayed correctly, you may have to create the file in a text editor, save as UTF-8, and upload to the tracker directory.

teams.csv

To use a csv file, $useTeamsCSV must be set to true in the config. All columns must be in place, regardless of whether they are used or not - they must still be kept blank to preserve the CSV file structure. The CSV option is especially useful for exporting from a spreadsheet. A header must be present for each column.

Track status

Used to manually set the track status. The tracker will automatically get the track status from the GREEN FLAG, SAFETY CAR DEPLOYED, SAFETY CAR IN THIS LAP, RED FLAG and CHEQUERED FLAG server messages, and check the timecode of these against the last modified timestamp of the trackstatus.txt file - using the most recent update. The tracker does not refresh on PRE-RACE or CHEQUERED FLAG, but should once it receives a server message - if not you may have to set it to GREEN FLAG as the race starts.

Configuration options

The configuration options have been set up so that most, if not all, of the tracker's features and settings can be changed without editing any of the PHP files. Config.php is loaded when the tracker is updated, so can also be used to run execute PHP code. There are 55 config items in total.

Session switch

Tracker settings

Page / Header / Footer design

Championship information

Race information

Qualifying information

Server settings

Since the number of servers is unlimited, you can create however many $mannualIdServerXX variables as you require.

Database server

Set the IP address of the database to access; you may also add the default MySQL port (:3306) and a prefix if necessary.

The page will display the contents of the race table in the database if it is able to connect to the IP/port, if not it will display a MySQL error (this may take some time for it to timeout).

Update tracker

This will update the tracker at most every 30 seconds, and links to the update page including any security numbers in the filename to prevent just anyone running update.php.