Combat Logging - resset timer on damage

[Rhea]

If you're trying to log out "in danger" and the 15sec timer is running, it should reset back to 15s if you take any damage. Many online games solve logging this way. I believe that it would be very effective - together with metrics gathered on FDev side, and punishment if you repeatedly force disconnect in combat. (I would set this threshold very low )

 

[Komemiute]

I don't think Combat Logging means what you think it means...

 

[Muffindrake]

I don't think Combat Logging means what you think it means...

Despite FDev specifically stating they don't consider the logout option an exploit, that doesn't mean anything to us players. To someone who wants your cargo or kill you, it is nothing short of an exploit either way.

In addition to timer refreshing, players targeting someone logging out need to have a notification that it is going on. Anything else is atrocious to the game itself.

 

[Psycho Romeo]

I agree with the OP's suggestion, though like others have pointed out, I do not agree with the verbiage.

 

[Rhea]

Guys i'm not going to argue whether it's an exploit or not. Many games solve this issue by resetting timer - in fact I can't think of a single game that does not do this, and I have been through quite a few online games and their beta tests, they had this functionality in from the very beginning. Someone logging off on you is complete immersion breaker at least, if not total exploit. This would fix it.

 

[Distance]

Most people combat log by killing the process bypassing the timer. Using the timer is supposed to be legit but your idea would work for it as it does need to be increased.

I've quit playing myself until they come up with a proper solution to combat logging.

 

[thearmysredneck]

15 seconds is plenty long enough to kill a stationary or straight line non maneuvering target. Sometimes real life gets in the way of fantasy land. There no reason to punish anyone for that. Using the save and exit option is not an exploit, killing processes and deliberately interrupting data transmission is.

 

[xondk]

Despite FDev specifically stating they don't consider the logout option an exploit, that doesn't mean anything to us players. To someone who wants your cargo or kill you, it is nothing short of an exploit either way.

In addition to timer refreshing, players targeting someone logging out need to have a notification that it is going on. Anything else is atrocious to the game itself.

erm, I'm recalling them stating that it isn't an exploit but it is considered cheating, as in, something you shouldn't do?

 

[Rhea]

15 seconds is plenty long enough to kill a stationary or straight line non maneuvering target. Sometimes real life gets in the way of fantasy land. There no reason to punish anyone for that. Using the save and exit option is not an exploit, killing processes and deliberately interrupting data transmission is.

15 seconds is not enough when your target is an anaconda or python - which is 90% of combat loggers. These ships have huge shield capacity and if they pack some bulkheads, you sure as hell won't be able to take them out within 15 seconds. If your life gets in the way, then ask in the chat for them to stop shooting that you have to go away - that would take you less than 5 seconds with abbreviations: "please stop, irl problem, afk"

Also if you are going to die, irl issues or not, you are cheating by logging off.

 

[Psycho Romeo]

15 seconds is not enough when your target is an anaconda or python - which is 90% of combat loggers. These ships have huge shield capacity and if they pack some bulkheads, you sure as hell won't be able to take them out within 15 seconds.

To preface, I agree with the general motif. Logging out as a means to escape combat is pretty dirty. To look at it more objectively though, it's not nearly as dirty as high waking. In fact, of all the ways one could get out of combat, esc to menu is among the most noble, right behind low waking (in front of combat logging and high waking).

While I agree, I also think that this is something the attacker is going to have to build for. Anacondas can go from shieldless to popcorn in 15 seconds. Pretty much every ship that has the capacity to take on that anaconda in an actual fight can do it. But you have to build for it. Frag cannons, cannons, frag cannons, rails, frag cannons, plasma, frag cannons, etc. Five pulses might not get the job done so well.

If your life gets in the way, then ask in the chat for them to stop shooting that you have to go away - that would take you less than 5 seconds with abbreviations: "please stop, irl problem, afk"

This is a joke right? Ninety times out of ninety one you're going to have better luck just praying to your deity of choice to make the irl problem go away.

 

[thearmysredneck]

15 seconds is not enough when your target is an anaconda or python - which is 90% of combat loggers. These ships have huge shield capacity and if they pack some bulkheads, you sure as hell won't be able to take them out within 15 seconds. If your life gets in the way, then ask in the chat for them to stop shooting that you have to go away - that would take you less than 5 seconds with abbreviations: "please stop, irl problem, afk"

Also if you are going to die, irl issues or not, you are cheating by logging off.

Lunacy. I doubt many would even entertain the idea of stopping an assault if they seen that on comm's. If you and your pack (assuming your the same CMDR Rhea on youtube) can't kill a non shielded essentially afk ship in 15 sec your doing it wrong. I've had players actually combat log by killing processes or Internet connections. You don't see me making any fuss a out it. I haven't reported them either, no reason too. I have other things to worry about irl such as kids, wife, work, and weather or not my data analysis saved my clients a costly failure or i recommended a non warranted costly repair. If the game gets me that uptight if someone presses the escape key and waits 15sec to save and log out, then I'm doing it wrong, it's supposed to be an temporary excape for the stress we face irl. If this stresses you out so bad, then your doing it wrong and you have my sympathy for that. It's a game, it's not that crucial. Killing processes is cheating, so is killing your Internet connection. Waiting 15 seconds to log out through the menu is not.

 

[Rhea]

Lunacy.

Insult your classmates.

It would do nothing to fix it, combat loggers typically exit via task manager or simply unplug internet cable, those that are logging out in game via 15sec timer are playing by the rules.

Rules are not sufficient, it is cheating when they combat log after i take out their drives. Main menu or killing it, same difference.

To preface, I agree with the general motif. Logging out as a means to escape combat is pretty dirty. To look at it more objectively though, it's not nearly as dirty as high waking. In fact, of all the ways one could get out of combat, esc to menu is among the most noble, right behind low waking (in front of combat logging and high waking).

While I agree, I also think that this is something the attacker is going to have to build for. Anacondas can go from shieldless to popcorn in 15 seconds. Pretty much every ship that has the capacity to take on that anaconda in an actual fight can do it. But you have to build for it.

I disagree, High wake is impossible without drives, which is my specialty. While then I can slowly kill my opponent - railguns are not good for hull damage.


Every single one logs off to main menu when I take out their drives. Is this not cheating guys? I hear some combat-loggers in this thread.

 

[DocLooshkin]

Hmm... I don't play in open any more, but when I did, I accepted the consequences of doing so, painful insurance screens included - that just seems right to me. Logging out to main menu to avoid being killed isn't honourable, I agree. I can't really agree that it's cheating, though.

The fifteen seconds of free damage you can inflict is what FD seems to feel is a fair punishment for exiting combat early, whether that exit is for urgent RL issues that have to be dealt with, or simply to avoid death. You might disagree with that punishment for being too lenient, but it's a painful stretch to call it cheating, when it appears to be a fully intended thing by the developers.

It seems even less like actual combat logging, which is something I believe the developers have described as cheating - and which might presumably bring down a shadowban at some point.

 

[thearmysredneck]

Insult your classmates.

I did, you're one of them, as a fellow "Legionnaire" anyways lol.

Yes that was a strong rebuttal, but only to reflect plausibly of your suggestion. In my estimation over 95% of the time, your suggestion would be ignored. I'm one of the 5% who would not, as long as it's not certain power play actions such as attacking or defending an HQ or similar.

I hope your not referring to me with that combat logger statement. I've faced the rebuy several times defending our HQ as well as attacking the enemy's HQ in retaliation, both with and without members of the Legion.

 

[dementia]

Forgive my ignorance but what is High waking, Low waking and the accepted definition of combat logging?

I rarely play open unless to hook up with my friends.

 

[YinYin]

Forgive my ignorance but what is High waking, Low waking and the accepted definition of combat logging?

I rarely play open unless to hook up with my friends.

High wake is jumping to another system, cannot be mass locked by a player due to the large distance only taking larger bodies (planets/stations, no ships) into consideration for the jump calculation.
Low wake is jumping into super cruise, can be mass locked by a player due to low distance requiring smaller masses (such as ships) to be taken into consideration for the jump calculation.

There does not seem to be a widely accepted definition of combat logging - the official (frontier) one seems to be pulling the plug/terminating the game during combat - exiting via the in game save and exit (makes you a sitting duck for 15 seconds during combat) is the allowed but still frowned upon option.

 

[dementia]

High wake is jumping to another system, cannot be mass locked by a player due to the large distance only taking larger bodies (planets/stations, no ships) into consideration for the jump calculation.
Low wake is jumping into super cruise, can be mass locked by a player due to low distance requiring smaller masses (such as ships) to be taken into consideration for the jump calculation.

There does not seem to be a widely accepted definition of combat logging - the official (frontier) one seems to be pulling the plug/terminating the game during combat - exiting via the in game save and exit (makes you a sitting duck for 15 seconds during combat) is the allowed but still frowned upon option.

Thank you for the explanation. I obviously knew about the mass locking/attenuation when trying to engage the FSD but I didn't know that FSD to another system wasn't affected by ships.