Expedition Into Darkness Playtest Guide

Playtests are how most players will touch Expedition Into Darkness before the planned Q4 2026 Steam release. Builds are temporary, systems are unfinished, and your job is twofold: enjoy the ruins and send useful feedback. This guide covers signup, PC readiness, squad prep, and what to watch for while the game is still upcoming—not a finished retail ship. Cross-link heavily with System Requirements, Game Overview, Tools, Release Timeline, and Updates.

Mindset before you install

Healthy expectation	Unhealthy expectation
Jank, missing polish, changing combat feel	Day-one balance and full content
Short public playtest windows that open and close	Permanent always-online service
Feedback that shapes the Q4 2026 target	Demanding refund-tier completeness
Learning extract discipline early	Speedrunning a finished meta

Official channels (Steam app 3126410, expedition-the-game.com, and Antediluvian Interactive updates) beat random screenshot rumors. When community clips mention new maps or skeleton packs, treat them as playtest observations and file themes under Patch History rather than inventing patch IDs.

Signup: Steam, Discord, and closed windows

Access usually starts with signup on Steam (wishlist/follow the store page and use any Playtest or request buttons the studio enables) plus Discord announcements when the studio posts invite waves. Pair both: Steam for depot access, Discord for timing and rules.

June 15 – July 7 2026 public playtest window: That wave is closed after the end date. Signup for that window is over. Do not expect the June–July build to stay installed forever. Watch Steam and Discord for the next signup waves instead of assuming permanent access. Dated context lives on the Release Timeline.

Earlier public milestones (open alpha Mar–Apr 2025; Dec 11 – Jan 5 public playtest window) follow the same pattern: temporary windows, then wait for the next signup.

Access checklist

1. Wishlist and follow the Steam page so notifications fire; complete signup when a playtest request opens.
2. Join official Discord / mailing lists the studio points to for closed or limited waves.
3. Confirm whether the window is demo, NDA alpha, or open public playtest—rules differ.
4. Note the end date; plan two solid sessions, not one rushed hour. Remember June 2026 closed after July 7.
5. Download early in the window to avoid mirror congestion.
6. Verify friends’ access before you theorycraft a five-stack.

If you lack a key or missed a closed window, do not pirate “leaks.” Wait for the next signup wave and keep practicing planning habits on this wiki.

PC and setup checklist

Run the hardware table on System Requirements first, then:

Step	Action	Why
1	Update GPU drivers	Cuts odd crashes in alpha
2	Free >8 GB + patch headroom	Mid-weekend depots happen
3	Test mic / Discord	Co-op without voice is misery
4	Disable unstable overlays	Easier bug isolation
5	Keep wiki tabs ready	Extraction Checklist mid-run
6	Create a feedback note doc	Timestamp issues while fresh
7	Confirm keyboard/mouse vs controller	Early builds often lacked full pad support

Squad readiness (night before)

Use the Party Planner to assign seats and the Loadout Planner to lock kits. Agree on a teaching vs. deep-push objective. New players should read Getting Started and skim Guides so you are not explaining permadeath in the first dark hallway.

Suggested first playtest night agenda:

1. 15 min — patch, settings, voice check.
2. 10 min — role + extract rule callouts.
3. 1 short scout run — learn exits, die cheaply if needed.
4. 1–2 serious runs — enforce checklist discipline.
5. 15 min — shared feedback notes.

What to evaluate in-build

Focus on verbs the design cares about:

• Extract pressure: Did bag weight and fear of loss feel fair?
• Combat readability: Attacks, timed blocks/parries, stamina clarity.
• Navigation: Could you learn exits without a wiki spoon-feed?
• Co-op agency: Did five players have distinct jobs or trip over each other?
• Progression: Did camp upgrades make the next run meaningfully better?
• Performance: Hitch locations, load stutters, disconnects.

Map-specific notes belong beside Map (including Chapel Ruins) once you recognize repeating hazard patterns. Threat notes belong on Enemies. Build feelings belong beside Builds as placeholders—not as gospel tiers.

Feedback that developers can use

Bad feedback: “Game bad.” Good feedback: “On 2026-xx-xx build, timed block window felt shorter than last test; skeleton pack in catacomb wing X wiped us when fog + trap overlapped; log attached.”

Include:

• Approximate build date / playtest name if shown in client
• Party size
• Repro steps
• Expected vs. actual
• Specs (link your row from the requirements checklist)
• Whether it blocked extract or was cosmetic

Track studio-facing milestones at a high level on the Release Timeline so you remember which window taught you what.

Etiquette inside temporary builds

• Do not harass playtest strangers—temporary lobbies are not ranked ladders.
• Spoiler carefully if NDA applies; when unsure, keep details in private feedback.
• Do not claim the full game has shipped in public posts; say public playtest window / upcoming.
• Record deaths for learning, not for dunking on unfinished animation.
• Leave the build when the window ends; schedule a reminder for the next Steam/Discord signup wave.

After the window closes

1. Stash personal notes: what almost worked.
2. Update your checklist lines that failed.
3. Skim Updates and add observed themes—not fake version numbers.
4. Return to Game Overview if friends ask “what is this game?” mid-hype cycle.
5. Keep practicing planning muscle with Tools even between tests.
6. Watch Steam + Discord for the next signup—especially after closed waves like June 15 – July 7 2026.

Common playtest failure patterns

Pattern	Fix
Treating a public playtest window like a live service grind	Set learning goals, not infinite farm quotas
Missing signup because you only watched trailers	Wishlist Steam + join Discord pings
Assuming June 2026 access never ended	That public playtest window closed after July 7
Five DPS clones	Re-seat via Party Planner
Ignoring hardware until crash	Requirements checklist night-before
No extract rule	Hard timer or bag-value cap
Feedback written three days later	Notes during the session

Where this sits on the road to launch

Periodic demos and public playtest windows exist to pressure-test the extraction loop before Q4 2026. Your best contribution is structured play: clear roles, clear kits, clear abort rules, clear bug reports. When the full release eventually arrives, players who already internalized camp-vs-carried risk will climb faster than players who only watched trailers.

Official trailer context remains on the Game Overview. Specs stay on System Requirements. Dated milestones stay on the Release Timeline. Operational sheets stay under Tools. Change diaries stay under Updates. Use all of them so every playtest hour compounds.