The second Closed Alpha Playtest for SAW: Genesis is a four-day window with 24/7 servers, a fresh progression wipe, and a new playable Judge. The 3v1 horror game’s first alpha was about proving the core loop works. This one is about proving it holds up at scale, with stability, matchmaking, onboarding, and live issue monitoring all under the microscope.
Quick answer: New invitees get Steam keys on September 22. The servers open September 24 at 5 PM CEST (11 AM EDT / 8 AM PDT) and remain available continuously through September 27 at 4 AM CEST.
Release time: September 24, 5 PM CEST / 11 AM EDT / 8 AM PDT
Closed Alpha Playtest #2 dates and server hours
The test runs for roughly 96 hours, September 24 through September 27, and the servers stay online the whole time rather than opening in scheduled blocks.
| Time zone | Servers go live | Servers go offline |
|---|---|---|
| CEST | Sept 24, 5 PM | Sept 27, 4 AM |
| EDT | Sept 24, 11 AM | 10 PM |
| PDT | Sept 24, 8 AM | 7 PM |
If a critical bug shows up mid-test, matchmaking can be paused briefly to push a hotfix. Those pauses are announced in the closed Discord section reserved for playtesters, not through public channels.
Servers being offline right now is expected. They were switched off when the first alpha ended and come back on when the second test begins.
How to get access: returning CA1 players vs. new invites
There are two completely separate paths in, and mixing them up is where most of the confusion starts. Anyone who played the first Closed Alpha is already in. Everyone else needs an invitation email.
If you played Closed Alpha Playtest #1
You are automatically included and you do not need a new Steam key. The SAW: Genesis – Playtest product will be re-enabled in your Steam library closer to the start so you can preload, so an empty library right now is not a lost license. Set aside roughly 10GB of disk space for the download.
If this is your first playtest
You know it worked when the key redeems, the playtest product appears in your Steam library, and the client begins preloading. Preloading before September 24 also pulls in any updates released ahead of the test.
Only one account per person is allowed. Creating an alt account to improve your odds is not permitted.
Progression wipe: everyone starts from zero
Meta progression from the first alpha does not carry over. Every returning player begins the second test with a clean slate, which keeps matchmaking from pitting fully progressed veterans against the large group of first-timers coming in.
The progression rate itself has also been rebalanced and is now tuned around the roughly 96-hour length of the test, so the curve should fit the window rather than stretch past it. Designer-facing progression parameters were added behind the scenes, which lets the team retune values quickly during the test instead of shipping a full build change.
What’s new in the Playtest #2 build
| Addition | What it does |
|---|---|
| Watchmaker | New playable Judge, early version |
| Spectator Mode | Watch others after elimination |
| Outro sequences | All outros now trigger in-game |
| Proximity voice chat | Opt-in, hear players by location |
| Judge–Accused voice | Direct line between the two roles |
Proximity chat settings and muting
Proximity voice chat is opt-in, so it stays off until you enable it in the game settings, where you can also adjust microphone volume. To silence someone mid-match, press Esc, open the Tab menu, click the player’s nickname, and hit Mute. The direct Judge-to-Accused channel is the more interesting change, opening up bargaining, deduction, and roleplay between the two sides.
Interface and matchmaking changes
- Queue for both roles at the same time.
- Estimated and current queue wait times are displayed.
- A Report a bug button sits in the main menu.
- Result screen reveals information more gradually, with an option to skip animations.
- Result screen bugs fixed and match scoring is explained more clearly.
Stability and exploit fixes
- Crash frequency is lower, and critical gameplay blockers are less common.
- Guidance for Radeon driver compatibility issues, including which drivers to install.
- Safeguards against falling through the map.
- Syringe-spam abuse and several other exploits patched out.
Tutorial and onboarding rewrites
New players kept getting stuck on the same things, so the tutorial entry flow now makes it obvious that there are two separate tutorials rather than one. Missing prompts such as “Hold G to drop an item” were restored, and the explanations for pressure, itemization, and punctation were rewritten after player feedback flagged them as unclear.
NDA and streaming rules for CA2
The confidentiality terms carry over unchanged from the first alpha, and public recording or streaming of the build is off the table. If you already completed onboarding and signed the confidentiality statement, you do not sign again. Newly invited players must complete both before they get access. Creators are not given a separate set of rules, so read everything attached to the onboarding flow before you press record.
Waitlist status and how invites are selected
Signing up once is enough. If you registered for the playtester database already, re-applying does nothing, and being passed over for the first alpha does not remove you from the waitlist. The “Congrats, you’re on the waitlist” message means you are in the database, not that you have been selected.
Selection is driven by what the development team needs at that moment plus the details in your survey. PC specs matter, because the priority is inviting players whose hardware can run the current build smoothly enough to produce reliable feedback.
Feedback, controllers, language, and regions
- Bug reports and feedback go through the private Discord channels for onboarded playtesters.
- Gamepad support is active, with Xbox controllers recommended.
- The build is English-only.
- Servers cover EU and US regions.
The in-game Report a bug button is the fastest route for anything you hit mid-match, and the Discord channels are where hotfix pauses and build updates get announced during the four days. Preload early, keep the NDA in mind, and treat the wipe as the point rather than a setback.
