EVE Online Local and D-scan intel tool

Intel turns what the EVE Online client gives you on the clipboard into a quick read of who is around you. Paste a Local member list or a directional scan result and Intel detects which it is and reads it straight away. Each pilot in Local gets a threat tier read from the public killboard record, zKillboard's own character labels, and a count of how often you have seen them before. Everything you save stays in your own browser. Nothing you paste is uploaded to EO-Map.

What you can paste

What happens when you paste

A paste is read at once, with no confirm step. Comparing it with your own history is offline: nothing leaves your browser for it. When Intel knows the system, from your EVE location, your map selection or a system you pick, the paste is saved to your history straight away with an Undo for 60 seconds. Without a system it is read but not saved until you pick one. Both automatic saves can be switched off in Settings.

The public lookups for a pasted Local are on by default and can be switched off in Settings too. Your browser asks EVE's public API directly to resolve characters, corporations and alliances, and asks EO-Map's own killboard service for the public record of each resolved character: kills and losses, zKillboard's character labels, 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, and the service is sent a character id with no login and nothing about you.

Reading a Local

A pasted Local opens with one summary line: how many pilots are in Local, a threat bar, a count for each tier, the corporations and alliances that two or more of them share, and the zKillboard labels present. Each of those is a filter. Under it the pilots are listed threat first, one row each with the ticker, labels, kills and losses, zKillboard's danger figure and how recently they were on a killmail. While answers are still arriving the list keeps paste order, so rows do not jump. Compact keeps one line per pilot; Detailed adds organisation names, security status, age, your last sighting and their most-flown recent hull. Arrow keys move through the list and Enter opens a pilot.

Threat tiers and labels

Each tier follows fixed rules, and the reasons are shown on hover and in the dossier. High is at least one kill in zKillboard's 7-day window together with a danger reason, or 25 or more kills in that window on its own. A danger reason is a hunter record, meaning 20 or more kills at a zKillboard danger figure of 60 or more, or one of the labels BLOPS, BAIT, CYNO, FC, CAPITAL, SUPER, TITAN and GANKER. Watch is any kill in the 7-day window, or kills this or last calendar month plus a danger reason. Low is a quiet record, No record means never on a killmail, and Unknown means not looked up, not found, still loading or the service is unavailable. Friendly shares your corporation or alliance. It needs a signed-in EVE character, and without one nobody is Friendly.

The labels are zKillboard's own character labels, shown as zKillboard shows them, in its words and colours: AWOX, ALLIANCE AWOX, FACTION AWOX, GANKER, FC, BAIT, CYNO, BLOPS, LOGI, CAPITAL, SUPER, TITAN and ROOKIE. The definitions are zKillboard's, in its FAQ, and hovering a chip explains it. ROOKIE is worked out by EO-Map from zKillboard's numbers the same way zKillboard's page does. The AWOX labels and ROOKIE are shown but never raise a tier.

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.

The dossier

Click a pilot for a dossier laid out like a zKillboard character page: the portrait with its label chips, the name with its tier and reasons, corporation and alliance, security status and age, and links to the pilot's zKillboard and EVE Who pages. Six tiles follow for kills, losses, danger, solo share, ISK destroyed and kills in the last 7 days. Recent kills and losses are open by default, with where they happened, ships, active hours, associates, the full record and corporation history below. On a wide Intel window the dossier sits beside the list. On a narrow one it replaces the list, with Back, previous and next pilot, and Esc.

On the map

The Map switch paints, in magenta, the systems where the pilots in your Local got kills in zKillboard's 7-day window. An open dossier paints its own pilot instead: green where the character got kills, red where they took losses, amber where both happened, and violet for all-time hotspots with nothing recent. Each system in the dossier is a button that flies the map there. It is a temporary view, so closing Intel clears the map, and nothing about it is saved to your map settings.

Look up one pilot

The Lookup tab opens a single pilot without a paste. Type or paste a name and press Enter, and when EVE's public API finds exactly one character with that exact name the dossier opens straight away. The map's search box at the top left takes pilot names too and offers Look up in Intel; nothing is sent anywhere until you choose it. A lookup is never saved to your Intel history, and your last eight lookups are remembered in this browser so you can open them again.

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. 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; it is held in memory only until your next paste or a reload. 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: 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

1. Open Tools Library in the left rail and pick Intel on the Pilots tab, or use the link below.
2. In the EVE client, copy the Local member list (click a name in it, Ctrl+A, Ctrl+C) or a D-scan result (Ctrl+A, Ctrl+C).
3. Paste into Intel. It reads the paste at once and, when it knows the system, saves it with an Undo.
4. Read the summary and the threat-sorted pilot list, 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