[AzunaRiceBoy]

It would have gone 2 ways If you see in Reed point of view.

[Tedgp908]

Ok. Let’s first start with some terminology.

“DOS” = Denial of Service Attack. Basically someone overwhelms a server with the requests causing lag. This aren’t dangerous because any good data center will automatically filter these attacks out.

“DDOS” = Distributed Denial of Service Attack. This means multiple DOS attacks are coming from different IP’s or Locations. These are the ones that actually can fuck people’s shit.

Both of these attacks are extremely common. Bots exist trolling IP’s down the list hitting them all, in attempt to cause damage. These attack might have zero connection to anyone who has ever played on the server.

Not that the terminology is over with let’s discuss this. An individual(s) joining the server and lag starting is in no way proof that a user is attacking the server. The user doesn’t have to be on the server to actually do any of the above mentioned attacks. You have theorized that this user attacked the server with the proof of this user joining and lag existing mean nothing. If you want I actually ban someone for anything, you need proof that they are breaking the rules.

So here is how you actually prove someone is DOSing the sever. You run an audit of all the IP’a connecting to the server (NFO has this as a built in feature) you locate the IP of the DOS(S)er. It’s really obvious who it is. Then look at the IP of the the accused user. If they are equal BOOM this user is for sure the attacker (if an attack was happening at all). They have to be dead equal. Not any off this “oh it’s in the same region” bullshit.

Edit: Gametracker messing up would have nothing to do it with. Ganetracker in this case hits the SteamAPI, just like the load screen I made does.

[Alcoholic Femboy]

Ok. Let’s first start with some terminology.

“DOS” = Denial of Service Attack. Basically someone overwhelms a server with the requests causing lag. This aren’t dangerous because any good data center will automatically filter these attacks out.

“DDOS” = Distributed Denial of Service Attack. This means multiple DOS attacks are coming from different IP’s or Locations. These are the ones that actually can fuck people’s shit.

Both of these attacks are extremely common. Bots exist trolling IP’s down the list hitting them all, in attempt to cause damage. These attack might have zero connection to anyone who has ever played on the server.

Not that the terminology is over with let’s discuss this. An individual(s) joining the server and lag starting is in no way proof that a user is attacking the server. The user doesn’t have to be on the server to actually do any of the above mentioned attacks. You have theorized that this user attacked the server with the proof of this user joining and lag existing mean nothing. If you want I actually ban someone for anything, you need proof that they are breaking the rules.

So here is how you actually prove someone is DOSing the sever. You run an audit of all the IP’a connecting to the server (NFO has this as a built in feature) you locate the IP of the DOS(S)er. It’s really obvious who it is. Then look at the IP of the the accused user. If they are equal BOOM this user is for sure the attacker (if an attack was happening at all). They have to be dead equal. Not any off this “oh it’s in the same region” bullshit.

Edit: Gametracker messing up would have nothing to do it with. Ganetracker in this case hits the SteamAPI, just like the load screen I made does.

^ what he said.
The server also lags pretty bad randomly also so I mean only way to prove that he's the attacker you have to do what Ted said and check with NFO.

[Avi]

Not saying this is what they're doing, but a lot of current hacking clients have exploit finders that allow people to lag out the server while they are connected to it (usually by spamming net strings). It lags out the server until they stop it or are kicked, and they can retoggle it if they rejoin.

[Gabe]

Unbanned for lack of hard evidence