Feedback
Two ways to tell us something, and they are different on purpose: a bug is private and a feature request is public.
A bug, from the Dashboard
Section titled “A bug, from the Dashboard”The bug button sits in the top bar of the Dashboard, on every page of a project. It opens a form with one field — what happened. What you clicked, what you expected and what you got instead is enough; the page, the environment and the project go with the report by themselves.
After sending you get a number and a copy by email. Reply to that copy and the whole thread stays in one place.
Bugs are private: only we see them, and they never appear on the public page. You do not need to fill in versions or screenshots — say what you were doing, and we can find the rest.
A feature request, on the public page
Section titled “A feature request, on the public page”feedback.rudder.build asks for what your game needs in one field. An email is optional; without it the number you get back is your receipt.
Accepted requests appear on that page with a vote count. Voting needs no account: one vote per browser, and you can see what other studios asked for before you write your own.
A request is published only after review, and never in your name.
What is worth a report
Section titled “What is worth a report”| What | Where |
|---|---|
| A page that breaks, saves something else, or does nothing | The bug button in the Dashboard |
| A number, a record or a release that is not what you saved | The bug button in the Dashboard |
| Something you cannot figure out how to do | The bug button in the Dashboard |
| A feature your game needs and Rudder does not have | feedback.rudder.build |
| Billing, a plan, access for another person | [email protected] |
| A security problem | [email protected], not the public page |