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.

Night-before additions for 2026 waves

Confirm NDA rules, disk space for UE5 builds, Steam Guard readiness, and a written extract contract from Extraction Loop. Skim July 2026 Update so feedback uses current vocabulary (stronghold, interiors, Zweihänder).

Closing note

If the checklist feels too serious, good. Wasted waves from preventable setup errors help nobody—least of all the developers reading your feedback.

After-action mini checklist

Upload crash dumps if requested. Write two bugs and one delight. Thank the team without demanding a ship date. Then rest—fatigue creates useless bug reports.

Hardware spare kit

Keep a spare USB headset, a phone hotspot plan, and a second Steam Guard device nearby. Playtest windows are finite; hardware comedy should not spend them. Note failures for Behaviour only when they are actually build bugs.

Final mindset

You are a guest in a unfinished build. Curiosity plus restraint produces feedback developers can use. Ego plus clip farming produces noise. Choose curiosity for Blight: Survival waves.

Wave-morning stretch

Stand, water, five minutes of any melee warm-up, then boot. Physical readiness sounds silly until a missed parry costs a timed session. Treat Blight: Survival invites like short esports blocks, not casual launches.

Sleep on time. Tired testers file useless bugs.

Charge controllers before the wave begins.

Keep a paper backup of your Discord username in case overlays fail mid-wave.

Confirm your GPU control panel is not forcing an exotic overlay.