Captain's Log emblem Captain's Log

Commanders & Journal Archive

Fly more than one Commander? Captain's Log now knows about every commander in your journal archive - who flew what, when, and where their records live. Two buttons in the main window's top bar open two windows, because they answer two different questions:

Both windows hang off one brain: every fact either one shows comes from the same archive index and the same trip records, so opening one can never make the other lie. Both remember their own size and place too - widen the card wall until every commander fits, close the window, and it comes back that shape forever.

The first time you open either window after a change to your journal folders, the archive scan runs while you watch: the window appears at once and a progress bar ticks through the journal files, then a second pass indexes your trip databases. It's all read-only, so there's nothing to cancel - just a window that admits it's working.

The shared star database (GALAXY.db) is not split per commander - star systems and bodies are facts about the galaxy, not about who found them, so they stay in one place.

The COMMANDERS window

Commanders & Journal Archive

The COMMANDERS tab holds one card per commander found in your journals: their name, the dates they flew, an avatar, their archive totals - jumps, scans, unique systems and sessions - and how many trips belong to them. A card whose commander has no journals in your configured folders says so in place of the totals, rather than showing numbers you can no longer check. And a commander with neither journals nor trips gets no card at all: the wall shows what your records say today, not a memory of records that used to.

Under each card:

Below the cards is the UNASSIGNED LEGACY TRIPS strip: trips that belong to nobody - which is what all of your existing ones will be the first time you run this version, until the first-run upgrade claims the one you're already using (see Who owns which trip below). Double-click a row to fly it. Select rows with Ctrl+click / Shift+click and the ASSIGN TO CMDR button lights up saying how many you picked; choose a commander and, after asking first, Captain's Log records that commander as the owner inside the files and moves them into a folder named after them - so who owns what is legible in a file manager too. It refuses rather than guessing: it will not move the trip Captain's Log has open (switch first), and it will not rename a file onto a name that's already taken. Once the strip is empty it hides itself.

The window's right-hand side lists your journal source folders. By default Captain's Log reads the folder Elite writes journals to; ADD A JOURNAL SOURCE FOLDER lets it read others as well - an archive on a backup drive, a second install. Everything this window knows - the cards, their totals, and who the game is being played as - comes from those folders and nothing else. Each folder shows how many journal files it holds, in red if the folder has gone missing, and RE-SCAN ARCHIVE re-reads them all. A journal file that appears in two folders is only counted once.

Underneath sits UPDATE GALAXY FROM JOURNALS - the one journal job that belongs to no commander. It reads every journal in those folders into the shared GALAXY.db: no trip, no date range, and it won't start while a trip build is running. It is the slowest thing in Captain's Log - expect a couple of minutes on a full archive - so it has its own progress bar and cancel.

Who owns which trip

A trip can have an owner two ways, and either one is enough:

  1. it sits inside a folder named after the commander in your data directory, or
  2. it carries a binding recorded inside the file.

On the first run of a version with multi-CMDR support, Captain's Log looks at your newest journal, reads who was flying, and gives the trip you are already using to that commander - moving the file into their folder and recording the owner inside it. It only does this once, and only if nothing else has an owner yet, because a wrong guess is worse than no guess. It says so when it starts, and hovering the trip label at the bottom of the main window tells you who owns it and who decided:

CMDR Genar_Hofoen Assigned by Captain's Log from your most recent journal, on 15 Oct 2026. Change it in the Commanders & Journal Archive window if that is wrong.

If that guess is wrong, fix it: right-click the trip (in the TRIPS window or the legacy strip) or reach it through its commander's card menu and pick BIND TO COMMANDER. The current owner is ticked, OTHER (type a name)... covers a commander whose journals are long gone, and UNBIND COMMANDER takes the owner back off.

The TRIPS window

The TRIPS window

Its TRIPS tab is the flying tab. It belongs to the current commander - whoever the journals say you're playing as - and lists only their trips: TRIP, FIRST JUMP, LAST JUMP, JUMPS, SYSTEMS, newest first. It is never pointed at somebody else, because the one dangerous control in the window lives here: making a trip active. Fly the wrong commander's trip and every jump you make starts landing in it - so this page retires the danger by construction rather than by refusal. Who is current is worked out in order of honesty: the commander the game last loaded as, failing that the owner of the trip Captain's Log is filing into, failing that the most recently seen card.

The things you can do to a row:

NEW TRIP beside the table starts a blank trip for the commander the page belongs to: you name it, it's filed in their folder and bound to them, and a Switch to this new trip box in the prompt decides whether Captain's Log also starts flying it - starting a trip and starting to fly it are two decisions, so the box starts unticked. A brand-new trip has flown nowhere, so its date columns stay honestly empty, and it still lands at the top of the list: a trip sorts by when it last flew, and until it has flown, by when it was born.

WHEN ANOTHER CMDR LOADS

The setting lives in the Configuration Manager, in the Use Live Game or Beta Player Journals group, and decides what happens when the game loads a commander who is not the one your current trip belongs to:

There is no never switch option, and there honestly cannot be one: leaving Captain's Log filing one commander's jumps into another commander's trip is the original bug this check exists to stop. It never switches on a guess either - the app only moves your flying when the game's Frontier ID agrees with the record, a mere spelling difference can only ever ask, and a commander with no trips of their own is asked what to do rather than moved anywhere.

If the game has moved to a second commander while Captain's Log is still writing into the first one's trip, an amber banner appears above the TRIPS window's tabs naming both sides, with one button - SWITCH TO CMDR X - and a cross for "I know, leave it".

All of which assumes Captain's Log can see the switch: who is flying is read from the LoadGame events in journal files inside the folders listed on the COMMANDERS window. Move your journal files out of the game's folder by hand and the game knows you have changed commander while Captain's Log honestly does not - no switch happens, no prompt appears, and the TRIPS window belongs to the last commander it could actually read. Until the files are back in a folder it reads, or you ADD A JOURNAL SOURCE FOLDER pointing at wherever you moved them to, the live check is blind by relocation, not by fault.

SET AS DEFAULT picks the trip the live check aims that commander's flying at next time they load the game. It's the one control that's safe whoever is playing - it moves nothing that's being filed right now - which is why even another commander's card menu offers it ungreyed.

When a commander has no trips yet

If the game loads a commander with nothing to switch to - the second account's first flight, usually - the prompt offers three real things:

The prompt only appears when the load is visible, though - if that commander's journals sit in no folder Captain's Log reads, nothing prompts, because nothing is known. Press NEW TRIP yourself in that case, or give the app a folder it can read.

A brand-new Captain's Log - no trips anywhere yet - asks the same question at startup instead of quietly filing your first week into a scratch file, with CMDRNAME Trip 1 already typed in the box. If you NOT NOW your way out of that, the old v2default scratch file gets used - which is now the only way that file ever gets created.

The BUILD pages

The BUILD page, with a jump card in the trip builder tray

Both windows have a BUILD tab, and they're the same tool with one difference:

A BUILD page shows every jump in a commander's journal archive, oldest first - WHEN and STAR SYSTEM, one row per hyperspace jump - and turns the runs of jumps you select into a trip. Hover a row for its exact timestamp, which journal file it came from, and which stint it belongs to.

The page stores nothing: every visit re-reads the archive, so the newest jump you made is simply there. Only journals that contain jumps are read - a journal full of docking, shopping and scanning the system you already arrived in cannot add a row, so it's skipped.

The Journal File Organiser

The Journal File Organiser

The COMMANDERS window's ORGANISER tab moves one commander's journal files - and their trips - out of your game folders into a repository folder of your choosing, and brings them back. It exists for the pile that accumulates when you keep other people's journals around: a friend's debug files, an old save you're not playing any more. Parking tidies the card wall without deleting anything.

Choosing a repository folder inside a folder Captain's Log already reads as journals is refused up front - parked files there would be scanned straight back as live ones.

Deleting a trip

DELETE TRIP lives in the trip's right-click menu - or in its commander's card menu, which is the only way to reach a trip belonging to somebody who isn't flying right now. It's greyed on the trip Captain's Log has open; switch to another first. The confirmation tells you how many jumps and systems are in there and what dates it covers before it asks, because "delete Guardians 003?" is a thin way to decide to bin two years of flying.

What never appears as a trip

Captain's Log's own databases are not trips and cannot become ones: GALAXY.db (the shared star database), EDSMStarData.db and cl_values.db - checked by name and by contents, because a copy named something innocent can still be holding fifteen megabytes of star systems. You can't create a trip called Galaxy, and any file containing the star database's tables is refused for switching, assigning and deleting, whatever it's named. The old v2default scratch file is no longer special either: it gets claimed and filed like any other legacy trip - but the name stays Captain's Log's, so you can't create a new one.

A note on identification

Captain's Log identifies commanders by the Frontier ID in your journal files, because CMDR names get re-cased and reused. That ID is never displayed anywhere in the app - it is used internally to keep your flying in the right pile, and only the commander's name is ever shown.