Patch Notes Explained - How to Read Updates

Task Bar Hero patches typically run every six to eight weeks. Each patch touches balance, content, and bug fixes. This guide covers how to read a patch thread quickly using the public wiki catalog as your reference, and how to tell whether your current build will survive the patch.

Section Structure

A typical patch thread has four sections:

1. New Content - new heroes, stages, items, runes, or Cube functions.
2. Balance Changes - stat adjustments to existing heroes, items, or runes.
3. Bug Fixes - list of resolved bugs.
4. Known Issues - bugs the team is aware of but has not fixed.

The first three sections affect your gameplay. The fourth is informational only.

What to Skim

The New Content section is usually safe to skim. New heroes and stages are gated by unlocks, so they do not affect your current gameplay unless you have already reached the relevant stage.

The Bug Fixes section is mostly informational. Read it only if you have been experiencing a specific bug.

What to Read Carefully

The Balance Changes section is the most important. Balance changes can break your current build. The changes that matter most:

• Stat adjustments to heroes you actively use.
• Stat adjustments to weapons or armor in your current loadout.
• Cooldown or duration changes to skills you rely on.

For example, if a future patch reduced the Knight's Shield Charge movement distance by more than 10% compared to the catalog's current 1.43 base DPS / 0.6/s attack speed profile, your frontline play would lose reach and you would need to compensate with a faster frontline partner. That is a meaningful nerf and the response is to look at the Best Builds page for the new recommended team shell.

The catalog's Community Tier field is the single number to watch per hero. A drop from S to A for a hero you have invested in is the kind of change that justifies a swap to a hero whose Community Tier did not move.

How to Tell Whether Your Build Breaks

The rule of thumb: if a balance change reduces a key stat by more than 10% compared to the public catalog, your build needs an adjustment.

The key stats to watch:

• Hero base HP, ATK, armor (especially for tanks like Knight and damage dealers like Slayer or Sorcerer).
• Weapon stat bonuses for the weapon in your main slot.
• Skill damage multipliers and cooldowns for the skills you have slotted on your active hero.
• Rune Tree node values if the patch touches the Formation, Wealth, or Combat branches.

Minor changes (under 5%) are usually safe. Moderate changes (5 to 10%) might require a rune swap or a gear refresh. Major changes (over 10%) require a rebuild.

Why the Catalog Is Your Shortcut

The wiki catalog records a patchVersion field on every entity. After a patch lands, the diff between the old and new patch numbers tells you exactly which heroes, items, skills, runes, stages, monsters, or Cube functions the team changed.

Practical workflow after a patch:

1. Note the new patchVersion and the date on the official patch thread.
2. Open the wiki Updates page and look for the same patch version.
3. Compare the new catalog rows to the previous patch via the per-entity history link in the database.
4. Identify any hero, item, or rune in your active setup that changed.

That four-step loop is faster than reading the full patch thread, because the catalog only surfaces what actually changed.

After the Patch

After reading the patch notes:

1. Note the changes that affect your current build.
2. Calculate the net impact on your team's DPS and survivability.
3. Decide whether to switch heroes, swap gear, or accept the change.
4. Cross-reference the new values against the wiki catalog before committing resources.

Most patches do not break existing builds. The few that do usually telegraph the change in the patch notes' Known Issues section the patch before.

What About Hero and Rune Additions

The current catalog has six heroes (Knight, Ranger, Sorcerer, Priest, Hunter, Slayer) and eight Rune Tree branches. When a patch adds a hero, the addition lands as a new entry in the hero catalog with its own patchVersion and updatedAt. When a patch adds a rune branch, the addition lands as a new entry in the rune catalog with its own Recommended Order field.

Earlier drafts of this guide used "Mage", "Samurai", and "Necromancer" as example heroes. Those heroes are not in the current catalog. Use Knight, Ranger, Sorcerer, Priest, Hunter, or Slayer when you need a concrete hero reference, and use one of the eight named Rune Tree branches when you need a concrete rune reference.

Wrap-up

Patch notes are a learning tool. Read them carefully, but do not panic. Most changes are small balance adjustments that do not require immediate action. Use the wiki catalog as your authoritative reference for what actually changed, and verify concrete numbers against the database before committing saved inputs.