Flagoak Studios

The Quartermaster’s Desk

A delivery can appear to fail in the records when it actually arrived on time. At Flagoak Studios, that disagreement is a useful starting point for a design session. A field officer in one of our historical campaign concepts receives messages at different times, and the game must make both clocks readable. The story begins with who had enough information to act and what the next report made possible.

Before a decision reaches the board

The design role chooses one meaningful decision that a delay could change. In a crossing scenario, the player can hold the second wagon at the near bank or release it while the earlier arrival is still unconfirmed. A route may be physically usable before the officer is confident about the receiving yard. The test position should leave time for both choices to play out.

The research role studies the constraints behind the setting. Working notes distinguish evidence about materials and travel conditions from invented places, people and scenarios. The inventory can have the limitations of a particular supply system even when the valley itself is fictional. When we choose a simpler rule for play, the project brief records what that rule represents.

Before a decision reaches the playtest

The interface role lays out the departure, forecast and receipt as separate events. The art role gives each station a distinct ground texture, landmark and sign. Both need to agree on where the player first sees a changed condition. The landscape should support interpretation when the player looks away from the ledger, and the text should carry the same facts on a narrow screen.

The implementation role reproduces the same delivery with different planning orders. It checks that expected quantities stay separate from usable inventory, and that the next opening is calculated from the latest accepted road condition. The playtest role observes how a player explains a delivery once it appears in the receipt column. That account shows whether the interface communicated the chain of events.

What belongs in a report

When we find a confusing turn, we keep the smallest manifest that reproduces it. The report describes the last confirmed message and the missing information. It gives the next tester enough context to make a fresh choice. See Supply Reports for examples and Campaign Files for current game concepts.