Zones

Zones are interactive areas in your World that help create dynamic experiences for Players. They act as triggers that can activate events, spawn Mooks, and control Helpers based on various conditions.

• Basic Setup:
  1. Define the zone's radius and coordinates.
  2. Choose whether to lock the zone to specific Areas or Points:
     1. When a zone is locked, it will only activate when the Player is in the specified Area or Point.
  3. Set movement control options (like halting Player movement on entry).

• Events:
  1. Create scripted sequences that trigger when Players enter the zone.
  2. Create multi-step event progressions.
  3. Disable Helpers from being active during the event steps.

• Mooks:
  1. Spawn groups of Mooks within the zone.
  2. Set the Mooks as Avoidable for the Player to get a chance to avoid them (e.g., rolling for stealth).

• Activation Controls:
  1. Time-based windows (specific dates/times when zones are active).
  2. Area-based restrictions (zones only active in specific locations).
  3. Point-based positioning (zones tied to specific coordinates).
  4. NPC presence requirements:
     1. Can choose to teleport the NPC to the zone or require them to be in the zone for the zone to activate.
     2. Only activates if the NPCs are alive and available.
  5. Allow Repeat After (Days):
     1. Allows the zone to repeat after a certain number of days have passed.
     2. Set to 0 to disable (one-time only).

Events are scripted sequences that can be triggered when Players enter a zone. Each event can have multiple steps, with each step containing specific instructions, requirements, and actions.

Each event step consists of:

• Instructions:
  1. The main narrative content or description of what happens in this step.
  2. Support for @tagging characters, locations (areas and points) as well as $tagging items to provide context.
  3. Tagged objects' information becomes available to the narrative AI during the event.
  4. Important: Objects must be tagged to be referenced if not in the immediate vicinity.

• Requirements:
  1. Conditions that must be met before progressing to the next step.
  2. Can include multiple requirements per step.
  3. All requirements must be completed to advance.
  4. Examples:
     1. Player must talk to specific NPCs.
     2. Items must be collected.

• Constraints:
  1. Special instructions for the AI about what to avoid.
  2. Helps maintain story consistency.
  3. Prevents spoiler reveals.
  4. Controls information flow.
  5. Example: “Don't reveal the character's true identity yet.”

• Actions:
  1. Automated commands that execute when a step completes.
  2. Character Status Management:
     1. `Set @[Character] Status To [Active/Deceased/Unavailable]`.
  3. Movement Control:
     1. `Move @[Target] to @[Area/Point/Character/Coordinates]`.

• Helper Control:
  1. You can disable individual Helpers from being active during the event steps.
  2. This is useful for disabling movement or new character spawns during the event steps.

• Time Windows: Set specific dates and times when the event can occur.
• Required NPCs: Specify characters that must be present for the event to trigger.
• Teleport Options: Automatically move required NPCs to the event location.
• Repeat Settings: Configure how often the event can recur.