New Bug Tracker: User Echo

User Echo Steam Inline

Darkest greetings Underlord,

We’ve always been dedicated to providing the best experience we can in WFTO and one of the cornerstones of this is continued support and post-release development. This lets us address the bugs discovered and integrate suggestions that we feel fit into the game.

It’s no secret that WFTO did not launch in an ideal state, a topic we cover in our very first State of the Game post. Although many of the most critical problems were solved within days of release, and even more still when 1.1 released, we have continued to push out regular fixes. As of today a total of 636 bug fixes have been introduced and 819 other changes implemented.

A few days ago we unleashed patch 1.3.2 upon the world, bringing with it a whole host of new improvements and fixes. Thus far the reception has proved widely positive, with praise focussed particularly on the performance and AI improvements.

All of this has been made possible thanks to your continued support and feedback, and the work of a select group of community volunteers that make up our QA team – a group we don’t thank often enough!

Today we have an announcement that should make the whole process more efficient.

Introducing User Echo

Since the very first release of the Bedrock Beta we’ve always handled bug reports on our official forums. Initially this was intended as a short-term solution to save costs while the flow of bug reports was minimal, but over time it became the default method for handling reports, simply because our resources were too limited and time too short to consider moving away from it.

While we still aimed to address every report, this system was fraught with difficulties:

  • It was hard for users to search for similar reports
  • Significant moderation was required to ensure reports were handled correctly and duplicated appropriately to our internal bug tracker
  • Reports could easily become buried amongst others during hectic times

To make the process of reporting bugs more user friendly as well as assist our development and QA teams in managing reports, we’re introducing a new public bug tracker powered by User Echo!

Reporting a bug with User Echo

User Echo is an intuitive kit which will allow you to quickly report issues. As always please follow our guidelines for reporting bugs so you always provide the necessary information for a fix.

We’ll be covering the very basics of reporting a bug in this post, but keep your eyes on our forums for additional information on the features of User Echo.


When first navigating to our User Echo page you’ll be presented with a page like this. From here you can see the most recently updated tickets. These will often be in-progress or recently completed issues. Have a quick browse and see if your issue is on this list.

If you find your issue in this list then we recommend you quickly pop into the topic to see if it correctly matches your issue. If it does then you can +1 or comment on the topic to help ensure it gets the attention it deserves!

If your issue isn’t in the list then you can start to type the description for your bug in the text box. As you enter details you’ll find that User Echo searches our database for any matching entries. As before, if you see your issue in the list check it out and comment if it matches your complaint.


If none of the issues listed match your complaint then simply click the “Add a new one” button and fill in the fields. Remember to make this as informative as possible, include all the details you can such as our requested info, details on the bug, when and how it occurred, if you can replicate it, and screenshots or video.

You’ll need to sign in to post your report, either by registering a community account or signing in with your Facebook, Google+, Twitter, VK, Yahoo, Live, GitHub, Yandex or OpenID accounts.


Once your topic has been created you’ll usually receive a response from our team within 48 hours, often less, so be sure to keep on top of your ticket in case we need anything more to help our investigation.

On average tickets are resolved within 5 working days of being submitted, either by being fixed in the next patch, declined or marked as not a bug.

That covers the basics of our new reporting system. If you have any questions feel free to ask in the comments or on our forums!


Until next time Underlord,

– WFTO Team

Click here to discuss this update on our forums!

Click here to read our bug report guidelines!

Click here to be taken to User Echo!