Short version: this repo is for feedback, not code.
Thirdrez products are closed source, so there's nothing here to send a pull request against. What we do want — a lot — is to hear what's broken and what's missing. That's the whole reason this repository exists.
| 🐛 Something is broken in TRZ View™ | Report it → |
| 💡 An idea for TRZ View™ | Tell us → |
| 🐛 Something is broken in Kinetiq Engine™ | Report it → |
| 💡 An idea for Kinetiq Engine™ | Tell us → |
| ❓ A question | Discord — faster, and someone else may have hit it too |
| 🔐 Account, billing, or a security problem | contact@thirdrez.com — never in a public issue |
We're not asking you to write like an engineer. We're asking for the handful of things that decide whether we can reproduce the problem or not:
- One problem per issue. Three bugs in one issue means two of them get lost.
- What you expected, not just what happened. That gap is usually the actual bug.
- How to make it happen again, if you can. This is the single most valuable thing in any report.
- Your version and system. A bug that only shows up on one driver or one build is invisible to us without it.
- A screenshot or a short video. For anything visual, this beats three paragraphs every time.
For TRZ View, the in-world region also matters more than you'd guess — plenty of problems only happen in one place.
- Don't apologize for not being technical. Most of the people we build for are creators and residents, not developers. Describe it the way you'd describe it to a friend.
- Duplicates are welcome. If someone already reported your bug, add your details to their issue. Knowing five people hit something changes how we prioritize it.
- "This is probably just me" — tell us anyway. It usually isn't just you.
We don't take code contributions, and there's no source here to change. If you spot a typo in one of these documents, a small PR is fine and appreciated. Anything larger, open an issue first so we can talk about it before you spend time on it.
Everything here is public, so leave out passwords and real-life details you wouldn't want indexed by a search engine. Beyond that, see the Code of Conduct — it's short.
By opening an issue you're letting us use what you wrote to improve the products, including building the thing you suggested. See the LICENSE.