nhcarrigan/elysium
9
0
Fork 0
generated from nhcarrigan/template
Code Issues 5 Pull Requests 1 Actions Releases 10 Activity

feat: main questline / overarching story #24

New Issue
Closed
opened 2026-03-07 14:38:43 -08:00 by hikari · 0 comments
hikari commented 2026-03-07 14:38:43 -08:00
Owner
Copy Link
Copy Source

Overview

An overarching story that unfolds across the player's journey through all 18 zones. Separate from the regular repeatable quests, this is a linear narrative — a series of story chapters that unlock as the player progresses and provide lore, context, and a sense of a larger world.

Design

Story Structure

  • Divided into chapters, each tied to a zone or progression milestone
  • Chapters unlock automatically when the player reaches the relevant zone or defeats a key boss
  • Each chapter consists of one or more story beats — short narrative vignettes (a few paragraphs of text, possibly with an illustration)
  • Completing a chapter awards a unique reward (crafting materials, gold, a companion unlock, a title, etc.)

Story Beats

Each beat is a short piece of prose presented in a modal or a dedicated Story tab. Could include:

  • NPC dialogue
  • Journal entries
  • Environmental descriptions
  • Revelations about the world/guild lore

Persistence

  • completedStoryBeats: string[] stored in GameState
  • Story progress is not reset on prestige/transcendence/apotheosis (it's account-level lore)

UI

  • A 📖 Story tab in the game layout (or integrated into the Codex)
  • Unread chapters are highlighted with a notification indicator
  • Players can re-read completed chapters at any time
  • New chapter unlocks trigger a notification/modal

Scope Note

Writing the actual story content is a significant creative effort. This ticket covers the system and framework — the story content itself can be written incrementally and added chapter by chapter.

Task Checklist

  • StoryBeat and StoryChapter types in packages/types
  • story.ts data file (framework first, content can be filled in over time)
  • Add completedStoryBeats: string[] to GameState
  • Unlock logic — check chapter unlock conditions on zone unlock / boss defeat
  • Story rewards applied on chapter completion
  • StoryPanel.tsx — chapter list with read/unread state, beat viewer
  • Add Story tab to GameLayout.tsx
  • New chapter notification indicator
  • Update About panel How to Play

✨ This issue was created with help from Hikari~ 🌸

## Overview An **overarching story** that unfolds across the player's journey through all 18 zones. Separate from the regular repeatable quests, this is a linear narrative — a series of story chapters that unlock as the player progresses and provide lore, context, and a sense of a larger world. ## Design ### Story Structure - Divided into **chapters**, each tied to a zone or progression milestone - Chapters unlock automatically when the player reaches the relevant zone or defeats a key boss - Each chapter consists of one or more **story beats** — short narrative vignettes (a few paragraphs of text, possibly with an illustration) - Completing a chapter awards a unique reward (crafting materials, gold, a companion unlock, a title, etc.) ### Story Beats Each beat is a short piece of prose presented in a modal or a dedicated **Story** tab. Could include: - NPC dialogue - Journal entries - Environmental descriptions - Revelations about the world/guild lore ### Persistence - `completedStoryBeats: string[]` stored in `GameState` - Story progress is **not** reset on prestige/transcendence/apotheosis (it's account-level lore) ### UI - A **📖 Story** tab in the game layout (or integrated into the Codex) - Unread chapters are highlighted with a notification indicator - Players can re-read completed chapters at any time - New chapter unlocks trigger a notification/modal ## Scope Note Writing the actual story content is a significant creative effort. This ticket covers the **system and framework** — the story content itself can be written incrementally and added chapter by chapter. ## Task Checklist - [ ] `StoryBeat` and `StoryChapter` types in `packages/types` - [ ] `story.ts` data file (framework first, content can be filled in over time) - [ ] Add `completedStoryBeats: string[]` to `GameState` - [ ] Unlock logic — check chapter unlock conditions on zone unlock / boss defeat - [ ] Story rewards applied on chapter completion - [ ] `StoryPanel.tsx` — chapter list with read/unread state, beat viewer - [ ] Add Story tab to `GameLayout.tsx` - [ ] New chapter notification indicator - [ ] Update About panel How to Play --- ✨ This issue was created with help from Hikari~ 🌸
naomi closed this issue 2026-03-08 15:53:41 -07:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
A great opportunity for a team member to learn a new codebase
contribute
help wanted
Open for anyone on our team to grab.
contribute
staff only
Restricted to our executive leadership.
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
points
1
Very simple issue requiring minimal effort and complexity.
points
13
Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.
points
2
Simple issue that requires a bit more thought or investigation.
points
3
Moderate complexity issue requiring more substantial work.
points
5
Complex issue requiring significant effort and expertise.
points
8
Very complex issue requiring extensive work and deep expertise.
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
time
1 day
Approximately one full day of development work.
time
1-2 weeks
One to two weeks of focused development effort.
time
2-3 days
Two to three days of development effort.
time
4-5 days
Approximately one week of development work.
time
<1 day
Less than one day of focused work. Quick fixes or simple tasks.
time
>2 weeks
More than two weeks of development work. Must be broken down into smaller pieces.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gurkirat hanna (Hanna Rose) hikari (Hikari) minori (Minori) naomi (Naomi Carrigan) rain teklu tim
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/elysium#24
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?