Player Features and Ideas Discussion

I don't see how it's possible to abuse such a mechanic. The ship would attempt to warp after the current cycle ends. Gosh, need to get a point on it or have it bubbled.

Log off/disco, bastion/triage/siege/cyno finishes cycle, ship attempts e-warp.


Also, every dread/carrier/cyno pilot worth their salt keeps their stront/LO in half-stacks anyways. So those modules can be made to shut off after the cycle ends.

Yes, thank you for explaining how E-warp works. Thats the whole point of this thread, to change the mechanic to something more logical. The reasoning "thats how it works" is a terrible argument for allowing this kind of mechanic to remain in place. If I applied the same kind of thinking to the old log-off mechanics, then we would be back to a game where you could safely log anything off so long as there wasn't enough DPS to kill you, because "that's how it works". So I could just log off my ratting carrier when it gets tackled by a small gang and safely disappear. Or I could fit an MWD to my nano BS and reach insane speeds beyond what frigates can reach. "

that's how it works" doesn't hold water when we try to use it anywhere, now does it?If we applied the thinking "thats how it works" to more things in eve, nothing would ever get fixed because "that's how it works".

That mechanic was changed because it didn't make sense. It also doesn't make sense that under normal circumstances my ship could remain in space until downtime when in any other scenario it would have warped and disappeared.

I'm fairly sure it hasn't been. I lost a Vargur from a power outage a few weeks ago. (Thunderstorm.) I managed to get my computer back on & connect to EVE just in time to see it explode. No scramming ships in the mission, so I definitely wasn't scrammed.

Honestly, I'm not really bothered with the current mechanic. (I knew the risk, and when I heard the thunder thought about switching to my Mach, next time I will. ) I certainly wouldn't complain if they changed it to e-warp at the end of a cycle, though.

just tested on my paladin. I warped 100km from a planet, activated bastion, and stopped eve via the task manager. I let 90 seconds pass and logged in. My ship had E-warped and automatically started warping back to my original spot when i logged in. e-warp appears to be working

auto-repeat was active

I didn't speak about this mechanic.


The real problem is here: while being DC all modules are shuted down (not instantly, they have to finish their cycle), the bastion has a 1min cycle. During this minute, all hardeners are OFF, NPC kill you in a second.

So i suggested this:

ill will retry with aggression timer

EVE does have a Ping-Pong Mechanic to check for Disconnection
It would also stand to reason that there either is, or /should/ be a Mechanic that let's the server know about a "Clean" Shutdown... i.e. Quit

The only possible abuse therefore that could happen is the traditional rage-quit "switch of power" / "reset" that people used to do to prevent their Supers from getting killed, as E-Warp actually basically instantly warps you off (that's the entire point in it) where it then will sit for up to 15 minutes in a "Safe Spot" before logging you out and the ship disappearing.

On the whole I actually don't have a big issue with how the mechanic works as such, because I do think technical problems such-as Connectivity issues /should/ give your ship a chance to survive; as you've basically been screwed over by your ISP / Modem / Router, which sure some of those things you can control; but most people are limited to 1 maybe 2 ISPs and more often than not they ARE using the best option available to them.

Trying to figure out which of those are abusing it by simply switching off their power though, I think could potentially be solved with an "Unclean" Shutdown that if flagged triggers a service to run on boot... I mean this can also be collecting information if you lose connection as well, so when it returns the game knows it isn't your fault and perhaps provides you with Insurance Compensation and a Flag on the KM denoting it was a Disconnection Kill (i.e. not official / api authenticated)

Where-as when you reboot your system, it could check to see if Windows / Mac Crashed (again another valid possibility) or if you just happened to Rage Quit, in which case Windows (not sure about Mac) will actually log the unclean reboot rather than a crash report.

I mean there are ways to really try to keep such situations relatively fair to everyone while stopping people from being abusive sore losers.

I didn't expect much more from a cadarian mission runner, a "40% just levels his raven" as i saw on this forum.

Yes, it's a bad thing too. Why the bastion stay active when there is an agression timer? Is that a bug or it's perfectly desired by CPP?