LoL Patch and Meta Guide (2026): How to Read Patch 26.22

Every two weeks Riot changes League of Legends, and every two weeks the same thing happens: some players read a list of buffs and nerfs, decide the game is ruined or saved, and change their whole champion pool — while others don't read anything and discover the change when they lose to it. Neither helps you climb. This guide shows how a patch is made and released, how to read patch notes in ten minutes, what the dev context tells you, how Riot decides what to change, how to tell a real meta shift from noise on stat sites, and how to adapt your games. Patch 26.22, live since 4 November 2026, is the example throughout.

How a patch reaches you

League patches follow a fixed rhythm that you can plan around. Riot Support publishes the year's schedule — patches land on Wednesdays, Pacific time, unless Riot marks another day — and the 2026 schedule puts 26.23 on 18 November 2026 and 26.24, the last patch of the year, on 9 December 2026. Our 2026 patch schedule lists every date. Around each release, four things happen:

1. ~1 wkThe preview

   Riot's balance team posts a list of planned changes about a week ahead — AltChar reported the 26.22 preview on 27 October. It names champions, often without numbers.

2. PBETesting on the PBE

   Changes go to the Public Beta Environment. Riot's PBE FAQ says it adds and changes content there "daily based on feedback" and that features may never reach the live game.

3. −1 dayThe patch notes

   The official notes go up the day before — 26.22's on 3 November at 19:00 UTC.

4. LiveRelease and follow-ups

   The patch goes live (4 November for 26.22). Riot sometimes ships a mid-patch update — 26.21 had one for Varus on 22 October.

As of 8 November 2026, Riot hadn't posted the 26.23 balance preview: Hotspawn's 7 November roundup said "no champion or item changes have been announced so far". Expect it in the week before 18 November 2026.

What's in a set of patch notes

The 26.22 notes follow Riot's usual structure. Knowing it lets you jump straight to the parts that affect your games:

The ten-minute read order

You don't need to read every line. BoostPirate's coaches read patch notes in this order, and stop when the time is up:

1. 2 minYour pool

   Find your main, partner and safety. Read the numbers and the dev context. Is it a number change or a change to how the champion plays?

2. 3 minYour lane

   Scan for champions you meet often in your role. A buffed lane opponent changes your matchup even if your champion didn't change.

3. 2 minYour items and runes

   Check every item in your usual build and your keystone. A nerf to a starting item — like Doran's Bow in 26.22 — touches every early game in that role.

4. 2 minSystems

   Objectives, minions, ranked, map. Rare, but the changes that affect every game. 26.22 had none for Summoner's Rift.

5. 1 minOne note

   Write down the one change you'll notice in your games — "Thresh hook into ult is 50 damage weaker per rank" — and play a normal before ranked.

Reading the dev context

Under most changes Riot writes a sentence or two about why. That text is more useful than the numbers, because it tells you what Riot thinks is wrong — and therefore what might change next. The 26.22 notes are full of good examples:

Read them for three signals. "Harder than we expected" and "softer than we expected" (Viktor, Smolder) mean Riot is correcting its own last change, so the champion is moving back toward where it was. "On the fence last patch" (Yasuo after Yone) means a follow-up to an earlier change. And "a much deeper champion" (Locke) means Riot expects the champion's performance to keep rising as players learn it, so it's nerfing ahead of that curve.

Which numbers actually matter

Not every number has the same weight. A rough guide, using 26.22's changes as examples — BoostPirate's reading, not a Riot rule:

Why Riot changes what it changes

Riot published its champion balance framework in a dev post on 30 May 2019 and updated it on 30 June 2020. It watches four groups of players and flags a champion as too strong if it crosses the line for any one of them — and too weak only if it falls below the line for all four:

For average and skilled play the win-rate line tightens as ban rate rises — the 2019 post has average play at 54.5% when a champion's ban rate is below the average (about 7%), down to 52.5% at five times that. The 2020 update tightened the average and skilled lines by 0.5% and widened elite play from the top 0.1% to the top 0.5% of players. Riot hasn't republished the exact lines since, so treat these as how Riot thinks rather than today's numbers.

Two parts of the framework explain a lot of patches. It deliberately leaves mastery data out of buff and nerf decisions, so champions with a steep learning curve aren't nerfed just because experts win with them. And new and reworked champions aren't held to the lines for about a month after release, so expect bigger swings in their first patches. The pro-play line also explains why a champion can be nerfed while it looks average in your games: high presence in pro play is enough.

Patch-to-patch chains: 26.21 → 26.22

Single patches make more sense as part of a chain. Four from the last two patches, from Riot's 26.21 and 26.22 notes:

The lesson: when Riot nerfs a champion, watch the next patch for the correction or the follow-up. Viktor's 26.21 nerf was partly reversed two weeks later; Yone's nerf led to Yasuo's. If your main was hit, the next patch's dev context often tells you whether Riot thinks it went too far.

Reading the meta on stat sites

Patch notes tell you what changed; stat sites tell you what happened. They're useful if you read them the way Riot's own framework does — by group, by sample size and by change rather than by one number. Start with sample size. A win rate is a measurement with noise, and the noise is bigger than most people think. For a champion that truly wins 50% of games, plain statistics give these 95% ranges:

iTero's 2023 analysis of win-rate data gives the other traps with real examples: a Kayle top win rate of 67% over three games that "might as well read: win rate between 0–100%"; a Qiyana mid win rate below 45% for first-time players and above 55% once mastered; and a jungle Rammus at 56% in Iron. Its advice matches ours — use the relative change from patch to patch for the same champion and rank filter, not a raw number. A checklist before you believe a meta claim:

• Same rank filter as you. A champion that's strong in Diamond+ can be weak in Gold, and the other way round.
• Thousands of games, not hundreds. Below a few thousand, a few points of difference is noise.
• Compare to last patch. A champion going from 49% to 51% after a buff is a real signal; 51% on its own isn't.
• Check pick and ban rate. A low pick rate often means the champion is played by its specialists, which lifts its win rate.
• Wait a few days. The first day of a patch is played by the players who rush to try changes — not a normal sample.

Previews and the PBE aren't final

Preview lists are useful for planning, but they change. AltChar's report on the 26.22 preview (27 October) listed adjustments for Aurora, Mel and Renekton and changes to Doran's Bow and Doran's Blade. In the final notes, Mel got her midscope, Doran's Bow lost 1 AD — but Aurora and Renekton only appeared in the bug fixes, and Doran's Blade wasn't changed at all. Riot's PBE FAQ says the same about test content in general: what you see on the PBE may never be added to the live game. Don't change your pool on a preview; wait for the notes.

Adapting your climb to a new patch

The point of reading patches is to lose fewer games to them. BoostPirate's patch-day routine:

Patches also move the timing of the season. The last patch of 2026 is 26.24; our season end guide tracks when ranked closes, and the power spikes guide covers how item and level timings shift with balance changes.