Reporting a bug

Found something wrong in the game? Tell us from inside the game. It takes a minute, and you don't need to leave or open a website. Your report goes straight to the people who build Bezgelor, together with the details they need to find the problem.

There are two ways to report: typing /c bug in chat, or using the game's own Report a Bug window. Both send the same kind of report. With the Bezgelor Field Kit add-on installed, there is a third: a short step-by-step window that sends the same report too.

The quick way: /c bug in chat

Type /c bug and press Enter (typing commands). The game asks you a few short questions. You answer by typing /c bug followed by a number from the list, or by /c bug followed by your own words.

Example: a quest objective that didn't count.

You:  /c bug
Game: Let's report a problem. Which part of the game is it about?
      1. Quest  2. Combat or an ability  3. An item or a vendor
      4. A character in the world (NPC or creature)  5. Housing
      6. Crafting  7. PvP or an instance  8. Something else
You:  /c bug 1
Game: Which quest is it?
      1. Reporting for Duty
      0. None of these
You:  /c bug 1
Game: What went wrong?
      1. An objective didn't count  2. The quest didn't appear or I can't get it
      3. I can't hand it in  4. Something else
You:  /c bug 1
Game: Now tell me what happened in your own words, in one message.
You:  /c bug I killed three yetis and the tracker still says 0
Game: Here is your report. ... You wrote: I killed three yetis and the tracker still says 0
      Thank you! Your report (number 12) was sent to the developers.

Everything you can type

When the quest list comes up, the quest you track is number 1. If you just asked /c why quest about a quest (asking why), that quest is number 1 instead, and your report includes what the game said about it.

Your report is sent as soon as you've described the problem and answered the questions, and the game shows you what was sent. To stop before that, type /c bug cancel. If you walk away in the middle, the report is cancelled after 10 minutes.

Tips for a useful report

• Report it where it happened. The game records where you are and what you're targeting, so report while you're still there, ideally straight away.
• For a combat problem, target the creature first. The game then records which creature it was and the last abilities you used, and you can pick the ability that went wrong.
• Say what you expected and what happened instead. "The boss's ground circle hit me after I'd left it" is more useful than "combat is broken".
• If you remember how it worked in the original WildStar, say so. Bezgelor is rebuilt from what survives of the original game, and some details are our best guess. Your memory is evidence we can't get any other way. /c remember is made for it (remembering the original game).
• One problem per report. Two separate bugs are easier to fix as two reports.

The game's Report a Bug window

The game's own Report a Bug window (in the Interface menu) works too. Choose a category and subcategory, pick a quest if it's about one, click the creature or character it's about if there is one, describe the problem, and send it. You'll see a short confirmation in chat.

The Report Player window is separate. It's for reporting another player (spam, bots, cheating). Those reports go to the staff, not to the bug list.

What happens next

1. Received. Your report is stored straight away.
2. With the developers. Within a few minutes it is added to the developers' bug list.
3. When someone has looked at it, you get an in-game mail from "Game Master". It says whether the problem was confirmed, fixed, already known (a duplicate), or something we've decided not to change. Sometimes it includes a short note from the developer.

You can check at any time with /c bug status.

Fixed: please check it

When a problem you reported is fixed, and the fix is in the server you play on, the game asks you to check it: a short line in chat when you log in (or straight away if you are playing), and /c bug list shows the report as fixed, please check it. Go and try it, then:

• It works now: type /c bug confirm 12 (your report's number). The report is closed and we send you a short thank-you mail.
• It still happens: type /c bug reopen 12 and what you see, for example /c bug reopen 12 the yetis still don't count. The report goes back to the developers with your words.

Each report in /c bug list shows what you wrote (You wrote: "...", cut at 400 characters), what it was about (the quest, creature or ability, with its category when it names one), the date you filed it and any reply from the developers (We said:), so you can find the thing again and try it. The Field Kit's My reports and News show the same lines.

You can only answer your own reports. A fix the developers have made but that is not on the server yet shows as fixed, coming with the next server update.

You can send a report every 10 seconds, and up to 20 in an hour. If you reach the limit, /c bug tells you straight away how long to wait, before you write anything. A report that was already written when the limit was reached is kept: type /c bug yes when the time is up to send it.

What a report includes

To find the problem, a report automatically includes:

• your character (class, level, race, faction), where you are, and the server version;
• the quest you picked, with each objective's progress;
• what you're targeting (which creature, its level and health);
• the last ten abilities you used;
• what happened to your character in the last minute (for example kills, damage, quest updates) and the server's technical log lines about your character from that minute.

A report doesn't include your chat messages or whispers, your e-mail address or your IP address. The only text in it is what you wrote. Reports are read by the people who work on Bezgelor. The public bug list never shows your character name or account.

When not to use /c bug

• Stuck in the scenery? Type /c stuck first. After ten seconds of standing still it moves you to a safe place (getting unstuck). Then /c bug the place where it happened, because a spot that traps players is a bug we want to fix.
• Not sure why something does not work? /c why explains what the game can see (asking why), and tells you to /c bug it when it sees nothing wrong.
• Can't log in, or lost something valuable? Use /c bug if you can still play. If you can't get into the game, ask on Discord or open an issue on GitHub (links are on the website).
• A problem with another player: use the game's Report Player window.