EVE Online Local and D-scan intel tool
Intel turns what the EVE Online client gives you on the clipboard into evidence you can keep, and puts it next to what the public record says. Paste a Local member list or a directional scan result, and Intel detects which it is, compares it with what you have seen before, and on request looks the names up on EVE's public API and on the public killboard record. Everything you save stays in your own browser. Nothing you paste is uploaded to EO-Map.
Public beta. Intel is open to everyone but still being shaped, so expect rough edges and copy that changes between visits. Two limits are deliberate: pilots are never attributed to ships (a D-scan is counted by hull, and a pilot list and a D-scan taken together are never joined), and every figure is a count over a named window, never a score.
What you can paste
Local member list
Click the member list in Local, press Ctrl+A then Ctrl+C, and paste. The clipboard holds only names, so Intel files it as the Local member list of the current system, with the system taken from your map selection until you correct it.
Directional scan
A scan is counted by hull: the total, how many are ships, what changed since your previous scan in the same system, and how many of the specialist classes are on it. Ships on a D-scan never get a pilot.
What Analyse does
Three things, kept apart. Comparing a paste with your own history is automatic, offline and free: nothing leaves your browser for it. Save to my history keeps a private report in this browser. Look up on public sources is the only step that uses the network. It asks EVE's public API for identity, which your browser calls directly to resolve characters, corporations and alliances, and it asks EO-Map's own killboard service for the public record of each resolved character: kills and losses, hulls flown and lost, systems, active hours and recurring associates. That service collects zKillboard on the server side with its own caching, so your browser never contacts zKillboard, sends no login and sends nothing about you.
Reading the result
A pasted member list is read as a group first: how many names EVE found, how many were on a killmail this week, how many have a hunter's record, and how many you have seen before. Under that, one row per pilot with corporation and alliance tickers, cautions such as a new character or a young corporation, the killboard record, an activity word and hull roles, then your own history with them. Click a name for a dossier: identity, one assessment line from the public record, your history in one line, and the systems the record names.
Absence is not proof. A character with no killboard record may be perfectly active, because zKillboard only holds killmails that were submitted to it. Intel says "no record" rather than showing you a zero, and every figure is a count of killmails over a named window, never a score.
On the map
While a dossier is open, the systems its record names are painted on the 3D map as a temporary view: green where the character got kills, red where they took losses, amber where both happened, and a quiet neutral for all-time hotspots with nothing recent. Each system in the dossier is a button that flies the map there. The view belongs to the dossier, so closing it clears the map, and nothing about it is saved to your map settings.
History, mistakes and undo
A report is one paste or scan you saved. An encounter is one situation: reports close together in the same system are grouped, so a Local you paste every thirty seconds for twenty minutes is one encounter with many reports. History lists your encounters newest first. For the first minute after saving, Undo removes a report completely. Change system corrects a report and keeps the previous value on record. Retract keeps a report greyed out and stops counting it, and Delete permanently removes everything counted from it, each behind a confirmation.
Where your data goes
Intel is the first EO-Map feature with a durable personal store, and it is opt-in: nothing is saved until you choose to save. Reports, rows, compact evidence records, aliases and the cached public lookups live in this browser's IndexedDB. The raw pasted text is never stored anywhere. Detailed rows are kept for one year by default, adjustable in Settings, and the compact records stay until you delete them so your counts remain exact after old rows expire. Export writes one JSON file you own; Import merges or replaces it with a preview first. A browser without IndexedDB, such as a private window, runs Intel for the session only and tells you so.
One EO-Map service is involved, and only when you ask: the killboard service is sent a character id and answers with public statistics. Nothing from Intel reaches an analytics event. The privacy page and the transparency report carry the full detail.
How to open it
- Open Tools Library in the left rail and pick Intel on the Intel / Activity tab, or use the link below.
- In the EVE client, copy the Local member list (click it, Ctrl+A, Ctrl+C) or a D-scan result.
- Paste into the box, check the short strip that says what Intel read and where it will be filed, and press Analyse.
- Read the group summary and the pilot rows, click a name for its dossier, and watch its systems light up on the map.
Part of EO-Map
Intel is one panel of EO-Map's interactive 3D map of New Eden. The same session plans stargate routes, shows alliance sovereignty, paints per-system activity and flashes live kills, so who is around you and what is happening around them read on one map.
Related tools
- Live kills, to watch kills flash on the map as they happen.
- Activity map, for how busy a system has been.
- Route planner, with personal risk along the route.
- Sovereignty map, for who holds the space you are in.
- My Geography, your own clones and items on the same map.
- All EO-Map features.
Frequently asked questions
Is Intel finished?
No. Intel is a controlled public beta: open to everyone, still being shaped, and honest about its limits. Pilots are never attributed to ships, every figure is a count over a named window rather than a score, and absence from the killboard is never read as inactivity.
Does EO-Map store what I paste?
No. Reports, rows and evidence records live in your browser's IndexedDB, and the raw pasted text is never stored anywhere. The only things sent to a server, and only when you choose to look names up, are the pasted names to EVE's public API and a character id to EO-Map's killboard service.
What does "no record" mean next to a pilot?
That the character has never appeared on a killmail submitted to zKillboard. It is not the same as inactive: a careful pilot, a hauler or a new alt may have no record at all. Intel shows the words rather than a zero because absence is not proof.
Can Intel tell a Local list from another chat channel?
No. The clipboard holds only names, so the client cannot tell one member list from another. Intel asks you to save a pasted list as the Local member list of the current system. If you copied the wrong window, discard before saving; if you notice later, retract or delete the report from History.