🛠️ ❗ Refactor Story.js for Two-Phase Story System

[MvPorcalla]

📋 Description

Refactor the existing story.js into a Story Manager System that supports a two-phase story structure:

• Baby Phase (Prologue): Player starts as a baby, making choices and encountering events that shape the player's stats and development. At the end of this phase, the player's stats will determine the available job class options.
• Adult Phase (Main Story): After job class selection, the player enters a linear but branching main story with:
  • Story checkpoints
  • Filler story events or encounters (random or selected from story pool)
  • Possible stat allocation or leveling system (to be decided)
  • Branching paths based on player’s past choices, stats, and job class
  • Different possible endings

At the end of the story, the Epilogue Phase will display a summary (image and text) of the player’s entire journey, including key choices and completed filler events.

---

✨ Features

• Split the story into Baby Phase and Adult Phase
• Track player stats and choices throughout both phases
• Implement job class assignment based on baby phase stats
• Load filler events and encounters dynamically from a story pool
• Support branching paths based on player decisions and job class
• Display a custom Epilogue summarizing the player’s journey, choices, and story path

---

🔗 Related Files

• story.js → Main refactor target
• player.js → Track story phase, stats, and job class
• gameManager.js → Handle phase transitions and story flow
• ui.js → Display story text, choices, and epilogue content
• assets/data/storyPool.json → Optional, for filler events storage

---

💬 Additional Notes

• Consider adding a story manager or controller to better organize story flow and transitions between phases.
• Filler events should be modular and reusable to support dynamic loading and replayability.
• Epilogue should reflect:
  • Player’s job class
  • Major story choices
  • Completed filler events
  • Player stats and achievements