If you have war against certain high sec corps/alliances it really means that high sec is no more safe place to move.

Yeah, if HICs/Lokis/Whatevers fit enough SeBos and there's not much lag, they can indeed lock pods before they warp.

Probably had a whole bunch of Remote Sensor Boosters on him. You can get lock time down too about 1.4 seconds on a Broadsword if you poor on the Rebo's

Probably had a whole bunch of Remote Sensor Boosters coming from a Neutral Alt on him. You can get lock time down too about 1.4 seconds on a Broadsword if you poor on the Rebo's

No remote sensor boosting alts. You have any idea how many pods/cloakies are targeted with no more than a muttering of "arse" "almost" or "poop"? Every now and again a get tha jackpot. There's no magic. It's 50/50, ya get tha lock, ya don't get tha lock. It's all fun tho, only a game, for every kill there's a load more ya miss. Hi 5's for taking it in ya stride and not rage quiting. Hopefully see ya around with some nice loots for Sexy. Time. to scoop up. :)

When a warp field disruptor is active, no remote effects will work on the HIC.

No remote reps, no cap transfer, no shield transfer nothing.

This includes a scripted infinity point.

He had a rack of local sebo's.

No remote sensor boosting alts. You have any idea how many pods/cloakies are targeted with no more than a muttering of "arse" "almost" or "poop"? Every now and again a get tha jackpot. There's no magic. It's 50/50, ya get tha lock, ya don't get tha lock. It's all fun tho, only a game, for every kill there's a load more ya miss. Hi 5's for taking it in ya stride and not rage quiting. Hopefully see ya around with some nice loots for Sexy. Time. to scoop up. :)

Even if we've been spamming warp before the ship destruction? I never had any issues with this well known pod saving tactic in 6 years of game. I thought that was making pod warp pretty much instant after destruction.

Don't forget, the overview now updates more quickly than it used to.

Likely a contributing factor.

apllied equally on both sides => 1-1=0 => does not matter

I wasn't disputing your math, but the fact remains that if your overview now updates a second or so quicker you now have a better chance of targeting the pod after ship destruction.

Hi everyone,

How is it possible to fit a broadsword that can kill pods in epire during wars?

...

I want to know how is that possible.

Thanks for your help!

Don't forget, the overview now updates more quickly than it used to.

Likely a contributing factor.

There was a thread over this pod not warping instantly earlier. Some said those commands spammed cause the server to lag out and wont happen as fast as you had hoped or something. Maybe you can go back and find it.

Even if we've been spamming warp before the ship destruction? I never had any issues with this well known pod saving tactic in 6 years of game. I thought that was making pod warp pretty much instant after destruction.

me neither, except once there was that bunch of intis on my ass, and a little lagg...



Ok, to clear this up, maybe soneone from CCP can confirm or disclaim this:

Order of things happening:

1.) Ships explodes
2.) Pod spawns

3.) Server notifies Pod-owner and aggressor simultaniously that there is now a pod and no ship
(delay equals Ping of the respective player)

4.a.) Pod-owner klicks "warp" (has been klicking frenetically at least twice a second all along)
4.b.) Aggressor klicks the Pod ( to lock and then point in the moment the lock is active)
(delay equals each pilots individual reaction time)

5.a.) Pod-owner sends "i do wanna warp" to the server
5.b.) Aggressor sends "i do wann lockit" to the server
(delay equals Ping of the respective player, again)

6.) Server processes "warp" and "lock" requests according to the times of when the information was recieved, not sent

(assuming Pod warps instant = 0,0 seconds)

=> Real Lock Time = ( Lock Time - (Your Ping - Enemy Ping) * 2 - (Your Reaction Time - Enemy Reaction Time) )
=> to survive, Lock Time - ( Your Ping - EnemyPing) * 2 - (Your Reaction Time - Enemy Reaction Time) ) must be above zero :D

Assuming you click "warp" twice a second, Your average reaction time would be 0,25 Seconds.
Assuming the Enemy has insane Luck and/or insame Skills, we just assume 0,1 Seconds here.
Lets further assume therese a slight, but not really noticable lagg on you side, we assume 150 ms = 0,15 Seconds here.
For the Enemy we assume a standard connection with a Ping of just about 50 ms = 0,05 Seconds.

(Pod warps instant = 0) 0 > Lock Time - (0,15 - 0,05) * 2 - (0,25 - 0,1)
<=> Lock Time < 0,35
=> Lock Time needs to be below 0,35 seconds to get the Pod.

Now that 0,1 seconds is acutally no realistic reaction time, more accurate would be 0,3 but lets just say 0,2 (=1/5) and,
You might klickt faster than twice a second, lets say every 2/5 seconds, for some simple numbers.
(average reaction time would be 1/5 seconds then)
Lets see how the Ping plays out in this case.

Then:

0 > Lock Time - (YourPing - EnemyPing) * 2 - (0,2 - 0,2)
<=> Lock Time < (Your Ping - Enemy Ping)*2
<=> Your Ping > (Lock Time)/2 + Enemy Ping

This means, your Ping must be at least as high as Your enemys plus half his locktime, would be something between 500 and 2000 in most cases.

And one usually has a ping below 500, so therefore the Pod is safe.
And as well, this proves: Lagg Kills!

I had a weird occurrence once. . . .

My ship got blown up in low-sec and I was able to warp my pod out and jump through the next gate.

I checked my loss mails . . . and my pod was listed as a loss.

Petition with GM confirmed that the logs did indeed show I had lost my pod, but that I still had my pod, clone, and implants. I was asked to file a bug report. (-_-)

Another nail in the pvp coffin. Now we can't fly in highsec or lowsec with implants without risking an extremely expensive loss. Or alternatively we can fly with no implants in and lose training time.

Hypothetically, you could mitigate your losses by winning the occasional fight.

ice ******* burn Malcanis shiiiiiiiiiiiiiiiiit

This is the second thread Ive seen about pods getting caught. I wonder if it has something to do with the overview changes CCP made. The overview use to update once every 2.5 seconds. Now it does so once a second. The result is they see your pod sooner. If fact, they could well see your pod before you do, depending on local internet latency of your and their connection. Result: you can get locked even before your client has been informed you are in a pod.

CCP, maybe you should take a look at this. It seems to me that to be fair everyone should get the same information at the same time. Something like the server, once the target has taken sufficient damage to explode, telling all clients "do not explode the ship and spawn the pod until 04:14:32" so as to give time for all clients to get the message.

The issue appears to have to do with the "spamming warp" tactic. If you have commands queued up through mashing the "Warp" button as you transition sessions when your ship explodes, it appears that there is a de-synch between client and server whether your ship or capsule is in warp or not.

If you check your logs, it will show that the client believes you are already in warp and refuses to acknowledge the command. I have seen this on several occasions for a number of pilots.

Latency does not appear to have anything to do with this, as the warp command will fail for several seconds (perhaps even indefinitely). I have confirmed my own connectivity to Tranquility to be in 140-150ms range consistently with 0% packet loss. This is not a network connectivity problem.

Even if you don't get podded at this point, you will not be able to warp to your originally selected destination. You will, however, be able to switch destination and warp to it without any further issues.

Workaround: Start hammering warp *after* your ship goes explody.

Hi everyone,

How is it possible to fit a broadsword that can kill pods in epire during wars?

Yesterday i bought a Vigil (yes even old players enjoy some Vigil goodness). That ship wasn't fitted yet when i crossed the way of a war target Broadsword on the other side of a gate.
I thought, good luck catching me and proceed to warp.

First surprise: He warp scrambled me, ok fair enough, he might be super sensor boosted, and being an empty Vigil i thought well who gives a damn, so proceeded to spam warp until i pop so i can save my pod.

Second surprise: While i was spamming warp since he got me my pod should have been able to escape. Particulary in empire since there are no bubbles etc.
Well no!!!!!! As soon as i popped my pod was locked!!!!!!!


I want to know how is that possible.
Also, looking at my killer KB i can see that guy is the pro of empire pod killing, pretty much all his victime got pod killed in empire. If you wanna look for his name: Bulletproof Cupid

Thanks for your help!

I play from Australia. Due to graphics lag, network lag and general latency, I usually get podded before my ship has finished losing structure.

My greatest complaint is the habit of the camera to reset to 0m range when the target the camera was previously focussed on is destroyed. At about the time my ship is in deep structure, I know I have been podded because the camera resets to 0m in preparation for playing the death explosion of my ship. The catch here is that my computer becomes entirely unresponsive for several seconds, so I can't click "warp to" even if I was able to pick exactly the right moment to do so. I just sit there watching the death explosion try to render itself using features my video card doesn't support at about two fames per second, with all the fans in the computer doing their est jet-on-takeoff impression.

About five seconds later the HUD starts blinking red and white due to the client apparently getting confused about whether the thing I am flying has hit points to not. About ten to twenty seconds into this experience, the game will busily be trying to render the hangar where my medical clone has been resuscitated while simultaneously trying to play the shield, armour and structure warnings from the pod being shot up, pop up the dialogue and voiceover from Aura telling me I have been podded and do I want to learn about clones, followed closely by my system shutting down from thermal overload.

All this because CCP decided that resetting the camera distance to 0 would be cool.

Of course someone might come along and suggest I need a new computer: this will happen in time (new iMac range due out in a month or so). My story relates to the past and contains a useful point for CCP to consider :P

This is a relatively new thing I have experienced and wonder if there has been a small change somewhere, unannounced by CCP.

The server is running a simulation step once every second (since Bloodlines that is). Before we got TiDi movement commands got prioritised over any other command type. That means if you got your IP packet with your warp command to the server in the same second then the warp scram command, you warped off. That's not the case anymore.

There is no reason for whining tho. Before Bloodlines I was able to scram shuttles before they warped from a gate.

Your client usually pauses for a couple seconds when your ship 'splodes. Its loading the pod graphics/sounds/etc. Sometimes my disk thrashes for a few seconds and i end up in station instead of in warp.

Its been happening for a looong time, and even though i can play 2x clients on max graphics smoothly, it still locks up.

Your client usually pauses for a couple seconds when your ship 'splodes. Its loading the pod graphics/sounds/etc. Sometimes my disk thrashes for a few seconds and i end up in station instead of in warp.

Its been happening for a looong time, and even though i can play 2x clients on max graphics smoothly, it still locks up.

i agree you probably had a sec or 2 with lag that should be enough to lock a pod if you have 100-2000 scan ress

How is it possible to fit a broadsword that can kill pods in empire during wars?