Disconnect mid-combat.....?

Something to bear in mind.

  • If you intentionally disconnect then according to the Devs that's combat logging and if reported (buy the other players) it could get you into trouble.
  • If you unintentionally disconnect (ISP failure / cat pulls out cables / whatever) then again it's combat logging, but if it happens infrequently you should be OK from the Devs.
  • If you select Log Out (via the menu) and survive the 15s countdown then that's OK. (Though your ship could be hammered during the 15s)
 
Something to bear in mind.

  • If you intentionally disconnect then according to the Devs that's combat logging and if reported (buy the other players) it could get you into trouble.
  • If you unintentionally disconnect (ISP failure / cat pulls out cables / whatever) then again it's combat logging, but if it happens infrequently you should be OK from the Devs.
  • If you select Log Out (via the menu) and survive the 15s countdown then that's OK. (Though your ship could be hammered during the 15s)

This only partly correct.

Intentionally logging out: Combat logging
Intentionally logging out within the 15 seconds: combat logging (just as it was before ... without the 15 seconds)
Unintentionally disconnect: Combat logging (but the devs can see it as a DC and if happening infrequently, one report will not result in a ban)
 
This only partly correct.

Intentionally logging out: Combat logging
Intentionally logging out within the 15 seconds: combat logging (just as it was before ... without the 15 seconds)
Unintentionally disconnect: Combat logging (but the devs can see it as a DC and if happening infrequently, one report will not result in a ban)

Wrong. The 15 sec counter is there for this reason, if you wait out the timer it's a fair logout. You'll only get banished if you consistantly get reported for disconnecting during combat, either by process kill or router disconnect. If you always wait out the timer nothing will happen to you.
 
In other words, because of a severely intolerant policy on the part of FD, the only way to be sure you won't get banned to a 'shadow server' where you will have no impact on the game universe is to play in solo. My experiments with Open are now over and shall not be repeated.
Them's the breaks. FD wants piracy to be a valid playstyle, but it doesn't really work if people can just leave.
Open isn't for everyone and Solo exists for a reason. There's nothing wrong with playing in either, but if you play in Open you should at least accept that PvP is a possibility.

For the record, I don't know if the shadow ban is verified by FD as the punishment. Last I remember, it was a vague "don't combat log or else". I do remember that the punishment was a multiple infractions type of thing, though.
In my own opinion, allowing an unspecified number of "accidental" combat logs with no punishment and then moving on to simply consider repeat offenders as killed upon combat log would be a better system. But I'm sure by now FD has been hammered to near death by "better system" ideas.
 
During my experiments with Open, I was looking for a little PvP to see what it was like. I recognize and accept that it will happen and I entered into Open only when I was willing to court it.

What I refuse to accept, however, is the possibility of being punished for a stupid internet crap-out. Damned if I'll put myself in line for that. I do NOT need any crap from CMDRS who completely pooh-pooh the idea that things beyond my control may happen, and I do NOT need any bans, penalties, or even nasty letters from FD because of a lightning strike or a car running into a damn phone pole. Heck with it. Solo for me from now on... maybe Mobius sometimes.

You won't get punished. Doesn't happen. Not for the occasional internet drop, in any case. You have to be reported loads of times before any ban comes your way.
 
During my experiments with Open, I was looking for a little PvP to see what it was like. I recognize and accept that it will happen and I entered into Open only when I was willing to court it.

What I refuse to accept, however, is the possibility of being punished for a stupid internet crap-out. Damned if I'll put myself in line for that. I do NOT need any crap from CMDRS who completely pooh-pooh the idea that things beyond my control may happen, and I do NOT need any bans, penalties, or even nasty letters from FD because of a lightning strike or a car running into a damn phone pole. Heck with it. Solo for me from now on... ok, BACK to solo. maybe Mobius sometimes.


The part about the internet drops is for repeated times when it happens at such a convenient time
 
During my experiments with Open, I was looking for a little PvP to see what it was like. I recognize and accept that it will happen and I enter into Open at my own risk.

What I refuse to accept, however, is the possibility of being punished for a stupid internet crap-out. Damned if I'll put myself in line for that.

Considering the only information I have is from January, I'm certainly not the expert on the exact punishments. But over on the Suggestions forum, there's a dev sticky;

Hello Commanders!

This is a quick update to let you guys know what we’re looking at regarding the issue of “combat logging”.

For clarity’s sake, “combat logging” is when a Commander ungracefully exits the game (e.g. using ALT + F4 then shutting down the game process) to avoid defeat, destruction and damage.

Commanders might use this exploit the moment they are interdicted or the moment before they are about to be destroyed.

Although this is flagged primarily as a multiplayer concern, the issues (and solutions) apply equally to the single player game.

First things first: we do consider this an undesirable exploit. It’s not “part of the game”.

Because we don’t have an all powerful server running the moment-to-moment game play simulation, there is no infallible arbiter to take control of a player’s ship when they ungracefully exit.

So what we’re doing is logging telemetry that will help us detect when this exploit is explicitly being used.

Right now, all we’re doing (and have already started doing) is looking at and implementing methods of collecting and analysing data.

At some point, however, we will start to take action against Commanders using this exploit. I can only suggest that you should avoid using this exploit if you want to avoid any penalties issued for its use. I'll just repeat: please avoid combat logging - we're taking this issue very seriously.

On a related, but separate track, we’re looking at introducing benefits to Commanders that persevere and stick it out through dangerous encounters, as well as general credit costs and rewards balancing.

I’m not quite ready to talk about these in more detail just now. Obviously though, they can never counter the potential costs of ship destruction, but we want to look at a range of disincentives and incentives both to counter this issue.

I hope this helps clarify our position a little.

I assume this implies that occasional disconnects are forgiven, as long as you stick to the end most of the time. That being said, there's probably a newer dev post about this issue somewhere. I didn't realize it had been so long since this post.
 
I don't trust it. Murphy's law; if it can happen, it will. And it CAN, if something goes haywire with my ISP all of a sudden. They get hit with a weird virus, my router decides to go nuts, a rat chews through a wire JUST far enough to make it seem like it's working but give me random disconnects... No. Not chancing it.

If you trust your connection so little then maybe it's for the best, because I'm talking about LOTS of reports. Think about it. Have you seen ANY posts complaining about I've been banished, my connection dropped, it wasn't my fault? No. Know why? It doesn't happen.
 
I don't trust anything that completely when FD puts out a policy that sounds this unforgiving. And now it sounds like they'll do it in solo too.

My connection isn't bad; I haven't been disconnected in a long time. I just don't trust FD after seeing that little policy statement zxaber quoted. I don't trust that it doesn't happen; I bet that people who get banned in-game get banned from the forums too, so they wouldn't be able to complain.


I doubt that as they don't ban you from the game when you get forum bans
 
Unbelievable! They're going to punish me if I get disconnected in SOLO too many times too?! SCREW THAT! Quit time.

Edit: Ok, I take that back. I'll play until they ban me for getting one dc too many and continue to periodically complain about this junk until then too.

You really really should try and comprehend better what is being said.

Its about consistency. If your router regularly drops, there would be no pattern of combat logging. You would be randomly dropping out both in and out of combat. You're not going to get banned for it.

If you did appear on FDs radar (perhaps if you were in open and getting reported regularly) or their tools noted you were frequently disconnecting, you might get an email from support asking you about your problems (if FD support are proactive).

The problem would occur if you were only losing connection during combat. That would show a pattern of disconnecting from combat that would be hard to ignore.

Would FD take action against someone who regularly disconnected (intentionally) from combat in Solo mode? No idea. If you only play in solo you are only cheating yourself... my guess is they would have a good chuckle at your behaviour in the office and let it pass.
 
Last edited:
Uhh ... Other than having no option to return to Open, what's the difference between Solo and being in a Shadow ban sand box?

How would one know the difference unless FD informed someone?

What am I missing?
 
I don't trust anything that completely when FD puts out a policy that sounds this unforgiving. And now it sounds like they'll do it in solo too.

My connection isn't bad; I haven't been disconnected in a long time. I just don't trust FD after seeing that little policy statement zxaber quoted. I don't trust that it doesn't happen; I bet that people who get banned in-game get banned from the forums too, so they wouldn't be able to complain.

Your forum account isn't even connected to your ingame account, how should they do that?!

On your other issues, calm down, nothing to worry about. I haven't heard of a single reported case were a CMDR got banned to shadow server for combat logging, not in open and not in solo. They even contact and warn you for more severe violations before they take actions.

- - - Updated - - -

Uhh ... Other than having no option to return to Open, what's the difference between Solo and being in a Shadow ban sand box?

How would one know the difference unless FD informed someone?

What am I missing?
Solo and open share the same galaxy, your actions in solo influence the state of the background simulation.
 
Uhh ... Other than having no option to return to Open, what's the difference between Solo and being in a Shadow ban sand box?

How would one know the difference unless FD informed someone?

What am I missing?

From what has been said actions done in shadow ban have no effect on the rest of the players universe, but their actions affect yours I believe. Also depending on how many are banned you wont see anyone else except those that are banned . I am not sure about whether they notify you or not
 
I don't trust anything that completely when FD puts out a policy that sounds this unforgiving. And now it sounds like they'll do it in solo too.

My connection isn't bad; I haven't been disconnected in a long time. I just don't trust FD after seeing that little policy statement zxaber quoted. I don't trust that it doesn't happen; I bet that people who get banned in-game get banned from the forums too, so they wouldn't be able to complain.

Based on this, I think we can all agree it is an INTERNATIONAL CONSPIRACY aimed specifically at ED players with unstable internet connection.

Seriously, don't be all paranoid about this. You will not get banned unless you deserve it.
 
Back
Top Bottom