Reporting Combat Logs and other exoloits

[Ouberos]

A couple of days ago there was a thread from a serial clogger who had been warned about it by FDev.

If FD are now actually doing something about clogging I wanted to know if there is an official procedure for reporting such?

Would it be in game via the report player function or via support with video / log evidence? Perhaps if someone from FD could give some guidelines that would be great.

Please note : I'm not interested in opinions on the validity of combat logging.

 

[Lunchmoney]

Report cmdr button, in game.
Video evidence is not proof. It would just be someone disappearing on you. You don't know why they disappeared.
With lots of reports on the same cmdr FD should start to look at logs and only then will evidence start to form.

 

[RevCaoticFox]

Report option in game. Good luck with results tho, I have an 8 episode series on my YouTube channel, all reported, all still play to CLOG another day. 2015 FD announced their opinion of CLOGGING as being "not part of the game" and "an exploit", yet here we are 2019, and 85% of ppl n OPEN, readily CLOG.

 

[Viajero]

Small typo in the title. Would you like moderators to edit that to “Reporting Combat Legs and Exosuits”?

 

[Ouberos]

Report option in game. Good luck with results tho, I have an 8 episode series on my YouTube channel, all reported, all still play to CLOG another day. 2015 FD announced their opinion of CLOGGING as being "not part of the game" and "an exploit", yet here we are 2019, and 85% of ppl n OPEN, readily CLOG.

I wouldn't say it is that high but yes it is a problem.

In the past we would report in game but I'm curious if there is an official answer and confirmation that Combat logging is now being dealt with.

 

[Ouberos]

Small typo in the title. Would you like moderators to edit that to “Reporting Combat Legs and Exosuits”?

Not really mate, I'm interested in cheats and rule breakers today. As a global moderator has FD given you any guidelines?

 

[RevCaoticFox]

I wouldn't say it is that high but yes it is a problem.

In the past we would report in game but I'm curious if there is an official answer and confirmation that Combat logging is now being dealt with.

It's 85% in my videos. And that's being generous, NOT exaggeration. 1 WEEK of testing, 1 non-CLOGGER

 

[CAPT. Ho Chi Minge]

I would assume that any action taken would be between FD and the player , no other lines of communication is usually par for the course as far as anyone other than the logger is concerned.

 

[RevCaoticFox]

I would assume that any action taken would be between FD and the player , no other lines of communication is usually par for the course as far as anyone other than the logger is concerned.

Until they are seen again by the victim of their cheating. And reported again, and still seen again. Dot dot dot, etc etc etc

 

[Crimson Kaim]

Report cmdr button, in game.
Video evidence is not proof. It would just be someone disappearing on you. You don't know why they disappeared.
With lots of reports on the same cmdr FD should start to look at logs and only then will evidence start to form.

It certainly is. When someone is being shot at and logs out faster than 15 seconds it's a log. The chances that your internet dies any time you get hit by a player is too low to take it into consideration. Log out through menu is permitted and once you have seen 30-40 loggers you get experience and notice the difference between task kill, freezes and DCs etc.

 

[M00ka]

Are we talking about Combat Logging as in pulling the plug or Combat Logging as in using the 15 sec exit button? And how do players know the difference?

 

[JustJon]

Are we talking about Combat Logging as in pulling the plug or Combat Logging as in using the 15 sec exit button? And how do players know the difference?

Well I was under the impression that whether you just pull the plug or properly log to the menu your ship stays in the instance for 15 seconds?

Or when you 'kill your system' do you immediately disappear?

Usual arguments will come out through - consensual PVP and you lose - deal with it.

Non consensual PVP well that's when the fun begins!

 

[Hacker#451563]

Well I was under the impression that whether you just pull the plug or properly log to the menu your ship stays in the instance for 15 seconds?

Or when you 'kill your system' do you immediately disappear?

Usual arguments will come out through - consensual PVP and you lose - deal with it.

Non consensual PVP well that's when the fun begins!

If the player logs out via the menu with the 15 second timer it's not classed as an exploit.

 

[VR SenseiMatty]

Are we talking about Combat Logging as in pulling the plug or Combat Logging as in using the 15 sec exit button? And how do players know the difference?

I guess they're talking about pulling the plug.
If they have a ganking ship and they can't destroy a frozen and harmless exploration ship in less than 15 seconds they must really suck!

 

[Whitehair]

Report option in game. Good luck with results tho, I have an 8 episode series on my YouTube channel, all reported, all still play to CLOG another day. 2015 FD announced their opinion of CLOGGING as being "not part of the game" and "an exploit", yet here we are 2019, and 85% of ppl n OPEN, readily CLOG.

LOL.

Might that actually be '85%' of the people you shoot at instead of '85%' of the people who play?

 

[Aashenfox]

It's 85% in my videos. And that's being generous, NOT exaggeration. 1 WEEK of testing, 1 non-CLOGGER

Can I ask what targets you were choosing and if you were interdicting them or they were interdicting you? And you are saying that you were winning the combat and they left the engagement by ungraceful exit? Not menu log? I find that very hard to believe.

Because there are varying degrees of this, from a newbie trader not knowing that this is frowned upon, just worried about his cargo (I can forgive this), to a murder hobo FDL who interdicts people and then suddenly realises he's having his butt handed to him, and task kills. There are also a load in the middle, so before you label such a massive part of the playerbase 'cheats' I think you need to provide a lot more info about hte testing method and the kind of ships you tested.

Also, 1 week of testing is hardly a large sample but even if we say that's ok, it's also curious how you arrived at 85%. 85 is a semi prime number, it is not divisible by anything except itself, 1, 5 and 17, which means you either tested 6 players (5 CLed and one didn't, and that's not exactly 85% either, but it's close enough that I would give you the BotD), and therefore once again a sample size of 6 is hardly indicative (over a week it's less than one per day, random chance is definitely playing the larger role here). Or you tested 20 commanders and 17 CLed, which can't be the case since you said only 1 didn't CL.

Branding 85% of the playerbase cheats on the apparently flimsy evidence you've provided is borderline libelous and I'm sure, an exaggeration.

 

[Alwayslate]

If there was a wildly applied serious punishment regarding combat logging, we'd see people cry over it already.

 

[Aashenfox]

If there was a wildly applied serious punishment regarding combat logging, we'd see people cry over it already.

There never will be, because in the current net model, it is impossible to differentiate between a genuine disconnection and a cable pull or task kill from the server side.

 

[Brrokk]

It certainly is. When someone is being shot at and logs out faster than 15 seconds it's a log. The chances that your internet dies any time you get hit by a player is too low to take it into consideration. Log out through menu is permitted and once you have seen 30-40 loggers you get experience and notice the difference between task kill, freezes and DCs etc.

It isn't. All the disappearance proves is that the connection between your client and theirs was lost. You have no way of knowing whether they're still connected to the FD server. If they are, they see you disappear in the same way. That's why video from one POV is no proof unless the other player confirms that it matches his experience.

 

[Alwayslate]

There never will be, because in the current net model, it is impossible to differentiate between a genuine disconnection and a cable pull or task kill from the server side.

Doesn't matter. Just check the frequency.