Start a discussion for the issue you're seeing. A clear description is more useful than knowing the technical terms; screenshots and short clips can help.
For a bug report, include what you can:
Summary:
Pinward or Pinworks version/build:
Operating system and device:
Table and mode (if relevant):
Steps that lead to the problem:
What I expected:
What happened instead:
Does it happen every time?
Relevant screenshots, replay, or logs:
For performance or input problems, mention your graphics hardware, controller, and display setup if you know them. For an authoring problem, a small example that reproduces it is especially helpful. Keep a copy of your original table.
Search for an existing report first. If you find the same issue, add your version and any new evidence there. Otherwise, use a separate discussion per problem so we can follow up clearly.
Review anything you share. Logs and file paths can contain names or other private details. Don't post passwords, account tokens, purchase details, or reset links. If a file needs to be shared privately, email support@qtrfeast.com first. Please don't attach executable programs.
When something is resolved, reply with what worked. It helps the next person and lets us distinguish a workaround from a fix. A report may lead to an internal development issue; you don't need a separate developer account to ask for help here.
Attach replay files in their native XZ-compressed format, without putting them in a ZIP. Attachments can be up to 20 MB and are public when shared in public discussions. For larger files, contact support first.
For a solved question, select the reply that helped as the best answer. A best answer records a useful response; it does not mean a game bug has been fixed.
