Oh good, another "I'm right and everybody who disagrees is wrong" warrior. We haven't had one of those in, oh, five minutes at least...
Opinions on combat logging
- Thread starter mephisto9466
- Start date
Oh good, another "I'm right and everybody who disagrees is wrong" warrior. We haven't had one of those in, oh, five minutes at least...
15 seconds with lasers lmfao, have you ever even shot at a ship before?
Here's what you can do instead, reverberating cascade torpedoes and armour penetrating rail guns. IF you're good enough, and that'll take at least 20 seconds.
[video=youtube_share;lXO3KMjND6I]https://youtu.be/lXO3KMjND6I?t=29[/video] TTK 31 seconds on a Cutter without shields.
You CANNOT kill someone in under 15 seconds, and you are LOGGING OUT DURING COMBAT. That is combat logging.
Give me a valid reason that isn't based around saying "logging out during combat isn't combat logging because I'm logging out through the menu." By definition, it's logging out during combat. What does that mean? Combat logging. Wow who'd have thought???
Have fun thinking the earth is flat. Didn't say he can't post, told him to put his money where his mouth is. Quite the difference.
You are assuming the intent of the 15s timer is to guarantee death in any given combat setting.
As for menu logging in a combat setting being combat logging, errm - nope, FD has expressly clear.
Show me where FD explicitly said logging out via the menu isn't combat logging (which it is) and I'll believe you, and never make a post about it again.
Link
Essentially, due to menu logging not being able to guarantee no damage being incurred it is not considered combat logging.
Last edited:
Oddly enough I agree. If you're menu logging during combat in order to avoid combat then yes, in my eyes that's a combat log. At the very least it's against the spirit of the game.
If you're logging off during combat because something in Real Life demanded your attention at zero notice, then that's a different matter entirely.
Tbh if something bad enough happened IRL, like something happening to my kid for example, I'd leave the computer running. I wouldn't care about the 50m. In that case I'd put in a ticket to dispute the rebuy. I agree with you though, real life comes first.
What gets my goat is when two CMDRs who shall not be named, attack and destroy my DBX and then my SRV, without provocation, at a guardian site.
Then have the audacity to log off or fly elsewhere in the hour it took me to bring my battle ready Anaconda out to exact some revenge....!
CMDR Cosmic Spacehead
Then have the audacity to log off or fly elsewhere in the hour it took me to bring my battle ready Anaconda out to exact some revenge....!
CMDR Cosmic Spacehead
For clarity's sake, this is, verbatim what it says in the link you provided:
"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."
__________________________________________________________________________________________________________________________________________________
Go through that word for word and show me expressly where he states that logging out via the menu in combat to, as he words it: "to avoid defeat, destruction and damage." DOES NOT COUNT.
Send them a friend request & keep typing 'but why?' every 15 seconds. See how long it takes for them to use the 'unfair' blocklist
During the conversations here about this topic, the terms Combat Logging, and Menu Logging have been established to distinguish between an action that is cheating, Combat Logging, and an action that is not cheating, Menu Logging. Many players, FD, and the rules of the game make a serious distinction between the two. The semantic argument that is going on here is one poster attempting to remove that notable distinction, and one defending it.
Combat in any video game is not some sacrosanct activity. It may be in poor form to Menu Log, depending on the actual circumstances involved, but it still just pixels organized into snazzy space ships. To me, the guy who is raging over a combat/menu log is simply the mirror image of the guy Logging. Both are putting way to much value on those organized pixels.
Combat in any video game is not some sacrosanct activity. It may be in poor form to Menu Log, depending on the actual circumstances involved, but it still just pixels organized into snazzy space ships. To me, the guy who is raging over a combat/menu log is simply the mirror image of the guy Logging. Both are putting way to much value on those organized pixels.
Show me where FD designate Menu Logging (in order to duck out of combat "to avoid defeat, destruction and damage.") is different to combat logging.
Either way you're ungracefully exiting to meet the same ends. How are they semantically differentiated when both the process, intention, and ends are the same?
Send them a friend request & keep typing 'but why?' every 15 seconds. See how long it takes for them to use the 'unfair' blocklist
Oh, that's evil
Send them a friend request & keep typing 'but why?' every 15 seconds. See how long it takes for them to use the 'unfair' blocklist
I don't want them to block me, or I block them. I want revenge!.
But I'd settle for a Belgian waffle.
Ouch - that must have been irritating, but at least you will have at least one of their names in your CMDR interaction history so can exact your revenge later should you come across them again.
Khan said:
That's just aids I feel for you man. I'd just say dismiss your ship whenever you get out into your SRV. That's what I do since I don't trust anybody in my instance lol
Would you settle for a muffin? Asking for a friend.
At the Guardian sites it's actually useful to have your ship close by on the ground, if it has point defences. They'll help shoot down the Guardian missiles.
It is expressly implied by "Combat Logging" requiring an "ungraceful exit" by their definition, menu logging is not an "ungraceful exit".
That's true... I haven't actually done any of the Guardian site stuff since they were first released, so I haven't encountered the missile thing. Maybe you could get friends to go with you and guard each other while you complete the puzzles?7