OpsTrack

**OpsTrack mod v0.7.0** **Recordings now survive server crashes** - If your server crashes during a recording, OpsTrack continues **the same recording** when the server comes back on the same map. You don't need a command, it doesn't wait for players, and it works with or without autostart. - The replay stays **one continuous operation**. The downtime shows as a gap, so the mission is no longer split in two. - Admins who are online get a message: *"resumed recording … after a crash (total gap N min)"*. - It can't continue after a map change, more than **60 minutes** of downtime, or if the recording was stopped on purpose. In those cases a new recording starts as usual. **Planned restarts start a fresh recording** - Shutdown, `#restart`, a scenario change and **game over** now close the recording properly. The next one starts fresh, either by autostart or with `#opstrack_start`. - The end screen after game over is **no longer recorded**. - **Tip:** some hosting panels restart by killing the server process outright. OpsTrack can't tell that apart from a crash, so the recording continues. If you want a fresh one, send `#opstrack_stop` via RCON before the restart. **Commands** - `#opstrack_start`: continues the interrupted recording if there is one. - `#opstrack_start new` (or `#opstrack_start new <Map>`): **always** starts a new recording. - `#opstrack_start` / `#opstrack_stop` now tell you when a recording is being resumed or closed, and ask you to wait a few seconds. **Updating** - **No config changes needed.** Just update the mod. - While recording, the mod keeps a small file at `profile/OpsTrackRecording.json`. Please don't edit or delete it.