How League of Legends Patch Notes Work: A Complete Reader's Guide

League of Legends operates on a two-week patch cycle, meaning Riot ships approximately 24 numbered patches per year. Patches are labeled with a season number and a sequential patch number — for example, 15.1 is the first patch of Season 15, 15.2 is the second, and so on. This cadence has been consistent for years and gives players a reliable rhythm for when to expect balance changes.

Patches go live on Tuesday mornings in North America, typically around 6 AM ET. Other regions follow on the same day during their local maintenance windows. Before reaching live servers, changes are tested on the Public Beta Environment for roughly one to two weeks. Monitoring PBE changes is one of the best ways to get ahead of the meta before a patch officially drops.

Not every patch carries the same weight. Some are small patches with targeted tweaks to a handful of champions, while others are sweeping system overhauls affecting items, objectives, or runes. Mid-season and preseason patches tend to be the largest and most disruptive. Recognizing the scope of a patch the moment notes drop helps you prioritize which changes to study first.

Riot structures patch notes into consistent top-level categories: champion changes, item changes, rune changes, system changes, and bug fixes. At the very top you will usually find a brief editorial summary written by a Riot designer. This narrative section explains the design intent behind the biggest changes, not just the raw numbers. Reading it first gives you context for everything that follows.

Each champion entry lists the specific stats or abilities modified. Riot uses a straightforward format: the old value appears first, followed by an arrow and the new value. For example, "Base AD: 62 → 58" means the champion lost four base attack damage. Color coding — typically red for nerfs and green for buffs — lets you scan quickly, but the magnitude and type of change matter far more than the color alone.

Systems changes are often buried toward the bottom of the notes and receive less community attention despite sometimes being the most impactful section. An objective timer change, a drake buff, or a change to turret plating gold can reshape entire strategies without a single champion being touched. Make a habit of reading the systems section before diving into champion entries.

Not all stat changes carry equal weight, and raw percentage differences can be misleading. A base damage reduction from 100 to 95 is a five-percent nerf, but a base AD reduction from 62 to 58 on an AD-scaling champion compounds across all auto attacks and ability damage for the entire game. Context — what the stat feeds into and how often it is used — matters far more than the isolated number.

Ability cooldown changes are among the most impactful stat types to watch. Reducing an ultimate from a 120-second cooldown to a 90-second cooldown is a 25 percent improvement in availability, dramatically changing a champion's teamfight presence and skirmish potential. Players often overlook cooldown buffs because the number looks small, but compounded over a 35-minute game the ability may come up several additional times.

Scaling changes — like an ability's AP ratio shifting from 70 percent to 80 percent — reward itemization knowledge. A ten-percentage-point scaling increase benefits late-game builds far more than early-game skirmishes. When evaluating a scaling buff, think about the standard build for that champion and at what point in the game the ratio change becomes meaningful, because that is when the champion's power will spike.

A buff on a champion who was already strong is very different from a buff on a champion sitting at 47 percent win rate for three patches. Riot publishes the intent behind changes, and cross-referencing current champion performance data on sites like U.GG or Lolalytics alongside the raw notes tells you whether a change is likely to push a champion into meta-defining territory or merely bring them back to playable.

Item changes interact with champion kits in non-obvious ways. When Riot buffed Luden's Tempest in patch 14.10, the ripple effect boosted every poke mage who built it as a first item, not just the handful specifically mentioned in the notes. Identifying which champions benefit most from indirect item buffs is one of the highest-value skills for climbing in the days immediately following a patch.

Rune changes similarly propagate across many champions at once. A nerf to Conqueror in patch 14.7 hit every melee bruiser who relied on it for sustained damage — Camille, Fiora, Irelia — without any of those champions appearing in the champion-specific section. Tracking rune meta shifts requires you to think in terms of keystones and which champion archetypes depend on them.

The Public Beta Environment runs changes for one to two weeks before they reach live servers. PBE patch notes are posted in Riot's developer forums and aggregated by community sites like Surrenderat20. Tracking PBE is especially valuable for item changes and rework previews, where you can begin theorycrafting builds before the patch is live and arrive at conclusions ahead of the broader player base.

PBE data has limitations. Riot frequently tweaks numbers mid-PBE cycle, meaning the first announced values may not be the final values that ship. Treat PBE notes as directional signals rather than final truth. Focus on whether a change is a buff or nerf, which champions or item archetypes it affects, and roughly how large the magnitude appears — leave precise build optimization for the first 48 hours on live servers.

Content creators and competitive analysts increasingly cover PBE changes in real time. Following high-Elo players who main the champions you play is one efficient way to absorb PBE analysis passively. Challenger one-tricks often identify edge cases — like a stat interaction that makes a previously unviable rune suddenly optimal — within hours of changes hitting PBE, well ahead of any tier list update.

Riot reserves the right to push mid-patch updates at any time without a scheduled maintenance window. These typically appear as addendum sections appended to the existing patch notes page, labeled with the date the change was applied. When a champion is released or reworked, it is almost guaranteed that at least one mid-patch adjustment follows within the first few days as Riot observes live-server data.

Mid-patch changes are easy to miss because they do not generate the same community noise as a full patch release. Bookmarking the patch notes page and checking it a few days after a patch drops prevents you from making decisions based on outdated information. Many players continue building around a champion that was quietly hotfixed days earlier, costing them LP with no understanding of why performance suddenly dropped.

Major hotfixes signal that something slipped through PBE testing at an unexpectedly broken power level. Champions like Kai'Sa after the 13.1 itemization update and Aurelion Sol post-rework both received emergency nerfs within 48 hours of release. When you see a hotfix incoming, the logical move is to either exploit the champion before the nerf or avoid it entirely depending on how quickly the correction is expected.

The most actionable use of patch notes is identifying which champions moved from unplayable to viable in a single patch. Players who were grinding a champion at 47 percent win rate and then receive a meaningful buff can leverage the improved stats immediately. Being the first player in your MMR bracket to pick up a freshly buffed champion gives a genuine skill advantage because opponents have not yet adapted their counterplay.

Conversely, recognizing nerfs early lets you stop investing in champions before their win rate collapses on ladder. If you have been one-tricking a champion that received a significant damage nerf, spending the first week transitioning your rune page and secondary picks is far more efficient than grinding through the statistical decline. Tier lists take days or weeks to catch up to patch reality; your own analysis can lead by a significant margin.

Tracking multiple patches sequentially builds intuition for Riot's balancing philosophy. Riot tends to ship conservative buffs first, observe for one to two patches, then adjust further if a champion is still underperforming. Recognizing this pattern lets you anticipate when a champion who received a minor buff in patch 15.3 is likely to receive another in 15.5, setting up a strategic early investment before the second buff drives mainstream adoption.

Several third-party tools make patch note analysis substantially faster. U.GG and Lolalytics both update their win-rate and pick-rate data within 24 to 48 hours of a patch going live, giving you empirical confirmation of whether a buff actually moved the needle. ProBuilds.net shows how high-Elo players are adjusting their builds in response to changes, which is especially useful for item-focused patches.

Wombo Combo's summoner search lets you look up specific players by their Riot ID to see which champions they have been playing post-patch and how performance has shifted. Tracking high-Elo players who main a champion that was just buffed gives you a real-world data point beyond theoretical analysis — if Challenger players immediately pick up the champion and post strong stats, that is a confirmation signal worth acting on.

Spreadsheets and personal patch logs are underrated tools for long-term improvement. Noting which champions you correctly identified as rising or falling with each patch builds a track record you can analyze over time. Players who treat patch analysis as a repeatable skill — rather than a one-time exercise before rank games — develop a consistent meta-reading advantage that compounds across an entire season.