EVE General Discussion

My question is clear, your answers continue to be ambiguous. There is a commonly used setting that allows you to block conversation requests from everyone in the client. So if everyone is blocked, how would you ever suspect such an attack?

I'm asking for some precise clue rather than a glittering generality of "if you suspect..."

If there aren't any then, frankly, your posts about this matter lack any real content...

Scenario:

You're in a fleet of capital ships, which comes upon an enemy fleet. You notice that whenever one of your capitals gets primaried, he disconnects from the game. You hear in TS/Mumble that they were convo spammed. Suddenly this happens to the next person who gets primaried, and the next. Everybody sets their client to auto-reject conversation requests, but the disconnects still happen.

That's one scenario where you could reasonably suspect such an attack.

Edge cases. If it's an actionable item for GMs now, every single dc'd capsuleer is going to be peitioning this and I am shocked that everyone in this conversation doesn't intuitively know this.

If there were some clear indicator, then maybe it would make sense to have it be an actionable offense. But since the option is "leave yourself vulnerable" or "prevent yourself from being aware of it" the options are really lose/lose for players.

That means any reasonable scenario will be petitioned, whether it happened or not.

DoS attacks inolve repetitive pings.

Powering on your bank of routers is not a DDoS, but each router sends out some packets...

[Edit]
Also, let me be absolutely frank here, buoying GMs with dozens of difficult-to-investigate scenarios is probably not what Eve Online needs at this particular time, thank you very much.
[/Edit]

Fair enough, but this type of attack requires multiple attackers and is different than that.

It is most like the type I mentioned. And without a way to detect it, this is a can of worms.

I am not going to keep hammering on this, but this is all not very well-thought out from what I've seen.

I guess there should be a memo and a devblog. People deserve to know.

You're probably missing my point. Spies won't be a source the GMs are going to refer to.

Players can either choose to not block by default, which leaves them vulnerable but allows them to know if they were convo bombed, or they can block by default, which saves them from petty annoyances but doesn't do anything to stop the convo bomb. A spy's knowledge is worth nothing to a GM, who will have logs (lots of them, a tedious amount even, perhaps) to go through in order to correctly dispense "justice" for this "misuse of the system" where everybody happens to press a button at the same time.

If the nuisance is disabled, you have no way to know if you DC because of normal lag or convo bomb lag. This means you would be foolish not to petition if there is a resulting loss.

I'm tryng to say we don't need tons of people petitioning this knowing GM's might reimburse them now or hand out bans or something. It's just going to generate a lot of work in an already-strained area of CCP's operation.

Actually if you read the thread you'd see that I think they need to deal with this server-side.

Then it goes away.

But no. You just do the ad-hominem thing.

Nice job.

A good spy in the right fleet is going to pass on who this is happening to. If that person suddenly drops out, it's not exactly hard to figure out what happened. True that the GM's won't ask the spy, but that wasn't the point in the first place.

It could be proven to see if convo-bombing, even if rejecting is set, still creates traffic on the router.

Just follow the stream in Wireshark and look to see if packets flood in. I bet any corporation with a good plurality can do this.