Page 2 of 2

Posted: 06 Jan 2007, 03:30
by EXit_W0und
f you're talking about unit class (air, sea, land, building, hover, othercrap) then it is a subcatagory of class restricting...
I was talking about both - currently you can disable a particular unit in the lobby but i haven't seen any options to have a numerical limit on each one.
Categories could even be convenient for quickly setting up limits rather than clicking each unit.

Posted: 06 Jan 2007, 17:50
by KDR_11k
I hope the metal and energy sliders get killed or at least disabled by default... Just use the commander's storage values.

Posted: 06 Jan 2007, 20:04
by BlackLiger
KDR_11k wrote:I hope the metal and energy sliders get killed or at least disabled by default... Just use the commander's storage values.
They were in OTA, so it's unlikely. What it needs is the option to save and load presets...

Posted: 07 Jan 2007, 10:59
by KDR_11k
"It was in OTA" is not a sufficient reason to not axe them.

Posted: 07 Jan 2007, 11:07
by SwiftSpear
Hence we see the impending rational behind the OSRTS project.

Re: CountTowardUnitLimit=0

Posted: 07 Jan 2007, 14:42
by Lippy
Back to the original topic:
Argh wrote:Very simply, I'd like a tag that causes a unit to not be counted towards overall unit-limits. The units would also need to not be counted towards victory conditions (i.e., if the game is set to non-ComDeath = End, and all units that have CountTowardUnitLimit=1 are dead, then you win).

This would allow for the creation of several new types of gameplay.
I think a more useful fbi tag would be one where you specify the amount that is counted towards the unit limit for each instance of that unit. E.g. CountTowardUnitLimit=10 would add 10 to the unit limit for each unit. As well as satisfying your needs (CountTowardUnitLimit=0), it would also open up a lot of different opportunities in the future.