Player Features and Ideas Discussion

Aggression mechanics need a small tweak:

Allow pilots to inherit aggression within ~20-30 seconds of logging off.

Currently it's FAR too easy for pilots in tanky ships to fly around in an utterly carefree manner without worrying about dying to solo PvPers or small gangs. Here's why: say you're in a Drake/Command Ship/tanky battleship and you're cruisin gates without a scout, like a boss. You jump through a gate and encounter a solo PvPer or couple of dudes out in their newly-buffed assault frigates on the other side. ****! You might lose your ship! OH WAIT, no you wont. Simply log off before your gate-cloak expires and you'll be fine due to the inability of the hostile ships to kill you in under 60 seconds.

The same scenario goes for capital / supercapital ships jumping to cynos / cyno beacons as well. Simply put, tanky ships can cruise around unscouted with very little risk of dying to small gangs / solo PvPers unless the hostiles can put a dictor bubble up before the hostile can jump in.

My original suggestion was going to be to render logged off ships open to receiving aggression flags until they had entered or completed their emergency-warps (thus, if you jump into dictorless-hostiles and CTRL-Q, you'll become aggressed when the hostiles tackle your ship when it decloaks to e-warp off). If this is technically feasible I would suggest implementing this change. If it's not feasible to track states like that, you could simply set a 15-30 second timer (most ships take around this amount of time to e-warp off anyway) during which aggression could still be inherited post-logoff.

It's seriously obnoxious in an exploity-way that people can just jump into dictorless camps and get away scot-free as long as they have a big tank. I'd love you long time if you'd remedy this situation at some point... preferably sooner rather than later.

While I agree that the problem you're trying to solve is exploity and should be plugged in some way, your solution is bad and is very unlikely to be implemented taking in account CCP's plans for changing how logoff works. If you don't already know, the plan is to make it so, that you can logoff and wait for your ship to disappear without closing the client. This way it isn't left to chance what happens to your ship when you logoff. This is a good thing and your idea goes against the whole point of this planned change.

I would think the better solution would be so for normal Warp, 75% Speed is Required (as it is now) but Emergency / Log-off Warp has that extended to 95-100%.

This wouldn't stop the issue, but this would basically mean it takes longer to do an E-Warp. This would render the target more vunerable to Warp Disruption / Scrambling prior to logging out. Would work incredible well with the new log-off mechanics.

How exactly what? Why is it bad or other ways to solve it? Currently it's bad because mechanics that get you killed after you've logged off the game are god awfully bad design. It's much more preferable to have a system, that no new flags can be added to you once you have logged off. Yes it allows some loopholes, but it's much more preferable to have those loopholes, than allowing people to use different loopholes to gank people who have already logged off justifiedly thinking they were clear to do so. It is simply the less bad way to implement it currently and causes much less work for the GMs, since they don't have to deal with constant petitions about it.

Another solution? Currently I'd just raise the issue and leave the solution to CCP. Reason being that since tho whole logoff system is being changed, so they might as well think about how to eliminate this problem permanently while they're at it. When the devblog is published, raise the issue there too to make sure it gets looked at. Depending on how the new logoff system is implemented, it could even allow gaining new flags after the logoff is initiated, since the player would be able to be aware of them now and cancel the logging off sequence to deal with the situation appropriately.

Just to make sure there is no misunderstanding here. I think the goal of the idea is good, but in the current system the solution is not a good one. It might be doable after the logoff changes have gone through, but if he wants to fix the issue before the new system in implemented, the solution has to be something else.

If you log off in a safe way, you'll still be fine with something like my proposed mechanic in place. If you jump into a gatecamp or a hostile appears in your anomaly and you log off, however...

Why would this change be so horrific? If you log out at your safespot and some bomber who probed you out and was sitting there all day waiting for you to log points you, you should die IMHO. I imagine this is the kind of thing you are envisioning when you say this idea is bad?



Agreein with this. You have to wait for them to finish their ewarp (takes 15-30s), then wait your scan probe time (assuming you had the probes pre-positioned) which adds another couple of seconds, then warp to the result (which takes another ~10+ seconds). If someone is set up well enough to pull this off, the target probably deserves to die. Don't log out with probes on you.

This isn't fair to those who believe in taking responsibility for their own actions & finding intelligent/effective ways to survive these encounters. Until this exploit is fixed or declared as an official exploit I'll be training my interdiction skills in protest as soon as my current skill queue finishes.

Sorry, I should have explained it a little better:

I was thinking of allowing New Aggro Timers deliverable to any and all ships in space.... Then, just shorten the time the ship is in space to a more reasonable number (20-30 s). This is not necessarily "better," but more like simpler.... If you can start shooting a ship, you get to finish shooting a ship... As long as the ship-will-disappear-in-x-time timer is shortened enough, then you have essentially the same solution you presented... The only strangeness would be NPC aggression, which might keep a ship in space long enough to get you in trouble.... I consider this a possible issue with legit DCs...