This stream runs about 54 minutes. It opens on a card reading "Hypermine Vanilla VOD" and "Engine Token Delivery" with no episode number, so the number here comes from the playlist. Runwyld is online when Basket logs in, with a "heyo basket" in the chat, and it's night, so Basket sleeps it off first. Runwyld leaves about 16 minutes in, and jandoncom joins near the end.
Carts all over the place
Down where the engines and cabooses wait under Basket Station, chest carts are sitting in random spots. Basket's guess: carts that had been stacked up upstairs went through the system together, hit the wall and shot apart as they dropped. A back wall on the drop might fix it, but for now Basket just puts two strays back in the stack.
Naming the engine tokens
Today's job is the token side of the trains. The first cart of every train is a chest minecart carrying tokens that say "I'm the engine," plus destination markers that tell the intersections where it wants to go. The last cart is the caboose, and its token clears each intersection behind the train.
That takes a lot of named items. Basket hauls cobblestone up from the basement and works out that every destination needs about 11 droppers full of named items, destinations or null placeholders. "If somebody wants to do the math on that, that is how much cobble I will need," and that's for this station alone.
The engine tokens get the prefix for Basket's rail, so the anvil name is "BR:ENGINE." How many does an engine need? Maybe five, maybe just one.
There's one problem. Basket can't find any comparators: "I probably left them at the other rail station." Basket can build without them but not really test. While searching, Basket hops into a creative test world to show the chat a model of an intersection, with item pickups under the track in all four directions.
Five tokens for every engine
Back on the server, anything that reaches the end of the destination sorter must be an engine token, a caboose token or lost and found. Basket loops that line into open space, shifts a rail line over one block for room, and builds a sorter to fill five hoppers. An engine running past grabs one item from each, with no timers needed. The sorter needs a comparator, so for now Basket fills the hoppers by hand.
Then the test. Basket hits the destination button. The old engine and caboose are cleared out, and a new engine comes up to its spot.
Inside it is the item that happened to be in the destination droppers, a rail, plus five engine tokens. It works. It also requests too many replacement carts, so an extra one ends up going back and forth. "There's some debugging to do still." A viewer asks whether a hopper next to the powered rail is locked, so Basket checks: all five hoppers gave up their items.
The caboose will get its tokens differently, a quick burst into a hopper while it waits, but Basket puts that off to build it right later.
Left or right
When a train leaves, the button switches the track long enough for the whole train to pass. From there it either goes straight or turns: one way leads back to town, the other to the iron farm. That choice needs to come from the tokens, read by hoppers under the track fast enough to flip the switch.
The spot is crowded. Partway through, Basket takes a sudden hit, blames delayed fall damage, and the server connection drops. After rejoining, Basket reroutes the turnaround track so the split happens further out, even if it briefly runs the wrong way on a track. "Given that there's only me on the server," that's fine for now. The timer that holds the switch open gets moved over two blocks, and a button test shows it still lets the caboose through.
That leaves two empty spots for the hoppers that will read "go right" and "I'm a caboose." Basket hopes the train reaches them in time to switch, and plans to keep going next stream, after finding some comparators. The credits run to the end with no gameplay after them.