Skip to content

Terminal Output

github-actions[bot] edited this page Nov 9, 2026 · 9 revisions

EDLD Terminal Output Reference


Startup Banner

On launch, EDLD preloads the current journal, bootstraps mission state, then prints a session summary:

==========================================
  ▶  MONITORING ACTIVE
  CMDR MERRICK CALBRUIN
  Type-10 Defender  |  Solo
  Expert +56%
  A. Lavigny-Duval  Rank 22  (152,198 merits)
  Bhutatani
  Stack: 386.32M (18/20 complete, 2 remaining)
==========================================

Conditional lines appear only when the relevant data is available:

Line Condition
Powerplay allegiance Only when pledge is active
Location Only when star system is known
Stack Only when massacre missions are active
Credits / Cargo / Fuel Only when the value is known at startup
Fleet Carrier Only when a carrier is on file
Terminal launch banner
Launch banner printed to terminal on startup

Event Lines

EDLD prints timestamped event lines to the terminal. Each line carries a fixed-width sigil indicating event category and urgency. When running the Textual dashboard, terminal output is suppressed and the dashboard's blocks receive the same events.

[14:23:07] *  KILL  Anaconda [Bhutatani Partnership] +4 [30.25M cr]
[14:31:44] *  MISS  Accepted massacre mission (active: 12)
[14:38:00] ~  SUMM  Session Summary: ...
[14:55:12] !! ATCK  Under attack by security services!

Urgency Prefix

Prefix Meaning
!! Critical — immediate threat or loss
! Warning — degraded state or alert
* Active event — kill, mission change
^ Damage / defensive event
+ Gain — reward, merit, fuel
~ Summary / periodic report
- Status / informational
> Navigation / movement

Category Tag

Tag Event type
KILL Bounty or faction kill bond awarded
MISS Mission accepted, loaded, completed, or abandoned
SUMM Session summary (periodic or on demand)
ATCK Under attack by security services
WARN Inactivity or kill rate alert
SCAN Cargo scan, security scan, or outbound scan
SHLD Shield state change
HULL Ship hull damage
DEAD Ship or fighter destroyed
SLF Fighter launched, damaged, or destroyed
FUEL Fuel level notification
MERC Powerplay merits earned
SHIP Ship loadout change
INFO Session start, CMDR info, menu/quit events
JUMP Supercruise entry or FSD jump
DROP Dropped at destination (RES or CZ)
TERM Session management ended the game
CAPI Frontier sign-in for the Companion API expired
CRGO Cargo jettisoned
CARR Fleet carrier: jump scheduled, canceled or completed, cooldown over, upkeep short
ROUT Route checks — permit locks, a tank that runs dry, a dry stretch, the wrong target, a re-plot
SURV Arriving at a survey stop: what is left to do there
EXPL Exploration callouts — an undiscovered system, a world first mapped, untrodden ground, a targeted system never reported; unsold discoveries scanned by someone else
BIO Exobiology callouts — a genus new to your codex here, clear to sample, a sample run left unfinished
MINE Mining callouts — a prospected rock you watch for, a motherlode, the ring, the hold filling, no limpets aboard
AUTO What auto honk and the next-stop plot did, or why they did not
BKUP Journal backups
EDSM Gaps found and filled in the EDSM flight log

Periodic Summary

Posted at :00, :15, :30, and :45 of every hour while at least one activity provider reports data — to the terminal / dashboard and optionally to Discord. None is posted while output is paused after Not in game (below).

Session Summary
Duration:          2:14:33
  Combat
    Kills:              67  |  29.9 /hr
    Bounties:        5.61M  |  2.50M /hr
  Exploration
    Distance:       7 jumps  |  175 ly
    Bodies scanned:     16  |  2.36M
  Missions
    Completed:           3  |  397.6k credits
  PowerPlay
    Merits:          1,072  |  478 /hr

Values right-align and the | delimiter is column-aligned across all rows. Each section appears only when that activity type has data for the current session. Summaries accumulate across the full session — each one shows the running total, not just the last interval.

The summary fires on the first qualifying quarter-hour tick after EDLD starts, then repeats on every subsequent :00/:15/:30/:45 boundary.

Whether each part of it is printed, sent to Discord, or sent with a ping is set by the Periodic* keys under [LogLevels]: PeriodicKills, PeriodicFaction, PeriodicCredits and PeriodicMerits.

Session summary posted to Discord
The same summary as posted to Discord

Not in game

When the game has been closed, or left at the main menu, for 15 minutes (and EDLD has been running for at least 5), one line says so — Not in game: Elite Dangerous client not detected or … Player at main menu — to the terminal and, at your highest notification level, to Discord. After it EDLD says nothing more on either: no repeat of the alert, no periodic summaries, no event lines. Output resumes when you load into the game again (LoadGame), or when EDLD is restarted. The dashboards, the overlay and EDAM go on showing the last known state throughout.

Clone this wiki locally