ok, but under one condition: no need for confirmation. There are many situations where i just need to leave game cause reality ant dont want to wait jut cause someone needs their pixelated fireworks to feal alive.
Combat Logging
- Thread starter mephisto9466
- Start date
- Status
Whole combat log thing does not compute.
1) you atack someone
2) they aknowlage they are defeated
3) you won
4) wictory dance?
I can understand feal of superiority due to victory over someone. How is it diferent when someone combat logs?
Yes it is
This, this and a million times this. If someone clogs on me, GREAT! I win! I saved a load of ammo, probably some damage, and I get to call them yeller and stuff which is even better than seeing the splosion. People are weird sometimes.
By the way, re: number 4:
WICTORY!
Last edited:
I think if you exit the game - in whatever way - to avoid a perfectly valid in-game situation you simply don't like, then it's a bit cheesy.
It's like you fly a totally poverty-spec ship build which you bought when you couldn't really afford it (guilty lol) then hit the reset switch any time anyone interdicts you. Or you're well-equipped, but take on a bounty target - or any other valid target - that it turns out you cannot handle, so you hit the reset switch.
I play in Solo or a Private group exclusively, however I've only done what might be considered a Combat Log once. My reason? Well, I experienced a game bug while in a HighRes site bounty-hunting. It was the old getting marked as Wanted after attacking a verified Wanted NPC. My wingmate witnessed it, we'd both scanned the target and had been sat for a couple of minutes chatting, deciding whether to attack this bounty or wait for the feds to attack first. We chose to go for it lol. Of course, despite only hitting said Wanted NPC once - and he remained marked as "Wanted" FYI - and barely even scratching his shields, I instantly become public enemy number one, with ALL the local enforcement ships near me (about seven or so) going red and starting to attack. I remember thinking, "urgh, this bug again, better flee" and proceeded to do so, but, despite near full shields my controls froze, and I could do nothing. As this entire sequence of events was triggered by a bug, I exited the game. I consider this single "combat log" to be fine, as I was not involved in a valid consequence of gameplay at the time.
So, that was a perfectly valid combat log which was required only due to events unfolding caused by a game bug. I'd do it again without hesitation - especially with a 20 million Credit re-buy! What's not valid in my view, and can get quite annoying even though we're not PvP, is when my Wingmate takes on a target that's beyond him, beyond us when I had a lesser ship, starts loosing, then bails (exits game) and the attacker then instantly guns for me. Even if we agree on a target which turns out tougher than expected, it's not acceptable to just log out of the game - especially when your team mates stay committed.
Basically, to me, the only valid time to combat log is during non-valid game events, such as bugs - of which there are still numerous ones of course. I've only ever had two deaths in the game - I play super cautiously - and both were due to suspect events in-game.
I recall the first, these were both in the very early days after release, I'd just destroyed an NPC that had attacked me. He was just a cloud of dust - we didn't have the chunks of wreckage we do now. I flew through where the NPC had been a few seconds after his demise and instantly blew up. The game seemed to think I'd hit something quite solid, but there was quite literally nothing there. I was in a fairly well-equipped Viper MkII at the time IIRC.
The second time I died I thought it was genuine, though annoying, I got stuck in an interdict/escape loop. I'd be interdicted, escape - chaff & boost - get back into super cruise then instantly be pulled out again. I could not win the mini-game, despite getting my bar all the way into the blue (a bug, it turned out) and would then be pulled out of SC again. Each time, I'd take a little damage from the NPC Pirate who demanded nothing and just shot me. In the end I died. I reported this encounter on the forums, and it was then I was informed that this was apparently buggy behaviour and that I should have "just exited the game" then gone back in as a valid work-around for the bug.
So, those are my thoughts on "combat logging" based on my own experiences. There have been lots of other situations where a "combat log" would have saved me profits etc. but I let the valid gameplay situation unfold. Sometime I escaped a situation with a chunk out of my hull and less cargo, others I actually turned the tide and either defeated my attacker, or forced them to flee.
Scoob.
It's like you fly a totally poverty-spec ship build which you bought when you couldn't really afford it (guilty lol) then hit the reset switch any time anyone interdicts you. Or you're well-equipped, but take on a bounty target - or any other valid target - that it turns out you cannot handle, so you hit the reset switch.
I play in Solo or a Private group exclusively, however I've only done what might be considered a Combat Log once. My reason? Well, I experienced a game bug while in a HighRes site bounty-hunting. It was the old getting marked as Wanted after attacking a verified Wanted NPC. My wingmate witnessed it, we'd both scanned the target and had been sat for a couple of minutes chatting, deciding whether to attack this bounty or wait for the feds to attack first. We chose to go for it lol. Of course, despite only hitting said Wanted NPC once - and he remained marked as "Wanted" FYI - and barely even scratching his shields, I instantly become public enemy number one, with ALL the local enforcement ships near me (about seven or so) going red and starting to attack. I remember thinking, "urgh, this bug again, better flee" and proceeded to do so, but, despite near full shields my controls froze, and I could do nothing. As this entire sequence of events was triggered by a bug, I exited the game. I consider this single "combat log" to be fine, as I was not involved in a valid consequence of gameplay at the time.
So, that was a perfectly valid combat log which was required only due to events unfolding caused by a game bug. I'd do it again without hesitation - especially with a 20 million Credit re-buy! What's not valid in my view, and can get quite annoying even though we're not PvP, is when my Wingmate takes on a target that's beyond him, beyond us when I had a lesser ship, starts loosing, then bails (exits game) and the attacker then instantly guns for me. Even if we agree on a target which turns out tougher than expected, it's not acceptable to just log out of the game - especially when your team mates stay committed.
Basically, to me, the only valid time to combat log is during non-valid game events, such as bugs - of which there are still numerous ones of course. I've only ever had two deaths in the game - I play super cautiously - and both were due to suspect events in-game.
I recall the first, these were both in the very early days after release, I'd just destroyed an NPC that had attacked me. He was just a cloud of dust - we didn't have the chunks of wreckage we do now. I flew through where the NPC had been a few seconds after his demise and instantly blew up. The game seemed to think I'd hit something quite solid, but there was quite literally nothing there. I was in a fairly well-equipped Viper MkII at the time IIRC.
The second time I died I thought it was genuine, though annoying, I got stuck in an interdict/escape loop. I'd be interdicted, escape - chaff & boost - get back into super cruise then instantly be pulled out again. I could not win the mini-game, despite getting my bar all the way into the blue (a bug, it turned out) and would then be pulled out of SC again. Each time, I'd take a little damage from the NPC Pirate who demanded nothing and just shot me. In the end I died. I reported this encounter on the forums, and it was then I was informed that this was apparently buggy behaviour and that I should have "just exited the game" then gone back in as a valid work-around for the bug.
So, those are my thoughts on "combat logging" based on my own experiences. There have been lots of other situations where a "combat log" would have saved me profits etc. but I let the valid gameplay situation unfold. Sometime I escaped a situation with a chunk out of my hull and less cargo, others I actually turned the tide and either defeated my attacker, or forced them to flee.
Scoob.
Just think about menu logging like this:
The victim is charging his frameshift drive to open a wormhole to the Main Menu dimension and the only way to stop him is to destroy his ship.
I dare FDEV to make an in-game animation for this.
The victim is charging his frameshift drive to open a wormhole to the Main Menu dimension and the only way to stop him is to destroy his ship.
I dare FDEV to make an in-game animation for this.
Just think about menu logging like this:
The victim is charging his frameshift drive to open a wormhole to the Main Menu dimension and the only way to stop him is to destroy his ship.
I dare FDEV to make an in-game animation for this.
It's been suggested before that initiating a menu-log should simply create a "high wake" event in-game.
If FDev implemented this, nobody'd even know that anybody was menu-logging so they'd have no reason to complain about it.
Show an explosion instead, everyone's a winner.
Unless they used a Wake Scanner
That's one of those suggestions that really should be ridiculous, and yet I can't actually find a fault with it..!
Combat logging is when CMDR Combat stops playing.
In my capacity as resident cynical old git, I am forced to disagree. [sad]
After 10 seconds thinking about this, it occurs to me that somebody would be able to shoot at a ship, the other ship could menu-log and the 1st ship would then be able to scoop a heap of stuff from the debris.
Rinse & repeat as required.
Course, there could be an explosion with no debris but then we'd be in a similar position to the thing with wakes.
Maybe they should change the game so that there's only, say, a 50% chance that wakes are scannable then you'd never know for sure.
Alternatively, make it so destroying a ship doesn't always cause material drops for the same reason.
Do Commanders' ships drop stuff? I was under the impression they didn't, but then I've never actually shot at another commander.
LOL, that's absolute rubbish.
One is menu logging - all above board and acceptable.
One is Combat Logging - not acceptable and cheating.
Yours Aye
Mark H
It wouldn't so much someone calling a name or two. It would be more along the lines of freedom of association.
If I had seen a post like the now removed one first, my responses in this thread may have been different:
https://forums.frontier.co.uk/showthread.php/389075-Dueling-practice-Been-searching
Not sure what I would have done, but politely declining is certainly not out of the question.
And there is the player group rules I am a part of, which the poster just joined:
And since the post has been redacted, there is at least a change of heart on the "I don't care what anyone thinks". Hopefully there is a change of heart on the core issue as well.
Last edited:
LOL, no it is not rubbish.
Combat logging is logging out during combat to avoid the consequences of combat.
FDev doesnt get to define common gaming terms.
Combat logging happens in a bunch of different online sandbox games, DayZ, Rust, Ark off the top of my head.
FDev does get to define the combat logging they care about.
LOL and cheers.
But they do get to define what is and isn't cheating in their game. They've said that menu logging isn't cheating.
It's not cheating, but players who menu log will still be labelled as a clogger by the community.
True (and justifiably so if they're doing it deliberately to get out of combat) but it isn't, technically, cheating if FDev say it isn't.
Powderpanic
Banned
If you LOG out of a COMBAT situation.
You COMBAT LOG
Whether you punk out by pulling the cable or hitting the 15 second timer, end result is that you couldn't deal with the situation you were in and probably shouldn't be wasting others time by playing in Open.
But we know that players log against NPC's as well, so its not just an Open only problem.
Daft really where its almost impossible to die in ED if have half a clue what you are doing. The skill requirement to succeed is already so painfully low.
You COMBAT LOG
Whether you punk out by pulling the cable or hitting the 15 second timer, end result is that you couldn't deal with the situation you were in and probably shouldn't be wasting others time by playing in Open.
But we know that players log against NPC's as well, so its not just an Open only problem.
Daft really where its almost impossible to die in ED if have half a clue what you are doing. The skill requirement to succeed is already so painfully low.
- Status