AI assisted with source research and drafting. The prototype below is a design proposal, not a completed playtest or a claim of personal experience with Elite Dangerous.
A spaceship's jump command has more than one useful response. The cockpit can show that charging has started, how far it has progressed, and whether the pilot can still change their mind.
Those messages answer different questions. A progress bar can keep moving while leaving the last question unanswered.
A documented boundary in the jump sequence
Frontier's Elite Dangerous Players Guide v1.05, pages 74–75, describes a hyperspace jump sequence with a HUD charge bar. It also explains that the pilot can cancel before the five-second countdown begins by using the frame shift drive command again. Once that countdown starts, cancellation is no longer available.
This is a reading of the older guide's documented sequence, not a claim that its timings describe every current ship or drive.
The design interpretation is that the display has two jobs: communicate progress and communicate the actions still available. A pilot waiting for a drive to charge and a pilot committed to a jump may both be waiting, but they have different control over what happens next.
The guide establishes the rule. It does not establish how well players understand it. That is the question worth testing.
Give the waiting state a clear meaning
Consider a fictional shuttle with a departure button. Pressing it starts a short preparation phase. During preparation, the player can cancel. After preparation, the shuttle enters a final countdown and departs automatically.
Use three explicit states in a paper prototype or a small interactive mockup:
- Preparing: show progress and an available Cancel control.
- Departure committed: replace the cancel affordance with a clear message that the countdown cannot be stopped.
- Departed: show the changed location rather than leaving the completed progress bar on screen.
These are proposed interface choices, not a description of Elite Dangerous's exact cockpit presentation.
If the player cancels during preparation, return to a clearly idle state. If they try after commitment, explain why the shuttle continues. An input animation alone cannot tell them whether cancellation succeeded.
Keep the commitment message visible long enough to read. A brief flash or a change from one color to another may look dramatic while leaving the rule ambiguous.
Test comprehension at the boundary
Compare two versions with identical timings and cancellation rules. One shows a progress bar and the final countdown. The other adds the explicit preparation, commitment and cancellation messages.
Ask players to stop the departure at different moments. Include an early attempt and an attempt after commitment. Record whether they think the cancellation worked, whether the shuttle actually stops, and whether they repeatedly press a control while trying to understand its state.
Then ask a plain question: “Can you still stop the shuttle now?”
The result to look for is agreement between the player's answer and the actual rule. Faster button pressing alone would not show that the interface became clearer.
Repeat the task with sound muted. Important control changes should remain understandable when a spoken announcement is unavailable. If the text version becomes cluttered, simplify the wording before adding another animation.
Decide whether commitment belongs here
The test assumes that a non-cancellable phase serves the game. That assumption needs its own review. For a frequently repeated menu action, an irreversible countdown might merely waste time. A short departure sequence might need no cancellation boundary at all.
Even if the second display improves understanding, it would not prove that the countdown is enjoyable or that a spaceship needs more cockpit indicators.
The useful lesson from the guide is specific: when an action changes from something the player can stop into something they must wait through, make that change legible. The machinery can feel elaborate while the answer to “Did it accept my input?” stays simple.
Top comments (0)