Next Upgrade/patch - Page 15

geoschmo · #**141** January 23rd, 2003, 12:50 AM

4. Changed - When planets take damage, weapon platforms will be destroyed
first. After all weapon platforms are destroyed, then the remaining
units will take damage randomly.

Sah-WEEET!

couslee · #**142** January 23rd, 2003, 12:53 AM

Cap'nq. I know that. I said I re-obsoleted them (made them not obsolete, made them obsolete again).

Nice try at trying to dx this tho.

Puke · #**143** January 23rd, 2003, 12:54 AM

so the 'ANY' type mounts have not been fixed? they still function as 'NONE' type mounts?

geoschmo · #**144** January 23rd, 2003, 01:04 AM

Quote:

Originally posted by Puke:
so the 'ANY' type mounts have not been fixed? they still function as 'NONE' type mounts?

That was fixed in 1.83 Puke. I didn't notice or i would have mentioned it to you.

A weapon type requirement of 'any' will now work for any weapon, but ONLY on weapons. A weapons type requirement of 'none' will work on any component that is NOT a weapon.

Geoschmo

Rexxx · #**145** January 23rd, 2003, 01:54 AM

Quote:

Originally posted by Mephisto:
Version 1.84:
4. Changed - When planets take damage, weapon platforms will be destroyed first. After all weapon platforms are destroyed, then the remaining units will take damage randomly.

Very nice feature.

Quote:

7. Fixed - AI would build multiple system-wide resource modifier facilities in a system.

Great.

Slick · #**146** January 23rd, 2003, 02:17 AM

Quote:

Originally posted by geoschmo:
4. Changed - When planets take damage, weapon platforms will be destroyed
first. After all weapon platforms are destroyed, then the remaining
units will take damage randomly.

Sah-WEEET!

Surely this now means that Troops vs. Troops will be much more common. And as such, Troops against planet capture is now a viable option. Or am I reading this wrong?

Slick.

Puke · #**147** January 23rd, 2003, 02:35 AM

Quote:

Originally posted by geoschmo:
[QBA weapon type requirement of 'any' will now work for any weapon, but ONLY on weapons. A weapons type requirement of 'none' will work on any component that is NOT a weapon.
[/QB]

NOOOOooooooo

so, we still dont have a mount that works for both weapons and non-weapons? so, i have to work around it by giving useless weapon abilities to the non-weapon components that I want covered in the mount? so, strategic combat will likely be assed up as a result.

grrr.

Rollo · #**148** January 23rd, 2003, 02:51 AM

Quote:

Originally posted by Puke:

quote:
Originally posted by geoschmo:
[QBA weapon type requirement of 'any' will now work for any weapon, but ONLY on weapons. A weapons type requirement of 'none' will work on any component that is NOT a weapon.

NOOOOooooooo

so, we still dont have a mount that works for both weapons and non-weapons? so, i have to work around it by giving useless weapon abilities to the non-weapon components that I want covered in the mount? so, strategic combat will likely be assed up as a result.

grrr.[/QB]

hmm, how about making two identical mounts? one using ANY the other NONE..
of course i don't know what you are trying to accomplish.. so i shut up now

geoschmo · #**149** January 23rd, 2003, 03:30 AM

Ok. Puke I see what you mean. Perhaps this was just a miscommunication. What do you suggest? I guess what we need is a third term besides 'any' and 'none'. One that includes every component. I am sure Aaron would be happy to add it, I am not sure anyone has made it clear that is what we were asking for. This is an improvment over both of them being the same.

Geoschmo

Phoenix-D · #**150** January 23rd, 2003, 04:56 AM

Not sure why I haven't thought of this before, but maybe for a patch or SE5.

Why not make the available on/targets field comma seperated lists, like the "family list" restriction added recently for mounts?

Phoenix-D