EVE General Discussion

If someone gets a normal aggression timer and then a fleet warps in to try gank a ship, can the aggressee log-off to save their ship from getting ganked?

Just a question. Thanks for answering =D

I forget which dev post it was but one of the problems with blob wars was people logging off, so they are going to change that in order to stop people saving their ships that way.

Yes i did see that, which is what is confusing me.

That devblog says they WILL ALTER so logging off like that saves a ship...but still unsure if that system is in place yet.

No. You'll have a 15-minute logoff timer.

If you're pointed, you'll remain on the field until you explode. If you're not pointed, you'll emergency-warp and sit in space until your timer expires and you disappear; however, your enemies will have 15 minutes to probe you down and kill you, and they will very likely do so.

The logoff aggression timer (not to be confused with gate aggression timer, NPC aggression timer, canflipping aggression timer, CONCORD aggression timer aka GCC, or kill rights) starts every time either you attack anyone, or anyone attacks you. By "attacks" I mean any hostile action - e.g. gunshots, EWAR, AoE weapons, etc. The timer lasts for 15 minutes and is restarted with every hostile action. The timer is also system-specific, so if you jump in a different system, you don't have the timer anymore. But if you jump back, your timer from the old system resumes.

If you log off while you have this timer active, your ship will perform an emergency warp (1 milion km (1 Gm) in a random direction) if possible, i.e. not warp scrammed. It will then sit there for 15 minutes, then disappear. Without the timer, you do an e-warp, sit in place for 1 minute, then disappear.

The change coming this winter is that your logoff aggression timer can be restarted even during the 15 minutes you are already logged off, but your ship is still in space. Previously, one could just log off, and if they could tank incoming damage for 15 minutes, their ship would disappear. Now, as long as you are under attack at least once every 15 minutes, your ship will stay in space as long as your enemies need to kill you.

It's also worth noting that the timer extension does not apply when you logged off without a logoff aggression timer running. If you log off without aggression, even if someone manages to find you in one minute and starts shooting at you, your ship will still disappear.

I pray the forum doesn't eat this post, as that would make me rage.

So to summarize:

Logoff timer currently: You still warpoff if you dc/log deliberately if not scrammed,
New timer: Still stay in the same place

Think i got that, thanks.

BUT what i don't understand is this: how come a ship with a cap transfer array be classed as a hostile action when he goes to transfer cap to a fleetmember (e.g basilisk cap buddy)?

I'll check out sisi soon.

Here's what happened: decided to take my CNR into a few incursions with some random group before i went to bed and saw a good fleet, joined up and all seemed fine. They had 2 scimmys and a basi, who claimed didnt have a buddy. I offered him my help and he accepted.

Soon as i locked onto him and started the cap transfer on it, i got an aggro timer and they proceeded to jam/shoot the **** out of me (was about 8 machs i think?) I thought 'oh **** you' and decided to log-off.

So if cap transfer isn't hostile why was i still put on a timer?

Did the person you transfer cap to have some sort of aggression timer on?

So killed by griefers? pathetic. Bye then.

He's talking about Incursion griefers. Before going into a site, some player X will get aggression from his buddy Y. Unbeknownst to the rest of the fleet (or sometimes knowingly) a player A will aid the aggressed X (rep/transfer) and now sets themselves up as an easy target to the incoming fleet of players from the same corp as Y., all touting aggression on A.

Now I can't recall if there's a pop-up warning before repping/xfering to someone with aggression, but if there isn't it constitutes a real problem as severe as when CCP had to fix repping of GCC targets.