TLDR; captains being able to see cloaked units is a broken mechanic
so, just ran into this obvious hack. imagine this scenario:
you activate chamelon cloak, travel some 9km (using afterburner obviously), below their spawn and around a massive wall.
2 secs left on cloak, but you’re being shot right as you go around the wall.
the target is a lone engineer captain 3km out. you haven’t yet locked onto him or decloaked.
what is wrong with this picture?
well, for one, there is no micro-locator to be seen… or even within range for that matter. furthermore, your vector of approach would have to have been predicted, and the wall is massive, too large to cover.
you then proceed to tackle and attack the target, closing to within 500m behind him, having travelled over 3.5km. still no micro-locators to be seen, just the captain…
then another tackler shows up from his spawn to finish you off, leaving the captain at 50% hull.
normally, there is no way the captain would have survived had he not seen me coming.
how is that, you ask?
it’s simple really… the game engine reports engine trail locations when an ally is in range.
since i travelled below their spawn, in range of his allies, my engine trail was reported to the captain, who used that information to shoot me right as i came around the wall at 3km out, cloaked…
nice hacks, problem solved?
hey, want to fix? stop reporting client and engine trails if your ship does not take any damage for 5 consecutive seconds in cloak.
this is assuming you don’t report client locations when units are out of range… if you report all client locations then this is inevitable and undetectable.
this is still exploitable, even though it may not have been in this case.
i mean engine trails being reported… hackable…