this is all well and good, but I was in a situation where I had to choose one feature over another because I wanted #4 but with a unit being able to spot the target at a distance....Spring.SetUnitCloak
( number unitID,
boolean cloaked | number scriptCloak,
[ number decloakDistance | boolean decloakAbs ] ) -> nil
If the 2nd argument is a number, the value works like this:
1:=normal cloak
2:=for free cloak (cost no E)
3:=for free + no decloaking (except the unit is stunned)
4>=ultimative cloak (no ecost, no decloaking, no stunned decloak)
Would it be a lot of trouble to add an option where: cost, no decloak, no stunned could be set as params for more power use rather than just this value based configuration?