Reporting Combat Logs and other exoloits

Status
Thread Closed: Not open for further replies.
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.

Punishment can be issued based on reoccurring trends, i.e. does commander x lose connection often when he gets attacked by other players and no other time? If so, shadow ban.
 
I already had the situation, that some people were duelling, i was watching. After a little fighting, both suddenly started to fly off in a straight line, shooting at empty space. Both then were convinced that the other one combat logged. Both of them wanted me to also report the other one for combat logging, as I apparently was their witness.

I was still able to see both. At the same time. I was able to read the chat from both. They did not see each other any more, they were not able to see each others chat. So please, please: can one of those people here, hating combat logging so much, please tell me WHICH OF THE TWO was the combat logger, so i can finally report him?
 
Last edited:
I already had the situation, that some people were duelling, i was watching. After a little fighting, both suddenly started to fly off in a straight line, shooting at empty space. Both then were convinced that the other one combat logged. Both of them wanted me to also report the other one for combat logging, as was their witness.

I was still able to see both. At the same time. I was able to read the chat from both. They did not see each other any more, they were not able to see each others chat. So please, please: can one of those people here, hating combat logging so much, please tell me WHICH OF THE TWO was the combat logger, so i can finally report him?

Neither. This happens to me in pvp practice often (and at any other time, I still get disconnected randomly every couple of hours since 3.3). What happened from your perspective is that they both logged off, this is because one of them owned the instance (the one who got disconnected probably, causing ownership of the insurance to be passed to you or the other guy (probably you)), so when the instance was killed, from your perspective both ships disconnect.

The evidence that both thought the other logged is the proof of this scenario or something similar.
 
Last edited:
Doesn't matter. Just check the frequency.

Punishment can be issued based on reoccurring trends, i.e. does commander x lose connection often when he gets attacked by other players and no other time? If so, shadow ban.

As I say above I get random disconnects still since 3.3. In the last two weeks (4 sessions of pvp practice) I have been disconnected during combat twice through no fault of my own. Would you consider twice in two weeks a trend? I probably would, and in this case, as many others, you'd punish an innocent commander.

I do however agree that serial offenders should be easy to spot for fd.
 
Last edited:

My question was rethorical. I am well aware that it's just one of the many ugly faces of our P2P infrastructure. I just wonder if any of those anti-combat-logging people ever will manage to get to understand this. There are a number of cases, where i am still undecided if they just lack the mental capacity to understand the effects of the games infrastructure, or if they decide to ignore this information in favor of their personal agenda.
 
My question was rethorical. I am well aware that it's just one of the many ugly faces of our P2P infrastructure. I just wonder if any of those anti-combat-logging people ever will manage to get to understand this. There are a number of cases, where i am still undecided if they just lack the mental capacity to understand the effects of the games infrastructure, or if they decide to ignore this information in favor of their personal agenda.

Gotcha. ;)
 
And how should we console players report people? We dont have the option to report them ingame?!
@Silow If someone logs on me, i record it and i message them and they admit in the message that they logged, is that enough proof for you?
 
Last edited:
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.

🤣 I never tire of your posts
 
Whoever bothers with reporting? Frontier never addressed combat logging, so trying to do their job is pretty low. They are creating players that log for sport during combat, since 3300.
We had threads here were loggers said that game is not as important as real life reasons, so they log or menu exit as they please.
Yes ofc a game is not more important than real life, but when they were told that the ship should stay in game during combat even if the pilot logged for x reasons, they didnt even like that, because they dont wanna lose their space pixels, so yea...
 
A Pirate colleague of mine has had the same guy log on him twice in two days. The individual concerned is already listed on the Reddit list.

The 85% statistic might be questionable but the issue is not.

The clogger has been reported in game.
 
My question was rethorical. I am well aware that it's just one of the many ugly faces of our P2P infrastructure. I just wonder if any of those anti-combat-logging people ever will manage to get to understand this. There are a number of cases, where i am still undecided if they just lack the mental capacity to understand the effects of the games infrastructure, or if they decide to ignore this information in favor of their personal agenda.

FDev put mission generating on dedicated servers, which killed board flipping. Things can change. I don't hope for anything anymore, but it doesn't hurt for others to do so.
 
I think it's about time task manager be banned from Windows, so every mandatory online SAAS Darksoul in space wannabe videogame devs can "design" their freeform emergent content.

Who knows maybe in 2020.
 
Whoever bothers with reporting? Frontier never addressed combat logging, so trying to do their job is pretty low. They are creating players that log for sport during combat, since 3300.
We had threads here were loggers said that game is not as important as real life reasons, so they log or menu exit as they please.
Yes ofc a game is not more important than real life, but when they were told that the ship should stay in game during combat even if the pilot logged for x reasons, they didnt even like that, because they dont wanna lose their space pixels, so yea...

There’s been at least two threads in the past week or so were the poster complained about communication from FDEV regarding their frequent disconnects. The one I saw fully admitted to combat logging via disconnect or task killing. I think that’s why Oubs posted this thread. Something’s changed and it suggests FDEV has developed tools to address clogging.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom