ChatGPT Prompts for Gamers & Game Creators

Create a compelling backstory for a Dungeons & Dragons character I'm building.

Race: [e.g., Half-Elf, Tiefling, Dragonborn]
Class: [e.g., Warlock, Paladin, Rogue]
Level: [starting level]
Alignment: [e.g., Chaotic Good, Lawful Neutral]
One personality trait I've chosen: [e.g., "never breaks a promise" or "compulsively lies about their past"]

Build the backstory in these layers:

**Origin & Upbringing**:
- Where they grew up (village, city, nomadic, underground, etc.) and what that place was like
- Family situation — who raised them, are they alive, what's the relationship now
- The moment they first discovered their class abilities (a warlock's pact, a paladin's oath, a rogue's first theft)

**The Inciting Wound**:
- One event that broke their old life and set them on the adventuring path
- Who was involved and what happened to those people
- The emotional scar it left — what do they fear, avoid, or overcompensate for because of it

**Bonds & Debts**:
- One NPC they'd die for and why
- One NPC they owe a debt to (could be leveraged by the DM)
- One rival or enemy who might resurface

**Quirks & Roleplay Hooks**:
- A verbal tic, habit, or ritual they perform (e.g., always touches a locket before combat, refuses to eat meat)
- A secret they haven't told the party
- A personal goal beyond "defeat the big bad" — something intimate and character-driven

Write it as a 400-word narrative I can hand to my DM, plus 3 bullet-point hooks the DM can weave into the campaign.

Generate 5 unique campaign plot hooks for a tabletop RPG session.

System: [D&D 5e / Pathfinder / Call of Cthulhu / Blades in the Dark / other]
Party composition: [list classes and levels, or just the number of players]
Setting: [high fantasy / dark fantasy / steampunk / sci-fi / modern horror / homebrew — describe briefly]
Tone the group enjoys: [heroic / gritty / comedic / mystery-driven / political intrigue]
What they've been doing recently: [brief summary of last session or current arc]
What I want to avoid: [tropes or scenarios the group is tired of]

For each hook, provide:

1. **The Inciting Incident**: What happens to pull the party in — make it personal, not just "a stranger in a tavern asks for help"
2. **The Apparent Problem**: What the party thinks they're dealing with at first
3. **The Real Problem**: What's actually going on underneath (the twist or deeper layer)
4. **Escalation Path**: How it gets worse if they ignore it or fail early checks
5. **Moral Dilemma**: A choice the party will face where there's no clean "good" answer
6. **Key NPCs**: 2-3 characters involved, each with their own agenda (name, role, motivation, secret)
7. **Estimated Session Length**: How many sessions this hook could sustain (one-shot, 2-3 sessions, full arc)

Make each hook use a different narrative engine:
- Hook 1: Mystery (something doesn't add up)
- Hook 2: Ticking clock (something bad happens if they don't act fast)
- Hook 3: Moral quagmire (both sides have legitimate claims)
- Hook 4: Personal stakes (it directly affects a PC's backstory)
- Hook 5: Heist or infiltration (they need to get in somewhere they shouldn't be)

Create a memorable NPC for my tabletop RPG campaign that my players will actually remember and want to interact with.

NPC's role in the story: [quest giver / ally / villain / shopkeeper / comic relief / wildcard]
Setting: [describe your world or campaign setting briefly]
How the party will first encounter them: [where and under what circumstances]
What I need this NPC to do for the plot: [their narrative function]

Build this NPC with these layers:

**The Surface (what players see immediately)**:
- Name, appearance, and one visual detail that makes them instantly recognizable (a scar, a distinctive hat, mismatched eyes)
- Voice and speech pattern — give me a 2-sentence example of how they talk (formal? slang? whispers? booming?)
- First impression: what players will assume about them within 10 seconds

**The Personality Engine**:
- Core motivation: The one thing they want more than anything
- Core fear: The one thing they'll do anything to avoid
- How these two forces create internal conflict
- Their opinion of adventurers in general (and how that colors interactions)

**The Depth (what players discover over time)**:
- A secret that reframes everything the party assumed about them
- A moral line they won't cross — and one they already have
- Something they're genuinely good at that has nothing to do with the plot
- A relationship with another NPC that reveals a different side of them

**DM Toolkit**:
- 5 signature phrases or reactions for common situations (being threatened, being flattered, being asked for help, being caught in a lie, saying goodbye)
- How they behave in combat (if applicable) — tactics, cowardice, bravery, dirty tricks
- What happens to the story if the party kills them, befriends them, or ignores them (3 branching outcomes)

Create a detailed strategy guide for a specific game scenario I'm struggling with.

Game: [game name and platform]
Specific challenge: [boss fight / multiplayer meta / resource management / build optimization / ranking up]
My current approach: [what I've been doing that isn't working]
My skill level: [beginner / intermediate / advanced / competitive]
Constraints: [limited resources, specific character/loadout, solo vs. team, etc.]

Build the strategy in layers:

**Situation Analysis**:
- Break down why my current approach is failing — identify the specific mechanics I'm fighting against
- What the game is actually rewarding vs. what I think it's rewarding
- Common mistakes at my skill level and how to identify them in my own play

**The Core Strategy**:
- Step-by-step game plan with decision points clearly marked
- Priority order: what to do first, second, third — and what to ignore entirely
- Resource allocation: where to invest time/currency/upgrades for maximum return
- Contingency plans: if X happens, pivot to Y

**Mechanical Execution**:
- Specific inputs, timings, or sequences I need to practice
- Common tells or cues to watch for (enemy patterns, audio cues, UI indicators)
- The "muscle memory" drill: a repeatable practice routine to build the skills needed

**Mental Game**:
- Decision-making framework: how to read the situation and choose the right action under pressure
- When to play aggressive vs. defensive and the indicators for each
- How to recover from mistakes mid-game instead of tilting
- The mindset shift that separates my skill level from the next one up

**Progress Checkpoints**:
- 3 measurable indicators that the strategy is working
- What "good enough" looks like vs. what perfection looks like
- When to abandon this strategy and try something else

Help me create a structured Game Design Document (GDD) for a game concept I'm developing.

Game concept: [1-2 sentence elevator pitch]
Genre: [platformer / RPG / roguelike / puzzle / simulation / FPS / strategy / other]
Target platform: [PC / mobile / console / web / multi-platform]
Team size: [solo / small indie team / studio]
Scope: [game jam prototype / vertical slice / full release]
Primary inspiration: [1-3 games that are closest to what you're making]

Create the GDD with these sections:

**1. Vision Statement** (1 paragraph):
- What is the core experience? Complete this sentence: "The player should feel _____ because _____."
- The one mechanic or idea that makes this game worth existing alongside its inspirations

**2. Core Gameplay Loop**:
- The 30-second loop (moment-to-moment actions)
- The 5-minute loop (short-term goals and rewards)
- The 30-minute loop (session-level progression and satisfaction)
- Diagram the relationship between these loops

**3. Player Mechanics**:
- Core actions the player can take (move, shoot, build, etc.)
- Progression systems (how the player grows stronger/more capable)
- Risk/reward dynamics (what the player gambles and what they gain)

**4. World & Narrative**:
- Setting and tone (2-3 sentences)
- Story delivery method (cutscenes / environmental / emergent / none)
- How narrative reinforces gameplay (or stays out of its way)

**5. Art & Audio Direction**:
- Visual style reference (name 2-3 specific games or artists)
- Color palette and mood keywords
- Audio priorities (music style, key sound effects, voice acting yes/no)

**6. Technical Scope**:
- Target engine and tools
- Must-have features vs. nice-to-have features (ranked)
- Biggest technical risk and mitigation plan

**7. Milestone Plan**:
- Prototype milestone: what's playable and what's placeholder
- Alpha milestone: feature-complete checklist
- Beta milestone: polish and content targets
- What to cut first if you're behind schedule

Help me design a game level or puzzle that teaches through play and escalates in complexity.

Game genre: [platformer / puzzle / metroidvania / stealth / adventure / other]
Core mechanic being used: [e.g., gravity switching, time rewind, block pushing, grapple hook, light/shadow]
Where this level falls in the game: [tutorial / early game / mid game / late game / bonus/secret]
Player's current skill level at this point: [what mechanics they've already mastered]
New concept this level introduces: [the one new thing the player will learn here]

Design the level in these phases:

**Phase 1 — The Safe Introduction**:
- A simple room or section where the new mechanic is presented with zero risk of failure
- How the player discovers the mechanic naturally (environmental cues, not text tutorials)
- The "aha moment": what realization should click in the player's mind

**Phase 2 — The Controlled Challenge**:
- 2-3 escalating rooms that test the new mechanic in isolation
- Each room adds one variable (timing, enemies, environmental hazard)
- Clear success/failure feedback so the player knows what went wrong

**Phase 3 — The Combination**:
- A section that requires combining the new mechanic with a previously learned one
- The "genius moment": the player feels clever for making the connection themselves
- Optional hint system: how to help stuck players without ruining the discovery

**Phase 4 — The Twist**:
- A final challenge that subverts expectations — the mechanic works differently than assumed, or the environment changes the rules
- This section should make the player rethink everything they just learned

**Level Flow Diagram**:
- Map out the critical path from entrance to exit
- Mark optional areas, secrets, and shortcuts
- Note pacing: where the player rests, where tension peaks, where they feel rewarded

**Common Design Pitfalls to Avoid**:
- 3 specific mistakes that would make this level frustrating instead of challenging
- How to playtest for difficulty calibration
- The "watch someone play" checklist: what to observe when someone else tries your level

Help me build a comprehensive lore bible for my game world that's deep enough to inform every design decision but organized enough to actually use.

Game title (working): [name]
Genre and setting: [e.g., post-apocalyptic sci-fi, dark fantasy, cyberpunk noir]
Scale of the world: [single city / region / continent / planet / multiverse]
Time period the game takes place in: [and how much history matters to gameplay]
Tone: [grim / hopeful / absurdist / mythic / grounded / psychedelic]

Build the lore bible in these sections:

**Cosmology & Origin**:
- How the world came to be (the creation myth people believe vs. what actually happened)
- The fundamental rules of this world (what's possible that isn't in ours, what's impossible that is)
- The cosmic or existential threat looming over everything (if any)

**History Timeline** (5-8 key events):
- For each event: what happened, who was involved, what changed permanently
- Which events are common knowledge vs. lost/suppressed history
- How the current state of the world is a direct consequence of these events

**Factions & Power Structures**:
- 3-5 major factions, each with: name, ideology, territory, leader, strength, weakness, what they want from the player
- How these factions interact (alliances, rivalries, trade, cold wars)
- Where the player fits in this power structure at the start vs. by the end

**Culture & Daily Life**:
- What ordinary people care about (not just kings and heroes)
- Currency, trade, and economy in one paragraph
- Religion, superstition, or belief systems
- Technology level and how it varies between factions
- Art, music, entertainment — what do people do for fun in this world?

**The Lore Iceberg**:
- Surface level: what the player learns in the first hour
- Mid level: what observant players discover through exploration
- Deep level: secrets that recontextualize the entire story
- Hidden level: developer lore that's never stated but informs everything

**Design Integration Notes**:
- How lore should influence level design, enemy design, item descriptions, and NPC dialogue
- 5 environmental storytelling opportunities (stories told through the world, not words)
- Naming conventions for places, characters, and items that feel consistent

Help me write a branching dialogue tree for an important conversation in my game.

Characters in the conversation: [player character + NPC name and personality]
Context: [what's happening in the story, where this conversation takes place]
What the player needs to learn from this conversation: [key information or quest details]
What the NPC wants: [their goal in this conversation — it shouldn't just be "give the player info"]
Emotional stakes: [what makes this conversation matter beyond plot mechanics]
Number of meaningful branches: [2-3 for a simple exchange, 4-6 for a major decision point]

Write the dialogue tree with these elements:

**Opening Exchange** (2-3 lines each, no choices yet):
- Establish the tone and the NPC's current emotional state
- Give the player a reason to care about what comes next
- Plant a subtle hint about the conversation's hidden layer

**Branch Point 1** (player choice):
- Option A: [Diplomatic / Empathetic] — the kind approach
- Option B: [Direct / Aggressive] — the confrontational approach
- Option C: [Cunning / Deceptive] — the manipulative approach
- (Optional) Option D: [Unusual / Creative] — the unexpected approach that rewards lateral thinking
- Write the NPC's distinct reaction to each (they should feel meaningfully different, not just "slightly different wording to the same outcome")

**Branch Point 2** (consequences deepen):
- Each branch from Point 1 leads to a new situation with its own choices
- At least one branch should reveal information the others don't
- At least one branch should close off a future option permanently

**Resolution Variants**:
- Best outcome: player gets what they want AND preserves the relationship
- Good outcome: player gets what they want but damages something
- Bad outcome: player fails to get what they want but learns something crucial
- Hidden outcome: unlocked only by a specific combination of choices or having prior knowledge

**Implementation Notes**:
- Flag each branch with variables to track (for consequences later in the game)
- Note which lines can be reused across branches to save writing/recording budget
- Mark lines that require voice acting direction (emotional beats, pauses, tone shifts)

Help me write a structured, thoughtful game review that goes beyond "I liked it" or "I didn't."

Game: [title]
Platform played on: [PC / console / mobile]
Hours played: [approximate]
Completed?: [yes / no / abandoned at what point]
My overall feeling: [loved it / liked it / mixed / disappointed / hated it]
My gaming background: [what genres I usually play, skill level, what I value in games]

Structure the review as follows:

**The Hook** (opening paragraph):
- Start with a specific moment from the game that captures its essence — not a plot summary
- Set up the central question the review will answer
- Make the reader want to keep reading whether they've played the game or not

**What It's Trying to Do** (1-2 paragraphs):
- Describe the game's apparent ambition — what experience is it trying to create?
- How does it position itself relative to its genre (traditional, innovative, subversive)?
- Who is this game for? (Not everyone — be specific)

**What It Does Well** (2-3 paragraphs, with specific examples):
- Mechanics: What feels good to do? What systems click together satisfyingly?
- Aesthetics: What looks, sounds, or feels remarkable?
- Design: What decisions show thoughtfulness and craft?
- For each point, describe a specific moment, not a general impression

**What It Struggles With** (2-3 paragraphs, with specific examples):
- Be precise about what's wrong and why it matters to the overall experience
- Distinguish between personal preference ("I don't like this genre convention") and genuine design flaws ("this system undermines the game's own goals")
- Suggest what a fix might look like (shows you understand the problem, not just the symptom)

**The Verdict** (closing paragraph):
- Return to the central question from the hook
- Who should play this and who should skip it
- Where it sits in its genre — is it a must-play, a hidden gem, a noble failure, or a missed opportunity?
- One final image or moment that the player will carry with them

Avoid: numerical scores, "graphics are good" without specifics, spoilers without warnings, comparing to every other game in the genre.

Help me plan a speedrun route for a game, breaking down the optimal path from start to finish.

Game: [title and version/platform]
Category: [Any% / 100% / specific category]
My current best time: [or "first attempt" if new to speedrunning this game]
Known skips or glitches I can execute: [list any you're comfortable with]
Known skips I can't do yet: [list difficult tricks you're still learning]
Current world record: [time and runner, if known]

Build the route with these sections:

**Route Overview**:
- Total segments/splits and estimated time for each
- The critical path: what must be done and in what order
- What gets skipped entirely and why (items, areas, cutscenes, bosses)
- Major decision points where the route could branch based on RNG or execution

**Segment-by-Segment Breakdown**:
For each major segment:
- Optimal movement path (describe precise movement through each area)
- Time-saving tricks ranked by difficulty and time saved
- "Safety strats" for each trick (slower but consistent alternatives)
- RNG factors: what can go wrong that's outside your control, and how to react
- Menuing: any inventory, equipment, or menu manipulation needed

**Time Save Priority List**:
- Rank every potential time save from easiest to hardest
- For each: time saved, consistency rate, and practice method
- Identify the "free" time saves everyone should get vs. the "grind" saves for competitive times
- The point of diminishing returns: when to stop optimizing and start running

**Practice Plan**:
- Which segments to practice in isolation and how
- Common mistakes and how to recover from them mid-run
- Mental checkpoints: what to think about at each split
- When to reset vs. when to keep going (the reset threshold for each segment)

**Run Day Strategy**:
- Warm-up routine before attempts
- How many attempts per session before fatigue hurts performance
- How to handle bad early segments (push through or reset?)
- The mindset for PB attempts vs. practice runs

Help me brainstorm and plan a game mod that would genuinely improve or transform the player experience.

Game to mod: [title]
Modding tools available: [official mod tools, community tools, or code-level access]
My modding experience: [beginner / intermediate / experienced]
What I wish the game did differently: [the frustration or desire driving this mod]
Scope I'm comfortable with: [texture swap / UI tweak / new mechanic / total conversion / new content]

Generate 5 mod concepts, ranging from simple to ambitious:

**Mod 1 — Quality of Life** (small scope, high impact):
- A simple change that fixes a universal annoyance
- Why the base game doesn't do this (design oversight vs. intentional choice)
- Implementation approach and estimated effort

**Mod 2 — Rebalance** (medium scope):
- A systems-level change that shifts how the game feels to play
- What's currently unbalanced and how this mod addresses it
- Risk of breaking other systems and how to mitigate it

**Mod 3 — New Content** (medium-large scope):
- A new area, quest, character, or item set that fits the game's existing style
- How it integrates with existing content without feeling bolted-on
- Content pipeline: what assets need to be created and in what order

**Mod 4 — Mechanical Innovation** (large scope):
- A new gameplay system that the base game doesn't have
- How it interacts with existing mechanics
- The minimum viable version vs. the dream version

**Mod 5 — Total Conversion** (ambitious):
- A complete reimagining using the game's engine
- What makes this game's engine suitable for this vision
- Scope management: how to release in phases so players get something before it's "done"

For each mod concept:
- Unique selling point (why someone would download this over alternatives)
- Compatibility concerns with other popular mods
- Community reception prediction (would this be controversial?)
- First steps: what to do in the first weekend of development

Generate 5 game jam concepts that are creative, feasible within a tight deadline, and built around a specific theme or constraint.

Jam theme/constraint: [e.g., "only one button," "the world changes every 10 seconds," "role reversal," or leave blank for open-ended]
Time available: [24 hours / 48 hours / 72 hours / 1 week]
Team: [solo / 2 people / small team — list roles available: programmer, artist, audio, designer]
Engine: [Unity / Godot / Unreal / GameMaker / Pico-8 / web/JS / other]
My strengths: [what I'm fastest at — gameplay code, pixel art, music, level design, narrative]
My weaknesses: [what I'm slowest at or can't do]

For each concept:

**The Pitch** (2 sentences max):
- What the player does and why it's interesting
- How it connects to the jam theme (if applicable)

**Core Mechanic** (1 mechanic only — scope is everything):
- Describe the single interaction that makes this game work
- Why this mechanic is inherently fun or interesting (the "juice")
- How it connects to the theme in a non-obvious way

**Minimum Viable Game** (what to build in the first 25% of the jam):
- The playable core: what do you need to have a "game" vs. a tech demo?
- Placeholder strategy: what can be ugly/simple initially and polished later?
- The "is this fun?" test: how to evaluate at the halfway point whether to continue or pivot

**Polish Priority** (what to add if you have time):
- Ranked list of additions from highest to lowest impact
- Sound and juice: which 3 sound effects and 3 visual effects would add the most feel
- The one "wow" moment: a single impressive detail that makes judges or players remember your game

**Scope Traps to Avoid**:
- The feature that sounds essential but will eat 6 hours and add 10% to the experience
- Art trap: where you'll be tempted to over-polish visuals at the expense of gameplay
- The "just one more thing" danger zone: when to stop adding and start polishing

**Submission Checklist**:
- Title screen and basic UI (5 minutes of work that looks professional)
- A compelling screenshot and description for the jam page
- The 30-second pitch for judges: what makes this worth playing?