Planning an Endless Sky interface modernization
An Outfitter prototype became a whole-game UI plan, with gameplay parity and separate layout and color references.
Explore the mess / 19 entries
Projects, experiments, and notes involving games. Follow a topic across otherwise unrelated rabbit holes.
Nothing matches those filters.
Try a broader term, or follow a topic link in the archive.
Browse the notebook →An Outfitter prototype became a whole-game UI plan, with gameplay parity and separate layout and color references.
A network-boot question became a comparison of separate remote desktops and shared physical desktops, ending with a usable Linux thin-client session and working audio.
A proposed technology-mod stack became a practical test of what was installed, enabled for a world, and actually visible in the workbench.
A compact processing room led into reactor expansion and a new constraint: keeping lava production ahead of demand.
A skyblock base grew from an unbuilt floor plan into automation, a cramped service layer, a room retrofit, and recurring power constraints.
A skyblock floor evolved from a 200-block concept into a centered 201×201 concrete plan, with a corrected hub and CSV material counts.
An expert Minecraft pack design moved from campaign decisions into a smaller development instance, with guide-first quests and concrete compatibility tests.
How the no-asset game idea became a generation-ship simulation whose technology can be lost as well as recovered.
Planning a first-day Vintage Story guide around the things a new player should be able to do before nightfall.
A browser pixel experiment grew into a C++ ecology sandbox with inherited traits, grazing, local nutrients, CSV telemetry, and measured performance bottlenecks.
A horror-game design where the only view of a building is a floor plan that can lie, and sound supplies the missing physical world.
A survival-game design that moved toward restoring the land, assembling useful systems, and a deliberately smaller first-day slice.
A generation-ship side-scroller found its identity in close-quarters resistance, fragile shared infrastructure, and the etiquette of a civil war inside a sealed home.
A C++ game-system experiment made official records shape a city’s legal reality, with replay, conflicting authorities, and reversible public-memory decrees.
A C++ fictional-history engine separating hidden causes, unreliable evidence, and changing interpretations, developed through narrow, auditable implementation slices.
A Python prototype explored identity through player actions, while schema mismatches exposed the need to validate the links between actions and projects.
Five material directions for a dark Minecraft build, from ruined deepslate to swamp rot and deep-sea ruins.
A ready-to-print baseball scorecard request became a layout for lineups, innings, pitching, substitutions, and game notes.
A turn-by-turn science-fiction story changed from surveillance and resistance into unstable realities, time travel, loss, and an altered future.