Hearthpwn

That seems odd, the UI should log an error or something. Not sure how to work out what's causing this :(

Well, my excuse is that I didn't write that >.> If you update to 0.3.12 you should be able to import from a Deck Builder URL.

It's cropped up a few times, it's just been really difficult to pin down exactly why it happens :(

Hm, we never thought anyone would want to do that I guess. It's easy enough to add, I'll try to get to it tomorrow now that other work things are not ON FIRE.

The error is helpful, thanks. I'm still confused about how or why this is happening though, and can't seem to reproduce the problem :( Hopefully Molster isn't super busy some time soon and he can look at his terrifying UI code.

The functionality exists but isn't automatic - we're pretty sure it would be a bad idea to automatically add several hundred thousand new decks. Switch to the Innkeeper window (when Hearthstone is running) and click "Export and Verify Decks", you'll get a window like the following. Click a deck to load it in the Hearthpwn deck builder, then click "Save" on that page to save and share it.

That doesn't even make sense for fixing your login issue, but yay if it did so. Debugging super random problems like this is annoying :(

I'm stumped on this one. I don't have all of the cards to recreate it (curse you, Old Gods packs) - does it still behave badly if you make a new deck with the same cards?

That sounds pretty bizarre - I'm assuming this is a constructed deck? Was it made using the weird "deck template" things?

These are all "403 Forbidden" errors, even when trying to retrieve updates. Are you behind some sort of work/school/etc proxy that requires authentication?

Weird but cool that it's fixed. I'll look at switching our hash algorithm to something that won't trigger this in future, this is the second or third time it's come up :v

Is there anything in your ui.log?

Quote from cmlk93 >>

Quote from Freddie >>

"The host part isn't a local hostname" - something on your computer has changed the address of localhost? Try the alpha version I guess.

 any idea for me?

This is our mysterious friend the "FIPS" error - we store an MD5 hash of your collection to check for changes, but if Windows is set to FIPS mode (a financial/security thing) MD5 isn't allowed to be used. I think the solution to this is to change the hashing algorithm we use, though I feel like any machine with this enabled probably shouldn't be running games/Innkeeper anyway ;)

I'll look at the standard vs wild thing, not sure if we'll be able to automate the change - might just have to be a "You're trying to import a Wild deck and your deck is set to Standard, change it to continue" thing. I haven't tested import in windowed lately, I'll see if I can reproduce that. Secret stuff might have to wait for the next release, we're trying to nail down (some of) the 0.3 bugs so we can get it on to the release channel.