Configuration Overview

Titan uses a modular configuration system where fight configs reference separate move sets, phase sets, and behaviour configs. This allows for powerful reusability and composition.

New Modular Architecture

Key Change

Breaking Change

Old System: Monolithic configs with all data embedded

New System: Modular configs with references to separate files

Benefits

✅ Reusability - Share moves/phases across multiple Titans
✅ Organization - Separate concerns into logical files
✅ Maintainability - Update one move set, affect multiple Titans
✅ Flexibility - Mix and match components

File Structure

Directoryserver/
- Directoryconfig/titan/
  - Directoryfights/ Fight manifests (references)
    charizard.json
    raichu.json
    ceruledge.json
    … (33 total)
  - Directorymoves/ Move set definitions
    charizard.json
    raichu.json
    ceruledge.json
    core.json (shared moves)
    default_titan.json
    index.json
  - Directoryphases/ Phase configurations
    charizard.json
    raichu.json
    ceruledge.json
    default_titan.json (generic 3-phase)
    index.json
  - Directorybehaviour/ Behaviour configs (optional)
    default.json
    raichu.json
    index.json
- Directoryworld/datapacks/your_pack/data/titan/
  - Directoryaction_effects/ ActionEffect timelines
    charizard_inferno_blaze.json
    raichu_gigavolt_havoc.json
    ceruledge_armor_oblivion.json
    … (100+ effects)
- Directorymods/
  - titan-x.x.x.jar

Configuration Types

1. Fight Manifests (`config/titan/fights/*.json`)

Location: config/titan/fights/ Format: JSON Purpose: Reference other config files

Fight manifests are lightweight references that link to move sets, phase sets, and behaviours:

{
  "_comment": "Titan Raichu Boss Fight - Electric powerhouse",
  "pokemonProperties": "raichu",
  "name": "Storm Surge Titan Raichu",
  "moveSet": "raichu",      // ← References config/titan/moves/raichu.json
  "phaseSet": "raichu",     // ← References config/titan/phases/raichu.json
  "behaviour": "raichu"     // ← References config/titan/behaviour/raichu.json
}

When to Edit:

Creating new Titan variant
Changing which configs to use
Swapping move/phase/behaviour sets

See: Fight Configurations →

2. Move Sets (`config/titan/moves/*.json`)

Location: config/titan/moves/ Format: JSON Purpose: Define all moves available to a Titan

Move sets contain move definitions and selection strategy:

{
  "moves": {
    "thunderstrike": {
      "name": "Thunderstrike",
      "cooldown": "120",
      "range": "10.0",
      "damage": "42.0",
      "damageType": "ELECTRIC",
      "actionEffect": "titan:raichu_thunderstrike",
      "condition": "true",
      "weight": 1.4,
      "minHealthPercent": 0.5,
      "maxHealthPercent": 1.0,
      "phase": -1
    },
    // ... 14 more moves
  },
  "selectionStrategy": "WEIGHTED_RANDOM"
}

When to Edit:

Adding new moves
Adjusting damage/cooldowns
Changing move weights
Modifying health availability ranges

See: Move Sets →

3. Phase Sets (`config/titan/phases/*.json`)

Location: config/titan/phases/ Format: JSON Purpose: Define health-based progression

Phase sets configure health thresholds, stat modifiers, and movement:

{
  "phases": [
    {
      "healthThreshold": 1.0,
      "moves": ["storm_call", "thunderstrike", "chain_lightning"],
      "speedModifier": 1.15,
      "damageModifier": 1.0,
      "scaleModifier": 1.1,
      "movementPattern": "KITING",
      "aggressionLevel": 1.2,
      "onEnterScript": "q.titan.apply_potion('minecraft:speed', 999999, 0);",
      "onExitScript": "q.titan.remove_potion('minecraft:speed');"
    },
    {
      "healthThreshold": 0.6,
      "moves": ["storm_surge", "electroweb", "thunder_cage"],
      "speedModifier": 1.28,
      "damageModifier": 1.2,
      "scaleModifier": 1.15,
      "movementPattern": "TELEPORT",
      "aggressionLevel": 1.5,
      "movementOverrides": {
        "teleport": {
          "minRange": 4.0,
          "maxRange": 8.0,
          "radialCandidates": 10,
          "heightVariance": 2.5,
          "cooldownMs": 12000
        }
      }
    },
    // Phase 3...
  ]
}

When to Edit:

Adjusting health thresholds
Modifying stat modifiers (speed/damage/scale)
Changing move pools per phase
Configuring movement patterns
Adding phase scripts

See: Phases →

4. Behaviour Configs (`config/titan/behaviour/*.json`)

Location: config/titan/behaviour/ Format: JSON Purpose: Default movement pattern and aggression (optional)

Behaviour configs set baseline AI parameters:

{
  "movementPattern": "TELEPORT",
  "aggressionLevel": 1.35
}

When to Edit:

Setting default movement controller
Configuring base aggression
Adding state machines (advanced)

Default: If omitted, uses default.json (STANDARD movement, 1.0 aggression)

See: Movement Controllers →

5. ActionEffect Timelines (`world/datapacks/your_pack/data/titan/action_effects/*.json`)

Location: world/datapacks/your_pack/data/titan/action_effects/ Format: JSON (Cobblemon ActionEffect format) Purpose: Define attack animations and damage timelines

ActionEffects are referenced by move sets’ actionEffect property:

{
  "timeline": [
    {"type": "add_holds", "holds": ["effects"]},
    {"type": "stop_movement", "duration": "2000"},
    {"type": "define_obb", "name": "attack_area", ...},
    {"type": "telegraph_obb", "obbName": "attack_area", ...},
    {
      "type": "server_molang",
      "expressions": [
        "q.play_sound('minecraft:entity.lightning_bolt.thunder', 2.0, 1.0);",
        "t.pos = q.position(0);",
        "q.particle_effect('cobblemon:thunder_actorcloud', t.pos, 200, 8.0);"
      ]
    },
    {
      "type": "damage_obb",
      "obbName": "attack_area",
      "damage": "q.move_damage",
      "expressions": [
        "q.damage_all(q.move_damage);"
      ]
    },
    {"type": "set_vulnerable", ...},
    {"type": "remove_holds", "holds": ["effects"]},
    {"type": "pause", "pause": 1.5}
  ]
}

When to Edit:

Creating new custom moves
Adjusting attack timing
Changing OBB shapes/sizes
Modifying telegraph duration
Tweaking vulnerability windows
Updating MoLang scripts

See: Action Effects → | Server MoLang →

Configuration Loading Pipeline

graph TD
    A[Fight Manifest
fights/raichu.json] --> B[Load moveSet: 'raichu']
    A --> C[Load phaseSet: 'raichu']
    A --> D[Load behaviour: 'raichu']

    B --> E[Move Set
moves/raichu.json]
    C --> F[Phase Set
phases/raichu.json]
    D --> G[Behaviour
behaviour/raichu.json]

    E --> H[TitanFightManager]
    F --> H
    G --> H

    H --> I[TitanComponent
Runtime]

    E -.->|actionEffect refs| J[ActionEffect Timelines
world/datapacks/your_pack/data/titan/action_effects/]
    J -.-> I

    style A fill:#4a9eff
    style E fill:#e67e22
    style F fill:#e67e22
    style G fill:#e67e22
    style J fill:#9b59b6
    style I fill:#2ecc71

Fight Manifest loaded when Titan created (/titan create)
Move Set loaded from moveSet ID
Phase Set loaded from phaseSet ID
Behaviour loaded from behaviour ID (or default)
TitanFightManager assembles complete configuration
TitanComponent orchestrates runtime behavior
ActionEffects loaded on-demand when moves execute

Configuration Workflow

Initial Setup (First Time)

Install Titan - Place JAR in mods/
Start Server - Configs auto-generate in config/titan/
Test Default - Try pre-configured Titans
Customize - Edit configs for your server

Creating a New Titan

Option 1: Use Defaults

{
  "pokemonProperties": "pidgey",
  "name": "Sky Titan Pidgey",
  "moveSet": "core",
  "phaseSet": "default_titan",
  "behaviour": "default"
}

Uses shared configs - no custom files needed!

Option 2: Full Custom

{
  "pokemonProperties": "garchomp",
  "name": "Earthquake Titan Garchomp",
  "moveSet": "garchomp",
  "phaseSet": "garchomp",
  "behaviour": "garchomp"
}

Create custom move/phase/behaviour files

Option 3: Mix & Match

{
  "pokemonProperties": "gengar",
  "name": "Shadow Titan Gengar",
  "moveSet": "gengar",
  "phaseSet": "default_titan",
  "behaviour": "default"
}

Custom moves, generic phases/behaviour

Typical Editing Flow

graph LR
    A[Edit Move Set] --> B[/titan reload]
    B --> C[Test Moves]
    C --> D{Good?}
    D -->|No| A
    D -->|Yes| E[Edit Phase Set]
    E --> F[/titan reload]
    F --> G[Test Phases]
    G --> H{Good?}
    H -->|No| E
    H -->|Yes| I[Edit ActionEffects]
    I --> J[/titan reload]
    J --> K[Test Attacks]
    K --> L{Good?}
    L -->|No| I
    L -->|Yes| M[Done!]

Quick Iteration

For fast testing:

Keep server running
Edit config file(s)
Run /titan reload
Spawn new Titan to test
Repeat

Tip: Existing Titans keep old config. Spawn fresh ones to test changes.

Using Core Moves

Multiple Titans can share the core move set:

config/titan/moves/core.json:

{
  "moves": {
    "generic_slash": {
      "name": "Titan Slash",
      "cooldown": "100",
      "range": "5.0",
      "damage": "10.0",
      "damageType": "PHYSICAL",
      "actionEffect": "titan:generic_slash",
      "weight": 1.0
    },
    "titan_roar": { ... }
  },
  "selectionStrategy": "WEIGHTED_RANDOM"
}

Usage in multiple fights:

{
  "pokemonProperties": "machamp",
  "moveSet": "core"  // ← Shared moves
}

// fights/primeape.json
{
  "pokemonProperties": "primeape",
  "moveSet": "core"  // ← Same moves
}

Using Default Phases

The default_titan phase set provides a generic 3-phase progression:

{
  "pokemonProperties": "snorlax",
  "moveSet": "snorlax",
  "phaseSet": "default_titan",  // ← Generic phases
  "behaviour": "default"
}

Extending Configurations

You can’t directly extend configs, but you can copy and modify:

Copy core.json → custom_melee.json
Add custom moves to custom_melee.json
Reference "moveSet": "custom_melee"

Configuration Priority

Fight Config Matching

Fight configs match by pokemonProperties:

// Most specific (form + level)
"pokemonProperties": "charizard form=mega_x level=80+"

// Medium specific (form only)
"pokemonProperties": "charizard form=mega_x"

// Least specific (species only)
"pokemonProperties": "charizard"

Titan uses the most specific match.

ActionEffect Resolution

ActionEffects load from:

Data packs (highest priority)
Mod resources (fallback)

To override default ActionEffects:

Extract from JAR if needed
Place in data pack: world/datapacks/your_pack/data/titan/action_effects/
Edit as needed
Reload: /titan reload

Default Configurations

Titan includes 33 pre-configured Titans:

Fully Enhanced (12)

Charizard, Raichu, Ceruledge, Mewtwo, Gyarados
Gengar, Dragonite, Rayquaza, Lucario, Pikachu
Alakazam, Blastoise

Each with:

10-15 custom moves
3 phases with movement overrides
Cobblemon snowstorm particles
Complete ActionEffect timelines
Movement controller progression

Basic Configs (21)

Articuno, Salamence, Garchomp, Arcanine, Raikou
And 16 more…

Each with:

Basic move definitions
3 phases with default progression
Standard ActionEffects

Customization Levels

Level 1: Stat Tweaks (Easy)

Edit move sets:

Change damage values
Adjust cooldowns
Modify move weights
Tweak health ranges

No ActionEffect editing needed.

Level 2: Move Pool Changes (Medium)

Edit phase sets:

Add/remove moves from phases
Change movement patterns
Adjust stat modifiers
Add phase scripts

Uses existing ActionEffects.

Level 3: Movement Patterns (Medium-Advanced)

Edit phase sets with movementOverrides:

Configure teleport parameters
Adjust hit-and-run timing
Tune kiting distances
Set flying controller behavior

See: Movement Controllers →

Level 4: Custom ActionEffects (Advanced)

Create new attack timelines:

Design OBB hitboxes
Set telegraph timings
Configure vulnerability windows
Write MoLang scripts
Add Cobblemon particles

Requires ActionEffect & MoLang knowledge.

See: Server MoLang →

Level 5: State Machine AI (Expert)

Build complex AI behavior in behaviour configs:

Define custom states
Create transitions
Write MoLang conditions
Design multi-state patterns

Requires advanced MoLang scripting.

See: State Machines →

Configuration Backup

Before Major Changes

# Backup all Titan configs
cp -r config/titan config/titan.backup

# Backup data pack
cp -r world/datapacks/your_pack world/datapacks/your_pack.backup

Version Control

Recommended for servers:

git init
git add config/titan/
git add world/datapacks/your_pack/data/titan/
git commit -m "Initial Titan configs"

Track changes over time for easy rollback.

Troubleshooting

Config Not Loading

Symptoms: Changes don’t apply in-game

Fixes:

Run /titan reload after editing
Check logs for JSON errors
Verify file is in correct location (config/titan/)
Ensure JSON is valid (use validator)
Check referenced IDs exist (moveSet, phaseSet, behaviour)

Referenced Config Not Found

Symptoms: ERROR: Move set 'raichu' not found

Fixes:

Verify file exists at config/titan/moves/raichu.json
Check ID matches exactly (case-sensitive)
Ensure JSON is valid
Check file extension is .json

ActionEffect Not Found

Symptoms: ERROR: ActionEffect 'titan:move_name' not found

Fixes:

Check actionEffect value in move config
Verify file exists at world/datapacks/your_pack/data/titan/action_effects/move_name.json
Ensure file extension is .json
Check data pack is loaded

Titan Not Applying Config

Symptoms: Existing Titans keep old behavior

Fixes:

Spawn fresh Titan after /titan reload
Existing Titans cache old config
Remove and respawn to test changes

JSON Syntax Errors

Symptoms: ERROR: Failed to parse titan config

Fixes:

Check for missing commas
Verify bracket matching
Remove trailing commas
Use JSON validator online
Check quotes (double quotes ", not single ')

Best Practices

Naming Conventions

Fight Configs: pokemon_name.json

charizard.json
raichu.json
ceruledge.json
vulpix_alolan_true.json

Move Sets: Match fight name

charizard.json
raichu.json

Phase Sets: Match fight name

charizard.json
raichu.json

ActionEffects: pokemon_move_name.json

raichu_gigavolt_havoc.json
ceruledge_armor_oblivion.json
raichu_thunderstrike.json

Organization

Keep related configs together:

fights/raichu.json → moves/raichu.json → phases/raichu.json → behaviour/raichu.json

Use descriptive comments:

{
  "_comment": "Titan Raichu v3.0 - Rebalanced for 4-player groups",
  "_author": "YourName",
  "_last_updated": "2025-10-18",
  "pokemonProperties": "raichu",
  ...
}

Reusability

Create shared configs:

core.json - Generic moves
default_titan.json - Standard phases
default.json - Standard behaviour

Reference in multiple fights for consistency.

Migration from Old System

Old Format (Deprecated)

{
  "pokemonProperties": "charizard",
  "name": "Inferno Titan Charizard",
  "moves": { /* all moves embedded */ },
  "phases": [ /* all phases embedded */ ],
  "selectionStrategy": "WEIGHTED_RANDOM"
}

New Format

fights/charizard.json:

{
  "pokemonProperties": "charizard",
  "name": "Inferno Titan Charizard",
  "moveSet": "charizard",
  "phaseSet": "charizard",
  "behaviour": "charizard"
}

moves/charizard.json: (moves object + strategy) phases/charizard.json: (phases array) behaviour/charizard.json: (movement + aggression)

See: Fight Configurations → for migration details

Next Steps

Fight Manifests

Learn the new manifest format

Fight Configurations →

Move Sets

Define moves with 15 properties

Move Sets →

Phase Sets

Configure multi-phase progression

Phases →

Interactive Builder

Visual config editor

Fight Config Builder →

Master the modular config system to build reusable, composable boss fights!

Configuration Overview

Configuration Overview

New Modular Architecture

Benefits

File Structure

Configuration Types

1. Fight Manifests (config/titan/fights/*.json)

2. Move Sets (config/titan/moves/*.json)

3. Phase Sets (config/titan/phases/*.json)

4. Behaviour Configs (config/titan/behaviour/*.json)

5. ActionEffect Timelines (world/datapacks/your_pack/data/titan/action_effects/*.json)

Configuration Loading Pipeline

Configuration Workflow

Initial Setup (First Time)

Creating a New Titan

Typical Editing Flow

Quick Iteration

Configuration Sharing

Using Core Moves

Using Default Phases

Extending Configurations

Configuration Priority

Fight Config Matching

ActionEffect Resolution

Default Configurations

Fully Enhanced (12)

Basic Configs (21)

Customization Levels

Level 1: Stat Tweaks (Easy)

Level 2: Move Pool Changes (Medium)

Level 3: Movement Patterns (Medium-Advanced)

Level 4: Custom ActionEffects (Advanced)

Level 5: State Machine AI (Expert)

Configuration Backup

Before Major Changes

Version Control

Troubleshooting

Config Not Loading

Referenced Config Not Found

ActionEffect Not Found

Titan Not Applying Config

JSON Syntax Errors

Best Practices

Naming Conventions

Organization

Reusability

Migration from Old System

Old Format (Deprecated)

New Format

Next Steps

1. Fight Manifests (`config/titan/fights/*.json`)

2. Move Sets (`config/titan/moves/*.json`)

3. Phase Sets (`config/titan/phases/*.json`)

4. Behaviour Configs (`config/titan/behaviour/*.json`)

5. ActionEffect Timelines (`world/datapacks/your_pack/data/titan/action_effects/*.json`)