The details

Everything Directive 47 knows about your game, read straight from the files Elite Dangerous already writes.

Ask where your ships are and the answer comes off your own disk — not from a website, and not from a model that will produce a plausible one.

Ask for it

“where am I” “what am I flying” “where is my carrier” “what ships do I own” “what materials am I carrying” “how have I done this session” “what are my career statistics” “how many merc coins do I have” “what’s my reputation with the Empire” “how much exploration data am I carrying” “reset unsold exploration”

Every one of those reaches the thing it names. This capability has six answers and used to be reached as a whole, with the first of the six taken by default — which is where you are. So “where is my fleet carrier” was answered with where you were standing, under your own name, with your own route attached, and so was every other question here.

“My jump range” means yours, and only yours. Ask about a ship — “what’s the Cobra Mk III’s jump range?” — and this capability does not answer at all; the question goes to the model, which has the specification tables and knows about hulls you do not own. It used to be caught here and answered with your docking bay.

What it can tell you

What an event changed. Selecting an event on the Journal page shows a band titled WHAT THIS CHANGED, between What this means and Every field, saying what d47 took from it. “Nothing in d47’s picture changed.” is a normal answer: most events carry nothing d47 keeps. An event that never reached the Commander’s state has no band.

Where you are — system, body, docking state, and what you are doing:

Fixture One is in Fixture Nebula Point, near Fixture Nebula Point A. Currently in supercruise.
Next jump: Fixture Reach (class M). 3 jumps left on the route.

What you are flying, from your actual outfitting rather than from a table of ship specifications — which is what makes your Anaconda different from anyone else’s:

Flying Bold Endeavour, a Anaconda, ident JM-01.
maximum jump range 52.31 ly, fuel tank 32 t, cargo 12/64 t, unladen mass 1122.6 t, hull 94%.
Rebuy 9,694,497 cr.
24 modules fitted, 9 engineered.
Hardpoints:
  Huge Hardpoint 1: 4A Plasma Accelerator, fixed — Efficient Weapon, grade 5, Thermal Conduit
  Large Hardpoint 1: 3C Multi-Cannon, gimballed — Overcharged Weapon, grade 5, Auto Loader
  ...
Core Internal:
  Armour: Military Grade Composite — Heavy Duty Armour, grade 5, Deep Plating
  Power Plant: 8A Power Plant — Overcharged Power Plant, grade 5
  Frame Shift Drive: 6A Frame Shift Drive — Increased FSD Range, grade 5, Mass Manager
  ...
Optional Internal:
  Compartment 1 (size 7): 7A Shield Generator — Reinforced Shield Generator, grade 5
  Compartment 4 (size 4): 4E Cargo Rack
  ...
Unpowered: 4E Cargo Rack.

Paint jobs, decals, name plates and the other cosmetics are left out of the list and the count: only what sits in one of the hull’s outfitting slots is listed, under the outfitting screen’s headings and in its order.

Name another ship you own and the same report comes off loadouts.json — every Loadout Elite has ever written for it, kept whether or not you are aboard right now — dated so a ship refitted since you last boarded it is visibly stale:

Campaigner, a Panther Clipper MkII, as of 2026-08-01 09:00 UTC.
maximum jump range 48.14 ly, fuel tank 128 t, cargo capacity 1200 t, unladen mass 1575.4 t.
27 modules fitted, 6 engineered.
Hardpoints:
  ...

A ship you own that no Loadout has been read for says so rather than describing a different one:

Campaigner (Panther Clipper MkII) — no loadout has been read for it yet. That is written the
next time you board it.

Where your carrier is. Ask “where is my carrier” and that is all you get back — the system and when it was last reported:

Fleet carrier Bootstrap (K7Q-BQL) is in Colonia, as of 2026-09-05 16:36 UTC.

Your fleet is a separate question, and asking it is what makes Directive 47 read out ship names. “What ships do I own”, “my fleet”, “what ships are on the carrier”:

Fleet carrier Bootstrap (K7Q-BQL) is in Colonia, as of 2026-09-05 16:36 UTC.
Currently flying Bold Endeavour, a Anaconda.
2 other ships stored, as of 2026-09-05 16:36 UTC:
  Deciat:
    Wanderer (Asp Explorer)
  Shinrarta Dezhra:
    Mule (Python)

The system is a heading and each ship is alone on the line under it, because a fleet of a dozen run together after one colon is a paragraph to read and a single breath to hear.

What every ship carries, not just the one you are sitting in. Each Loadout Elite writes is kept, so “which of my ships with at least 24 tonnes of cargo has the best jump range” is a question about figures already on disk:

2 ships, each as it was last seen fitted — refit one and it reads as it was until you board it again. Jump range is the maximum with one jump's fuel and an empty hold, as the game reports it, so a full tank or a laden hold is shorter.
  Bold Endeavour, a Anaconda — you are flying it, cargo 8 t, jump 52.31 ly, unladen mass 1122.6 t, fuel 32 t, worth 219,694,497 cr, rebuy 9,694,497 cr, as of 2026-09-05 16:36 UTC
  Mule, a Python — Shinrarta Dezhra, cargo 128 t, jump 21.44 ly, unladen mass 350.6 t, fuel 32 t, worth 61,204,110 cr, rebuy 3,060,205 cr, as of 2026-08-14 19:02 UTC
No loadout read, so not covered above: Wanderer (Asp Explorer).

Both caveats are in the answer because both are real. The jump range is the right figure for ranking ships against each other and the wrong one for a run with the hold full, and a ship refitted since you last boarded it is remembered as it was — which is what the timestamp on each line is for, and what Rescan my journals on the Ships page repairs. A ship you own that no Loadout has been read for is named rather than left out, so a ranking is never mistaken for the whole fleet.

What is in module storage, grouped by where it is, because the question underneath is nearly always “can I fit it here, or do I have to fetch it”:

3 modules in storage, as of 3311-01-01 00:01 UTC.

Deciat:
  int powerplant size6 class5 (PowerPlant Boosted, grade 5), hot — 58,000 cr to transfer, 60 minutes

Shinrarta Dezhra (where you are):
  Beam Laser

In transit: Prismatic Shield Generator.

Ask for one thing and it narrows to it — get_stored_modules takes a fragment, so “have I got a shield anywhere” works without the full catalogue name.

This is your own storage read off disk, and it is a different question from where a module can be bought: that one is galaxy search and it leaves the machine. This one works with the galaxy search switched off, which is what a fresh install is.

Where Elite writes no readable name, Directive 47 keeps the symbol’s words rather than inventing a friendly one — int powerplant size6 class5 above is ugly and true, and a guessed “6A Power Plant” would be indistinguishable from the feature working.

What you are carrying, by category, with the top holdings rather than all of them — a full list is over a hundred lines and no answer to a spoken question:

1,204 units across 87 materials.
Raw: Carbon 47, Iron 36, Nickel 22, and 12 more.
Encoded: Distorted Shield Cycle Recordings 3.
On foot: 14 items in the backpack, 212 in the ship locker.
  Backpack consumables: Energy Cell 3, Medkit 2.

How the session has gone, counted from when you entered the game rather than from when the journal file happens to have started:

Session running 2.4 hours.
Earned 2,605,000 cr — 250,000 bounties, 1,400,000 trade, 880,000 exploration, 75,000 missions.
14 jumps, 384.2 ly travelled.
22 bodies scanned.
Balance at session start: 1,000,000 cr.

Every figure is a sum of amounts Elite reported. Nothing comes from a price table or a market lookup, so the numbers are the ones you would recognise.

The BGS work you have done, per system and faction, since the last BGS tick — “what’s my BGS work”, “what have I done for the BGS”. It comes from the last seven days of your journals, so it survives a restart. With no tick time it covers the last 24 hours and says so, naming the BGS tick time setting in Galaxy. At most three system and faction pairs are named, the one with the most entries first, and the rest are counted:

Since the BGS tick at 16:14 UTC, 3 hours ago:
Diamond Frogs in HIP 97704: missions +5 and -1; bounties 117,480 credits; trade 2,400,000 credits sold for 310,000 profit; cartography 506,832 credits; influence 23.1% before the tick, 24.0% when you were there at 18:02 UTC.
and 4 more factions.

Name a faction or a system and only the matching pairs come back, all of them. When a tick time is known and your journals hold a reading from before it and one from after, each line adds the faction’s influence before the tick and at your latest visit, or “unchanged” when the two readings agree. Elite updates systems for some hours after the tick, so that is what the readings showed, not a result of your work.

Your career statistics, from the journal’s Statistics event — every section Elite writes, or one section named, with each figure under a readable name and in its unit — credits, Merc Coins, light years, or hours and minutes:

Career statistics, as of 2026-09-05 16:36 UTC:

Exploration:
  Total Hyperspace Distance: 4557.72 ly
  Time Played: 54 minutes

Name one section and only that one comes back — “what have I earned from exobiology”:

Exobiology, as of 2026-09-05 16:36 UTC:
  Organic Data Profits: 4,204,000 cr

“How many merc coins do I have” reads out the bank account section, where Elite keeps the Merc Coin ledger beside the credit balance:

Bank Account, as of 2026-09-26 10:00 UTC:
  Current Wealth: 1,234,567 cr
  Merc Coins Current: 46 Merc Coins
  Merc Coins Total Earned: 1,046 Merc Coins
  Merc Coins Total Spent: 1,000 Merc Coins
  Merc Coins Spent On Merc Gear: 750 Merc Coins
  Merc Coins Spent On Engineering: 250 Merc Coins

The journal carries no weekly earning allowance and no cap, so d47 does not say how many Merc Coins are left to earn this week.

Statistics is written about 30 seconds after LoadGame, once per session:

The game has not reported your career statistics this session.

Your reputation and navy rank — each superpower as a band and a number out of 100, with the Imperial and Federal navy ranks beside the Empire and the Federation. Ask for one superpower — “what’s my reputation with the Empire”, “what’s my imperial rank” — and only that one comes back:

Reputation, as of 2026-09-23 10:00 UTC:
  Empire: Cordial, 28 of 100. Imperial Navy rank: Outsider, 93% into it.

The superpower figures come from the Reputation event Elite writes when you enter the game.

A minor faction, by name — “what’s my reputation with Mother Gaia”. The reading comes from the last time you arrived in a system where that faction is present, so the answer always says when that was:

Mother Gaia: Friendly, 43 of 100, last read on 2026-09-20.

Part of a name is enough when only one faction you have met matches it. When several do, they are listed by name rather than one being picked for you.

The bodies you have mapped and not sold — every body you finished mapping with the Detailed Surface Scanner since you last sold its system’s data, each with about what Universal Cartographics will pay for it:

About 3,277,078 credits of mapped bodies unsold, from 3 bodies. 3 of them were mapped efficiently. This is an estimate, and it leaves out stars and bodies scanned but not mapped, so Universal Cartographics will pay more.

Elite never writes what a body is worth; only a sale carries credits, and only for the whole sale. The value is computed from the body’s scan with the formula players have worked out from sales — a figure per planet class, raised for a terraformable body and for its mass, multiplied for mapping, for being first to map it, for being first to discover it, and for mapping it within the probe target. It is spoken as an estimate for that reason. The Detailed scan Elite writes straight after a mapping can say the body had not been mapped when an earlier scan said it had; a body counts as already mapped or already discovered if any scan up to the mapping said so.

When you finish mapping a body, the Mapped body value callout says what it is worth and the new total. The total goes down when you sell: MultiSellExplorationData removes every held body in each system it names, because the sale names systems rather than bodies. It goes to zero when you die, and when you say “reset unsold exploration”, which the model cannot do for you. It is rebuilt from your journals at every start, so it is right after a restart.

When it does not know

It says which event it is waiting for rather than shrugging — “Directive 47 started after Elite” and “this is unknowable” have different fixes:

No Loadout event has been seen yet, so I do not know what you are flying. It is written when
you enter the game or change your outfitting.

I have no ship list yet — it is written when you dock at a station with a shipyard.

I have no module storage list yet — it is written when you dock at a station with outfitting.

Where the carrier is comes from your journals, not from this session. Directive 47 reads the whole journal folder for carrier events at startup — CarrierBuy, CarrierLocation, CarrierJump and CarrierStats — so the answer survives a restart, and it says when the carrier was last reported so you can judge how stale that is. Elite writes those events when the carrier jumps and when you open its management panel, and never in between; a carrier that has sat in one system for a fortnight was last reported a fortnight ago, and the date says so rather than the answer pretending it is fresh. Nothing is inferred from where your ships happen to be stored.

Carrier events only ever reach the owner’s journal, so having seen none is genuinely ambiguous and the answer says so rather than claiming you have no carrier:

No fleet carrier appears in any journal read, so I do not know where one is.

And before any journal has been found at all — a fresh install, or Elite has never run:

No Elite Dangerous journal has been detected yet.

It already knows where you are

You do not have to say where you are before asking something else. A short summary of your situation goes with every question you put to the model, so “what should I do about this” has something to work with:

Location: Deciat, docked at Garay Terminal (Orbis)
Status: docked
Ship: Bold Endeavour, a Anaconda
Ship metrics: max jump 52.31 ly, fuel 28.5/32 t, cargo 64/64 t
Cargo hold: Tritium 40t, Gold 16t, Beryllium 8t
This session: 14 jumps, 2,605,000 cr earned

It states only what the journal reported, and leaves a line out entirely rather than saying “unknown”.

Your hold is reported as how full, not just how big. Capacity on its own is what let a passing remark call a laden hold half empty: there was a tank size in front of the model and no manifest to check the claim against. The held figure and the heaviest few commodities now go with it, so a comment about your cargo is a comment about your actual cargo. Until Cargo.json has been read for the ship — still starting up, or driving the SRV under it — the line falls back to cargo capacity 64 t, which claims nothing about how full you are.

More than one Commander

Two Commanders on one machine stay separate. Location, ship, carrier, fleet, materials and session totals are kept per Commander and never merged.

When Elite changes

Frontier adds and changes journal events several times a year. An event Directive 47 does not recognise is skipped and noted rather than breaking the read, and a field that is missing or has changed shape reads as absent rather than as zero — an invented figure in your game state is worse than a missing one.

Codex pictures

Stock pictures of codex entries are published as files on a GitHub release. Directive 47 fetches the list the first time a codex page wants a picture in a session, and each picture the first time a page shows it, and keeps them in data\codex-pictures. A picture’s file name gives its codex entry and region; nothing else is sent: no key, no Commander name, no position and nothing else from your journal.

Pictures you save yourself are kept in the same folder and never leave this PC.

To make your own, say “take a picture” in game, then open the entry’s page in the main window (Commander, Ledgers, Codex, the region, the entry) and press Choose a picture. The captures are listed newest first, those taken with this entry ahead of the rest. Press one to crop it: drag inside the square to move it and drag a corner to resize it. The square stays inside the capture and is never smaller than 384 pixels of it. Save keeps a 768 by 768 picture, the capture it was cut from and the square, in data\codex-pictures\local\<Frontier ID>; Cancel keeps nothing.

With a picture of your own for the region, the entry’s page also offers Re-crop, which opens the kept capture with the saved square, and Replace. Use the stock picture, or Remove my picture when there is no stock one, deletes your picture and its capture. These are in the main window only; the big panel shows the picture and none of them. An entry in a region D47 cannot name has none of them.

Codex pictures in the settings turns it off. Nothing is fetched and a codex page shows only the pictures you saved yourself, even for stock pictures already on disk, which are kept.

Share codex pictures

Pictures you save are kept for the active Commander, in data\codex-pictures\local\<Frontier ID>, and a codex page shows only that Commander’s. Pictures saved before this setting existed moved into the folder of the first Commander whose journal was read afterwards. With no Commander active, no picture of your own is shown and Choose a picture is not offered.

Share my codex pictures with my other Commanders in the settings is off by default. Ticked, every Commander’s pictures are one pool: a page shows the active Commander’s picture where there is one and another Commander’s where there is not. Re-crop, Replace, Remove my picture and Use the stock picture act on the active Commander’s picture only. Stock pictures are shared either way.

Open new codex entries

When you log a codex entry for the first time, the panel opens that entry’s page, in the window and on the headset panel: Commander › Ledgers › Codex › the region › the entry. It is on by default. A surface showing a dialog page or a keyboard entry stays where it is, and the others still move. When several entries are logged at once, the last one’s page is shown. Entries replayed from the journal when D47 starts open nothing.

Open new codex entries in the settings turns it off.

Codex publish token

This is for the maintainer of the stock codex pictures. The stock pictures are files on releases of the public repository dseelinger/d47-codex-pictures, listed by index.json on the release codex-pictures-1. With a token, a codex entry’s page in the main window can put a picture on that list for every Commander, or take one off it.

To make the token, create a fine-grained personal access token on GitHub with access to the repository dseelinger/d47-codex-pictures only and the permission Contents: Read and write. Paste it into Codex publish token in the advanced settings, where it is stored encrypted for this Windows account. Without a stored token, Directive 47 reads the environment variable D47_CODEX_PUBLISH_TOKEN. The repository needs at least one commit, such as a README, before the first publish, because GitHub cannot tag an empty repository.

Publish shows when your own picture for the entry and region is the one on show. It uploads the picture to the highest-numbered codex-pictures-N release with fewer than 1000 files, creating the next one when none has room, then adds the picture to index.json, and deletes the stock picture it replaced. Your picture is then deleted from this PC, so the page shows the stock picture every install now sees; the kept capture and square stay, so Re-crop still works.

Unpublish shows when there is a stock picture for the entry and region. It asks first, then takes the picture off index.json and deletes it from the release. Pictures Commanders saved themselves are kept.

One publish or unpublish runs at a time. A failure stops at the step it reached, shows GitHub’s message, and changes no file on this PC. Neither button shows on the big panel or without a token.

{"type":"object","properties":{},"required":[],"additionalProperties":false}

{"type":"object","properties":{"faction":{"type":"string","description":"Report only the work done for this faction. Omit for every faction."},"system":{"type":"string","description":"Report only the work done in this system. Omit for every system."}},"required":[],"additionalProperties":false}

{"type":"object","properties":{"by":{"type":"string","description":"The grouping to report. Omit for the top entry of each.","enum":["enemy","ship","system","faction"]},"name":{"type":"string","description":"Report only the entries of the grouping whose name contains this, without regard to case."},"period":{"type":"string","description":"The last day, week (7 days) or month (30 days) before now, or all of the record. Default all.","enum":["day","week","month","all"]}},"required":[],"additionalProperties":false}

{"type":"object","properties":{"kind":{"type":"string","description":"Report only this kind of transaction.","enum":["trade","exploration","missions","combat","vouchers","rescue","community_goals","colonisation","powerplay","ships","modules","upkeep","rebuy","fines","crew","on_foot","engineers","carrier"]},"period":{"type":"string","description":"The last day, week (7 days) or month (30 days) before now, or all of the record. Default week.","enum":["day","week","month","all"]}},"required":[],"additionalProperties":false}

{"type":"object","properties":{"period":{"type":"string","description":"Since the last sale of exploration data (trip), since this session began, or all of the record. Default trip.","enum":["trip","session","all"]},"region":{"type":"string","description":"Report only this codex region, by name, or here for the region the Commander is in."}},"required":[],"additionalProperties":false}

{"type":"object","properties":{"region":{"type":"string","description":"The codex region, by name, or here for the region the Commander is in. Default here."}},"required":[],"additionalProperties":false}

{"type":"object","properties":{"body":{"type":"string","description":"The body name, or its short form such as \u00227 b\u0022. Leave out for the most recently seen body that has geological signals."}},"required":[],"additionalProperties":false}

{"type":"object","properties":{"jump_range":{"type":"boolean","description":"Answer with the unladen jump range alone. Set it only when they asked for the jump range and nothing else about the ship."},"ship":{"type":"string","description":"Which ship, by name or hull. Omit for the one currently flown."}},"required":[],"additionalProperties":false}

{"type":"object","properties":{"ships":{"type":"boolean","description":"List the ships the Commander owns and which system each one is stored in. Set it only when they asked what ships they have or what ships are in a system. Asking where the carrier is is not that question."}},"required":[],"additionalProperties":false}

{"type":"object","properties":{"min_cargo":{"type":"integer","description":"List only ships with at least this many tonnes of cargo capacity."},"mining":{"type":"boolean","description":"List only ships fitted for tritium mining \u2014 a mining laser or Volley Repeater, a collector controller and a refinery \u2014 each with the modules that show it."},"order_by":{"type":"string","description":"Rank the ships by this figure, largest first. Listed by name otherwise.","enum":["jump_range","cargo"]}},"required":[],"additionalProperties":false}

{"type":"object","properties":{"module":{"type":"string","description":"Narrow the list to stored modules whose name contains this \u2014 for example \u0022shield\u0022 or \u0022Frame Shift Drive\u0022. Leave it out for the whole store."}},"required":[],"additionalProperties":false}

{"type":"object","properties":{"section":{"type":"string","description":"One section of the career statistics to report. Omit to report every section.","enum":["Bank_Account","Combat","Crime","Smuggling","Trading","Mining","Exploration","Passengers","Search_And_Rescue","Squadron","Crafting","Crew","Multicrew","Material_Trader_Stats","FLEETCARRIER","Exobiology"]}},"required":[],"additionalProperties":false}

{"type":"object","properties":{},"required":[],"additionalProperties":false}

{"type":"object","properties":{"faction":{"type":"string","description":"A superpower or a minor faction, whole or part of its name. Omit for the four superpowers and both navy ranks."}},"required":[],"additionalProperties":false}

{"type":"object","properties":{},"required":[],"additionalProperties":false}