In the last devlog I talked about Gravity Wells, the zones where everything happens. This one is about the thing that connects them: the Jump Drive.
The Jump Drive is how your ships move between Gravity Wells. It's not instant travel. It's not a button you press to teleport somewhere safe. It's a process, and every step of that process creates a window where something can go wrong.
Three phases
A jump has three moments. First, the charge-up: your ships power up the drive, and for several seconds they sit there, visible, unable to fire. Anyone watching can see what you're about to do. You can cancel during this phase, but if you're charging because you need to leave, canceling means staying in the fight you were trying to escape.
Second, transit. Your ships disappear from the Gravity Well they're in and cross the Deep Space between destinations. They're gone. For the enemy, it's a brief period of uncertainty if they don't have sensor coverage on the target Gravity Well.
Third, stabilization. Your fleet arrives at the edge of the destination Gravity Well with weapons offline and systems recalibrating. If someone is waiting for you, those first seconds after arrival are brutal. You're there, you're visible, and you can't shoot back yet.
The retreat problem
This is the situation I wanted the Jump Drive to create: you're losing a fight. Your Cruiser's shields are down, your Destroyers have taken hull damage, and the enemy is pushing. You order the jump. The charge-up starts. Now you're standing still, taking fire, waiting. Can your ships survive long enough to complete the charge? Do you pull back the ones that are too damaged and sacrifice a Frigate to buy time? Or do you cancel and try to fight it out?
Running away in The Outer Line costs something. It's not free. And the enemy can make it hurt.
The invasion window
On the other side of that same coin, jumping into a defended Gravity Well is risky. If the defender has a Listening Post or scouts with sensor coverage, they see your fleet charging up. They have time to position ships at the most likely arrival point, set up crossfires, activate Fortress Mode on their Battleship. When your fleet drops out of the jump, it lands at the edge of the Gravity Well with weapons dark, and whatever the defender prepared is already aimed at you.
This is the core tension. Attacking costs you the stabilization window. Defending gives you those seconds to prepare. But the attacker gets to choose when and where, and the defender has to guess which direction the fleet is coming from.
Splitting the fleet
Because jumping commits your ships, dividing your force becomes a real decision. Send everything to one Gravity Well and you hit hard, but you leave every other Gravity Well you control undefended for the duration of the transit and the fight. Send half, and maybe you don't have enough to break through.
I've been testing this with the AI and it creates some situations I really like, though I'm still not sure the timing feels right in all cases. Sometimes the charge-up is long enough that splitting feels too punishing. Other times it feels too easy to jump back and forth. The numbers need more work.
What does seem to work is the psychological pressure. When you see an enemy fleet charging up and you don't know which of your Gravity Wells they're heading for, you have to make a call with incomplete information. That's the kind of decision I want the game to be about.
Moving the Mobile Shipyard
Every ship can jump. But when the Mobile Shipyard jumps, the stakes are different.
The Shipyard's charge-up takes significantly longer than regular ships. It's your production, your module investment, your entire strategic backbone packed into one hull. While it's charging, it can't build. It can't repair. It's just sitting there, glowing, telling everyone exactly what you're about to do.
But sometimes you have to move it. The Gravity Well you're in has been stripped of resources, or the enemy is closing in with more force than you can handle, or you need to be closer to the front to shorten production delivery times. So you commit. You assign an escort, you start the charge, and you hope nothing goes wrong during the transit.
I've lost test games because I moved the Shipyard at the wrong time. I've also won games by repositioning it to a Gravity Well the enemy wasn't expecting, setting up production behind their lines. It's a gamble every time, and the long charge-up means you can't change your mind halfway through.
The hardpoint that matters most
Here's the thing that ties the Jump Drive into the hardpoint targeting system from Devlog #02. The Jump Drive is a hardpoint. It can be targeted and destroyed.
A ship with a crippled Jump Drive is stuck in whatever Gravity Well it's in. It can still fight, still move within the Gravity Well, still be useful. But it can't leave. If the fight goes badly, that ship isn't coming home. And a Support Ship can restore the hardpoint, but only if one is nearby and the battle gives you enough breathing room.
This creates a targeting priority I didn't fully anticipate during design. In some fights, crippling the enemy's Jump Drives is more valuable than destroying ships outright. You don't need to kill them if they can't retreat. You just need to keep them there until you're ready to finish the job, or until they've spent enough resources defending a position you've already written off.
Next time
Next devlog is about what you build once you've taken a Gravity Well. Structures, defenses, and the choices that turn empty space into territory.