Current community data lists 17 playable perks grouped as Basic, Support, Frontline, and Backline, plus status-specific entries. The route inventory contains more dedicated guide names than the playable count, so this page keeps coverage and current classification separate.

Role filter

Use role groups to begin a squad conversation.

A role group is a navigation aid, not a complete judgment. Basic, Frontline, Backline, and Support describe the organization reported by the current community perks index. The labels help a squad identify overlap and missing responsibility before a run, but they do not prove that every perk in a group performs the same task or that one group must always be represented.

Start with the job the squad needs during the survival loop. Frontline responsibility concerns holding pressure and protecting space. Backline responsibility concerns contributing from safer positioning and managing resources that support that distance. Support responsibility concerns enabling the group, while Basic provides the index’s baseline grouping. These are planning interpretations, so an exact ability, drawback, charge rule, or stat value still belongs to the current perk page.

When two Agents want the same role, compare their equipment demands and selected traits before forcing variety. Duplicate roles can be intentional. The failure occurs when both players expect the other person to supply ammunition, preserve medical resources, watch the return window, or anchor the defense.

Decaying Winter official Roblox experience icon
The official experience icon anchors this loadout-reference page without inventing perk art, perk stats, or a guaranteed squad composition. Source: the coconut crew! via Roblox.

Observed guide surface

Read the guide-route inventory as coverage, not a playable count.

The current route inventory exposes twenty-one dedicated “Perk Guide” labels. The facts ledger separately records seventeen playable perks in the current index and warns that status-specific entries also exist. Those numbers should not be silently reconciled by deleting four names or declaring them retired. A route can represent historical, special, duplicated, or otherwise status-bound coverage.

The table preserves every observed guide label and attaches the same verification requirement to each row. A later update can bind the row to its current role group, playable status, ability text, pros, cons, and source date after checking the dedicated page. Until then, the table is a complete index of observed guide routes rather than an invented gameplay database.

21 records

Observed entryGuide routeCurrent-use boundary
ApostleApostle Perk GuideObserved dedicated guide route; verify current playable or status-specific classification
ArbiterArbiter Perk GuideObserved dedicated guide route; verify current playable or status-specific classification
ArtilleristArtillerist Perk GuideObserved dedicated guide route; verify current playable or status-specific classification
BarbarianBarbarian Perk GuideObserved dedicated guide route; verify current playable or status-specific classification
BerserkerBerserker Perk GuideObserved dedicated guide route; verify current playable or status-specific classification
BlitzerBlitzer Perk GuideObserved dedicated guide route; verify current playable or status-specific classification
CrosslinkCrosslink Perk GuideObserved dedicated guide route; verify current playable or status-specific classification
DamnedDamned Perk GuideObserved dedicated guide route; verify current playable or status-specific classification
DrifterDrifter Perk GuideObserved dedicated guide route; verify current playable or status-specific classification
ExecutionerExecutioner Perk GuideObserved dedicated guide route; verify current playable or status-specific classification
HivemindHivemind Perk GuideObserved dedicated guide route; verify current playable or status-specific classification
ImmolatorImmolator Perk GuideObserved dedicated guide route; verify current playable or status-specific classification
LazarusLazarus Perk GuideObserved dedicated guide route; verify current playable or status-specific classification
MindflayerMindflayer Perk GuideObserved dedicated guide route; verify current playable or status-specific classification
ProphetProphet Perk GuideObserved dedicated guide route; verify current playable or status-specific classification
RiskrunnerRiskrunner Perk GuideObserved dedicated guide route; verify current playable or status-specific classification
SovereignSovereign Perk GuideObserved dedicated guide route; verify current playable or status-specific classification
SurvivalistSurvivalist Perk GuideObserved dedicated guide route; verify current playable or status-specific classification
TickspiderTickspider Perk GuideObserved dedicated guide route; verify current playable or status-specific classification
VagabondVagabond Perk GuideObserved dedicated guide route; verify current playable or status-specific classification
ZealotZealot Perk GuideObserved dedicated guide route; verify current playable or status-specific classification

Comparison method

Compare responsibilities before mechanics.

A useful comparison begins with four questions. What part of the cycle does the perk change? What resource does it consume or preserve? What risk does it transfer to teammates? What must be true for the perk to deliver value? These questions remain useful when a numeric balance patch changes an exact value because they describe the decision structure rather than freezing a stale number.

Then connect the perk to the trait limit and equipment plan. An Agent can equip up to three traits according to the current traits index. A ranged plan also creates an ammunition requirement, while a melee plan changes exposure and fallback needs. The perks route should not duplicate every trait or weapon effect; it should expose those dependencies and provide direct links to the databases that own them.

  • Choose a role responsibility the squad can observe during the run.
  • Identify the supply, ammunition, position, or timing dependency created by the perk.
  • Check whether selected traits reinforce the same job or leave a critical gap.
  • Revisit the dedicated source after balance changes before trusting exact mechanics.

Squad handoff

Turn a perk choice into a short handoff.

Before scavenging begins, describe a perk choice in one sentence the team can use: role, expected position, important resource, and fallback. That sentence is more actionable than a tier label because it tells other Agents what they can rely on. It also exposes conflicts early, such as two ranged plans competing for ammunition or several players assuming someone else will carry support supplies.

After the run, update only the part that failed. If the role was right but the equipment demand was wrong, move to the weapons or items route. If the perk worked but the Agent could not sustain the intended position, review the trait pairing. If the squad understood the build but timing broke down, return to the walkthrough. This keeps perk research connected to play instead of becoming an isolated ranking exercise.

Frequently asked questions

Why are twenty-one guide names shown when the index lists seventeen playable perks?

The observed route inventory includes dedicated guide pages beyond the current playable count, and the research notes that status-specific entries exist. The archive preserves the full route surface instead of guessing which four labels should be removed. Current classification must be checked against the perks index and each dedicated page.

Does a role group determine the best squad composition?

No. Basic, Frontline, Backline, and Support are useful organizing labels, but squad value also depends on traits, equipment, ammunition, supplies, positioning, and the live objective. Use the groups to expose responsibility and overlap, then verify current perk mechanics before making a final loadout decision.

Sources and verification