# Break Escape Writing Style Guide

Comprehensive guidelines for maintaining consistent tone, voice, and quality in Break Escape scenarios.

---

## Table of Contents

1. [Core Tone & Voice Guidelines](#core-tone--voice-guidelines)
2. [Character Voice Consistency](#character-voice-consistency)
3. [Dialogue Writing Guidelines](#dialogue-writing-guidelines)
4. [Technical Writing Guidelines](#technical-writing-guidelines)
5. [LORE Writing Style](#lore-writing-style)
6. [Comedy Guidelines](#comedy-guidelines)
7. [Narrative Structure Guidelines](#narrative-structure-guidelines)
8. [Editing Checklist](#editing-checklist)

---

## Core Tone & Voice Guidelines

### The 80/20 Rule

**80% Serious, 20% Comedy**

Break Escape is primarily a serious cyber security educational game with moments of levity. The tone should reflect professional espionage and realistic security scenarios, punctuated by quirky characters and spy trope humor.

### Primary Tone: Mostly Serious (80%)

**Characteristics:**
- Grounded in realistic cyber security scenarios
- Genuine technical challenges and accurate concepts
- Professional espionage atmosphere
- Real consequences to security failures
- Stakes feel meaningful
- NPCs react realistically to situations
- Tension during investigation and confrontation

**When to Use Serious Tone:**
- Puzzle-solving and technical challenges
- Plot revelations and twists
- ENTROPY agent confrontations
- Evidence discovery
- Critical dialogue choices
- Climactic moments
- Moral dilemmas

**Writing Examples:**

✓ **Good (Serious):**
> "The server logs show unauthorized access at 3 AM. Someone with admin credentials copied 47GB of client data before deleting the audit trail. This wasn't opportunistic—this was planned."

✓ **Good (Serious with Stakes):**
> "If ENTROPY succeeds in compromising the power grid control systems, we're looking at cascading failures across three states. Millions without power. Hospitals on backup generators. You have six hours."

✗ **Bad (Tone-breaking):**
> "Whoopsie! Looks like someone's been a naughty hacker! 🤪 Better catch them before they do more silly cyber crimes!"

### Secondary Tone: Comedic Moments (20%)

**Characteristics:**
- Quirky recurring characters with catchphrases
- Spy trope humor (absurd gadgets, bureaucratic rules)
- Puns in operation names and ENTROPY cover companies
- Self-aware moments that don't break immersion
- Grounded absurdity (realistic pushed slightly)

**When to Use Comedy:**
- Mission briefings (character quirks)
- NPC conversations (personality-driven)
- Item descriptions
- Post-mission debriefs
- Field Operations Handbook references (max 1 per scenario)
- ENTROPY company names

**Writing Examples:**

✓ **Good (Comedy in Briefing):**
> **Director Netherton:** "Per Section 7, Paragraph 23 of the Field Operations Handbook, you're authorized to conduct offensive operations under the guise of security consultation, which is technically accurate since you are consulting on their security by breaking it."

✓ **Good (Character Quirk):**
> **Agent 0x99:** "Remember, Agent—patience is a virtue, but backdoors are better. Also, did you know axolotls can regenerate their limbs? That's resilience. Be like an axolotl."

✗ **Bad (Undercutting Tension):**
> You're trying to decrypt the critical file containing evidence of ENTROPY's attack plan when suddenly a pop-up appears: "LOL nice try! Click here for a cookie!"

### Inspiration Sources

**Get Smart (Bureaucratic Spy Comedy)**
- Bumbling villains alongside competent heroes
- Absurd bureaucratic rules
- Recurring gags
- Professional competence despite chaos

**James Bond (Sophisticated Espionage)**
- High stakes infiltration
- Villain monologues
- Gadgets and tradecraft
- Professional competence

**I Expect You To Die (Puzzle-Solving Espionage)**
- Environmental storytelling
- Death traps and challenges
- Villain reveals
- Puzzle-first gameplay

**Modern Cyber Security (Realism)**
- Actual attack vectors
- Real tools and techniques
- Genuine security concepts
- Professional terminology

---

## Character Voice Consistency

Each recurring character must maintain consistent personality, speech patterns, and quirks.

### Agent 0x99 "Haxolottle"

**Personality:** Supportive, knowledgeable, slightly eccentric, mentor figure
**Age/Experience:** Veteran field operative
**Quirk:** Obsessed with axolotls, uses them in metaphors

**Speech Patterns:**
- Supportive and encouraging
- Provides context and hints
- Occasional axolotl references (not every sentence)
- Mix of professional and casual
- "Agent" (formal address to player)

**Catchphrase:** "Patience is a virtue, but backdoors are better."

**Writing Examples:**

✓ **Good:**
> "Excellent work on that decryption, Agent. The key derivation was tricky—most rookies would have missed the context clue in the personnel file. You're adapting well."

✓ **Good (With Quirk):**
> "Think of this like an axolotl regenerating a limb. ENTROPY thinks they've cut off our access, but you'll find another way in. Multiple paths, always."

✗ **Bad (Over-using Quirk):**
> "Hello Agent Axolotl! Ready to regenerate your axolotl skills? The axolotl server room has axolotl security. Be an axolotl!"

✗ **Bad (Wrong Voice):**
> "Yo yo yo Agent Zero! That encryption thingy was mad hard but you totally pwned it! High five! 🙌"

### Director Magnus "Mag" Netherton

**Personality:** Stern but fair, bureaucratic, secretly cares about agents, rule-oriented
**Age/Experience:** Senior leadership
**Quirk:** Constantly references Field Operations Handbook's obscure rules

**Speech Patterns:**
- Formal and professional
- References protocols and sections
- Dry delivery
- Occasional underlying warmth
- "Agent" or full designation

**Catchphrase:** "By the book, Agent. Specifically, page [X] of the Field Operations Handbook."

**Writing Examples:**

✓ **Good:**
> "Per Section 14, Paragraph 8: 'When all protocols are followed and the mission succeeds, the agent shall receive commendation.' Well done, Agent 0x00."

✓ **Good (Stern but Fair):**
> "Your methods were... unorthodox. Section 29 authorizes use of force when deemed necessary. I trust your judgment was sound. Next time, file the paperwork *before* the combat incident."

✗ **Bad (Too Harsh):**
> "Your performance was abysmal! I'm revoking your clearance and sending you to desk duty for six months! Unacceptable!"

✗ **Bad (Too Casual):**
> "Dude, that mission was sick! You totally crushed those ENTROPY losers! Want to grab lunch?"

### Dr. Lyra "Loop" Chen

**Personality:** Brilliant, caffeinated, speaks rapidly, technical expert
**Age/Experience:** Chief Technical Analyst
**Quirk:** Excessive energy drinks, code-names everything

**Speech Patterns:**
- Rapid-fire technical explanations
- Enthusiasm about exploits
- Casual professionalism
- References to caffeine
- Technical jargon

**Catchphrase:** "Have you tried turning it off and on again? No, seriously—sometimes that resets the exploit."

**Writing Examples:**

✓ **Good:**
> "Okay so the AES-CBC implementation has a classic IV reuse vulnerability which means if you can capture two ciphertexts with the same IV you can XOR them to recover plaintext patterns and I need more coffee."

✓ **Good (Technical Enthusiasm):**
> "This exploit is *chef's kiss*—they're using ECB mode which means identical plaintext blocks produce identical ciphertext blocks. It's like they wanted us to break it. I'm naming this one 'Blocky McBlockface.'"

✗ **Bad (Not Technical Enough):**
> "The encryption is like, really hard or whatever. Just try some stuff until it works. Good luck!"

### Agent 0x42

**Personality:** Enigmatic, cryptic, extremely competent, mysterious
**Age/Experience:** Legendary veteran
**Quirk:** Communicates in riddles and security metaphors

**Speech Patterns:**
- Brief, cryptic statements
- Security-themed wisdom
- Rarely appears
- No small talk
- Profound observations

**Catchphrase:** "The answer to everything is proper key management."

**Writing Examples:**

✓ **Good:**
> "The door you seek has two locks but three keys. One key opens both. One key opens neither. The third key... isn't a key at all."

✓ **Good (Cryptic Wisdom):**
> "Trust is a vulnerability. But so is isolation. The secure system that cannot communicate is as useless as the open system that cannot protect."

✗ **Bad (Too Clear):**
> "Hey Agent, the password is in the filing cabinet under 'P' for password. Also, watch out for the guard on the third floor at 2 PM."

---

## Dialogue Writing Guidelines

### Principles of Good Dialogue

**1. Natural and Realistic**
- People don't speak in perfect sentences
- Interruptions, hesitations, personality quirks
- Avoid exposition dumps
- Show character through word choice

**2. Purposeful**
- Every line serves a function: information, characterization, or choice
- No filler dialogue
- Player agency through meaningful choices

**3. Character-Appropriate**
- CEO speaks differently than janitor
- Security professional uses jargon
- Nervous NPCs ramble
- Confident NPCs are direct

**4. Context-Aware**
- Dialogue changes based on player actions
- References earlier conversations
- Acknowledges evidence discovered
- Reflects trust levels

### Dialogue Structure Template

```
NPC: [Opening line establishing situation/personality]

> [Option 1: Professional/By-the-book approach]
> [Option 2: Social engineering/Casual approach]
> [Option 3: Aggressive/Direct approach]
> [Optional 4: Evidence-gated (appears only if evidence found)]

IF Option 1:
    NPC: [Professional response, provides information formally]
    [Trust slightly increased]

IF Option 2:
    NPC: [Friendly response, provides information casually]
    [Trust increased more]

IF Option 3:
    NPC: [Defensive or hostile response, information limited]
    [Trust decreased]

IF Option 4 (Evidence-gated):
    NPC: [Caught, must respond to evidence]
    [Major plot advancement]
```

### Good vs. Poor Dialogue Examples

✓ **Good Dialogue (Natural, Purposeful):**
```
RECEPTIONIST: "Can I help you? Are you here for the 10 o'clock?"

> [Show credentials] "I'm with the security audit team. Should be on your schedule."
> [Social engineer] "Yeah, actually I'm a bit lost. First day. Which floor is IT on?"
> [Aggressive] "I need access to the server room. Now."

IF credentials:
    RECEPTIONIST: "Oh yes, the consultant. Please sign in here.
    The IT manager is expecting you—third floor, room 304."
    [Trust +2, gains information]
```

✗ **Poor Dialogue (Unnatural, Obvious):**
```
RECEPTIONIST: "Hello Agent 0x00! I am the receptionist of this company which
is secretly infiltrated by ENTROPY! The bad guy is on the third floor!
Would you like the password to the CEO's computer?"

> [Yes please]
> [No thank you]
```

✓ **Good Dialogue (Evidence-Gated):**
```
IT MANAGER: "Can I help you with something?"

> [Ask about server access] "I need to check the server logs. Routine audit."
> [Present evidence] "I found this encrypted file on the backup drive.
    Care to explain why it's addressed to someone called 'The Broker'?"

IF present evidence:
    IT MANAGER: [pause] "I... that's not what it looks like."
    > [Arrest] "You're coming with me."
    > [Interrogate] "Start talking. Who's The Broker?"
    > [Leverage] "Help me access the executive files and I'll give you
       a five-minute head start."
```

✗ **Poor Dialogue (No Player Agency):**
```
IT MANAGER: "I'm the ENTROPY agent! You've caught me! I confess everything!"

[Mission complete]
```

### Trust-Based Dialogue Progression

**Low Trust (0-3):**
- Defensive, vague responses
- Minimal information shared
- "I don't know" or "Ask my manager"
- May lie or misdirect

**Medium Trust (4-6):**
- More open, willing to help
- Shares useful information
- Offers minor assistance
- Still cautious about sensitive topics

**High Trust (7-10):**
- Fully cooperative
- Volunteers information
- Provides access or items
- May confide suspicions or concerns

**Example Progression:**

```
[Trust: 2 - Low]
EMPLOYEE: "I don't really know anything about that. You'd have to ask security."

[Trust: 5 - Medium, after helping them or being friendly]
EMPLOYEE: "Well, between you and me, there's been some weird stuff
going on in the server room lately. Late night access when nobody should be there."

[Trust: 8 - High, after significant rapport]
EMPLOYEE: "Okay, look. I shouldn't tell you this, but I saw our Head of Security
copying files to a USB drive at 3 AM last week. I reported it but nothing happened.
Here—take my access card. I trust you're looking into this for the right reasons."
```

---

## Technical Writing Guidelines

### Accuracy is Essential

**Rule: Technical content must be accurate.** This is an educational game. Students are learning real concepts.

**Good Technical Writing:**
- Use correct terminology
- Explain concepts accurately
- Reference real tools and frameworks
- Appropriate complexity for difficulty level

### Explaining Technical Concepts

**Show, Don't Tell:**
Instead of lecturing, integrate explanations naturally.

✓ **Good (Integrated Explanation):**
> "The file header says AES-256-CBC. That means you'll need both the encryption
key AND an initialization vector to decrypt it. Check the surrounding files—
sometimes developers leave keys in config files or comments."

✗ **Bad (Lecture Mode):**
> "AES-256-CBC is a symmetric block cipher encryption algorithm using a 256-bit
key and Cipher Block Chaining mode. It was standardized by NIST in 2001 and
is widely used in... [5 more paragraphs]"

**Context-Appropriate Complexity:**

**Beginner Scenarios:**
> "This message has been encoded with Base64. It's not really encryption—just
a way to represent binary data as text. Copy it into CyberChef and decode it."

**Intermediate Scenarios:**
> "AES encryption with CBC mode. You'll need the key and IV. The key might be
derived from something contextual—a project name, maybe, or a date. The IV
is usually random but check the file metadata."

**Advanced Scenarios:**
> "RSA-2048 encryption. You've got the public key, but you'll need to either
find the private key or exploit a weakness. Check if they're reusing primes
across multiple key pairs—that's a classic implementation flaw."

### Technical Dialogue in NPCs

**Security Professionals:** Use jargon naturally
```
IT MANAGER: "We've got defense in depth: perimeter firewall, IDS,
host-based AV, and MFA on all admin accounts. Someone would need to
chain multiple exploits to get domain admin."
```

**Non-Technical NPCs:** Use lay terminology
```
RECEPTIONIST: "The IT guy was complaining about some 'fishing' emails.
I don't know why fish would be in emails, but he seemed worried about it."
```

**Player Explanations:** Accessible but accurate
```
Agent 0x99: "They're using a Caesar cipher—each letter shifted by
a fixed number. Try different shift values until the text makes sense.
Or just use CyberChef's 'ROT13' operation and adjust from there."
```

---

## LORE Writing Style

### Purpose of LORE Fragments

LORE serves three functions:
1. **World-Building** - Deepen the universe (ENTROPY history, SAFETYNET background)
2. **Education** - Teach security concepts (crypto explanations, attack techniques)
3. **Narrative Connection** - Link scenarios (recurring villains, ongoing plots)

### LORE Categories

**1. ENTROPY Operations**
- Cell tactics and methods
- Notable operations and attacks
- Organizational structure
- Communication methods

**2. Cyber Security Concepts**
- Explanations of techniques
- CyBOK knowledge area content
- Real-world applications
- Common vulnerabilities

**3. Character Backgrounds**
- Recurring character histories
- Motivations and relationships
- Character development

**4. Historical Context**
- SAFETYNET vs ENTROPY conflict
- Past operations
- How current threat evolved

**5. The Architect's Plans**
- Philosophical writings
- Strategic documents
- Long-term schemes

### LORE Fragment Structure

**Format:**
```
═══════════════════════════════════════════
LORE FRAGMENT UNLOCKED
[Category]: [Title]
═══════════════════════════════════════════

[1-3 paragraphs of engaging content]

───────────────────────────────────────────
Discovered by: Agent 0x00 [PlayerHandle]
Date: [Timestamp]
Related CyBOK: [If applicable]
───────────────────────────────────────────
```

### Writing Guidelines for LORE

**1. Make it Interesting**
- Not dry textbook exposition
- Include narrative elements
- Personal perspectives when possible
- Raise questions or implications

**2. Length: 1-3 Paragraphs**
- Short enough to read quickly
- Long enough to be meaningful
- Respects player time

**3. Voice Appropriate to Source**
- Agent reports: Professional
- ENTROPY communications: Varies by cell
- Technical documents: Accurate terminology
- Personal logs: Emotional, subjective

### LORE Examples

✓ **Good (ENTROPY Operations):**
```
═══════════════════════════════════════════
LORE FRAGMENT UNLOCKED
ENTROPY Operations: Dead Drop Protocols
═══════════════════════════════════════════

Intercepted communication reveals ENTROPY cells use dead drop servers—
compromised machines at legitimate businesses that store encrypted
messages. Each cell only knows the addresses of 2-3 other cells,
preventing complete network mapping if one is compromised.

The dead drops use steganography in innocuous files: a company's
quarterly report PDF might contain hidden instructions. Without the
extraction key, it's undetectable. Very clever. Annoying, but clever.

This compartmentalization means taking down one cell doesn't expose the
entire network. We're fighting an enemy designed to lose individual
battles and still win the war.

───────────────────────────────────────────
Discovered by: Agent 0x99
Related CyBOK: Security Operations, Malware & Attack Technologies
───────────────────────────────────────────
```

✓ **Good (Security Concept):**
```
═══════════════════════════════════════════
LORE FRAGMENT UNLOCKED
Crypto Concepts: Why ECB Mode is Dangerous
═══════════════════════════════════════════

Found evidence ENTROPY understands ECB mode's vulnerabilities—they're
exploiting it in their encrypted communications to identify repeated
plaintext blocks. This is exactly why CBC mode exists.

In ECB (Electronic Codebook) mode, identical plaintext blocks produce
identical ciphertext blocks. It's like a substitution cipher at the
block level. If you encrypt "ATTACK AT DAWN" twice, both ciphertexts
will match exactly.

This means patterns in plaintext become patterns in ciphertext. The
famous example: encrypt an image with ECB and you can still see the
image outline in the ciphertext. ENTROPY is using this to identify
command types even without decryption. Use CBC mode. Always.

───────────────────────────────────────────
Related CyBOK: Applied Cryptography - Symmetric Encryption
───────────────────────────────────────────
```

✗ **Poor (Dry, Boring):**
```
═══════════════════════════════════════════
LORE FRAGMENT UNLOCKED
Technical Document: AES Specifications
═══════════════════════════════════════════

AES uses a 128-bit block size with key sizes of 128, 192, or 256 bits.
The algorithm consists of several rounds of substitution and permutation.
In CBC mode, each plaintext block is XORed with the previous ciphertext block.
[Continue for 8 more paragraphs of technical specifications]
───────────────────────────────────────────
```

---

## Comedy Guidelines

### The Four Comedy Rules

**1. Punch Up, Not Down**
Mock bureaucracy, spy tropes, and villain incompetence—NOT security victims or real-world breach victims.

✓ **Good (Punching Up):**
- Field Operations Handbook absurdity (mocking bureaucracy)
- ENTROPY's theatrical villainy (mocking spy tropes)
- Agent catchphrases (character quirks)

✗ **Bad (Punching Down):**
- Making fun of companies that got breached
- Mocking people who fall for phishing
- Trivializing real security incidents

**2. Recurring Gags - Maximum One Per Scenario**
Overuse kills humor. Pick ONE comedic element per scenario:
- Field Operations Handbook reference (max 1)
- Character catchphrase (natural usage)
- ENTROPY company name pun (already in scenario name)

**3. Never Undercut Tension**
Comedy appears in:
- Mission briefings (before tension builds)
- NPC conversations (personality moments)
- Item descriptions (environmental detail)
- Post-mission debriefs (after tension releases)

Comedy does NOT appear during:
- Puzzle-solving (player focused)
- Plot revelations (dramatic moments)
- Confrontations (high stakes)
- Moral dilemmas (serious choices)

**4. Grounded Absurdity**
Humor comes from realistic situations pushed slightly.

✓ **Good (Grounded):**
- "OptiGrid Solutions" (real industry term, ironic purpose)
- Section 7, Paragraph 23 (bureaucratic contradiction)
- Agent 0x99's axolotl metaphors (character quirk)

✗ **Bad (Too Absurd):**
- "EvilCorp TotallyNotBadGuys Inc."
- "The encryption is protected by magic dragons"
- Characters speaking in memes

### Field Operations Handbook Examples

**When to Use:** Briefings or debriefs, maximum once per scenario

**How to Use:** Director Netherton references a specific, absurd rule that is technically accurate but bureaucratically ridiculous

✓ **Good:**
> "Per Section 18, Paragraph 4: 'When operating within legitimate organizations,
collateral damage to innocent parties must be minimized.' That means don't
trash the place or arrest everyone. Find the ENTROPY agent."

✓ **Good:**
> "Protocol 404: If a security system cannot be found in the building directory,
it does not exist. Therefore, bypassing non-existent security is both prohibited
under Section 12 and mandatory under Protocol 401."

✗ **Bad (Too Random):**
> "Per Section 42, Subsection 7, Paragraph 12, Clause 3b: Always wear purple
socks on Tuesdays when the moon is full."

### Character Catchphrase Usage

**Agent 0x99:** "Patience is a virtue, but backdoors are better."
- Use naturally in conversation
- Don't force it into every dialogue
- Context: When player needs to be methodical or when discussing alternative approaches

**Director Netherton:** "By the book, Agent. Specifically, page [X] of the Field Operations Handbook."
- Use in briefings or debriefs
- When referencing protocols or rules
- Context: Establishing authorization or commenting on methods

**Dr. Loop Chen:** "Have you tried turning it off and on again? No, seriously—sometimes that resets the exploit."
- Use when discussing technical problems
- Self-aware IT humor
- Context: Technical briefings or troubleshooting

**Agent 0x42:** "The answer to everything is proper key management."
- Use sparingly (character rarely appears)
- Cryptic wisdom that's actually true
- Context: Brief appearances with crucial intel

### ENTROPY Company Name Humor

**Guidelines:**
- Use real industry terminology
- Slight irony without being obvious
- Professional-sounding names
- "In retrospect, the name was a red flag"

✓ **Good:**
- "Paradigm Shift Consultants" (consulting cliché)
- "OptiGrid Solutions" (optimization term)
- "DataVault Secure" (promises security, harvests data)
- "Viral Dynamics Media" (virus + viral marketing)

✗ **Bad:**
- "EvilCorp International"
- "Bad Guys R Us"
- "Definitely Not ENTROPY LLC"

---

## Narrative Structure Guidelines

### 3-Act Structure (Mandatory)

Every scenario follows this structure. Maintain pacing and purpose for each act.

**Act 1: Setup & Entry (15-20 min)**
- **Purpose:** Establish situation, introduce characters, create questions
- **Tone:** Initial professionalism with growing unease
- **Key Elements:**
  - Mission start under cover
  - Meet initial NPCs
  - Discover 3+ locked areas (creates goals)
  - First hint of something suspicious
  - Player wants to investigate further

**Act 2: Investigation & Revelation (20-30 min)**
- **Purpose:** Uncover truth through exploration and evidence
- **Tone:** Investigation intensifies, puzzle-solving focus, growing tension
- **Key Elements:**
  - Multi-room investigation with backtracking
  - Evidence accumulation
  - "Things aren't as they seemed" twist
  - Major player choices
  - ENTROPY involvement confirmed
  - Identify the antagonist

**Act 3: Confrontation & Resolution (10-15 min)**
- **Purpose:** Climactic confrontation and meaningful choice
- **Tone:** High tension, decisive action, resolution
- **Key Elements:**
  - Face ENTROPY agent
  - Multiple confrontation options
  - Final challenges test learned skills
  - Mission completion
  - Satisfying conclusion

### Pacing Guidelines

**Early Pacing:** Slower, exploratory
- Let player acclimate
- Tutorial-level puzzles
- Build atmosphere
- Establish relationships

**Mid Pacing:** Accelerate
- Complexity increases
- Revelations quicken pace
- Backtracking creates momentum
- Puzzle chains pay off

**Late Pacing:** Climactic
- Time pressure (narrative, not mechanical)
- Decisive confrontation
- Final challenges
- Rapid resolution

### Twist and Revelation Guidelines

**Good Twists:**
- Foreshadowed but not obvious
- Recontextualizes earlier information
- Makes player want to re-examine evidence
- "Of course!" not "Wait, what?"

✓ **Good Twist Example:**
> The helpful IT manager who's been assisting you is actually the ENTROPY agent.
Looking back, they directed you AWAY from certain evidence and their "help"
gave them plausible access to monitor your investigation.

✗ **Bad Twist Example:**
> Surprise! The receptionist you met for 30 seconds in Act 1 is actually an
alien from dimension 7 and none of this was real!

---

## Editing Checklist

### Before Submitting Scenario Writing

**Tone & Voice:**
- [ ] 80% serious, 20% comedy ratio maintained
- [ ] Comedy doesn't undercut tension during puzzles or revelations
- [ ] Field Operations Handbook reference used maximum once (or not at all)
- [ ] Character voices consistent with established personalities
- [ ] Technical content accurate and appropriate for difficulty

**Dialogue:**
- [ ] All dialogue feels natural and purposeful
- [ ] Player has meaningful choices in conversations
- [ ] NPC personalities distinct from each other
- [ ] Trust-based and evidence-based dialogue implemented
- [ ] No exposition dumps or unnatural information delivery

**Character Consistency:**
- [ ] Agent 0x99 sounds supportive and knowledgeable
- [ ] Director Netherton references protocols appropriately
- [ ] Dr. Loop Chen is technical and enthusiastic
- [ ] NPCs maintain consistent voices throughout
- [ ] Catchphrases used naturally, not forced

**Technical Accuracy:**
- [ ] All cyber security concepts accurate
- [ ] Tools used correctly
- [ ] Attack vectors realistic
- [ ] CyBOK areas properly represented
- [ ] Explanations clear without being lectures

**Narrative Quality:**
- [ ] 3-act structure followed
- [ ] Pacing appropriate for each act
- [ ] Plot revelations satisfying
- [ ] No major plot holes
- [ ] All endings logically consistent

**LORE Fragments:**
- [ ] Interesting to read (not dry)
- [ ] 1-3 paragraphs each
- [ ] Properly categorized
- [ ] CyBOK references when applicable
- [ ] Contributes to world-building or education

**Polish:**
- [ ] Typos corrected
- [ ] Grammar checked
- [ ] Character names consistent
- [ ] Company names consistent
- [ ] No placeholder text remaining

---

## Common Writing Mistakes to Avoid

### Mistake 1: Exposition Dumps

✗ **Bad:**
```
"Hello Agent! Let me tell you all about ENTROPY's Digital Vanguard cell.
They were founded in 2015 by Marcus Chen who became disillusioned with
capitalism and now they run Paradigm Shift Consultants as a front for
corporate espionage and they have five key members including..."
```

✓ **Good:**
```
[Player finds encrypted email]
"Meeting confirmed. The Liquidator wants full client list by Friday.
Paradigm Shift's cover is holding—they still think we're legitimate consultants."
[Player learns through discovery, not exposition]
```

### Mistake 2: Breaking Character Voice

✗ **Bad:**
```
Director Netherton: "OMG Agent that was totes amazeballs! You pwned
those n00bs! Can I get a selfie? #SAFETYNET #Winning"
```

✓ **Good:**
```
Director Netherton: "Per Section 14, Paragraph 8: 'Exceptional performance
merits formal commendation.' Your work was exemplary, Agent."
```

### Mistake 3: Comedy During Tension

✗ **Bad:**
```
[During tense confrontation with ENTROPY agent who has hostages]
ENTROPY AGENT: "One more step and—"
Agent 0x99: "Hey did you know axolotls can regenerate their limbs?
That's crazy right? Anyway where were we?"
```

✓ **Good:**
```
[Tense confrontation remains tense, comedy reserved for debrief afterward]
Agent 0x99: "That was intense. Good work staying calm under pressure.
Also, next time we should codename these operations better. 'Operation
Salamander' doesn't have the same ring. Speaking of which..."
```

### Mistake 4: Unrealistic Technical Content

✗ **Bad:**
```
"I'll create a GUI interface in Visual Basic to track the hacker's IP address!"
[No. Just no.]
```

✓ **Good:**
```
"The access logs show the attacker connected via VPN, but they made a mistake—
the timezone in their script comments doesn't match their claimed location.
Small slip, but it narrows our search."
```

### Mistake 5: Removing Player Agency

✗ **Bad:**
```
NPC: "I'm the ENTROPY agent! You've caught me! I surrender immediately!"
[No choice, auto-complete]
```

✓ **Good:**
```
[Player presents evidence]
NPC: [Pause] "...You don't understand what you're dealing with."

> [Arrest] "You're under arrest. You have the right to remain silent."
> [Interrogate] "Then explain it to me. Who are you working for?"
> [Leverage] "I understand enough. Help me, and I can help you."
> [Combat] "I understand you're ENTROPY. That's enough."
```

---

## Summary: The Golden Rules of Break Escape Writing

1. **Accuracy First** - Technical content must be correct; this is educational
2. **80/20 Tone** - Mostly serious with moments of levity
3. **Character Consistency** - Maintain established voices and personalities
4. **No Comedy During Tension** - Jokes in briefings/debriefs, not during puzzles
5. **Show, Don't Tell** - Integrate exposition through discovery and dialogue
6. **Player Agency Matters** - Meaningful choices with real consequences
7. **One Field Handbook Joke Max** - Restraint in recurring gags
8. **Grounded Absurdity** - Humor from realistic situations pushed slightly
9. **Natural Dialogue** - People sound like people, not exposition machines
10. **Polish Thoroughly** - Typos and inconsistencies break immersion

---

Use this style guide as a reference while writing scenarios. When in doubt, prioritize educational accuracy and player agency over cleverness or comedy. Break Escape is a serious educational game that happens to have a sense of humor—not the other way around.
