How Many Dudes? Wiki - Progression: Tiers, Stars and Collections

Progression in How Many Dudes? is built around learning a deep roster rather than abandoning early Dudes for a permanently superior tier list. The official New Player Guide says every Dude can be strong through the right Relics, Stats, team composition, and Trinket. The full-release Steam page frames the longer journey around three Tiers, Stars, Collections, Pocket Dice, modes, and Steam achievements.

Use this hub to decide what to pursue next and what evidence a failed run actually gives you. The exact unlock thresholds and reward amounts are not fully published in the sources used here, so the live client remains authoritative for any requirement displayed on your account. For a closer look at difficulty progression and retroactive credit, continue to the Tiers guide.

Treat the three Tiers as learning layers

The developer guide identifies the G.O.A.T. as the Tier 1 boss at round 105. That gives early progression a concrete target: build and refine a five-Dude team that can survive the normal run and answer its first major boss test. A loss before or at that point should produce a specific roster, economy, or timing lesson.

Higher Tiers are not a reason to rush past the first. The guide says Tier 2 and Tier 3 provide harder bosses and more rewards. Move up when you can explain why the previous team succeeded and which parts remain robust under greater pressure, not merely because the menu now permits it.

The official guide also says that later accomplishments can grant Stars for lower Tiers retroactively. This prevents a strong higher-Tier result from becoming wasted lower-level cleanup. It does not mean every reward or requirement backfills in the same way; confirm the exact Star display in the live progression interface.

Use Stars to map breadth, not just repetition

Stars are tied to progression performance in the official material. A useful way to read the Star board is as a coverage map: it highlights Types or challenges you have not yet proved at a given Tier. The board can therefore suggest the next experiment without declaring that an unstarred Dude is weak.

When pursuing a new Star, preserve a familiar support core and change the smallest necessary part of the roster. This keeps the test readable. If the whole team changes at once, success or failure says little about the Dude or interaction you intended to learn.

Record the Tier, boss reached, five Types, represented Families, defining Relics, and the immediate failure. A Star attempt that dies to one large impact needs a different correction from one that times out or cannot reach priority enemies. The progression screen gives the destination; this record gives the next action.

Expand Collections through deliberate experiments

The Steam page describes Collections as a full-release progression feature. Use Collection gaps as prompts to inspect content you have overlooked: an unfamiliar Type, a Family set, a Relic trigger, or another tool the roster can incorporate. Collection completion is most valuable when it also expands your working vocabulary for team construction.

Do not turn the Collection into an unsupported checklist copied from an old demo guide. The official Dudex is the current public reference for Dude Types and other content, and the live Collection screen reflects what the base game expects from the current account. Support or summoned entities can also appear in a database without counting as ordinary recruitable roster Types.

When an entry depends on a mechanic you do not understand, read its live description before spending a run on it. Define the trigger, owner, target, duration, cooldown, and desired payoff. Then create a team that can make the event happen often enough to observe it.

Spend Pocket Dice with a clear purpose

The full-release Steam description names Pocket Dice as a progression system. Public material reviewed for this page does not provide a complete current table for Dice costs, acquisition rates, or every use. Read the live interface before committing a scarce resource, especially when an older video or demo discussion states a specific number.

Give each spend a written objective: broaden a tested option, support a current Tier push, or improve access to a Collection goal. Avoid spending only to make a notification disappear. Resources create more progression when they support a planned series of runs than when they are scattered across unrelated ideas.

After the spend, compare results rather than assuming the account upgrade solved the problem. If the same fight still ends for the same reason, roster structure or execution remains the bottleneck. A progression currency should amplify good decisions, not replace diagnosis.

Separate account goals from run goals

An account goal may be earning a Star, filling a Collection entry, trying a new mode, or completing an achievement. A run goal should be narrower: verify one synergy, defeat one boss, or test whether a defensive answer changes a known loss. The narrow run goal tells you what to buy when several upgrades compete.

Before starting, choose one primary account goal and one learning goal. A Tier push might pair with learning a new Family interaction. A Collection attempt might pair with understanding a Relic trigger. If the run cannot advance both, protect the primary goal rather than turning every purchase into a side quest.

The Steam page currently lists 69 Steam achievements for AppID 3934270. Treat that count as storefront state checked on 2026-08-01, not as an eternal number. Use the live Steam achievement list for exact names, hidden status, and current completion conditions.

Convert a boss wall into a progression plan

First, classify the wall. Fatal burst calls for effective health, prevention, control, or better timing. Slow attrition calls for recovery. Inability to damage a target calls for access, targeting, movement, or a different damage profile. Running out of purchasing power calls for an economy review.

Second, find the earliest decision that could change that ending. It may be a Flyer that opens the wrong Relic pool, spending too much before a key shop, or adding damage while survival is already failing. Correct the earliest causal decision rather than only the final purchase.

Third, decide whether to retry at the same Tier. Repeat when the premise has a clear corrective branch. Step down when you need a lower-pressure environment to learn an interaction. Move up when the current Tier is consistently solved and the higher Tier will expose the next weakness.

Verify what belongs to the current base game

This guide is scoped to the base game at Steam AppID 3934270, released July 30, 2026. It does not treat the earlier demo, a Playtest, DLC, a soundtrack, or another store product as interchangeable evidence. The July 23 official news says demo progress can transfer, but transferred history does not make every demo-era rule current.

For any numeric threshold not stated by the cited full-release sources, use the live client. That includes exact unlock steps, individual reward quantities, Pocket Dice costs, and mode-specific scoring. This boundary keeps progression advice useful even when account state or balance changes.

A practical next-session route

Choose one unfinished Star or Collection target. Open the corresponding Dude and Relic definitions in the game or official Dudex. Build a roster premise with a named damage plan and survival plan, choose the Tier that will test it cleanly, and preserve enough cash to see the relevant pool.

After the run, update only three facts: the furthest round or boss, the exact failure pattern, and the earliest decision you would reverse. Then read the Tiers guide if the next decision is whether to remain at the same difficulty, step down to practice, or move upward.