There's no such thing as pod safety. Or safety for that matter.

... or was I just wrong altogether about pod safety in low?

There's no such thing as pod safety. Or safety for that matter.

I didn't see anything about "HTFU." I saw him answering one of your questions. Apparently you didn't like the (correct) answer to one of your questions, and you got buttmad about it.

I would consider it nigh-impossible if you are coming out of a dead ship, since you can hit warp before you appear on their overview. Or if you're landing on a gate/station and become invulnerable upon activation/docking.

However if you're landing in space and trying to decelerate, then warp somewhere else, I am not very surprised to see that you got caught.

Remember than an inty can see where you are going and beat you there. So only fly to a BM or a cluster of celestials so the inty pilot can't tell which one you are flying to.

Using the right-click interface to get to a bm DOES take too long. When doing insta-undocks or other maneuvers that might require instant selection of bookmarks, have the people and places window already open. Current system bms will be green. So you can spam click them without the delay of the context-menu.

As far as I am aware, the align time for a capsule is several orders of magnitude too high for even a Claw to instalock. It's only lag that will get you killed in a capsule.

Just so I know for the future, is there some inty fit that makes this possible, or was it network lag, or was I just wrong altogether about pod safety in low?

He didn't answer my question at all. He gave me a blanket "EVE is dangerous, mmkay?" statement.

To be clear, my question was: "Can a pod align (I know they have virtually no alignment time) and warp faster than an inty can lock and scram them."

My alt lost a pod that narrowly missed the front page of eve-kill.net last night .

Stilleto was waiting for me to come out of warp, had me targed and pointed before I could warp off. This was all in spite of the fact that I was manically spamming warp to another celestial. I was under the impression that even an instalock inty can't pull this off and that the only way to lose a pod in low (provided you know how to spam warp) is to smartbombs.

Just so I know for the future, is there some inty fit that makes this possible, or was it network lag, or was I just wrong altogether about pod safety in low?

Keep in mind that 90%+ of the playerbase sees every question as just an excuse wave their teeny little e-peens around. "HTFU" is just the most utterly pathetic way in which this is done. Feel free to ignore such people, as you are correct in that they have nothing to contribute to the discussion, the question, or life in general.



Pods catching is difficult, but can be done with very specialized ships/tools. Usually this involves a Slasher with 3 x Sensor Boosts and 1 x Warp Disruptor (I've done this myself) or a ship with numerous Remote Sensor Links feeding into a second ship, which then grabs you.

Outside of that, however, catching a pod is almost impossible without a interdiction bubble of some kind, smartbombs (as you said) or just plain horrible lag.

For extra safety many people keep bookmarks anywhere between 151km+ directly in front of a station's ejection port, allowing for (near) instant warp immediately after undocking, and letting you clear the range of any (normal) scramble attempts & buying to time to actually change direction to where you really want to warp off to. Again, there are some very specialized ships/tools that can be used to scramble someone from absurd distances (like 80km+) but even they can't reach to that kind of range.

Thanks for this tip.

It's quite possible to lock and scramble a pod in lowsec, or highsec for that matter, even if the pilot in the pod is spamming warp.

Time-to-warp for a pod is something absurd like 0.25 seconds, while fastest possible lock time is 1.0 seconds (and an inty needs 2614+ scanres for that, ie double sebo). A single sebo would be 2.0 seconds, no sebo 3.0 seconds. Point also appears to go through the second after the lock.

This seems to fit with my experience, which is basically that if you see the death coming, you should almost never get podded outside a bubble (beyond lag, or bumping off something that prevents warp).

Time-to-warp for a pod is something absurd like 0.25 seconds, while fastest possible lock time is 1.0 seconds (and an inty needs 2614+ scanres for that, ie double sebo). A single sebo would be 2.0 seconds, no sebo 3.0 seconds. Point also appears to go through the second after the lock.

This seems to fit with my experience, which is basically that if you see the death coming, you should almost never get podded outside a bubble (beyond lag, or bumping off something that prevents warp).

Just so I know for the future, is there some inty fit that makes this possible, or was it network lag, or was I just wrong altogether about pod safety in low?

Theres so much wrong in this post its barely worth pointing out the errors.

Name one single thing then.

Just for starters, your "instacanes" are nowhere near instant, and are a poor choice for catching pods. With max skills and fleet leadership bonus, a double sebo cane has 736 scanres and thus a 3.549 second locktime, while triple is 989mm and 2.644s - and that's before the extra delay of the tick system.

Time-to-warp for a pod is something absurd like 0.25 seconds, while fastest possible lock time is 1.0 seconds (and an inty needs 2614+ scanres for that, ie double sebo). A single sebo would be 2.0 seconds, no sebo 3.0 seconds. Point also appears to go through the second after the lock.

This seems to fit with my experience, which is basically that if you see the death coming, you should almost never get podded outside a bubble (beyond lag, or bumping off something that prevents warp).

Well. The server uses one second ticks. If the interceptor can lock a pod in noticeably less than a second. chances are that it will.

At least that's my take on it.

To be clear, my question was: "Can a pod align (I know they have virtually no alignment time) and warp faster than an inty can lock and scram them."

Welcome to off grid boosted instalocking.

Pods don't warp instantly.

Imagine a straight line. You're coming out of warp, looking forward.

You decellerate, but you're not at 0 velocity instantly.
Now imagine you spam warp to somewhere in the opposite direction ... that takes time!
You can shorten the timeframe between coming out of warp and entering warp again by warping somewhere that is in front of you. That way, you can use the fact that you're not at 0 velocity after exiting warp to your advantage.

All else ... implants to shorten aligntime might help.

This getting your pod out while your ship is torn to pieces is some kind of CCP **** up.

A long time ago, i think about 2 years, it was impossible to catch your pod while your ship was going to explode. You just spammed "warp to" while you were dying and escaped.

Then CCP changed something (something server something to avoid that the server has to process 100x times the same command in a short time period) and for some time it was a very very bad idea to spam "warp to" even 1x click of "warp to" at the wrong time/tick. Dysnc stuff, you were still in your ship client side but not server side. It added extra lagg and your chances to loose your pod was very high. (I can remember a string of lost pods using Merlins)
Later on the CCP again changed something, it can be bad idea to spam "warp to" sometimes but a moderate 1x "warp to" every second or so gets you out in 99%. The 1% and that is my guess, has to do with you hitting the button at the wrong server tick/ticks, while the server process your ship to pod thingie.

This!

In fact, I recall some Dev explicitely stating that "spamming the warp button is actually counterproductive" as it messes with the ticks, causes lag or whatever.
Don-¦t know if that was fixed, though (probably not, so "a moderate 1x "warp to" every second or so" is the best advice given so far).

But spamming warp button has a more "GTFO" feel to it

Using the right-click interface to get to a bm DOES take too long. When doing insta-undocks or other maneuvers that might require instant selection of bookmarks, have the people and places window already open. Current system bms will be green. So you can spam click them without the delay of the context-menu.

I didn't see anything about "HTFU." I saw him answering one of your questions. Apparently you didn't like the (correct) answer to one of your questions, and you got buttmad about it.

Your align time as well as the lock time on the stiletto probably fell within the same server tick, causing him to get you pointed before you hit warp. Unfortunately you are bound to the timing of the server ticks when trying to min/max mechanics that happen that quickly.

IDK - I use that method but still get podded by fast locking ships. Seems to me that something CCP changed about a year ago in the ship explosions makes the UI unselectable for 1-3 seconds at least on old computers. And that especially when added to the 0.5+ sec lag of round trip trans-Atlantic connections means podded quite often.

Also I forget but do auto-target modules treat pods of ships just killed as hostile? I was thinking not but if so ..That would bypass the wait for overview to show the pod.

Just wanted to dispel a myth.

Warping to something directly in front of you doesn't shorten your align time if your are not moving. If your at 0 m/s it takes the same amount of time to align to any celestial in any direction to warp out.

That may seem counter-intuitive but seriously, try it.

My alt lost a pod that narrowly missed the front page of eve-kill.net last night .

Stilleto was waiting for me to come out of warp, had me targed and pointed before I could warp off. This was all in spite of the fact that I was manically spamming warp to another celestial. I was under the impression that even an instalock inty can't pull this off and that the only way to lose a pod in low (provided you know how to spam warp) is to smartbombs.

Just so I know for the future, is there some inty fit that makes this possible, or was it network lag, or was I just wrong altogether about pod safety in low?

hope this helps.

My alt lost a pod that narrowly missed the front page of eve-kill.net last night .

Stilleto was waiting for me to come out of warp, had me targed and pointed before I could warp off. This was all in spite of the fact that I was manically spamming warp to another celestial. I was under the impression that even an instalock inty can't pull this off and that the only way to lose a pod in low (provided you know how to spam warp) is to smartbombs.

Just so I know for the future, is there some inty fit that makes this possible, or was it network lag, or was I just wrong altogether about pod safety in low?

The server ticks happen in 1 TiDi second.
Clicking pod warp takes spam interval plus your lag to server.
Clicking the lock on takes your lag plus spam interval. (same as clicking warp, mutually cancelling for many purposes with similiar lag)
Locking a pod on a fast lock takes 0.7 seconds.

Rough estimate:
0.7/1 seconds out of the server tick (TiDi makes it easier) ~ 30% chance to get the lock on in the same server tick as the warp command, assuming similiar lag. Might leave something unconsidered here.

Edit: with bad connection / bad computer the pod spam warp lag is higher than a lock spam lag on a good setup, so SSD + good connection wins.