So no change in six months then?
This can all go away pretty easily, pretty quickly. Stock responses only go so far to allay concerns imo.
Last edited:
PvP An Investigation Into Frontier's Actions on Combat Logging, Part 2
- Thread starter Rinzler o7o7o7
- Start date
So no change in six months then?
This can all go away pretty easily, pretty quickly. Stock responses only go so far to allay concerns imo.
Sole Hunter
Banned
Yes normally if you are a hacking or cheating you should be removed from the game and/or banned.
Well, I guess that settles that.
FD say they are doing things about it, but will never discuss if, when, or how.
Nothing really more to discuss here i suppose. [blah]
Rinzler o7o7o7
Banned
Yes, according to support. They can determine if something was a log using internal methods, supposedly.
Tl;dr:
Crap, we got caught again, time to copy and paste our response from last time and hopefully people will be appeased again.
*Chuckles in the background*
FD, I personally don't care about combat logging any more since I gave up on piracy because of how it's just impossible to support in this game and with the attitude of the development team.
But seriously, at this point owning up to not giving two crap about combat logging is better than this half-reared facade pulling that really isn't fooling anyone other than new players or white knights.
Shame on you, FD, not because I care about combat logging anymore, but this serious shameful display.
Surely a “stronger” C&P will give some people more incentive to Clog....
Not just from other players, but from NPC’s...
I don’t get how combat logging isn’t (apparently) being clamped down on before any C&P rework.
Sole Hunter
Banned
Who knows, but...
At this point it's pretty clear to me :
They don't care so you shouldn't care either. It's obvious they don't take action on combat loggers.
Last edited:
Deleted member 110222
D
FD is able to see when a client disconnects. However, no, they cannot tell at all what caused the outage. It could be a deliberate act, it could be a service suspension from the user's ISP, it could be a car smashing through the window.
FD can't tell the difference. All they know is that a client DC'd. Now, what can be done is formulate patterns. But this has to be treated very carefully, as unless FD receive evidence from the user in question as to what caused the outage, FD are not actually in a position to say what caused the outage.
Last edited by a moderator:
The primary goal must be to prevent the issue, or reduce it's impact. A punishment would only build resentment which could harm sales. FDev are not the police, and comparing CLogging to hacking is pretty extreme.
If long term trends (karma system) pick up solid evidence of cynical behaviour then sure, throw the book at 'em. But I don't think the OP's example fits that pattern. We all draw the line in different places, the point of the proposal I linked to is that it can be zero tolerance, no line need be drawn. It just removes the benefit of doing so against another player.
Deleted member 110222
D
This conflicts with my understanding. Source required.
Sole Hunter
Banned
They don't prevent anything at all if no action is taken.
Thankyou Paige, much appreciated.
For mine, I don't condone combat logging in open mode (apart from the menu logging method, given that Frontier themselves are ok with the timer approach). That said, nor do I have much sympathy for SDC either, given their history and past actions of many of their members (and those of like-minded groups). Similar to what has been previously mentioned by others, I'm not convinced the SDC 'investigation' has been approached in quite the right way to adequately distinguish their sample from legitimate disconnects. Any investigation of reports by Frontier needs an appropriate pattern of behaviour - I'm not in a position to know what Frontier considers to be sufficient for that but nor do I care and I applaud Frontier for sticking to their guns in not divulging their methods. It would be nice if they could advertise some stats perhaps in regard to numbers of reports/investigations, numbers of confirmed offenders, numbers of shadowbans dished out etc, but there are those who would wear those stats like a badge of honour so I don't blame them for not advertising such stats.
Personally I also believe the only viable approach is to implement a contextual PvP flag, but we know Frontier aren't about to do that.
Fact is there will always be some happy to resort to combat logging, just as there will always be some happy to behave like ats. We're typically told that the latter should be accepted as a fact of life in playing in open mode - while that remains so, then the former should also be an accepted fact of life in playing in that same mode. Deal with it and move on.
Last edited:
Maybe they don't have the resources to sift and deal with all the cases that their detection systems (they have these running I am assuming) throw up?
The whole point of having a system like that is to increase efficiency to the point where it requires minimal human input to handle those cases.
If it's not efficient to the point where their staffs can handle it, that goes to length to spell out how much they do not care.
It's funny, I don't even care about combat logging anymore but this kind of shady PR is something I despise.
If you can't do it you have prevented it. Obviously you can't make it impossible to ungracefully disconnect, there are lots of innocent reasons why it might happen (crappy internet etc).
So the next best thing is to make it so there is no advantage. As an example if the mission list remained unchanged whatever mode you were in you would not be prevented from mode switching, but there would no longer be any point in doing it. I hope this example is clear.
Goose4291
Banned
I hope you dug your shell scrape deep enough before making that comment.
White Knight fire incoming, your posit
Deleted member 115407
D
It isn't, I see people all the time in Open. As long as you don't purposefully eschew high-traffic areas, it isn't difficult to find other commanders (and in some places, in healthy numbers).
Just because every nondescript system you fly to isn't bursting at the seams with hollow squares doesn't mean people aren't out there.