Skip to main content

Detection Parts

This documentation is for version 2.0, and likely won't be supported or work in older versions.

Trains usehave 2 "TrainDetectPart" parts that are positioned onin the railstrain model to detect changesother thatparts on the client or server should change something.rails. Track circuit parts, however,parts are separate, and are moved above each carriage for larger detection parts to detect them. None of thesethe train parts require or check for any children, unlike pre-2.0. All of these parts must be in the correctDetectionParts carriage,folder inof the DetectionPartscorrect folder.carriage. All of these parts will be given an appropriate CollisionGroup when they are registered with the train system, you don't need to change this manually.

Train Parts

TrainDetectPart_F

image.png

  • Positioned on the rail on the right side of the train, in the DetectionParts folder of the first carriage.
  • Should be around 1 x 2 x 1 studs in size, but this doesn't really matter as long as it does not encompass over half of the track.
  • Will be given a CollisionGroup of TrainDetectPart on registering
  • Must exist for the train to be considered valid and match the (upcoming) train guidelines

TrainDetectPart_B

image.png

  • Positioned on the rail on the left side of the train, in the DetectionParts folder of the last carriage
  • Should be around 1 x 2 x 1 studs in size, but this doesn't really matter as long as it does not encompass over half of the track.
  • Will be given a CollisionGroup of TrainDetectPart on registering
  • Must exist for the train to be considered valid and match the (upcoming) train guidelines

CircuitTrain_DetectPart

image.png

  • Positioned approximately above the railsrails, in the DetectionParts folder of each carriage
  • Should be at least 3 studs tall to ensure detection
  • Will be given a CollisionGroup of CircuitTrain_DetectPart on registering
  • Must exist for each carriage for the train to be considered valid and match the (upcoming) train guidelines

JointTrigger

image.png

  • PositionedMust be positioned across the railsrails, -in doesn'tthe specificallyDetectionParts havefolders toof touchcarriages either(this railpart is optional)
  • Should be around the Y position of the rails
  • Will be given a CollisionGroup of JointTrigger on registering
  • These parts should be aligned to where the train wheels touch the rails, and they will produce a sound when a train passes them
  • Does not have to exist for any carriages for the train to be considered valid and match the (upcoming) train guidelines

Rail Parts

SpeedLimit