Originally by: Jimer Lins

---

I know that there's enough people irked at this exploit being abused so much and that there are some relatively simple changes that would make it less abusable.

My personal favorite is the "login timer", which would be like a reverse aggro timer.

1) If you log in in space (and only if you log in in space) your ship must remain for a minimum of 5 minutes, during which time it can be aggroed regardless of whether you are connected or not.
2) For the 30 second timer after disconnect, you are vulnerable to aggro mechanics.
3) After logging out, your warpin point never moves until you have actually completed a warp back to it, regardless of how many times you log out.

That would mean that anyone who logged in, then logged out to move their warpin would be vulnerable to being probed out and aggroed within 5 minutes, and would take the logoffski==safe brigade and cut them off at the knees.

It would also mean that those who logoff under gatecloak (or after hitting the jump button) would be able to be tagged with aggro without having to resort to silliness like an AOE weapon on a covert ops.

---

Originally by: Ospie

---

Originally by: Jimer Lins

---

I know that there's enough people irked at this exploit being abused so much and that there are some relatively simple changes that would make it less abusable.

My personal favorite is the "login timer", which would be like a reverse aggro timer.

1) If you log in in space (and only if you log in in space) your ship must remain for a minimum of 5 minutes, during which time it can be aggroed regardless of whether you are connected or not.
2) For the 30 second timer after disconnect, you are vulnerable to aggro mechanics.
3) After logging out, your warpin point never moves until you have actually completed a warp back to it, regardless of how many times you log out.

That would mean that anyone who logged in, then logged out to move their warpin would be vulnerable to being probed out and aggroed within 5 minutes, and would take the logoffski==safe brigade and cut them off at the knees.

It would also mean that those who logoff under gatecloak (or after hitting the jump button) would be able to be tagged with aggro without having to resort to silliness like an AOE weapon on a covert ops.

---

This looks like a good solution to this issue.

On the whole support this idea, what people who keep posting against this complaint don't seem to realise is that this is a get out of jail free card for freighters, orcas and little more (most BS's won't survive a couple of BS's shooting them) - and it's specifically abused by those industrial ships and little else. If you're bouncing about in lowsec in a cruiser and you disconnect when you jump into a camp, you're going to die with or without a fix to this problem, so the average player will see no difference to their gameplay at all.

---

Originally by: Santiago Fahahrri

---

Originally by: Ospie

---

Originally by: Jimer Lins

---

I know that there's enough people irked at this exploit being abused so much and that there are some relatively simple changes that would make it less abusable.

My personal favorite is the "login timer", which would be like a reverse aggro timer.

1) If you log in in space (and only if you log in in space) your ship must remain for a minimum of 5 minutes, during which time it can be aggroed regardless of whether you are connected or not.
2) For the 30 second timer after disconnect, you are vulnerable to aggro mechanics.
3) After logging out, your warpin point never moves until you have actually completed a warp back to it, regardless of how many times you log out.

That would mean that anyone who logged in, then logged out to move their warpin would be vulnerable to being probed out and aggroed within 5 minutes, and would take the logoffski==safe brigade and cut them off at the knees.

It would also mean that those who logoff under gatecloak (or after hitting the jump button) would be able to be tagged with aggro without having to resort to silliness like an AOE weapon on a covert ops.

---

This looks like a good solution to this issue.

On the whole support this idea, what people who keep posting against this complaint don't seem to realise is that this is a get out of jail free card for freighters, orcas and little more (most BS's won't survive a couple of BS's shooting them) - and it's specifically abused by those industrial ships and little else. If you're bouncing about in lowsec in a cruiser and you disconnect when you jump into a camp, you're going to die with or without a fix to this problem, so the average player will see no difference to their gameplay at all.

---

That's a terrible solution. Not everyone plays the same way. I fly with a nomadic group in deep 0.0 space. We are often more than 15-20 hostile jumps from any place we can dock. We log out in space every day - because we rarely dock. It is not acceptable for ships to float around for 5 minutes after a player logs out or loses connection.

For some pilots that would be the equivalent of - "When you log out in a station your ship is ejected into space and sits there for 5 minutes."

---

Originally by: EdFromHumanResources

---

Wow you said you were going to post a thread about me ctrl Qing I cant believe you actually did it. But hey there are more whine threads about this than pos warfare so sure ill support it because it'll never happen.

---

Originally by: Zenethalos

---

Originally by: EdFromHumanResources

---

Wow you said you were going to post a thread about me ctrl Qing I cant believe you actually did it. But hey there are more whine threads about this than pos warfare so sure ill support it because it'll never happen.

---

You're probably right. It seems CCP is more concerned with carebears having their way and ensuring their security, that and stupid pilots. All these people complain that they dont have a stable connection and its not fair. Whats not fair is that for every 1 person with a faulty connection there are 5 asshats exploiting that saying they dropped.

---

Originally by: Tesseract d'Urberville

---

I agree the system can be abused too easily, and we should consider alternatives.

BUT,

I don't see a proposal here that protects players who honest-to-god involuntarily disconnect at the worst possible moment due to a network failure, wifi disconnect, client crash, or a power outage. These things do happen occasionally (wifi disconnects happen to me from time to time, and a year ago the Macintosh client that I run crashed with irritating regularity) and players should not be punishable in those types of situations.

Sorry, not supported.

---

Originally by: Tesseract d'Urberville

---

I agree the system can be abused too easily, and we should consider alternatives.

BUT,

I don't see a proposal here that protects players who honest-to-god involuntarily disconnect at the worst possible moment due to a network failure, wifi disconnect, client crash, or a power outage. These things do happen occasionally (wifi disconnects happen to me from time to time, and a year ago the Macintosh client that I run crashed with irritating regularity) and players should not be punishable in those types of situations.

Sorry, not supported.

---

Originally by: Tesseract d'Urberville

---

I agree the system can be abused too easily, and we should consider alternatives.

BUT,

I don't see a proposal here that protects players who honest-to-god involuntarily disconnect at the worst possible moment due to a network failure, wifi disconnect, client crash, or a power outage. These things do happen occasionally (wifi disconnects happen to me from time to time, and a year ago the Macintosh client that I run crashed with irritating regularity) and players should not be punishable in those types of situations.

Sorry, not supported.

---

Quote:

---

1) No ship should EVER, EVER EVER vanish while it is locked, scrambled, and being fired on. EVER.

---

Originally by: 4ndromed4

---

I really support this. I mean the current system is just absued too much. Yes a new system can also lead to "unfair" situations. But having ppl roaming around and when they are trapped just log off is ridicoulus. It's fighting without taking the concequences.

---

Originally by: Jimer Lins

---

I know that there's enough people irked at this exploit being abused so much and that there are some relatively simple changes that would make it less abusable.

My personal favorite is the "login timer", which would be like a reverse aggro timer.

1) If you log in in space (and only if you log in in space) your ship must remain for a minimum of 5 minutes, during which time it can be aggroed regardless of whether you are connected or not.
2) For the 30 second timer after disconnect, you are vulnerable to aggro mechanics.
3) After logging out, your warpin point never moves until you have actually completed a warp back to it, regardless of how many times you log out.

That would mean that anyone who logged in, then logged out to move their warpin would be vulnerable to being probed out and aggroed within 5 minutes, and would take the logoffski==safe brigade and cut them off at the knees.

It would also mean that those who logoff under gatecloak (or after hitting the jump button) would be able to be tagged with aggro without having to resort to silliness like an AOE weapon on a covert ops.

---

Originally by: Gaogan

---

If you actually get disconnected at the wrong time what the hell makes you think you should be 100% safe? If you disconnect in a level 4 mission while rats have you scrambled, do you log back on in a pod? If you disconnect while trying to solo a hac in a t1 frig, do you survive? Then why should you be safe if you disconnect when you jump into a gate camp, or at a ss while the guys you just took pot shots at are probing you out? **** happens. If you really disconnect and get killed, too bad, suck it up.

The following needs changed desperately to put a stop to entire fleets logging off, and the 3 @#%!wads that have been hanging around our space all week, logging on, ganking someone, and logging off with total impunity, and other such ******ation.

1) No ship should EVER, EVER EVER vanish while it is locked, scrambled, and being fired on. EVER.

2) Fix the log on and immediate log off/on again exploit to avoid coming back to where you initially logged off.

3) Fix the jump clears aggression timer exploit ( yes, it still works )

4) Increase the non aggro vanish timer from 30 seconds to 2 minutes. Why? Every other game balances log off timers to prevent you from getting away if an enemy is close to catching you if you had not logged off anyhow. Even without aggro you should stick around just long enough for an accomplished prober who is already looking for you to find you. If they were hot on your tail and you tried to ditch, you should be toast.

5) Like every other mmo, when you quit the logoff countdown should start, and you should be able to sit there while your ship is waiting to vanish at the safe spot. If you get attacked then the logoff is aborted and you can defend yourself, if not, then the client closes when your ship vanishes and you know you will be safe until you log on again.

---

Originally by: Darkside 34

---

Once you are agressed (someone is attacking you) then your ship will NOT dissapear until the hostiles STOP aggroing you. Your ship will continue to attempt to warp off to another safe, so if the hostiles have horrible tackle, its their bad luck.

---