Skip to content

Moffstation Design Pillars#1

Merged
DuckManZach merged 10 commits intomoff-station:masterfrom
DuckManZach:design-pillars
Apr 17, 2026
Merged

Moffstation Design Pillars#1
DuckManZach merged 10 commits intomoff-station:masterfrom
DuckManZach:design-pillars

Conversation

@DuckManZach
Copy link
Copy Markdown
Member

Lays out the design pillars for Moffstation, as well as the requirements of future design docs.

Requires approval of the maintainer team.

Copy link
Copy Markdown
Member

@Centronias Centronias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Broadly good. Lotsa grammar things.

Comment thread src/development/design-doc-main.md Outdated
Comment thread src/development/design-doc-main.md Outdated
Comment thread src/development/design-doc-main.md Outdated
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it'd be valuable to include something to say how these sit relative to upstream.
So maybe it's

  • goes further than upstream
  • diverges from upstream
  • clarifies upstream

I haven't read the individual pillars yet, so idk maybe it's not needed.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I the answer to this depends upon the specifics of the direction we take it. If something upstream is doing conflicts with one of the pillars, I would imagine our pillars would take precident. Unsure whether an explicit clarification is needed though

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, sorry, I mean to say that each individual pillar should describe where it sits among those three options.
Ostensibly any pillar overrides upstream because otherwise what's the point?

Comment thread src/development/design-pillars.md Outdated
Comment thread src/development/design-pillars.md Outdated
Comment thread src/development/design-pillars.md Outdated
Comment thread src/development/design-pillars.md Outdated
Comment thread src/development/design-pillars.md Outdated
Comment thread src/development/design-pillars.md Outdated
DuckManZach and others added 2 commits April 1, 2026 11:12
Co-authored-by: Centronias <charlie.t.santos@gmail.com>
Copy link
Copy Markdown
Member

@Centronias Centronias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Broadly fine to me, I think we'll refine them as we run into issues with 'em.

Comment thread src/development/design-pillars.md Outdated
The game is not about winning or losing; it's about creating an interesting story.

No round should feel the same as the last; there should be a large amount of variety and randomness, both impactful and small, to give each round an authentic feeling.
Good stories happen when players are emerged in unfamiliar situations, and are able to create interesting, bizarre, or unique outcomes. When situations are predictable or solved the same way every time, players stop engaging with the scenario and instead follow learned patterns.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"emerged" doesn't make sense to me here.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Think I meant to say immersed

Copy link
Copy Markdown

@Nyxilath Nyxilath left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Giving a read-over following Centronias' suggestions, everything here seems to fall in line where I would expect and agree upon.

The only real thing that crossed my mind is under our 'Round Investment / Event-Driven' segment, where it may be worth splitting these into two separate categories as while they're tangential they do have separate key takeaways, the former highlighting what content we're looking for Moffstation, while the latter goes moreso into how and why we're going about this content. While these topics are relevant to each other, it may be worth splitting these into separate pillars so they can stand more strongly on their own, and further clarified as questions arise.

@DuckManZach
Copy link
Copy Markdown
Member Author

Im gonna go ahead and merge these, we can go back and revise if we wanna improve them more later

@DuckManZach DuckManZach merged commit b6e3624 into moff-station:master Apr 17, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants