Combat Logging

Status
Thread Closed: Not open for further replies.
What do you guys consider combat logging?


[video=youtube;F1X00RKdJm8]https://www.youtube.com/watch?v=F1X00RKdJm8[/video]

I once knew a guy who combat logged IRL in a round of golf with his mates. After hitting two bunkers and a pond on the same hole, he took his golf bag in dead silence and walked 20-ish km back to his home.

On a serious note, I have always been a strong advocate for cheating. A win-state or a no-loss state is the only acceptable outcome of a competition. Case in point: Everyone knows who Lance Armstrong is, but unless you're a hardcore fan of Self-Propelled Men in Spandex, the "retroactive" winners are all but forgotten.

I only play in solo... I don't engage in combat, which would make me an easy target. it would be easy to just clog as soon as you get interdicted, but since there's a mode for people like me I'll stick to that. In online-only games that lack Solo but are fun except for the part where you have to interact with other people, I always clog at the slightest risk of losing. If that's not an option, I'll use other shady means of gaining an advantage. Consider it a protest against how multiplayer is ruining games.

As of ED, combat loggers perplexes me. You have the option to either go Solo or join Mobius... Granted, it's not ideal. There should be a proper offline mode as well, but dude, no need to ruin it for those who actually enjoy Open.
 
...

[REDACTED]
CMDR eMKayUSA, you recently joined a player group, I strongly advise you to read the few fair rules set out by that group.
Here they are, in case you missed them... 1 do not attack eachother unless aranged, 2 help each other make credits, 3 do not arrack explorers, 4 defend the home systems, and 5 do NOT combat log against other players (even the 15 second log)
 
Last edited by a moderator:
[REDACTED]

See, this is where I bat for the other camp. I'm in no way shape or form a PvP'er, but I accept that playing in Open carries a small amount of risk. If I get yanked out of SC by another Commander then I either evade or get melted. Because that's the spirit of the game. If I felt the other Commander was a total waste of my time and added nothing to the game, and I thought there was a good chance we'd meet up again, then I may add them to my (currently empty) Block List. But that would be it.

I'm not going to tell people what mode to play in, but I would suggest that a Private group might suit your gameplay better if you feel the need to CL. I do not intend that as an insult.
 
Last edited by a moderator:
Both are combat logging. FDev, allegedly, only cares about the former. If they do actually care, they don't care that much.

I think they care and would penalise it if they could (not menu logging though that's legit), they just cant reliably identify it.
 
I think they care and would penalise it if they could (not menu logging though that's legit), they just cant reliably identify it.

As I understand it they can identify that there's been a non-graceful disconnect (ie a task-kill or loss of network connection), what they can't do is identify the intent.

They should be able to do it statistically, though - if a Commander gets a lot of these disconnects shortly after being interdicted and/or fired upon, then they should be taking steps. Definitely an area that needs looking at.
 
Apparently doing anything other that waiting for your inevitable destruction by a vastly more powerful ship, with no chance of winning if you do fight back, is cheating in some way or other.

Playing in solo or private groups.
Highwaking out of the interdiction.
Using the Menu logout.
Using the block function to avoid that/those players.

All bad.

Being destroyed with no chance at escape or retaliation. Good.

Task killing is cheating, the rest aren't as defined by FD.
 
As I understand it they can identify that there's been a non-graceful disconnect (ie a task-kill or loss of network connection), what they can't do is identify the intent.

They should be able to do it statistically, though - if a Commander gets a lot of these disconnects shortly after being interdicted and/or fired upon, then they should be taking steps. Definitely an area that needs looking at.

That would work, the issue is not punishing people who've done nothing wrong.

My connection is shaky in bad weather, last night was terrible (I've got a lot of free firewood out of it, if I put in the effort with the axe). I've noticed a higher chance of disconnects in combat/station menu's/SC transitions probably due to more information going back and forth (you can see it if you press CTRL+B). So they'd need to work around that to avoid throwing the baby out with the bathwater.
 
That would work, the issue is not punishing people who've done nothing wrong.

My connection is shaky in bad weather, last night was terrible (I've got a lot of free firewood out of it, if I put in the effort with the axe). I've noticed a higher chance of disconnects in combat/station menu's/SC transitions probably due to more information going back and forth (you can see it if you press CTRL+B). So they'd need to work around that to avoid throwing the baby out with the bathwater.
But if the "disconnects" were forming a pattern of being during combat perhaps steps to prevent open play should be taken.
 
I am not sure but I think if you check with any of the committed PVPers you will find that,

Disconnecting the modern is combat logging.

Task killing is combat logging.

Logging out after 15 seconds is combat logging.

Playing in solo is combat logging.

Not playing at all is combat logging.

Not buying the game in the first place is combat logging.

Not owning compatible hardware is combat logging.

Not yet being born is combat logging.
 
I am not sure but I think if you check with any of the committed PVPers you will find that,

Disconnecting the modern is combat logging.

Task killing is combat logging.

Logging out after 15 seconds is combat logging.

Playing in solo is combat logging.

Not playing at all is combat logging.

Not buying the game in the first place is combat logging.

Not owning compatible hardware is combat logging.

Not yet being born is combat logging.

As a dedicated PvPer I disagree completely with your definition of my opinion on combat logging. Logging to avoid combat is combat logging, it's pretty simple really.
 
@ mephisto: Combat logging is when Frontier pulls the plug while you are in a nice combat. Believe it or not but this is the most common combat log that appears in Elite Dangerous:

[video=youtube;9Orl0E7kRe8]https://www.youtube.com/watch?v=9Orl0E7kRe8[/video]
 
What do you guys consider combat logging? Alt tabbing and ending the task? Waiting the 15 seconds then exit the game? Or both?

The first... The latter is fine...

That said, exiting to menu with the 15 second timer:-
1) This should be displayed to all CMDRs in the instance. ie: If I'm exiting my 15 second countdown should be shown not just to me, but to all other CMDRs in my instance.
2) I'd suggest if in that 15s you're fired upon, a further 15s is then added, to make a total of 30s to exit.
 
Last edited:
Status
Thread Closed: Not open for further replies.
Back
Top Bottom