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: September 9, 2026

Before you report

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

Useful details

  • Short summary and expected vs actual behavior.
  • The shortest steps that reproduce the problem.
  • Product and your role (GM or player), without private world or scene names.
  • Browser and OS version.
  • Time of occurrence and any visible error message.

Helpful extras

  • Sanitized screenshots or short clips from a blank or bundled sample, without private content.
  • Affected asset type (token, tile, light, or audio), without private file names or local paths.
  • 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 support@aethera.tv.

Where to report

Email support@aethera.tv. For non-sensitive bugs, you can also use an issue tracker when available: Issue tracker unavailable. Do not send passwords, tokens, sign-in links, or private campaign files.

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 in the changelog, operational state on the Status page, and VTT-specific releases in the Aethera VTT changelog.

Support prioritization and availability: Support