Life in a Wormhole: Welcome to the Alliance #eveonline

The war declaration I mentioned yesterday came on the last day of our month-long trial period with the Alliance, so while we were prepping for a bit of alone time in wormhole space, we were also going through the minor paperwork that comes with full membership; apparently, we managed to pass muster and got some pretty glowing reviews from the other corps in our wormhole.

As an added plus, Walrus and Cabbage offer to make our ‘trial’ arrangement permanent, so thankfully we don’t have to relocate, either — we’re not ‘guests’ anymore; just the third ‘home’ corporation in our system. It feels good. We become full members within an hour of the wardec going active, which I personally find kind of amusing.

Not that the wardec has no effect at all — it does hinder us a bit (at least it hinders me), simply because we’re keeping our persistent connection to known space closed for the duration. This isn’t a problem for the obvious reasons — if we really needed supplies, all of our corporations have alt characters outside the alliance who can haul stuff in — the ‘problem’ is that we’re taking this opportunity to do some mining in the home system, hitting the three belts currently available in the system while the chance of outside interruption is low.

This increased security is due to the strange nature of wormholes in general. The way it works is that while any given wormhole system has one or two persistent connections available, they are only potential connections — they show up on scan, but they don’t “activate” until you actually warp a ship out close enough to them to show up on the same tactical overview grid as the wormhole.

Basically, what that means is that until you actually fly close to a wormhole, is has no ‘other’ side; it’s not connected to anything until it needs to be (I smell some database programming efficiencies here). This affords a wormhole dweller a fair amount of security just by leaving their wormhole connections alone; since there’s no ‘other’ side to the wormhole, no one can use your unvisited persistent connections to enter your system — the only way to get unexpected visitors is if some other system’s wormhole connection randomly selects your system as its destination point when it’s activated. This is (a) not incredibly common (happens to us every week or so, maybe) and (b) pretty easy to watch for.

So, given all that, and the fact that we are already going to leave our LowSec exit closed, Mining Ops are set up, with the accompanying request to “keep all exits closed unless necessary”, which means that our class two connection should be left alone as well, unless you know you have the ability and time to collapse it when you’re done.

I don’t want to endanger my fellow alliance mates while they shoot rocks, and Berke’s not around much this week, so I’m left with few options for the next couple days, twiddling my thumbs while I pondering the fact that I didn’t remember to bring a mining ship into the home system.

I’m not the only one mildly displeased by the current situations, though; surprisingly, it’s the pilots in the system doing the mining who are looking askance at the whole set up, and the reason is that demon of wormhole mining: refining loss.

Miners in known space don’t generally have to deal with this kind of problem; when they mine, they haul the raw ore back to a station and, assuming that their skills are good and their standing with the faction that controls the station is good, they will realize close to 100% return on the refining process. In short, if they mine X amount ore that should, on paper, yield Y amount of minerals, then Y amount is pretty much exactly what they’re going to get.

Wormholes don’t work that way. There are no stations, and the best refining facility you can set up at your tower yields only a 75% return on the refinement process, which (if you’re selling the minerals for profit) is a pretty major cut into your profits and (if you’re building stuff) is a pretty damned inefficient way to get the materials you need for manufacture. On top of that, any kind of effort to haul the raw ore out into known space where the refining percentages are better is hampered by the fact that the ore itself is extremely bulky and basically a huge pain in the ass to move out of the wormhole in any useful amount.

And mining is already kind of iffy in terms of profit in the first place: even in high security known space, a pilot with the standing and ability to run level 4 missions will make far more ISK running missions than they will with maxed-out mining skills, unless they’re running something like four mining accounts at the same time. Even with the the existence of the rarer, more valuable ores inside wormholes, shooting sleepers is still almost always an exponentially faster and more effective way to make some ISK, even assuming perfect refining, and without that, mining becomes a very, very, very last-resort activity, even for pilots with a long list of perfect industrial skills.

Even carebear wormhole dwellers balk at 'mining op' fleet invitations.

Which is why my fellow pilots are spending their time in solitary talking about a Rorqual.

A what?
A rorqual-class capitol industrial ship is a kind of big-(big-big-)brother to the Orca. It is capable of performing a number of functions (mobile ship hangar and clone bay being of particular interest in known space), but the most valuable function to a group of wormhole miners lies in its ability to compress ore; it doesn’t refine it into manufacture-grade minerals, but instead makes them far more portable in their raw state, which lets you accumulate what would otherwise be unmanageable amounts of ore and — thanks to something like a 140:1 compression ratio — smash them into a dense package that can be far more easily hauled to known space.

Obviously, this is a great solution to the problem.

There’s just a few problems:

  • Cost: Between the blue-prints, required training books, and materials, the Rorqual costs several billion ISK to make, and to train up pilots who can us it in the way I’ve described.
  • Mass Limitations: All the minerals that Rorqual manufacture requires have to be acquired from somewhere — either purchased and hauled in from known space (which goes back to the whole problem with hauling minerals through mass-limted wormholes), or mined and refined in the home system (which runs into the problem with 75% return from the refining array).
  • Training time: None of us can pilot a rorqual right now, and ideally at least one member from each of our corps should be able to, so we can all make use of it at any time — that’s a big commitment for a pilot to make, even if they’d be done before the ship is actually completed.
  • It’s a ship in a bottle. We live in a class two system, which in turn means that any wormholes that leave or enter our system have a certain total mass restriction, and a certain per-jump mass restriction. In short, that means that we can’t build or buy a Rorqual out in known space and bring it in, nor can we get such a ship out if we build it inside the hole; if we build it, we have to build it locally, knowing that it can never leave.

In short, it’s a hell of a big project, and a hell of a big commitment to make. Given that our little corp only just joined the Alliance a few days ago, the fact that we’re even discussing it says something about the great relationship we’ve already formed with our fellow system-mates.

It’s all just talk for now, of course, likely driven by a bit of cabin fever and the fact that every hour spent mining is (thanks to the refining problem) at least 15 minutes worth of completely binned effort, but all the same I take it as a good sign for the future health of our home system.

6 replies on “Life in a Wormhole: Welcome to the Alliance #eveonline”

  1. Sounds like you are in for a rough week.

    I was curious if you could go into a bit more detail about WH mechanics. If I scan down the persistent K-space connection (or any “outbound”) it isn’t activated. If I warp to the hole does it activate, or only if I jump through? Also when I show info on the home side of the WH is that how I can tell if it’s an outbound or inbound? It’s not very clear… as you can see I’m confused.

  2. Hi Tweed,

    Don’t feel bad about being confused — it’s a damned confusing topic, and a lot of what is ‘known’ about all of this is deductive work done by the players: it’s not something that’s ever been verified in official channels (at least as far as I’ve been able to find).

    This is what is “known” (in the way that the most reliable scientific theories are ‘known’):

    1. If you scan the persistent outbound wormhole connection and resolve it, you have its location, but it is not yet activated. This has been ‘proved’ about as thoroughly as anything like this can be proved — simply because no wormhole pilots have (in the last two years) ever seen a pilot come into their system via a wormhole that no one ‘inside’ the wormhole visited first.

    2. The ‘other side’ of a wormhole is activated either when you warp ‘on grid’ with it (on grid simply means you’re close enough to it for it to show up on your overview), or when you jump through it. No one’s entirely sure of which it is.

    I don’t ‘know’ any more than anyone else, but I’d be willing to bet 20 bucks that the other side of a wormhole is determined (and the ‘k162’ side created) when you warp on-grid with the wormhole, regardless of whether or not you actually jump through. Reasons include:

    a) The ‘lifespan’ timer on a wormhole starts from the moment you warp on-grid with the wormhole for the first time, NOT from the first time (if any) you jump through it.
    b) There’s a tiny lag spike the first time you warp on-grid with a new wormhole — that feels like the database being updated, to me.
    c) It just makes more coding sense. You never know when the wormhole will actually get jumped through, so it’s just more efficient to generate the exit point at the moment when it first becomes remotely possible that they might jump, rather than waiting until someone actually does — it’s not like the jump-zoning effect needs more lag added to it.

    You can tell if a wormhole is an outbound or an inbound by the “name” of the wormhole on Overview: a K162 wormhole is ALWAYS an inbound connection (in other words, the origin-point of the wormhole is the other system, not yours); any other name classification is an outbound. This is important to know, because if you see a k162, it automatically means that someone outside of your wormhole opened it, and may be sneaking around your wormhole right now.

    The info screen mostly tells you stuff like the general category of space that the wormhole connects to, how long before it dies of old age, and how destabilized it is from use.

  3. Ahhhhh I see.

    So when I scan down a WH in K-space that’s why they all (almost all) have a K162 designation on the K-space side (someone came out). When I jump through, I bookmark the WH side of W-space and see it has a separate designation. If you jump to a WH to check the “Show Info”, it activates it. So I guess you just know where the connections are, not what they are (in your situation now). Basically if I’m in my WH and I see a WH that pops up with a K162, that’s a bad thing. Got it.

    Another question… All WH’s have 1 static connection right (as in the same system each and every day)? C1-3 are usually K-space and the higher ones are static to another low level WH. I guess my question is on the difference between static connections and persistent. Like if same said WH had a persistent connection to a C5 will it always be the same C5 or a different C5 each new day/WH creation? I think you see where im going with this… kinda hard to explain.

    It all goes back to the day you wrote about mapping your home “system”, got me very curious.

    Thanks for taking the time.

  4. Yup: a lot of the wormholes you’ll find in known space will be K162s. Most, but not all.

    There is a way to make a very good educated guess as to what kind of wormhole is, without visiting it — it has to do with scanning a system with a single probe at 32 AU and knowing what signal strength all the wormholes will show up as in those conditions… The trick is, that strength varies depending on your ship, your skills, your probes, and lots of other stuff, so it’s only a guess, even if a good one.

    All wormholes but Class 2s have 1 static connection; class 2s have two static connections. They are also the most numerous type of wormhole.

    Class 1s, 2s, and 3s always have a static connection to known space. In addition, Class 2s always have an additional static connection to some specific class of wormholes. For instance, our first class2 home has static connections to HighSec and Class1 space; our new home statics are LowSec and Class2 (which is nice, since we’re guaranteed at least one additional wormhole system past our first one, since we connect to another Class2).

    I use “persistent” instead of “static” because I think Static is a terrible designation for what a wormhole is — “static” implies unchanging, and a wormhole connection is anything but that — stargates are ‘static’, from my point of view. “Persistent” means there will always be a connection there, but it can (and will) change in terms of what that connection means — like a marriage.

    But basically, just assume when I say persistent that I mean the same thing as when anyone else says “static”.

  5. Wormhole mining ops rock. If you don’t have to look over your should for stealth bombers, WH mining ops are great.

  6. I can fit 243 ABC ores in 1 Great Secure Container. I can hold 9 of those in a mammoth. That’s 2187 ore in one out bound trip to K space. With 1000 ore being compressed to 1 800m3 ore I can fit 4 of those ores in 1 GSC which means 36 compressed blocks going out. That’s 2187 the old way and 36000 the new way in one trip. Can’t wait.

Comments are closed.