//Design Philosophy

The skies have already been sundered. What remains is whether they can be mended, or merely endured.

This line is the clearest shorthand I have for the project. This applies to the design philosophy as much as it applies to the narrative.

The world is already broken. The question is how the systems, mechanics, and player experience can reflect that condition while still offering something worth engaging with.

▸Pillars

Expressive Movement

Movement is not only traversal. It is part of combat identity. The player should feel that how they move is as much a part of their playstyle as what they do.

That means parkour and flow-state thinking are not just about getting from point A to point B. They are also about how the player approaches combat, exploration, and world interaction.

The player should feel that momentum, angle, and timing are meaningful decisions rather than animation glue between encounters. That is why parkour and flow-state thinking sit so close to the rest of the combat design.

Meaningful Choice

The game is structured around consequences rather than binary morality. The player should feel that their choices are meaningful, but not that there is a single right way to play.

I want player decisions to register through faction dynamics, narrative pressure, and world-state shifts. The emphasis is on context and tradeoff, not clearly labeled right answers.

Systemic Depth

Combat, builds, progression, and world systems should reinforce one another. The player should feel that the tools they have are part of a larger ecosystem of systems that interact in interesting ways.

The ideal outcome is that different players can solve similar problems through different combinations of tools, roles, and priorities without the game flattening them back into one optimal path.

Respect Player Time

I do not want grind for its own sake.

Even when the project borrows inspiration from games with heavy progression loops, the design standard here is that repetition should either deepen mastery, reveal something new, or be optional.

Mechanics As Metaphor

The fiction should not sit on top of the mechanics like packaging. The systems should be designed to communicate something about the world, the characters, and the themes.

When a player is learning how to use a tool or navigate a system, they should also be learning something about what that tool or system means in the context of the world, e.g. an ability is not just a way to deal damage. It is a way to express personality, or to interact with the world in a way that says something about it.

▸UX Implications

Coming from a UX background, I think about readability and emotional tone at the same time. That means:

• ▪dense interfaces should still scan quickly
• ▪visual hierarchy should communicate urgency and state clearly
• ▪terminology should support memory, not just flavor
• ▪navigation should help a reviewer or player understand the structure of the game without needing a lore lecture first

▸World Before Plot

The most important project rules is that nu-Eden should feel like a world before it feels like a game.

That affects how I think about documents, codex pages, factions, and the prototype itself. The player is important, but not the only thing making the world move.

▸The Working Standard

If a feature does not improve clarity, deepen expression, or strengthen the relationship between system and theme, it should be questioned whether it belongs in the game.

That standard is especially important on a first game project, where the temptation to keep adding cool ideas is much stronger than the discipline to cut them.