Umm what is that biggest hit
ToniXD_16
Member Posts: 214 ★
0
ToniXD_16
Member Posts: 214 ★
Comments
(although, you said “MANY programming languages” ?? Which programming languages could you have a “signed 32-bit integer” that does NOT have that 2,147,483,647 capacity, lol ?)
And fyi for others who punch in 2 to the 32 power and cut it in half for signed vs unsigned and say it should end with “648”, that's because “zero” takes up a spot (technically on the half that is positive), while the “negative” max does indeed reach that full negative “… 648”.
But I’m wondering what the potential mixing of storage variable sizes, overflows, etc, are involved resulting in the left side number in that pic, that “97 billion” number which miraculously ends as a whole “10-thousands” 0000.
(and is well beyond the 32-but storage used for individual hit maximum)
In another game I played there was the question "what's the most damage you could ever see all at once" and I calculated that this would happen when a certain explosion happened in the game that was designed to deal three times the player's own health bar at them, which obviously would kill them. The reason for the triple damage was because there were certain mechanics in the game that could save you from dying even if you took damage equal to your health bar. Three ticks of this kind of damage would bypass any such mechanics.
Curiously, the design was bugged, and instead of dealing three times the targeted player's health in damage, it dealt something like 150 times the target's health instead, which was a bit of overkill. The bug was never fixed, because what would be the point: the point was to kill the player anyway.
Different games have different ways to "kill something now" and even a single game can have multiple different ways to do that, as the game's supported mechanics evolve over time. You might think that it would be simpler to just "kill the thing" rather than deal damage like this, but game engines are often complex things. Sometimes when you try to shortcut the process of something taking damage, dropping to zero, then dying with some clever bit of hackery, you discover the game engine fights back and does very weird stuff. In one game I recall a designer attempted to short cut the process and just despawn the thing being insta-killed, and what resulted was the visual representation of the thing disappeared, but the game logic continued to think the thing existed and you ended up with an invisible untargetable unkillable zombie that just wandered around sniping players.