Blight: Survival Playtest Checklist

This playtest checklist is a tool-style page for Blight: Survival applicants and invitees. Work top to bottom the evening before a wave. Pair it with the narrative Playtest guide if you still need signup context.

Account block

• Steam account logged in and authenticated on the test PC
• Behaviour Playtest Squad profile completed for Blight: Survival
• Official Discord joined with announcement roles enabled
• Email access nearby for invite links
• Refuse any third-party “free key” sites

Hardware block

• Specs rechecked against System Requirements
• GPU drivers updated
• SSD free space well above 20 GB
• Headset verified
• Controller or keyboard binds conceptualized via Controls

Software block

• Overlay conflicts noted (disable if unstable)
• Recording software only if the wave allows it
• VPN off unless the studio instructs otherwise
• Discord overlay tested once

Knowledge block

• Skim Getting Started
• Skim Combat System
• Decide solo or co-op contract (Solo, Co-op
• Write a one-line mission tempo goal (Mission Survival

NDA and conduct block

• Read the wave rules completely
• No leaking if forbidden
• No harassment in voice lobbies
• No cheating tools — ever

During-session block

• Note patch/build string if shown
• Reproduce bugs twice when safe
• Screenshot error codes
• Tag whether issue is solo or co-op

Post-session block

• Submit official feedback form while memory is fresh
• Sort notes into combat / UI / performance / mission flow
• Rest before hopping rumor Discords
• Update your personal extract rules if the build taught you something new

Optional stretch goals

Film a private clip for the bug report if allowed. Compare Marshlands fog visibility notes with Marshlands. Restamp your Weapon Tier List opinions privately — do not present them as patch facts.

Checklist failure modes

Most failed sessions come from expired Steam guard codes, full disks, or unread NDA rules — not from lack of Zweihander skill. Logistics first, glory second.

Thirty-minute short form

Accounts linked? Drivers updated? Disk free? Headset tested? NDA read? Extract rules written? Feedback form bookmarked? If any box is unchecked near launch time, fix logistics before polishing Zweihander fantasies for Blight: Survival.

Practice loop for Playtest Checklist

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 Playtest Checklist, 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 Playtest Checklist 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 Playtest Checklist 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 Playtest Checklist, 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 Playtest Checklist 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.