Walkthrough & Builds / League of Legends / Proprietary Engine

League of Legends 26.22: A Repeatable Mid-Lane Build and Wave Plan

A simple mid-lane build and wave-management routine for League of Legends patch 26.22, built around repeatable decisions.

Official cover artwork for League of Legends, featuring Riot Games, Proprietary Engine, and MOBA cues.

League builds change with every patch, but wave planning is a durable skill. A modest build executed with a clear first recall will outperform a perfect item list with no lane plan.

A Repeatable Mid-Lane Build and Wave Plan

Verified field fix

The shortest safe order for this issue:

  1. Choose one champion and one first-item spike for ten games.
  2. Plan the first three waves before the minions meet.
  3. Review one death per game for wave state, not just the champion matchup.

Build around the first recall

Set a gold target for your first recall and decide what the item lets you do: push, trade, or survive a dive. Do not buy a component just because a guide lists it if the lane state makes the spike unusable. One champion for ten games gives you comparable data.

League of Legends — repeatable mid-lane plan
Champion: one pick, ten games
Wave 1: trade or hold based on matchup
Wave 2: ward priority side before pushing
Wave 3: crash or freeze for first recall
Recall: buy the planned spike, not the most expensive component
Review: one death, one wave decision, one map move
Use the practice tool and a replay. The build is a hypothesis; the wave state decides whether it applies.

The first three waves

Decide whether you are pushing for level two, holding the wave near your tower, or preparing a crash for a recall. Practise the same opening in the practice tool. If the enemy jungler changes the plan, note it on the replay timeline instead of calling the plan wrong.

Field notes before you change the build

A League of Legends build is a testable plan, not a screenshot of someone else’s final character. State the patch, the encounter, and the resource budget the plan assumes. If those change, the build is a new hypothesis.

Practise the same encounter and change one ability, item, or upgrade tier. A route or build that only works with perfect execution is not a reliable recommendation, especially in a Proprietary Engine game with variable enemy behaviour.

  • Do not spread upgrades across every tree before the core loop is stable.
  • Do not copy a build without checking its patch version and resource costs.
  • Do not judge a change from one lucky encounter or a highlight clip.

Check it before you keep it

Count one repeatable decision per game

0 / 5 complete

Build for repeatability

Write down the assumptions, test the same scenario, and keep the version that produces fewer panic decisions. That is the build you can actually use.

The line to keep

One champion, one first recall, one review question. That is a build plan you can actually repeat.

Did this fix work on Patch Patch 26.22 — client and Vanguard updates?

One click. No account. Your vote is stored in this browser and de-duplicated per file.

Verified against Patch 26.22 — client and Vanguard updates. Votes are local-only telemetry.

League of Legends: bench questions

2 answers
Should I follow a pro build exactly?
Use it as a starting point. Your lane matchup, jungle path, and team composition decide whether the first item timing is real.
How do I stop autopiloting?
State the first three waves out loud before the game and review one decision after. Adding more champions makes the habit harder to build.
Filed under

Walkthrough & Builds

Patch tested: Patch 26.22 — client and Vanguard updates

This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.

Continue the file stack Game hub ↗
Index: Pagefind Type a game, symptom, or tool

    ↑↓ navigate ↵ open GPH / COMMAND SEARCH
    Local profile / hardware telemetry

    My rig

    Stored only in this browser. Game hubs use it to estimate whether your build clears the recommended specification — nothing is uploaded.

    No profile yet. Save once and the masthead, spec pages, and tool prefills follow.

    Telemetry never leaves this browser.