Screenshots attached. Of course, I was too dumb to take an actual replay of the game before it was too late, but the screenies should demonstrate what I'm talking about (note that they're all PCX files, so you'll need some kind of program to view them).

Right as one of the players in the game lagged out and another left, I noticed that one of my enemy's lings had 0 hp and wasn't dying. I then noticed it attacking one of my lings, which also had 0 hp and wasn't dying. After a little experimentation, the other guy and I found that these lings were immortal and would seemingly never die.

How did we do this??? O_O

Attachments:

It's one of the hacks from an old build of Apocalypse, not really new.

But neither of us had any hacks on (or at least I didn't)... it happened on it's own.

You know, the game saves replays automatically...
maps\replays\LastReplay.rep

Yeah, but by the time it occurred to me to save the replay, I had already played other games .

Even without hacks, such a bug can occur. It could also be unique to that map.

I was playing of Blood Pressure Marathon and there was an Overlord that spawned with 0/1 Hp. Dunno if that's possible with triggers or no. People were also telling others to storm the damn thing if you wanna kill it.

0/1 hp units are possible. Set max hp to 0 and set the secondary box beneath hp to anything except 0. [Thanks Roy, for correcting me]

I'd be curious though if it actually works killing it with storms.

Post has been edited 1 time(s), last time on Aug 10 2010, 6:58 pm by NudeRaider.

Actually, for 0/1 HP, you set the max HP to 0, and it shows the max HP as 1 in-game. Setting the second box to anything but 0 (the default) will set the current HP to 1, ruining the effect. Therefore, the second box must be 0 to have 0/1 HP.

I ran a quick test, and I confirmed that the unit cannot be killed unless via trigger. It can take seemingly unlimited physical damage, stand casually under psi storms, and have feedback spammed on it, all without affecting the unit at all (except feedback burning their energy, of course). Furthermore, the unit is not recognized as damaged, as a medic will not heal the unit, claiming that it needs an injured target. Using the "Modify Unit Health" action also has no effect on said unit.

People are likely just speaking with ignorance, because storm did absolutely nothing, even when I changed Unused Upgrade 10.

Edit: Spawn Broodlings would most certainly kill the unit.

Post has been edited 2 time(s), last time on Aug 11 2010, 12:46 am by Roy.

HP is stored in 4 bytes, but you only can see the last 3 bytes. It is also signed. I do not know how units are treated when they have negative hp (they might be invincible, or they might have a very very large health pool).

If HP is 00 00 00 00, then the unit will never take any damage, and never die due to damage (there may be spells which kill it), as it has 0 health. I am unsure of the possibility to set a unit's HP to 0% (it's possible to make a trigger which says this, but I don't know if it actually runs).

The byte that you can't see is actually the little box in editors. For some reason, SI only allows 1 digit in this box, rather than 3. To put this into perspective, a terran marine has 40 health. As a 4 byte decimal, this value is 10240, which is also the decimal value needed to detect that particular hp in an EUD condition. If we change the terran marine's hp to have a 1 in the little box, the new hp will be 10241. This number can go all the way up to 255 (FF), at which the hp will be 10495.

If we use a unit with 10495 max hp, the GUI in starcraft will report it as having a denominator of 40 health. However, when fully healed, the unit will appear to have 1 health greater than normal, since any value in the hidden byte rounds up. You can also see this in zerg regeneration. When you set a zerg unit's hp to a percentage constantly on hyper triggers, you will see it flash between two numbers. That's because it's being set to a number divisible by 256 (ie 40 health or 10240 hp) and then zerg regeneration adds 4 to that number each frame (ie 41 health or 10244 hp).

That will give the unit 1 hp.

And negative hp units die after receiving 1 hit.

If the game said "Unable to Add Order" at any point during the game, then OrderBufferRape was used.

Very useful for the resource powerups as independent-sized units will also die in one hit with negative HP.

It wasn't created with triggers. It was a simple zergling blood game where a couple of the lings refused to die for some reason. The zerglings didn't start with 0 hp, they were reduced to that and yet still lived.

Then I wonder why you never noticed the Unable to Add Orders message. Because that's the only way that is possible.

I don't remember seeing an "Unable to Add Orders" message. When does it come up?

Someone starts burrowing and unburrowing a unit (or sieging a tank), and it will start saying Unable to Add Order. All the miners will stop gathering, and the entire game freezes for a while.

This enables players to cancel units in production to gain minerals for it, get excessive amounts of drones for cancelling extractors in the making (and minerals), and also all reavers freeze up that shoot scarabs during the maxbuffer, and some units that end up killed while the buffer is maxed, the game won't be able to handle its death at HP 0 and they stay that way and they'll be immortal.

Edit: Also I have no idea where this attached map came from, but someone was looking for it in the Request Map thread...

Attachments:

Well, I wasn't burrowing any of my zerglings at the time, although I don't know about the other players... and the game never froze, I would definitely have noticed that...