EVE Online force projection planner
The Cradle of War update announced for EVE Online reprices Ansiblex jump gates by distance, and alliances are deciding now where their capitals and bridges should sit. EO-Map's Force Projection panel turns the announced numbers into a fare-zone map, a private bridge network and a fleet simulation, free in your browser, no account, no download.
Announced mechanics, treated as announced
Everything this tool models comes from CCP's July 2026 articles on the Ansiblex capacitor update, expected in the Cradle of War release in September 2026. Those rules are announced, not live: nothing in the game works this way today, and the numbers may change before they ship. EO-Map pins them as a dated ruleset and labels every zone and cost as announced until they are verified live.
The announced model prices each Ansiblex jump by where the destination gate sits relative to the owning alliance's sovereignty capital. Within 5 light-years, jumps are free. Four more fare bands begin at 5, 10, 15 and 20 light-years, and each ship class pays a published capacitor fare per band, drawn from the origin gate's 1,250 TJ pool, which recharges at roughly 200 TJ per hour. Long-range bridging is exactly what the new fares tax.
Five tabs, one question each
Projection
Pick an alliance capital, or pin any system as a hypothetical one. The five fare zones appear as per-system tint across the cluster, with true-distance shells in 3D.
Threat
Click a target system and read the zones backwards: which staging capitals hold it in a cheap band, ranked by zone and distance.
Network
Describe your own Ansiblex network, one gate per system. It lives in this browser and nowhere else.
Plan
Set an origin and destination and get a mixed stargate-and-bridge route, plus where new bridges would save the most time.
Fleet
Simulate a doctrine along the route and see when the first ship, half the fleet and the last ship arrive.
A network that stays in your browser
No public data source lists any alliance's real Ansiblex network, so EO-Map does not claim one. The Network tab is where you describe the bridges you know: pick two systems within the 5 light-year pair limit and the pair is validated against the placement rules, including the game's one-Ansiblex-per-system rule. Pairs can be marked built, planned or disabled.
The network is stored in your browser's local storage, never uploaded, and shared only if you export it yourself as a JSON file someone else can import. Demo networks and example fleets ship with the tool, so a newcomer can try the whole loop without building anything first.
Plan a route, then stress it with a fleet
The Plan tab works from the map. Left-click a star to set the origin; right-click one for a menu with destination, waypoints and avoided systems. The planner computes a mixed stargate-and-bridge route, reuses bridges your network already has, separates what to build from what to reuse, and suggests where new bridges buy the most time. The result draws on the map with direction of travel, in 3D and 2D.
The Fleet tab takes that route and a doctrine, counts per ship class, and runs an event simulation in a web worker on your own machine. Each ship pays its class's fare from the bridge it jumps through; when a bridge runs dry, the ships behind it wait for the recharge. The results give first, half-fleet and full-fleet arrival times, rank bridges by waiting caused, and compare the move against stargates alone. Starting capacitor is an assumption you choose, because live bridge capacitor is not knowable, so every time is a best case, not a promise.
Where the data comes from
Star positions and stargates come from the pinned official EVE Online Static Data Export, build 3464040, the same source as the rest of EO-Map. Alliance sovereignty capitals come from EO's regularly refreshed snapshot of public CCP sovereignty data. The fare table, capacitor size and recharge model come from CCP's announcement articles, pinned as a versioned ruleset dated 2026-07-21 and labeled announced. The bridge network comes from you alone.
How to open it
- Open EO-Map and pick Force Projection from the Tools Library, or use the direct link below.
- On the Projection tab, choose an alliance that holds sovereignty, or pin any system as a hypothetical capital.
- Switch to Threat and pick a target system to rank every live capital's fare zone against it.
- On the Network tab, load a demo network or add your own pairs.
- Set an origin and destination on the Plan tab, accept a route, then run it with a doctrine on the Fleet tab.
Part of EO-Map
Force Projection is one panel of EO-Map's interactive 3D map of New Eden. The same session shows current alliance sovereignty, live kills and system activity, so a bridge plan can be read against who holds the space it crosses and how hot it is right now.
Related tools
- Jump planner, for capital jump ranges and hull-specific jump routes.
- Route planner, for sub-capital stargate routes with security preferences.
- Sovereignty map, for who holds each system and where the capitals sit.
- Live kills, to see where ships are dying.
- Activity map, for jumps and kills per system.
- All EO-Map features.
Frequently asked questions
Does the map know where real Ansiblex gates are?
No. No public data source lists any alliance's Ansiblex network, so every bridge shown is one you described yourself. The demo networks that ship with the tool are fictional examples that follow the announced placement rules, not anyone's real network.
Are these fare zones live in EVE Online?
No. The zones, fares and capacitor numbers were announced for the Cradle of War update expected in September 2026 and are not live in the game today. The tool pins them as a dated ruleset, labels them announced wherever they appear, and CCP may still change them before release.
Is my bridge network uploaded anywhere?
No. The network lives in your browser's local storage and nowhere else. Sharing is a deliberate act: export the network as a JSON file and pass that file on yourself. Share links never carry network data.
How are the fleet travel times computed?
By an event simulation running in a web worker on your own machine, using the announced per-class fare table and the capacitor recharge model from the pinned ruleset. Starting capacitor is an assumption you set, so every arrival time is an estimate and a best case, not a promise.
Can a route mix stargates and bridges?
Yes. The Plan tab computes mixed routes, reuses bridges your network already has and separates what to build from what to reuse. In the Fleet tab, a leg served by both a gate and a bridge defaults to the bridge and can be flipped to the gate.
Why only one Ansiblex per system?
Because the game allows one Ansiblex structure per system, a rule that predates the announced changes. A system can anchor one end of one pair at most, so bridge chains alternate bridge jumps with stargate hops, and the tool validates every pair against that rule.