Getting help

Fabled has five distinct help channels. Pick the one that matches your problem. Using more than one for the same issue makes it slower for us to respond, not faster.

Pick a channel

• Quick question or community chat: join the Discord server at discord.com/invite/fabledgg. GMs, players, and the team are all there. Best for 'is this a bug or am I missing a setting?' kinds of questions, and for showing off your tables.
• Account, billing, or sign-in trouble: email [email protected]. Use email when you cannot reach the in-product help (you cannot sign in, your subscription is wrong, your invoice does not match what you expected). Include your account email in the message so we can find you.
• General enquiry or sales question: fill in the contact form at fabled.gg/contact. It works without an account and routes to the right department based on the dropdown you pick.
• Bug report (you are signed in): click the small bug-icon button in the app and file a structured report. The reporter automatically attaches a screenshot, the last few seconds of console output, and your browser details, so we have what we need to reproduce. See the Report a bug how-to for the form's fields and what each one is for.
• Self-service answers: the FAQ (under Docs in the sidebar) covers the most-asked questions across sign-up, campaigns, the Forge, the marketplace, billing, account, and the table. If your question fits one of those buckets, the answer is already there.

Which channel for which problem

A rough decision tree, in the order most users should walk it:

1. Is there a question-mark icon on the screen where the problem lives? Open it. The drawer is usually the fastest path to the right doc.
2. If not, search the FAQ at fabled.gg/docs/faq. Eight categories; one of them will cover your question.
3. If the FAQ does not cover it and you can reproduce a clear bug, file it through the in-app bug reporter so we get the screenshot and console context for free.
4. If the problem is about your account or billing, email [email protected] directly. The bug reporter is for product behaviour, not account state.
5. If you want to talk to another human or are not sure what kind of question you have, jump into Discord and ask. The community answers a lot of questions before the team has to.

What to include when you reach out

The bug reporter pre-fills almost everything we need. For email or the contact form, three pieces of context make a huge difference to response time:

• What you tried to do in one sentence: 'I clicked Save on my framework and got an error', not 'frameworks are broken'.
• What happened instead: the exact error text if there was one, or a screenshot if it was visual.
• The URL of the page where it went wrong. We can almost always look up the rest from there.

What we cannot help with through these channels

A few things route elsewhere or just are not something the support team can change:

• Refunds outside the published policy. The team can confirm what the policy is and how to claim under it, but exceptions are rare. Read the policy first; ask in email second.
• Custom framework support. Frameworks you build yourself are yours; if a custom framework misbehaves, the framework's author is the right person to ask. The Discord has a creators channel that often catches these.
• Lost characters / lost campaigns caused by an account holder deleting them. Deletion is final; we cannot restore deleted content for you. If you are about to delete something you might want back, save it first.

Where to go from here

• The Report a bug how-to walks through the bug-reporter form field by field, including what severity level to pick.
• The Contact us how-to covers the contact-form fields and which department to pick for which problem.
• The Troubleshooting concept page lists the most common 'something is not working' cases and the first thing to try for each, before you reach out.