Full disclosure: for now, only we ourselves get into the game. We catch game bugs ourselves; this template is for when playtests open. Until then, we’re waiting for site and forum bugs here — they have their own pinned thread.
A good bug report answers three questions: what you did, what you saw, what you expected. Everything else is a bonus.
Template:
- What happened — one sentence.
- How to reproduce — steps, in order. 1, 2, 3.
- What you expected — how it should have gone.
- Where — hub or raid, day or night, rain, indoors or outside.
- How often — every time, sometimes, once in a whole evening.
- When and who — date, rough time and your in-game name: that’s how we find the server log.
- Screenshot or video — as a link: images can’t be embedded in posts yet.
Example (made up, the game is still closed): Hub. Two of us in a squad stand still by the Guide’s car. After five seconds the car leaves and my squadmate stays behind. Two times out of three.
Bad example: “doors are broken.”
Spoiler
We know. We built them that way.If the game crashes, it sends us the tail of the log by itself the next time you connect. Write anyway: the log knows where it crashed, not what you were doing at that moment.
Found a dupe or a way to see through walls? Don’t post the recipe in an open thread. Say what you found, without the steps — we’ll reply right here and tell you where to send the details.
A question for anyone who’s written bug reports for other games: what’s dead weight in this template, and what’s missing? And do you want a “report a bug” button right in the game, or is it easier to come here?