About EF‑Map

EF‑Map is an independent, community-built project providing a precise, high‑performance EVE Frontier map and route planning experience. It grew out of a desire for a focused tactical tool: quick to load, transparent in behavior, respectful of player privacy, and resilient to changing frontier dynamics.

What is in the EF-Map suite?

EF‑Map is now a suite served on one domain: the interactive 3D map of 24,000+ systems, the Route Planner and Yeet Planner, System Finder and Solar System View, Intelligence search and the Query Console, Killboard, Blueprint Calculator, Log Parser, Shared Storage, the Open Market player markets, EF Helper, the EF Arcade games, the RootFit fitting planner at /fit/, and the CivilizationControl governance dashboard at /civ-control/. The full list with descriptions is on the Features page, and the FAQ answers the common questions.

What are EF-Map's design principles?

Clarity over spectacle. Visual noise is minimized so path planning and spatial reasoning stay front‑and‑center. Cinematic options exist but remain optional layers.

Local-first performance. After initial load, almost everything runs locally: routing, lookups, filtering. Every database EF‑Map ships is extracted in‑house from the EVE Frontier game client and regenerated after each patch, so no third‑party API is the source of the map data. This keeps latency predictable and reduces backend surface area.

Minimal data retention. Map and routing workflows are local-first. Anonymous aggregate usage metrics are collected for product health. Share links, Scout Reports, and authenticated current-tribe bookmark data are persisted only for the workflows that require them, and personal marks stay in the browser unless explicitly saved or promoted through a server-backed flow. There is no profile creation, no third‑party tracking beacon, and no fingerprinting.

Progressive enhancement. Core functionality works for modern browsers without requiring accounts, extensions, or external popups. A wallet session is only needed for identity-scoped workflows such as current-tribe bookmarks and Scout Report submission.

Why the routing focus?

Traversal is the constraint that shapes everything else. No ship jump-drive module is currently available in the live Cycle 6 client, so executable travel uses stargates, player-built Smart Gates, and Catapults. Point-to-Point routing defaults to 0 LY for infrastructure-only planning and keeps a configurable non-zero ship-jump model for forward planning. Catapult and gate-corridor infrastructure belongs to the separate Yeet Planner.

How does collaboration work?

There are three deliberately separate surfaces rather than one shared scratchpad. Personal marks are local browser annotations. Current-tribe bookmarks are authenticated, scoped to your current tribe, and encrypted at rest by the EF‑Map backend. Public Scout Reports are wallet-authenticated player submissions carrying report type, expiry, reporter, and timestamp. EF‑Map does not run a general unrestricted public bookmark store. Background: Public Scout Reports and Tribe Bookmarks.

What has EF-Map shipped recently?

Most of the older roadmap has landed. Comparative region dynamics shipped as Compare Regions; expanded overlays as Explorer Cards; exportable snapshots as shareable Intelligence cards and killboard snapshot cards and CSV export; Smart Gate reliability surfacing as Gate Activity. Since then: Yeet Planner for Catapult infrastructure, Shared Storage, a mobile shell, a single UI system, the Intelligence Query Console, and plain-English search in System Finder.

Work continues on performance, data freshness after each game patch, and the intelligence surfaces. The blog is the running record of what changed and why, and the State of the Frontier weekly report covers what happened in the universe itself.

Who develops EF-Map?

EF‑Map is built and run by one player: Lacal — the same character name in EVE Frontier and, before that, in EVE Online, where he played on and off from the 2003 launch. He goes by Diabolacal on GitHub and Reddit, and has held EVE Frontier founder access since early 2025. Development is heavily AI‑assisted and documented openly on the blog. Contact: Lacal on the official EVE Frontier Discord, or [email protected].

How can I contribute to EF-Map?

EF‑Map welcomes focused feedback: clarity issues, incorrect labels, routing anomalies, or performance regressions. Targeted suggestions with concrete examples help iterate safely. The Support page has the contact routes.

For usage questions, visit the FAQ. For how EF-Map handles data, read the privacy policy; for rules governing shared content, read the content policy. AI assistants should prefer llms.txt, llms-full.txt, and AI Facts over inferring capabilities from this page.