The first sig I resolve is a wormhole, but by its signature strength it is not a K162. Therefore almost certain to be our static. I don't fly to it yet because it is possible (though unlikely) that none of the other signatures are wormholes. And I do not want to unzip mindlessly. Three more sigs are new gas sites.
Imagine this wobbling (image from Penny) |
Now I check my PI to see if I need to move goo, which is best done as zipped up as possible. I don't need to do anything. Great. I'll instantiate our static and see if I can get a route to highsec that way. I fly over to the static, being careful to align first so I have the maximum time to get into the next system. I am in my Manticore; perhaps I will be lucky and surprise someone. But, no. The static, like the C2, is in EOL. Evidently the C2 people searched it down and instantiated it 12+ hours ago.
This sucks. No way out of my system other than EOL wormholes which I do not know the timing of. They might pop in a minute, or in five hours. No way to know, or even to get a decent idea, other than to recall the timing of my last static, but I deleted that bookmark already.
I could use mass to pop the static wormhole to recreate it. But I am not so keen to play tonight as to want to pop wormholes by myself. And the thing should vanish on its own if I just wait, on average, 2 hours. I'll just read a book while I sit watching the C2, which ought to evaporate first. Bye, EVE, I'll have an eye on you right over here.
It's about 7:30 now.
8:30. Wormhole still there.
9:30. Wormhole still there. It's kind of running longer than I had expected. But now it must be short time.
10:30. Wormhole still there.
11:00. Shurrrrp! The wormhole is gone. Finally! If I had known how long it was going to be... but I didn't. No use backprojecting how I'd live differently if I was able to know things about the future.
You could have borrowed one of our pilots. Although he claims it's just confirmation bias, it seems that dying wormholes tend to collapse within two minutes of his jumping through.
ReplyDelete