Spring RTS Engine

As I understand then the cloaked unit is revealed when standing too close to enemy units collision/close sight cylinder not a sphere and thats why planes uncloak units that they directly fly over!
IMO this should be changed to react to spheres cause many ppl make fighters patrol around their base and it is impossible to get a cloaked+stealthy unit through that defence without noticing(well counting on patroling fighter count). Well in BA and CA the intrusion system is already enough!

Discuss -

I think it'd be cool to have a tag like sensecloak or something, so taking BA as an example, fighters wont see anything where scouts and radar planes will.
though its not like BA has that many cloaking units to begin with.

why would you need many cloaking units..

Sensecloak=0 Detected as Cylinder?
Sensecloak=1 Detected as Sphere?

That might be interesting... could it be done?

0 should probably disable sensecloak altogether, 1 should be default, 2 spherical.

Well, you know I'm no coder!

I'm not sure if Sensecloak is the best name for the tag, however...

"seeCloakedUnits"?

(I have a patch written, just need
an acceptable name to sign it off.)

seeDeadPeople=1;

probably 'DetectCloaked'.

A tag to just set it as yes/no would be best, the sphere stuff is probably way too complicated.

Saktoth wrote:probably 'DetectCloaked'.

A tag to just set it as yes/no would be best, the sphere stuff is probably way too complicated.

I figure the Sphere stuff is easier than the cylinder. You set a point of origin and a radius. Bam.

Cylinder is the same, except you project everything on a 2d plane. Both are easy TBH.

You don't set a height? Damn.

Cloaking is a mess in spring....

I can't imagine a mod that would use cloaking very proactively, it's just too awkward and improper the way it currently is.

Cloaked units can't get close to other units or they will be seen, yet unless they are meticulously micromanaged they will trudge right on into another unit in plain sight. Developmentally the systems for anticloaking are extremely hardcoded and those which are less restrictive use ridiculous workarounds (YAY, GIANT RED BLIPS FILLING THE ENTIRE MAP!) Radar basicly see cloaked units unless they are also "stealth" which presents a myriad of other problems. Basically, mod developers have very very little control over LoS and unit sight right now, with the exception of the cloak system, which is restrictive ass at best.

Only the standard behaviour for cloaking is hardcoded, you can get/set CLOAKED in BOS and of course use Lua, if you want you can e.g. have an "uncloaker" gadget that makes all cloaked units uncloak if they get closer than a certain value to a detector.

Do they still decloak if they get close to a unit? Of course, it's probably possible to set the uncloak radius rediculously small...

i havnt read all the posts here but i always assumed that min distance was based on a collision sphere, not XY coords.

if not changing it to work on a collision-sphere or point-distance would be preferable, however this would take longer too calculate.

quickfix would be too have an fbi tag along the lines of candetectcloaked

this would be a good fix but as for how difficult it would be too impliment i dont know.

D.R

Longer to calculate? That's one mult and one add. Adding that fbi tag would take much more power. And even then it's nothing compared to the parts of spring that are actually computation heavy.

Only the standard behaviour for cloaking is hardcoded, you can get/set CLOAKED in BOS and of course use Lua, if you want you can e.g. have an "uncloaker" gadget that makes all cloaked units uncloak if they get closer than a certain value to a detector.

CA's sniper can fire while cloaked, etc.