Server guide

Logs and troubleshooting

Most server problems show up in the logs with a clear prefix. This page lists where to look, what each prefix means and the usual fixes.

Where the logs are

Server: the script_*.log, RPT and crash logs in the profile folder (the -profiles directory). Central Economy errors also appear in the economy and RPT output.
Client: script and RPT logs, for prompts, controls and rendering. On Windows they're under %LOCALAPPDATA%\DayZ.

Log prefixes

`[RotorCraft] Loot entries`	Loot file check, about 15 seconds after start: `OK` or `missing for: ...`
`[RCESPAWN]`	Startup placement, nearby aircraft, rejected entries and blocked positions
`[RCEDATA]`	Aircraft settings loading, rejected fields and handling overrides
`[RCEDMG]`	Difficulty preset, effective limits, impacts and crew or airframe injuries
`[RCEWPN]`	Weapon settings problems
`[RCELIFE]`	Aircraft created, loaded, still here, killed and deleted, with position and lifetime
`[RCESTORE]`	Saved data rejected on load
`[RCEENGINE]`, `[RCEPARTS]`	Engine events, missing or ruined parts, empty-pilot shutdown
`[RCEROTOR]`, `[RCEHIT]`, `[RCEZONE]`	Rotor strikes and replacement, projectile hits, damage zones
`[RCEWRECK]`, `[RCEDEGRADE]`	Destruction, explosions, wreck retention, degradation
`[RCEFLIP]`	Flip checks and refusal reasons
`[RCEKEY]`	Ignition key settings, missing IDs, no room for a key
`[RCECOVER]`	Camo net covering and uncovering
`[RCELOG]`, `[RCEGAUGE]`, `[RCEPFD]`, `[RCEINPUT]`	Flight, instruments and controls (verbose lines need debug logging)
`[RCEWATER]`, `[RCECOPILOT]`, `[RCESEAT]`, `[RCETAB]`	Water, co-pilot takeover and boarding (need debug logging)

Turning on debug logging

Set "debugLogging": true at the top level of RotorCraft_Aircraft.json and restart. Or add -flyDebugLog to the server launch command; that overrides the file. To turn it off, set it to false and remove the launch flag, then restart. Clients get the setting from the server. Lifetime, error and many event lines are always logged.

Common problems

Players are kicked while loading in

Almost always a version mismatch. Players with a different mod version get kicked while loading in, so restart the server promptly after every update.

"Client is a newer build than the server": compare the DayZ game versions first, including stable versus experimental. Update the server installation you actually launch. If the message names a mod or PBO, update that mod instead.
Signature or mod mismatch: check the bikey is in the top-level keys folder, the PBO and its .bisign match, client and server have the same mod version, and there's no duplicate mod folder loaded. On Linux, check the case of the paths. Keep signature checking on.

No aircraft spawn

Wait at least 20 seconds after mission start.
Check RotorCraft_Spawns.json: enabled is 1, and the positions are for your map. Maps other than Nasdara start with no positions.
Another aircraft or wreck within 14 m blocks a position. So do slopes, water and obstructions.
If you use Central Economy events instead, check the events are active, the counts and player avoidance.

[RCESPAWN] gives the reason for each position; [RCELIFE] ... created confirms an aircraft appeared. See Aircraft spawns.

Players can't find blades, belts or ammo

The loot files aren't loaded. Look for [RotorCraft] Loot entries missing for: .... Check the rotorcraft mission folder, the two file names and the <ce folder="rotorcraft"> line in cfgeconomycore.xml, then restart. See Server setup.

The flip prompt appears, then stops

The player must stand upright, stay still, keep a healthy wrench in hand and stay in reach. The aircraft must be tilted enough, still, empty of living players and on reasonably level ground with room to turn over. The server checks again when the flip completes. [RCEFLIP] logs the reason, for example still moving, no room or ground too steep.

An aircraft disappeared

Work out whether it was ruined, cleaned up, moved or failed to load. Check [RCELIFE] lines (still here, killed by, deleted), [RCEWRECK] ... stays, and [RCESTORE] ... rejected saved data. Make sure the right mod version is loaded and the storage path hasn't changed. Don't wipe storage to diagnose it.

Remember that wrecks are removed after wreckLifetime (30 minutes by default), and an aircraft under a camo net keeps decaying on its normal timer.

The server won't start

Read the first script or config error, check the mod files are complete and CF loads first, then check your mission files. Look for Can't compile with a file and line, Undefined function, Cannot open file, or missing addon errors. If needed, go back to the last working mod version together with its matching storage backup.

A broken settings file doesn't stop the server; it logs a fallback such as [RCEDATA] can't read or [RCEDMG] settings: can't read and uses defaults. If your changes don't seem to apply, look for those lines.

Players' keys don't work

Flight keys are client bindings; nothing is configured on the server. Players from earlier versions may still have recovery on X or old weapon bindings. Point them to Controls.

Other mods

RotorCraft Evolution needs only Community Framework. Not every combination of mods can be tested, and mods that change vehicles, weapons, ammunition, animations, key bindings or the player can conflict. If you suspect a conflict, try without the other mod on a test copy of your server.

Getting help

Post in the bug-report forum on the Discord with:

your full mod list and load order;
the server script log and RPT from the session, and the client logs if it's a client-side problem;
what you expected and what happened.

Something missing or wrong? Ask in the Discord.