If you're having genuine internet issues, just stay in PG/solo. Of course, this would only apply when the encounter you disconnected in was a player encounter.
Combat Logging Punishment Proposal
If you're having genuine internet issues, just stay in PG/solo. Of course, this would only apply when the encounter you disconnected in was a player encounter.
I have stable internet and our wing had multiple crashes yesterday. Not a huge fan of that idea until FDev can improve their stability.
My internet is notoriously bad sometimes.
When it's acting up, I just stay in solo.
But even then, unless my gaming session is entirely bounty hunting, the random times my internet drops is hardly ever during combat. (Even when Bounty Hunting, there's a lot of "safe" time in between)
And of course, the whole system would reset after some time. The chances of getting 5 disconnects during combat, and being confined to solo for a month is actually quite rare. It's not like you'd get your 5th combat disconnect in 3 years, and then need to spend a month in Solo. Lol
If you don't combat log for a certain time, it'd reset back to the beginning.
CMDR Cosmic Spacehead
Again, this is why I keep pushing my idea from page 3, and many others now.
Doesn't punish accidents.
(Technically it does, you just wouldn't care)
Every time I hear this argument I cringe a bit. Often our internet connections are dictated by location and we have as much right as anyone to play in Open. Good for you that your provider is somehow flawless.
Anyway, I think the trigger should not be automatic. It needs to be initiated by complaints and then followed up by evidence. Combat loggers are annoying, but not so much so that having innocent players caught up in the sweep is acceptable.
I think a manual approach might well be more reliable but if an automated system can be developed it would free up resources at FDev longer term, and have a quicker turn-around.
It's worth repeating that the aim is primarily to discourage it's use, rather than simply to punish it. To reach a point where it's not worth CLogging rather than staying & accepting your poor situation, or perhaps even to encourage players to think before getting into a potential CLogging situation in the first place.
And of course, without unduly penalising the innocent.
I do feel that if a players connection is unreliable they should probably stick to Solo, if that gives them a more reliable connection. But if they want to play with others it's probably not for this system to dictate that.
Not brutal, simply irrelevant in this case, CS:GO in an ultra competitive PVP centered game, basicaly the opposite of what Elite is, so it would obviously have a stronger punishment system for people trying to dodge defeat.
For the automatic system, I liked the idea that after a disconnection (no matter the reason) you would have to log into the same mode (Open/group/solo) that you were in when it happened and if possible, the same instance. For me, that would actually be a qol improvement and it would stop one of the more annoying log methods of going out, coming back in solo, moving to where they want and then going into Open again. Even progressively longer automated timers on that would be good.
Yes I think it's an excellent concept too, and easy enough for all players to understand, which is kind of what I was going for with my simplistic OP.
I've linked to CMDR_CosmicSpaceHead's proposal in the OP, it does seem to be universally popular.
It's a little disappointing to see so few suggestions from the PvP crowd, I know from previous threads how passionate they can be about this topic, this seems an ideal opportunity to make a real difference.
Agreed, exactly like CSGO's system. If you don't have a stable connection and/or may need to quit suddenly, don't join the competitive matchmaking queue. Just stick to the open drop-in drop-out pub modes where it makes no difference.
Way too punishing. Whole swaths of the population would be locked out. Scorched earth tactics will always be doomed to backfire. You do that and there will be people legitimately suing for a refund. Logging is lame and irritating but it's not worth that. There's no "competitive matchmaking queue" for Elite Dangerous. It's not that sort of game.
It does seem closer to CQC than the main game. Is CLogging a problem in CQC?
Right? Oh, I wish they'd give CQC an overhaul. I really enjoyed it but there's not been anyone on at the same time as me for so long I just stopped trying. Off topic over.
Read between the lines with what Riverside said about CQC in mind. I was just making a probably too subtle joke in response to the extreme suggestion.
Most PvP-ers I know play literally around the clock during Fish Betas that have a particular favoured system where everyone is encouraged to cluster. Basically full mods plus full participation equals max happiness.
Then the Fish Beta closes and we're back to a dispersed galaxy with random grind luck trollolo mods. Gawd, Open is so pitifully meh compared to Beta, for a duellist.
I have done this too, it is fun but more MX-5 cheap thrills than Porsche satisfaction of a job well done. I'd favour a permanent Beta server (creative mode), with a cut down set of say 10 systems.
Last edited:
I had sooo much fun last Beta. Missile tests for the win! Kim Jong Un had nothin' on me!
That would be awesome!
It's simple. Just reset the countdown every times the ship or shields take damage from another player, and enforce a 15 second in game presence even if disconnected if player driven damage or interdiction was inflicted. Voila, problem solved - if you are attacking somebody and they combat log, they are as good as dead. Make it only for player inflicted damage to be safe. Boom, combat logging gone forever - people will still log out when they see another hollow square in a system but that's a lesser issue IMO.
Last edited:
Ah yes, the simple solution that everyone who doesn't understand how a peer-to-peer game works comes up with. So obvious, that anyone with any sense would ask why it hadn't already been suggested before they posted it yet again.
And no, I'm not going to waste my time explaining yet again why it won't work.
The problem is that it effects other players. I used to play a lot of online chess, and some people had horrific connections and would disconnect like every game. I didn't play against people with a ping time over 5 seconds (hey man this was in the 90s gimme a break haha)
The colossal irony is that the solution to random PK griefing is and has always been a permanent Fish Beta. plus getting tough on combat logging.
Basically, with a permanent Fish Beta all the good pilots would never trouble Open ever again (however cruel when bored, the good pilots do actually prefer fight to slaughter), and the bottom-feeders who want to harm the weak only would (if they couldn't log) be swiftly killed or at least chased away by the PvE guys.
Win/win.
FDev...?