Every roster Dude Type in How Many Dudes? has baseline Stats, a unique Ability, and dedicated Relics. An Ability becomes useful only when the team can produce its trigger, reach its target, and survive long enough for the payoff. Reading those pieces separately is more reliable than assigning a Dude a fixed tier or role.
The official Dudex is the current reference for exact text. Click referenced terms in the game or Dudex whenever two words look similar: Direct Damage, Attack Damage, Healing, a Crit, a Dash, Stored Damage, and Fatal Damage can lead to different interactions.
Break the sentence into five parts
First identify the trigger. It may occur when battle starts, every few seconds, after a number of Direct Damage hits, on a Crit, when the Dude takes damage, or when an ally reaches a condition. A strong payoff attached to an unreliable trigger is not a stable engine.
Next find the owner and target. Some effects belong only to the acting Dude; others select the most-injured roster member, an adjacent roster position, a random Type, or a nearby enemy. Target wording determines whether duplicate Types cooperate, compete, or simply affect separate instances.
Then record timing and limit: interval, duration, stack cap, stored amount, or cooldown. Finally identify the scaling Stat and payoff job. An effect can scale from Attack Power, DPS, Max HP, distance, damage dealt, or another live quantity. Its job may be damage, healing, movement, prevention, control, economy, or enabling another trigger.
Position can be part of the Ability
Some definitions read the roster order directly. The current Dudex says Alien Dude beams a random Dude of the Type immediately above him on the roster, forcing a Dash toward the lowest-HP enemy. General Dude commands a random Dude of the Type immediately below him to Taunt nearby enemies.
For these mechanics, a good Type in the wrong slot can be functionally disconnected. Write the roster vertically and draw the target direction before the run. If several copies occupy a Type slot, check the wording for whether one is selected randomly or the entire Type receives the effect.
Position can also change indirect value. A movement command may activate distance or Dash effects; a forced Taunt can make a defensive trigger reliable. Evaluate both the immediate action and the event it creates for Relics, Trinkets, and teammates.
Distinguish event engines from timed engines
An event engine grows with trigger frequency. Ninja Dude’s current Ability responds to a Direct Crit, while Ranger Dude’s Magic Arrow has a chance after Direct Damage. Crit Chance, Attack Speed, additional hits, or other Stats matter only where the exact event chain supports them.
A timed engine fires on its own interval. Wizard Dude currently casts a Fireball every three seconds, and Trooper Dude calls an Orbital Strike at battle start and on a longer interval. Attack Speed does not automatically shorten every timed Ability; read the definition and choose Stats that scale the stated damage or solve downtime.
Hybrid engines require more care. Electrician Dude gains Charges from Direct Damage and discharges after reaching a threshold. Druid Dude transforms after a number of Direct Damage hits. These mechanics need both enough trigger frequency and a payoff window that lasts long enough to matter.
Read Stored, Expelled and Equalized effects literally
Several current Types transform rather than immediately erase damage. Warlock Dude slows incoming damage through Pact and can Expel part of what is Stored. Manager Dude copies and Stores a portion of Intern damage before Expelling it onto a chosen target. Mummy Dude Stores Doom on an enemy until the threshold condition is met.
Stored Damage is not automatically ordinary mitigation or ordinary damage dealt. Trace where the amount sits, when it leaves, what type it becomes, and which target receives it. The same caution applies to Transfers and Deflection.
Equalization changes two values toward a relationship instead of applying a normal flat heal. Ghost Dude’s current Phase Shift equalizes HP between the most-injured and healthiest roster Dudes, then heals them. Strange Spores also uses HP Equalization on a timed consumable window. Check which values and targets the text names before treating equalization as generic recovery.
Match Stats to the actual conversion
The developer guide gives examples of different Stat appetites. Mutant Dude benefits from Cleave, Attack Power, and Attack Speed in his damage-to-Floofball loop, while Crit Chance does not improve the described healing throughput. Pirate Dude wants Evasion and Crit Chance for his taunt-and-survival plan. Knight Dude favors Toughness and Max HP for his tanking job.
The same Stat can be essential, secondary, or irrelevant across Types. Start at the Ability formula and dedicated Relics, then ask what increases trigger frequency, payoff size, or survival during the payoff. Do not build the entire team around one Stat if several members cannot convert it.
Test one uncertain conversion at a time. Observe whether changing the Stat alters the counter, trigger cadence, or result in the live UI. A controlled test is better evidence than assuming every damage-looking effect scales from Attack Power or every timer scales from Attack Speed.
Account for summons and support entities
The official Dude Types index includes Echo Dude and Skeledude rows without ordinary roster Abilities. Quantum Dude summons an Echo Dude; Necrodude summons a Skeledude. These rows help define objects created by a roster Ability and should not be counted as separate Flyer choices.
When a summon is involved, identify who owns the trigger, who receives buffs, and whether Type- or Family-based effects include the summoned entity. Use the live referenced terms rather than guessing from the shared name. A summon appearing on the battlefield does not automatically gain every roster privilege.
Record support entities separately in a build note. This keeps the five Flyer slots distinct from additional bodies and prevents roster-count calculations from drifting away from the Store’s 42 advertised recruitable Types.
Turn an Ability into a team job
Summarize each planned Type in one causal sentence: “This Dude creates X event, which gives Y target Z payoff every N condition.” If the sentence cannot be completed from current text, open the Dudex before recruiting around it.
Then connect the five sentences. One Dude should create an event another can convert; survival should last through the damage ramp; movement should deliver the correct targets; and the economy should support the Relics required to make the chain reliable.
After a failed battle, identify which link did not occur. A missing trigger needs Stats or another enabler. A correct trigger with a weak payoff needs scaling. A strong payoff that arrived after a knockout needs timing or defense. This diagnosis preserves useful Types while changing the part that actually failed.