POE2 Faster Campaign Run Planning: A Patch-Aware Delay Log

A useful campaign plan removes repeated decisions while remaining easy to revise when the game changes.

Define what the run is testing

Turn a vague speed goal into a bounded campaign-planning exercise.

• State whether the run is testing route recall, fewer town interruptions, quicker skill decisions, simpler equipment checks, or a combination of these.
• Choose observable signs of friction, such as an unplanned stop, backtracking, an unresolved skill choice, or a prolonged equipment comparison.
• Do not use another player's completion time as proof that the same route suits your character, constraints, or current version.

Create a compact checkpoint sheet

Put the decisions most likely to interrupt the run into a single reference.

• Divide the planned run into recognizable progression checkpoints without inventing mechanic-specific requirements.
• For each checkpoint, record the intended next objective, any planned town action, and decisions that must be resolved before continuing.
• Keep uncertain route details labeled as unverified so they can be checked in the current version rather than remembered as facts.

Prepare skill and equipment decision rules

Reduce repeated evaluation without prescribing unsupported build choices.

• Write the intended role of each planned skill choice and the condition that would cause you to reconsider it.
• Define what an equipment change must solve before it deserves a pause, such as a stated progression constraint or a problem observed during the run.
• When the closed evidence does not support a specific choice, use a conditional rule based on the player's current plan instead of naming a universal selection.

Set boundaries for town stops

Prevent routine maintenance from becoming an open-ended interruption.

• List the actions intended for each planned stop so unrelated checks do not accumulate.
• Identify the conditions that justify an extra stop, while leaving version-dependent triggers unverified until confirmed in play.
• If an interruption occurs, log its cause rather than assuming every stop was avoidable.

Record delays during the run

Collect enough information to distinguish a route problem from an isolated execution error.

• At each meaningful delay, note the checkpoint, intended action, actual interruption, and immediate cause.
• Classify the delay as planning uncertainty, navigation uncertainty, town management, skill choice, equipment review, execution, or unknown.
• Preserve unknown causes as unknown; a single delayed segment does not establish a campaign mechanic or a general route rule.

Revise from repeated evidence

Improve the plan without rebuilding it around one unusual run.

• Review which delay categories recur and which appear only once.
• Change the smallest relevant part of the route sheet, then compare the next run under reasonably similar conditions.
• Retain changes that make the plan easier to execute for the player, even when they do not support a precise time claim.

Decision checklist

• Record the current game version or update context.
• Define the specific source of campaign friction being tested.
• Write the planned progression checkpoints.
• List intended actions for each planned town stop.
• Record upcoming skill decisions and their conditions.
• Define what would justify an equipment review.
• Mark uncertain route details as unverified.
• Log meaningful delays and their immediate causes during the run.

Worked example

A player notices that campaign momentum repeatedly breaks around town visits and equipment comparisons. Before the next run, they make a checkpoint sheet that lists the intended objective, the actions reserved for each planned town stop, and the condition that would justify inspecting equipment. During the run, they record an unplanned stop caused by an unresolved skill decision and a separate delay caused by navigation uncertainty. Afterward, they update the skill-decision note but do not rewrite the equipment rule because the log did not show that rule causing the interruption. They keep the navigation cause marked unknown until another comparable run provides more information.

Common mistakes

• Copying a rigid route without checking its version context or personal constraints.
• Treating a community discussion as authority for campaign mechanics.
• Optimizing around a completion-time target that the available evidence does not support.
• Changing route, skills, equipment rules, and town behavior at the same time.
• Converting an isolated delay into a general rule.
• Leaving uncertain route details unlabeled after an update.

Related guides