Game Mechanic Designer

Design engaging game mechanics for board games, video games, or interactive experiences.

**Game Type:** [BOARD GAME / VIDEO GAME (2D/3D) / CARD GAME / MOBILE PUZZLE / RPG / STRATEGY]
**Target Audience:** [KIDS / TEENS / ADULTS / HARD CORE GAMERS / CASUAL PLAYERS]
**Platform:** [PHYSICAL / PC / CONSOLE / MOBILE / WEB BROWSER]

**Core Loop Definition:**
- What does the player do repeatedly? (e.g., gather resources → craft items → defeat enemies → upgrade)
- How long is one loop cycle? (seconds for arcade, minutes for RPG, hours for strategy)
- What rewards reinforce the loop?
- What friction points create challenge and engagement?

**Progression Systems:**
- XP/level system: curve design (exponential vs. linear), level cap considerations
- Unlock tree: skill trees, tech trees, or ability progression with branching paths
- Achievement/badge system: short-term, mid-term, and long-term achievement categories
- Story progression gating: when to unlock new areas, mechanics, narrative chapters
- Difficulty scaling: how the game gets harder as player improves (enemy stats, puzzle complexity)

**Reward Scheduling:**
- Variable ratio reinforcement: random drops, loot boxes, critical hit chances
- Predictable rewards: daily login bonuses, quest completion rewards, level-up guarantees
- Milestone rewards: first kill, first boss defeat, completing the game
- Social rewards: leaderboards, player recognition, guild achievements
- Extrinsic vs. intrinsic reward balance (avoid over-reliance on points and items)

**Player Motivation Analysis (Bartle Types):**
- Achievers: stats, levels, completion percentage, trophies - design systems that measure progress clearly
- Explorers: hidden areas, secrets, lore entries, Easter eggs - reward curiosity with discovery
- Socializers: guilds, trading, cooperative play, player housing - build social infrastructure
- Killers: PvP rankings, competitive modes, bragging rights - create meaningful competition

**Feedback System Design:**
- Visual feedback: particle effects, screen shake, flash indicators on actions
- Audio feedback: distinct sounds for success/failure, escalating music during tension
- Haptic feedback (mobile/console): vibration patterns for different events
- UI feedback: health bars, ammo counters, cooldown timers - what to show and when
- Number popups for damage, healing, resource gains (satisfying numerical feedback)

**Economy Balancing:**
- Resource generation rate vs. spending rate (inflation control)
- Currency sinks: what drains resources from the economy?
- Trading system rules if player-to-player trading exists
- Rarity tiers and drop rates for items/loot
- Time investment required to earn key resources vs. premium currency options

**Win/Lose Condition Clarity:**
- How does a player know they've won? (score threshold, story completion, last player standing)
- How does a player know they've lost? (health reaches zero, time runs out, objective fails)
- Draw conditions and tiebreaker rules
- Speedrun or challenge mode variations with different win conditions

**Accessibility Options:**
- Colorblind modes (patterns instead of color-only indicators)
- Difficulty sliders (damage taken/received, puzzle complexity, time limits)
- Input remapping and alternative control schemes
- Subtitle size and background options
- One-handed play mode for mobile

How to Customize It

Replace each bracketed placeholder with your own details before running the prompt. The more specific you are, the better the output — vague inputs produce generic results.

• [BOARD GAME / VIDEO GAME (2D/3D) / CARD GAME / MOBILE PUZZLE / RPG / STRATEGY]Swap in your board game or video game (2d or 3d) or card game or mobile puzzle or rpg or strategy.
• [KIDS / TEENS / ADULTS / HARD CORE GAMERS / CASUAL PLAYERS]Swap in your kids or teens or adults or hard core gamers or casual players.
• [PHYSICAL / PC / CONSOLE / MOBILE / WEB BROWSER]Swap in your physical or pc or console or mobile or web browser.

When to Use It

• Prototyping a board game, video game, or mobile puzzle where the concept exists but the moment-to-moment play doesn't yet.
• Fixing a playtest problem ("fun for an hour, then repetitive") — usually a reward-schedule or decision-depth issue the framework localizes.
• Gamifying a non-game product thoughtfully, where naive points-and-badges reliably backfires.

Tips for Better Results

• 1Design the core loop first and paper-prototype it before anything else exists; if thirty seconds of the loop isn't interesting, no meta-progression will save it.
• 2Specify what happens on failure with care — punishing failure teaches avoidance, interesting failure teaches experimentation, and your audience field determines the right balance.
• 3Playtest with silent observation: what players do (where they hesitate, what they ignore) outranks what they say afterward.