cybersecurity/BreakEscape
1
0
Fork 0
mirror of https://github.com/cliffe/BreakEscape.git synced 2026-02-21 11:18:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

feat: Add Agent 0x00 intro cutscene and lore exploration dialogue system

Browse Source 
- Add agent_0x00_cyber_division_intro.ink: Introduction cutscene for Agent 0x00 joining SAFETYNET's CYBER-PHYSICAL division
  * Introduces Director Netherton and Agent 0x99 "Haxolottle"
  * Player makes meaningful choices affecting relationships
  * Tracks influence with netherton_respect and haxolottle_trust variables
  * Establishes player_attitude and specialization_interest
  * Multiple branching paths based on player responses

- Add lore_exploration_hub.ink: Reusable dialogue system for exploring ENTROPY and SAFETYNET lore
  * Hub-based conversation pattern with multiple NPCs
  * Tracks influence with handler, tech support, director, and fellow agents
  * Progressive revelation system (deeper topics unlock with higher influence)
  * Covers ENTROPY origins, philosophy, cells, and tactics
  * Covers SAFETYNET mission, methods, shadow war, and field operations
  * Deep lore unlocks: Berlin Crisis, handler backstory, moral complexity
  * Works with different speakers (Haxolottle, Dr. Chen, Director Netherton)
  * Mission-agnostic design for reusability

- Add comprehensive README.md documenting:
  * File purposes and when to use them
  * Variables reference and influence tracking system
  * Character voice guidelines for each NPC
  * Integration examples and usage guidelines
  * Testing checklist and quality standards
  * Future expansion ideas

All dialogue follows established character voices from universe bible and
implements influence-based relationship progression system.
This commit is contained in:
Z. Cliffe Schreuders
2025-11-18 10:36:08 +00:00
parent 147c4af225
commit 7f7ee5d761
3 changed files with 1929 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

389
story_design/ink/README.md Normal file
View File

@@ -0,0 +1,389 @@
# Break Escape - Ink Dialogue Scripts
This directory contains Ink dialogue scripts for the Break Escape universe, focusing on Agent 0x00's introduction to SAFETYNET's CYBER-PHYSICAL division and reusable lore exploration systems.
## Files
### 1. `agent_0x00_cyber_division_intro.ink`
**Purpose**: Introduction cutscene for Agent 0x00 joining the CYBER-PHYSICAL division
**When to Use**:
- Campaign opening sequence
- Tutorial/onboarding for new players
- Character establishment moment
**Key Features**:
- Introduces Director Netherton and Agent 0x99 "Haxolottle"
- Establishes SAFETYNET HQ atmosphere
- Player makes meaningful choices affecting relationships
- Sets up future character dynamics
**Variables Set**:
- `netherton_respect` (0-100) - Director's assessment of the agent
- `haxolottle_trust` (0-100) - Handler's confidence in the agent
- `player_attitude` - Character approach style (eager, cautious, confident, analytical)
- `specialization_interest` - Career direction hints (cyber, physical, hybrid)
- `knows_cyber_division` - Lore flag
- `knows_handler_role` - Lore flag
- `professional_impression` - Initial standing
**Narrative Structure**:
1. **Summons to HQ** - Player receives mysterious call to Director's office
2. **Director Netherton Briefing** - Formal introduction to CYBER-PHYSICAL division
3. **Handler Introduction** - Meeting Agent 0x99 "Haxolottle"
4. **Philosophy Questions** - Player expresses operational approach
5. **Orientation Setup** - Transition to ongoing work
**Character Moments**:
- Director Netherton's stern but caring demeanor
- Haxolottle's warm, mentor personality and axolotl metaphors
- Tension between Netherton's formality and Haxolottle's casualness
- Player agency through multiple choice branches
**Integration Notes**:
- Can reference `player_name` external variable
- Can reference `previous_missions_completed` for continuity
- All relationship variables persist for future scenarios
- Multiple endings based on player choices
---
### 2. `lore_exploration_hub.ink`
**Purpose**: Reusable dialogue system for exploring SAFETYNET and ENTROPY lore during missions
**When to Use**:
- Phone conversations with handler during missions
- Downtime dialogue during infiltrations
- Pre/post-mission briefings
- Optional character building moments
**Key Features**:
- Hub-based conversation pattern (return to menu after each topic)
- Influence tracking with multiple NPCs
- Progressive revelation (deeper topics unlock with higher influence)
- Works with different speakers (handler, tech support, director)
- Mission-agnostic design for reusability
**Influence Variables**:
- `handler_influence` (0-100) - Relationship with handler (Haxolottle)
- `tech_influence` (0-100) - Relationship with technical support (Dr. Chen)
- `director_influence` (0-100) - Relationship with command (Netherton)
- `fellow_agent_influence` (0-100) - Relationship with peer agents
**Topic Categories**:
#### ENTROPY Topics
- **Origins** - Where ENTROPY came from, emergence theories
- **Philosophy** - Accelerationism, nihilism, ideological diversity
- **Cells** - Digital Vanguard, Critical Mass, Ghost Protocol, Ransomware Inc.
- **Tactics** - Technical methods and operational patterns
- **Coordination** - How decentralized cells work together (mystery)
#### SAFETYNET Topics
- **Mission** - Organizational purpose and legal gray areas
- **Methods** - Technical capabilities and operational approaches
- **Shadow War** - Ongoing invisible conflict with ENTROPY
- **Field Operations** - Practical advice for missions
- **CYBER-PHYSICAL** - Specialized work integrating digital and physical security
#### Deep Lore (Unlocks with High Influence)
- **Handler Backstory** (30+ influence) - Haxolottle's past and Operation Regenerate
- **Berlin Crisis** (50+ influence) - Director Netherton's difficult decision
- **Moral Complexity** - Legal authority, oversight, ethical considerations
- **Cutting-Edge Research** (30+ tech influence) - Experimental capabilities
**Entry Points**:
- `start_handler_lore` - Conversation with handler (Haxolottle)
- `start_tech_support_lore` - Conversation with tech support (Dr. Chen)
- `start_director_lore` - Conversation with director (Netherton)
**Integration Examples**:
```ink
// During mission downtime
=== mission_checkpoint ===
You reach a safe moment. Your phone buzzes.
+ [Answer handler's call]
-> start_handler_lore
+ [Continue mission]
-> next_objective
```
```ink
// Phone conversation trigger
=== phone_ring ===
#speaker:agent_haxolottle
Haxolottle: Got a moment? Want to discuss anything?
-> lore_hub_handler
```
**Character-Specific Styles**:
**Handler (Haxolottle)**:
- Warm, supportive, mentoring tone
- Axolotl metaphors about adaptation and regeneration
- Shares field experience and practical wisdom
- Most comprehensive lore coverage
- Balance of professional and personal
**Tech Support (Dr. Chen)**:
- Rapid-fire technical explanations
- Focuses on methods, capabilities, research
- Enthusiastic about cutting-edge topics
- Less emotional depth, more technical detail
**Director (Netherton)**:
- Formal, structured, handbook references
- Focus on mandate, protocols, rules of engagement
- Rare moments of vulnerability about organization's future
- Shorter conversations, more authoritative
---
## Design Principles
### 1. Influence-Based Progression
Both scripts use influence tracking to:
- Gate deeper/more personal information behind relationship building
- Reward player curiosity and engagement
- Create replayability through gradual revelation
- Make relationship development feel earned
**Influence Gains**:
- Basic questions: +3 to +5
- Thoughtful questions: +8 to +10
- Personal questions: +10 to +15
- Deep vulnerability moments: +15 to +25
**Influence Gates**:
- 0-20: Basic information available
- 20-40: Moderate depth unlocked
- 40-60: Personal stories and context
- 60+: Deep lore and vulnerable moments
### 2. Hub Pattern
Lore exploration uses hub-and-spoke conversation structure:
- Return to topic menu after each conversation
- Topics marked as discussed to prevent repetition
- New topics unlock based on prerequisites
- Easy to add new topics without breaking existing structure
### 3. Character Voice Consistency
Each character maintains distinct voice:
**Director Netherton**:
- Formal speech, handbook references
- "Per section X.Y..." phrasing
- Rare approval is meaningful
- Protective through procedural language
**Agent Haxolottle**:
- Casual but professional
- Axolotl metaphors (not overused)
- Supportive and warm
- Field experience perspective
**Dr. Chen**:
- Rapid technical explanations
- Enthusiastic about research
- Less filtered, more direct
- Energy and momentum
### 4. Player Agency
Multiple choices that matter:
- Affect relationships (influence changes)
- Reflect character approach
- Unlock different dialogue branches
- Create roleplay opportunities
### 5. Lore Integration
Information designed to:
- Enhance understanding of game world
- Provide context for missions
- Build investment in conflict
- Answer player questions naturally
---
## Variables Reference
### Relationship Variables
```ink
VAR netherton_respect = 50 // Director's assessment
VAR haxolottle_trust = 50 // Handler's confidence
VAR handler_influence = 0 // Cumulative handler relationship
VAR tech_influence = 0 // Cumulative tech support relationship
VAR director_influence = 0 // Cumulative director relationship
```
### Character State Variables
```ink
VAR player_attitude = "" // Player's roleplay style
VAR specialization_interest = "" // Career direction
VAR conversation_depth = 0 // How much player has explored
```
### Topic Tracking (Boolean Flags)
```ink
VAR discussed_entropy_origins = false
VAR discussed_entropy_philosophy = false
VAR discussed_entropy_cells = false
VAR discussed_safetynet_mission = false
VAR discussed_shadow_war = false
VAR discussed_field_ops = false
VAR discussed_cyber_physical = false
VAR discussed_moral_complexity = false
```
### Deep Lore Unlocks
```ink
VAR knows_berlin_crisis = false // Director's difficult past
VAR knows_handler_backstory = false // Haxolottle's history
VAR knows_entropy_masterminds = false // High-level ENTROPY intel
VAR knows_0x42_legend = false // Mysterious agent stories
```
---
## Usage Guidelines
### For Scenario Designers
**Integrating the Intro Cutscene**:
1. Place at campaign start or major transition point
2. Ensure external variables (`player_name`, `previous_missions_completed`) are set
3. Carry forward influence variables to future scenarios
4. Reference player's `player_attitude` in mission briefings
5. Use `specialization_interest` to tailor challenge types
**Integrating Lore Exploration**:
1. Add phone conversation triggers during missions
2. Use as optional dialogue during downtime
3. Include in pre/post-mission briefings
4. Gate advanced topics behind influence requirements
5. Reference discussed topics in later dialogue
**Maintaining Continuity**:
- Persist influence variables across scenarios
- Reference previous discussions when appropriate
- Build on established character relationships
- Acknowledge player's growing expertise
### For Writers
**Adding New Topics**:
1. Create topic flag: `VAR discussed_new_topic = false`
2. Add hub menu option with condition
3. Write topic content with influence gains
4. Link back to hub: `-> lore_hub_handler`
5. Consider prerequisites for topic visibility
**Character Voice Checklist**:
- [ ] Netherton uses formal language and handbook references
- [ ] Haxolottle includes supportive mentoring and occasional axolotl metaphor
- [ ] Dr. Chen speaks rapidly and technically
- [ ] Dialogue reflects character's background and expertise
- [ ] Influence gains match conversation depth
**Quality Standards**:
- Each topic should be 3-5 exchanges (not too long)
- Include at least one meaningful choice per major topic
- Award influence for good questions and engagement
- Maintain consistent tone across related topics
- Provide both information and character development
---
## Testing Checklist
Before integration:
- [ ] All knots are reachable
- [ ] No orphaned diverts (-> pointing to non-existent knots)
- [ ] Variables are consistently named
- [ ] Influence gains are balanced (not too easy/hard to max)
- [ ] Topic flags prevent repetition
- [ ] Hub pattern returns correctly
- [ ] Exit conversation works properly
- [ ] Character voices are distinct and consistent
- [ ] External variables are properly marked EXTERNAL
- [ ] Ink compiles without errors in Inky editor
---
## Future Expansion Ideas
### Additional Topics
- Specific ENTROPY cell deep dives (Zero Day Syndicate, AI Singularity)
- SAFETYNET training and recruitment process
- Historical operations and case studies
- Technology and equipment discussions
- Personal stories from NPCs
- Moral dilemmas and ethical discussions
### Additional Characters
- Dr. Chen dedicated dialogue tree
- Agent 0x42 mysterious encounters
- Fellow agent peer conversations
- ENTROPY defector interviews
- Command council members
### Advanced Features
- Dynamic topic recommendations based on current mission
- Relationship status summaries
- Character mood/stress tracking affecting responses
- Time-gated topics (only available at certain points)
- Mission-specific lore variants
---
## Credits
**Writing Style Influenced By**:
- Break Escape Universe Bible (story_design/universe_bible/)
- Character profiles (Director Netherton, Agent 0x99, Agent 0x00)
- Ink Scripting Guide (story_design/story_dev_prompts/07_ink_scripting.md)
- Lore System Design (story_design/universe_bible/08_lore_system/)
**Ink Resources**:
- [Ink Documentation](https://github.com/inkle/ink/blob/master/Documentation/WritingWithInk.md)
- [Inkle Studios](https://www.inklestudios.com/)
---
## Integration Support
For questions about integrating these scripts:
1. Check `docs/INK_INTEGRATION.md` for technical integration
2. Review `story_design/story_dev_prompts/07_ink_scripting.md` for Ink best practices
3. See `story_design/story_dev_prompts/FEATURES_REFERENCE.md` for available game features
## Notes for Developers
**Event Hooks** (for future implementation):
- `#start_gameplay` - Transition from cutscene to game
- `#exit_conversation` - Close dialogue interface
- `#speaker:character_id` - Set active speaker for dialogue UI
**Save System Considerations**:
- All influence variables should persist across sessions
- Topic flags should persist to prevent repetition
- Consider separate save slots for influence vs. mission progress
**Performance**:
- Hub pattern is efficient for branching conversations
- Boolean flags prevent unnecessary re-computation
- Influence calculations are simple arithmetic
---
*Last Updated: 2025-11-18*
*Version: 1.0*
*Status: Ready for Integration*

649
story_design/ink/agent_0x00_cyber_division_intro.ink Normal file
View File

@@ -0,0 +1,649 @@
// ===========================================
// AGENT 0x00 - CYBER-PHYSICAL DIVISION INTRODUCTION
// Break Escape Universe
// ===========================================
// A cutscene introducing Agent 0x00 to their new assignment
// in SAFETYNET's CYBER-PHYSICAL division.
// ===========================================
// Relationship and choice tracking variables
VAR netherton_respect = 50 // Director Netherton's assessment (0-100)
VAR haxolottle_trust = 50 // Handler's confidence in agent (0-100)
VAR player_attitude = "" // eager, cautious, confident, analytical
VAR specialization_interest = "" // cyber, physical, hybrid
VAR knows_cyber_division = false // Has player asked about the division?
VAR knows_handler_role = false // Has player asked about handlers?
VAR professional_impression = true // Starting with good impression
// External variables (could be set by game)
EXTERNAL player_name
EXTERNAL previous_missions_completed
// ===========================================
// OPENING: SAFETYNET HEADQUARTERS
// ===========================================
=== start ===
[Location: SAFETYNET Headquarters, Director's Office]
[Time: 0900 hours]
#speaker:narration
The elevator doors open with a soft chime. You step into the corridor of SAFETYNET's executive level—a place you've only heard about in whispers. Sleek, minimalist, and impossibly secure.
The walls are lined with framed commendations and photos of operations you'll probably never be cleared to know about. Each door bears only a number, no names.
A subtle display guides you: "Director Netherton - Office 7A - Proceed."
Your phone buzzed exactly 47 minutes ago with a single message: "Report to HQ. Director's office. 0900 sharp."
No explanation. No context. Just the summons.
* [Walk confidently to the office]
~ player_attitude = "confident"
~ netherton_respect += 5
You've been called here for a reason. Whatever it is, you're ready.
-> directors_office
* [Approach cautiously]
~ player_attitude = "cautious"
You take a moment to steady yourself. Deep breath. This could be anything—commendation, reprimand, or something else entirely.
-> directors_office
* [Review what you know]
~ player_attitude = "analytical"
~ netherton_respect += 3
As you walk, you mentally catalog the possibilities. Your recent operations were successful. No major rule violations. Performance metrics solid. This is probably...
-> directors_office
// ===========================================
// DIRECTOR NETHERTON'S OFFICE
// ===========================================
=== directors_office ===
#speaker:narration
You reach Office 7A. The door is already open.
Director Magnus Netherton sits behind an immaculate desk, reviewing something on a tablet. He's exactly as described—impeccably dressed in a charcoal suit, gray at the temples, and radiating the kind of authority that comes from two decades of making life-or-death decisions.
Without looking up:
#speaker:director_netherton
Agent {player_name}. You're three minutes early. Acceptable.
He gestures to a chair.
#speaker:director_netherton
Please, sit.
* [Sit immediately]
You take the offered seat, maintaining professional posture.
-> first_briefing
* [Ask why you've been summoned]
~ netherton_respect -= 5
~ player_attitude = "eager"
You: Director, may I ask why I've been called in?
-> premature_question
* [Wait for him to continue]
~ netherton_respect += 5
~ player_attitude = "cautious"
You sit down silently, waiting for the Director to speak first. Patience is a virtue in SAFETYNET.
-> first_briefing
=== premature_question ===
#speaker:director_netherton
Netherton finally looks up, his expression unreadable.
#speaker:director_netherton
You'll find out momentarily, Agent. Patience is a virtue outlined in handbook section 3.4—though I suspect you already know that.
He returns his attention to the tablet for exactly five more seconds, then sets it down.
-> first_briefing
// ===========================================
// THE BRIEFING - CYBER-PHYSICAL DIVISION
// ===========================================
=== first_briefing ===
#speaker:director_netherton
Your performance over the past {previous_missions_completed > 0: {previous_missions_completed} operations | several months} has been noted.
{player_attitude == "confident":
Netherton: You carry yourself with confidence. Good. You'll need that.
}
{player_attitude == "cautious":
Netherton: You're careful. Methodical. These are valuable traits.
}
{player_attitude == "analytical":
Netherton: Your analytical approach to challenges has not gone unnoticed.
}
#speaker:director_netherton
You've proven yourself capable in {previous_missions_completed > 0: fieldwork | your previous assignments}. However, SAFETYNET has a more... specialized need for your skills.
He taps the tablet, and a holographic display materializes above his desk—organizational charts, mission statistics, threat assessments.
#speaker:director_netherton
The CYBER-PHYSICAL division. Our operatives who engage with threats that exist at the intersection of digital and physical security.
The display shifts to show images: server rooms, corporate facilities, critical infrastructure, research labs.
#speaker:director_netherton
ENTROPY doesn't simply hack systems from a distance, Agent. They infiltrate facilities. They compromise supply chains. They plant hardware backdoors. They manipulate both silicon and society.
* [Express eagerness to join]
~ player_attitude = "eager"
~ haxolottle_trust += 5
You: I'm ready for this, Director. When do I start?
-> eager_response
* [Ask about the division's scope]
~ player_attitude = "analytical"
~ netherton_respect += 5
~ knows_cyber_division = true
You: What exactly does the CYBER-PHYSICAL division handle that other divisions don't?
-> division_details
* [Ask why you were selected]
~ player_attitude = "cautious"
You: Why me, sir? There are more experienced agents.
-> why_selected
=== eager_response ===
#speaker:director_netherton
Netherton's expression doesn't change, but there's something that might be approval in his eyes.
#speaker:director_netherton
Enthusiasm is noted, Agent. However, there are protocols. Per handbook section 12.3, new division assignments require a comprehensive briefing and handler assignment.
-> division_details
=== division_details ===
#speaker:director_netherton
The CYBER-PHYSICAL division handles operations requiring both cyber security expertise and physical infiltration capability.
He highlights several case files on the display:
#speaker:director_netherton
- Facility infiltration to access air-gapped systems
- Physical implantation of monitoring devices
- On-site network penetration and data exfiltration
- Supply chain interdiction
- Hardware security assessments of critical infrastructure
{not knows_cyber_division:
~ knows_cyber_division = true
}
#speaker:director_netherton
Unlike pure cyber operations conducted remotely, or pure physical security assessments, CYBER-PHYSICAL operatives must excel at both. The margin for error is... minimal.
-> handler_introduction_setup
=== why_selected ===
#speaker:director_netherton
A valid question.
He pulls up what appears to be your personnel file.
#speaker:director_netherton
Your technical proficiency is well-documented. Your adaptability in the field has been demonstrated repeatedly. And perhaps most importantly...
He looks directly at you.
#speaker:director_netherton
You complete missions while adhering to operational protocols. A rarer combination than one might expect.
{player_attitude == "cautious":
Netherton: Your cautious nature is an asset, not a liability. CYBER-PHYSICAL operations require agents who think before they act.
}
~ netherton_respect += 10
-> division_details
=== handler_introduction_setup ===
#speaker:director_netherton
Per standard operating procedure outlined in handbook section 14.7, you will be assigned a dedicated handler for CYBER-PHYSICAL operations.
He presses a button on his desk.
#speaker:director_netherton
Someone with extensive field experience who can provide real-time support during your operations.
The office door opens.
* [Turn to see who enters]
-> haxolottle_entrance
// ===========================================
// AGENT 0x99 "HAXOLOTTLE" INTRODUCTION
// ===========================================
=== haxolottle_entrance ===
#speaker:narration
A figure enters—relaxed posture, tech-casual attire, holding what appears to be a coffee mug with an unusual design. They look comfortable in a way that suggests years of experience.
#speaker:agent_haxolottle
Agent {player_name}, I presume?
They extend a hand for a handshake.
#speaker:agent_haxolottle
Agent 0x99. Callsign "Haxolottle." Yes, like the axolotl. Yes, I know it's unusual. And yes, there's a story behind it that I'll probably tell you over comms during a mission at exactly the wrong moment.
* [Shake hands professionally]
~ haxolottle_trust += 5
~ professional_impression = true
You shake hands firmly. Professional. Confident.
You: Pleased to meet you, Agent 0x99.
-> haxolottle_initial_banter
* [Shake hands warmly]
~ haxolottle_trust += 10
You shake hands with a genuine smile. This person seems... approachable. Different from the Director's intensity.
You: Call me {player_name}. Looking forward to working together.
-> haxolottle_initial_banter
* [Ask about the axolotl reference]
~ haxolottle_trust += 8
~ specialization_interest = "curious"
You shake hands, genuinely curious.
You: I have to ask—why "Haxolottle"?
-> axolotl_story_teaser
=== haxolottle_initial_banter ===
#speaker:agent_haxolottle
Haxolottle grins and glances at Director Netherton.
#speaker:agent_haxolottle
Still as warm and welcoming as ever, I see, Director.
#speaker:director_netherton
Netherton doesn't look up from his tablet.
#speaker:director_netherton
Agent 0x99, please maintain professional decorum per handbook section—
#speaker:agent_haxolottle
—Section 3.2.b, interpersonal conduct. I know, I know. Fifteen years and you're still citing the handbook at me.
Haxolottle turns back to you with a conspiratorial wink.
#speaker:agent_haxolottle
You'll get used to it. The Director's bark is worse than his bite. Actually, wait, that's not true. His bite is exactly as strict as his bark. But it comes from a good place.
-> handler_explanation
=== axolotl_story_teaser ===
#speaker:agent_haxolottle
Haxolottle's eyes light up.
#speaker:agent_haxolottle
Oh, you're going to fit in just fine. The short version: axolotls are masters of regeneration and adaptation. Lost a limb? Grow it back. Need to change your approach? Metamorphosis is an option.
#speaker:director_netherton
Director Netherton clears his throat.
#speaker:director_netherton
Agent 0x99, perhaps we could save the amphibian biology lecture for after the formal briefing.
#speaker:agent_haxolottle
Right, right. Professional decorum. Got it, Director.
Haxolottle turns back to you with a smile.
#speaker:agent_haxolottle
Long version later. For now, just know: in this job, the ability to regenerate from setbacks and adapt to changing circumstances is everything. Hence, Haxolottle.
-> handler_explanation
=== handler_explanation ===
#speaker:director_netherton
Director Netherton stands, hands clasped behind his back.
#speaker:director_netherton
Agent 0x99 will serve as your handler for CYBER-PHYSICAL operations. They will provide mission briefings, real-time support during operations, and post-mission debriefing.
#speaker:agent_haxolottle
Translation: I'm the voice in your ear when you're standing in a server room you're not supposed to be in, trying to bypass security you definitely shouldn't be bypassing, while maintaining a cover story that seemed way more convincing during planning.
~ haxolottle_trust += 5
#speaker:agent_haxolottle
I've been doing this for fifteen years. Spent eight in the field before transitioning to handler work. Whatever you run into out there, I've probably seen it—or something close enough to help.
* [Express confidence in the arrangement]
~ haxolottle_trust += 10
~ netherton_respect += 5
You: I appreciate the support. Looking forward to working with you both.
-> mission_philosophy_question
* [Ask about their field experience]
~ haxolottle_trust += 5
~ knows_handler_role = true
You: What kind of operations did you run in the field?
-> haxolottle_experience_brief
* [Ask what happens if you disagree during a mission]
~ player_attitude = "analytical"
~ netherton_respect += 8
You: What if we disagree about the best approach during an operation?
-> disagreement_protocol
=== haxolottle_experience_brief ===
#speaker:agent_haxolottle
Haxolottle leans against the Director's desk casually—earning a slight frown from Netherton, which they ignore.
#speaker:agent_haxolottle
Infiltrated controlled corporations. Ran counter-intelligence on ENTROPY cells. Did some work that's still classified and will probably stay that way until we're both retired.
#speaker:agent_haxolottle
The operation that earned me the callsign involved being pinned in a compromised position for three days, surviving through adaptation and creative problem-solving. Turned a blown mission into our biggest intelligence coup that year.
#speaker:agent_haxolottle
Point is: I know what you'll be dealing with. The fear. The adrenaline. The moment when everything goes sideways and you have to improvise. I've been there.
~ knows_handler_role = true
~ haxolottle_trust += 5
-> mission_philosophy_question
=== disagreement_protocol ===
#speaker:director_netherton
Netherton answers before Haxolottle can.
#speaker:director_netherton
An excellent question. Per handbook section 14.9, field agents have operational discretion when directly engaged. You are on-site. You have eyes on the situation. Your handler provides guidance, not commands.
#speaker:agent_haxolottle
What the Director's saying is: I'll give you my best assessment based on the big picture I can see. But you're the one in the room. If you've got a better read on the situation, I trust your judgment.
#speaker:agent_haxolottle
That said, if I'm telling you something's dangerous, there's probably a very good reason. We're partners in this.
~ netherton_respect += 10
~ haxolottle_trust += 10
-> mission_philosophy_question
=== mission_philosophy_question ===
#speaker:director_netherton
Director Netherton pulls up a new display—threat assessments, ENTROPY cell activities, ongoing operations.
#speaker:director_netherton
The CYBER-PHYSICAL division faces unique challenges. ENTROPY operates in the shadows between digital and physical security. They exploit the gaps where traditional defenses fail.
#speaker:agent_haxolottle
We're the ones who close those gaps. Sometimes with elegant technical solutions. Sometimes with a lockpick and a convincing cover story.
#speaker:director_netherton
Your approach to these operations will shape your effectiveness. I'm interested in understanding your operational philosophy, Agent {player_name}.
* [Prioritize thoroughness and caution]
~ player_attitude = "cautious"
~ specialization_interest = "analytical"
~ netherton_respect += 10
You: I believe in careful planning, thorough reconnaissance, and minimizing risk. Better to take the time to do it right.
-> cautious_philosophy_response
* [Prioritize speed and decisiveness]
~ player_attitude = "confident"
~ specialization_interest = "physical"
~ haxolottle_trust += 10
You: In my experience, hesitation is dangerous. Gather intel, make a plan, execute with confidence. Adapt as needed.
-> confident_philosophy_response
* [Prioritize adaptability and flexibility]
~ player_attitude = "analytical"
~ specialization_interest = "hybrid"
~ netherton_respect += 8
~ haxolottle_trust += 8
You: Every situation is different. I believe in having multiple approaches ready and adapting based on what I encounter.
-> adaptive_philosophy_response
=== cautious_philosophy_response ===
#speaker:director_netherton
Netherton nods approvingly.
#speaker:director_netherton
A methodical approach. This aligns well with handbook guidance on operational planning section 7.3. Measured execution reduces unnecessary exposure and maintains operational security.
#speaker:agent_haxolottle
And when things inevitably go sideways—because they always do—that thorough planning gives you a foundation to build your improvisation on. Like an axolotl regenerating a limb: you need the core structure first.
There's that axolotl reference again.
-> specialization_discussion
=== confident_philosophy_response ===
#speaker:agent_haxolottle
Haxolottle grins.
#speaker:agent_haxolottle
I like it. Decisiveness is underrated. Analysis paralysis has killed more operations than bold action, in my experience.
#speaker:director_netherton
Netherton looks less enthusiastic but not disapproving.
#speaker:director_netherton
Confidence is valuable, Agent, provided it's paired with sound judgment. Per handbook section 8.5, field discretion requires balancing speed with caution.
#speaker:agent_haxolottle
Translation: be bold, but don't be reckless. We're working on it together. If your instincts say "go," and I don't have a compelling reason to stop you, we go.
-> specialization_discussion
=== adaptive_philosophy_response ===
#speaker:agent_haxolottle
Haxolottle actually looks impressed.
#speaker:agent_haxolottle
Now that's the mindset. Adaptability. Flexibility. Like I said—axolotl thinking. The ability to regenerate your approach when the first one doesn't work.
#speaker:director_netherton
Director Netherton also appears satisfied.
#speaker:director_netherton
A balanced perspective. The handbook acknowledges in section 14.2 that field conditions are inherently unpredictable. Agents who can adjust methodology while maintaining mission focus demonstrate advanced operational maturity.
#speaker:agent_haxolottle
In other words: you get it. Perfect. We're going to work well together.
-> specialization_discussion
=== specialization_discussion ===
#speaker:director_netherton
Netherton dismisses the holographic display.
#speaker:director_netherton
Agent 0x99 will handle your detailed orientation over the coming week. You'll receive technical briefings, facility access, and equipment assignments.
He looks directly at you.
#speaker:director_netherton
The CYBER-PHYSICAL division handles the operations that are too complex for single-discipline approaches. You will encounter challenges that test both your technical capabilities and your field craft.
#speaker:agent_haxolottle
What the Director's not saying is: you're going to be challenged. But you're also going to grow faster than you ever thought possible. We don't assign people to CYBER-PHYSICAL unless we believe they can handle it.
#speaker:director_netherton
Quite. Do you have any questions before you begin orientation?
* [Ask about first assignment]
You: When will I receive my first CYBER-PHYSICAL operation?
-> first_assignment_timing
* [Ask about training and preparation]
You: What kind of preparation should I focus on?
-> training_guidance
* [Express readiness to begin]
You: No questions, Director. I'm ready to start.
-> ready_to_begin
=== first_assignment_timing ===
#speaker:director_netherton
Netherton glances at his tablet.
#speaker:director_netherton
Per protocol, new division assignments require a one-week orientation period. However, given current operational tempo and ENTROPY activity levels...
He looks at Haxolottle.
#speaker:agent_haxolottle
I've got a scenario developing that's perfect for a shakedown operation. Corporate facility, suspected ENTROPY infiltration, moderate complexity. Could be ready to brief in 72 hours.
#speaker:director_netherton
Acceptable. Agent {player_name}, complete your orientation, review the required materials, and report to Agent 0x99 on Thursday at 0800 hours.
~ netherton_respect += 5
-> closing_briefing
=== training_guidance ===
#speaker:agent_haxolottle
Haxolottle answers first.
#speaker:agent_haxolottle
Honestly? The best preparation is reviewing what you already know. You've got the fundamentals. Now it's about integrating them.
{specialization_interest == "cyber":
Haxolottle: Your technical skills are solid. Brush up on physical infiltration basics—lockpicking, cover stories, reading floor plans. The cyber part, you've got.
}
{specialization_interest == "physical":
Haxolottle: Your field craft is good. Make sure your technical knowledge is current—latest exploit frameworks, network architecture, common security systems. The physical part, you've got.
}
{specialization_interest == "hybrid":
Haxolottle: You've got a good foundation in both areas. Focus on integration—how to use physical access to enable cyber operations, and vice versa. That's where CYBER-PHYSICAL work gets interesting.
}
#speaker:director_netherton
Additionally, review handbook sections 12 through 18. CYBER-PHYSICAL operations have specific protocols regarding evidence handling, data exfiltration, and operational security.
~ netherton_respect += 8
~ haxolottle_trust += 5
-> closing_briefing
=== ready_to_begin ===
#speaker:director_netherton
Netherton almost smiles. Almost.
#speaker:director_netherton
Confidence without arrogance. Acceptable. Agent 0x99, proceed with orientation protocol per handbook section 12.5.
#speaker:agent_haxolottle
Copy that, Director.
Haxolottle gestures toward the door.
#speaker:agent_haxolottle
Come on, Agent {player_name}. Let me show you your new office space, introduce you to the team, and explain why the coffee on level 3 is better than level 5 despite what anyone tells you.
~ haxolottle_trust += 10
~ professional_impression = true
-> closing_briefing
=== closing_briefing ===
#speaker:director_netherton
Director Netherton stands, signaling the meeting's conclusion.
#speaker:director_netherton
Agent {player_name}, welcome to the CYBER-PHYSICAL division. Your performance will be evaluated continuously. I expect excellence.
{netherton_respect >= 60:
Netherton: Based on your record and this conversation, I believe you're capable of meeting that standard.
}
{netherton_respect < 60:
Netherton: I trust you'll rise to the challenge.
}
He extends his hand for a formal handshake.
* [Shake hands firmly]
You shake the Director's hand. His grip is firm, measured. Professional.
-> final_moment
=== final_moment ===
#speaker:director_netherton
Per handbook section 2.7, maintain operational security regarding your division assignment. Dismissed.
As you turn to leave with Haxolottle, the Director speaks once more:
#speaker:director_netherton
{netherton_respect >= 70: Agent {player_name}... good luck. | Agent... don't disappoint me.}
The door closes behind you.
#speaker:agent_haxolottle
Haxolottle grins as you walk down the corridor.
#speaker:agent_haxolottle
So! Welcome to CYBER-PHYSICAL. You survived a Netherton briefing without him citing the handbook more than... okay, he cited it a lot. But he likes you—I can tell.
#speaker:agent_haxolottle
First rule of working with me: I will make axolotl metaphors. They're genuinely helpful about 60% of the time. Second rule: when I say "get out now," trust me and get out.
#speaker:agent_haxolottle
Everything else we'll figure out together. Ready to see your new workspace?
* [Absolutely]
~ haxolottle_trust += 5
You: Lead the way.
-> orientation_begins
* [Ask about the team]
You: You mentioned introducing me to the team?
-> team_tease
=== orientation_begins ===
#speaker:agent_haxolottle
Haxolottle leads you toward the elevators.
#speaker:agent_haxolottle
One more thing—and this is important. We're partners in this work. I've got experience and perspective. You've got skills and fresh eyes. Best operations happen when we trust each other.
They press the elevator button.
#speaker:agent_haxolottle
So if you've got questions, ask. If something doesn't feel right, speak up. And if I tell you about axolotl regeneration during a critical moment... well, it'll probably be relevant. Probably.
The elevator arrives.
#speaker:agent_haxolottle
Welcome to CYBER-PHYSICAL, Agent {player_name}. This is going to be interesting.
-> END
=== team_tease ===
#speaker:agent_haxolottle
Oh, you'll like them. We've got Dr. Chen in technical support—brilliant, talks incredibly fast, lives on energy drinks. There's a betting pool on whether they actually sleep.
#speaker:agent_haxolottle
Then there's Agent 0x42—you might not meet them directly. They're... mysterious. Legendary field operative. Appears cryptically, provides crucial information, vanishes. Very dramatic.
#speaker:agent_haxolottle
And of course, there's the rest of the CYBER-PHYSICAL agents. Good people. We look out for each other out there.
They press the elevator button.
#speaker:agent_haxolottle
You're joining a solid team, Agent. We've got your back.
-> orientation_begins
// ===========================================
// END OF INTRO CUTSCENE
// ===========================================
// Variables set:
// - netherton_respect (relationship with Director)
// - haxolottle_trust (relationship with handler)
// - player_attitude (roleplay style)
// - specialization_interest (career direction hints)
// - knows_cyber_division (lore flag)
// - knows_handler_role (lore flag)
// ===========================================

891
story_design/ink/lore_exploration_hub.ink Normal file
View File

@@ -0,0 +1,891 @@
// ===========================================
// LORE EXPLORATION HUB
// Break Escape Universe
// ===========================================
// Reusable dialogue system for exploring SAFETYNET and ENTROPY lore
// Can be triggered during missions or between operations
// Tracks influence with NPCs and unlocks deeper information
// ===========================================
// Influence tracking (different NPCs can use different influence pools)
VAR handler_influence = 0 // Relationship with handler (like Haxolottle)
VAR tech_influence = 0 // Relationship with technical support (like Dr. Chen)
VAR director_influence = 0 // Relationship with command (like Netherton)
VAR fellow_agent_influence = 0 // Relationship with peer agents
// Topic tracking - what has the player already discussed?
VAR discussed_entropy_origins = false
VAR discussed_entropy_philosophy = false
VAR discussed_entropy_cells = false
VAR discussed_entropy_tactics = false
VAR discussed_safetynet_mission = false
VAR discussed_safetynet_methods = false
VAR discussed_shadow_war = false
VAR discussed_field_ops = false
VAR discussed_cyber_physical = false
VAR discussed_moral_complexity = false
// Deep lore unlocks (requires high influence)
VAR knows_berlin_crisis = false
VAR knows_handler_backstory = false
VAR knows_entropy_masterminds = false
VAR knows_0x42_legend = false
// Conversation state
VAR current_speaker = "handler" // handler, tech_support, director, fellow_agent
VAR conversation_depth = 0 // Tracks how much player has explored
VAR player_curiosity_noted = false
// External variables
EXTERNAL player_name
EXTERNAL mission_active
// ===========================================
// ENTRY POINT - HANDLER CONVERSATION
// ===========================================
=== start_handler_lore ===
~ current_speaker = "handler"
#speaker:agent_haxolottle
{mission_active:
Haxolottle: Got a quiet moment? Happy to answer questions while you're on downtime.
- else:
Haxolottle: What's on your mind, Agent {player_name}? Need some context about what we're up against?
}
-> lore_hub_handler
// ===========================================
// HANDLER LORE HUB (Haxolottle-style)
// ===========================================
=== lore_hub_handler ===
+ {not discussed_entropy_origins} [Ask about ENTROPY's origins]
-> entropy_origins_handler
+ {not discussed_entropy_philosophy} [Ask about ENTROPY's philosophy]
-> entropy_philosophy_handler
+ {not discussed_entropy_cells and discussed_entropy_origins} [Ask about specific ENTROPY cells]
-> entropy_cells_handler
+ {not discussed_safetynet_mission} [Ask about SAFETYNET's mission]
-> safetynet_mission_handler
+ {not discussed_shadow_war and discussed_safetynet_mission and discussed_entropy_origins} [Ask about the shadow war]
-> shadow_war_handler
+ {not discussed_field_ops} [Ask for field operation advice]
-> field_ops_advice_handler
+ {not discussed_cyber_physical and discussed_field_ops} [Ask about CYBER-PHYSICAL work specifically]
-> cyber_physical_handler
+ {handler_influence >= 30 and not knows_handler_backstory} [Ask about Haxolottle's past]
-> handler_backstory
+ {handler_influence >= 50 and not knows_berlin_crisis} [Ask about difficult operations]
-> berlin_crisis_story
+ [That's all for now]
-> end_handler_conversation
// ===========================================
// ENTROPY ORIGINS
// ===========================================
=== entropy_origins_handler ===
#speaker:agent_haxolottle
~ discussed_entropy_origins = true
~ handler_influence += 5
~ conversation_depth += 1
Haxolottle: Ah, the big question. Where did ENTROPY come from?
Haxolottle: Honestly? We're not entirely sure. Our best intelligence suggests they emerged in the early 2020s during the pandemic chaos. Digital transformation accelerated, security practices couldn't keep up, and someone—or multiple someones—saw an opportunity.
Haxolottle: At first, we thought we were tracking different threat actors. Then patterns emerged. Shared tactics. Coordinated timing. Resources moving between what we thought were independent groups.
Haxolottle: By 2025, it was clear: this was an organization. Decentralized, cell-based, but unified by something. Philosophy, funding, leadership—we're still piecing it together.
* [That's concerning]
~ handler_influence += 3
You: So we're fighting an enemy we don't fully understand?
-> entropy_origins_followup_concern
* [Ask about their goals]
~ conversation_depth += 1
You: What are they actually trying to achieve?
-> entropy_origins_followup_goals
* [Thank them for the information]
You: That helps contextualize things. Thank you.
-> lore_hub_handler
=== entropy_origins_followup_concern ===
#speaker:agent_haxolottle
Haxolottle nods seriously.
Haxolottle: Yes and no. We understand their methods—we see them in action every day. We understand their capabilities—they're formidable but not unlimited.
Haxolottle: What we don't fully grasp is the "why" behind the "what." And that uncertainty means we have to stay adaptable. Like an axolotl adjusting to different water conditions—we work with what we know and adapt as we learn more.
~ handler_influence += 5
-> lore_hub_handler
=== entropy_origins_followup_goals ===
#speaker:agent_haxolottle
Haxolottle leans back, considering.
Haxolottle: That's where it gets interesting. Different ENTROPY cells seem to have different goals. Some are clearly financial—ransomware, data theft, extortion. Others appear ideological—accelerationism, techno-anarchism, chaos for its own sake.
Haxolottle: Then there are the esoteric cells. The ones pursuing objectives we can barely comprehend. Reality manipulation. Entity summoning. Quantum consciousness alteration. That's the stuff that keeps me up at night.
Haxolottle: The unifying thread seems to be "entropy"—increasing chaos, destabilizing systems, accelerating societal breakdown. Whether that's means or end, we're not certain.
~ discussed_entropy_philosophy = true
~ handler_influence += 8
~ conversation_depth += 1
-> lore_hub_handler
// ===========================================
// ENTROPY PHILOSOPHY
// ===========================================
=== entropy_philosophy_handler ===
#speaker:agent_haxolottle
~ discussed_entropy_philosophy = true
~ handler_influence += 5
~ conversation_depth += 1
Haxolottle: ENTROPY's philosophy... it's not monolithic. Each cell interprets it differently.
Haxolottle: Some are true believers in accelerationism—tear down existing systems to build something new from the ashes. They genuinely think they're helping, in a twisted way.
Haxolottle: Others are nihilists. They want chaos for its own sake. No grand vision, just destabilization and disorder.
Haxolottle: And some are just using the philosophy as cover for criminal enterprise. The ideology gives them structure and recruitment, but they're in it for money and power.
* [Ask which type is most dangerous]
~ conversation_depth += 1
You: Which type poses the greatest threat?
-> philosophy_danger_assessment
* [Ask if any can be reasoned with]
~ handler_influence += 8
~ conversation_depth += 1
You: Can any of them be reasoned with? Turned?
-> philosophy_redemption_question
* [Move on]
-> lore_hub_handler
=== philosophy_danger_assessment ===
#speaker:agent_haxolottle
Haxolottle: The true believers, without question.
Haxolottle: Criminals can be caught, assets seized, organizations dismantled. Nihilists burn out eventually—chaos for its own sake is exhausting.
Haxolottle: But ideologues? They're patient. They're persistent. They'll sacrifice themselves for the cause. And they're often brilliant people who genuinely believe they're doing the right thing.
Haxolottle: That makes them harder to predict, harder to deter, and much more dangerous long-term.
~ handler_influence += 8
-> lore_hub_handler
=== philosophy_redemption_question ===
#speaker:agent_haxolottle
Haxolottle looks thoughtful.
Haxolottle: You're asking the right questions, Agent. That shows good judgment.
Haxolottle: Yes. Some can be reasoned with. We've had defectors—people who joined ENTROPY for idealistic reasons and realized the reality didn't match the rhetoric. People who were coerced or manipulated.
Haxolottle: Part of our job is recognizing the difference between committed operatives and unwitting participants. The handbook has entire sections on engagement protocols for potentially redeemable assets.
Haxolottle: Not everyone wearing an ENTROPY badge is beyond saving. Some are just... lost. And if we can offer a better path, we should.
~ handler_influence += 15
~ discussed_moral_complexity = true
-> lore_hub_handler
// ===========================================
// ENTROPY CELLS
// ===========================================
=== entropy_cells_handler ===
#speaker:agent_haxolottle
~ discussed_entropy_cells = true
~ handler_influence += 5
~ conversation_depth += 1
Haxolottle: We've identified about a dozen major ENTROPY cells, each with distinct specializations and methodologies.
Haxolottle: Let me give you the highlights of the ones you're most likely to encounter:
Haxolottle: **Digital Vanguard**—pure cyber operations. APT-level capabilities, zero-day exploitation, sophisticated malware. They're the technical elite.
Haxolottle: **Critical Mass**—infrastructure targeting. Power grids, water systems, transportation networks. They want maximum societal impact.
Haxolottle: **Ghost Protocol**—the surveillance experts. They gather intelligence, compile dossiers, and sell information. Knowledge is their weapon.
Haxolottle: **Ransomware Incorporated**—exactly what it sounds like. Criminal enterprise wrapped in ENTROPY ideology. Financially motivated but effective.
* [Ask about a specific cell]
-> specific_cell_details
* [Ask how cells coordinate]
~ conversation_depth += 1
You: How do these cells coordinate?
-> cell_coordination_explanation
* [That's enough for now]
-> lore_hub_handler
=== specific_cell_details ===
#speaker:agent_haxolottle
Haxolottle: Which one are you curious about?
+ [Digital Vanguard]
-> digital_vanguard_details
+ [Critical Mass]
-> critical_mass_details
+ [Ghost Protocol]
-> ghost_protocol_details
+ [Ransomware Incorporated]
-> ransomware_inc_details
+ [Actually, never mind]
-> lore_hub_handler
=== digital_vanguard_details ===
#speaker:agent_haxolottle
~ handler_influence += 3
Haxolottle: Digital Vanguard—the tech perfectionists of ENTROPY. They treat hacking like an art form.
Haxolottle: They specialize in advanced persistent threats, supply chain compromises, and zero-day exploitation. If there's a vulnerability no one's found yet, Digital Vanguard is probably looking for it.
Haxolottle: They recruit heavily from academic institutions and competitive hacking scenes. Lots of CTF champions who went to the dark side.
Haxolottle: Their operations tend to be surgical—highly targeted, meticulously planned, technically brilliant. When you encounter their work, you'll recognize the craftsmanship.
-> lore_hub_handler
=== critical_mass_details ===
#speaker:agent_haxolottle
~ handler_influence += 3
Haxolottle: Critical Mass—the infrastructure saboteurs. They're after the systems that keep society running.
Haxolottle: Power grids, water treatment, transportation networks, telecommunications. They target the foundations. Their stated goal is demonstrating how fragile our infrastructure really is.
Haxolottle: What makes them particularly dangerous is they combine cyber expertise with understanding of industrial control systems and physical infrastructure. CYBER-PHYSICAL threats, through and through.
Haxolottle: They've been linked to several near-miss incidents. We've stopped them more often than the public knows. But we don't catch everything.
-> lore_hub_handler
=== ghost_protocol_details ===
#speaker:agent_haxolottle
~ handler_influence += 3
Haxolottle: Ghost Protocol—the information brokers and surveillance specialists.
Haxolottle: They don't typically execute attacks directly. Instead, they gather intelligence, compile dossiers, and sell information to the highest bidder—often other ENTROPY cells.
Haxolottle: They're masters of OSINT, social engineering, and long-term surveillance operations. They know more about our operations than I'm comfortable with.
Haxolottle: Encountering Ghost Protocol is weird because they're often not hostile—they'll observe, document, and vanish. The danger comes later when someone else uses that intelligence against you.
-> lore_hub_handler
=== ransomware_inc_details ===
#speaker:agent_haxolottle
~ handler_influence += 3
Haxolottle: Ransomware Incorporated—the criminal enterprise wing of ENTROPY.
Haxolottle: They're straightforward in motivation: money. They deploy ransomware, steal data for extortion, and run business email compromise schemes at scale.
Haxolottle: What makes them ENTROPY rather than ordinary cybercrime is their infrastructure and support network. They operate like a legitimate business—HR, customer service, even help desks for victims who need decryption assistance.
Haxolottle: Don't underestimate them just because they're financially motivated. They're professional, well-resourced, and surprisingly effective.
-> lore_hub_handler
=== cell_coordination_explanation ===
#speaker:agent_haxolottle
~ handler_influence += 8
Haxolottle: Good question. The answer is: we're not entirely certain.
Haxolottle: Cells appear to operate independently most of the time. Autonomous operations, separate resources, minimal communication.
Haxolottle: But occasionally—maybe 10% of cases—we see coordination. Shared intelligence. Resource transfers. Synchronized operations across multiple cells.
Haxolottle: That suggests some kind of coordination mechanism or higher authority, but we haven't identified it. No central command that we can find. No obvious communication channels.
Haxolottle: It's one of the biggest intelligence gaps we have. How do decentralized cells occasionally act in concert? Still working on that one.
-> lore_hub_handler
// ===========================================
// SAFETYNET MISSION
// ===========================================
=== safetynet_mission_handler ===
#speaker:agent_haxolottle
~ discussed_safetynet_mission = true
~ handler_influence += 5
~ conversation_depth += 1
Haxolottle: SAFETYNET's mission? Officially, we're the Security and Field-Engagement Technology Yielding National Emergency Taskforce.
Haxolottle: *grins* Unofficially, we're the people who stop ENTROPY from burning down digital civilization.
Haxolottle: We operate in a legal gray area—offensive security operations that most governments won't publicly acknowledge. We infiltrate, we gather intelligence, we neutralize threats before they materialize.
Haxolottle: The philosophy is "best defense is a preemptive offense." Don't wait for ENTROPY to attack. Find them first. Understand their operations. Dismantle them before they strike.
* [Ask about legal authority]
~ conversation_depth += 1
~ player_curiosity_noted = true
You: What's our actual legal authority for these operations?
-> legal_authority_question
* [Ask about oversight]
~ conversation_depth += 1
~ handler_influence += 5
You: Who oversees SAFETYNET? Who do we answer to?
-> oversight_question
* [Move on]
-> lore_hub_handler
=== legal_authority_question ===
#speaker:agent_haxolottle
Haxolottle: Complicated question. Complicated answer.
Haxolottle: We operate under classified executive orders and emergency powers acts. Technically legal, practically untested in court, definitely not something the public knows about.
Haxolottle: When we infiltrate a facility under false pretenses, we're relying on national security exemptions and carefully worded authorizations that would make privacy advocates's heads explode.
Haxolottle: The cover story—you're a security consultant, you're a contractor, you're running authorized penetration tests—that's partly about operational security and partly about legal deniability.
Haxolottle: If an operation goes wrong, SAFETYNET doesn't officially exist. You're a rogue actor. It's not fair, but it's how the system works.
~ handler_influence += 10
~ discussed_moral_complexity = true
-> lore_hub_handler
=== oversight_question ===
#speaker:agent_haxolottle
Haxolottle: Officially? Select committee members in certain governments. People with security clearances so high they probably don't exist on paper.
Haxolottle: Practically? We're overseen by SAFETYNET Command Council—people like Director Netherton. They report to... someone. I'm not cleared to know the full chain of command, and honestly, I'm okay with that.
Haxolottle: What matters is: we have rules of engagement. We have ethical guidelines. The handbook isn't just bureaucratic nonsense—it's our attempt to do this work responsibly.
Haxolottle: We're given enormous power and minimal oversight. That makes our internal ethics and judgment critically important. It's why they're so careful about recruitment.
~ handler_influence += 12
~ discussed_moral_complexity = true
-> lore_hub_handler
// ===========================================
// SHADOW WAR
// ===========================================
=== shadow_war_handler ===
#speaker:agent_haxolottle
~ discussed_shadow_war = true
~ handler_influence += 8
~ conversation_depth += 1
Haxolottle: The shadow war. That's what we call it—the ongoing conflict between SAFETYNET and ENTROPY that the public never sees.
Haxolottle: Every day, ENTROPY operatives are planning attacks, infiltrating systems, recruiting new members. And every day, we're working to stop them.
Haxolottle: Most people will never know how many disasters we've prevented. Power grids that almost went down. Data breaches that almost happened. Infrastructure attacks we intercepted.
Haxolottle: And ENTROPY doesn't know about most of our successes—that's by design. If they knew how often we've infiltrated them, they'd change their security. Better to stay invisible.
Haxolottle: It's exhausting, honestly. A war where victories aren't celebrated and defeats are catastrophic. Where we can't tell anyone what we do or why it matters.
* [Express appreciation for the work]
~ handler_influence += 10
You: That sounds incredibly difficult. Thank you for what you do—what we all do.
-> shadow_war_appreciation
* [Ask about the toll it takes]
~ handler_influence += 12
~ conversation_depth += 1
You: How do you handle that? The invisibility, the pressure?
-> shadow_war_psychological
* [Move on]
-> lore_hub_handler
=== shadow_war_appreciation ===
#speaker:agent_haxolottle
Haxolottle smiles, genuinely touched.
Haxolottle: Thank you, Agent. That means more than you might think.
Haxolottle: We're in this together now. Every operation you run, every threat you neutralize—you're part of this shadow war. And you're making a difference, even if the world never knows.
~ handler_influence += 10
-> lore_hub_handler
=== shadow_war_psychological ===
#speaker:agent_haxolottle
Haxolottle takes a moment before responding.
Haxolottle: Honestly? It's hard. Some days I wonder if we're making any difference. We stop one cell, two more spring up. We close one vulnerability, ENTROPY finds three others.
Haxolottle: What keeps me going is the people. My agents. Colleagues like you. Knowing we're fighting for something that matters, even in the shadows.
Haxolottle: And regeneration—like the axolotl. When the work breaks you down, you find ways to rebuild. Take time to recover. Support each other. Remember why we started.
Haxolottle: You'll have hard days too, Agent. When that happens, remember you're not alone. We've all been there. We'll help you through it.
~ handler_influence += 15
~ knows_handler_backstory = true
-> lore_hub_handler
// ===========================================
// FIELD OPERATIONS ADVICE
// ===========================================
=== field_ops_advice_handler ===
#speaker:agent_haxolottle
~ discussed_field_ops = true
~ handler_influence += 5
~ conversation_depth += 1
Haxolottle: Field operations advice? I've got fifteen years of hard-earned lessons. Where do I start?
Haxolottle: **First**: Trust your training, but don't be a slave to it. Plans fall apart. Improvisation is part of the job. Like an axolotl adapting to new environments.
Haxolottle: **Second**: Maintain your cover story. You're not "undercover"—you ARE the cover. Believe it yourself. Act like you belong, and people will believe you belong.
Haxolottle: **Third**: OPSEC is everything. One mistake—using your real name, accessing personal accounts, breaking character—can blow the whole operation.
Haxolottle: **Fourth**: When in doubt, slow down. Rushing causes mistakes. Better to take an extra hour than to trigger an alarm.
* [Ask about handling complications]
~ conversation_depth += 1
You: What about when things go wrong?
-> complications_advice
* [Ask about fear management]
~ conversation_depth += 1
~ handler_influence += 8
You: How do you handle fear in the field?
-> fear_management
* [Thank them for the advice]
-> lore_hub_handler
=== complications_advice ===
#speaker:agent_haxolottle
~ handler_influence += 8
Haxolottle: When things go wrong—and they will—focus on what you can control.
Haxolottle: Unexpected security patrol? You control your reaction. Maintain cover, adjust route, stay calm.
Haxolottle: System you're trying to access is different than intel suggested? You control your approach. Reassess, find alternative, or call for support.
Haxolottle: Mission parameters change mid-operation? You control your decision-making. Communicate with me, evaluate options, make the call.
Haxolottle: The agents who survive and succeed aren't the ones who never encounter problems. They're the ones who handle problems effectively.
Haxolottle: Regeneration. Adaptation. Like—
You: Let me guess. Like an axolotl?
Haxolottle: *laughs* You're catching on.
~ handler_influence += 10
-> lore_hub_handler
=== fear_management ===
#speaker:agent_haxolottle
~ handler_influence += 12
Haxolottle becomes more serious.
Haxolottle: Fear is normal. Healthy, even. It keeps you sharp.
Haxolottle: The trick isn't eliminating fear—it's functioning despite it. Feel the fear, acknowledge it, then put it aside and do the work.
Haxolottle: Breathing helps. Tactical breathing—four counts in, hold four, four counts out, hold four. Resets your nervous system.
Haxolottle: And remember: you're not alone. I'm on comms. Support team is monitoring. You have backup plans and extraction protocols. You're prepared for this.
Haxolottle: I've been exactly where you'll be—heart pounding, hands shaking, wondering if you're going to get caught. I got through it. You will too.
~ handler_influence += 15
-> lore_hub_handler
// ===========================================
// CYBER-PHYSICAL WORK
// ===========================================
=== cyber_physical_handler ===
#speaker:agent_haxolottle
~ discussed_cyber_physical = true
~ handler_influence += 8
~ conversation_depth += 1
Haxolottle: CYBER-PHYSICAL work is where things get interesting. It's the intersection of digital and physical security.
Haxolottle: You need to think in both domains simultaneously. You're physically infiltrating a facility AND conducting network reconnaissance. Bypassing door locks AND exploiting system vulnerabilities.
Haxolottle: The physical gives you access to the digital. Air-gapped systems you can't reach remotely. Hardware implants you need to place manually. Networks you have to be inside to attack.
Haxolottle: And the digital gives you advantages in the physical. Disabling cameras remotely. Unlocking doors electronically. Accessing building management systems.
Haxolottle: Best CYBER-PHYSICAL operations use both in concert—a beautiful symphony of integrated exploitation.
* [Ask about common CYBER-PHYSICAL scenarios]
~ conversation_depth += 1
You: What are typical CYBER-PHYSICAL mission types?
-> cyber_physical_scenarios
* [Ask what makes it challenging]
~ conversation_depth += 1
You: What makes CYBER-PHYSICAL work harder than single-domain operations?
-> cyber_physical_challenges
* [Move on]
-> lore_hub_handler
=== cyber_physical_scenarios ===
#speaker:agent_haxolottle
~ handler_influence += 5
Haxolottle: Common scenarios? Let me walk you through the hits:
Haxolottle: **Server room infiltration**—physically access air-gapped systems, extract data, implant monitoring devices. Classic CYBER-PHYSICAL.
Haxolottle: **Supply chain interdiction**—intercept hardware shipments, implant backdoors in devices, return them to the supply chain. Physical access enables digital compromise.
Haxolottle: **Facility reconnaissance**—gather physical intelligence about layout, security, personnel while simultaneously mapping network architecture and digital assets.
Haxolottle: **Critical infrastructure assessment**—evaluate both physical security of facilities and cyber security of control systems. Finding the intersection vulnerabilities.
Haxolottle: You'll run all of these eventually. Each one teaches you something about integrating the domains.
-> lore_hub_handler
=== cyber_physical_challenges ===
#speaker:agent_haxolottle
~ handler_influence += 8
Haxolottle: The challenge is cognitive load. You're managing two completely different threat models simultaneously.
Haxolottle: Physically, you're worried about: security cameras, patrol schedules, access controls, maintaining cover, physical evidence.
Haxolottle: Digitally, you're worried about: network monitoring, intrusion detection, log analysis, data exfiltration, digital forensics.
Haxolottle: And they interact in complex ways. Bypassing a door physically might create a digital log. Hacking a camera system requires physical access to a network port.
Haxolottle: You need to think like a penetration tester AND a burglar simultaneously. It's mentally exhausting until you develop the integration instinct.
Haxolottle: But that's why you're here. You've got the foundations in both domains. Now we teach you to weave them together.
~ handler_influence += 10
-> lore_hub_handler
// ===========================================
// DEEP LORE - HANDLER BACKSTORY
// ===========================================
=== handler_backstory ===
#speaker:agent_haxolottle
~ knows_handler_backstory = true
~ handler_influence += 15
~ conversation_depth += 2
Haxolottle looks surprised by the question.
Haxolottle: You want to know about my past? Most agents don't ask.
Haxolottle: I joined SAFETYNET... fifteen years ago. Recruited from a penetration testing firm after I responsibly disclosed some very uncomfortable vulnerabilities in government systems.
Haxolottle: Spent eight years in the field. Ran operations across four continents. Infiltrated ENTROPY cells, extracted intelligence, survived situations that probably should have killed me.
Haxolottle: The "Haxolottle" callsign came from Operation Regenerate—got pinned in a compromised position for seventy-two hours. Maintained cover, adapted strategy, turned what should have been a catastrophic failure into our biggest intelligence coup that year.
Haxolottle: During those three days, the only reading material I had was biology texts. Learned about axolotl regeneration. The metaphor stuck.
* [Ask why they became a handler]
~ conversation_depth += 1
You: Why did you transition from field work to handling?
-> why_handler_transition
* [Ask about the operation that earned the callsign]
~ conversation_depth += 1
You: What exactly happened during Operation Regenerate?
-> operation_regenerate_story
* [Express appreciation]
You: Thank you for sharing that. It helps to know your background.
-> lore_hub_handler
=== why_handler_transition ===
#speaker:agent_haxolottle
~ handler_influence += 10
Haxolottle: Good question. Honestly? I was getting burned out.
Haxolottle: Eight years of field work takes a toll. The stress. The constant danger. The isolation of maintaining cover identities for months.
Haxolottle: Then I got paired with a junior agent on a complex operation—mentorship role. Realized I was better at teaching than I expected. And I genuinely enjoyed helping them succeed.
Haxolottle: After that mission, SAFETYNET offered me a handler position. Chance to use my experience to support the next generation. Less personal risk, more strategic impact.
Haxolottle: I won't lie—I miss the field sometimes. The adrenaline. The direct action. But watching agents I've trained succeed? That's its own kind of satisfaction.
Haxolottle: And I get to make all the axolotl metaphors I want without someone telling me to shut up and focus on the mission.
~ handler_influence += 15
-> lore_hub_handler
=== operation_regenerate_story ===
#speaker:agent_haxolottle
~ handler_influence += 12
Haxolottle: Operation Regenerate. That's a story.
Haxolottle: I'd infiltrated an ENTROPY cell by assuming a compromised identity. Deep cover, weeks of preparation. Was gathering intelligence on their network structure and leadership.
Haxolottle: Then the original identity holder showed up. Unplanned. Unexpected. Suddenly I'm in a room with someone who knows I'm not who I claim to be.
Haxolottle: Couldn't extract—would have blown the entire operation and exposed SAFETYNET's capabilities. Couldn't maintain cover—he knew. Couldn't neutralize the threat—too many witnesses.
Haxolottle: So I improvised. Convinced him I was ENTROPY internal security running a loyalty test. Played it aggressive. Turned the tables.
Haxolottle: Spent seventy-two hours in that role—investigating "security concerns," interviewing cell members, all while extracting intelligence and praying he wouldn't call my bluff.
Haxolottle: Got out with intelligence that led to dismantling three connected cells. And a profound appreciation for regeneration—rebuilding your approach when the original plan dies.
~ handler_influence += 15
-> lore_hub_handler
// ===========================================
// DEEP LORE - BERLIN CRISIS
// ===========================================
=== berlin_crisis_story ===
#speaker:agent_haxolottle
~ knows_berlin_crisis = true
~ handler_influence += 20
~ director_influence += 10
Haxolottle's expression becomes somber.
Haxolottle: The Berlin Crisis. That's... not a story many people know.
Haxolottle: It happened about two years ago. SAFETYNET operation in Berlin—routine ENTROPY cell investigation that turned into a nightmare.
Haxolottle: One of our agents got compromised. Captured by the cell. ENTROPY was going to expose them, blow SAFETYNET operations across Europe.
Haxolottle: Director Netherton coordinated the extraction personally. Bent several handbook rules. Made some very questionable calls about collateral risk.
Haxolottle: But he got our agent out. Alive. Safe. The mission was technically a failure—lost the ENTROPY cell, burned intelligence assets—but Netherton prioritized the agent's life over operational success.
Haxolottle: It's why he's so strict about protocols now. Why he quotes the handbook constantly. Because when he broke the rules to save someone, it cost us dearly.
Haxolottle: And it's why I trust him completely. He'll protect you, Agent. Even when it costs him.
~ handler_influence += 20
~ discussed_moral_complexity = true
-> lore_hub_handler
// ===========================================
// END HANDLER CONVERSATION
// ===========================================
=== end_handler_conversation ===
#speaker:agent_haxolottle
{conversation_depth >= 5:
Haxolottle: You ask good questions, Agent {player_name}. Curiosity is a valuable trait in this work. Keep thinking deeply about what we do and why.
~ handler_influence += 10
- else:
Haxolottle: Anytime you want to talk, I'm here. Understanding the context helps you do the job better.
~ handler_influence += 5
}
#exit_conversation
-> END
// ===========================================
// ALTERNATIVE ENTRY POINTS
// ===========================================
// Entry point for technical support NPC (like Dr. Chen)
=== start_tech_support_lore ===
~ current_speaker = "tech_support"
#speaker:dr_chen
Dr. Chen: Got questions? I can explain technical details about ENTROPY's methods or our countermeasures. Rapid-fire style, hope you can keep up.
-> lore_hub_tech_support
// Simplified tech support hub (different perspective)
=== lore_hub_tech_support ===
+ {not discussed_entropy_tactics} [Ask about ENTROPY's technical tactics]
-> entropy_tactics_tech
+ {not discussed_safetynet_methods} [Ask about SAFETYNET's technical capabilities]
-> safetynet_tech_methods
+ {tech_influence >= 30} [Ask about cutting-edge research]
-> cutting_edge_research
+ [That's all]
#exit_conversation
-> END
=== entropy_tactics_tech ===
#speaker:dr_chen
~ discussed_entropy_tactics = true
~ tech_influence += 8
Dr. Chen: ENTROPY tactics—okay, technical breakdown incoming—
They use APT-style persistence, multi-stage payloads, living-off-the-land techniques, supply chain compromise, zero-day exploitation, social engineering at scale, and increasingly AI-powered automation.
Not random script kiddies. These are sophisticated threat actors with resources, patience, and technical excellence.
What makes them dangerous is integration—they combine technical exploits with physical access, human manipulation with automated attacks, patience with precision.
We counter with our own technical capabilities, but it's an arms race. They develop new techniques, we develop countermeasures, they adapt. Continuous cycle.
~ tech_influence += 5
-> lore_hub_tech_support
=== safetynet_tech_methods ===
#speaker:dr_chen
~ discussed_safetynet_methods = true
~ tech_influence += 8
Dr. Chen: Our technical capabilities—classified details obviously but general overview—
Custom exploitation frameworks. Proprietary malware analysis tools. Advanced network monitoring. Hardware implant technology. Secure communication infrastructure. Real-time intelligence correlation systems.
Plus partnerships with academia and private sector. We get early access to vulnerability research, cutting-edge security tools, zero-day intelligence.
My team develops custom tools for field operations. You need to bypass specific security system? We build the exploit. Need to exfiltrate data without detection? We create the method.
It's like running a security research lab combined with a mission support center. Fast-paced, high-pressure, intellectually stimulating.
~ tech_influence += 5
-> lore_hub_tech_support
=== cutting_edge_research ===
#speaker:dr_chen
~ tech_influence += 15
Dr. Chen speaks even faster, excited about the topic.
Dr. Chen: Cutting-edge stuff—this is confidential—we're researching quantum-resistant cryptography, AI-powered threat detection, hardware-level security, supply chain verification systems, and some experimental techniques I can't fully discuss.
The esoteric ENTROPY cells are pushing us into weird territory. Quantum computing. Reality manipulation claims. We're having to develop countermeasures for threats that sound like science fiction.
It's fascinating and terrifying simultaneously. We're at the frontier of cybersecurity, dealing with adversaries who don't respect conventional limitations.
~ tech_influence += 15
-> lore_hub_tech_support
// ===========================================
// DIRECTOR VARIANT (Brief, formal)
// ===========================================
=== start_director_lore ===
~ current_speaker = "director"
#speaker:director_netherton
Director Netherton: You have questions regarding operational context, Agent?
-> lore_hub_director
=== lore_hub_director ===
+ {not discussed_safetynet_mission} [Ask about SAFETYNET's mandate]
-> safetynet_mandate_director
+ {not discussed_moral_complexity} [Ask about rules of engagement]
-> rules_of_engagement_director
+ {director_influence >= 40} [Ask about the organization's future]
-> safetynet_future_director
+ [No further questions]
#exit_conversation
-> END
=== safetynet_mandate_director ===
#speaker:director_netherton
~ discussed_safetynet_mission = true
~ director_influence += 8
Netherton: SAFETYNET's mandate, as outlined in founding charter section 1.2, is protection of critical infrastructure and national security interests through proactive counter-espionage operations.
We operate under classified legal authorities. Our existence is not publicly acknowledged. Our successes are invisible. Our failures would be catastrophic.
The responsibility is enormous. The oversight is minimal. Therefore, our adherence to operational protocols and ethical guidelines is paramount.
We are not vigilantes. We are not above the law. We operate in the gray areas the law cannot effectively address, with the understanding that our power must be exercised responsibly.
~ director_influence += 8
~ discussed_moral_complexity = true
-> lore_hub_director
=== rules_of_engagement_director ===
#speaker:director_netherton
~ discussed_moral_complexity = true
~ director_influence += 10
Netherton: The Field Operations Handbook sections 8 through 11 outline our rules of engagement in detail.
Key principles: Minimize collateral damage. Protect innocent bystanders. Use appropriate force. Maintain plausible deniability. Prioritize intelligence over elimination.
We are not assassins. We are intelligence operatives. Our objective is understanding and disrupting ENTROPY, not indiscriminate destruction.
When force is necessary, it must be proportional, justified, and documented. I review every operation personally. Deviations from protocol are investigated.
The power we wield demands discipline. Without it, we become the threat we're supposed to counter.
~ director_influence += 15
-> lore_hub_director
=== safetynet_future_director ===
#speaker:director_netherton
~ director_influence += 20
Netherton pauses, considering the question carefully.
Netherton: The future of SAFETYNET depends on agents like you, Agent {player_name}.
ENTROPY is evolving. Their techniques advance. Their cells multiply. Traditional approaches are insufficient.
We need operatives who can think strategically, act ethically, and adapt continuously. Who understand both the technical and human dimensions of security.
The organization I helped build two decades ago must evolve. New generation leadership. New methodologies. Maintained ethical foundations.
*He looks directly at you*
Netherton: You represent that future. Your generation will face threats I cannot fully anticipate. My role is ensuring you're prepared for them.
~ director_influence += 25
-> lore_hub_director
// ===========================================
// SYSTEM NOTES
// ===========================================
// This hub system can be integrated into missions as:
// 1. Optional dialogue during downtime
// 2. Phone conversations with handler
// 3. Briefing room discussions
// 4. Post-mission debriefs
//
// Influence tracking allows:
// - Deeper information unlocked over time
// - Character relationship development
// - Different perspectives from different NPCs
// - Replayability through gradual revelation
//
// Topics designed to be modular - can be accessed
// in any order, with some requiring prerequisites
// ===========================================