Ok, I'll explain. Cargo matters if you are doing BGS or PP. Not the cargo to be picked up, but the cargo that needs to be destroyed.
You implied it via your statement regarding potential loss.
Indeed. Although we do have the old "well, I don't have a better response nor can engage the person on an intellectual level, so let's resort to namecalling and brute force" demonstration here. /yawn
And you probably thought things had changed here, alas no, same old same old![]()
TBH, you seem to fail to understand a lot of things about ED, so no surprise there
Calling people names over a game is a bit pathetic. It’s also kind of ironic as it presents you as the exact thing your accusing the other guy of being.
Ad Hominem. No surprises there eitherTBH, you seem to fail to understand a lot of things about ED, so no surprise there
Wouldn't that be a carelessbear?You are a carebear because you disregard part of the gameplay as something you don't care about
I do not differentiate. why do I have to? accidents happen. when talking about combat logging we're talking about intentional actions and not accidents.I don't see anything being "disregarded" here... I see a lot of different people asking the same questions- such as,
"How do you differentiate between someone with a legitimate reason for being disconnected, versus someone who purposely disconnects to avoid altercation?"
All I see is assumption that the people asking direct questions must somehow be "carebears" and a rather dismissive salty attitude in return. Please do shock us with your supposed "enlightening" response.
Ah, sorry, but I have to stick up for the PvP community here. CP is not representative nor illustrative of the excellent Elite Dangerous PvP community.If you are an example of the mentality of the PvP fraternity then I am quite pleased I am not a member!
That however is spot on. But we are of course enlightened people who can see through stereotypes and clichesAnd believe me, you are not doing a lot of good for the PvP community, just reinforcing a lot of bad sterotypes ….
I do not differentiate. why do I have to? accidents happen. when talking about combat logging we're talking about intentional actions and not accidents.
my question is to you: what is so goddamn hard to understand about this?
I agree and do apologise to the PvP community at large but currently there is only one PvP voice being heard.Ah, sorry, but I have to stick up for the PvP community here. CP is not representative nor illustrative of the excellent Elite Dangerous PvP community.
That however is spot on. But we are of course enlightened people who can see through stereotypes and cliches![]()
Told you we were enlightened people, who recognise when they spoke too soon and apologize for their hasty words..I agree and do apologise to the PvP community at large but currently there is only one PvP voice being heard.
One of our squad-members was accused to be a c-logger. Why? He went to Golconda...in open...as he saw some gank...uhm...pvp'ers locking on on him, he MENU-LOGGED!!! After that he cooled down for 5 Minutes logged in again and instantly MENU-LOGGED again, as he witnessed the same "pvp'ers". Shortly after that, he received a "friendly" mail from Frontier, wherein the accusation of c-logging was stated. He replied, that we would like to take a glance at the log-protocol, that proofes he c-logged. Guess what again...no more consequences.
So much for carebears and gankers...oh...and by the way...the mentioned squad-member is a pretty good (in both meanings of the wording "good") pvp'er.
Exactly that. The problem lies on Frontier's half of the playground. My mentioned incident, "proofes", that even Frontier cannot precisly differ between an intended c-log, connection-loss or a menu-log. Otherwise my mate wouldn't been contacted by Frontier. To conclude: Until Elite is not fully reworked, there won't be any chance to sanction c-log properly.Yet once more, accusations without proof that are mere assumption. I'm glad things worked out for your squad-member.
Torches and pitchforks being called for here would affect everyone negatively- as there's no way to differentiate the difference between a "c-log" versus a legitimate disconnect outside of the person in question openly (pun intended) admitting to the fact publicly.
Therefore... there is no "problem" that needs a solution here... if the accuser can prove that someone is "combat logging" by their own admission, then the penalties should apply.
Exactly that. The problem lies on Frontier's half of the playground. My mentioned incident, "proofes", that even Frontier cannot precisly differ between an intended c-log, connection-loss or a menu-log. Otherwise my mate wouldn't been contacted by Frontier. To conclude: Until Elite is not fully reworked, there won't be any chance to sanction c-log properly.
Remember what appears to be Combat Logging to one person is low waking to someone else! Yes ages ago I was accused of menu logging when I low waked out of a situation. Apparently I was suppose to stay there and get blown up but by evading I was effectively cheating. Luckily that was not a fair representation of the PvP community, more an isolated case of stupidsWell, I somewhat agree... the onus still belongs to the accuser- yet the proof needs to be verified by Frontier. What I've seen a lot of is accusation without proof- and yet no way to actually determine legitimate disconnections versus intentional disconnections. IIRC, there's also a way for accusers to physically see in game (some sort of "ghosting" affect) between a "menu log" versus a "hardware" (or disconnect), so if someone is randomly accusing people of "combat logging" when it's not substantially proven as such, it should also be turned on the accuser, as well.
The Boy Who Cried "Wolf" comes to mind here.
Oh one more thing, how broke this game is, regarding PvP is. We (A Wing) chased a corvette, pinned her and open fire. The Vette deployed a fighter an instantly the vette rubberbanded like hell. Nevertheless we somehow manage to fire. suddenly the vette "dissapeared". We were NOT sure if he c-logged or it's the games fault. No wake no nothing. Luckily for us, and with full respect for the vette's commander he "reappered" and let us finish our job. No flaming on comms, just a "gg". Clearly an unintentioned c-log. Sure we could have blamed him for c-logging right after he "went" and we would had "proof" (video), but we are "good" pvp'ers.Well, I somewhat agree... the onus still belongs to the accuser- yet the proof needs to be verified by Frontier. What I've seen a lot of is accusation without proof- and yet no way to actually determine legitimate disconnections versus intentional disconnections. IIRC, there's also a way for accusers to physically see in game (some sort of "ghosting" affect) between a "menu log" versus a "hardware" (or disconnect), so if someone is randomly accusing people of "combat logging" when it's not substantially proven as such, it should also be turned on the accuser, as well.
The Boy Who Cried "Wolf" comes to mind here.
For many a PvPer it's the fact that the other party cheated in order to escape an unwanted situation.However, one question I do have is why are players so upset when someone CLOGs? They weren't denied a massive payout because from what I have read most that CLOG out are clean, non PvP players so they wouldn't have a bounty. They technical won the battle as they forced their opponent to leave the instance. They wouldn't be scooping up any cargo because as far as I know a destroyed player ship doesn't release cargo, only NPCs do that.
So what have you lost except the visual of the ship exploding? Is it the salt generated, the satisfaction of beat another human being (which in fact you did even if the CLOGGED)?