The mode reference begins after this fixed ad boundary.
The Daily Dude creates a named repeat-run context
The Daily Dude is an official game mode. The supplied sources confirm the name but do not provide a complete ruleset, scoring table, or reset schedule in the structured project evidence. This page therefore treats it as a distinct run context and avoids inventing daily modifiers. The useful rule is to record that the run belongs to Daily Dude before comparing it with another composition or Tier attempt.
When evaluating a Daily Dude run, use the same stable system questions: what five Dudes are available, which Families are represented, how the starting Relic pool is shaped, and what pressure ends the run. Keep the mode label attached to the result because a run created under a named mode should not be used as proof that the same opening or outcome applies everywhere.
Use “The Daily Dude creates a named repeat-run context” as a run checkpoint rather than a universal ranking. Before applying “The Daily Dude creates a named repeat-run context,” note the current five-Dude roster, the Families already represented, and the immediate pressure shown by the encounter. A short “The Daily Dude creates a named repeat-run context” record makes the result easier to compare after battle while keeping unsupported exact values, hidden formulas, and one-size-fits-all builds out of the decision.
Ensemble Mode is a separate official team context
Ensemble Mode is also named in the official release information. Its presence confirms that team-building decisions can be evaluated under more than one mode context. The current evidence does not supply enough exact rules to publish an invented comparison of rewards, restrictions, or difficulty. Instead, the page defines the questions that remain stable across modes and the data that must stay mode-specific.
For an Ensemble run, record the available roster, the five-Dude selection, distinct Families, and the resulting Relic-pool breadth. Then compare recovery, investment, defense, and boss preparation with the same checkpoints used elsewhere. If a result differs from Daily Dude or Rematch, attribute it to the known mode context until an official rule explains the exact cause.
Use “Ensemble Mode is a separate official team context” as a run checkpoint rather than a universal ranking. Before applying “Ensemble Mode is a separate official team context,” note the current five-Dude roster, the Families already represented, and the immediate pressure shown by the encounter. A short “Ensemble Mode is a separate official team context” record makes the result easier to compare after battle while keeping unsupported exact values, hidden formulas, and one-size-fits-all builds out of the decision.
Rematch Mode returns the player to another run decision
Rematch Mode is described in the official developer guide. The name indicates a repeat encounter context, but the supplied structured facts do not establish every condition, reward, or carry-over rule. This reference therefore does not invent them. It keeps Rematch separate from Daily Dude and Ensemble so future verified details can be added to the correct route and existing run notes remain unambiguous.
Use Rematch analysis to test whether the earlier failure came from the five-Dude composition, the Relic pool, defensive preparation, Mobility, or a boss-earned Trinket assignment. Change one decision category at a time. A rematch is most informative when the player can identify what changed between attempts rather than replacing the whole plan and losing the comparison.
Use “Rematch Mode returns the player to another run decision” as a run checkpoint rather than a universal ranking. Before applying “Rematch Mode returns the player to another run decision,” note the current five-Dude roster, the Families already represented, and the immediate pressure shown by the encounter. A short “Rematch Mode returns the player to another run decision” record makes the result easier to compare after battle while keeping unsupported exact values, hidden formulas, and one-size-fits-all builds out of the decision.
- Record the mode and starting state.
- Name the failure pressure from the previous attempt.
- Change one roster or system variable.
- Compare the new result within the same mode context.
Pre-Posted Flyers affect the starting Relic pool
The official developer guide states that Pre-Posted Flyers affect the starting Relic pool. This is a mode and opening-state rule with direct team-building consequences. Before judging an early Relic choice, check which Flyers were already posted and what Dude Types or Families they represent. The pool may have been shaped before the first normal recruitment decision.
That fact also explains why two runs can begin with different option sets even when the player intends a similar strategy. Do not infer a drop-rate change or a hidden balance adjustment from the difference. First compare the Pre-Posted Flyers and represented Families. Then apply the standard pool rule: seven Dude Relics per selected type and eight Family Relics per represented Family, with each Relic added once.
Use “Pre-Posted Flyers affect the starting Relic pool” as a run checkpoint rather than a universal ranking. Before applying “Pre-Posted Flyers affect the starting Relic pool,” note the current five-Dude roster, the Families already represented, and the immediate pressure shown by the encounter. A short “Pre-Posted Flyers affect the starting Relic pool” record makes the result easier to compare after battle while keeping unsupported exact values, hidden formulas, and one-size-fits-all builds out of the decision.
Keep confirmed mode names separate from unverified details
The most reliable comparison currently available is structural. Daily Dude, Ensemble, and Rematch are distinct named contexts. Pre-Posted Flyers can affect the starting Relic pool. The five-Dude team, differing affinities, represented Families, Relics, Trinkets, Tiers, and walkthrough checkpoints remain the system vocabulary used to analyze each run.
As new first-party rules are published, they should be added under the correct mode rather than generalized across all three. Until then, record mode, Tier, Star target, starting Flyers, roster, and failure pressure. That produces useful notes without claiming exact schedules, rewards, or restrictions that are not in the current evidence.
Use “Keep confirmed mode names separate from unverified details” as a run checkpoint rather than a universal ranking. Before applying “Keep confirmed mode names separate from unverified details,” note the current five-Dude roster, the Families already represented, and the immediate pressure shown by the encounter. A short “Keep confirmed mode names separate from unverified details” record makes the result easier to compare after battle while keeping unsupported exact values, hidden formulas, and one-size-fits-all builds out of the decision.
| Mode or rule | Confirmed fact | Use in run notes |
|---|---|---|
| The Daily Dude | Official named mode | Label the daily run context |
| Ensemble Mode | Official named mode | Keep team results mode-specific |
| Rematch Mode | Named in the developer guide | Compare a repeated attempt |
| Pre-Posted Flyers | Affect the starting Relic pool | Record the opening pool state |
Game mode questions
Which game modes are confirmed by name?
FAQ: The official sources name The Daily Dude and Ensemble Mode, and the developer guide describes Rematch Mode. The supplied structured evidence does not contain every rule, schedule, or reward for those modes, so the page does not invent a full comparison chart.
What do Pre-Posted Flyers change?
FAQ: Pre-Posted Flyers affect the starting Relic pool. Check the starting Flyers and represented Families before comparing early Relic choices between runs, because the pool may differ before normal recruitment decisions begin. Use the “what do pre-posted flyers change” boundary when reviewing the next run, and keep any stronger conclusion separate until an official rule or clean first-party record supports it.
Can results from one mode be treated as universal?
FAQ: No. Keep the mode, Tier, starting Flyers, roster, and failure pressure attached to the result. The stable system rules can be compared across runs, but a mode-specific starting condition should not be generalized without an official rule. Use the “can results from one mode be treated as universal” boundary when reviewing the next run, and keep any stronger conclusion separate until an official rule or clean first-party record supports it.