Combat recording
The app can start and stop a video recorder automatically when a fight is detected — the same detection the Combat Overview uses (a fight starts with the first combat line in your gamelog and ends after 5 seconds of silence). The app never captures video itself; it drives an external recorder through providers, configured in Settings → Record fights. Two exist — OBS and command hooks — and any combination can be enabled at once.
Prerequisites
- Settings → Display Combat Overview: on. Recording rides the overlay’s fight detection; without it nothing triggers.
- A Gamelogs folder configured once in the DPS Meter module (the overlay tails the newest gamelog from there on its own).
- Record fights: on. Off by default — nothing runs until you enable it. The configuration lives on the Recording page (its sidebar entry starts in the sidebar’s Hidden section — expand it and click the eye to restore it) and is mirrored in Settings; both edit the same state.
How a recording runs, whichever path you pick:
- Fight start (first combat line) → recorder starts.
- Fight end (5 s of silence) → recorder stops after the configurable post-roll (default 10 s), so the aftermath stays in the clip. If combat re-erupts within the post-roll, the same recording keeps rolling.
- Replays in the DPS Meter never trigger recordings or the overlay: live
capture and playback are independent backend loops on separate event
channels (
dps://events/dps://bucketsvs.dps://playback-*), so stopping, replaying or scrubbing there can’t end fight detection. While the overlay is on, the meter’s live Stop only detaches the meter from the shared live capture. - Turning Record fights off mid-fight stops the recorder immediately.
- Only for character (multi-boxing): set a character name and only fights from that character’s gamelog record — the capture reports whose log it follows and the recorder compares (case-insensitive). Empty = any character.
- Test recording (bottom of the card) runs a 5-second synthetic fight through whatever providers are enabled — same start/stop actions, same post-roll — so you can verify the setup without undocking.
Provider: OBS (recommended)
OBS brings hardware encoding and, crucially, the replay buffer: the seconds before the fight was detected — the alpha strike that started it — end up in a clip too.
- Install OBS Studio 28 or newer (obs-websocket is bundled).
- In OBS: Tools → WebSocket Server Settings → Enable WebSocket server.
Note the port (default
4455) and the password (or disable authentication). - Create a scene with a window / game capture of your EVE client — the
window is titled
EVE - <CharacterName>, so each character’s client can be targeted precisely. - Optional but recommended: Settings → Output → Replay Buffer: on, then start the buffer (Controls → Start Replay Buffer, or enable auto-start in OBS’s general settings).
- In this app: Settings → Record fights → Provider: OBS: on, URL
ws://127.0.0.1:4455, the password from step 2, then Test connection — it replies with the OBS version when everything is wired.
Per fight, the app then:
- saves the replay buffer (skipped quietly when the buffer is off) and starts a recording on fight start;
- stops the recording on fight end (+ post-roll);
- writes a sidecar next to the finished clip —
<clip>.fight.jsonwith the fight’s exact time span, damage totals, and the attackers (name + ship) — so external tooling can index clips by fight.
Provider: command hooks (any recorder)
For recorders without an API, enable Provider: command hooks and give it
two shell commands, run through sh -c (cmd /C on Windows): one on fight
start, one on fight end. {start} and
{end} are replaced with the fight’s epoch seconds, handy for file names.
Exit codes are ignored by design — a recorder that is already running must not
surface as an overlay error.
Example with gpu-screen-recorder
on Linux (flags vary by version — check gpu-screen-recorder --help):
-
Fight start command
gpu-screen-recorder -w screen -f 60 -a default_output -o "$HOME/Videos/eve-fight-{start}.mp4" -
Fight end command
pkill -SIGINT -f gpu-screen-recorder(
SIGINTmakes it finalize the file.)
If you run gpu-screen-recorder’s own replay service instead, leave the
start command empty and make the end command save the buffer, e.g.
killall -SIGUSR1 gpu-screen-recorder — you get pre-fight seconds without
OBS.
Anything scriptable works the same way: ffmpeg, wf-recorder, a curl to
some other tool’s API, or a notify-send if you just want a ping.