The Trinket reference begins after this fixed ad boundary.
Trinkets enter the plan through Act bosses
Act bosses reward Trinkets. That acquisition rule distinguishes Trinkets from the Relic pool assembled by Dude Types and Families. A Trinket is not simply another Relic choice drawn from the same pre-run structure; it arrives as a boss-earned modifier after the team has already survived the Act. The run must therefore prepare for the boss before it can plan around the reward.
The boss connection makes the walkthrough and Tiers pages natural prerequisites. Early defense protects against one-shots, Mobility helps pursue moving bosses, and the Tier 1 G.O.A.T. at round 105 is the first named milestone in the supplied guide. This page does not infer which Trinket drops from a specific boss or publish an unsupported reward table, because those mappings are not present in the structured first-party evidence.
Use “Trinkets enter the plan through Act bosses” as a run checkpoint rather than a universal ranking. Before applying “Trinkets enter the plan through Act bosses,” note the current five-Dude roster, the Families already represented, and the immediate pressure shown by the encounter. A short “Trinkets enter the plan through Act bosses” 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.
A Trinket is assigned to a Dude Type
The official facts state that a Trinket is assigned to a Dude Type. That creates a targeted team decision. When a reward appears, identify which Dude Type receives the modifier and what that Dude contributes to the five-Dude plan. The useful question is not whether the reward is generically powerful; it is whether the assignment strengthens the role the current run needs from that Dude.
The supplied evidence does not provide a complete Trinket catalog, exact values, or every assignment rule. The page therefore uses a decision framework rather than invented item rows. Check the recipient, the current boss or mode pressure, the team’s stat affinities, and the represented Families that already shape the Relic pool. A Trinket can amplify a strategy, but it does not erase the rest of the roster structure.
- Identify the Dude Type receiving the Trinket.
- Connect the modifier to the current team need.
- Recheck the five-Dude composition after the assignment.
Use Trinkets to amplify an existing team direction
Trinkets are described as amplifying team strategies. “Amplify” is important: the reward should be read in the context of the composition that earned it. A team already built to survive large bursts may value a modifier differently from a team struggling to keep contact with a moving target. An investment-focused run may evaluate timing and protection before pursuing another source of output.
This does not justify assigning fixed combat roles to every Family or ranking unlisted Trinkets. The confirmed structure supports a narrower process. Define the team’s current direction, inspect the Dude Type receiving the reward, and decide whether the modifier improves the weakest checkpoint or deepens the strongest established synergy. If the reward pushes the roster toward a different plan, revisit Team Building and Relics together.
Use “Use Trinkets to amplify an existing team direction” as a run checkpoint rather than a universal ranking. Before applying “Use Trinkets to amplify an existing team direction,” note the current five-Dude roster, the Families already represented, and the immediate pressure shown by the encounter. A short “Use Trinkets to amplify an existing team direction” 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.
Know when to open Relics, Trinkets, or Team Building
Open Relics when the question concerns the pool created by seven Dude Relics per selected type and eight Family Relics per represented Family. Open Trinkets when the question concerns an Act boss reward assigned to a Dude Type. Open Team Building when the question starts with the five slots, differing stat affinities, and more than 850,000 reported compositions.
The three pages deliberately overlap at decision boundaries. A new Dude changes the Relic pool. A boss reward changes one Dude’s contribution. A mode or Tier changes the pressure the whole team faces. Following the correct system boundary prevents an acquisition rule from being mistaken for a roster rule and keeps the wiki useful even while a complete first-party item catalog is not available.
| Question | Open | Reason |
|---|---|---|
| What can enter the choice pool? | Relics | Dude Type and Family contributions |
| Who receives the boss reward? | Trinkets | Assigned to a Dude Type |
| How should five slots work together? | Team Building | Composition, affinities, and Family breadth |
Trinket questions
Where do Trinkets come from?
FAQ: The official release information states that Act bosses reward Trinkets. The supplied evidence does not provide a complete boss-to-Trinket drop table, so the page keeps the acquisition rule and the assignment decision without inventing specific rewards. Use the “where do trinkets come from” boundary when reviewing the next run, and keep any stronger conclusion separate until an official rule or clean first-party record supports it.
What receives a Trinket?
FAQ: A Trinket is assigned to a Dude Type. Evaluate the modifier in relation to that Dude’s place in the five-Dude composition and the immediate run pressure, rather than treating it as a detached item with one universal value. Use the “what receives a trinket” boundary when reviewing the next run, and keep any stronger conclusion separate until an official rule or clean first-party record supports it.
Are Trinkets part of the Relic pool?
FAQ: The confirmed rules describe them differently. Relics are shaped by selected Dude Types and represented Families, while Trinkets are earned from Act bosses and assigned to a Dude Type. The systems interact through the team but should not be merged into one pool.