Set a cart-train baseline, change one cart or part at a time, and compare run endings without relying on an invented universal build.
Keep the first train simple, record its ending, then test exactly one cart, engine, fuel, turret, or position change.
More carts create room for more roles, but no current evidence proves a universal order. Use a repeatable baseline so you can tell whether each change actually helps your goal.
Use these blocks to decide what to check, what to avoid, and which next page helps before you spend time or resources.
Record the number of carts and the front-to-back order of every engine, fuel unit, and turret. A screenshot is more useful than memory when a longer train starts behaving differently.
A timestamped gameplay recap observes that extra carts provide additional build space. Test the empty cart first, then add or move one component so capacity, position, fuel, and power do not change together.
For distance, record the stopping marker. For speed, also record whether the train stays controlled. For an obstacle test, confirm the same obstacle appears. Keep a change only after it improves the chosen result twice.
There is no proven universal order; use a baseline and test one role at a time.
The current public sources reviewed here do not verify a maximum.
Use the goal and ending symptom to decide whether another engine, fuel or verified utility test is useful.
The setup planner turns your current mix into a three-run test plan.
Open the next page that matches what you are trying to do in-game.
Compare this train method with the other player walkthroughs.
Record part counts and produce a one-change test plan.
Compare the role priority that matches your last ending.
Review confirmed roles and version-sensitive part claims.
Diagnose a stop, slow run, crash, or obstacle.
