Repository navigation
Event Settings
The EventSettings block controls the master event lifecycle: whether the event runs, when helicopters spawn, minimum player requirements, and wreck cleanup timing.
"EventSettings": {
"EnableEvent": 1,
"MinPlayersToStart": 1,
"SpawnTime": 5,
"RespawnTime": 10,
"CrateBurningTime": 30,
"WreckDespawnTime": 0
}| Type | Boolean (1 / 0) |
| Default | 1 |
| Description | Master switch for the entire mod. When set to 0, no helicopter will ever spawn. Useful for temporarily disabling the event without removing the mod from your load order. |
Example — Disable the event:
"EnableEvent": 0| Type | Integer |
| Default | 1 |
| Description | The minimum number of online players required before a helicopter can spawn. If the player count is below this threshold when the spawn timer fires, the mod will automatically retry every 5 minutes until enough players are online. |
Tip: For high-population PvP servers, setting this to
5–10ensures the event only fires during active hours. For solo/testing servers, keep it at1.
Example — Require at least 5 players:
"MinPlayersToStart": 5What happens in the server logs when players are insufficient:
[BSPatrolModule] Insufficient players (3/5). Retrying in 5 minutes.
| Type | Integer (minutes) |
| Default | 5 |
| Description | Delay in minutes between server start (or mission start) and the first helicopter spawn. This gives the server time to boot up and players time to connect before the event begins. |
Example — First helicopter spawns 15 minutes after restart:
"SpawnTime": 15Example — Helicopter spawns almost immediately (for testing):
"SpawnTime": 1| Type | Integer (minutes) |
| Default | 10 |
| Description | Delay in minutes between each helicopter spawn after the first one. This timer starts as soon as the previous helicopter is created (not when it crashes or despawns). If a helicopter is still alive when the timer fires, the mod waits an additional 5 minutes before checking again — it will not spawn two helicopters at the same time. |
Important: The respawn timer counts from the moment the helicopter is created. So if the helicopter patrols for 8 minutes before being shot down and
RespawnTimeis10, the next helicopter will appear approximately 2 minutes after the crash.
Example — A new helicopter every 30 minutes:
"RespawnTime": 30Example — Rapid events for action-packed servers:
"RespawnTime": 10Example — Rare event (once per hour):
"RespawnTime": 60| Type | Integer (seconds) |
| Default | 30 |
| Description | How many seconds the loot crates remain on fire after the crash. While burning, players cannot open the crates — the crate name shows "Burning Crate" and the interaction action is blocked. The crates have a fire particle effect and sound during this time. This mechanic forces players to hold the crash site and creates PvP tension as other players arrive. |
Example — Crates burn for 2 minutes (high tension):
"CrateBurningTime": 120Example — Crates burn for 5 minutes (extreme PvP bait):
"CrateBurningTime": 300Example — Crates can be opened immediately (no burning):
"CrateBurningTime": 0| Type | Integer (minutes) |
| Default |
0 (disabled) |
| Description | How many minutes after crashing the wreck (and all its crates, defenders, effects, and map markers) will automatically despawn and be cleaned up. Set to 0 to disable auto-despawn — the wreck will persist until server restart. When the wreck despawns, a despawn notification is sent to all players if notifications are enabled. |
Note: The wreck is not persistent across server restarts. If the server restarts, any existing wreck is automatically deleted on load regardless of this setting.
Performance tip: On servers with frequent events, setting a reasonable despawn time (30–60 minutes) prevents accumulation of crash site effects (fire particles, smoke, lights, sounds) that can impact client performance over long sessions.
Example — Wreck disappears after 45 minutes:
"WreckDespawnTime": 45Example — Quick cleanup (20 minutes):
"WreckDespawnTime": 20Example — Wreck stays until restart (default):
"WreckDespawnTime": 0"EventSettings": {
"EnableEvent": 1,
"MinPlayersToStart": 10,
"SpawnTime": 20,
"RespawnTime": 60,
"CrateBurningTime": 180,
"WreckDespawnTime": 30
}This configuration:
- Requires 10 players online before the event starts
- First helicopter spawns 20 minutes after server restart
- A new helicopter spawns every hour
- Crates burn for 3 full minutes — plenty of time for PvP fights to develop
- Wreck auto-despawns after 30 minutes to keep the map clean
"EventSettings": {
"EnableEvent": 1,
"MinPlayersToStart": 1,
"SpawnTime": 5,
"RespawnTime": 15,
"CrateBurningTime": 15,
"WreckDespawnTime": 0
}This configuration:
- Starts with just 1 player — always active
- Helicopter spawns quickly after restart (5 min)
- Frequent respawns every 15 minutes
- Short burn time (15 seconds) — players can loot fast
- Wreck stays until server restart
"EventSettings": {
"EnableEvent": 1,
"MinPlayersToStart": 3,
"SpawnTime": 30,
"RespawnTime": 120,
"CrateBurningTime": 60,
"WreckDespawnTime": 90
}This configuration:
- Needs at least 3 players for the event to feel meaningful
- Long delay before first spawn (30 min) — gives RP time to develop
- Helicopter every 2 hours — feels like a rare, significant event
- Crates burn for 1 minute — moderate tension
- Wreck despawns after 90 minutes — crash site is a temporary landmark
"EventSettings": {
"EnableEvent": 1,
"MinPlayersToStart": 1,
"SpawnTime": 1,
"RespawnTime": 5,
"CrateBurningTime": 5,
"WreckDespawnTime": 10
}This configuration:
- 1 player, spawns in 1 minute, respawns every 5 minutes
- Minimal burn time for quick testing
- Wreck cleans up fast so you can test repeatedly