Task Bar Hero Tools

Find the verified Windows save folder, protect a good copy from Steam Cloud overwrite, and choose the safest available recovery path.

Use when

Use when progress disappeared, another PC may hold the good save, Steam Cloud synced the wrong state, or the game no longer launches.

First action

Fully close the game and copy the entire TaskBarHero save folder before renaming, replacing, or synchronizing files.

Confidence

Official developer FAQ

Source

developer-pinned Steam recovery guide

Separate survivability, Priest support, carry DPS, farming, and rebuild timing for 2-10 Nightmare.

Use when

Use when early Nightmare progress stalls before the party is ready for heavier rune pivots.

First action

Check the quick diagnosis table before changing your whole party.

Confidence

Player reports

Source

manual guide notes

Split 3-10 Nightmare boss walls from Hell Soulstone, chest route, and rune-pivot decisions.

Use when

Use when the same stage feels like a survival, DPS, and farming problem at once.

First action

Choose the blocker type, then route back to solver, farming, or Rune/Cube help.

Confidence

Player reports

Source

community questions + notes

Focus on 3-10 Hell clear stability, route consistency, Soulstone and chest decisions, and whether farming beats a rebuild.

Use when

Use when Nightmare is already readable and the active question is specifically Hell progress or reward routing.

First action

Check whether the latest Hell block failed, cleared noisily, or only felt bad because of rewards.

Confidence

Player reports + estimates

Source

Similarweb + guide notes

Separate Hell Soulstone routes, chest farming, dry streaks, and stage-wall decisions without inventing official rates.

Use when

Use when Soulstone, chest attempts, route consistency, and stage progress are getting mixed together.

First action

Check whether the problem is route consistency, dry streak, or the wrong bottleneck.

Confidence

Needs verification labels

Source

manual notes + player reports

Plan repeatable chest farming routes, dry-streak checks, fallback farming, and when Soulstone is the wrong bottleneck.

Use when

Use when the search is about chest farming in general, not a single Hell Soulstone or 3-10 Hell stage problem.

First action

Pick whether the current issue is route volume, failed clears, dry streaks, or the wrong farming target.

Confidence

Player reports + estimates

Source

Similarweb + Autocomplete + manual notes

Read chest drop-rate searches safely with source status, attempt logs, route comparison, and uncertainty boundaries.

Use when

Use when the search asks for chest drop rates, but no reliable official percentage or hidden loot table is available.

First action

Check the quick answer, then log one fixed-route block before changing build, runes, or farming target.

Confidence

GSC archive + Autocomplete + SERP + estimates

Source

GSC archive + Autocomplete + SERP + manual notes

Prioritize runes by the active blocker, gold pressure, hero slots, Cube state, chest flow, and route stability.

Use when

Use when the search is about rune priority, not a full rune tree, official formula, or exact cost database.

First action

Pick the blocker first, then decide whether combat, economy, chest-flow, or slot-preserving spend comes next.

Confidence

Player reports + estimates

Source

Similarweb + Autocomplete + SERP + manual notes

Compare class builds by current blocker, role, farming route, Rune/Cube timing, and a one-block test plan.

Use when

Use when the search asks for the best build, but the real answer depends on survival, carry damage, support, or farming stability.

First action

Pick the blocker first, then choose one class plan to test instead of copying a universal tier list.

Confidence

Player reports + estimates

Source

Similarweb + Autocomplete + manual notes

Use a blocker-first scorecard to compare class roles, attempt logs, Rune/Cube timing, and farming context before changing builds.

Use when

Use when the search asks for a build calculator, but exact official formulas or hidden class coefficients are not available.

First action

Score survival, boss HP, wave pressure, route consistency, and resource cost before picking one build test.

Confidence

GSC archive + Autocomplete + estimates

Source

GSC archive + Autocomplete + manual notes

Read skill tree choices by current blocker, class role, Rune/Cube timing, and farming route without fake official formulas.

Use when

Use when the search is about the skill tree as a system, not a full official tree, exact node cost table, or universal best path.

First action

Name the blocker first, then decide whether survival, carry damage, class role, Rune/Cube timing, or farming stability comes next.

Confidence

Player reports + estimates

Source

Similarweb + SERP history + manual notes

Read the complete visible skill tree as branch groups, role paths, upgrade order, and mistakes to avoid.

Use when

Use when the search asks for the full skill tree, not a datamined node table, exact official costs, or hidden formulas.

First action

Split the tree into survival, carry damage, support, economy, route, and late test paths before spending broadly.

Confidence

GSC archive + Autocomplete + SERP + estimates

Source

GSC archive + Autocomplete + SERP + manual notes

Decide when Priest solves survival, when a carry still needs DPS, and when safer farming beats a broad rebuild.

Use when

Use when build searches point to Priest but the real blocker may be uptime, damage, gear, or route stability.

First action

Run one Priest test block with the carry fixed, then compare the failure timing.

Confidence

Player reports + estimates

Source

manual guide notes

Choose Sorcerer AoE tests, protect the backline, and decide when gear, XP, runes, or farming beat another spell swap.

Use when

Use when build searches point to Sorcerer but the real blocker may be wave pressure, survival, scaling, or noisy testing.

First action

Pick one elemental plan, keep the party protection fixed, then compare failure timing.

Confidence

Player reports + estimates

Source

public guide checks + notes

Prioritize Hunter as a focused carry test, protect the damage window, and decide when gear, farming, or runes beat another class swap.

Use when

Use when build searches point to Hunter but the real blocker may be carry uptime, frontline protection, boss damage, or noisy farming tests.

First action

Keep one Hunter plan fixed for a short block, then compare whether deaths, boss HP, or route stability actually changed.

Confidence

Player reports + estimates

Source

Similarweb + Autocomplete + manual notes

Prioritize Ranger as a steady ranged uptime test, protect the damage window, and decide when gear, farming, or runes beat another class swap.

Use when

Use when build searches point to Ranger but the real blocker may be carry uptime, frontline protection, boss damage, route stability, or noisy rune timing.

First action

Keep one Ranger plan fixed for a short block, then compare whether deaths, boss HP, or route stability actually changed.

Confidence

Player reports + estimates

Source

Similarweb + Autocomplete + manual notes

Prioritize Knight as a frontline uptime test, protect carry damage, and decide when gear, farming, or runes beat another class swap.

Use when

Use when build searches point to Knight but the real blocker may be frontline uptime, carry damage, support, route stability, or noisy farming tests.

First action

Keep one Knight plan fixed for a short block, then compare whether deaths, boss HP, or route stability actually changed.

Confidence

Player reports + estimates

Source

Similarweb + Autocomplete + manual notes

Prioritize Mage as a magic carry test, protect the backline damage window, and decide when gear, farming, or runes beat another class swap.

Use when

Use when build searches point to Mage but the real blocker may be magic uptime, backline protection, boss damage, or noisy farming tests.

First action

Keep one Mage-style magic plan fixed for a short block, then compare whether deaths, boss HP, wave pressure, or route stability actually changed.

Confidence

Player reports + estimates

Source

Similarweb + Autocomplete + manual notes

Test Inferno as burn pressure, fire-style damage, or protected backline uptime without inventing official formulas.

Use when

Use when build searches point to Inferno but the real blocker may be survival, sustained damage, wave pressure, or noisy farming tests.

First action

Keep one Inferno plan fixed for a short block, then compare deaths, boss HP, wave pressure, route stability, and Rune/Cube opportunity cost.

Confidence

Player reports + estimates

Source

Similarweb + manual notes