Monkey King Match Plan: When to Join, Pressure, or Farm

Monkey King does not need one fixed script. Give the match a clear job, watch for the conditions that support it, and change branches when those conditions disappear.

Define Monkey King's job for the next decision window

Replace a vague intention to play aggressively or keep farming with a match-specific responsibility.

• Describe what Monkey King's next contribution is meant to enable for this lineup.
• Name the visible result that would show the plan is still progressing.
• Identify what the team would lack if Monkey King chose a different branch.
• Keep the job conditional because the closed evidence does not verify a fixed current-patch role.

Set a checkpoint before leaving the lane plan

Make the lane-to-midgame transition deliberate without prescribing an unsupported timing.

• Record whether the original lane plan still fits the visible state.
• Identify the next credible team action rather than moving toward activity by default.
• Check teammate positioning, available information, and the cost of leaving current resources.
• Choose a recheck cue before committing to a route.

Compare joining, pressuring, and gathering resources

Evaluate the available branches against the same observable questions.

• Join when the proposed action has a defined purpose, participating teammates, and a plausible follow-up.
• Apply pressure only when the team can use the space or response it is meant to create.
• Gather resources when they support a stated next job rather than postponing the decision indefinitely.
• Reject any branch whose required information or team support is missing.

Use continue, fallback, and replan cues

Keep a reasonable decision from becoming an inflexible sequence.

• Continue while the intended job remains relevant and the supporting conditions remain visible.
• Use the fallback when participation weakens or the expected follow-up disappears.
• Replan when new information changes the team's immediate priority.
• Avoid chasing the original payoff after its enabling conditions have ended.

Connect resources to a purpose

Prevent farming and purchases from becoming detached from the next team action.

• State what the next resource threshold is supposed to make possible without assigning an unsupported exact value.
• Compare the likely completion window with the action the team appears ready to take.
• Reconsider the plan if teammates already cover the intended function or the match problem changes.
• Route detailed purchase questions to the existing game-state item guide.

Review the first mismatched transition

Create a Monkey King-specific improvement loop without duplicating the full replay-review guide.

• Find the first point where joining, pressuring, or gathering resources were all plausible choices.
• Write down only the information visible when the decision was made.
• Compare the chosen branch with Monkey King's stated job and fallback.
• Carry one cue-response adjustment into the next suitable match.

Decision checklist

• State Monkey King's next team job in one sentence.
• Name the visible action that could justify joining teammates.
• Check what the team loses if Monkey King remains elsewhere.
• Give continued resource gathering a specific purpose and recheck cue.
• Set a fallback before committing to pressure or a team action.
• Review the first transition where the chosen branch stopped matching the visible state.

Worked example

Suppose the lane phase is ending and teammates begin moving toward a possible action. The player first states Monkey King's job: support that action only if the group remains positioned to follow through. The continue cue is sustained teammate commitment; the fallback cue is the group separating or the intended follow-up disappearing. If support remains visible, Monkey King joins with a defined purpose. If it vanishes before commitment, the player chooses a lower-commitment pressure or resource branch and schedules another state check. The lesson is not that one branch is universally suitable, but that each branch needs observable conditions and an exit.

Common mistakes

• Leaving the current plan because activity elsewhere looks urgent without defining the intended contribution.
• Continuing to gather resources without naming the next job they are meant to support.
• Applying pressure when teammates cannot use the response it is intended to create.
• Following a reasonable initial call after its information, support, or payoff has disappeared.
• Turning one unusual match into a fixed current-patch rule.

Related guides