Feedback
Free AlphaReporting what broke is the most useful thing an alpha tester can do. There are two routes: the public forum thread for anything another tester might recognise, and email for anything you would rather not post in the open.
- Passwords, API keys, tokens or any account credential.
- Private conversations with your players.
- Text from licensed adventures or other paid material.
- Plot spoilers your group has not reached.
Send text only. Do not attach or paste a diagnostic bundle or a campaign archive, and do not link to one. If we need a support bundle, we will ask you for it and take it privately — review its contents yourself before sending it anywhere.
Public — the forum thread
The Fantasy Grounds thread for Nerve is the best place for questions other testers can answer, and it is where we post known issues. Start here unless your report contains something private.
Before posting, take out personal information, credentials and anything from a private campaign. Do not attach a support bundle to a public post — if we need one we will ask, and you can send it privately. Everything in the "please do not include" list above applies twice over in the open.
Private — email
For anything you would rather not post publicly, email us and we will read it. Put the summary in the subject line so it is searchable later.
That button opens your mail client with the checklist below already filled in. If it does not work, write to backchannelstudios1@gmail.com and include whatever you can.
What to include, either route
Three things are essential:
- Category — bug, suggestion, or performance observation.
- A one-line summary, in the words you would use to search for it later.
- What happened — what you were doing, what you saw, what you already ruled out.
For a bug, these make it far easier to reproduce. "Unknown" is a fine answer — a report with gaps beats no report:
- Nerve version, Fantasy Grounds version, ruleset, and which AI provider or model you selected.
- The exact error code, including the detail text underneath it — the detail often matters more than the code.
- Steps to reproduce from a known starting point, plus what you expected and what actually happened.
- Response time in seconds, if the problem is about speed or a timeout.
- Optional but useful: solo or multiplayer, other extensions enabled, and whether an approved action showed up in the native record.
What happens to your report
- Reports are text only. We do not want a diagnostic bundle or a campaign archive here.
- Anything you post in the forum thread is public and is not ours to take down. Email is the route for anything private.
- What you send us by email is not published by us.
- You get a reference number the moment a report is actually stored. If storage fails you get an error and your text stays in the form — we never show a success message for a report that did not arrive.
- The form is rate limited. There is no CAPTCHA and no puzzle to solve.
- We cannot promise a response time, so we are not going to print one. How report data is handled is described on the privacy page.