EVE Frontier Log Parser Runs in your browser

EVE Frontier writes a log of what you do: the ore you mine, the shots you fire and take, and every system you enter. The EF-Map Log Parser reads those logs and shows your cycle on the map: where you spent your time, where you mined, where you hunted, and the path you flew. It is free, needs no account, and reads the files in your browser. Nothing is uploaded unless you choose to publish your totals to the leaderboard.

Open Log Parser How to load your logs

Your logs on the map

Pick a lens and every system you played in gets a ring, bigger where you did more. They are the same density rings the Killboard uses for kills.

Path draws every jump you made, brighter where you flew the same hop more often, and Replay plays your travel back jump by jump while the rings grow. Hover a system and its card gets a "Your logs" section: visits, time there, ore mined, NPC kills and damage taken. Fit on map frames all of your systems at once.

Your PvP kills and deaths are pinned on the map too. They come from the Killboard, which reads on-chain killmails, because the game logs never record a ship loss.

Your cycle, day by day

Under the map controls sits a strip with one column per day of the cycle, stacked by what you did that day: mining, ratting, PvP, travel and scouting (self-destruct loops). Click a day and the map and every number switch to that day. The day view shows:

Days follow your computer's local time.

The numbers

Five totals sit at the top of the panel: Ore mined, NPC kills (estimated, shown with ≈), NPC damage (damage to structures is counted separately), Jumps (logins and respawns after a self-destruct are not counted) and Systems explored. Below them, five tabs:

Highlights

Your records for the cycle: biggest haul, fastest mining, best hunting ground, most time spent, busiest day, best hunt, favourite prey, who hit you hardest, longest session and shots evaded.

Mining

Ore by type, with crude matter tagged, and every mining session, sortable by biggest, fastest or most recent, with its peak rate per minute.

Combat

Each NPC type with estimated kills, fights, damage, HP and damage taken; who shot at you and how often you evaded; structures and pilots you shot; your killboard kills and deaths.

Travel

Every system with time spent, visits, ore mined, kills and when you were last there, plus your recent jumps, each labelled jump, login or respawn.

Leaderboard

A preview of exactly what would be published, buttons to publish, update or remove your entry, and the community board itself.

How NPC kills are counted

Cycle 7 logs have no line for a kill. Your damage to a target stops at its remaining HP, though, so the damage you deal to one NPC type adds up in whole multiples of its HP (a Grave Ostler has 1,764 HP, for example). The Log Parser counts kills from that, which is why they are shown as estimates (≈). Kills where a fleetmate did most of the damage are not counted, and NPCs that repair themselves can't be rated.

Players aim by hand in Cycle 7, so your outgoing hits no longer carry hit-quality grades. Incoming fire still records hits and misses, which is where the evasion figures come from.

Getting started

  1. Open the Log Parser with the button on this page, or from the Tools Library under Intel / Activity.
  2. Choose your logs folder. It is usually Documents\Frontier\logs. If OneDrive backs up your Documents folder, look in OneDrive\Documents\Frontier\logs. Choosing the Frontier folder above it works too.
  3. Let it read. Only this cycle's game logs and Local chat logs are read. Local chat is how the parser knows which system you were in.
  4. Press Sync after you play. In Chrome and Edge the folder is remembered and Sync reads only new or changed files, so a whole cycle of logs syncs in under a second. In Firefox and Safari, Sync opens the folder picker again instead. You can also drag the folder onto the panel.

If the folder holds logs for more than one character, the panel shows the one you played most recently and lets you switch.

Open Log Parser

What stays in your browser

Cycle 7 and Fog of War

The Cycle 7 map on EF-Map is charted by players, so a system you visited that nobody has charted yet can't be placed on it. The Log Parser counts those systems as "not charted yet" and places them once they are charted. It reads only the log files the game writes; it does not read game memory or reveal anything Fog of War hides.

Related resources

Frequently Asked Questions

Is there a combat log parser for EVE Frontier?

Yes. EF-Map's Log Parser is free and reads your EVE Frontier game logs and Local chat logs in your browser. It shows your cycle on the map: time spent, mining, ratting and PvP for each system, the path you flew with a replay, and what you did each day, plus tables of NPCs you fought, who shot at you, and your killboard kills and deaths.

Where are my EVE Frontier logs?

Usually in Documents\Frontier\logs, or OneDrive\Documents\Frontier\logs if OneDrive backs up your Documents folder. It holds a Gamelogs and a Chatlogs folder. Choose the logs folder (or the Frontier folder above it) in the Log Parser and it finds both.

How does it count NPC kills if the logs don't record kills?

Your damage stops at a target's remaining HP, so the damage you deal to one NPC type adds up in whole multiples of its HP. The Log Parser counts kills from that and shows them as estimates (≈). Kills where a fleetmate did most of the damage are not counted, and NPCs that repair can't be rated.

Are my logs uploaded anywhere?

No. The logs are read and stored in your browser. If you publish to the community leaderboard, which needs a signed-in wallet, only your totals are sent: no systems, times or log lines. Those numbers are self-reported from your logs and not verified on chain.