Warfare & Tactics

No, this is not how the server works.

It gives out information (or however you want to call it) every 1 seconds, but when you send data to the server, as in f1ing the cloak or ctrl-clicking lock the server will determine who did what first. Do you really think the server only ticks in 1 second intervals and in between that nothing else happens? Incoming information isn't processed in one second intervals.

The only way to get instalocked in a cloaking ship is because of client or network lag, most of the times the issue is that people click the cloak too early so it doesn't engage, or they click it too late. In that little timeframe people send their locking "request" to the server, the server processes that before the cloak "request" comes in and voila, lock before cloak.

Maybe that's how it works, though I would be surprised if it was.

Don't forget that in Factional Warfare there a loads and loads of stealth bombers flying missions through camped gates the whole time.

They rarely get caught. In fact I have never seen one get caught unless they get bumped by a ceptor or get the bad luck to spawn with 2500m of someone.

If it worked like this I think we would see a lot more getting popped.

I believe a dev had posted in the past that the server used to prioritize these commands that come in the same tic depending on the command. Specificially he said a warp out command would have priority over a warp scram command.

If this is now random I wish ccp would tell us.

insta lock r done by remote sensor boosting fleets. go market - remote sensor booster - show info !!!!!!!

One of the biggest and most important factors here are that players don't realize very well how big the server roundtrip - including calculations and checks - really are. CCP, like all mmo "providers" have as one of the top priorities as well as challenges(!) to make the game appear as smooth and lag free as possible - often "cheating" by expoiting client side mechanics that the human mind doesn't notice as clearly as others.

With the above, I am simply stating that your "ping" (some two-three figure ms unit) will NEVER be a reliable factor when it comes to certain functions (those that cannot as easily be "hid" client side), and neglecting them in search for "other explanations" is always going one step too far.

Do any of you think it is a coincidence that it is always a function where a logical "check" of the interactions between players (did he lock or not - yes or no - there is no client fasade to smooth this out) that always "bugs"? That's a rethrorical question ofc.

In short - several things could have happened at the particular case described in the OP. it is however rather pointless to speculate, when the fact is latency is always a lot more than you think and *can* always be the explanation. Stating "I had no lag" is simply null-worth. We all have a lot more lag (higher server round trip time) than most of the game's functions let us be aware of. The second one understands that - many "bugs" (definate player interactions mainly) become 100% logical.

If CCP didn't cut corners (all mmos do this) playing on our human awareness and all checks (incl hitting rats/whateverlowpriorityfunction) actually made the linear route from client to server to calculations/checks back to client -> "your lazor hits rat for loads!", people wouldn't bear playing it due to a massive sensation of lag. This is a fact and something mmo providers have to compensate for as much as possible to give the *impression* of the most game functions actually working at pace of listed "ping". This is never the case in reality though and some things (like definate yes/no checks that has to be relayed to players) can't be smoothed by the client cutting corners.

"Cloak of shadows" bug in WoW. Locking/cloaking bug in EVE. Just succumb to the fact that they are not bugs, but extremes of examples where the full server roundtrip is needed, and a full server roundtrip is always way longer than your ping (calculations and checks are NOT instant and a lot of compromising is needed on locations/commands etc - this is much more processor heavy than some might think).

It doesn't get better than this with current internet/server technology - CCP literally have to compensate also for slower connections to make for an overall 'seemingly' lag free gaming experience. Just be happy that it's hard to reach locking times that closes in on real server roundtrip times but always assume your server connection (when it comes to player interaction commands) is in the second(s) range and not your two-three ms digit "ping", because that's the truth.

Lost my ship and pod that day too, they had an orca parked at the gate too that was boosting away.