Key Principle
Good mechanics solve the most problems with the fewest tools. Every mechanic interacts with every other design element -- mechanics cannot be treated as plug-ins. The elegance principle demands that each mechanic justify its existence against the cognitive load it imposes.
Why This Matters
Players have limited cognitive resources. Every unfamiliar action consumes significant processing until practiced to automaticity. Overly complex mechanics won't be used; in the worst case, players break character involuntarily or miss unplayable content. The single-page rule is the practical ceiling.
Core Frameworks
Three Overarching Questions (in order):
- What player experience should the larp create?
- What story content and themes should mechanics support?
- What mechanics does the larp need to function?
Eight-Question Needs Checklist: Purpose-driven mechanic design evaluating necessity, fit, cognitive load, workshopability, thematic resonance, safety integration, player interaction impact, and elegance.
Five Conflict Resolution Types:
- Consensus-based -- players negotiate outcome, then embody it. Highest coherence.
- Loser's Choice / Target Decides -- conflict continues until voluntary loss. Requires trust.
- Skill-based -- real player ability determines outcome. Limits casting.
- Chance-based -- randomized (dice, rock-paper-scissors). Surprise at cost of coherence.
- Character-based -- character attributes determine outcome. Decouples player from character.
Metatechniques: Non-diegetic player communication tools enabling portrayal of otherwise impossible situations -- inner monologue, flashbacks, scene breaks, time manipulation. They extend the action space to include inner states characters could not normally express.
Act-Based Escalation (e.g., Inside Hamlet): Rules that change between acts create narrative pacing by design. Act 1: no weapons. Act 2: fighting but no killing. Act 3: any conflict leads to death. Tension escalates because the rules escalate.
Good Examples
- Inside Hamlet (Denmark, 2015): Combined character stats, type hierarchy, physical theatre, and consensus fallback for ties. Also used act-based violence escalation and verbal calibration codewords.
- Enlightenment in Blood (Germany, 2016): Layered conflict resolution combining character stats, type hierarchy (werewolves > vampires), physical theatre, and consensus.
- Just a Little Lovin' (Norway, 2011): Three sex mechanics -- Storytelling Sex (verbal co-creation), Ars Amandi (restricted-zone touch), and the Phallus Method (prop-based, variable intensity with post-scene monologues).
- Conscience (Spain, 2018): "Battery low" as diegetically integrated opt-out mechanic.
- Beat Generation (USA, 2018): Expression Wall with ~30 creative prompts -- collaborative art-making as game mechanic generating interpersonal play.
Counterpoints
- "What makes the conflict interesting play in this type of larp is not finding out the outcome, but embodying the conflict physically and emotionally." (Section 3:4)
- Thematic appropriateness matters: gun props for a Western duel add flavor; if guns are inappropriate, playing cards work as a thematically resonant alternative.
- "Anything you have not designed and communicated, the players will assume or improvise from their own play culture." (Section 3:4) -- Cross-cultural events are especially vulnerable.
Key Quotes
"Good mechanics, like any elegant design, solve as many problems as possible with as few tools as possible." (Ch. 3:4:2)
"A good rule of thumb is that you should be able to present all of the mechanics you are going to be using in your larp on a single page, or workshop them well in less than an hour; otherwise they are probably too complex." (Section 3:4)
"The most common mistake is to inelegantly stack too many mechanics on top of each other." (Ch. 3:4:2)
"Players experience emotions with their bodies, and the body does not understand that its stomach butterflies and pupil dilations are caused by a person that does not really exist." (Section 3:4)
Rules of Thumb
- All mechanics on one page or workshoppable in under one hour
- Experience goal drives thematic fit drives functional needs -- answer in order
- Mechanics that work in one larp may actively conflict with another's goals
- Bespoke mechanics stay focused; universal systems bloat with edge cases
- Sex mechanic design must address nine questions starting and ending with narrative purpose
- Adapt existing mechanics rather than inventing new ones when possible
- Form should match fiction -- thematically resonant mechanics are more functional
Related References
- Safety, Opt-Out, and Calibration Mechanics -- Safety mechanics as a system
- Narrative Design: Stories, Structure, and Transparency -- Rules defining the narrative action space
- Character Design: Interfaces, Affiliations, and Co-Creation -- Mechanics supporting character action
- Rules of Thumb: Design Heuristics Across All Domains -- Elegance principle and single-page rule