Reporting bugs

The most useful thing you can do as a tester is report clearly when something breaks or feels wrong. Here's how.

The in-app bug reporter

The fastest way to report anything is the bug reporter button in the bottom-right corner of the app. It's always visible — you don't need to leave the page you're on.

When you click it:

  • It captures the current page URL, your account info, and any recent errors automatically
  • You write a short description of what happened
  • It goes directly to the team

Use this for anything that happens mid-session — broken buttons, missing data, errors, things that don't respond. You don't need to switch tabs or find an email.

Discord beta channel

For anything that's not a hard bug — confusing flows, features that feel off, suggestions, questions — drop it in the Discord beta channel. That's where most of the conversation happens and where you'll see what other testers are running into.

Email

Reply to any email from Payton. Goes directly to him.

What makes a useful report

You don't need to be technical. The most useful reports answer three questions:

  1. What were you trying to do? — "I was trying to share an NPC to Discord from the GM Screen."
  2. What happened instead? — "The share panel opened but the Post button did nothing."
  3. Can you reproduce it? — "Yes, it happens every time I try to share an entity card."

If you saw an error message, include it exactly. If you're not sure whether something is a bug or expected behavior, report it anyway — that ambiguity is itself useful feedback.

What to do when the app shows an error

If you see a red error banner or an unexpected blank screen:

  1. Don't reload immediately — take a screenshot or note the URL first
  2. Use the bug reporter — it captures context at that moment
  3. Then reload and continue if you can

If the app is completely broken and you can't access the bug reporter, email Payton or post in Discord with the URL you were on and what you were doing.

See also