Why are you asking me this?
PvP An Investigation Into Frontier's Actions on Combat Logging, Part 2
- Thread starter Rinzler o7o7o7
- Start date
Why are you asking me this?
Because cheats and exploiters would (and apparently have) use it to fake someone else combat logging to try to game the report player function to get that legit CMDR punished. So they have to be careful about malicious/false reports.
Cheats and exploiters are the reason we can't have nice things.
Yes, but why was he asking me that?
How am I supposed to know what and how FDEV take action on that?
My point is, as the Devs has clearly stated, Combat Logging is an exploit, therefore cheating.
He's asking you if you have thought out the possibilities for cheats/exploiters gaming combat logging punishment, like they have the speed limit.
As it makes any punishment for clogging a lot more problematic for FDEV.
Nope, I'm not a developer.
As a player, it's my responsibility to abide by the rules the developers have laid down and report those who break them.
Which I'm quite happy to do.
Yep, but if you want to see punishment for clogging you need to remember that cheats will also try to exploit any reporting system. It's like player finding tools, they sound great from a bounty hunting perspective then you remember about stalkers and they fall apart (that happened with EVE IIRC).
Everything has to be cheat/malice/fake/lying/nutter/exploit proof as much as possible, sometimes the only way to do that is by not doing it.
This is possible but can not happen very often.
Instancing and general chances of being interdicted by players don't give a lot of possibilities to fake/induce a CL on another player.
So this is an argument against punishing any single report of CL, so is the general network instability which reported some people here.
To punish a CLer there should be more than one report by different people. Those people and the CLer should not be part of each others friends list, they should be totally unrelated. "More than one" could be at least 3 in week, or 5 in a month, or a little bit less, just to give something you can argue on.
These rules would be enough for bad PvP players who attack or engage into PvP but CL if they loose.
Most people who are just ganked by other PvP players would fall under the radar and would not be punished.
So how many is too many ryan_m?
This whole Clogging thing is about being fair, right? sticking to the rules? Sometimes disconnects happen, sometimes it's not the fault of the one that got disconnected.
You, those of you that are hypersensitive to being Clogged on, are in some cases being griefed. And that's frustrating, sure, but any suggested solution that potentially punishes other innocent (or ignorant) parties isn't going to help when solutions that don't are available.
Cheats cheat in any way they can. I got reported for cheating because I was using the block function for it's intended purpose on station exploiters (it went nowhere obviously), do you seriously think people won't try to game clogging punishments ?.
Goose4291
Banned
I get that.
I'm referring to the idea that Asp Explorer just floated as to why punishment shouldn't occur, on page 104
This isn't a perfect analogy but you gotta assume innocent until proven guilty (beyond reasonable doubt) right? I'm no expert (at anything
) but I am aware that it's quite possible to forge a Clog. It's near impossible to forge a history of CLogging. FDev would see the same players being CLogged on by a bunch of players that don't Clog in other circumstances / with other players.More needs to be cheat proof than shouldn't occur.
Oh - not directed at you personally of course - was a completely general question
In multiplayer games of any description, where any player can find an opportunity to "SCOAR DA WINZ" at the expense of everyone else - wether through exploitation of game mechanics, rubber rules, hardware manipulation, network lulzbunnery, or good old fashioned ganking - it's absolutely guaranteed that it'll happen.
How about we jump those hurdles when/if they come? Let's first get proven cases of cheating properly punished and then we'll worry about the extremely rare edge cases of someone able to bypass FD's checks and make it appear as if another player clogged.
One.
Combat logging .. a Solution
Problem: Combat logging.
FIX: Any ship, that fires on a 'target' or is fired upon is 'locked'
If the 'Internet' connection is lost the 'locked' ship that lost their connection ( combat logger) is blown up.
and the other Pilot is credited with a kill, any infringement by that remaining ship / player ( ie Griefing) at the start of the combat, is wiped.
https://forums.frontier.co.uk/showt...nsequence-Commutation-Commerce-the-bane-of-ED
Problem: Combat logging.
FIX: Any ship, that fires on a 'target' or is fired upon is 'locked'
If the 'Internet' connection is lost the 'locked' ship that lost their connection ( combat logger) is blown up.
and the other Pilot is credited with a kill, any infringement by that remaining ship / player ( ie Griefing) at the start of the combat, is wiped.
https://forums.frontier.co.uk/showt...nsequence-Commutation-Commerce-the-bane-of-ED
Last edited:
How would you establish that it was a cynical act & not random bad luck?
What would be the criteria for the disconnect?
What do you think the punishment should be?
Griefers charter.