> For the complete documentation index, see [llms.txt](https://lng.gitbook.io/lng-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lng.gitbook.io/lng-docs/companion-mod/basics/profiles-lngcompanion-missions-missiontrial-json.md).

# profiles\LNGCompanion\Missions\MissionTrial.json

Here is the formatted GitBook page for your `MissionTrial.json` file.

Because this file shares a lot of DNA with the `KothConfig.json`, I focused the explanation on how Trials differ from KOTH (mostly that they are on-demand progression events, rather than fixed-location zone captures).

***

#### ⚔️ `MissionTrial.json` Overview

The `MissionTrial.json` file configures the Companion's personal Trial Events. Unlike KOTH, which occurs at specific map coordinates, Trials are dynamic, on-demand horde events that allow players to progress their personal storyline, unlock Vaults, and gain Slot Upgrades by surviving intense PvE encounters.

***

#### ⚙️ Core File Structure

| **Property**     | **Type** | **Description**                                                                                                                                                                  |
| ---------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Stages`         | `Array`  | The master list of progression stages (Stage 0 through 9). Each stage defines the specific boss fights and horde sizes a player must face to unlock their next Vault or UI Slot. |
| `ExpansionEvent` | `Object` | The primary boss fight players trigger to unlock their next physical Vault (e.g., expanding from Vault 1 to Vault 2).                                                            |
| `SlotEvent`      | `Object` | The secondary boss fights players trigger to unlock passive module slots in their Drone UI.                                                                                      |

***

#### 🧟 Event Configuration Variables

*These variables govern the flow, difficulty, and rewards of the specific Trial.*

**Event Flow & Timers**

| **Setting**              | **Type** | **Description**                                                                                             |
| ------------------------ | -------- | ----------------------------------------------------------------------------------------------------------- |
| `MissionCooldownSeconds` | `Int`    | Time between allowed Trial activations.                                                                     |
| `FirstLoginDelaySeconds` | `Int`    | How long to wait after server restart before a Trial can be initiated.                                      |
| `TrialDurationSeconds`   | `Int`    | How long the player must survive the horde to win the Trial.                                                |
| `DragonSpawnTimeSeconds` | `Int`    | Time (in seconds) after the event starts before the final Boss spawns.                                      |
| `SafeZoneCheckRadius`    | `Float`  | The radius checked to ensure the player isn't trying to exploit the Trial by starting it inside a Safezone. |

**Entities & Difficulty**

| **Setting**            | **Type** | **Description**                                                                                                              |
| ---------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------- |
| `TrialModuleHolder`    | `String` | The specific Zombie/Monster classname that spawns carrying the required activation module.                                   |
| `EventModuleClassname` | `String` | The item the player must loot from the holder and insert into the system to start it (e.g., `"LNG_EventModule_VaultCount"`). |
| `DragonClass`          | `String` | The exact Boss monster classname (e.g., `"MPG_Bear_2_3"`).                                                                   |
| `HordeClassnames`      | `Array`  | List of AI classnames that will continuously swarm the player during the survival phase.                                     |
| `MinZmb` / `MaxZmb`    | `Int`    | The minimum and maximum number of AI alive at once during the Trial.                                                         |

**Loot & Rewards**

| **Setting**        | **Type** | **Description**                                                                               |
| ------------------ | -------- | --------------------------------------------------------------------------------------------- |
| `ModuleReward`     | `String` | Specific reward item given upon clearing an `ExpansionEvent` (e.g., `"LNG_Module_Vault_x1"`). |
| `UpgradeItem`      | `String` | Specific slot upgrade card given upon clearing a `SlotEvent` (e.g., `"LNG_UpgradeCard_01"`).  |
| `RandomRewardPool` | `Array`  | The standard randomized loot table granted upon victory.                                      |

***

#### 💻 Example Configuration

Below is a condensed snippet showing how a Stage 0 Trial Expansion Event is structured.

JSON

```
{
    "Stages": [
        {
            "StageID": 0,
            "ExpansionEventActive": 1,
            "ExpansionEvent": {
                "MissionCooldownSeconds": 7200,
                "FirstLoginDelaySeconds": 300,
                "TrialModuleHolder": "PITSTOP_Monsters_Reaper",
                "SpawnTrialModuleHolderRadius": 50.0,
                "EventModuleClassname": "LNG_EventModule_VaultCount",
                "TrialDurationSeconds": 300,
                "DragonSpawnTimeSeconds": 150,
                "DragonClass": "MPG_Bear_2_3",
                "MinZmb": 8,
                "MaxZmb": 15,
                "HordeClassnames": [
                    "ZmbM_PatrolNormal_Autumn",
                    "ZmbM_usSoldier_normal_Woodland"
                ],
                "ModuleReward": "LNG_Module_Vault_x1",
                "RandomRewardPool": [
                    "Battery9V",
                    "DuctTape"
                ]
            },
            "SlotEventActive": 1,
            "SlotEvent1": {
                "EventModuleClassname": "LNG_EventModule_SlotCount",
                "TrialDurationSeconds": 300,
                "DragonClass": "MPG_Bear_2_3",
                "MinZmb": 1,
                "MaxZmb": 5,
                "UpgradeItem": "LNG_UpgradeCard_01",
                "RandomRewardPool": [
                    "Battery9V"
                ]
            }
        }
    ]
}
```

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://lng.gitbook.io/lng-docs/companion-mod/basics/profiles-lngcompanion-missions-missiontrial-json.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.