Beta Reporting Guidelines

Use these guidelines to report bugs, feedback, and stability issues during the Aethera VTT open beta. Clear reports make a problem easier to reproduce without exposing private work.

Last updated: August 9, 2026

Before you report

  • Check Known Issues to avoid duplicates.
  • Confirm the issue persists after a page refresh.
  • Note whether it happens in a specific scene, tool, or module.

Required details

  • Short summary and expected vs actual behavior.
  • Steps to reproduce (minimum 3 steps if possible).
  • World name, scene name, and role (GM or player).
  • Browser and OS version.
  • Time of occurrence and any visible error message.

Helpful extras

  • Screenshots or short clips (mask personal data).
  • Asset file names or IDs involved (tokens, tiles, lights, audio).
  • Whether the issue happens with modules disabled.

Security issues

If you believe you have found a security vulnerability, do not post it publicly. Report it privately via Loading support email.

Where to report

Use the issue tracker when possible: Issue tracker. If the tracker is unavailable, email Loading support email.

Response expectations

I review beta reports by impact. A report may not receive a personal reply, and a confirmed issue may be scheduled rather than fixed immediately. Track shipped changes on Updates, operational state on the Status page, and VTT-specific releases in the Aethera VTT changelog.

Support prioritization and availability: Support