What's new
The short version of each release, in the order they shipped. The full list is in the changelog, which is the same text the app shows you when it updates.
2.18.0: a marketplace for settings
New: a marketplace for settings. Share the setup a character is running under a name and a description, aimed at one class or at everybody, and use what other people have shared. Sort by popularity, by rating, by newest or by how often an entry has been used, filter by class, and search.
Every entry is checked on the server before it is stored. Only keys shaped like settings this app writes are accepted, values must be true or false, a number, a short name or a list of those, and anything else is refused with a sentence saying which field and why.
Notification webhooks, Telegram tokens, proxy addresses, the lists of named players and the guild name are removed and never travel. They are somebody's identity or somebody's machine, and the publisher is told exactly what was left out.
One vote per account, changeable, and taken back by pressing the same arrow again. Entries carry the date they were published and the app version they came from.
Applying an entry writes over the defaults rather than over what your character already has, so an entry means what it names and nothing else.
Anything can be reported, with a reason, and taken down without destroying the votes or the author's history.
2.17.7: the second hand, and installers that replace each other
Fixed: the Assassin never equipped a second weapon. Every weapon maps internally to the main hand, and the Assassin is the only class carrying a weapon in the second one, so that hand was never a candidate: nothing was equipped there, nothing was bought for it, and the seller treated every upgrade for it as junk and sold it. Reported as a level 60 character still holding a level 1 starter weapon.
Both hands are now compared separately and the weaker one gets the upgrade. A shield is refused for that hand outright, because wearing one would trade the class's second weapon for a block chance.
Fixed: applying a preset could reset settings on every character. The version stamp the frontend writes had fallen five migrations behind the bot, so applying a preset told it the settings were old and it re-ran them: World Boss upgrades back on, expeditions preferred, gem replacement on, the pet order rewritten, the achievement engine off. Applying to all characters did that to every account at once.
Clicking a preset or a saved profile now only opens it. Applying is a separate button, applying to every character asks first and says what it costs, and it can be undone afterwards: every character gets back exactly what it had.
Fixed: the gear analysis recommended nothing to the nine hybrid classes. It compared an item's class requirement against the character's class directly, which can only ever match for Warrior, Mage and Scout.
New: Server Start can push the album to a percentage you choose, spend at most a set number of mushrooms getting there, and write one line in the activity log when it arrives, so you can take the thirst back over by hand.
New: a star on every scanned player puts them on the attack-first list, for farming a missing item by hand.
Fixed: installing over an older version could leave both. There are two installers, .exe and .msi, and neither knew the other existed, so an .msi over an .exe install meant two entries in Apps & features and two copies of the program. Each removes the other now, before it installs anything.
Fixed: "delete application data" left almost all of it. It removed the webview cache and not the folder holding every setting, log, scrapbook cache and analytics file, which was 650 MB on the machine this was found on. Both go now, together with the start-with-Windows entry and the shortcuts older versions left behind.
2.17.4: the opening, watched live
Server Start. The first days decide the rest of a character, and the order that pays is not the order the modules run in by default. Server Start runs the opening in phases: the guild first, then the arena until the album can be bought, then the album alone, then the dungeons, then everything. A phase holds back the modules that do not belong to it, and the page names every one it is holding back, so "why is my bot not questing" is answered on screen.
The album comes first for a reason worth knowing: its fill percentage IS the experience bonus the game grants on everything. Every point of it makes every later quest worth more, which is why filling it early beats questing early.
A live feed. The current target with its win chance, the actual items that fight would collect drawn with the game's own artwork, the next eight targets in the order the combat module weighed them, the dungeons waiting behind them, and the gains as they arrive. The queue is the list the bot acted on, not a second opinion, so the panel cannot drift away from what the bot is doing.
Speed Mode. One switch. It pays a mushroom for the next fight instead of waiting for the free one, so the album fills at the speed you buy. It works only in the arena and album phases, stops by itself when the opening is over, is off by default and capped per day, and your mushroom reserve still applies above it.
The scrapbook crawler was working the wrong end of the server. It started at Hall of Fame page 0, the top of the ladder, so a level 15 character spent every request on players in the six hundreds: ten minutes of crawling, 701 players cached, 2 of them fightable. It starts at your own rank now. It also stopped paying for information it already had, since every Hall of Fame page carries each player's level and the crawler was looking up all 51 names before checking it. Same budget, targets you can actually fight.
Anonymous mode had three leaks, all in the parts of the screen people photograph when they ask for help: the character name in front of each activity entry, the linked characters in the settings sync banner, and the player names inside the log's command payloads. All three are masked now.
Thirst for adventure showed the wrong ceiling. Every beer raises the day's maximum by 20, so a character who had drunk eleven had 320 minutes and the Overview still printed "0/100".
The advertisement module is no longer built or shipped, for security reasons. The code stays behind a feature flag and is still compiled and tested, but no released build contains it.
2.17: the Hellevator, properly
The Hellevator had three separate faults, and together they meant it did nothing at all while reporting no error.
It never joined the event. Its status read as "not available" whenever no run data had arrived, including during a live event the character simply had not joined yet. The join was the only thing that could produce that data, so it waited for something only it could cause. Switched on, event running, nothing happened, and nothing said why.
Every treat purchase was refused. The shop slot is counted from one and was sent counted from zero, so the server looked up the first treat while the app named the second, and answered "snack type mismatch". In one day: 302 refused purchases and not a single fight.
One refused step ended the cycle. The purchase ran before the fight and treated a refusal as fatal, so a shop that said no meant no climbing at all. Claiming rewards, signing up for the raid and shopping are all best effort now.
Also in 2.17
- A Hellevator page on the Events tab, appearing by itself while the event runs: the climb, the treats on offer with the one it will buy and what it is worth per key card, the guild raid floors, the floor's monster, the recent fights, and a line saying what happens next.
- Hellevator settings of its own, beside the World Boss and the Legendary Dungeon rather than buried in Extras.
- It climbs on key cards first and buys a treat when it starts losing. A treat lasts two floors, so one bought at the bottom spends cards on floors that were winnable bare. The first loss is where a treat starts paying for itself.
- Eight more languages, all complete: Czech, Polish, Russian, Chinese, Japanese, Italian, French and Spanish, alongside German and English. Chinese and Japanese also got the typography they need, because nothing below eleven pixels is readable in those scripts.
- A whiteboard you can wire. Draw the cycle, drag a box onto another to place it in the sequence, click a line to cut it. Boards can be named, saved, exported, imported and undone, and they travel with the settings sync.
- Press an item to see what it would replace, with the equipped item beside it and the difference in colour.
- A headless build for ARM64 Linux, for a Raspberry Pi or a similar board.
- Numbers and dates follow the language you chose, not the operating system's. A German on an English system picked Deutsch and still read 1,234,567.
- Signing up for the guild raid is now off by default. Shipped on, it was refused on every account, every time. See Hellevator.
2.16: a lock, and a build that was not the build
The app could lock up shortly after signing in. The status poll took a second read lock on the account's session to read two strings from it, and the engine holds that lock for writing across its network requests. Any poll landing mid cycle waited for the whole cycle, and the polls behind it queued up.
The build that ships is now the build that gets tested. An optional feature was reaching users straight from the release job, never linted and never tested, because it was compiled out of every check. The checks now run in both configurations.
2.14: schedules and saved profiles
The bot can be restricted to days and hours. Outside those windows it sends nothing at all. It does not idle quietly, it stops. See Settings.
A profile library. Save the settings you are running under a name and come back to them in one click. Each profile describes itself from the settings rather than from a description typed once, which goes stale the moment you re-save.
The beer controls moved to Mushroom spending. Every beer costs a mushroom, and they sat under Tavern & Quests, so the list of "what may spend my mushrooms" quietly left three of them out.
2.13: dungeon order, and money that reads like the game
Choose the order your dungeons are fought in. Off by default, because the bot still picks the most winnable target, which is right for almost everybody. See Dungeons, tower & fortress.
Every ordered list can be dragged, as well as nudged with the arrows.
Large numbers are shortened the way the game shows them. Wood, stone and souls all read the same way.
A refused attempt no longer backs off for a full hour. An hour is the wrong unit for something that may be true again in a minute.
2.12: accounts, and a console you can automate
Accounts that were already signed in stopped vanishing from the screen while their bots kept running in the background.
The console build got a non-interactive mode, which hands a JSON object out: the character list, a full character state, what the combat module decided. See the CLI reference.
2.11: anonymous mode
A switch in the header hides every name in the app: your characters, your accounts, opponents, guilds and their members, the battle history, the activity feed and the log, so a screenshot can be shared as it is.
Names are replaced by a stable stand-in rather than blanked, so you can still tell whether the player who beat you twice was the same player. The stand-in is salted with a random value generated on your own machine that never leaves it. See The overview screen.
The Tower told the server the floor it had already beaten rather than the one it was entering, so every attack was refused and the shared daily fight was spent on nothing.
2.10: one module for arena and scrapbook
Arena fighting and scrapbook hunting became one module. They used to be two, with two copies of the rules that disagreed with each other about whether a win-chance floor may veto a free fight.
The Arena screen shows the decision: how many candidates came from each source, what each was worth, which one won, and during the cooldown, what it will fight next. See Arena.
The download is a third smaller, from 364 MB to 238 MB, and looks exactly the same.