Tests

Zerg building with build time of 1 causes it to never finish, and always heal rapidly. Build time of 2 builds as intended.
Zerg and Terran buildings can have an HP of 0. Protoss Buildings will crash with an HP of 0(Nexus).

Build time of 0 will work for Terran buildings(Unless you can somehow select the building before it finishes construction).
Build time of 0 will work for Zerg buildings(will never finish) but crashes if you select it.
Build time of 0 will work for Protoss buildings but crashes if you select it.

Build times of -1(65535?) for all 3 race buildings will cause them to never[edit:take really long to] complete(could use for effects, using AI to create them).

Another note: You can open single player saves in multiplayer by just renaming them, and vise versa.

Post has been edited 1 time(s), last time on Feb 12 2009, 8:26 pm by Heinermann.

? I thought they crashed if you looked at them. I remember building pylons with 0 build time and looking away and having no ill-effects, but if I watched it crashed.

I remember doing that before...

um? I've made build time of 0 on pylons and cannons on Accident, And it never crashed or gave any bugs, the only thing that happened was they spawned with little hp. o_O?

Yeah, but select them in their warp-in animation while the progress bar is still visible. It will crash.

Little HP is because it finishes too fast, the HP generation can't keep up. Also applies to units in build queue.

I know that much xD, But I never tried Clicking on them when there being built o.O?

Can you move the buildings with the -1 build time via triggers?

You should be able to. You would have to use "buildings" or "any unit" instead of the specific unit I think.

I did some tests on the whole "low build time, high hp, units/buildings being made without full hp" problem, and I found that it was predictable. When you make something, it adds hp on a per frame basis, but the game can only handle so much hp per frame. If the amount goes over that per frame limit (I forget what it is) it does the usual overflow, and doesn't read that first bit ( ie... 10001 becomes 0001).