Testing guidelines.

01

Before every session

1. Install the latest assigned Steam build and confirm its version.
2. Update Windows, graphics drivers, Steam, and Steam Deck software where applicable.
3. Read the current known-issues list and the notes for the active build.
4. Confirm whether you are testing on Windows PC, Steam Deck Gaming Mode, or Steam Deck Desktop Mode.
5. Keep notes on your class, location, quest, settings, and actions while testing.

02

Write reports the team can reproduce

• Check the current build and known-issues page before starting.
• Submit one bug per report so each issue can be tracked independently.
• Attempt to reproduce the issue three times when it is safe to do so.
• Record exact steps, build version, location, character, input method, hardware, expected result, and actual result.
• Include the Unreal Crash Reporter message, log, or save file when a crash or progression failure makes it relevant.
• Choose the closest severity: Critical Blocker, Major, Minor, or Cosmetic.

03

Screenshots and recordings

Screenshots and short recordings are encouraged as private bug evidence, but they are not required. Written reproduction steps still matter.

• Capture the lead-up and the result, not only the final frozen frame.
• Keep clips short and focused when possible.
• Pair media with written steps, build information, and context.
• Remove passwords and unrelated personal information before uploading.
• Share larger files through an approved private link when needed.

04

Protect closed builds

Closed-build gameplay, screenshots, recordings, files, and discussion must stay inside approved private studio channels. Do not stream, post, forward, or discuss private testing material publicly without written authorization from Cryptid Forge Studios.

Discord rules communicate studio expectations, but access to a legally confidential build may also require a separate written NDA or testing agreement.

05

Be constructive and stay active

Honest criticism is welcome. Explain what happened, why it affected the experience, and what you expected. Avoid personal attacks or vague reports such as “it is broken.” If you cannot participate in a scheduled wave, tell the team so the testing roster stays accurate.