How Many Dudes? synergies come from matching a Dude's Ability with useful stats, a controlled Relic pool, a suitable Trinket, and teammates that solve the same encounter. The game supports more than 850,000 team compositions, so this guide explains verified interactions and repeatable planning rules instead of claiming that one fixed team wins every run.
How Synergies Work
A synergy is an interaction in which two or more choices strengthen the same plan. One Dude may supply damage, another may keep the group alive, and a third may provide the speed or coverage needed to continue attacking. Relics and Trinkets then reinforce those jobs, while the current encounter determines whether the completed team can use them effectively.
How Many Dudes? has 42 roster Dude Types divided among six Families: Action, Employed, Fantasy, Sci-Fi, Undead, and Warrior. Regular Dudes follow separate rules outside those six Family groupings. A Family label can help connect a roster, but sharing a Family is not enough by itself; Abilities, useful stats, survivability, and the problem presented by the next battle still matter.
The official material says that every Dude can become extremely strong when supported correctly. This makes a role-first question more useful than asking which Dude is always best. Start by asking what the Dude does, which stats improve that job, what can stop the Dude from doing it, and which teammate can cover that weakness.
Keep the Relic Pool Focused
Posting a Flyer for a roster Dude adds seven Relics for that Dude and eight Relics for its Family to the available pool. Duplicate Family Relics are added only once. Recruiting across many Families therefore expands the number of possible Relics, which can make a specific effect harder to find even when every individual recruit looks useful.
Before posting another Flyer, review the current team in three layers. Identify the primary way the team wins, list the stats and effects that support that win condition, then decide whether the new Dude improves those needs enough to accept a broader Relic pool. This simple pause protects a coherent run from becoming a collection of unrelated good ideas.
Verified Dude and Stat Pairings
The following pairings come from examples already recorded from official guidance. They describe stat affinity and Ability support, not a complete ranking. Each pairing still depends on available Relics, a suitable Trinket, teammates, challenge level, and the encounter ahead.
Mutant: Cleave, Attack Power, and Attack Speed support Mutant's documented direction. Cleave helps attacks affect more targets, while power and speed improve the pressure created by those attacks. This plan still needs enough survival and access to targets; adding damage does little if Mutant cannot stay active.
Pirate: Evasion and Crit Chance match Pirate's confirmed affinities. Evasion supports continued activity by avoiding some incoming pressure, while Crit Chance improves offensive spikes. A Pirate plan should still account for attacks that are not reliably solved by evasion and for encounters where burst damage must arrive at the correct time.
Knight: Toughness and Max HP support Knight's durable role. This pairing is useful when the team needs a Dude who can survive heavy pressure and keep the rest of the roster functioning. It does not make all damage irrelevant, so recovery, Temporary Health, Cheat Death effects, or other protection may still be needed in demanding encounters.
Electrician: Attack Power and Run Speed are documented affinities for Electrician. Power strengthens the relevant output, and movement helps Electrician spend more time in useful positions. Run Speed is especially practical when slow pursuit would otherwise reduce damage even though the team's raw numbers look strong.
Ranger: Hunter's Blade can work with Crit Chance to produce far more Magic Arrows. This is the clearest recorded example of an effect and stat reinforcing the same Ability loop. The interaction gives a direction for the build, while the rest of the roster still has to protect Ranger and handle enemies that limit the team's ability to maintain that loop.
Relics and Trinkets
Relics are the main way to alter a Dude's Abilities and stats during a run. A useful Relic supports the team's chosen job, closes an identified weakness, or enables an interaction that the roster can repeatedly use. A rare-looking effect that points in a different direction can be weaker than a modest effect that reinforces the plan already working.
One Trinket can be bound to each roster Dude Type during a run. The official guidance recommends learning what an Ability does, which stats help it, and which Trinket reinforces the intended role. Because a Trinket is tied to a Dude Type, judge it as part of that Dude's complete job rather than as a free bonus that can be moved wherever convenient.
Use a three-part check when comparing options: does the effect improve the Dude's main Ability, does the team create the conditions needed to trigger or use it, and does it matter in the next dangerous encounter? An option that passes all three checks is a genuine synergy. An option that only raises a number may still be helpful, but it should not distract from a more urgent structural weakness.
Build for the Encounter
The value of a Dude changes with the scenario. The official Tier List Maker warns that context matters, and the documented boss guidance shows why. A team that clears ordinary waves quickly can still fail when a boss demands protection from heavy hits, movement speed, sustained access to the target, or control of many accompanying enemies.
The G.O.A.T. encounter at Round 105 is a concrete example. The boss is described as fast, high in health, capable of burst damage, and accompanied by several hundred Ram minions. Toughness, Max HP, Temporary Health, Cheat Death effects, and Run Speed can matter because the team needs to survive large hits and remain close enough to keep attacking.
This does not turn one defensive setup into a universal answer. Earlier rounds, later Challenge Tiers, Daily Dude rules, and Ensemble Mode can change the available roster and the problem being solved. Name the encounter before judging the build, then keep recommendations tied to that situation.
A Repeatable Team-Building Process
Start with one primary job such as sustained damage, repeated Ability triggers, survival through large hits, or enough movement to maintain contact. Choose a Dude whose documented Ability and affinities support that job. Then add teammates that improve the same plan or cover a specific weakness without widening the Relic pool more than necessary.
After every important battle, review what actually failed. If damage is high but Dudes cannot reach the target, movement may matter more than another offensive bonus. If the team reaches the target and disappears during one burst, add protection or recovery before increasing damage again.
Use this short sequence during a run:
- Define the next encounter's main threat.
- Identify the current team's win condition.
- Choose stats, Relics, and Trinkets that reinforce that condition.
- Add a teammate only when the benefit justifies the new Relic options.
- Review the battle result and change the weakest link first.
What Still Needs Testing
The available official material confirms systems and several stat-affinity examples, but it does not establish one universal Tier List, exact best team, or guaranteed build order. Exact drop probabilities, every cross-Dude interaction, and version-specific performance also require controlled testing. This guide will not turn community enthusiasm or a single successful run into a general rule.
A reliable comparison should name the game version, Challenge Tier, encounter, roster, Relic pool, Trinkets, and repeated test conditions. When those details are missing, treat a suggested combination as an experiment. The wording on this page will be updated when stronger evidence supports a more precise recommendation.
Continue Your Run
Use the Beginner Guide for recruiting, recovery, economy, and first-run priorities. The Game Guide explains the full roster, Families, Relics, Trinkets, and modes, while the G.O.A.T. Boss Guide applies survival and mobility planning to the documented Round 105 encounter.
The Wiki Hub collects every completed guide and official resource. For current entity descriptions, Ability text, Relics, Trinkets, Stats, Enemy Types, and Enemy Traits, continue to the official Dudex.