Roadmap TODOs
27 open
27 items
○
Later add: ARMOR, RING, etc.
○
Add Level and Experience here when the leveling system replaces the current PowerLevel-only progression.
○
Extend this conversion when full inventory, spellbook, and other per-character systems need persistence.
○
Restore Level/Experience and other new subsystems here as CharacterSaveData grows.
○
Promote the root save payload from List<CharacterSaveData> to a SaveGame object when WorldState and roster data are added.
○
Load schema version, WorldState, and roster metadata here once the save format expands beyond character snapshots.
○
Serialize WorldState, roster unlocks, and future save-version metadata alongside characters.
○
Move spell metadata toward unlockable/progression-aware content once leveling and spell acquisition are added.
○
Integrate combat logging, target validation, and status-effect resolution with CombatManager instead of direct console-only flow.
○
Replace the raw character list with a CharacterRoster once slot unlocks and active-hero tracking are implemented.
○
Bootstrap the starting region from saved WorldState/region data instead of creating a one-off world here.
○
Prevent creation when the roster is full and surface the next slot unlock requirement in the menu.
○
Persist the active character in save data so the last played hero is restored on launch.
○
Route Explore into the travel/location loop once regions, encounters, and quest hooks exist.
○
Replace this stub with CombatManager once combat, loot, and post-fight rewards are implemented.
○
Present region/location choices here and resolve travel, random encounters, dialogue, and world-flag updates.
○
Start CombatManager here and replace this placeholder once enemies, actions, and rewards exist.
○
Evolve this into region/world data that can participate in travel routes, encounter tables, and reputation/world-flag checks.
○
comments, and formats them into a professional Markdown document.
○
comments
○
[: ](.*)", RegexOptions.IgnoreCase)
○
Introduce Level/Experience and shared combat-facing members here when Character implements the combat system contract.
○
Replace this with region travel rules that consult WorldState, unlock flags, and travel requirements.
○
Add functionality to travel to different worlds, which may require additional properties and methods related to world management.
○
Research need for all constructors or only those to create a character
○
Implement spells and mana system (ESP)
○
Route casting through the combat turn system so spell selection, mana spend, and status effects are resolved consistently.