Where I live in Mexico, though there is internet service, it is probably the most antiquated system still in existence. I live to far from the heart of the city and with the majority of people now utilizing cell phones. There is little to no upgrading of old conventional web service. My best explanation of what I have would be similar to what use to be called in the old days as a "Party Line". There is one major box or something in which everyone in my small neighborhood is plugged into. If and when there are too many of us online at a time. Some one gets bumped off. Thus I experience anywhere from 6 to 18 and more disconnects per a 12 hour online day.
Cheating Vs Combat Logging
Ouch, nasty.
I would recommend you not to play in open though, because i would say that's not fair on other people you might be playing alongside and you may be degrading their experience.
In regards to the main point, FD have said menu exit is not cheating, therefore nothing to really argue about on that matter. People might feel it is cheating, but nobody is going to get banned for it.
I played only in SOLO for a year, moved to OPEN for a month and realized it was happening to often. Thus now I only play in my private or my son's private mode. He's not online nearly as much and is aware of my situation in regards to disconnects. Thus for what ever purpose, Private Mode is in a sense still in OPEN, thus if FDev ever constricts play, I'll still have access.
Why wouldn't Frontier just do what every other MMO with pvp in it do...
If you log out in combat (you have been damaged by weapons within the last X minutes), your ship stays in game, and still faces consequences even if the players client is closed. So if someone really needs to quit because the boss walked into the office, they could do so, even if in combat. Their ship, if being engaged by anyone else would remain and stay vulnerable for X minutes. If you emergency close client, crash, or disconnect and haven't been engaged within the last X minutes, the log out functions as it does currently.
Simple solution, no bans required, people will stop weaseling out of engagements. This would make the Open Play more fun.
If you log out in combat (you have been damaged by weapons within the last X minutes), your ship stays in game, and still faces consequences even if the players client is closed. So if someone really needs to quit because the boss walked into the office, they could do so, even if in combat. Their ship, if being engaged by anyone else would remain and stay vulnerable for X minutes. If you emergency close client, crash, or disconnect and haven't been engaged within the last X minutes, the log out functions as it does currently.
Simple solution, no bans required, people will stop weaseling out of engagements. This would make the Open Play more fun.
Except you can log out using the timer. You don't need to hard disconnect. Same with the launch and forgetting something.
This is really a non-issue. No one is harmed by someone CL'ing. If anything it screams "I quit". FDev can deal with it how they see fit, but I can tell you from recent experience and as someone who plays almost exclusively in Solo, I was playing on Mobius server yesterday and got the server disconnect 6 or 7 times while hunting HGEs. Once I was in the instance about to scoop and got the error. I thought "what if someone looks at my logs, would they think had some exploit going on?"
Then I was playing and there was a thunderstorm approaching. Right during a CZ battle, off goes the internet feed. I have everything on UPS and line conditioning, but I cannot control the incoming feed. It was out for about 5 minutes then right back on. Maybe indistinguishable from a kill switch.
Another time recently I was getting screen locks (happening a lot lately) in station menus, just the time wheel spinning or the buttons unresponsive on the screen. I would log out but even Esc didn't do anything. I had to task kill the game.
This is a program, it does things like this, you have to task kill it. I think if someone reports you for CL'ing and they have video evidence, you better not be in danger of losing your ship and you better not have other reports, but if there's some automatic tell, then the witch hunt will be a problem.
Then I was playing and there was a thunderstorm approaching. Right during a CZ battle, off goes the internet feed. I have everything on UPS and line conditioning, but I cannot control the incoming feed. It was out for about 5 minutes then right back on. Maybe indistinguishable from a kill switch.
Another time recently I was getting screen locks (happening a lot lately) in station menus, just the time wheel spinning or the buttons unresponsive on the screen. I would log out but even Esc didn't do anything. I had to task kill the game.
This is a program, it does things like this, you have to task kill it. I think if someone reports you for CL'ing and they have video evidence, you better not be in danger of losing your ship and you better not have other reports, but if there's some automatic tell, then the witch hunt will be a problem.
Agree with the automatic reporting being a problem.
I used to play Discovery Freelancer and you had to be reported with evidence by another player before they'd even look at it. There would be sanctions if guilty.
I reckon that having all your engineering removed would be a fair disincentive to combat log.
I used to play Discovery Freelancer and you had to be reported with evidence by another player before they'd even look at it. There would be sanctions if guilty.
I reckon that having all your engineering removed would be a fair disincentive to combat log.
I don't agree.
A big part of any game like this is the presumption that everyone is playing by essentially the same rules, and has the same opportunities to influence the game setting.
Cheating to preserve assets, or time, gives the cheater an edge up on legitimate players. It may be minor, but it's there. This sort of unfairness should be strongly discouraged.
None of these are combat logging and it would take an incredible number of coincidences for any rational system to punish someone for unintentional disconnections, especially when most of them provided no in-game benefit.
Automatic logging and flagging (for review, not automatic punishment) of patterns of disconnections are necessary to catch cheating via disconnection in situations where there are no witnesses.
Disconnecting for an in-game advantage in Solo, or when alone in PG or Open, still allows a player's character an advantage they should not have and is still cheating.
I think it only matters in the instance of player versus player. Even then only to that player who is left holding the bag. Otherwise it's really no more severe of a impact than someone slamming a Sidewinder into a planet to get back to the station faster, or to get all the way back to the bubble from Colonia. To me those seem to be much more aggressive. Sure neither one results in saving of the ship but time is an asset. How much money could you make in the time it would take to jump all the way back to the bubble from Colonia?
There's a feature in a game that allows you to block players. If someone combat logs and you just block them. That pretty much ends that problem. Eventually that individual would have no one in their instance because they are known to combat log.
This problem isn't unique to Elite Dangerous, it happens on online sports games all the time where people quit when they are losing and sometimes those games don't register that as a game that was even played. So the quitter doesn't suffer a loss.
Scripting and botting are completely different from combat logging. Calling the two equal or saying they're both cheats it's just minimalizing the hacks.
So the problem of combat logging obviously is related to combat and it seems that the player wants to see the other ship explode, to get some satisfaction from their win. But instead that ship has becomes unresponsive. I don't know if people get more upset because the break in immersion or because of the fact that they didn't get to destroy the other person's vessel, setting them back some assets.
Last edited:
I don't particularly see any difference between someone disconnecting on me in combat, someone hacking to destroy my CMDR's ship with a single shot from a pulse laser, and someone yanking the plug to keep their trade vessel from being destroyed by and NPC or a toaster rack in Solo.
The ultimate result is the same; what should not have been is and legitimate in-game continuity is broken. The basic means is the same as well; it's all a violation of the rules.
I completely disagree.
And that approach is how the scripters are able to continue doing their thing, since why prioritize that over some benign act of panic? Why wouldn't FDev put scripting on the back burner and focus on the much much larger user base that has the ability to CL?
I don't agree with the assertion that willfully disconnecting to change the outcome of in-game events is benign. If anything, the apparent prevalence and tacit acceptance of it would give it a larger overall impact than most other forms of cheating.
Regardless, from my perspective it's all the same issue; a cheat is a cheat no matter how it's done. They should be identified and removed. The same kinds of telemetry collection and review mechanisms should be perfectly capable of flagging both.
So scripting should be handled in the same way as task killing or intentional dropping of the internet connection to avoid ship loss or for any other in-game reason.
So someone with a script sitting in front of a station single shot killing everyone in the instance, or someone who claims first discovery on a system that no one else can reach, or someone who destroys all the ships in a DW2 pack using hacks to both get there and to kill the ships... That person should be treated in the same way as the person who task kills in solo to avoid blowing up in the toaster rack.
If so, this unwillingness to differentiate just means no priority.
And this is odd because all of the concern recently regarding hackers in the game, from the elite PvP crowd, seems to differentiate this from CLing because they say "why you should care" and I simply don't care if someone CLs in Solo. Do you think they do, and is there a push to stop CLing in Solo?
So someone with a script sitting in front of a station single shot killing everyone in the instance, or someone who claims first discovery on a system that no one else can reach, or someone who destroys all the ships in a DW2 pack using hacks to both get there and to kill the ships... That person should be treated in the same way as the person who task kills in solo to avoid blowing up in the toaster rack.
If so, this unwillingness to differentiate just means no priority.
And this is odd because all of the concern recently regarding hackers in the game, from the elite PvP crowd, seems to differentiate this from CLing because they say "why you should care" and I simply don't care if someone CLs in Solo. Do you think they do, and is there a push to stop CLing in Solo?
Last edited:
They can't punish combat logging as cheating, because that would punish the many cases of accidental internet break. They would be forced to examine Combat Logging case by case, due to many complaints, and they would loose a huge quantity of players on a witch hunt.
But this topic has been spoken about so many times. It's up to FDevs to choose the right path, and many good examples have been given. Give it a rest, if you suspect a player of Clog, just add him to the black list, and he will never bother you again.
But this topic has been spoken about so many times. It's up to FDevs to choose the right path, and many good examples have been given. Give it a rest, if you suspect a player of Clog, just add him to the black list, and he will never bother you again.
For those cases, that is what the in-game mechanic via menu logout is for.
Though I've never actually CL'ed, I have both lost connection because of my antiquated internet connection and change the mode when I happen to get stuck in the rack and once when I accidentally prematurely launched.
The RULE states:
"Deliberately disconnecting to preserve one's assets or otherwise avoid in-game consequence is cheating."
If and when one gets stuck for what ever reason in the toast rack for example or accidentally launches prematurely and utilizes the so called "IN GAME Mechanic" as you state, they are by default "Deliberately disconnecting to preserve one's assets". The process of doing such and the process of performing a CL and the reason's for both are exactly the same (preserving one assets). One can argue semantics till the cows come home, but if of the two reason's is cheating, then both are.
You are correct and I couldn't agree more; to me it seems a little less like cheating when you use the menu to logout to escape being stuck in the toaster rack, (or if one forgets to stock limpets and doesn't want to exit the station and re-request docking), but that is just me. In the PvP community, there is no distinction between severing network connection / task killing and menu logging. When other Cmdrs are involved use of any of the above is hugely frowned upon and a bannable offense in a lot player groups.