Join the list
Submit the playtest access form. A request is not an automatic invitation.
Prototype playtest guide
This guide covers the private prototype as it exists now. Builds can change quickly, progress may be reset, and an invited account is required before protected downloads appear.
Submit the playtest access form. A request is not an automatic invitation.
Invited testers receive a signup key. Use it once in the tester launcher to create an account.
Sign in, wait for build availability, then download the protected Windows build or desktop launcher.
Current prototype
These controls describe the current prototype and may change between cohorts. Report any action that is uncomfortable, difficult to discover or impossible with your input setup.
Useful feedback
Record the location, what you expected, what actually happened and whether another player was involved.
Separate a harsh but understandable consequence from a rule that was invisible or impossible to respond to.
The most valuable signal is whether you voluntarily start another session after experiencing death and descent.
Common questions
Account registration is invitation-only and requires a signup key. Joining the list does not create an account or guarantee an invitation.
Your account can be valid while a build is still being packaged or temporarily unavailable. The launcher will show availability after login.
Sign in again to refresh the session, confirm the build still shows as available, and retry. Include the launcher status message in any test report.
Do not assume it will. Prototype saves, accounts and character progress may be reset when systems or data formats change.
No final death rule is locked. The current experiment tests one-Layer descent, an unmoored danger window, partial loss and a catastrophic repeat-death state.
No. The first validation build focuses on a compact surface route, an elevated objective and the first underworld descent.
No. The shardless world is the architecture and design direction. Concurrency will be increased only after smaller external tests are stable.
Include the build version, time, location, action, expected result, actual result, reproduction steps and any visible error. Add hardware details for performance issues.
Next step