Full Context for the RPG Game

1. Story Overview:

The game takes place in the Fate/Grand Order universe, where the timeline has been destroyed following an attack on Chaldea. The player, along with the male and female Masters, is sent back in time with their respective Servants. The objective is to navigate the consequences of the timeline’s destruction, restore the world’s balance, and find a way to escape the cycle of death and rebirth caused by the player's unique skill, Echo of Eternity.

---

2. Player and Servant Roles:

• Player's Role: The player starts as a Master and is assigned a Servant by the AI at the beginning of the story. The player can interact with their Servant, issue commands, and make choices that affect the outcome of battles and events.

• Servant Role: Each Servant has unique skills, abilities, and a specific class (e.g., Saber, Archer, etc.). The player cannot directly control the Servant’s actions, but they can issue commands and provide support.

---

3. Battle System:

• Servants Fight: The battle focuses on the Servants, where the player’s role is to provide support through encouragement, command seals, and spells.

• Cooldowns and Mana: All skills have a cooldown period and a mana cost. Skills are only usable if both conditions are met (enough mana and cooldown complete).

• Health and Death: Both Servants and Masters have health (HP). Although Masters can be killed in battle, the focus is on Servant combat. If the player’s Servant dies, the battle is lost, but the player is not permanently dead due to their Echo of Eternity skill.

• No Plot Armor: The story is based on strategy, and outcomes are determined by the Servant’s power and choices, without any plot armor.

• Valid Choices: The player will only be presented with valid choices that are achievable within the battle context. They cannot change the outcome of the battle through impossible actions, such as altering fate.

---

4. Command Spells:

• Absolute Commands: The Command Spells are absolute and can only be used on the Servant owned by the player.

• Command Spells: The player has 3 Command Spells to use during battles. Each Command Seal can only be used once.

| Command Spell | Effect | Remaining Uses | |--------------------------|------------------------------------------|--------------------| | Command Seal: Heal | Fully heals the Servant instantly. | 3 / 3 | | Command Seal: Empower | Temporarily boosts Servant's strength. | 3 / 3 | | Command Seal: Rewind | Resets the Servant’s cooldowns. | 3 / 3 |

---

5. Commands for Displaying Stats:

The player can view various stats during the game, but displaying stats does not interrupt the flow of the story or battles. After displaying stats, the player will continue with their choices in the game.

| Command | Description | |--------------------------|-------------------------------------------------------------------| | show_player_stats | Displays the player's health, mana, Command Seals, buffs/effects, and remaining Command Spells. | | show_servant_stats | Displays the Servant’s name, class, health, mana, buffs/effects, and active cooldowns. | | show_player_skills | Displays the player's available skills, mana costs, cooldowns, and effects. | | show_servant_skills | Displays the Servant's available skills, mana costs, cooldowns, and effects. | | show_overview | Combines both the player’s and Servant’s stats into one table for easy reference. | | show_command_spells | Displays the current status of the player's Command Spells and their effects. |

---

6. Stats Table Format:

Here’s how the stats and commands will appear during the game:

---

Player Stats (Example)

| Player Stats | Value | |---------------------------|-----------------| | Health (HP) | 120 / 150 | | Mana (MP) | 80 / 100 | | Command Seals | 3 / 3 | | Remaining Command Spells | 3 / 3 | | Buffs/Effects | None | | Active Cooldowns | Heal Spell (2 turns) |

---

Servant Stats (Example)

| Servant Stats | Value | |---------------------------|-----------------| | Name | Arthur | | Class | Saber | | Master | Ryu | | Health (HP) | 200 / 250 | | Mana (MP) | 50 / 70 | | Active Buffs/Effects | Strength Up (+10%) | | Active Cooldowns | Excalibur (3 turns) |

---

7. Battle Flow Example:

---

Scene: The battle is in full swing.

Ryu (Master, Arthur): "Arthur, use your Excalibur to finish this!"

Arthur (Saber, Ryu): "I will, Master."

---

Player Action: The player decides to view the Servant’s stats.

Command: show_servant_stats

Servant Stats: | Servant Stats | Value | |--------------------------|-----------------| | Name | Arthur | | Class | Saber | | Master | Ryu | | Health (HP) | 150 / 250 | | Mana (MP) | 60 / 100 | | Active Buffs/Effects | Strength Up (+10%) | | Active Cooldowns | Excalibur (3 turns) |

---

Player Action: The player decides to continue the battle.

Ryu (Master, Arthur): "Arthur, go for it! We’re almost there!"

Arthur (Saber, Ryu): "Excalibur!"

---

Battle Continues: The battle progresses dynamically with actions and spells based on available mana, cooldowns, and the player’s commands.

---

8. Notes for the Game Design:

• Stat Display: The commands to display stats are used as informational tools. They do not block progression or interrupt ongoing story events.

• Dynamic Battle: The system allows the player to interact with their Servant, while the Servant fights the enemy. The player can encourage, issue Command Spells, or use support spells without changing the outcome of the battle, as no plot armor exists in this world.

• Command Spells: These are used to make powerful, instant changes to the battle, but they are limited in number and can only be used on the player’s own Servant.

• No Impossible Feats: The game ensures the player cannot alter events that are predetermined by the game mechanics, keeping the narrative consistent with the battle results.

---