Option 1: VectorForces
You put value into force. Train goes woosh. This is what I used with my automatic trains. However, there are some downsides, such as the random physics issues that may occur, causing the train to unexpectedly fling. This can be resolved with CustomPhysicalProperties, but it seems as a very hacky-ish solution
Option 2: AlignPosition
Similar to VectorForces, you use an attachment, however this time you set Attachment1 to the next node where you want the train to go. This will result you potentially placing down many nodes, making this option time consuming. It also does bring in some physics oddities, which you can solve with AlignOrientation or as said before, CustomPhysicalProperties.
Option 3: AlignOrientation + AlignPosition + CFrame
The post explains it well enough. I won’t get into details here.
Please don’t:
- Use CFrame only. Apart from looking robotically, if used client-sided, expect it to eat up memory. Also it’s a pain to work with.
- Use BodyMovers. They’re practically deprecated at this point