Blight: Survival Armor & Customization

Armor in Blight: Survival is both protection and identity. Developers confirmed you can customize your character visually and mechanically, wear armor stripped from enemies, and eventually recolor pieces and change crests. This page gathers those promises into a practical customization mindset.

European visual influences

The setting is alt-history medieval with artistic liberties. Expect a wide range of European armor silhouettes rather than strict museum replicas. That variety supports the fantasy of scavenging across a no man’s land filled with fallen soldiers from multiple traditions.

Looting enemy armor

Being able to wear enemy gear turns every skirmish into a potential fashion and stats upgrade. In extraction-lite loops, that also means deciding whether a rare chest piece is worth the weight on a greedy push — tie decisions to Mission Survival.

Recolor and crests

Planned recolors and crest swaps help co-op teams look unified without identical stats. Use that later for clan identity; see lore notes on joining clans in official FAQ context and our Writhens page.

Mobility versus protection

Until numbers exist, assume heavier sets buy survivability and cost stamina or sprint efficiency. Dagger players may prefer mid sets; Zweihander users might lean heavier if recovery is already slow. Test in playtests and report feel — Playtest.

Pairing with talents and weapons

Armor should cover the weakness your weapon creates. Long recovery heavies need either stronger guard tools (Parry & Shields) or lighter armor that lets you reposition. Document your favorite trio on Talents.

Horror readability

Dark maps demand silhouettes you can parse. Avoid stacking every blackened piece if the UI lacks strong ally outlines in early builds — call it out in feedback.

Hub wardrobe routine

Between missions, rearrange sets deliberately. Do not enter a Marshlands-style wet biome (see Marshlands) with a kit you hate the sprint feel of.

Cosmetics ethics in co-op

If a legendary-looking drop is mostly cosmetic, rotate it. Squads that share spoils stay together longer (Co-op).

Fashion that still reads in fog

Looking like a plague knight is half the fantasy. Confirm your silhouette still parses in Marshlands-like fog and that weight matches weapon recovery. If ally names are hard to see in a test build, brighter crests become teamwork tools—file that feedback for Blight: Survival.

Practice loop for Armor

Turn this page into a weekly habit: pick one claim from the sections above, test it against the latest official Blight: Survival trailer or FAQ wording, and write a single sentence you would tell a squadmate. Prefer decisions you can rehearse—spacing, extract timing, loadout comfort—over memorizing unverified numbers.

What to ignore for now

Skip leaked calendars, fake key sellers, and influencer “day-one meta” sheets. For Armor, the useful prep is confirmed systems, honest TBA labels, and a short personal checklist you can execute in a playtest lobby without opening ten rumor tabs.

After the next official update

When Behaviour or Haenir publish new footage, return here and mark which Armor assumptions still hold. Update your notes with the trailer date, keep Steam and Discord as primary sources, and revise only the paragraphs that new evidence actually changes.

Squad briefing template

Share three bullets max: what Armor changes about your first mission, which linked wiki page teammates should read next, and one risk you refuse to take until you have hands-on time. Short briefings beat essay dumps when coordinating Blight: Survival sessions.

Feedback-ready questions

If you enter a playtest after reading about Armor, prepare two concrete feedback prompts—one about feel, one about clarity. Vague praise helps less than “telegraph X was unreadable in fog” or “extract UI hid the timer behind inventory.”

When you revisit Armor after a new Blight: Survival reveal (pass 1), rewrite one personal rule, one loadout preference, and one link you will send friends. Dated notes beat vague confidence while systems are still iterating.