Original Post — Direct link

So over the last few weeks I've heard people in my group talking about how some ratters would immediately initiate warp when a cloaky hunter entered their site. At first I thought it must just be a coincidence, CCP wouldn't make a mistake as big as that, would they?

But the reports persisted. Today, it finally got my curiosity up.

Expecting a long evening of testing, I grabbed a drink, turned on some music and got started. I logged into sisi, opened up all kinds of debugging tools and got ready to start playing around.

I went into a system with empty local, a safe with nothing else on grid. A pod on one client and a cloaked bomber on the other. Pretty simple setup.

First thing I did was to open up Eve's internal log viewer. I didn't expect anything from it, it couldn't be that obvious right? But I had to start with something, so I went with the easiest thing.

Well it turned out that the easiest thing is often enough. When I initiated warp on my cloaked hound it generated a bunch of messages in the Log Viewer of the other client

. This happens every time any ship initiates warp on your grid, even if that ship is cloaked.

Here's a sh*t quality video demonstrating it.

This is obviously a big deal. The only way you can prevent people from making exploits that detect cloaked ships is to not send any information about them to the client.

While I haven't actually found a way to detect a cloaked ship entering your grid (sisi went into downtime a couple of minutes afterwards), the fact that the client receives information about that makes me think that there are other ways to detect cloaked ships.

For now, try not to warp around when you're trying to stay hidden.

To CCP: I have created a bug report about the issue, EBR-181741. Pls fix.

External link →
over 4 years ago - /u/CCP_Falcon - Direct link

This is something we're currently looking at, thanks for the additional heads up :)

over 4 years ago - /u/CCP_Falcon - Direct link

Originally posted by [deleted]

I think a response needs to be a bit more significant than, “...something we’re currently looking at”. We need a more complete reply as to what happened, why it happened, who or what is responsible, and what is done to remedy the problem.

No, you don't.

What you need to know is that it's been brought to our attention, and it's being addressed by the development team.