PvP An Investigation Into Frontier's Actions on Combat Logging, Part 2

Paige, that is simple.

They provied evidence for fake account. You do not know it was fake, and it does not matter. A fact is the cable has been cut and Fdev did nothing.

It proves FDev did nothing, as everyone expected. I am reporting few combat logging every day i am playing, and i am seeing these commanders still in-game.

Maybe, or maybe FDEV are just better at identifying SDC's false reports.
 

ryan_m

Banned
This conflicts with my understanding. Source required.

Ag4NQAO
https://imgur.com/Ag4NQAO
 
I still don't understand why the so-called victims of combat logging actually care, so someone pulls the plug on you... whatever?

I've had a couple of characters log on me and I laughed. A win is a win.

I don't think it needs a deep understanding of the psyche, it's enough that it bothers them (just as other behaviours bother different people) and it's a solvable problem. It's against the rules, even if you don't consider it that, it's not in the spirit of the game. It's using an out of game mechanism to solve an in-game problem (another example would be stream sniping).
 
Oh the irony... the players abusing the lack of crime and punishment to gank, are complaining about the players abusing the simplistic netcode to escape them.

I can certainly understand this perspective. It does feel a little bit like that doesn't it - consequences for destroying CMDRs have been so light while the impact is almost entirely felt by the victim, it's not really surprising that some would resort to combat logging. I find switching to solo or private a better option personally.
 
I'm not that bothered really truth be told, nor have I ever done it. But it's nice to know that if I do it doesn't matter.
 
How do other games deal with alt-tabbing exits? (or whatever the method is, task-kill thingy)

They bite the bullet. ED's netcode is written for PvE, cooperative gameplay where it doesn't really matter if someone disconnects forcefully. That type of netcode is easier since it doesn't have to deal with people actively trying to mess with it, just normal network behavior, and it was probably chosen to make the initial release deadline before the kickstarter money ran out. So like most other issues in ED, what we're dealing with is a placeholder.
 
They bite the bullet. ED's netcode is written for PvE, cooperative gameplay where it doesn't really matter if someone disconnects forcefully. That type of netcode is easier since it doesn't have to deal with people actively trying to mess with it, just normal network behavior, and it was probably chosen to make the initial release deadline before the kickstarter money ran out. So like most other issues in ED, what we're dealing with is a placeholder.

Oh dear, I see. Thanks.
 
Maybe, or maybe FDEV are just better at identifying SDC's false reports.

The best is you are not right because it does not matter a report is true or false.
If CLogged was done then punish should be made, no matter who did it :)

And it that case, reports was true. Clogg was done on other player.
 
The best is you are not right because it does not matter a report is true or false.
If CLogged was done then punish should be made, no matter who did it :)

And it that case, reports was true. Clogg was done on other player.

It was a faked prearranged combat log just to justify another false report.

However FDEV came to the conclusion it was a load of rubbish doesn't matter (and they won't reveal it) what matters is they correctly assessed it as a load of rubbish.
 
They bite the bullet. ED's netcode is written for PvE, cooperative gameplay where it doesn't really matter if someone disconnects forcefully. That type of netcode is easier since it doesn't have to deal with people actively trying to mess with it, just normal network behavior, and it was probably chosen to make the initial release deadline before the kickstarter money ran out. So like most other issues in ED, what we're dealing with is a placeholder.

Yep. Elite is PvE-focused, with PvP basically just an added extra, not a focus. This is why I believe a PvP flag of some form would have been a better option - there'd still be those who act the at and those who would cheat/combat log, but at least we'd have the extra tool at player level to defeat those behaviours (without needing effort at Frontier's end to investigate combat logs). Still, they did incorporate solo and private modes so there is that. Just as PvEers have had to resort to private groups, including Mobius, to avoid ats, maybe it's about time PvPers also got just as coordinated into a PvP private group to avoid combat loggers (they could impose their own bans on offenders that way). Oh wait, that doesn't work for PvP here does it, for some reason.....
 
Last edited:
I don't know where this claim about open being empty comes from. I get busy instances 24/7, and that's with my subpar Australian instancing.

The 3-4x weekly "Open vs Solo/PG" posts that used to be in here which always seemed to boil down to that the "safe spaces" were bleeding Open of players and breaking the game.
 

Goose4291

Banned
Maybe, or maybe FDEV are just better at identifying SDC's false reports.

Stig, based on their inability to prevent or plug exploits the community have told them about, in some cases for months, thats some top tier clutching at straws.

Unless of course it affects the preferred player groups, in which case stuff seems to get fully (or at least partially) fixed overnight.
 
Back
Top Bottom