Survivor Build Planning Guide

The goal of survivor build planning is not to stack four “good” perks. It is to build a repeatable plan for real matches: unstable teammates, uneven hook cycles, and killers that force awkward pathing.

Use the builder as a testing tool, not a final answer machine. Define your biggest loss pattern first, then build around fixing that problem before adding style picks.

Slot Planning Framework

Slot 1 (Win condition): pick the core objective of the build (anti-tunnel, gen pace, chase uptime, or reset stability).
Slot 2 (Information): add one read layer so route decisions are not blind guesses.
Slot 3 (Safety): reserve one slot for collapse states like slug pressure or bad hook timing.
Slot 4 (Flex): adjust this slot by queue type, map pressure, and current patch trends.

Filter Strategy That Actually Works

Start broad with one primary tag and one supporting tag.
Do not stack six filters at once unless you are solving a very specific comp setup.
If your results look too narrow, remove low-impact style tags before core tags.
Always verify that your final four perks each have a clear job in match flow.

Solo Queue vs SWF Rules

Solo queue: prioritize independent value and safe fallback states.
SWF: you can run higher-synergy chains, but keep at least one self-contained slot.
If teammates are inconsistent, revert to your solo baseline instead of forcing coordinated tech.
Avoid full altruism stacks unless your objective tempo is still protected.

Patch-Proof Testing Loop

Save baseline build A before making any changes.
Create build B with one slot swapped, not three.
Test both builds in similar queue conditions.
Keep the version with cleaner hook recovery, chase continuity, and gen pace.

Common Builder Mistakes

Over-filtering into niche perks with low trigger uptime.
Running four high-synergy perks that fail when one teammate misses timing.
Copying meta screenshots without matching your actual queue type.
Ignoring map and killer matchup context after locking perks.

FAQ

How many filters should I apply at once in the survivor builder?

Usually two to four. Enough to define a plan, not so many that you force niche low-uptime perks.

What should I lock first in a survivor loadout?

Lock your win-condition slot first, then add one info slot, one safety slot, and one flex slot.

Should solo queue and SWF use the same builds?

Not usually. Solo queue needs self-contained value while SWF can support more coordinated perk chains.

How often should I refresh survivor loadouts?

After major patches and whenever your most common loss pattern changes.

How can I test if a new perk swap is actually better?

Change one slot at a time, run a short sample, then compare hook-state recovery, chase uptime, and generator pace.