Far Frontier
Sihan Ma’s Game Design Document
Lecture summary: Game Overviews, Design Pillars and Gameplay Loops
1. Communicate the Core Experience Clearly
A game overview usually consists of two to four sentences and should communicate the core concept in thirty seconds or less. Focus on what players do, their objectives and what makes the experience appealing, rather than only describing the setting or backstory.
2. Connect Player Actions with the Experience You Promise
An overview can begin with a compelling hook, followed by the main player actions and the role players inhabit, then conclude with the distinctive experience the game promises. Every sentence should add useful information. Avoid repeating details already shown elsewhere, and refine the overview through prototyping and player feedback.
3. Use Design Pillars to Maintain a Consistent Vision
Design pillars are the foundational principles that guide feature selection, priorities and project scope. The speaker recommends three to six pillars, with four or five often being a useful target. Each pillar should include a concise title and one or two supporting sentences so the team shares the same understanding.
4. Make Design Pillars Useful for Decisions
Every feature should support at least one pillar without contradicting the others. Pillars should describe specific experiential choices rather than vague ambitions such as “the best gameplay.” One useful test is to reverse a pillar: if its opposite could also describe a reasonable game, it likely expresses a meaningful design choice. Art and narrative can also be pillars when they explain the intended player experience.
5. Distinguish the Core Loop from the Metagame Loop
The core gameplay loop consists of frequently repeated actions such as movement, combat, avoidance and earning rewards. The metagame loop connects these actions to longer-term goals, including upgrades, unlocks and story progression. The core loop provides immediate enjoyment, while the metagame loop supports sustained motivation.
6. Map the Relationship Between Actions and Resources
To create a loop diagram, connect player actions in sequence, add a short description to each step, and identify the resources gained or spent. Resources may include health, currency and equipment, as well as information, narrative progress or access to new areas. The diagram should show where rewards come from, how they are used and how they support the next cycle.
7. Examine Progression Across Different Timescales
Analyse gameplay across seconds, minutes and hours: how immediate actions achieve small goals, and how those goals contribute to level and overall progression. Repeated actions remain engaging through new content, choices and a sense of advancement. This also applies to narrative games, where dialogue, exploration and story development can form meaningful loops without complex resource systems.