Dev diary
How an update gets to you: daily test builds, checks and notes
When an update reaches you, it has already been built, checked and played on our side. Here is the route, with examples from October.
A new test build every day
Since the end of September, a new test build of the game is made automatically every day from the latest changes. Busy days bring more: on October 14 the test version was updated five times. From October 1 to October 27, 87 test builds went up.
The test version is a separate copy of the game with its own servers. Our team and testers play it first and check fixes there. If a problem is still there, the fix goes back for another try.
Each build gets the next version number. That is why the public versions jump from 0.1.339 to 0.1.399 to 0.1.417. The numbers in between are test builds.
What a build goes through
Every build that can go out to players passes these steps:
- Fresh translations. Since early October, the latest translations are pulled in before each of these builds. A corrected line in any of the 11 languages lands in the next build.
- Start-up checks. Since mid-October, each build is started automatically in several browsers: a current Chrome set up like a budget phone, a desktop Chrome and the older Chrome 114. In each one a test guest has to log in, enter the world and walk for a few seconds. If that fails anywhere, the build stops there and can never go out to players.
- File check. A few minutes after a build goes up on the test version, and again after it goes out to everyone, an automatic check asks for each game file and makes sure it comes back in the right format. On October 21 that was more than a thousand files.
The Chrome 114 check comes from a real problem. After the October 15 update, the game had trouble starting for some players on older phones whose built-in browser is stuck on Chromium 114 or earlier. A fix went up on the test version on October 16 and reached everyone on October 21 in version 0.1.417. Now every build has to start in that old browser too.
From the test version to everyone
Nothing goes to everyone on its own. Someone on the team picks a build that is already on the test version and sends out that exact build. It is copied, not built again, so you get the same game that was checked.
Three of those 87 October test builds became public updates:
- October 1, version 0.1.339: new slash trails for poison and cursed weapons. Picking a creature you cannot attack no longer locks it as your target.
- October 15, version 0.1.399: the biggest of the three. It brought icons for buffs and debuffs, a redesigned task list, an Elven weapon set, new Mage and Barbarian outfits, Thai, Vietnamese and Turkish translations, and seven fixes.
- October 21, version 0.1.417: better loading on older browsers and improved translations in all supported languages.
Every public update since October 1 has patch notes in the News section, split into what is new and what was fixed. The notes cover what changed since the update before, and a person on the team reads and approves them before they go up.

When you find a bug
Write to [email protected]. We read every message, and replies usually take one to three business days. Please include:
- your character name
- how you sign in
- your device and browser
- what happened, with a screenshot if you can
The browser matters: the October 21 fix was only for older browsers.
A fix takes the same road as everything else: into a test build, checked on the test version, then out to everyone with the next public update. Fixes you would notice in the game are listed under Fixes in that update's notes.