Basically the topic subject.
I slid in a fw plex. I preactivated modules, clicked approach and started spamlocking the target. I have failed to lock him despite him clearly not warping away.
I fail to lock him cuz of my warp invul at 16:46:01. I (probably) start locking him at 16:46:02. 3 seconds later, at 16:46:04 it says my attempt to target failed.
I’ve seen this happen occasionally too. Unlike when a target is ineligible for locking, where you immediately get a message, it goes through the entire lock process, and then goes “lock failed” afterwards. I don’t know what causes it.
I think I do. The client has to make an educated “guess” what time that lock would be established to run it’s locking animation. Should the target still be eligable at the end of that timer, a proper lock is established. It’s possible that the target manages to become non-eligable before that happens, as the client can’t predict every possible event that might affect this.
