Give me the patchnotes

[jotd]

Of the new version you just put online!!
Seems better so far, first 2 pvp games 2 wins.

 

[AutomaticCoding]

1. Broke the GUI
2. Broke mouseless ability on non-fullscreen mode (At-least, on mine)
3. More verbose logging
4. Added mulligan support
5. Added targeting support (Seems to be printing non-printable characters to the log (?), if this is the case, hex representation should be used)*
6. Win|Losses|Total actually increments now, doesn't assume it has won every game.
7. Seems like it properly cancels session with buddyauth

What I can see so far.

*Yes, it definitely is printing internal memory directly to the log:-

Let's hope Hearthstone doesn't standardize spell type 0x00, else, we're going to see quite a few broken logs (And copying and pasting a string containing 0x00 (On Windows, which, is what your bot targets) cancels it, due to the fact the Windows clipboard uses null-terminated strings).

 

[Apoc]

1. Broke the GUI
2. Broke mouseless ability on non-fullscreen mode (At-least, on mine)
3. More verbose logging
4. Added mulligan support
5. Added targeting support (Seems to be printing non-printable characters to the log (?), if this is the case, hex representation should be used)*
6. Win|Losses|Total actually increments now, doesn't assume it has won every game.
7. Seems like it properly cancels session with buddyauth

What I can see so far.

*Yes, it definitely is printing internal memory directly to the log:-

Let's hope Hearthstone doesn't standardize spell type 0x00, else, we're going to see quite a few broken logs (And copying and pasting a string containing 0x00 (On Windows, which, is what your bot targets) cancels it, due to the fact the Windows clipboard uses null-terminated strings).

So, yeah. Just to stop this before you start a scare-fest. The "unprintable" characters, are just from the obfuscation we currently use in the bot. It's trying to print an unprintable Unicode character. (Because that's what our obfuscation does)

Basically; it should be printing something more readable (which it is, in our internal builds), but due to the post-processing, it kind of nukes that. It's not a huge issue, we'll tweak some stuff and fix that later.

The mouse issues are still being worked on. I'll be doing more testing on that. Basically; in technical terms... the game only allows you to "grab" and "drop" cards if your mouse cursor is within the bounds of the game window. (There are alternative ways to avoid that specific issue, but it raises other security issues that we're not 100% solid on handling just yet, so we use another method to avoid it entirely)

The UI is being set up for localization. It should have been working, but I suppose not. We'll get that fixed ASAP. Nothing but the strings used for display are broken, so it shouldn't effect anything. (Just a bit odd to read)

 

[AutomaticCoding]

So, yeah. Just to stop this before you start a scare-fest. The "unprintable" characters, are just from the obfuscation we currently use in the bot. It's trying to print an unprintable Unicode character. (Because that's what our obfuscation does)

Basically; it should be printing something more readable (which it is, in our internal builds), but due to the post-processing, it kind of nukes that. It's not a huge issue, we'll tweak some stuff and fix that later.

The mouse issues are still being worked on. I'll be doing more testing on that. Basically; in technical terms... the game only allows you to "grab" and "drop" cards if your mouse cursor is within the bounds of the game window. (There are alternative ways to avoid that specific issue, but it raises other security issues that we're not 100% solid on handling just yet, so we use another method to avoid it entirely)

The UI is being set up for localization. It should have been working, but I suppose not. We'll get that fixed ASAP. Nothing but the strings used for display are broken, so it shouldn't effect anything. (Just a bit odd to read)

I wasn't attempted to start a 'scare fest', I assure you, I was just trying to create a less-than-official change long of what I've personally noticed through the update (As I couldn't provide what OP wanted, an official change log), I'm sorry if that's how it seems. As for the localization, I did realized that, I just didn't really comment on it.

For the mouse issues, I can't comment on that what-so-ever, as, I literally have no idea how Hearthstone works, so, whatever you think is best.