We discovered another funny side effect of all this which I forgot about. The Rancer type smartbombing gate camps no longer work for ships that appear instantly, since you simply don't load grid until you are already on the gate. Negative ten won't be too happy about this.

i'm still obsessed by the 15+ au/s bubble immune cyno ceptor traveling 3 systems/min i pointed out in another thread. Now it will go even faster with warp implants, light cyno out of grid or even out scanner and then a sabre will land on you in 1.1 sec.

I think they will quickly figure out the timings to mash F1-F8 when the unlucky enter local. Even better if they have a scout watching the entry gate, to tell the smartbomber what ship type is coming.

When people unsub their supers and you lose 1000s of active characters maybe you'll listen.

I realize this probably has to do with server ticks, but this doesn't really excuse it and it entirely broken mechanic.

I can totally see alliances going "No more supers in 0.0 until this is fixed" sort of thing going around. Not to mention tier 3 snipe BCs will simply stop being used as they will get insta-bubbled every time without seeing it either, and the list goes on.

We discovered another funny side effect of all this which I forgot about. The Rancer type smartbombing gate camps no longer work for ships that appear instantly, since you simply don't load grid until you are already on the gate. Negative ten won't be too happy about this.

Come on, you guys already knew this seeing as this is the main reason for all the PL + other elite PVP tears in this thread.

not sur it would work, the ships now insta appears on gate, and in fact, the moment they appear they are already within the session change.

and if they are not on your grid, you cannot damage them from game echanic pov (think about it like the grid walls, you are at 2Km from another ship, but with a grid wall between you two: you cannot see or even damage him with smartbomb).

same here, the moment the target enter grids, it is already on gate, within the session change (so it's invuln)

It's all sounding a bit broken on the deceleration side.
Insta appear on grid and ^^ this.

These are the game engine not keeping pace with the speed from the sound of things as such it should not be release in this state.

Propose that deceleration remain the same as today and only the acceleration phase is linked to warp speed.
No one cares if a ceptor insta disappears as it warps off , its not game breaking.

Still delivering big speed improvements for smaller ships and enabling them to get in front without breaking defensive game play.

or actually solve the REAL issue wich is the server tick, thus you make those proposed changes not game breaking AND solve others issues with locking times, decloacking, modules failing to apply, weird timer / desync on various modules / weapons....


the issue is known, the solution is (according to CCP) pretty easy.......so WHY THE HELL have this not been done yet?

this would solve a metric ton of odd / weird mechanic behaviour AND allow the proposed changes to actually be not broken

would only work if the entire code base is written for a variable tick rate.

If the current codebase assumes 1 tick a sec then a 2 year rewrite to make the entire games codebase variable tick rate compatible is not a solution that is going to be delivered with rubicon.

Also all those extra calculations are going to increase load and tick rate increae will increase load meaning more servers with less sols per server to deliver that performance.

It has already been said by ccp that changing server tick is easy

Can you link please ?
I'd like to read.

Because of the current server tick, EVE is one of the most kind MMO's to poor internet connections; I know someone who could play via satellite, 2000ms ping, (2 seconds!) reasonably well once any fight was under way, though he would simply find himself in a station, right after jumping into some insta-lock camps. FPS games like Battlefield were impossible.

I don't believe we're getting any change to server tick any time soon. More than just increased server load, it would also knock out some subscribers.

Looking at deceleration (only) is still worth considering, but in post #190, CCP Fozzie replied directly to a question that mentioned deceleration, and was not persuaded to change anything then.

here it is: https://forums.eveonline.com/default.aspx?g=posts&m=3781114#post3781114

Come on, you guys already knew this seeing as this is the main reason for all the PL + other elite PVP tears in this thread.

if you consider game-breaking mechanics that are being pointed out by the people who are most likely to use them to be tears, well I'm sorry for you.

Yeah, because basically you are crying about not being able to use a broken mechanic in the first place.

TBH, at the speeds a frig exits warp at it should be rather hard for it to get hit by 8 staggered smartbombs - unless more than one go off in a single tick - which is the only reason people die to one (and perhaps two) BS smartbomb camps (unless they shuttle / pod warp).

So, it was broken before, sounds like it will be broken in rubicon as well, except we now get all the elite smartbomb pvp'ers crying about the lack of killmails - I suggest moving away from the gate and trying less elite PVP .

Because of the current server tick, EVE is one of the most kind MMO's to poor internet connections; I know someone who could play via satellite, 2000ms ping, (2 seconds!) reasonably well once any fight was under way, though he would simply find himself in a station, right after jumping into some insta-lock camps. FPS games like Battlefield were impossible.

I don't believe we're getting any change to server tick any time soon. More than just increased server load, it would also knock out some subscribers.

Looking at deceleration (only) is still worth considering, but in post #190, CCP Fozzie replied directly to a question that mentioned deceleration, and was not persuaded to change anything then.

Folks proposing increasing the server tick rate are pretty much wrong for this reason. Increasing the server tick rate is already possible - you've seen it demonstrated in the alliance tournament.

However, the real issues with ships insta-appearing on grid are more than likely related to the time delays in getting the server information from London to your client. These effects already exist - the game is slightly slower in the US, noticeably slower in Australia, and pretty bloody quick in the UK by comparison. ( Yes, I've played in all these locations) Now that ships decelerate faster these issues are much more apparent.

Yes, smaller ships warping faster is fun and ultimately its good for the game. But ships insta-appearing on grid is not. Small ships need to decelerate slower so the server has time to update the client.

i am lucky to have optical fiber connection, with a very good ping up to CCP server, and yet, with my two accounts i STILL encoutner the various issues i mentionned, and for the one we are talking about, the "insta appear" thingy.