Spring RTS Engine

Why is it unit have to be onoffable to have radar and/or sonar?

i know i shouldnt put my nose into topics i got no idea about, but first thing that came to my mind was : commander (which is not onoffable i think) :>

I will definitely look at it

activatewhenbuilt?

alternatively set the activation cob/lus call to true on unit creation?

activateWhenBuilt = true,

seems to solve it. Really pisses me off how this change happened. INB4 we cannot test every scenario... if you are working on radar... this is something to test! INEXCUSABLE! Seriously, just because *A is fine doesn't mean shit works!

I thought that radar/sonar et al had been tied to activation status since... well, forever (at least so far as Spring goes)?

Not to my understanding flozi. Still seems kind of odd that it HAS to be tied to activation status.

It's one of those TA-isms. Maybe it wasn't tied before but I think that led to whining by people that they couldn't turn radar towers off.

>:|

I think the reason it hasnt been tackled is because someday someones going to want an on offable metal maker that doubles as a sonar who then complains that the sonar turns off when he turns off his metalmaker or vice versa.

Swap out the function in above paragraph for more realistic scenario etc. On off, what exactly does it turn on and off? Why don't we leave it at the default TAisms and hope nobody ever asks!

I'd quite like to see a generic setup where we can define switches to turn arbitrary sets of components on and off (note I said sets, not individual things, tis more flexible).

I really kinda wonder why on/offable isn't moved to lua based? Seems like that would allow the devs to move the control for such specific things and avoid tag foresting to control this shit.

smoth wrote:I really kinda wonder why on/offable isn't moved to lua based? Seems like that would allow the devs to move the control for such specific things and avoid tag foresting to control this shit.

Because nobody has gotten around to doing it yet.