Decaying Winter traits

Selection budget

Treat three slots as a budget.

The current community traits index lists sixteen traits and reports that an Agent can equip up to three. The important consequence is not simply that choices exist; it is that every selected trait displaces another. A useful loadout therefore begins with a ranked set of needs rather than three individually attractive descriptions.

Start from the Agent’s perk role and the squad’s plan. If the Agent is expected to hold pressure, contribute from the backline, preserve supplies, or cover a support responsibility, write that responsibility first. Then identify the failure that most often prevents the role from working. A trait earns a slot when its current source-backed effect addresses that failure better than another available option.

Do not freeze exact bonuses from memory. Trait values are balance-sensitive, and the supplied research confirms the count and slot limit rather than every effect. The archive keeps the planning framework stable while leaving numerical claims to a current dedicated index.

Trait worksheet

Use a six-question comparison worksheet.

The worksheet converts a trait choice into evidence the squad can discuss. It deliberately avoids a generic “best traits” ranking because the same modifier can be valuable or wasteful depending on perk, equipment, supplies, positioning, and teammate coverage. Each row asks for an observable reason and a source check.

Complete the worksheet for the whole three-slot package, not one trait at a time. A pairing can fail through overlap even when every individual effect sounds useful. The final package should explain the Agent’s main job, its biggest risk, the constrained resource, the fallback, the squad benefit, and the moment when a balance or role change requires review.

Loadout binding

Bind traits to perk responsibility.

Perks and traits should be read in different layers. A perk establishes a larger role pattern or active system. Traits consume a limited set of modifier slots around that pattern. When a trait pairing merely repeats what the perk already handles, the squad should know why the redundancy is intentional. When the pairing covers a weakness, the handoff should name the weakness directly.

Use role language from the perks index only as a starting point. Basic, Frontline, Backline, and Support group entries for browsing; they do not replace the current text of a selected perk or trait. Compare the exact source descriptions before relying on an interaction, especially after updates.

• Write the perk responsibility in plain language.
• List the two most likely causes of role failure.
• Spend trait slots on the highest-priority gaps, then check overlap.
• Record a fallback that remains useful when the ideal setup collapses.

Equipment check

Check the equipment dependency.

A trait package can look complete and still fail because its weapon or supply assumptions are unsupported. Ranged weapons consume ammunition. Crafted weapons depend on blueprints and recovered resources. Medical, ration, infection-management, and deployable records answer different needs. Before finalizing traits, state what equipment the Agent expects and what happens if the scavenging phase does not provide it.

This step also improves squad distribution. If several Agents depend on the same scarce category, the conflict appears before the wave. The team can change a trait package, choose a different equipment plan, or assign one person to preserve the shared resource. The traits page becomes useful because it exposes those dependencies without copying volatile item or weapon statistics.