Wormholes

So....looking for the mythical WH to sell for billions :D I got stuck in a C3 with a null static. By stuck I mean, I scanned down an ambush at the exit to high sec when I was done exploring the WH. Before thinking about returning, I jumped into null sec and did a little exploring. I must have spooked the alliance, one person in space when I came in..l within 5 mins there were 40 pilots of the same corp. That is when I went back in the WH. I had a few of choices:

1) Run my luck against the ambush party, see if I could jump through the WH back home before being blown up. (I am in a blackbird focused on scanning, not really tanked or any dps to speak of. I could handle a few rounds of volley fire and my weapons are more to deter solo'st looking for me. About 50mil worth of scanning gear in the 5mil black bird.)

2) Jump back into null-sec and take the long ride home hoping I dont run into stargate campers (2 stabilizers so I should* not be scarmbled; but again, I can only handle a few rounds of fire from a couple of cruiser+).

3) Log and hope they dont find me within the time limit.

I decided not try (1). They had TII ships and I figured probably a bubble. I thought they would get me in 2 rounds of fire and not sure I could make it out that quick.

I was very curious about (3). I was cloaked and no aggro. I was over 6AU from the party so they would not have seen me even if I ewarped towards them. At the least, I would have been 5AU from them; so no d-scan from them. I don't think they had scanners because they were talking smack the whole time but never once warped on me. (I was using a TII Cloak so they would not have found me). I know when you log, your cloak is removed though and you ewarp 1,000,000KM.

I decided to use (2) and took the long way home. The null corp must have thought I would not do anything as I found them 3 jumps away when I came back.

I made it home safe and sound but wondering if I should have used (3). Do you think I would have been safe? I wanted to stay in the WH because the sticks appeared to be dead (no force field) and I figured to ambush corp was just hunting for the night. Thoughts?

I always used the rule of .. If the combat scan probes are not out. They will not get your ship scanned down in the minute that you sit idle. Figure time to launch probes. A couple of scan cycles and then your already gone. But if you see combat probes on dscan...well...that is a little tougher to decide.

I never thought about checking d-scan for combat probes. I always use it for ships and structures. I never checked for that option on the filters, I will have to add that. That is a good advice!

Two other things...

1) You said you *thought* the campers had a bubble. Why? Did you see one on dscan? Did they have a HIC? If not, then they did not have a bubble.

2) dscan range is 14.3 AU, not the 5 or 6 that you seem to think.

Also a nullsec run home would probably have ended in a bubble on the transition gate no amount of warpstabs are gonna help you then...

You should always always have scan probes on dscan results when flying in wspace. I keep them on all the time, but they are also useful when in an anomaly in kspace as well.

Almost always someone will have a cloaked ship to try to find you, so seeing the probes on scan is your only hope to detect them.

Until you run into someone doing proper hole control on a sieged system :| (fairly rare tho).

If OP thought that d-scan range is 1 AU he must be very new, have a long list of losses or be very lucky *g*

If not under aggression, it is always possible to safely log off in space. Pick a destination that is far away from the people hunting you and also far away from your current position, and be sure that it's not a 'safespot' you've already used while being hunted by the guys you're trying to escape from (they could be waiting for you there).

Then initiate warp, wait until warp begins, then log off. Your ship will go all the way to the point you initiated warp to, then after coming out of warp, your ship will immediately re-align and do the 1m km emergency warp. During this time it is impossible to pin your ship down (because it's warping), and all this time counts for the timer until your ship disappears. In most cases it will be gone before it even does the emergency warp. Under no circumstances can someone scan you down at your final position and arrive there in time to put a point on your ship.

I'm not sure it works like that on the timer, if you logout mid-warp it seems to not start the timer til you end the warp your in. I've not tested it specifically so might be wrong but I've noticed a couple of times when initiating a long warp to an alt then logging off once in warp from the alt's perspective the other ships still lands on grid, aligns out e-warps and stays in space ~60 seconds.

LOL! Good luck with that.



IMO one of the joys of eve is that you have so many choices on how to respond to any particular situation. Sometimes I make a patently stupid choice and die, sometimes I make vaguely stupid risky choices and get away with it, and sometimes I make a variably sensible choice … that often works but, even then, sometimes fails.

Logging out?

Logging out, even without aggro, is a risk if there are combat probes in space. The risk is not huge, but if the probes’ owner is skilled and is on-the-ball (e.g. adding you to their watch-list so they know when you logout) they are likely to be able to find your ship before it disappears.
In those situations I tend to find a safespot, stay cloaked (but with my ship moving in a straight line), and wait … usually going off to do something else, either in eve or RL. If the system is dangerously hostile I rely on downtime to log me off rather than doing so manually.

Running a nullsec gauntlet?

Some nullsec systems are ‘shallow’, even with direct hisec connections, and some are very deep with dozens of jumps before you get to lowsec / hisec. If you are not savvy to the ways of nullsec then running a long series of nullsec gates can be a fatal undertaking. If you are savvy, and patient, then it’s just a bit time consuming and tedious.
Having done this for a longtime now I have perch bookmarks and safepots for most en-route nullsec systems, and when I do endup in a new one I take the little extra time to build myself some bookmarks for next time. If I don’t have a perch on the outgoing gate I use the system map to identify a line that is unlikely to be bubbled and I warp to a location somewhere in that line – usually 100km from a planet building a semisafespot BM on the way. I then warp to the gate at range and, when I land near the gate, I burn in an appropriate direction to make a perch bookmark for that gate. This adds 5 or so minutes to each system, but pays for itself bigtime when you’re next in that system.

Running a wormhole camp back to hisec?

This is a bit of a 6P situation. You know, Prior Preparation Prevents P.i.s.s Poor Performance?
Depending on what I am doing, when I jump into a new w-system I virtually always bookmark the wormhole itself and then burn away to a nearby perch, say 300km below the wormhole, and bookmark that location. This takes me a couple extra minutes but that second, perch, bookmark lets me safely warp back ongrid with the wormhole and observe it … with minimal risk of being caught in a bubble.

If you do not have such a perch BM, then you can try to find a location near enough to the WH to ‘see’ it on DS. If you manage that you can use your DS to checkout ship types and whether any bubbles have been anchored. If there are no anchored bubbles and no HICtors / Dictors then you will be able to safely warp directly to the wormhole and exit.
You did directly bookmark the wormhole as you entered the system, didn’t you? I mean, you took a bookmark based on the main screen bracket or your overview, and not on a probe scan fix? This is very important here because probe-scan bookmarks land you about 7km from a wormhole … which can be fatal if it’s camped … whereas BMs taken from overview / brackets land you at zero.

If you cannot get an ‘eye’ on their camp then I’d counsel patience, rather than risking a jump to a camped WH. Just wait them out. Worst comes to worse, you can wait for the next hisec static to spawn, scan it down, and exit to hisec using it. If you know who they are add them to your watchlist. They may logout shortly … suggesting that the WH is no longer actively camped.




^^ This!

If you have popped out into null and triggered a response from the locals, you are probably keeping them from their wallet-padding. Even if they are PvP-dedicated nullsec dwellers they will be spending a fair bit of their home-time gathering isk to fund their other more exciting activities.
So, if you do not provide them with a stupidly easy quick kill, they are soon going to lose interest … especially as they see a few ticks of lost income passing by.

When I am very nastily camped into a system, and it has to be very nasty for me to consider myself camped, I just cloak, minimise the window, and go do something else in eve or RL. I check from time-to-time or just wait for DT to log everyone in-system out.




I am with Derath on this one. I’ve jumped many camps in my T3-hauler and never once been griefed … well, other than the occasional smak-talk attempts at griefing. For day-to-day moving around I use a much cheaper covops-frig but for very nasty locations, or for hauling valuable w-space booty out via nullsec, I use a dual-prop / nanoed / stabbed / covops / nullified T3. These ships have no tank at all, no mods that increase their sig-size, and are rigged to reduced align-warp time.
These ships ignore bubbles and are cloaked and into the next warp before most anything locks it. It’s certainly cloaked and gone before a HICtor can lock and infinipoint it, and would need several seboed ceptors to lock and point to even think about slowing down.

If you doubt this then I suggest you try some tests yourself, in hisec (or in SiSi). See if a seboed HICtor or ceptor can get a lock and point on you before you cloak / warp.