《Alien: Isolation》：科幻介面何時應該難用？

A battered terminal can make a space station feel lived in. But if a player cannot tell which button opens a door, is the fiction working, or is the interface simply failing?

Alien: Isolation offers a useful way to frame that question: decide which difficulties belong to the fictional machine, and which ones should never reach the player.

AI disclosure: An AI assistant researched, drafted, and checked this article against the linked developer interviews under the account owner's standing instructions. The prototype exercise below is a design proposal, not a completed test or a claim of personal production experience.

A future with a specific past

In a March 2014 interview with PlayStation Blog, Creative Lead Alistair Hope described a deliberate reference boundary: the team drew on material from before 1979. Their future would contain physical buttons and imperfect equipment rather than today's idea of frictionless technology.

Hope also described recording game material through VHS and CRT equipment, then bringing the result back into the game. This was a production technique for a particular visual language, not a prediction about future computing.

The useful lesson for another SF game is the consistency of the constraint. A station's terminal, handheld tool, and wall controls can suggest that they came from the same technological culture. The artist does not have to invent a completely new visual language for each prop.

That does not mean every fictional civilization needs old screens. A different world might use replaceable physical modules, shared public consoles, or equipment built for gloves. Choose a rule that affects the things players actually operate.

Two kinds of information, two kinds of interface

In his December 2014 Art of the Title interview, UI and title designer Jon McKellan explains a division in the game's interface.

Information representing Amanda Ripley's awareness or memory used a minimal overlay designed for clarity. Machines that she physically operated appeared inside the world and were deliberately more awkward, matching the old software they represented.

That distinction matters more than adding a retro filter. It locates the friction. A device can be cumbersome because that is the device the character has to work with; the entire game does not need to become equally cumbersome.

McKellan describes positive reactions to the ReWire terminal and final hacking game. This is a designer's account of the response, with no controlled comparison or sample size reported. It does not establish that awkward interfaces universally increase immersion.

For a new game, treat the distinction as a question to test: Is the player dealing with an understandable limitation of a machine, or struggling to understand the game's controls?

Give the awkwardness a job

Consider an invented emergency terminal aboard a cargo station. Its task is to redirect a lift to a maintenance deck.

A slow mechanical selector might communicate the equipment's age. A limited display might force the player to inspect one route at a time. A clear confirmation light could still show that the order was accepted.

Those are different design choices from hiding the selected option, using unreadable text, or failing to acknowledge a button press. The first group can express the machine's constraints. The second can leave the player unsure whether the game is responding at all.

A practical review can separate three layers:

• Appearance: casing, type, wear, screen treatment, and sound.
• Operation: the steps needed to issue an order.
• Feedback: what confirms the current selection, progress, failure, or completion.

Make each layer justify itself. A worn casing can establish age without adding an extra menu. A physical lever can make an action tangible without concealing its result. An extra step should support the intended encounter, not merely make the screen look busier.

Test one terminal before decorating a whole station

Build two versions of that lift terminal with the same destination labels and outcome.

In one, the player chooses a destination directly. In the other, the player moves a selector through the available destinations and confirms the choice. Keep text size, contrast, and confirmation feedback comparable so that a basic readability problem does not dominate the comparison.

First test both without danger nearby. Ask players to explain what they selected and whether the order succeeded. Note wrong selections, repeated inputs, and requests for help.

Then place the same task inside a short encounter where time matters. Alternate the order of the versions across players. Ask whether the extra operation made the machine feel tangible, created useful tension, or simply interrupted the scene.

This is a proposed small usability exercise, not a validated experiment. A few observations can identify obvious problems, but cannot establish a universal preference or a sales effect.

If the complicated version produces confusion even in the calm test, repair its feedback before calling that confusion horror. If it works once but becomes tedious on repeated visits, consider shortening familiar interactions. Keep essential text and input options accessible even when the fictional equipment is not friendly.

Where the idea does not fit

A station used for fast competitive play may need immediate, predictable controls. A heavily repeated maintenance task may become exhausting if every use performs the same slow ritual. Some players will need a clearer presentation than the art direction initially suggests.

The design hypothesis here is narrower than “clumsy technology makes better science fiction.” A coherent fictional machine can contribute to a world's identity when its limitations are legible and appropriate to the task.

Start with what the player needs to do. Then decide which part of using the machine is worth experiencing.