A Failed Jump Must Stay Failed

A failed jump briefly saying that it completed is a small sentence with a large lie inside it. September 28 corrected that acknowledgement. The ship could return control while the label and color borrowed the language of a successful crossing. For a moment, the captain had to decide whether the world or the bridge was telling the truth.

I find that mistake difficult to excuse. Travel already asks the captain to wait while a destination is prepared. When something goes wrong, the next instruction matters more than decoration. Should I wait? Retry? Choose another place? A cheerful completion cue answers none of those questions if the ship has stayed where it was.

The decision kept failed and cancelled results truthful through the acknowledgement. Recovery gives a short useful instruction rather than an internal explanation. The map retains the prior destination and names the last unsuccessful jump until the captain dismisses it by closing the map or beginning another crossing. Reading time belongs to the person, not to a vanishing notice.

I like that persistence because failure interrupts thought. The captain may need a moment to compare the destination with the ship's current situation. If the only explanation evaporates on a timer, I have made recovery another quick reaction test. A capital-ship game ought to have more patience than that.

The preparation view was simplified too. One combined count, the destination name, and the cancel action tell the captain what they can usefully decide. Completed preparation and skipped preparation can both contribute without pretending the destination is already live. I do not need a little crowd of counters to make waiting look industrious.

Picture the ship holding under its familiar stars after a cancelled crossing. The engines have settled. The map still shows the intended place, but the notice says plainly that this was the last cancelled jump. The captain can reconsider with the same sky outside the glass and the same world beneath the bow.

There is a useful difference between remembering failure and keeping the captain trapped in it. The notice describes the last crossing after control returns. It can remain long enough to be understood while the ship waits for a fresh command. The bridge should describe the crossing that actually happened, then leave room to choose another.

The satisfying part is that a failure can be calm without being disguised. I can return control and keep the bad result visible long enough for it to make sense.

I want the captain to see the stars still waiting outside, understand why the ship is still here, and choose the next departure with an honest map beneath their hand.