generated from nhcarrigan/template
feat: goddess expansion (post-vampire-apotheosis alternate game mode) #18
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Overview
After completing their first Apotheosis in Vampire Mode, players unlock a Goddess Mode — the third and hardest game mode, with divine/celestial theming. Same loop as the base game and vampire expansion, but even slower income, more expensive purchases, lower quest/boss rewards, and an altogether more punishing experience.
Players can toggle freely between all unlocked modes. State is fully isolated per mode — switching saves the current state and loads the other.
Unlock chain:
Architecture
Data Model
GoddessGameStatePrisma model mirroringGameStateandVampireGameState, stored in its own MongoDB collectionPlayergets agoddessUnlocked: Booleanfield — set totrueon first Apotheosis in Vampire Mode✨ Goddess ModeMode Switcher UI
goddessUnlocked = trueVisual Theme
.goddess-modeclass to the root elementTuning (harder than vampire mode)
Content (fully fresh goddess/celestial-themed, matching base game scale)
Zone theme suggestions: Celestial Gardens, The Gilded Sanctum, Astral Halls, The Divine Forge, Empyrean Reaches, The Eternal Throne, etc.
Task Checklist
GoddessGameStateschema + migration, toggle API update (three-way), mode switcher UI update,.goddess-modeCSS themebaseCostNote: Should be implemented after #17 (Vampire Mode) is complete, as it depends on the mode-switching architecture established there.
✨ This issue was created with help from Hikari~ 🌸