Repository navigation
FAQ
Common questions, known issues, and solutions for BS Patrol Helicopter.
$profile:BS_PatrolEvent/BS_HeliConfig.json
On most servers this translates to something like:
/path/to/your/server/profile/BS_PatrolEvent/BS_HeliConfig.json
The file is generated automatically on first server boot with the mod loaded.
Delete BS_HeliConfig.json and restart the server. A fresh config with default values will be generated.
The mod uses ConfigVersion to track config migrations. When a new mod version adds new config sections (like WreckSettings or MarkerSettings), it checks the version number and automatically adds missing sections if AutoUpdateConfig is 1. Do not manually change this value.
When set to 1 (default), the mod will automatically add new config sections to your JSON when you update the mod. The existing values you've customized are never overwritten — only new, previously-missing sections are added with their defaults.
Set to 0 if you want full manual control over the JSON file. New sections will still be loaded with defaults in memory, but the JSON file won't be modified.
Cause: The PatrolRoutes array is empty, or the spawn position coordinates are invalid.
Solution: Make sure you have at least one route with a valid SpawnPosition:
"PatrolRoutes": [
{
"RouteName": "My Route",
"SpawnPosition": "5213.19 390.0 9080.21",
"Waypoints": [
"4205.63 390.2 10859.44"
]
}
]
⚠️ Common mistake: Using commas in coordinates. The format must be"X Y Z"with spaces, not"X, Y, Z".
Check these in order:
-
Is the event enabled?
"EnableEvent": 1 -
Are there enough players? Check
MinPlayersToStart. The mod logs"Insufficient players (X/Y)"if the count is too low. -
Is a previous helicopter still active? The mod won't spawn a new one if the previous helicopter hasn't crashed yet. Check logs for
"Previous helicopter is still active". -
Check your spawn position. If it's
"0 0 0"or invalid, the helicopter can't be created. -
Check the server log for errors from
[BSPatrolModule].
- Make sure
PatrolRouteshas at least one route with validWaypoints. - Check that the waypoint coordinates are valid positions on your map.
- If using a custom map, make sure the coordinates are within the map boundaries.
The flight controller uses terrain detection and altitude smoothing to avoid this. However, if your waypoints are in extremely mountainous areas with steep elevation changes:
- Increase
PatrolAltitudein theDifficultysection (try100–150for mountainous terrain). - Space your waypoints further apart so the helicopter has time to adjust altitude.
- Make sure
LootCrateshas at least as many entries asCrateCount. - Check that
Presetsin each crate entry match the names of categories defined inLootCategories(case-sensitive). - If using LBMaster, verify the
LBPresetNamematches an existing preset. Check logs for"LB Preset 'X' NOT found".
- Verify that Expansion AI (
EXPANSIONMODAI) is installed and loaded on the server. - Check that
IsExpansionBotis set to1for bot entries. - Check logs for
"EXPANSIONMODAI not active. Ignoring bot". - Make sure the
ClassNameis a valid survivor class (e.g.,"SurvivorM_Hassan").
The mod uses raycasting to avoid this, but it can occasionally happen in dense areas. You can:
- Reduce
SpawnRadiusto keep defenders closer to the wreck (usually in open ground). - Accept that ~5% of spawns near buildings might clip slightly — they'll pathfind out.
- Markers require Expansion Navigation or LBMaster Groups to be installed.
- Check
MarkerSettings— make sure the relevant toggles are1. - Verify the integration mod is loaded (check for their entries in server logs).
It shouldn't — the wreck's OnStoreLoad method auto-deletes it on load. If you're seeing a persistent wreck:
- It may be a different object or mod creating it.
- Check if something else is re-saving the wreck to the storage file.
The mod logs to the standard DayZ server log (*.RPT file). Look for entries prefixed with:
| Prefix | Source |
|---|---|
| [BSPatrolModule] | Module lifecycle (spawn, retry, config loading) |
| [BS_FlightController] | Combat state changes, patrol transitions |
| [BS_Wreck] | Crate spawning, loot population |
| Defenders spawned: | Defender spawn summary |
| CrashedEvent: | LBMaster loot preset results |
Yes — BS Patrol Helicopter is a self-contained event. It doesn't modify any vanilla helicopter classes. It can coexist with vehicle mods, other helicopter events, or AI mods.
Yes, but you must configure your own PatrolRoutes with coordinates that are valid for your map. The default routes are for Chernarus.
Yes — the mod must be loaded on both server and client (it includes particle effects, sounds, models, and animations that are needed client-side).
-
Use
DespawnRadiusinCrashDefendersto clean up zombies/bots when players leave the area. -
Set
WreckDespawnTimeto auto-remove old crash sites. Without this, wreck effects (fire, smoke, lights) run until server restart. - Don't go overboard with defenders. 15–20 total is reasonable. 50+ zombies can cause server lag.
-
Increase
DespawnCheckIntervalif you have many active crash sites. The check is lightweight but runs on a timer. -
Use
RespawnTimeto control event frequency. Overlapping events (helicopter alive while wreck exists) are handled gracefully, but more events = more server load.