Global Settings

Edit $profile:\CZAutoz_Heli\mod_config.json to change settings that apply to all helicopters on your server. As of v0.2.9 the file is organised into clear sections — logging, features (universal, applies in both flight modes), featuresSimple / featuresAdvanced (per-flight-mode profiles — see Flight Mode Profiles), gameplay, repair, refuel and extraModules. Each setting below is shown by its full path (for example featuresSimple.autoHoverEnabled). Admins and roles now live in their own file — see Admin Access. Delete this file and restart to regenerate it with all default values.

These settings are safe to adjust freely — they control gameplay features like cargo, repair, fuel warnings, logging, and server-wide toggles. Unlike the per-helicopter flight physics values, there is no risk of breaking flight behaviour by changing these.

Since v0.2.3, a mod update migrates mod_config.json in place along with every other config — new keys are added, removed keys cleaned up, and all your custom values are kept (originals are still backed up first to $profile:\CZAutoz_Heli\Backups\v<oldversion>_<date>\). Only when first moving from v0.2.2-or-earlier onto a v0.2.3+ build might a one-time re-apply be needed. Since v0.3.1, Smart Config Updates apply to the per-helicopter files and the flight-mode profiles here — untouched values adopt improved defaults automatically; customised values are always kept.

Editing these settings from the in-game Admin Panel applies them live (since v0.2.3) — every spawned helicopter and connected player updates instantly, no restart or reconnect. Only direct edits to the JSON config files need a server restart, since those are read on startup.

Extra Cargo Modules

Each extra module adds 1,000 inventory slots. Maximum 10 modules per helicopter.

Setting	Helicopter	Max total slots
`extraModules.md500`	MD500 Civilian	10,250
`extraModules.mh6`	MH-6 Little Bird	10,250
`extraModules.sa342m`	SA342M Gazelle	10,250
`extraModules.uh1h`	UH-1H Iroquois	10,500
`extraModules.blackhawk`	MH-60L Blackhawk	10,500
`extraModules.merlin`	AW101 Merlin	11,000
`extraModules.mh47g`	MH-47G Chinook	11,000

Setting	What it does	Default
`features.seatedCargoAccess`	`1` = crew can open extra cargo while seated. `0` = locked while seated.	`1`

Repair

All repairs require a CZ_HelicopterRepairKit held in hands and the engine off — unless the main rotor is destroyed, which waives the engine-off rule for every zone. The helicopter must also be low enough: within 3 m of the ground for rotor repairs, 5 m for the airframe zones.

Setting	What it does	Default
`repair.kitUses`	Number of repairs a kit can perform before going ruined.	`5`
`repair.rotorRepairTime`	Hold time in seconds to repair a rotor.	`45`
`repair.zoneRepairTime`	Hold time in seconds to repair a body/engine/chassis/fuel zone.	`30`
`repair.globalHpPct`	Global HP fraction added per repair (0.10 = +10% global HP per action).	`0.10`

Zone repair is progressive — one hold repairs one damage level. Full repair of a heavily damaged zone may require multiple holds.

Clamped on load. repair.kitUses, repair.rotorRepairTime and repair.zoneRepairTime are each floored at 1 when the config is read — a 0 or negative value is raised to 1 rather than disabling the feature.

Refuelling

Controls how much fuel each container type adds and how quickly it drains during the refuel action.

Refuel Amounts

The amount of fuel added is expressed as a fraction of the helicopter’s total tank capacity — so the same setting applies consistently regardless of which helicopter is being refuelled.

Setting	What it does	Default
`refuel.canisterPct`	Fraction of tank added per full `CanisterGasoline` (jerry can). `0.10` = 10% per can, 10 cans to fill any helicopter.	`0.10`
`refuel.drumPct`	Fraction of tank added per full `CZ_HeliDrum`. `0.50` = 50% per drum, 2 drums to fill any helicopter from empty.	`0.50`
`refuel.bottlePct`	Fraction of tank added per full `Bottle_Base` item (water bottles, glass bottles, etc.).	`0.005`
`refuel.defaultPct`	Fraction of tank added per full unrecognised container (catch-all for modded fuel items).	`0.005`

Refuel Drain Speed

Controls how fast the container empties during the refuel action. Higher values drain the container faster, reducing the wall-clock time to complete a fill.

Setting	What it does	Default
`refuel.canisterRate`	Drain speed multiplier for `CanisterGasoline`. `1.0` = ~40 s for a full can. `2.0` = ~20 s.	`1.0`
`refuel.drumRate`	Drain speed multiplier for `CZ_HeliDrum`. Default `5.0` makes a full drum take the same wall-clock time as a full canister despite holding 5× the fuel.	`5.0`
`refuel.bottleRate`	Drain speed multiplier for `Bottle_Base` items.	`1.0`
`refuel.defaultRate`	Drain speed multiplier for unrecognised containers (catch-all).	`1.0`

Clamped on load. Every refuel.*Pct is clamped to 0.001–1.0, and every refuel.*Rate is floored at 0.01 — so a fill can never be set to zero or to more than one full tank per container.

Fuel-station refuelling (v0.3.0) needs no container and has no config keys — land within ~12 m of a working pump, walk to the fuel cap with empty hands, and hold F for a full tank in ~100 s. See HUD & Fuel.

Thresholds & Toggles

Setting	What it does	Default
`gameplay.fuelWarnThreshold`	Fuel fraction at which warning beeps begin. `0.20` = starts at 20% remaining.	`0.20`
`gameplay.playerCrashDamageMax`	Max HP damage to crew per hard impact (requires `damage.playerCrashDamageEnabled = 1` in the helicopter’s config).	`75`
`gameplay.engineHoldTime`	Hold duration in seconds for the Start Engine and Stop Engine action circles. Clamped on load to 0.1–10.0.	`1.0`
`features.rotorBladeShear`	`1` = rotor blades shear off on geometry contact (trees, buildings, terrain). `0` = no shear.	`1`
`features.rotorDiscCollision`	`1` = spinning rotor disc has physical collision. `0` = no disc collision.	`1`
`features.rotorPlayerKillEnabled`	`1` = players entering a spinning rotor disc are instantly killed. `0` = disabled.	`1`
`features.cabinModeEnabled`	`1` = Cabin Mode enabled. `0` = disabled server-wide for all helicopters. Fully reworked and ON by default since v0.2.8.	`1`
`features.detachRuinedParts`	`1` = ruined doors/parts fall off the airframe. `0` = they stay attached.	`0`
`features.freeLookAlwaysOn`	`1` = the seated camera free-orbits at all times (free look permanently on). `0` = the camera stays locked behind the aircraft and a single press of Left Alt toggles free look (v0.3.6 behaviour).	`0`
`features.doorAction3rdPerson`	`1` = the seated door open/close action also appears in 3rd-person view. `0` = 1st-person only.	`0`
`features.slingloadEnabled`	`1` = sling loading is available. `0` = disabled server-wide — the hook-up and release actions never appear on any helicopter, whatever `sling.maxKg` is set to.	`1`
`features.slingRespectLocks`	New in v0.4.1. `1` = a locked vehicle refuses the sling hook. Before attaching, the mod asks whichever lock mod the server runs — MuchCarKey, Trader, TraderPlus and Expansion are all understood — so a helicopter cannot lift a car straight around its lock. `0` = locks are ignored and anything within the lift class can be hooked. Shown in the Admin Panel as Sling: Respect Vehicle Locks.	`1`
`features.abandonedLandingDelay`	New in v0.4.1. Seconds an airborne helicopter with nobody aboard may hover before it descends and lands itself on safe ground — so an abandoned auto-hovering aircraft is recoverable instead of hanging in the sky until it is lost. `0` = disabled (abandoned helicopters hover indefinitely, pre-v0.4.1 behaviour). Overhauled in v0.4.2 — it now flies to the nearest verified-clear ground like a pilot (nose-first, terrain- and obstacle-aware), keeps well clear of the waterline, crosses to shore when abandoned over water, and lands with a single committed descent.	`120`
`features.autoPilotEnabled`	New in v0.4.2. `1` = pilots can press `P` in the pilot seat to open the Autopilot destination map and have the helicopter fly itself there — see Autopilot. `0` = disabled for everyone. Shown in the Admin Panel as Auto Pilot (map destination).	`1`
`features.autoPilotAutoLand`	New in v0.4.2. `1` = the autopilot also lands at the destination where safe — verified clear ground only, gentle committed descent, engine left running; with no safe ground nearby it holds hover and says so. `0` = arrival holds hover and landing stays manual. Shown in the Admin Panel as Auto Pilot Lands At Destination.	`0`
`features.autoPilotAutoTakeOff`	New in v0.4.2. `1` = the autopilot owns the whole departure — engaged on the pad it starts the engine if it is off, holds the aircraft on its wheels until the rotor reaches full flying speed, lifts off and climbs to a safe height before setting off. `0` = engaging from the ground is refused with a notice; the helicopter must already be airborne with the engine running before `P` will take it. Shown in the Admin Panel as Auto Pilot Takes Off From Ground.	`0`
`features.damageZonePanelEnabled`	`1` = the in-cockpit damage HUD panel is shown to the crew. `0` = hidden.	`1`
`features.isaAirDensity`	Air-density lift falloff with altitude (ISA model). `0` = off — lift is unaffected by altitude density. `1` = realistic (roughly 9% lift lost per 1,000 m of altitude). Above `1` exaggerates the effect. Clamped to `0`–`3`, and the falloff never takes lift below 20% however high you fly.	`1.0`

The features block holds the universal features — they apply no matter which flight mode the server runs. Flight-feel and difficulty features live in the per-mode profiles below.

Flight Mode Profiles (Simple / Advanced)

New in v0.2.9: the flight-feel features are split into two profiles — featuresSimple and featuresAdvanced. The server’s gameplay.flightMode picks which profile is live, so you can pre-configure two personalities once (for example: assists on and calm skies in Simple; wind, harsh VRS and no auto-hover in Advanced) and swap the whole set by flipping the flight mode — including live from the Admin Panel. On first boot after updating, both profiles are seeded automatically from your existing features values, so behaviour is unchanged until you deliberately edit one profile.

Setting	What it does	Default
`gameplay.flightMode`	`"Simple"` or `"Advanced"` — selects the flight model feel and which feature profile below is live.	`"Simple"`
`featuresSimple.autoHoverEnabled` / `featuresAdvanced.autoHoverEnabled`	`1` = Autohover works normally in that mode. `0` = disabled (`X` key does nothing).	`1`
`featuresSimple.autoHoverOnExit` / `featuresAdvanced.autoHoverOnExit`	`1` = Autohover automatically engages when the pilot exits their seat while airborne — the helicopter holds position until a new pilot boards. `0` = the helicopter is left uncontrolled.	`1`
`featuresSimple.autoShutdownOnExit` / `featuresAdvanced.autoShutdownOnExit`	Moved here in v0.4.1 (previously a single `features.autoShutdownOnExit`) so each flight mode can behave differently — existing configs migrate automatically, with both modes inheriting your old value. `1` = the engine shuts off when the pilot exits their seat close to the ground (within ~3.4 m). Pairs cleanly with `autoHoverOnExit`, which only engages from ~3.5 m up, so the two never fight over the same exit. `0` = disabled.	`0`
`featuresSimple.windPhysicsEnabled` / `featuresAdvanced.windPhysicsEnabled`	New in v0.2.9. `1` = the world’s live wind physically pushes the aircraft (strength follows the weather). `0` = off.	`0`
`featuresSimple.windStrength` / `featuresAdvanced.windStrength`	Wind force multiplier when wind physics is enabled. The `0`–`3` range is the Admin Panel slider’s range, not a config clamp — on load the value is only floored at `0`, so a direct JSON edit can go above `3`.	`1.0`
`featuresSimple.groundFlipRecovery` / `featuresAdvanced.groundFlipRecovery`	`1` = pressing `X` flips a tipped-over helicopter upright — works from any tipped attitude past ~70° (side-rest and nose-over included, v0.3.0) while on the ground and effectively stationary. `0` = disabled.	`0`
`featuresAdvanced.vrsEnabled`	Advanced only. `1` = Vortex Ring State — descending too fast into your own downwash costs lift. `0` = off.	`1`
`featuresAdvanced.vrsSeverity`	Maximum lift loss in a fully developed VRS (`0`–`1`).	`0.22`
`featuresAdvanced.vrsOnsetDescent`	Descent rate in m/s at which VRS begins.	`6.0`
`featuresAdvanced.blowback`	Advanced only. Nose-up tendency as airspeed builds (signed — flip to reverse).	`0.08`
`featuresAdvanced.antiTorque`	Advanced only. Collective-to-yaw coupling — pulling collective kicks the nose (signed — flip for opposite-rotation rotors).	`0.04`

VRS, blowback and anti-torque exist only in featuresAdvanced — the flight model never applies them in Simple mode, so they have no Simple twin.

Defaults retuned in v0.3.0 (blowback 0.35 → 0.08, antiTorque 0.12 → 0.04, vrsSeverity 0.40 → 0.22) after the Advanced model’s first full flight-testing pass — and blowback and anti-torque are now hard-capped in flight at 25% of the pilot’s own control authority, so no configured value can overpower the pilot. Config migration keeps your stored values: a server that generated its config on v0.2.9 still carries the old numbers. To adopt the new tuning, reset those three rows in the Admin Panel (applies live) or edit mod_config.json and restart.

Admin Access — Roles & Permissions

As of v0.2.9, admins and roles live in their own file — CZAutoz_Heli/permissions_admins_config.json, next to mod_config.json in your server profile — so a mod-config save can never touch admin data and vice-versa. Existing admins are migrated out of mod_config.json automatically on first boot — nothing to do.

Setting	What it does	Default
`whitelistRetryMinutes`	How often (in minutes) the server re-checks the whitelist if the first check fails. Clamped on load to 5–60.	`15`
`entries`	Array of admins. Each entry is a `steamID64` plus the `role` they hold — an admin’s abilities come entirely from their role.	placeholder owner
`roles`	The role definitions. Each is a `name` plus its list of permission keys. Seeded with the built-in `owner` (`all`) and `admin` roles.	`owner`, `admin`

{
  "whitelistRetryMinutes": 15,
  "entries": [
    { "steamID64": "76561198012345678", "role": "owner" }
  ],
  "roles": [
    { "name": "owner", "permissions": ["all"] },
    { "name": "admin", "permissions": ["mod.config.view", "heli.config.view", "heli.list.view", "..."] }
  ]
}

The built-in owner role always has every permission and can never be locked out; every other role has exactly the keys you grant it — including mod.config.edit and heli.config.edit if you choose to hand those out. Tabs a role can’t view are hidden; action buttons a role can’t use show a “Permission Declined” dialog naming the missing key. The full guide — every permission key, the built-in roles, creating staff roles, and the safety rails — lives on the Admin Panel & Permissions page.

Logging

Setting	What it does	Default
`logging.CZAutoz_logDebug`	`1` = verbose debug output written to a daily file at `$profile:\CZAutoz_Heli_debug_YYYY-MM-DD.log`. Only enable when troubleshooting — do not leave on in production.	`0`
`logging.CZAutoz_logActivity`	`1` = all player helicopter events logged to a daily file at `$profile:\CZAutoz_Heli_activity_YYYY-MM-DD.log`. Each entry includes the player’s display name and Steam GUID. Recommended to enable on all servers.	`0`
`logging.CZAutoz_logPhysics`	`1` = physics/flight diagnostics written to their own daily file at `$profile:\CZAutoz_Heli_physics_YYYY-MM-DD.log`, for tuning and flight-issue investigation. Leave off in production.	`0`

All three logs are date-stamped and roll over daily — a new file is opened when the server date changes, so nothing grows without bound.

Activity Log Events

The activity log is designed as an admin tool for investigations, compensation, and dispute resolution. Every significant player interaction with a helicopter is recorded with a precise timestamp, player display name, and Steam GUID — giving you a complete, chronological picture of exactly what happened, who was involved, and when. Common admin use cases:

Combat logging — confirm whether a player left a helicopter mid-fight or mid-pursuit
Theft and griefing — identify who took a helicopter, who was flying it, and what was removed from cargo
Compensation requests — verify whether a crash was caused by server-side damage, a rotor shear, or pilot error before compensating
Dispute resolution — cross-reference a player’s account of events against the timestamped log
Rotor kills — confirm who was piloting when a player was killed by a rotor disc, including both victim and pilot GUIDs

When logging.CZAutoz_logActivity = 1, every event is recorded with a timestamp, the helicopter classname, and the player’s display name and Steam GUID where applicable. All seat, engine, and physics events also include the helicopter’s world position (X/Z coordinates) at the time of the event.

Helicopter Presence

Event	What is logged
`HELI_SPAWNED`	Fires once on the first server tick for each helicopter — helicopter classname and world position. Covers persisted, mission-spawned, and admin-spawned helicopters
`HELI_DELETED`	Helicopter classname, world position, and the last pilot’s name — fires when a helicopter is removed (admin delete, cleanup, despawn)
`PHYSICS_INIT`	Technical one-liner per helicopter as its physics body initialises (classname, simulation rate)
`RESTART_SNAP`	After a server restart, how each persisted helicopter that was mid-air was placed — the line names the mode (settled to the ground, or restored to its held hover) and the position
`PHYS_RECOVER`	A helicopter’s physics state was automatically recovered after an engine-level fault

Engine

Event	What is logged
`ENGINE_START`	Player name, GUID, helicopter type, world position — fires when the start is initiated
`ENGINE_RUNNING`	Player name, GUID, helicopter type — fires when the spool-up completes and the engine reaches full power (v0.3.0 — previously logged as a second `ENGINE_START` line)
`ENGINE_STOP`	Player name, GUID, helicopter type, world position
`ENGINE_FAILSAFE`	A start that could not complete was safely wound down
`AUTO_SHUTDOWN`	Engine shut down automatically because the pilot exited on the ground — player name, GUID, helicopter type (requires `autoShutdownOnExit = 1` in the active flight-mode profile)
`ENGINE_DEAD`	The engine damage zone was destroyed — helicopter type, plus the pilot’s name and GUID
`BATTERY_DEAD`	The battery reached 0 charge and the lights were forced off — helicopter type

Seats

Event	What is logged
`PILOT_ENTER`	Player name, GUID, helicopter type, world position
`PILOT_EXIT`	Player name, GUID, helicopter type, world position — fires on any live exit, including a mid-flight disconnect (the combat-log signal)
`PILOT_KILLED`	Player name, GUID, helicopter type, world position (body detected in seat with `IsAlive() = false`)
`COPILOT_ENTER`	Player name, GUID, helicopter type, world position
`COPILOT_EXIT`	Player name, GUID, helicopter type, world position — fires on any live exit, including disconnects
`COPILOT_KILLED`	Player name, GUID, helicopter type, world position
`CARGO_ENTER`	Player name, GUID, seat index, helicopter type, world position
`CARGO_EXIT`	Player name, GUID, seat index, helicopter type, world position — fires on any live exit, including disconnects
`CARGO_KILLED`	Player name, GUID, seat index, helicopter type, world position

Cabin Mode

Event	What is logged
`CABIN_ENTER`	Player name, GUID, origin seat index, helicopter type
`CABIN_EXIT`	Player name, GUID, destination seat index, helicopter type

PvP Kill Detection

Event	What is logged
`CREW_KILLED_BY_PLAYER`	Victim name + GUID, killer name + GUID, kill context (`seat 0`/`seat 1`/`seat 2+`, `cabin walk`, `on deck`, `free walk`), helicopter type, world position. Only fires when the killer is another player — environment and crash deaths are covered by `PILOT_KILLED`, `CARGO_KILLED`, and `CREW_CRASH_DAMAGE`

Combat & Damage

Event	What is logged
`CREW_CRASH_DAMAGE`	Fires for each crew member who takes damage in a hard impact — player name, GUID, exact damage value, helicopter type, world position
`CRASH`	Pilot name, GUID, impulse value, hit zone, helicopter type, world position
`WATER_SLAM`	Pilot name, GUID, impact speed (m/s), helicopter damage, player damage dealt, world position
`ROTOR_KILL`	Victim name + GUID, pilot name + GUID, helicopter type
`ROTOR_DEAD`	Which rotor (main/tail), pilot name + GUID, helicopter type
`ROTOR_SHEAR`	Which rotor (main/tail), pilot name + GUID, helicopter type
`FUEL_EMPTY`	Pilot name + GUID, helicopter type
`DESTROYED`	Killer name + GUID (or `environment` if not a player), pilot name + GUID, helicopter type, world position
`WRECK_FIRE`	Wreck-fire state changes on a destroyed helicopter — classname, world position
`LINKED_CRASH_DAMAGE`	Crash damage applied to a cabin walker or deck-linked player — name, GUID, damage value, helicopter type
`ANTI_LAGDEATH`	A physics-spike impact was voided by the lag-death guard instead of damaging the crew

Flight Systems

Event	What is logged
`AUTOHOVER_ON`	Pilot name, GUID, hold altitude (m), helicopter type
`AUTOHOVER_OFF`	Pilot name, GUID, helicopter type
`AUTOHOVER_ON_EXIT`	Autohover engaged automatically because the pilot exited in flight or moved to the cabin — pilot name, GUID, helicopter type
`FLIP_RECOVERY`	Player name, GUID, helicopter type (requires `groundFlipRecovery = 1` in the live flight-mode profile)
`SLING`	Sling-load activity — `attached` (load classname, its mass in kg, helicopter type, rope length), `released` (load classname, helicopter type, the reason for release) and `winch` (helicopter type, the new rope length in m)

Maintenance & Repairs

Event	What is logged
`REFUEL`	Player name, GUID, fuel percentage after fill, helicopter type
`REFUEL_PARTIAL`	As `REFUEL`, for a container fill released before completing
`REFUEL_STATION`	Player name, GUID, helicopter type — tank filled to full at a fuel station (v0.3.0)
`REFUEL_STATION_PARTIAL`	Player name, GUID, fuel percentage reached, helicopter type — station fill released early (v0.3.0)
`ZONE_REPAIR`	Player name, GUID, zone repaired (body/engine/chassis/fuel), helicopter type
`ROTOR_REPAIR`	Player name, GUID, which rotor (main/tail), helicopter type
`ITEM_ATTACHED`	Item classname, slot name, helicopter type. The acting player cannot be identified at the engine level
`ITEM_DETACHED`	Item classname, slot name, helicopter type. The acting player cannot be identified at the engine level

Lights & Controls

Event	What is logged
`SPOTLIGHT`	Pilot name, GUID, new state (ON/OFF), helicopter type
`NAV_LIGHTS`	Pilot name, GUID, new state (ON/OFF), helicopter type
`WINDOW`	Player name, GUID, which window (left/right), new state (OPENED/CLOSED), helicopter type
`RAMP`	Player name, GUID, new state (opened/closed), helicopter type
`LANDING_GEAR`	Player name, GUID, new state (deployed/retracted), helicopter type

Admin & Spawning

Every Admin Panel action is logged with the acting admin’s name and GUID:

Event family	What is logged
`ADMIN_PANEL` / `ADMIN_PANEL_<ACTION>`	Every panel command — `TELEPORT`, `REPAIR`, `REFUEL`, `DELETE`, `REPAIR_ALL`, `REFUEL_ALL`, `DELETE_EMPTY` — plus denied and unauthorised attempts (`ADMIN_PANEL_DENIED`, `ADMIN_PANEL_NONADMIN`, flood protection)
`SPAWN` / `SPAWN_REJECT`	Admin helicopter spawns — classname, position, acting admin; rejects include the reason
`PRESET_SPAWN` / `PRESET_SAVE` / `PRESET_DELETE`	Loadout-preset activity from the panel, plus their `_REJECT` twins
`ADMIN_ADD` / `ADMIN_REMOVE` / `ADMIN_EDIT` / `ADMIN_GRANT_LIVE` / `ADMIN_REVOKE_LIVE`	Role and permission changes made from the panel, including denied attempts
`CONFIG_RELOAD`	Config reload triggered from the panel

We strongly recommend enabling activity logging on all servers. It has no meaningful performance impact and gives you the full picture you need to handle compensation requests, combat log reports, theft disputes, and any helicopter-related staff situation confidently and fairly. Without it, you are relying entirely on player accounts of what happened.This mod logs all helicopter-specific interactions, but it does not cover general server-wide PvP kills. For complete kill accountability — including who shot who, with what weapon, and when — we recommend also running a dedicated PvP logging mod alongside this one. The two logs complement each other: helicopter activity records the context, a PvP logger records the kill chain.

Whitelist Log

Whitelist checks are always logged, regardless of logging.CZAutoz_logActivity — since v0.3.0 into the shared fleet whitelist log, the same date-stamped file the CZ Autoz vehicle mods write to:

File	Contents
`$profile:\CZAutoz_Whitelist_YYYY-MM-DD.log`	One `RESULT` line per product per check — `WHITELISTED`, `NOT REGISTERED`, `PORT MISMATCH`, or `COULD NOT VERIFY (NETWORK)` — with the detected IP and port. Appended, one file per day, self-trimming

See Common Issues for how to use it when troubleshooting.

Getting Started

The Fleet

Features

Server Configuration

More

Extra Cargo Modules

Repair

Refuelling

Refuel Amounts

Refuel Drain Speed

Thresholds & Toggles

Flight Mode Profiles (Simple / Advanced)

Admin Access — Roles & Permissions

Logging

Activity Log Events

Helicopter Presence

Engine

Seats

Cabin Mode

PvP Kill Detection

Combat & Damage

Flight Systems

Maintenance & Repairs

Lights & Controls

Admin & Spawning

Whitelist Log

​Extra Cargo Modules

​Repair

​Refuelling

​Refuel Amounts

​Refuel Drain Speed

​Thresholds & Toggles

​Flight Mode Profiles (Simple / Advanced)

​Admin Access — Roles & Permissions

​Logging

​Activity Log Events

​Helicopter Presence

​Engine

​Seats

​Cabin Mode

​PvP Kill Detection

​Combat & Damage

​Flight Systems

​Maintenance & Repairs

​Lights & Controls

​Admin & Spawning

​Whitelist Log

Extra Cargo Modules

Repair

Refuelling

Refuel Amounts

Refuel Drain Speed

Thresholds & Toggles

Flight Mode Profiles (Simple / Advanced)

Admin Access — Roles & Permissions

Logging

Activity Log Events

Helicopter Presence

Engine

Seats

Cabin Mode

PvP Kill Detection

Combat & Damage

Flight Systems

Maintenance & Repairs

Lights & Controls

Admin & Spawning

Whitelist Log