Help
Find Round Trip technical support, private verified-purchase tickets, and the public feature ideas and roadmap board.
On this page
Support lives on the Bit Quirky Discord. Anyone can join and read. A verified Unity Asset Store purchase opens private tickets for Round Trip. You can ask before you know the cause, and support will help narrow it down.
Where to ask
Section titled “Where to ask”| You have | Go to | What happens |
|---|---|---|
| A how-to question other people may also hit | The public help forum | Ask in the open. Solved threads remain searchable for the next person with the same question. |
| A bug, a project we need to inspect, or anything containing your own code or data | A private ticket from #private-support | A channel opens for you and Bit Quirky staff. Choose Bug, How do I…?, or Playtest. |
| A purchase, invoice, license, or account question | A private Licensing ticket | Commercial and personal details stay inside the ticket. Nobody will ask for payment card details. |
| A feature suggestion or an improvement you can discuss publicly | The Round Trip feature board | Browse ideas and the roadmap, add an idea, vote or comment. This is product feedback, not technical support. |
| Something to show or code to share | #show-your-work and #community-code | Community channels for projects, patterns and useful snippets. |
Unsure where to ask for support? Start private. A private answer can become a fresh public answer later without carrying your project details with it.
Feature ideas and roadmap
Section titled “Feature ideas and roadmap”Browse existing suggestions and the roadmap on the Round Trip feature board. Anyone can read it. Sign in with a code sent to your email to suggest an improvement or vote and comment. You do not need a verified purchase to participate.
Votes help us prioritize, but an idea, vote or roadmap entry is not a promise of delivery. For bugs and how-to questions, use Discord support instead. Keep private code and project details off the public board; use a private Feature idea ticket when a suggestion needs confidential context.
Looking for another Bit Quirky Unity asset? Browse the ideas directory.
Verify your purchase for tickets
Section titled “Verify your purchase for tickets”- Join the server and accept the rules in #rules.
- Send the verification bot a direct message:
!verify <invoice-number>. The invoice number is on the Asset Store receipt and in your Unity account order history. - Round Trip tickets open for that Discord account. One invoice verifies one account.
If verification fails, or your purchase route supplied no invoice number, say so in #private-support and a person will sort it out privately.
What to include in a report
Section titled “What to include in a report”A compact report with exact text is better than a cropped red icon.
- Round Trip package version, shown in Window > Package Manager.
- Unity version and operating system.
- The source folder, class and method you had open.
- Where the problem appeared: installation, indexing, reading, drafting or Compile.
- The exact console error, status message or refusal text.
- Steps from a freshly opened editor to the result.
- What you expected instead.
- A small source example when it can be shared safely.
Send what you have. Support can ask for the missing pieces.
Keep credentials, access tokens, private addresses and personal data out of public posts. Strip unrelated game assets before sharing a project in a private ticket.
Reporting a documentation error
Section titled “Reporting a documentation error”Documentation bugs belong in the public help forum. Include the page URL, the heading above the problem, your package version and what the editor actually shows. A missing item on what it does not do yet counts too. Join the server first if the forum link is not available to you yet.
Pages that answer common questions
Section titled “Pages that answer common questions”| Page | Use it when |
|---|---|
| Protect your game files | You are about to edit a real project, or a script needs to come back from an earlier commit. |
| Troubleshooting | Something is broken and you want the next check by symptom. |
| What it does not do yet | A node or edit is refused and you need the current boundary plus today’s route. |
| Compatibility | You need package, Unity, dependency or player-build facts. |
| Release notes | You want the recent changes grouped by product area. |
| Glossary | A word on the canvas or in these guides is unfamiliar. |
- Troubleshooting: match a visible symptom to the next check.
- What it does not do yet: check the current refusal list.
- Compatibility: confirm your Unity and package versions.

