quest-skill

Tracking main and side quest progress involves reading a quest log to apply state transitions, trigger points, and causal continuity to influence plots and character actions. This ensures causal continuity by persisting task data changes after story events.

Maintaining story logic requires persisting task records and state transitions in a dedicated quest log reference file. By reading this log before generating plots and syncing updates afterward, you ensure narrative continuity and prevent forgetting critical tasks.

Updating quest status requires executing a Python script to apply state transitions based on story logic. The script reads the quest log, modifies task states to reflect plot progression, and persists the updated data to maintain narrative consistency.

Separating main quests from side quests is supported during task tracking and state updates. The quest management system optionally categorizes these tasks, allowing you to generate specific progress descriptions and trigger points for each quest type independently.

Python scripts are required to read, modify, and persist task data within the quest system. The script processes state transitions and updates the quest log markdown references to ensure plot continuity and synchronize task changes after story generation.