Player Features and Ideas Discussion

Hello, I play eve online a lot... mainly as a tackler for PL... I have come to be very annoyed at a few "flaws" with the eve online mechanics/server ticks... mainly the fact that eve online runs at 1hz ticks.

This means that basicly everything that happens in space, in eve... only happens every 1 sec/1hz...
Annoyance number 1: Modules activate 1 whole second after you get a confirmed lock on your target, this gives the target an entire extra server tick to warp away before you have them pointed/scrammed... to put this into perspective... if you take 1 sec to lock a target, it will actually take you 2 sec before they are pointed.... (some frigates are about to warp in less than 2 sec, making them almost impossible to catch without a bubble..... more to this later.......)...

Now for my main annoyance, t3 covert ops nulified to bubbles... I am very good at decloaking them, sadly the game mechanics also makes it very hard to point them before they warp... and for 2 reasons... first we have to actually get within 2km of them to decloak, I do this by using skirmish links and a fast dramiel with implants, going almost 9.5 km/s not overheated... this makes me able to pass straight through them, with the overview showing between 750m and 1500m sometimes... the entire time I am spamming lock by rapidly pressing ctrl, (where it will say I can't lock them because they are basicly in the process of cloaking)...
Here comes the kicker... I am able to fly through them, and straight past them, having been in range to stop their cloaking and to decloak them... yet they wont be decloaked because I am going fast enough to cross the 2km range they will be decloaked (on both sides of their ship)... before the server tick registeres it, (1 sec = 9.5km distance traveled for me at max speed)

This happens to me the most, that I can pass through someone without decloaking them, often I can ask the person, and they would also have seen me within distances as close to 14m sometimes.

A covert t3 tengu can be made to warp in 3.1 sec or less with the right rigs, even down to 2.2s with the right implants.... this creates a scenario where it will always be impossible to decloak and tackle before they warp away, unless they spawn next to something after jumping through the gate...

My main problem with the engine is that these ships get away because the game is not "responsive enough". and I hope that we can get to see a eve with faster ticks within the next few years...

oh, and when you say we can just put cans or drones around the gate.. we tried that, 200 drones, and then a GM comes to remove them :3 http://www.youtube.com/watch?v=Ue14P_2mxak ... I don't know if I am most annoyed at the fact that covert t3 can align so fast while warping cloaked and through bubbles, or the fact that the game is not responsive enough to allow them to be decloaked and tackled without putting a ton of objects around a gate

i think increased update frequency would be well received in general, not only for tackling. For example: two kiting frigs which fight each other can move from max point range to scram range within one single server tick and you cant do anything about that.

Its like remote controlling a formula one race on mars from earth ;)

How about if you are gonna gate camp you drop cans around the gate to prevent cloacking ? As there is a very simple solution to catching any Nullified and stabbed T3 what you propose is really, not a valid reason to up the feq.

I'm pretty sure CCP doesn't appreciate spamming cans around the gate. When I say "don't appreciate", I actually mean "they don't want you doing it and will remove them."

Consider flying a slower ship?

I think 2 Hz would be nice to have. Now, I'm no tackler, but it is annoying to me as well than when I carebear and end up, with, lets say, RoF of 7.2 seconds I am wasting large amounts of time (over the time of my carebearing session) reactivating my guns on next target when they pop.

Assuming it would be possible to increase the tick frequency without affecting the server performance hugely. If it is computationally costly then perhaps make the tick frequency function of a node load. For example, there is perhaps 20 guys in node, doing whatever they do, server ticks at 4 Hz, for example. Whoops, local spiked, the node hit, lets say 20% load, ticks slow down to 2 Hz, At 50% you drop it to 1 Hz, and when you hit 80% or more you can drop it probably as low as 0.2 Hz (altho thats already sort of into the time dilatation territory).

I like the idea of having the tick-rate bumped up.

CCP does not care about you droping cans as eve server cluster is seperated by nodes so it only effects one node. And all unanchored cans in space are automatically removed by DT cleanup process. So your argument is really derp.

TLDR; My boosted Dramiel goes too fast and works against me.

the thing is that the actual situation results in event reported in game, but not registered on server.

i've stopped counting the number of target that were pointed, but still managed to warp out.

and NO, they were not stabbed because this happen on pods, shuttles, or any other target that are pointed by a heavy dictor( so the nb of wcs they have is irrelevant).

the process is always the same, you lock and point it, notifications shows up, your mod run, you take sentrys (in low) BUT the ship still manage to warp out.

and this is getting worse and worse.

just yesterday night, i had 4 pods pointed, at 2 km from me, reported pointed by other corpmembers (we have heavy SEBOED ships), and still, they warped out, wich make 50% of the successfully pointed pod able to escape where they shall have been destroyed


so this is getting my full support, fix it, 2Hz tick is really needed