self snip
Last edited:
..snip..
FDev's unfortunate lack of consistent enforcement of their rules doesn't give me licence to ignore them, nor does it mean I'll give up hope that they'll eventually recognize the magnitude of the issue and get around to doing something about it.
SDC doesn't need any credibility for the argument they present to stand on it's own merits.
That's the thing about the good points...it doesn't matter one whit who is making them.
The discussion should be about Frontier's enforcement, or lack thereof, of their own rules; not SDC's credentials.
I'm certainly not a defendant of CL, but to state that SDC have presented a argument with merit is to my mind laughable. Their investigation was 'junk' with a sample size of 1 performing 5 instances of CL over 5 months: this certainly does not pass science 101.
To cite this as 'evidence' is risible and the whole thing feels more to do with self-publicizing propaganda and stirring up controversy that any real attempt at a robust investigation.
I'm certainly not a defendant of CL, but to state that SDC have presented a argument with merit is to my mind laughable. Their investigation was 'junk' with a sample size of 1 performing 5 instances of CL over 5 months: this certainly does not pass science 101.
To cite this as 'evidence' is risible and the whole thing feels more to do with self-publicizing propaganda and stirring up controversy that any real attempt at a robust investigation.
SDC doesn't need any credibility for the argument they present to stand on it's own merits.
That's the thing about the good points...it doesn't matter one whit who is making them.
The discussion should be about Frontier's enforcement, or lack thereof, of their own rules; not SDC's credentials.
The thread has grown far beyond the initial (and not at all rigorous) testing in the opening posts, but we still have people dismissing the issue of lack of enforcement as SDC propaganda. The argument has merit, in spite/because of most of the supporting evidence having nothing to do with SDC.
Frontier rarely punishes deliberate disconnections, explicitly made to avoid legitimate asset loss, and when they do, the punishment lacks the teeth to be a deterrent. That is the argument, that is the issue, and there is more than enough evidence in this and other threads to back this assertion up.
Except that their argument doesn't stand on its own merits.
First, the frequency of combat logging that they "tested" was extremely low. I often have multiple crashes in a single gaming session, many of which require me to task-kill the client. They would need to do their "testing" much better than they actually did for it to mean anything.
Second, that is exactly why you always want to know why any given group is making an argument. They clearly have an agenda to promote and have many reasons to bias their "testing". Taking their "evidence" at face value would just be naïve.
Third, they have admitted to breaking rules in the past when it suited them. That is not "speculation" that is by their own admission. It's a matter of public record on the forums how SDC has behaved in the past and how the group has conducted themselves. Now I'm supposed to suddenly believe that "evidence" presented by SDC is fair and honest? Sorry, but once you lose credibility, you don't get it back.
Except that SDC is not making the argument coherently. They're already starting from the premise that FD "isn't doing anything" about combat logging and acting as if they have "proof" of what FD is or isn't doing. They don't actually know what FD is or isn't doing to address actual systematic combat logging by players. All they know is that their own limited, biased and completely inadequate "testing" didn't produce the results they wanted.
It's obvious that a very low frequency of artificial combat logging is not going to be identified, analyzed or handled the same as someone who systematically and repeatedly engages in such behavior. The did the exact opposite of a "fair" assessment. They started with a conclusion and tried to manufacture "evidence" to "prove" something they already believed to be true and they did it in such a manner that it ended up proving nothing.
Ouch, Bear Grylls style. That takes balls.self snip
Except that their argument doesn't stand on its own merits.
Second, that is exactly why you always want to know why any given group is making an argument. They clearly have an agenda to promote and have many reasons to bias their "testing". Taking their "evidence" at face value would just be naïve.
Third, they have admitted to breaking rules in the past when it suited them. That is not "speculation" that is by their own admission. It's a matter of public record on the forums how SDC has behaved in the past and how the group has conducted themselves. Now I'm supposed to suddenly believe that "evidence" presented by SDC is fair and honest? Sorry, but once you lose credibility, you don't get it back.
Except that SDC is not making the argument coherently. They're already starting from the premise that FD "isn't doing anything" about combat logging and acting as if they have "proof" of what FD is or isn't doing. They don't actually know what FD is or isn't doing to address actual systematic combat logging by players. All they know is that their own limited, biased and completely inadequate "testing" didn't produce the results they wanted.
It's obvious that a very low frequency of artificial combat logging is not going to be identified, analyzed or handled the same as someone who systematically and repeatedly engages in such behavior. The did the exact opposite of a "fair" assessment. They started with a conclusion and tried to manufacture "evidence" to "prove" something they already believed to be true and they did it in such a manner that it ended up proving nothing.
I'd expect to see something like 'We recorded 2,546 discrete PvP encounters over a two month period and observed potential combat log behaviour in 250 of those. Of those 250 instances, 35 involved 7 players who were repetitively observed to experience a disconnect during the encounter.
When I started reading the OP in this thread I assumed it would be multiple clogs per day, attempting to establish that FDev do not take any action under even extreme circumstances (I would be disappointed, but not surprised if this was the case). Then if a datapoint is established beyond which FDev do take notice, try again less frequently to determine the point where FDev ignore it. That would have been interesting to learn. This is just a cynical attempt to make FDev look bad by pointing out a known issue in as salty a way as possible imo.
It's not just their argument, it's an argument that has been going on forever that some of them attempted to bring to the forefront again.
Their agenda, whatever it may be, is irrelevant and you don't need to even look at their evidence to see the core assertion has real merit.
All good counter arguments to SDC's tests, but being able to dismiss their test doesn't invalidate the core conclusion any more than a flawed demonstration of Newton's laws of motion by a third party would invalidate Newton.
My issue isn't with people picking apart the glaring flaws in SDC's testing. My issue is with those who dismiss the whole issue because it was SDC doing this particular test.
Though I only record a small fraction of my encounters, and only retain a small fraction of my videos, I can personally provide video evidence of more than one CMDR deliberately disconnecting without use of the menu timer, multiple times in very short periods. I can also show that these CMDRs either didn't get punished, or that their punishment allowed them to return to Open and continue such behavior in very short order. Other people have similar examples, some of which have been posted in this very thread.
Whatever SDC's agenda, setting the standard of proof so impossibly high that no one has the resources or wherewithal to meet them is at least as disingenuous.
Without help from Frontier's telemetry and logs, the best you are going to get is widely disparate reports, most of them anecdotes, with the rare coherent video that can be tied to an admission of guilt by the accused.
It's not just their argument, it's an argument that has been going on forever that some of them attempted to bring to the forefront again.
Their agenda, whatever it may be, is irrelevant and you don't need to even look at their evidence to see the core assertion has real merit.
All good counter arguments to SDC's tests, but being able to dismiss their test doesn't invalidate the core conclusion any more than a flawed demonstration of Newton's laws of motion by a third party would invalidate Newton.
My issue isn't with people picking apart the glaring flaws in SDC's testing. My issue is with those who dismiss the whole issue because it was SDC doing this particular test.
Though I only record a small fraction of my encounters, and only retain a small fraction of my videos, I can personally provide video evidence of more than one CMDR deliberately disconnecting without use of the menu timer, multiple times in very short periods. I can also show that these CMDRs either didn't get punished, or that their punishment allowed them to return to Open and continue such behavior in very short order. Other people have similar examples, some of which have been posted in this very thread.
Yes.Now that's fair enough as long as were not taking SDC as gospel. However while I agree that it needs tackling, FD have said that they DO act against CL when they feel they have enough evidence, are you suggesting this is a deliberate lie?
Yes.
If you pay attention outside of these forums, all evidence shows that they haven't done anything since around March last year (which strangely coincided with Part 1 of this thread) and then it was merely "stern warnings" via emails. Serial loggers are reported repeatedly, but you still see them in the game week in and week out.
FDev doesn't do anything about it, or the aforementioned serial loggers wouldn't be able to play every week. So, their claim of action is clearly a lie.
Some of these loggers are the very "griefers" you block Stigbob. Check out the description of my player group and what we do. Our members have had other players combatlog on them. Pray tell, which type of players do you think those were?Or you could just laugh at the cloggers for forfeiting in a lame way, and get on with the game.
Yes.
If you pay attention outside of these forums, all evidence shows that they haven't done anything since around March last year (which strangely coincided with Part 1 of this thread) and then it was merely "stern warnings" via emails. Serial loggers are reported repeatedly, but you still see them in the game week in and week out.
FDev doesn't do anything about it, or the aforementioned serial loggers wouldn't be able to play every week. So, their claim of action is clearly a lie.
There was a post in this thread providing around 10 videos of the same guy combatlogging whenever he was about to lose. He still played the game week in and week out after that. There is even a subreddit dedicated to combatloggers, and some of the ones there even admit to doing it in the discussion of their own video. They still play the game week in and week out.Except, again, we are supposed to take your word on this?
i feel like a dog chasing his tail at this point. Circles and circles and getting nowhere.