How did we get here?
Late last year, we posted the results of our
investigation into FDev’s actions on combat logging and found, unsurprisingly, that they were doing nothing. The project had two phases:
* Phase 1 involved reporting a bunch of combat logs while providing the videos for them and seeing if they were ever watched. None of the videos were watched, but we learned that
FDev can apparently figure it out using “internal methods”. This wasn’t going to cut it on its own, obviously.
* Phase 2 included multiple SDC members combat logging on each other with video evidence and proper tickets being submitted. No accounts received any warnings from FDev
What we found was that while telling the community they were punishing combat loggers, they were actually doing nothing at all. FDev responded to the post predictably, assuring everyone that they *totally do punish loggers*, but that they
messed up and didn’t follow the process for these specific combat logs over the course of 3 months or so. Shocking.
Obviously, we were still incredibly skeptical, despite FDev’s assurances that the process would be followed in the future, so we decided to test them again.
Before we move on to our new investigation, I think we should go over what combat logging is, as well as why it’s bad. I’m going to shamelessly lift from the previous post here:
What is combat logging?
Combat logging is the act of forcefully quitting (by either program task-kill or forced internet disconnect) the game while engaged in combat with another player.
Frontier has clarified this act as an exploit, and a bannable offense.
Combat logging to the main menu/desktop via the 15 second timer is a different matter and discussion to be had entirely. Currently, this action is confirmed by Frontier as “legitimate”, and as such is not being addressed in this post.
Why is combat logging bad?
Aside from being classed as exploiting by Frontier themselves, combat logging is bad for the game (and gameplay experience) of both the exploiter and the victim. Not only does logging deprive both players of meaningful interaction in game that is vastly empty and void of a human element, but it stifles the rare emergent experiences that make the game more than a sterile grind.
Not everyone considers being attacked by another player, often for no reason - and Role Play doesn't really cut it, because not everyone engages in Role Play, and not everyone desires to include everyone in their own Role Play. Calling this a "meaningful interaction" is a farce at best. If my first encounter with someone is them opening fire on me, you can bet your last breath I'm not going to desire another encounter with them. A meaningful interaction begins with Comms - send me a message. If I don't reply, then one of three things have happened:
1. You messaged me while I was away. This happens from time to time, usually at a station. I probably got up to use the head. Sorry, but I'm not going to log off for that. You can wait for my pad.
2. I was busy doing something more pressing than reading my comms. I'll likely reply when I have a minute.
3. Your message was written as if by an 8-year old, in txt tlk, included numbers substituted for words, or was not in a language I speak. I will not acknowledge txt tlk or number-substitution. If you communicate in this manner, you're just not someone with whom I desire to communicate. If your transmission was not in a language I speak, I may need a few minutes to run it through a translator and find an appropriate reply.
One person's Meaningful is another person's Annoying. But let's continue.
Furthermore, the very nature of risk and reward is upended (a fundamental aspect of any game) because the combat logging party is never faces any risk of loss. Because the combat logger faces no negative consequences for any action, non-combat loggers must shoulder the full—and completely asymmetrical—burden of risk for any interaction: this disincentivizes meaningful PvP gameplay in a game billed as a space MMO.
Meaningful again - but PVP is the most meaningless form of engagement Elite has to offer. There is zero reward, outside of Power Play, and even then, there are limits on this. If the target is of a completely foreign power operating in foreign space (A Duval supporter operating in Rui space) and is attacked by a Grom supporter - this earns zero Bonds, is worth zero merits, and is a waste of time. There are no stats for PVP kills. They award no cargo, no materials, nothing. It really is a complete waste of time. Now I do understand this is how some people want to waste their time - after all, that's why we play games, to waste time. But not everyone wants this, and this is something the PVP community just refuses to get. Yes, people might be playing in Open, and yes, anyone can be targeted, but that doesn't mean they want to be targeted.
And then, we have the lowest of the low - those PVP players who "invade" non PVP Private Groups. These folk should not simply be banned from the Private Groups, they should be banned from Elite entirely. They have no business engaging in this sort of activity. They are not wanted there, their actions are not welcomed there. This is a bigger offence than Combat Logging, and will never garner any sympathy from me if someone engaging in this is combat logged upon, nor should any action ever be taken against the combat logger in this situation - instead the combat initiator should be banned for their activity. Let's continue.
Prime examples of gameplay styles that are hard-countered by combat logging include:
* PvP piracy
* Powerplay undermining defense/attacks
* Inter-faction warfare
* Player bounty hunting
* Hunting newbie-killers
* Blockades
* System protection
PVP Piracy is certainly a legitimate play style, however it is also one with the least number of viable options to enforce, and largely used as an excuse as well. Since destroyed ships yield no cargo, actively firing on a ship with the intent to destroy it negates any possibility of piracy. Since there is no way to actually "hold" someone and hatch-breaker limpets are either countered with some reliability by Point Defense systems, or produce random-at-best results, these are not usually a Pirate's first option.
Power Play Undermining/Defense Against Undermining: Again, a fully legitimate activity, when done within the confines of what constitutes Undermining and Defense. And not everyone who plays is involved in Power Play, and not every Power Player is interested in engaging in combat - I've involved myself in Power Play on a few occasions, but not because I care about any specific power - I'm a module tourist. I run fortification for my merits, and when I'm done I move on - either to the next power for the next module, or I simply quit Power Play and resume my regular activities.
Inter-faction Warfare - This boarders on an Excuse more than anything else, since no one can really JOIN a faction. How many player-controlled SDC ships will show them as part of SDC when scanned? How many players will show Torval's Shield when scanned? That's right, none of them, because we cannot actually join a faction. So this easily becomes a convenient excuse, and with no way to back up anyone's actual claims - Oh, you're supporting the Peoples' Right to Choose Party of Some Obscure Sector, and shooting at anyone who opposes them? Well, I support the Peoples' Right to Choose Party too. Or do I oppose them? You don't have any way to really know, except to rely on my honesty, and I will honestly tell anyone exactly what they want to hear if it works to my advantage.
Player Bounty Hunting - With player bounties capped, this is also a boarderline excuse. Are you really going to hunt me over that pitiful You-Shot-a-Skimmer bounty or that 400 Cr missed shot bounty? If so, you may want to rethink your career path.
Hunting Newbie Killers - Many who cry out the loudest against combat logging are these same newbie killers anyways. They get no sympathy either. And while I certainly salute anyone who would put their time in to bringing these folks to justice, let's face facts - it's not even going to slow them down.
Blockades - Since there are more than one mode of play, these are completely meaningless and laughable at best. And since there is never any "official" backing for these - no faction offering missions to prevent traffic from entering a station or system, this falls into the realm of imaginary gameplay and excuse.
System Protection - See Blockade.
What does Frontier claim to be doing about it?
After much consternation and discussion involving the relative legality of combat logging with the devs, community, and community managers,
Frontier ruled the action of combat logging to be “exploiting” and as such is punishable by shadowbanning offenders (a “shadowban” is a client restriction preventing them from accessing “open play,” which is the online mode with other players.) After this ruling, Frontier has encouraged the reporting and documenting (usually with a YouTube link and supporting chat screenshots) of CMDRs engaging in exploiting. This reporting is done via the support ticketing system, and is usually accompanied by confirmation from Frontier that they have received, and are reviewing, the case of exploiting:
they have a stated response time of “usually within 48 hours” for reviewing tickets and supporting documents related to the case.
In the previous post, some commenters brought up some great criticisms of our methods. One that stuck out in our minds was that our process was too randomized. Nearly every reported log came from a different account, so if it was the first offense for all of those, maybe FDev wouldn’t action them at all.
I'm a bit more surprised that the very notion that setting up pre-arranged combat logging to claim "oh look, an offence (that I knew about, that I arranged in advance)" might not stick out the minds of the folks at Frontier and cause these reports to be dismissed out of hand. It's almost like calling the fire department and telling them "I'm setting my house on fire." and then getting upset when they don't show up to put it out.
The new plan
Given the shortcomings of our previous plans, we put the lone SDC brain cell to use to establish as fool proof a plan as we were capable of forming:
* A secure alt would combat log multiple times on multiple different players
* All combat logs would be recorded from the aggressor’s perspective, from interdiction through the in-game report after the combat log
* An additional ticket would be opened on the FDev website, and a short description of the events would be provided, along with the video of the incident
Following this procedure would ensure multiple tickets submitted for combat logging, which would establish a pattern of behavior for this account. The “logger” account was active, participating in PvE activities like trade CG’s and exploring. The account was purchased in June 2017, and was played as a normal account for this timeframe. Currently, the account has the following stats:
* Assets: 87 mil
* Combat/Trade/Explorer rank: Novice/Broker/Pathfinder
* Farseer/Elvira/Blaster unlocked and upgraded to G5
* Ships owned: AspX, Viper Mk3
A total of 5 combat logs were recorded over the course of 5 months. We did this to simulate what we felt a real player would do. No one combat logs 10 times in a week, they space it out when they run into PvP activity.
*
Ticket from combat log #1
*
Ticket from combat logs #2 & 3
*
Ticket from combat log #4
*
Ticket from combat log #5
In summary, what we have here are 5 different clear combat logs done from the same account over a length of time, which should be crystal clear to FDev as such. All logs were task-kills and were reported minutes after they occurred.
What we found
Frontier is still doing
literally nothing about punishing combat loggers. An account that had 5 clear task-kills received no punishments, no account limitations, not even a single warning letter.
This is now the 2nd time we have caught Frontier red-handed lying about their procedures surrounding this exploit, which has existed since game launch and has still not been fixed. FDev’s continual refusal to punish combat loggers is an absolute disgrace to the playerbase of this game. At this point, we can only assume that Frontier does not punish combat logging at all, either because they can’t detect it or because they don’t want to.
FDev, be straightforward with us. If you don’t care about combat logging, say so. It will save people a bunch of time if we don’t have to submit tickets for this stuff every time we see someone cheating. Instead, what you’re doing is undermining faith in yourselves, because you’re telling people to report exploiters because you totally do punish them while taking those reports and tossing them in the garbage can.
See above regarding the fire department. This is basically the same plan as the previous plan. Ever hear of insanity being defined as doing the same thing over and over, expecting different results?
In short, we all know what the real solution here is, but it will never be implemented - a Toggle PVP On/Off flag, one that cannot be changed in combat and requires a three-minute warm-up/cool-down period. This would solve the problem universally, as those who did not wish to engage in PVP could not do so, nor could PVP be forced on someone who does not wish to engage in such a manner.
But Frontier isn't going to do this, and this is going to remain a PVP-only problem from now until the end of the game.
Finally, given there are too many simple ways to cause a disconnection that even the most dogged investigation would reveal nothing more substantial than "connectivity was lost", there will never really be any completely fair way to arbitrate this. Add to this Elite's already less-than-stable intra-player P2P model, and you get exactly what we've got - a situation with no easy solution, save one: replacing the simple vanishing of a ship with a ship explosion - then no one is any the wiser as to what just happened.
