The false equivalence I was referring to is the conflation of anything done via the game itself with what's done wholly outside of the game.Factually incorrect - and a rather amusing misinterpretation of the logical fallacy argument.
Reasoning that, because another in-game character does something you think is crappy to your in-game character, that it's ok for you to bypass this gameplay by prohibited means, is a crystal clear example of false equivalence. There are very plain differences that you have to ignore to say "if this is ok, then so is this".
The delay is zero when forcibly killing the game task or severing connection some other way.Having only EVER combat-logged once in my entire career, I'm unsure as to the actual delay - that was a guess.
"Combat logging", as defined by Frontier, and citied in posts by Sandro Sammarco and Zac Antonaci, who were acting in their capacity as Frontier employees, in about a half dozen posts in this thread, is bypassing the timer.
I'd also argue that conflating using the timer, which is intrinsically out-of-character, to bypass contextually in-character events, is also a clear cut example of false equivalence, even if it's not prohibited behavior. However, this is not what "combat logging" is referring to, nor was the specific example I was refering to when I pointed out your original false equivalence (which may well have been unintentional on your part, due to your ignorance of the terminology used by Frontier and this thread).
The answer has been posted at least once, every page.what's the answer, not gonna read 5 pages