Combat Logging

Status
Thread Closed: Not open for further replies.

Powderpanic

Banned
That's certainly one approach that not only viable it's completely within the rules and solves two problems in one, your issue with clogging and the cloggers issue with playing with you.

Personally when gankers clog on me I regard it as a win.

The block function is fantastic. It removes the need for me to combat log.
Which would includes the cable pull, which is completely ignored by FDEV to the level that it is pretty much working as intended.
You know like driving at 80mph on a UK motorway. Yes its illegal but no one cares, so everyone does it.

I can block all challenge and feel like a winner as I kill noob after noob in Eravate with my OP engineered FDL of doom.
I mean in the unlikely even that the working as intended and fully fedev supported mechanic DID fail me and put me in danger from a player I had already heroically blocked, I could just join a multicrew and vanish faster than Braben says "Exciting"

This game is so wonderfully thought out and designed to cater for everyone! Now I can grief with even less risk than before!
I mean EVEN if someone had the team work to say camp out a station and try to shoot me while I was leaving, I could just switch mode and log back in to continue my noob ganking with absolute impunity!

I do love blazing my own trail! So good! Top Kek!
 
The one that's run by 5-1 exploiters ?, thankfully they are just a minority.

I wouldn't know about that... But all those guys were punished weren't they? If Fdev put half as much effort into punishing combat logging as they did nuking all the engineer exploiters, then perhaps less would do it.
 
I wouldn't know about that... But all those guys were punished weren't they? If Fdev put half as much effort into punishing combat logging as they did nuking all the engineer exploiters, then perhaps less would do it.

Isn't it also possible that if there weren't loads of exploited Super-duper ships that less people might have CL'ed?
 
How would FD be able to tell? All they would be able to tell is, that a certain time, no viable routes between IP’s was available. Which happens all the time all over the world.
 
The block function is fantastic. It removes the need for me to combat log.

I've never felt the urge to clog, but whatever floats your particular boat I suppose be careful you might get put on a reddit list

Which would includes the cable pull, which is completely ignored by FDEV to the level that it is pretty much working as intended.

It's not a big deal, just laugh it off and accept some people don't want to play the video game with you.

You know like driving at 80mph on a UK motorway. Yes its illegal but no one cares, so everyone does it.

Speak for yourself, I don't do RL speeding. Landing at full afterburner in a video game is different.

I can block all challenge and feel like a winner as I kill noob after noob in Eravate with my OP engineered FDL of doom.
I mean in the unlikely even that the working as intended and fully fedev supported mechanic DID fail me and put me in danger from a player I had already heroically blocked, I could just join a multicrew and vanish faster than Braben says "Exciting".

If you are using the block function to get rid of challenge in the game then perhaps you need to either git-gud or switch to solo, it sounds like open mode might be a little too challenging for you.


This game is so wonderfully thought out and designed to cater for everyone! Now I can grief with even less risk than before!
I mean EVEN if someone had the team work to say camp out a station and try to shoot me while I was leaving, I could just switch mode and log back in to continue my noob ganking with absolute impunity!

I do love blazing my own trail! So good! Top Kek!

I've got to admit the old taunt the rammer, switch mode to bypass, switch back and taunt him again is good fun.

I wouldn't know about that... But all those guys were punished weren't they? If Fdev put half as much effort into punishing combat logging as they did nuking all the engineer exploiters, then perhaps less would do it.

If they banned the cheats they've already identified there'd definitely be less cheating. The thing about cheats is they always cheat whenever they can get away with it. Nobody who used the 5-1 cheat isn't going to clog as soon as the fight goes against them, it's what cheats do.
 
How would FD be able to tell? All they would be able to tell is, that a certain time, no viable routes between IP’s was available. Which happens all the time all over the world.

The operative word you are looking for is trend - a pattern of behavior over time.
 
Pulling the plug or logging off through menu at "strategic moments", they're both equally cheating, regardless of being "sanctioned by FD"or not.

Do I care about it? Most definitively not.
 
Last edited:
Nobody who used the 5-1 cheat isn't going to clog as soon as the fight goes against them, it's what cheats do.

I know of plenty of players who used the 5-1 exploit and have more than a billion in rebuys. So that statement doesn't hold true.
 
I know of plenty of players who used the 5-1 exploit and have more than a billion in rebuys. So that statement doesn't hold true.

Credit's are meaningless to cheats they use cash exploits, they'd be pulling the plug just to try to annoy you or avoid respawning somewhere inconvenient. Don't trust anything cheats ever tell you about how trustworthy they are.
 
The last time I openly talked about combat logging I got a full forum ban for 24 hours, so I will be REALLY careful with what I'll say.

Combat logging, against my own personal opinion is:

Recording a video of a particular encounter, and upon conclusion of said encounter extensive notes are taken throughout. Logging any, and all particular good and bad practices that may have contributed in a win or loss.

The net result is a full log or itinerary of the encounter for reference. Combat logging is a great way to assess what went right or wrong and hopefully help the pilot refine his / her piloting technique so that next time, the same mistakes are not repeated, or, things that went really well, can be refined and repeated with greater success.


How did I do? [noob]
 
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.


Disagree

Their game, their definitions.

FDev placed a 15 sec timer into the log to menu *ONLY* when you are in "combat". At every other time, there is no delay in log to menu.

Killing the task or pulling the network connection, however - this doesn't have a 15 sec timer - so therefore is a Combat Log and therefore a dishonourable act. <Note the capitals>

If you want to call the 15 sec timer a combat log <no caps>, then so be it, but it is in no way a dishonourable thing to do, it is an accepted function. Or as I've seen some people say - "Valid Gameplay".

I mean, really, how long does a low wake or high wake take? Which are also "Valid Gameplay". About the same???

Just accept the Valid Gameplay for what it is and move on.

Cheerz

Mark H
 
Disagree

Their game, their definitions.

FDev placed a 15 sec timer into the log to menu *ONLY* when you are in "combat". At every other time, there is no delay in log to menu.

Killing the task or pulling the network connection, however - this doesn't have a 15 sec timer - so therefore is a Combat Log and therefore a dishonourable act. <Note the capitals>

If you want to call the 15 sec timer a combat log <no caps>, then so be it, but it is in no way a dishonourable thing to do, it is an accepted function. Or as I've seen some people say - "Valid Gameplay".

I mean, really, how long does a low wake or high wake take? Which are also "Valid Gameplay". About the same???

Just accept the Valid Gameplay for what it is and move on.

Cheerz

Mark H

You've made the same mistake I did. Sovapid is saying that it is Combat Logging (by any reasonable definition), but in the case of the Menu Exit it isn't illegal​ Combat Logging.
 
You've made the same mistake I did. Sovapid is saying that it is Combat Logging (by any reasonable definition), but in the case of the Menu Exit it isn't illegal​ Combat Logging.

I see where the opinion is routed, but I still don't agree with it, because I've invoked the privilege of using the term "Valid Gameplay". So I don't believe I've made a mistake, just that I've put a tad more analysis into this...

Low wake?
High wake?
Log to menu?

Are we seriously going to accept the notion that low wake or high wake acts that take you away from an engagement are "combat logging"? I suggest not. In which case, log to menu falls under the same category, strictly because there is a timer and it is a valid sequence of button presses, the same as high wake and low wake. Strictly all "Valid Gameplay" in my view.

[up]

Cheerz

Mark H
 
This canker sore again?

This is reason number 19 on my list of Why PVP in Elite is a WOMBAT.

There is no solution, there will never be a solution, and CTD's can be "manufactured" with a single line of code entered into the correct place.
Instant Driver Fault, Stack Overflow, or fault in NTDLL.dll and program termination that isn't your fault. At least not to anyone trying to look into it.

The sooner people learn to accept that some folks are going to do this no matter how many threads they post here and get back to playing the game, the better it will be for everybody.

Yes. People will cheat.
Yes. People will lie.
Yes. People will steal.
Yes. We will elect some of these exact same lying, cheating, stealing scumbags to public office, idolize them as celebrities, and make excuses for their miscreant behavior.

In short, we enable it.

Go name-and-shame them on reddit for what they do, since you can't do it here. Send them angry tweets and cover their facebook walls with graffiti until they sit there and let you kill them.

The only possible solution is to replace the sudden disappearance of their ships with a ship explosion animation. Then you'll never know what they did and won't care, and the rest of us, who don't care about PVP-only problems won't have to hear about it any more.
 
Yes. People will cheat.
Yes. People will lie.
Yes. People will steal.
Yes. We will elect some of these exact same lying, cheating, stealing scumbags to public office, idolize them as celebrities, and make excuses for their miscreant behavior.

.


Thanks dude for lightening the mood and bringing a smile. oh-seven. [up]
 
The last time I openly talked about combat logging I got a full forum ban for 24 hours, so I will be REALLY careful with what I'll say.
hehe, thats correct.

When they really care, they should put 15s timer to client disconnect, too. How hard it would be? For example this timer should be only in OPEN (for players with bad connection).

Also, telling to new players combat logging is "HACK", "you will be banned for that" its not good, only put more people out of OPEN. I met plenty of combat loggers and doesn't seem they have ban, and dont expect proof video from me, that is not mine job.
Censuring something what people normally using in OPEN is not good way how to fight against it. You just put new players in disadvantage.
 
Last edited:
I wouldn't know about that... But all those guys were punished weren't they? If Fdev put half as much effort into punishing combat logging as they did nuking all the engineer exploiters, then perhaps less would do it.

I hate to muck-rake but this is something that really bugs me.

No. they weren't punished.

If you rob a bank, having the stolen money confiscated is NOT punishment.
Punishment would be to go to prison and be deprived of your liberty for a period of time.

Same thing applies in ED.
If you cheat then having the proceeds of your cheating removed again is NOT punishment.
Punishment would be to have, y'know, some kind of punitive action taken against you; a ban or a save wipe or whatever.

Based on the precedent FDev have set, I'm not sure how you can "punish" somebody who cheats in a way that yields no immediately tangible benefits.
There's no "ill gotten gains" to confiscate and any other type of punishment would actually be harsher than what's previously been applied for other misdeamours to this point.

I guess we'll just have to rely on the impending "karma" system to deter CLing.
 
Credit's are meaningless to cheats they use cash exploits, they'd be pulling the plug just to try to annoy you or avoid respawning somewhere inconvenient. Don't trust anything cheats ever tell you about how trustworthy they are.

What cash exploits would this be then? Using the menu to exit combat is ok, but using the mission system in-game isn't - that it?
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom