How to Submit an Effective Report
Please include the following details to help our engineering team reproduce and resolve issues quickly:
- Summary: Describe the problem in one sentence.
- Steps to Reproduce: List the exact actions leading up to the bug.
- Expected Result: Explain what should have happened.
- Actual Result: Explain what actually occurred, including error codes or screenshots.
- Environment Details: Provide browser version, operating system, and network type.
- Match Information: Add lobby code, map, and timestamp for multiplayer incidents.
Bug Categories
Gameplay Logic
Tasks not completing, sabotage timers stuck, impostor powers failing to trigger, or roles behaving inconsistently.
Performance
Frame drops, crashes, sound distortion, controller latency, or excessive bandwidth spikes during matches.
Visual & UI
Avatar clipping, incorrect localization strings, inaccessible buttons, or layout issues on mobile.
Security & Fair Play
Exploits, suspicious third-party tools, or griefing tactics that bypass moderation systems.
Submission Channels
- Primary Form: Use the structured questionnaire below to submit your report directly to our QA queue.
- Email: Send attachments or logs to qa@sussyswapsimulator.org.
- Emergency Security Issues: Use security@sussyswapsimulator.org for vulnerabilities affecting user data.
We acknowledge every report automatically; high-priority issues receive a personal response within 24 hours.
Evidence Collection Tips
High-quality evidence accelerates validation. Consider the following when filing:
- Record 30 seconds of footage before and after the bug occurs.
- Capture the browser console log (F12) for runtime errors.
- Note the game build number located in the lower-right corner of the lobby screen.
- Include teammate usernames when the bug is related to player interactions.
Follow-Up Process
Once your report is submitted:
- We reproduce the issue using the provided steps and evidence.
- The bug is prioritized based on severity and player impact.
- A fix is scheduled and tracked on the Patch Notes page.
- You receive an email when the fix is deployed or if more information is needed.
Our transparency policy means every resolved bug is referenced in release notes alongside contributor credits where applicable.