Planning an Endless Sky interface modernization

The Outfitter prototype made me ask a bigger question about Endless Sky. I could imagine a cleaner way to browse and understand outfits, but I did not want a prettier screen that changed the game’s trading rules. I asked for a feasibility review, then clarified that the visual language should eventually reach the wider interface while the underlying gameplay stayed familiar.

That boundary became the most useful part of the study. The existing C++ panels already handled capacity, licenses, depreciation, multiple ships, refills, shortcuts, and failure messages. A redesign would have to preserve those interactions, not just draw attractive tiles. I kept a layout prototype and a separate color reference in distinct roles, then asked how a native implementation might proceed. The record ends at review and planning; it does not show a merged game-wide UI change.

A prettier transaction must be the same transaction

The discussion separated interface changes—layout, filtering, previews, navigation, typography, feedback—from economy, fitting rules, missions, combat, saves, and other gameplay behavior.

A proposed refactor could split an operation into a plan, preview, and application step, but it would still have to preserve the result:

Same saved state + same selected action
  → same gameplay outcome through either interface

That matters especially for multi-ship actions, partial transfers, unusual outfits, licenses, cargo limits, and plugin content. A cleaner preview should explain the existing action rather than silently replace it with simpler rules.

The visual vocabulary

The palette direction was neutral charcoal, cool white, and restrained cyan. These were explicit design tokens, not colors extracted mechanically from an image:

Most of the screen should remain neutral. Cyan identifies interaction; green, amber, and coral carry meaningful status alongside labels or symbols. A bigger capacity number is not automatically an improvement if it means more space consumed.

I later supplied another image and specified that it was a color reference only. The prototype remained the layout and interaction reference. I also clarified that the exact palette document had already been included in the M0 material; the new image helped judge composition rather than inventing missing tokens.

I ended with separate references for behavior, layout, and color. The Outfitter could be the first place to test whether a clearer UI still respected every transaction rule. The historical review did not record a merged change to the game.