A small tweak to Danger Logout

I saw a video of a person using the regular logout with timer, while in combat to leave. To come directly to the point: While it is not illegal according to FDev, it still feels wrong. So why not making making a person in danger cooldown vurnable to weapon damage. All incoming attacks ignore shields, resistance and modul protection of the person in logout. Might even want to increase recieved weapon damage by X%.
 
I saw a video of a person using the regular logout with timer, while in combat to leave. To come directly to the point: While it is not illegal according to FDev, it still feels wrong. So why not making making a person in danger cooldown vurnable to weapon damage. All incoming attacks ignore shields, resistance and modul protection of the person in logout. Might even want to increase recieved weapon damage by X%.

There are so many different ideas on combat logging but a lot of them run into the basic problem that, in its current iteration, the game doesn't allow a player ship to remain in space when they log out (a la EVE Online). Your idea has some merit but might be tough to implement - you're basically created a forced debuff when a player attempts to log out and they are considered to be in combat.

It's not a half bad idea - from a programming standpoint, it might be easier to just force shutdown all modules (or shields at least) such that the player is truly helpless...since that is what they're basically agreeing to by combat logging.
 
There are so many different ideas on combat logging but a lot of them run into the basic problem that, in its current iteration, the game doesn't allow a player ship to remain in space when they log out (a la EVE Online). Your idea has some merit but might be tough to implement - you're basically created a forced debuff when a player attempts to log out and they are considered to be in combat.

It's not a half bad idea - from a programming standpoint, it might be easier to just force shutdown all modules (or shields at least) such that the player is truly helpless...since that is what they're basically agreeing to by combat logging.

This is not about CG. FDev made it very clear that menue quit is totally fair game and legal. Only Alt+F4 is considered CG. For the latter I made a write-up to counter CG of griefers as part of C&P, as well as a kinda way to punish connection drops/without hurting the player to much if it was done by accident. https://forums.frontier.co.uk/showt...-C-amp-P-and-spice-it-up-with-Risk-amp-Reward!

I never used either option in Combat, but had a few instances in which I was in Danger, while not being in Combat(Guaridan Sites + Close to stars). I think there are edge cases in which the ship might take damage from collision and stuff or due to bugs(like getting stuck in a planet, that didn't load properly) and if you use the countdown there, you should not be punished.

As I said only Weapon Damage will affect you. I mean adding auto-submission to inderdiction and disabling thrusters while in countdown seem like a good idea, but I wouldn't want to crash from SC, just because I was close to a stellar body.
 
What are you after here? Punish players? Justice?




A think a better solution would be that if you logout during "danger" you are only allowed to log back in to the same game mode you logged out from while in danger for 24 hours.

Example:
I play in open, and I am in a fight and is loosing, so I use the menu logout with timer to exit the game, to avoid destruction.
Now I can only log back into open for 24 hours.


To clear the 24 hour timer, we have a 2nd timer that starts when you log back in, that is 5 minutes, and if you are in game for 5 minutes, and then logout without being in danger, then you are free to choose game mode as you wish. This is to stop people to using the system to login back in and then as fast as possible to logout again, before they end up being in danger, so they could switch game mode. Now if there are players "camping" your last position they have a fairly good chance to put you in danger again... resetting your 24 hour timer to 24 hour.




I do not expect this be of any major disturbance to PvE players, who uses this avoid destruction from NPC ships. as they would not be in any danger when they login again. So this would mostly affect PvP combat interactions.
 
I am not after punishing people or Justice. If people want to log out while in danger, they should be able to do it. But doing so in combat should not be that easy/come with the risk of falling prey before you acutally loged out. I mean I don't really care if it is done or not, but after seeing said video, I just thougth: "Well this looks stupid and badly designed. What would be a good way to not make it a viable option in combat situations?"

And the timer you suggest doesn't really help the main issue. Just because I have to stay a fixed ammount in let's say open, doesn't really detterent one from using this feature. Supposed you got gank'd, you log out by timer, block your assailant(thus preventing to be matched with them again), before coming back and just enjoying your day.

There are a number of strategies to avoid/deal with ganking&pirates, that don't require to quit the game one way or the other.
 

Avago Earo

Banned
I saw a video of a person using the regular logout with timer, while in combat to leave. To come directly to the point: While it is not illegal according to FDev, it still feels wrong. So why not making making a person in danger cooldown vurnable to weapon damage. All incoming attacks ignore shields, resistance and modul protection of the person in logout. Might even want to increase recieved weapon damage by X%.

Shouldn't this be in your other thread about CL'ing?
 
Shouldn't this be in your other thread about CL'ing?

You mean the C&P? I thougth about it, but this is not CG. This is a totally legal and fine move according to FDev, who only consider Alt+F4 the only true CG and as thus didn't fit into the whole narrative of punishing griefing gankers, since they would rather turn to CG if the tide turns against them. And the Spitballing one in Discussions is also about true CG.

This just affects leaving the game via menu, to not make it a viable option, in combat situations. It doesn't really is an issue, because if you can survive 15 seconds under fire, high-waking and even an additional R&R should do also the trick. It just looked so silly, that I thought to make a comment about it.
 
@OP - How do you propose to handle system/network crashes?

If our peer to peer connection goes Tango Uniform, which one of us is the logger?

If I engage you and have a lag generator so that you crash, what are your options to contest being labeled a logger?

See, the problem here is that the game doesn't know why you fell off, it just knows that the connection dropped. Until you can prove that the drop wasn't the fault of something other than an intentional action, you are asking for a "Guilty, period" methodology. Put another way, it is the equivalent of arming your police exclusively with grenade launchers.

FOOMP, FOOMP, FOOMP!

I got the bad guy!!!!

Yep, and all the innocent people with 20 meters...
 
What are you after here? Punish players? Justice?

A think a better solution would be that if you logout during "danger" you are only allowed to log back in to the same game mode you logged out from while in danger for 24 hours.

Example:
I play in open, and I am in a fight and is loosing, so I use the menu logout with timer to exit the game, to avoid destruction.
Now I can only log back into open for 24 hours.


To clear the 24 hour timer, we have a 2nd timer that starts when you log back in, that is 5 minutes, and if you are in game for 5 minutes, and then logout without being in danger, then you are free to choose game mode as you wish. This is to stop people to using the system to login back in and then as fast as possible to logout again, before they end up being in danger, so they could switch game mode. Now if there are players "camping" your last position they have a fairly good chance to put you in danger again... resetting your 24 hour timer to 24 hour.

I do not expect this be of any major disturbance to PvE players, who uses this avoid destruction from NPC ships. as they would not be in any danger when they login again. So this would mostly affect PvP combat interactions.

This is probably the most reasonable solution I have ever seen for combat logging. It might not be the perfect solution to combat logging, but it is better than what we currently have in-game and every other suggested fix I've seen.

Now if only FDev did something like this whenever they detect an 'ungraceful exit' from the game....
 
if you mess with the logout timer too much more people will just have network problems and crashes.

I run a system with 8 gigs of RAM and virtual memory turned off. Sometimes opening a browser window or some automated background task will start up and crash Elite instantly. Sometimes my wifi craps out. Sometimes I lose my DHCP lease and my IP address changes..

stuff happens.
 
Last edited:
@OP - How do you propose to handle system/network crashes?

Sorry but I clarified already 2 times, that I only! ONLY! talk about, what happens if you Menu Log, while in Danger. You now, that "please wait 15 seconds", before you can logout while under fire.

CLogging or Crashes are not touched by this, since a connection drop instantly throws you out of instance. That is an entirely different issue and not the topic of this thread.
 
This is probably the most reasonable solution I have ever seen for combat logging. It might not be the perfect solution to combat logging, but it is better than what we currently have in-game and every other suggested fix I've seen.

Now if only FDev did something like this whenever they detect an 'ungraceful exit' from the game....

Still not a thread about Combat-Logging, but the Menu Quit, which is fine. I agree that FDev needs to do soming about CLogging, but this thread is about people, who are so g tanky, that they can sit out a 15 second timer to regulary exit the game, while under heavy fire.
 
I saw a video of a person using the regular logout with timer, while in combat to leave. To come directly to the point: While it is not illegal according to FDev, it still feels wrong. So why not making making a person in danger cooldown vurnable to weapon damage. All incoming attacks ignore shields, resistance and modul protection of the person in logout. Might even want to increase recieved weapon damage by X%.

Not necessary. The logout is perfect
Highwake 15 sec = legit logout 15 sec

If you demand an instakill on logout attempt, than why not also when activating the fsd? Hell why not always insta-death?
 
if you mess with the logout timer too much more people will just have network problems and crashes.

I run a system with 8 gigs of RAM and virtual memory turned off. Sometimes opening a browser window or some automated background task will start up and crash Elite instantly. Sometimes my wifi craps out. Sometimes I lose my DHCP lease and my IP address changes..
stuff happens.

How does messing with the logout timer via menu affects performance? If your game crashes you are out. This idea is just, if you had properly read it. About people, who while under heavy fire, still can sit out the 15 second timer for logout, which is a perfectly fine way legally, but feels super dump and should not be possible.
 
Not necessary. The logout is perfect
Highwake 15 sec = legit logout 15 sec

If you demand an instakill on logout attempt, than why not also when activating the fsd? Hell why not always insta-death?

You can only wake with FSD, Engine and Powerplant working. So a hull tank could in some cases, make its escape, where other ships could not. Also loging out to get away is breaking immersion. This is also not insta death. There are mutliple situation, in which the game triggers a danger cooldown, there log-out should be fine.
 
Back
Top Bottom