On the contrary, this is the sort of thing I want to see, a system that takes action on loggers but leaves some leeway to account for accidents like power or internet outages.
IndeedYou can't directly punish CLoggers, but you can discourage it even without karma.
________
It is worth bearing in mind that Clogging is not just a 'problem' faced by gankers, it is a habitual mechanic used by sealclubbers too. Personally I would prioritise CLogging ahead of excessive ganking, because if CLogging is discouraged the playerbase stands a better chance of being able to solve many of these excessive ganking issues themselves.
This puts less pressure on the Karma system to be all things to all people.
Personally I consider loggers of any sort to be worse than gankers that don't log. At least those CMDRs aren't cheating.
'Graceful' right, all FDEV said is that the menu option will be revisited with Karma, and for now one won't face any punitive measures.
But it's quite obvious that quitting in the middle of a losing battle, especially when one is wanted, has cargo, or started the fight, is a cheap cowardly tactic. If one doesn't wish to play fairly with others you are better off sticking to private or solo, those modes exist and provide a less risky option of gameplay. Once karma comes out we'll hopefully see some proper action taken on cheaters, for repeat combat loggers having them instance only with other loggers seems a fitting solution that appeased everyone, even the loggers.
This obsession with Combat Loggers is mystifying. It's not the Combat Loggers that are draining open.
Sealclubbers CLog too![]()
OK, please listen really carefully - Using the existing game mechanics of exiting to menu and waiting the requisite 15 sec is legal, legitimate, and perfectly within the rules as stated by FDev on these forums for YEARS (read longer than you have been around). While I have not problem in negative consequences for those that choose to Combat Log (as has been defined by using any method of terminating the game communication WITHOUT using the menu/timer option) I do have very strong objections to penalizing those that follow the established legal process. I also have a problem with ANYONE telling me where and how to play the game, or when it is "appropriate" for me to choose otherwise - which you are doing here.
While I appreciate that you are entitled to your opinion (however self-serving and wrongheaded I believe it to be), I respectfully submit that you may want to look through the dozens of threads specifically addressing Combat Logging that were part of this board before you came along. In any event, until and unless FDev choose to announce a change to the TOS and EULA to re-define using existing game mechanics as a cheat I am going to continue to play my game where I want, how I want, and in whatever fashion I choose to do so. And as long as I am not cheating per those 2 documents there is not one darned thing anyone can say or do about it.
With that I will bid you farewell...
/rant
But it's quite obvious that quitting in the middle of a losing battle, especially when one is wanted, has cargo, or started the fight, is a cheap cowardly tactic. If one doesn't wish to play fairly with others you are better off sticking to private or solo, those modes exist and provide a less risky option of gameplay.
This obsession with Combat Loggers is mystifying. It's not the Combat Loggers that are draining open.
On this, we agree, but imo (and FD's) menu logging is not cheating.
Me too, lame but legal. There must be a way to exit the game for RL stuff, and as with CLogging, no punishment can be applied because context cannot be reliably determined.
Me too, lame but legal. There must be a way to exit the game for RL stuff, and as with CLogging, no punishment can be applied because context cannot be reliably determined.
Perhaps a flag that sets at the beginning of a session, and only gets properly cleared if one exits via the menu (legally). If a new session is initiated and the flag is still in the ON state, then appropriate Karma hit is applied and only decays after x (insert timeframe here)
Just my thought
Me too, lame but legal. There must be a way to exit the game for RL stuff, and as with CLogging, no punishment can be applied because context cannot be reliably determined.
At first glance, yes it looks like a good compromise.
Until you realize that a lot of players fly around in unmodified ships, badly modified ships and small ships. 30s against a highly modified combat ship is an eternity for those players. The result would be equal to just destroying the ship on log out and thus removing the need of a timer.
Things get tricky at that point.
"You" want to motivate players to keep playing until the potential dangerous situation is over.
The logout timer only affects players how want to play within the rules of the game. Those who "abuse" any system they find for their own advantage won't care about it. If the logout timer is to long they will simply kill the task or do something else to avoid ship destruction.
The result is a system that only punishes those who play fair while it has absolutely no effect on those who it was intended for.
Don't log out in combat. Easy enough. Not sure why you are even arguing. So many cry about immersion but as soon as they can't log out fast in a pvp battle they are the first to break immersion and log out or combat log.
Stay in combat until you escape or die. This logging out nonsense was curb stomped in EVE and it should be wiped out here as well.