Player Features and Ideas Discussion

I like the way almost every idea on this forum boils down to "I can't figure out how to kill it so it must be OP and needs to be nerfed!" You just need to figure out the vulnerabilities of the situation and play to those. The fact that JFs get killed all the time pretty much shows they can be killed, so the initial complaint is moot.

Simple fix.

Delete cynos.

Allow capitals to jump themselves.

They wont be able to jump directly on a station... but then again, you wont know they jumped into local to begin with either.

So your problem has very little to do with JF's being safe.... it has more to do with your inability to make low-sec less safe.

So can I haz your stuff now?

This is true for pretty much every ship.

sure thing plz take your meds

Of course you're virtually unkillable if you make no mistakes. That's true no matter what you do. If you're running missions or exploration complexes and drop cans at the acceleration gate warpin and watch dscan/local vigorously, there is no way that anyone is ever going to successfully gank you.

Traveling through lowsec is 100% safe if you fly in a covert ops or use a scout (scout can be in something like a noobship)

Mining in lowsec even is 100% safe if you stay prealigned and ready to warp as soon as anything shows up on overview.


The point is that everyone is human and eventually makes mistakes, and then you can kill them.

Goon Wiki:
As of today, Assault frigates are considered to be largely useless for both PVE and PVP. The reasons are detailed below.

OP I read your thoughts, but all I could hear was: waaaah-waaaah-waaaaaaah

Check eve-kill for hisec/lowsec JF kills. There is no 100% safety.

Riveting argument there, clearly your knowledge on this subject is extensive.

Actually, I think EvE offers too many methods for pilots to feel/be safe.

Omniscient local means you can be 100% certain you are safe at the moment, allowing you to min/max your ship for isk making purposes and not worry about interaction with opponents. This makes people whine, cry, and throw a hissy-fit anytime someone leaves a cloaked hostile in system, because they no longer feel 100% safe. I believe people should operate while under constant danger, and the rewards should basically reflect the risks/danger ever-present.

Covert, Nullified t3's means you can travel from point A to point B without fear of getting caught, without need for travel preparation (i.e. no scout, no bookmarks needed). The only way you lose them is due to piloting error and/or unfortunate lag.

Jump Mechanics allow people to transport ships from point A to point B while completely invulnerable to getting caught. The only way you lose your carrier/JF during jump-travel is by piloting error (primarily bad cyno placement) and/or unfortunate luck (like dc'ing).

Let's be frank, EvE has been becoming safer and safer as it evolves, and adding some danger back into the game is generally a good thing. At the same time, I would rather target local chat being used as an intel tool rather than jump logistics.

You will ONLY get a successful lock if the Loki pilot has an unfortunate lag spike!

Server Ticks (1 hz):
0: Loki loads grid under cloak.
1: Loki double clicks in space (or aligns or hits warp to). This info is sent to the server.
2: A: Loki activates cloak to cloak up.
2: B: Loki appears on your overview. You spam lock.
3: A: Loki is cloaked, (and warping away freely).
3: B: You get the "successful" lock this tick.
3: C: The server invalidates your lock/lock attempt because they are cloaked.
4 or 5: The loki disappears from your overview, flying off safely.

Now, If you are lucky, the loki misses the cloak activation on tick 2, and you get the successful lock prior to him cloaking. I haven't done enough tests to verify how truly successful instalocking ships are at catching IN T3's, but my experience has been it is pretty luck based (and shoddy, tbh).