Subscribe to download
Rotor Based Chronometer

The RBC is a simple chrono script which can manage multiple checkpoints, originally developed for drag competitions where at least two challengers must reach the finish line in time attack mode.
Checkpoints are triggers which stop the chrono for a specific checkpoint if this one is reached. The player has to collide with a barrier mounted on a rotor to activate a trigger. De-activate block damage in settings or admin panel is a must.

The script is minimalist, a reset and start options to (re-)activate all triggers and launch the chrono.

Each checkpoint must have:

• a unique rotor, named chrono_rotor_<name>
  
• a unique LCD panel, named chrono_timer_<name> (optional). The LCD panel will display the name of the checkpoint and the chrono.

Important:
<name> must be the same for the rotor and the LCD panel of a checkpoint and unique: two or more checkpoint should not have the same custom name.

Checkpoint nickname
A nickname can be attributed to a checkpoint and displayed on LCD panels instead of the <name>, by enter the nickname in the rotor's custom data.

Rotor configuration:

• Should be able to return to his start position: on and torque up to 447999 Newton (max value for non-experimental mode)
  
• Should not resist when getting hit by a car: off and torque down to 0~100 Newton, or the minimal value where the rotor is locked on his current angle.
  
• The orientation of the rotor depends of the size of a vehicle. Rotors on side of a track will be good for tall vehicles such as trucks, monster trucks, SUV, when rotors on top of a track will be good for very low profile cars such as dragsters, F1, LMP and other sportive cars.

Barrier:
Mounted on each checkpoint's rotor, a simple line of half inclined blocks.

LCD panels:
Nothing else required except:

• LCD panels in checkpoints must be named chrono_timer_<name>
  
• LCD panels which display the score must be named chrono_score

Every parameter except the displayed text can be edited manually.

• reset
  
• start

Rotors have a better refresh rate than sensors, which allow to get more precise times.

The method get the real time each tick. You may experience strict equality in very few cases, less than using sensors.

Nether tested with red cars to see if they go fasta, but believ they go fasta.