I am . I don ' t need anything but I ' m going with my buddy . <| sep |> Due to the fact that we say little people tend to project their personal latent dispositions on us to familiarize the unfamiliar . Mastery and Awareness of nonverbal communication is imperative to play this up to the fullest . It ' s all the easier when physically Dominant . <| sep |> It ' s not that simple . To see what happens here , you must first understand how integers work in computers . To bring you to the core problem How would you store an integer on your hard drive ? It is saved as 1 s and 0 s , yeah , but how do you know which 1 s and which 0 s are part of your integer and where does it end ? To solve these computer scientists have decided to simply have a maximum size for integers , so that say can be as big as whatever fits into , say 32 bits so the largest number possible would be 232 tel , or 2321 tel because you also need to be able to store a 0 , or 2311 tel when you want to allow negative numbers signed integers . This is a good solution , because then computers with according architecture can always do integer calculations in a single processor cycle because integers cannot be larger than x bits . Now what happens when a calculation produces an integer that is too large or too small ? Well here ' s the beauty The exceeding bits are simply truncated , cut off . So mathematically speaking computer integers aren ' t even integers . They ' re residue class rings . What this means for us is that when an integer would get only a single bit too large , its value is more than halved . Even worse with signed integers those that can hold negative values They suddenly become negative . That ' s what happened in the video , though Blizzard wisely caught the case of negative damage and dealt 0 damage instead . Now how do we fix this ? Well we could simply implement our own numeral types and make numbers that consist of multiple integers to store larger numbers . Maybe we can even have them store arbitrarily many integers to make arbitrarily large numbers possible . But the more interesting question is do we want to fix this ? Because as I said system integers are fast , as in a lot faster . Do we really want to sacrifice hearthstones ability to run smoothly on weak machines for this edge case scenario ? I can ' t tell you that . But now you know why it happens . Hope it helps . Edit to clarify , the machines getting in trouble for using different number representations wouldn ' t be your computer , it would be the hearthstone servers . I don ' t even know if your computer recalculates what the server tells it .