Skip to content
Bit Quirky Round Trip
Visual Scripting

Search documentation

All topics and APIs

Close returns focus to Search.

What are you looking for?

Try a common topic or enter a complete API identifier.

Browse the reference instead

Esc closes · Tab reaches results · Enter opens the focused link

v0.89.0
Menu

Help

Get Round Trip support through the Bit Quirky Discord, private verified-purchase tickets or the public help forum.

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.

Join the Bit Quirky Discord

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 graph.
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…?, Feature idea, 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.
Something to show or code to share #show-your-work and #community-code Community channels for projects, patterns and useful snippets.

Unsure which fits? Start private. A private answer can become a fresh public answer later without carrying your project details with it.

  1. Join the server and accept the rules in #rules.
  2. 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.
  3. 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.

A compact report with exact text is better than a cropped red icon.

  1. Round Trip package version, shown in Window > Package Manager.
  2. Unity version and operating system.
  3. The source folder, class and method you had open.
  4. Where the problem appeared: installation, indexing, reading, drafting or Compile.
  5. The exact console error, status message or refusal text.
  6. Steps from a freshly opened editor to the result.
  7. What you expected instead.
  8. 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.

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.

Page Use it when
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.
Full-size image