Just completed a hard Gaan-Telet run as vampire. I used only physical attacks against Horatio, but was not awarded the specialist badge. I did have whurrgarbl and was dealing burning damage on hit. Not sure if this is a bug or just the burning effect counting as magic damage for the purpose of the badge.

The game is kicking me back to the title / login screen after completing any and every dungeon. This happens after continuing out of the completion stats victory screen, and leaves me stuck reading unlock messages and whatnot while staring at the opening cluttered desk image instead of the actual kingdom where new stuff is presumably appearing. And yes, this breaks several of the early tutorials - the hand indicating what to click on next appears floating above the title screen and prevents me from hitting 'Play' to return to the kingdom unless I close and restart the game entirely.

I purchased and started playing Desktop Dungeons through Steam today, and this occurs regardless of whether the client is online, offline, or I've just run the game .exe without Steam open.

(Also, on a lesser note, mousing over the class challenge medal icons in the main menu codex states 'Click to select this challenge' when you cannot, in fact, click there to select the challenge.)

OneMoreNameless wrote:Is it really too much to expect that a game years in development, with a long open beta and over two weeks since its official release would actually function on the most basic levels?

No, it's not too much to expect a game to be working. You paid for it, it should work. Sorry.

We've rolled back the patch again because we didn't catch that new profile issue during testing this weekend. For what it's worth, the savegame system is currently going through a ton of changes because it's never been thrown at this many PCs that have problems connecting to Steam before. The web-player version, that has all that beta testing time behind it, works perfectly and if you have a DD.net account already, playing there is recommended right now.

Sorry, testing everything on Steam takes a lot longer than simply preparing a build and we'd already rolled back friday's patch once because it was looking in the wrong places for people's run data. I should have tested more.