Ships & Modules

2) Align time. Today Entity shed some light onto how Destiny works. The key point to the numbers you got and the numbers you have in EFT is that method you're using to measure align time is naturally flawed. It would work semi-okayish in 100x slowed down by TiDi system, but using stopwatch in normal conditions leads to wrong results. The proper way would be:

Open logserver, jump through gate/fullstop. Start aligning. Then, look for entries like:


First line is actual start of align process, second line is issued on warp 'commit' (when you become invulnerable, ships which have you locked lose you, and so on). It lets client to preload objects in the target grid, and it's issued only on warp commit because it would be exploitable otherwise (everybody knows you can't stop warp when it's already commited). This example shows charon align process with align time equal to 39.58.

Two notes here:
1) Align time is always rounded up to seconds (due to server tick nature). It doesn't matter for align time if your dram has 3.01 or 3.99 align time, both will take 4 ticks to completely perform align (though, it still matters for your general agility)
2) Subtle time difference in log is explained by fluctuating delay of transport layer

Crusader with 3% agi implant (2.95 align time):

Crusader w/o implants (3.05 align time):

You see how this theoretical 0.1 second difference results in 1 second real difference, yeah? Please note TiDi will just make warp-off process longer, but it won't change any breakpoints, so this mechanics applies to all ships in all systems regardless of TiDi scale.

Stopwatch method adds additional layer of several seconds... err, why? Most likely because simulation (server processes whose synchronized representaion you see in your client) takes one additional tick to full-stop your ship + 1 tick to start warp acceleration. Also, often yet another tick is added when you hit warp and stopwatch simultaneously (server doesn't start warp immediately, it waits for start of next tick). But the point is that you become invulnerable before that, before you actually see your ship entering warp on client side.

That is, align formula is absolutely correct. We don't care how client shows it, because on server ship enters invulnerability state properly. We could round up align time to reflect actual align time, but as it's often used as ship agility factor - i doubt we'll do it. Maybe when UI is refined to show both numbers, but it's not going to happen tomorrow.

why the f-ck do people use these stupid file sharing sites like rapidgate that are not friendly to download managers and force you to wait in the queue again if your download fails.

I'm getting constant error message when I attempt to update my existing skills. The error reads that my key is not good it must be updated.

I first tried my old API that has worked forever and I've tried a new API. Neither one will be accepted by EFT to update my character.

I have attempted to get the key to work several dozen times.

What is up with that?