POE2 Farming Route Preference Matrix: Choose Content That Fits You

A farming route only works for you when its demands, rewards, and play pattern match what you are willing to repeat.

Define the farming experience you want

Turn a vague route question into explicit preferences before evaluating content.

• Separate must-haves from nice-to-haves for reward style, boss interest, and control over optional modifiers.
• Record limits for preparation, time pressure, trading, and acceptable failure risk.
• Name the content you can currently complete and the type of repetition you actually enjoy.
• Treat any non-negotiable mismatch as a reason to remove a candidate before testing it.

Build a preference-first route matrix

Compare player-supplied candidates without inventing route mechanics or current reward rankings.

• Create one row per candidate route and one column per preference or constraint.
• Grade each cell as strong, acceptable, poor, or unknown instead of forcing unsupported precision.
• Include build fit, desired reward style, boss interest, modifier control, setup burden, time pressure, trade friction, failure risk, and repeatability.
• Leave unsupported route characteristics marked unknown until the player can verify them directly.

Apply readiness and sustainability gates

Prevent attractive preferences from hiding a route that the current character or resource pool cannot sustain.

• Check whether the build can complete a representative version of the candidate consistently.
• Identify every preparation step and resource commitment required before a test begins.
• Reject a candidate when repeated failures or preparation demands exceed the player's stated tolerance.
• Keep preference fit and current readiness separate so a desirable future route is not mistaken for a usable current route.

Run comparable test batches

Replace popularity and isolated outcomes with observations from the player's own sessions.

• Use a small fixed batch for each surviving candidate under conditions that are as similar as practical.
• Record completion, failures, preparation time, interruptions, and recovery between attempts.
• Separate output usable by the player from output that would require additional trading.
• Note enjoyment and fatigue because an unpleasant loop may not remain repeatable.

Select a primary route and fallback

Turn the comparison into a durable decision without presenting a universal recommendation.

• Choose the route that clears the required gates and produces the strongest overall preference fit.
• Keep a fallback for sessions when the primary route's setup, time, or attention demands do not fit.
• Document which observation would justify retesting or switching routes.
• Avoid converting a personal fit decision into a claim about current market-wide profitability.

Review the decision after relevant updates

Keep the matrix useful while acknowledging that the supplied patch evidence contains no route-specific details.

• Recheck assumptions after an update that changes the build, access conditions, rewards, or repeated-content experience.
• Retest affected matrix cells instead of discarding the entire framework automatically.
• Keep unverified reward, drop-rate, and market claims out of the comparison.
• Record the update context beside each test so older observations are not silently treated as current.

Decision checklist

• Write down three must-haves for the farming experience.
• Write down three deal-breakers that would make a route unsuitable.
• List only candidate routes the current character can reasonably test.
• Grade each candidate for build fit and repeatability.
• Grade each candidate for setup burden, time pressure, and failure risk.
• Grade each candidate for reward preference, boss interest, modifier control, and trade friction.
• Run comparable test batches for every candidate that passes the initial gates.
• Select a primary route and a fallback from recorded results.

Worked example

A player wants raw-currency-oriented rewards and boss encounters but dislikes frequent trading, timed pressure, and complicated preparation. They place two personally known candidates into the matrix without assuming either is more profitable. Their test notes show that Candidate A fits the desired encounter style but repeatedly exceeds the preparation limit. Candidate B offers less boss emphasis but fits the setup and trade constraints and remains comfortable to repeat. The player chooses Candidate B as the current primary route, keeps Candidate A as a future option, and records the readiness issue that would need to change before retesting it.

Common mistakes

• Starting with a popularity ranking before defining personal constraints.
• Treating an unknown route characteristic as if it were favorable.
• Letting one unusually good or bad result decide the comparison.
• Ignoring preparation time and interruptions when judging repeatability.
• Counting listed value as immediately usable output.
• Keeping a preferred route in contention after it fails a non-negotiable gate.

Related guides