A How Many Dudes? build begins shaping its Relic offers as soon as Flyers are posted. The official developer guide gives the pool rule: each roster Dude Type adds seven dedicated Relics, and that Dude’s Family adds eight shared Relics. Each individual Relic enters once. Recruiting another Type from an already represented Family adds its dedicated seven but not a duplicate Family set.
This makes roster construction a probability decision before any reroll occurs. The goal is not always the smallest pool. It is a pool with enough hits for the team’s jobs and few enough misses for the available economy.
Build a pool ledger before naming the comp
Write one row for each planned Flyer with Type, Family, essential dedicated Relic, useful dedicated backups, and useful Family effects. Mark whether its Family is already represented. This shows the exact moment a new shared set enters.
For five Types in one Family, the guide calculates 35 dedicated Relics plus eight Family Relics. For five Types across five Families, it calculates the same 35 dedicated Relics plus 40 Family Relics. The second roster sees more categories of shared effects, while the first gives dedicated pieces a larger share.
These counts describe entries, not guaranteed offer percentages. Shop and Stash presentation can have additional live rules, and the current source does not promise that every roll is a simple uniform sample. Use the ledger to compare relative dilution, then verify actual interfaces in the released client.
Choose the minimum viable pool
A minimum viable pool contains the pieces required for the team to function before optional Families are added. Start with the Type that supplies the irreplaceable heal, damage conversion, protection, movement, or economy interaction. Add only partners whose sets contain several real hits.
The developer guide uses Vampire Dude’s Blood Bag as a reason to pre-post a partial Ensemble team: open the important Type early and leave other positions unresolved while searching a smaller pool. The lesson is not that Vampire is mandatory. Any build with a single hard dependency benefits from delaying unrelated sets.
The core still needs a fallback. If it loses every round until the one defining Relic appears, the pool may be mathematically focused and strategically unviable. Add baseline survival or damage that works from Abilities and broadly useful effects.
Decide when breadth is an advantage
Broad Families are correct when the added shared sets contain many solutions to the team’s live problems. A roster that can use movement, Temporary Health, control, healing and several damage triggers may prefer diverse offers over one narrow hunt.
Count outcomes, not Families. If a new Family contributes eight effects but only one can trigger meaningfully, it creates seven likely misses. If six effects strengthen different members, the same expansion makes future offers safer.
Cash changes this judgment. A strong Business Dude sequence and disciplined spending allow more purchases and rerolls, making a wide pool easier to sample. A cash-starved run should demand higher hit density from every added set.
Use mode rules as pool controls
The official guide says Daily Dude and Rematch begin with all five Flyers pre-posted. Their complete roster pool is available immediately, so the task is evaluating and funding the fixed pool rather than controlling which Family arrives first.
Ensemble lets the player choose how many Flyers to pre-post. Empty slots receive random Flyer selection during the run according to the release announcement. A partial Ensemble setup can expose a compact engine first and allow later recruits to solve whatever the early rounds reveal.
Classic develops through its normal Flyer flow. There, every recruit should be evaluated twice: once as a battlefield Type and once as a new set of future offers. Do not post an optional Flyer just because the immediate Ability looks good if the resulting pool makes the required core much harder to complete.
Sequence purchases around pool expansion
Before adding a new Family, decide whether to acquire the important pieces already available. If the current pool holds a required dedicated Relic, spending now may be more efficient than expanding and trying to find it later among another eight shared entries plus a new dedicated set.
Preserve purchase cash as well as reroll capacity. A successful search that leaves the target unaffordable does not complete the engine. Conversely, buying every acceptable early effect can delay the Business Dude principal that would finance a much broader late pool.
After the defining pieces are secured, expansion becomes less dangerous. New Families can patch boss mechanics, improve target access, or add a second damage plan without threatening the foundation. Treat this as a phase change in the run rather than using one pool policy forever.
Read an offer through activation density
Activation density asks how many current Dudes can trigger or benefit from an effect and how often. A powerful Family Relic with one rare trigger may be less useful than a modest dedicated effect that fires continuously. Use exact Dudex language for the trigger, target, duration, stack cap and cooldown.
Separate owner-specific and team-wide value. A dedicated Relic may transform one Type into the primary engine. A Family Relic may support several Types but divide its value across them. The correct choice depends on whether the team lacks a carry, a bridge between jobs, or a global survival answer.
When two offers look close, choose the one that repairs the observed loss. Fatal burst, slow attrition, distant targets and insufficient damage require different effects even if both candidates are considered strong in general.
Compare the planned and actual pool after a run
Save the five posted Types, represented Families, defining acquired Relics, and several offers you declined. Note which misses came from a set you deliberately introduced. This reveals whether dilution was real or whether poor trigger matching made usable effects look weak.
For the next test, change one Flyer or pre-post choice. Removing a Family, delaying one Type, or expanding earlier each tests a different hypothesis. Do not replace all five and then attribute the result to pool control.
The public Dudex is the current catalog, while the developer guide supplies the seven-plus-eight rule. Recheck both after a balance update; do not carry Demo-era pool counts into Full Release without current confirmation.