How Many Dudes? Wiki - Modes: Classic, Daily, Ensemble and More

How Many Dudes? has several ways to turn the same roster-building systems into different problems. The official New Player Guide discusses Classic, Daily Dude, Ensemble, Endless, and Rematch while explaining Flyers and Relic-pool control. That makes one distinction especially useful: a mode is not just a run-length option. It can change how much of the team is known at the start and whether you can shape the item pool before the first round.

This hub helps you choose a mode without pretending that one is universally best. If you are learning the economy and normal recruiting cadence, begin with Classic. If you want a fixed puzzle, a curated roster, a longer survival test, or another attempt at a known fight, use the mode whose constraint matches that goal. Check the live mode-select screen for exact availability and rules because public developer material does not document every menu detail or unlock condition.

Start with the question you want the run to answer

Choose Classic when the question is, “Can I build a functioning team from the normal opportunities this run gives me?” The mode is the cleanest place to practice adapting Flyers, purchases, Stats, and Relics as they arrive. It teaches the baseline relationships that transfer into modes with stronger opening constraints.

Choose Daily Dude when you want a shared or fixed daily problem rather than an open-ended practice session. The official guide confirms that all five Flyers are pre-posted in this mode. That means the roster identities and their associated Relic pool are committed from the opening, so the skill test shifts from choosing who enters the pool to using the given pool well.

Choose Ensemble when you want deliberate pre-run construction. The developer guide says you can pre-post some of the five Flyers and leave other positions to be filled randomly during the run. Ensemble therefore supports a useful spectrum: lock an entire concept, lock only the indispensable core, or accept more random partners in exchange for flexibility.

Choose Endless when the goal is to find how long a functioning engine can survive and scale. The official guide names the mode but does not publish a complete rule sheet in the material used here. Treat the live menu and in-game prompts as authoritative for its current starting state, scoring, and termination rules.

Choose Rematch when you want another controlled attempt with all five Flyers already posted. The official guide groups Rematch with Daily Dude for this pre-posted state. That makes it useful for studying execution, purchase order, or Relic choices without rebuilding the recruitment premise from scratch.

Flyer state controls more than the team list

Posting a Flyer does two jobs. It recruits toward a five-Dude team, and it changes the Relic pool. The official guide explains that a roster Dude Type contributes seven dedicated Relics while its Family contributes eight shared Relics, each added once. A pre-posted team therefore begins with a much more defined pool than an empty or partially filled board.

In Daily Dude and Rematch, the five pre-posted Flyers put the complete team pool into play immediately. You cannot rescue a weak pool by simply refusing an optional Family later; the meaningful decisions are which available effects help the fixed roster and how to spend enough currency to see them.

Ensemble exposes this mechanism directly. Pre-posting only the core can keep an essential Dude set or Family set relatively concentrated, while empty positions preserve room for discoveries during play. Pre-posting all five gives maximum identity and minimum recruitment uncertainty, but it also commits every selected Family and dedicated set to the pool.

Classic should be read as the adaptation benchmark. The official guide contrasts its normal Flyer flow with modes that pre-post Flyers. Evaluate each new recruitment opportunity as both a unit decision and a future-offer decision, especially when the current build still needs one defining Relic.

Match the mode to your current learning stage

New players benefit from Classic because a failed run produces broad lessons. You can ask whether the team lacked durable front-line presence, target access, healing, damage, or a stable economy. You also see the cost of widening the Relic pool before the core is ready. Those lessons remain useful even when another mode fixes the team for you.

Once you can explain a Classic loss, Ensemble is a good laboratory. Start with a two- or three-Dude premise that has an explicit interaction, then decide whether each remaining Flyer should be selected or left random. A full preset hides adaptation weaknesses; a completely open team does not test the chosen premise cleanly. Partial pre-posting offers a middle ground.

Daily Dude works best as an evaluation exercise. Because the opening roster is supplied, define the team’s likely damage plan, survival plan, and desired economy before buying. Then compare your result with a later attempt or with another player’s reasoning. Do not assume that a daily solution remains available on another date.

Use Rematch to isolate a decision you can actually change. If the previous loss came from an early purchase, a mistimed reroll, or choosing a flashy Relic that did not address the threat, retry with that branch reversed. If the team fundamentally cannot answer a mechanic, the lesson is roster construction rather than execution.

Endless is more informative after the normal fundamentals are stable. Long survival magnifies small weaknesses: an unreliable trigger, a damage plan that cannot reach targets, poor recovery between large hits, or an economy that stops converting cash into power. Record the round and failure pattern, not just the time survived.

Build a mode-independent run checklist

At the start, identify which Flyers are already posted and which positions can still change. Then use the in-game UI or official Dudex to inspect every current Type, Family, Ability, and key Stats. A team name is not a plan until you know who starts the important trigger and who receives the payoff.

Before opening the Relic pool further, write down the effect the team most needs. It may be effective health against burst, recovery against accumulated damage, movement or target access, or additional damage after survival is secured. This prevents the mode’s novelty from turning purchases into unrelated experiments.

During the run, protect the economy needed to sample the pool. A theoretically perfect set does not matter if careless rerolls or low-value purchases prevent you from seeing enough offers. The official guide emphasizes that economy is a central system, so include cash generation and spending discipline in every post-run review.

After the loss, classify it by evidence: Did a Dude die to one large event, fall behind through repeated damage, fail to reach a target, or simply take too long to clear? Then choose the next mode or retry based on the question. Rematch can test an execution correction; Ensemble can test a roster correction; Classic can test whether the correction survives normal uncertainty.

Keep public evidence and live rules separate

The full-release Steam page advertises the core roguelite auto-battler, its large team-composition space, hundreds of Relics and Trinkets, three Tiers, and multiple modes. The official New Player Guide supplies the concrete Flyer-state distinctions used above. Neither source is a complete changelog for every mode rule.

For exact seed behavior, score calculation, unlock requirement, leaderboard timing, or current menu wording, read the live client. Do not carry a detail from the earlier demo into the base game unless the full-release client or a current official post confirms it. This page intentionally avoids inventing round limits or reward tables that the cited sources do not state.

Continue with the normal-flow baseline

Read the Classic Mode guide for a practical run framework: assess each recruitment, preserve a coherent Relic pool, stabilize before chasing ceiling, and turn a loss into the next test. The same framework makes the special constraints of Daily Dude, Ensemble, Endless, and Rematch easier to understand.