Last Stop Modes

Last Stop supports distinct ways to approach the road even when the full mode rules are not publicly documented. The official badge directory confirms an always-night Nightmare mode, an 80 Km solo objective, an 80 Km objective for a full team of four, and a revive milestone. Those facts support planning; they do not publish every enemy, reward, scaling or respawn modifier.

Mode index

Choose the learning environment

Use the normal route to learn controls, attachment, fuel, sale decisions and checkpoint recovery. Move to Nightmare after the team can already keep a bus supplied and reach Fred consistently. A harder mode does not teach basic organization faster when every attempt ends from the same fuel mistake.

Use solo when you want complete control of timing and outcome, accepting that every driving, fighting, looting and repair task belongs to one player. Use a team when role handoffs and revives outweigh the cost of coordination.

Do not confuse server cap with team size

The official Games API reports a maximum of 25 players for the experience. That is not a fixed bus-team rule. The official Team Player badge specifically says “full team of 4,” which is the clearest first-party team-size evidence for that objective.

Record the actual party or bus size in every tactic. Enemy scaling, loot sharing, revives and ending credit may behave differently and need current testing.

Compare modes with the same fields

Track lighting, enemy presence, checkpoint conditions, boss health, damage, resources, fuel, loot, rewards, revives, respawn, team credit and ending behavior. Use the same route and update where possible. A different class or bus can distort the comparison.

Do not call a mode more rewarding unless the current interface or repeated completion shows the reward. The official Nightmare badge confirms a completion goal, not an entire bonus table.

Plan supplies by responsibility

Solo needs accessible fuel, a spare mobility plan, one sustainable combat kit and fewer optional detours. Multiplayer can distribute weapons, healing and materials, but protected items require clear ownership. Nightmare should begin with a larger reserve and fewer speculative side trips.

For every mode, choose the Fred ending before the final stop. A mode completion and an ending are related run goals but distinct badge conditions.

Handle revives and failure

The official Guardian badge tracks 50 teammate revives, confirming that revival is a meaningful multiplayer action. It does not specify every revive timer, cost or credit condition. Record the current prompt and keep one player safe enough to perform the revive.

Solo players need to know whether a current mode provides any self-recovery or simply ends the attempt; do not infer it from multiplayer. Nightmare revival rules also require direct observation.

Build mode-specific records

Attach mode, team size, class, bus, update date and route to every boss or value claim. A Dracula health number from Nightmare should not overwrite a Normal record. A solo fuel plan should not be presented as a four-player shared inventory rule.

Evidence boundary

Nightmare’s always-night description, Solo Pro 80 Km, Team Player four-player 80 Km, Guardian revives and server maximum are Official facts. Detailed mode modifiers, scaling, rewards, respawns and team sharing need in-game testing. Checked September 18, 2026.

Normal as the baseline

Use the ordinary route to learn attachment, terminal, checkpoint and ending interactions before treating it as a farming mode. Record fuel consumption across a measured segment, the cost of one repair, the result of one sale, and the resources remaining at the last stop. That baseline makes a real Nightmare or party difference visible instead of relying on memory.

Normal is also the safest place to test a new class or bus layout. Change one part at a time. If the route fails after several simultaneous changes, the team will not know whether the cause was storage, weapons, fuel, roles or an update.

Switch modes with a purpose

Choose solo when you want control over resources, route pace and the Fred decision, or when pursuing Solo Pro. Choose multiplayer when roles, revives and a full team can reduce workload, or when pursuing Team Player. Choose Nightmare only when the always-night run itself is the target and the basic route is already reliable.

Do not select a harder mode merely because a community value table promises better loot. Confirm the current reward in the current mode and compare it with extra supply consumption. A successful baseline run can be more productive than repeated early Nightmare losses.

Compare the same checkpoint

For a useful mode comparison, use the same checkpoint or route segment, similar bus state, documented team size and a current server. Record enemies, fuel used, ammunition used, downed players, loot shown and time to clear. Boss observations need boss name and phase as well.

One comparison is a lead, not a universal multiplier. Repeat after a patch or when party size changes. Keep Normal, solo, multiplayer and Nightmare rows separate so a dramatic result from one setup does not rewrite every guide.

Finish-state checklist

At the last stop, confirm mode, team condition, intended Fred outcome and the player pursuing any final-hit badge. Complete the live objective, wait for badge delivery, and record actual currency or items separately. A mode badge, ending badge and reward screen are three different pieces of evidence.

If one player receives a result and another does not, compare join time, party membership, reconnects, final hit and downed state. Preserve those details before beginning another long attempt.