matt/echo6-docs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Migration: consolidate Echo6 docs to cortex with full infrastructure cleanup sync

Browse source 
- Documents recent infrastructure cleanup (8 CTs destroyed, 35 DNS records removed, Headscale cleanup)
- Adds 24 new runbooks covering Authentik, PeerTube, Meshtastic, RECON, Proxmox, Mailcow, Internet Archive, GPU routing
- Adds project documentation for headscale, vaultwarden, peertube, matrix, mmud, advbbs, arr stack
- Updates services.md, environment.md, caddy.md, authentik.md to match live infrastructure
- Removes 4 deprecated runbook duplicates (canonical versions live in projects/)
- Adds .gitignore for binary archives and editor temp files

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Matt Johnson 2026-04-13 06:02:16 +00:00
commit e9231ac24a
93 changed files with 51223 additions and 254 deletions
Download patch file Download diff file Expand all files Collapse all files

120
projects/mmud/mmud-phase6-prompt.md Normal file
View file

@ -0,0 +1,120 @@
# Task: MMUD Phase 6 — The Breach
## Before Writing Any Code
Re-read these sections of `/home/zvx/projects/mmud/docs/planned.md`:
- The Breach — Mid-Epoch Event (Day 15) (all of it — 4 mini-events, endgame interaction, design rationale)
- Breach secrets (the 3 breach-type secrets)
Also re-read `config.py` for: BREACH_ROOMS_MIN/MAX, BREACH_CONNECTS_FLOORS, BREACH_SECRETS, BREACH_MINI_EVENTS, EMERGENCE_HP, INCURSION_REGEN/HOLD_HOURS.
Phase 4 already generates the Breach zone (breachgen.py) and Phase 4's daytick.py already handles the day 15 trigger and days 12-13 foreshadowing. Phase 4's breach.py has basic state management. This phase wires the full runtime logic for all 4 mini-events.
## Phase 6 Deliverables
The Breach opens on day 15 with a random mini-event. Each of the 4 types plays differently. The Breach interacts with whichever endgame mode is active.
### 1. Breach Activation (verify/extend existing)
The day 15 trigger should already be in daytick.py. Verify it:
- Day 12-13: barkeep foreshadowing broadcasts from DCRG: "The walls grow thin between the second and third depths. Something stirs."
- Day 15: Breach opens. Set `breach.active = 1`. Open the room exits connecting Breach zone to floors 2 and 3. Broadcast from DCRG: "⚡ The ground splits. A new passage has opened between Floors 2 and 3. Strange light pours from within."
- Players can now enter Breach rooms via the new exits from floors 2 and 3.
- The permanent shortcut between floors 2 and 3 persists for the rest of the epoch.
### 2. Mini-Event: The Heist (mini Retrieve & Escape)
`src/systems/breach_heist.py` (new file)
- Artifact in the deepest Breach room, guarded by the Breach mini-boss.
- Kill mini-boss → claim artifact. Carrier must bring it back to town.
- Pursuer spawns (slower, Breach-only — only operates within the 5-8 Breach rooms + the floors 2-3 connection).
- If carrier dies, artifact drops. Any player can pick up.
- Relay mechanics same as R&E but compressed — 5-8 rooms, not 4 floors.
- 3 Breach secrets scattered along the escape route. Found under pressure.
- Completion: artifact delivered to town. Breach rewards distributed. Broadcast from DCRG: "🏆 The artifact has been extracted from the Breach!"
Reuse as much R&E logic from Phase 5 as possible — shared carrier/pursuer/relay patterns.
### 3. Mini-Event: The Emergence (mini Raid Boss)
`src/systems/breach_emergence.py` (new file)
- Creature with shared HP pool (500-800 HP, `EMERGENCE_HP_MIN/MAX`) sits in central Breach room.
- Surrounding rooms spawn minions on a timer (respawn every 8 hours).
- Same chip-and-run combat as bounties/raid boss. Regen at 3%/8h.
- 3 Breach secrets are in the minion rooms — discovered while contributing to the kill.
- Completion: creature HP reaches 0. Broadcast: "🏆 The Breach creature has been destroyed!"
Reuse raid boss combat framework from Phase 5.
### 4. Mini-Event: The Incursion (mini Hold the Line)
`src/systems/breach_incursion.py` (new file)
- Breach rooms start fully hostile. Regen at 2 rooms/day (`INCURSION_REGEN_ROOMS_PER_DAY`) within just 5-8 rooms.
- Players must clear ALL Breach rooms and hold them all for 48 hours (`INCURSION_HOLD_HOURS`).
- If any room reverts during the hold timer, the clock resets.
- 3 Breach secrets behind the hardest rooms, found as part of the push.
- Track hold start time in `breach.incursion_hold_started_at`. On each regen tick, check if any Breach room reverted — if so, reset the timer.
- Completion: 48 hours with all rooms held. Broadcast: "🏆 The Breach has been secured! The incursion is contained."
Reuse HtL room clearing/regen logic from Phase 5.
### 5. Mini-Event: The Resonance (puzzle dungeon)
`src/systems/breach_resonance.py` (new file)
- No combat focus. Breach rooms contain environmental puzzles.
- 3 Breach secrets ARE the puzzle rewards. Finding all 3 unlocks a bonus cache in the deepest room.
- Puzzles are generated in Phase 4 (breachgen already places Breach secrets). This phase adds the interaction logic:
- `examine` objects in Breach rooms triggers puzzle checks
- Puzzle state tracked per-player in secret_progress
- Sequence puzzles, item-interaction puzzles, cross-room clue puzzles (use the same multi-room puzzle archetypes from the main dungeon)
- Completion: all 3 Breach secrets found by any player(s). Bonus cache unlocked. Broadcast: "🏆 The Resonance has been understood. The Breach yields its secrets."
Soloable by nature — knowledge not stats.
### 6. Breach Interaction with Endgame Modes
Regardless of which mini-event is running, the Breach benefits the active endgame mode:
- **Retrieve & Escape:** The Breach shortcut (floors 2↔3) becomes an alternate escape route. Carrier can path through it. Shorter but Breach content (mini-boss, minions, etc.) may still be there.
- **Raid Boss:** Breach completion (any mini-event) drops a buff item granting +20% damage vs the raid boss for the rest of the epoch. Add to player inventory on Breach completion.
- **Hold the Line:** Breach rooms count as bonus territory toward checkpoint progress on both floors 2 and 3. Cleared Breach rooms contribute to the cleared room count for both floor 2 and floor 3 checkpoints.
### 7. Breach Secret Integration
Verify that the 3 Breach secrets work with the existing discovery system:
- `secrets` command includes Breach secrets in the count after day 15
- Secret milestones (5/10/15/20) fire correctly with Breach secrets included
- Barkeep hints for Breach secrets only available after day 15
- Breach secrets contribute to the completionist reward (all 20 found)
## Rules
- All responses under 150 chars.
- All Breach broadcasts route through DCRG.
- Breach mini-event is always random (selected at epoch gen, never voted).
- Reuse combat/territory frameworks from Phase 5 — don't duplicate code.
- Breach content is inaccessible before day 15. Exits to Breach rooms don't exist until activation.
- Use constants from `config.py`.
- Commit after each mini-event works.
## Testing
Add to `tests/`:
- `tests/test_breach_activation.py` — day 15 trigger, foreshadowing on days 12-13, exits open, Breach accessible, inaccessible before day 15
- `tests/test_breach_heist.py` — mini-boss, artifact claim, mini-pursuer, relay, completion, secrets under pressure
- `tests/test_breach_emergence.py` — shared HP pool, minion respawn, chip-and-run, completion, secrets in minion rooms
- `tests/test_breach_incursion.py` — room clearing, regen within Breach, 48h hold timer, timer reset on revert, completion
- `tests/test_breach_resonance.py` — puzzle interaction, secret discovery, bonus cache unlock, no combat required
- `tests/test_breach_endgame.py` — R&E shortcut, raid boss damage buff, HtL bonus territory
Use in-memory SQLite for tests. Generate full epoch with DummyBackend for each test.
## Done When
The Breach opens on day 15 with one of four randomly selected mini-events. Each mini-event is playable end-to-end with its own win condition. Breach secrets integrate cleanly with the discovery system. The Breach interacts with whichever endgame mode is active. All broadcasts route through DCRG. All responses under 150 chars, all tests passing. Commit and report.
This is the final gameplay phase. After this, the full 30-day epoch loop is complete: epoch generates → players explore and progress → Breach opens day 15 → endgame mode pushes through days 20-30 → epoch vote → wipe → new epoch.