Loot with a return point. Fortify a place the team can actually hold. Protect the shared route at night. Finish on purpose.
The four phases below organize the official loot, build, survive, and escape tasks. Community progression notes support the phase framing, not a universal perfect route.
Find the run on the rail
Jump to the phase that describes the current state, not the number you hope to reach.
Open with a return plan
Loot the city without turning the first trip into an open-ended run.
Run actions
- Pick one looting objective before leaving your safe point.
- Agree on a return signal if you are playing with a team.
- Bring the first useful haul back before expanding the route.
The group returns with a clear next build decision.
Players keep extending the trip with no shared stop point.
Turn loot into defense
Use the official build-defenses task as the next checkpoint, not as background flavor.
Run actions
- Choose the area the team will actually defend.
- Keep one way in and one way out easy to recognize.
- Set aside a reserve before spending on optional expansion.
Everyone knows where to regroup and what gets repaired first.
The base grows, but nobody owns the weak point or reserve.
Hold the run together
Treat surviving zombies as a team state: position, reserve, retreat, and regroup.
Run actions
- Call out the retreat point before pressure rises.
- Pause optional looting when the defense plan is already stretched.
- After each hard hold, check what the next phase still needs.
The team can explain the next action without splitting into separate plans.
The group survives one wave but loses the shared route.
Protect the escape decision
Keep escape visible as a real objective instead of extending the run by habit.
Run actions
- Name the condition that ends side trips for your group.
- Regroup before committing to the final move.
- If the route no longer matches the current version, stop and re-check rather than guessing.
The group chooses to leave or continue on purpose, not by drift.
One more optional task repeatedly replaces the agreed finish.
Solo and team runs share goals, not logistics
When the route starts to drift
Looting keeps expanding
- Check first
- Can everyone name the return signal?
- Recovery
- Finish the current objective and return.
- Stop when
- The group cannot agree on one next build action.
The base has no owner
- Check first
- Which entry or reserve fails first?
- Recovery
- Assign one weak point before expanding.
- Stop when
- Repairs consume everything needed for the next phase.
The plan no longer matches the game
- Check first
- Which visible step changed?
- Recovery
- Narrow the route to the official core loop.
- Stop when
- The missing trigger would require guessing.
Day 100 route questions
Is this an exact Day 100 speedrun route?
No. It is a phase-based planning route. Exact triggers and the single best route are not claimed.
Why does the route start with a return plan?
The official loop starts with looting and then building defenses. A return point connects those two tasks instead of treating looting as endless.
Should solo and team runs use the same checklist?
They share the same core tasks, but a team should add a caller and regroup signal while a solo run should keep each trip shorter and more reversible.
What if the route stops matching the current game?
Use the page as a planning frame only, stop at the mismatch, and switch to the troubleshooting guide instead of inventing a new trigger.