IMO the more important (and scary) thing to take away from the video and their bug report is that there are no code checks in place currently to prevent minion health -- and who knows what other data points -- from overflowing their storage variables, in this case a 4-byte integer. Granted, this was an extreme border case, but still probably something that should have been accounted for. There might be a number of other similar live bugs that we just don't have the means to test ourselves.
Ez what happens after 1.3 bil. You guys were so worried about hitting it, does the game crash?
It's a bit computer and programming technical. But you run into something called overflow, depending what kind of variable you use you hit it earlier og later.
Imagine a odometer in a car, that shows overall traveled distance. If you have it filled out with all 999999 and drive one more meter you hit 000000 instead of 1000000 because you run out of space for more numbers. It's the same principle here, except you wouldn't hit 0 you would hit the largest negative number.
The reason it's a strange number and they stop at 1.3 bill. and don't wan't to double is because programming and computers in general are binary based and Blizzard is probably using a 32 bit integer to store health and damage thereby making the maximum value 2,147,483,648 (or 2^32) going over that causes the health to overflow and go into negative and the card dies.
Hearthstone limits both number of minions allowed on the board and life total. So manipulating creature stats is pretty much the only way we'll see extreme values in Hearthstone. This particular set up required both players to be in cahoots. Couldn't happen in regular play. So I don't think they need to worry about negative health Lorewalker Cho "bugs".
Ez what happens after 1.3 bil. You guys were so worried about hitting it, does the game crash?
It's a bit computer and programming technical. But you run into something called overflow, depending what kind of variable you use you hit it earlier og later.
Imagine a odometer in a car, that shows overall traveled distance. If you have it filled out with all 999999 and drive one more meter you hit 000000 instead of 1000000 because you run out of space for more numbers. It's the same principle here, except you wouldn't hit 0 you would hit the largest negative number.
The reason it's a strange number and they stop at 1.3 bill. and don't wan't to double is because programming and computers in general are binary based and Blizzard is probably using a 32 bit integer to store health and damage thereby making the maximum value 2,147,483,648 (or 2^32) going over that causes the health to overflow and go into negative and the card dies.
That makes sense, I didn't even consider that it was just hitting the overflow value. Im curious to see if you could overflow the attack dmg if it would heal in the negative numbers instead of deal damage. You could use Blessed Champion but it would take longer than Divine spirit because it costs more.
http://i.imgur.com/HmDQcn9.jpg
http://www.twitch.tv/noxious_hs/c/2856783
http://i.imgur.com/mmieDJR.gif
This is crazy lol
do explain
What video is this from?
http://www.twitch.tv/noxious_hs/c/2856783
Absolutely ridiculous
This made my night heh. It also proves how broken spell sharing can be
Deathwing is a little pussy. ENTER THE PANDA!!
1.3 billion. Working as intended™
#trollface
This needs to go front page already :)
Nozdormu wins you every game where you opponent has to go to the bathroom on turn 9.
yes please front page.
IMO the more important (and scary) thing to take away from the video and their bug report is that there are no code checks in place currently to prevent minion health -- and who knows what other data points -- from overflowing their storage variables, in this case a 4-byte integer. Granted, this was an extreme border case, but still probably something that should have been accounted for. There might be a number of other similar live bugs that we just don't have the means to test ourselves.
I'g glad some one did this I posted a deck capable of this a few days ago, I should have just asked nox to do it then lol.
pfff who uses integers anymore? what is this, the 80's?
Happy you guys enjoyed this! <3
http://www.hearthpwn.com/managrind
Ez what happens after 1.3 bil. You guys were so worried about hitting it, does the game crash?
It's a bit computer and programming technical. But you run into something called overflow, depending what kind of variable you use you hit it earlier og later.
Imagine a odometer in a car, that shows overall traveled distance. If you have it filled out with all 999999 and drive one more meter you hit 000000 instead of 1000000 because you run out of space for more numbers. It's the same principle here, except you wouldn't hit 0 you would hit the largest negative number.
The reason it's a strange number and they stop at 1.3 bill. and don't wan't to double is because programming and computers in general are binary based and Blizzard is probably using a 32 bit integer to store health and damage thereby making the maximum value 2,147,483,648 (or 2^32) going over that causes the health to overflow and go into negative and the card dies.
Yup. This is what i tried to explain. The value overflows and it's health goes into negative = dead.
Hearthstone limits both number of minions allowed on the board and life total. So manipulating creature stats is pretty much the only way we'll see extreme values in Hearthstone. This particular set up required both players to be in cahoots. Couldn't happen in regular play. So I don't think they need to worry about negative health Lorewalker Cho "bugs".
That
http://www.hearthpwn.com/managrind
That makes sense, I didn't even consider that it was just hitting the overflow value. Im curious to see if you could overflow the attack dmg if it would heal in the negative numbers instead of deal damage. You could use Blessed Champion but it would take longer than Divine spirit because it costs more.