CMDRTOOLSGalactic Utility Bureau
FIELD UNIT // ONLINE
Menu
Other ToolsEDCarrier
Release candidateCMDRTools · EDMC plugin

Fleet-carrier routes.
One jump at a time.

Choose a destination, paste the next system into the carrier map, and schedule the jump. EDCarrier advances after confirmed carrier arrivals and keeps the next system ready on your clipboard.

Download 1.0.0-rc.2 How it works
FLEET-CARRIER ROUTETRACKING
01
ARRIVEDLHS 3447
✓
02
NEXT CARRIER JUMPBLEAE THUA AA-A H0
COPY
03
JOURNEY STATUS43 JUMPS REMAINING
ETA
ROUTE ADVANCEMENTON ARRIVAL
PLATFORMWINDOWS · EDMC 6.X
RELEASE1.0.0-rc.2
ROUTINGSPANSH CARRIER ROUTER
JUMP LIMIT500 LY

Mission briefing

The route moves when your carrier does.

EDCarrier handles route progression and clipboard targets. You remain in control of the carrier navigation map and every scheduled jump.

  1. 01

    Confirm the carrier

    Dock at it, select an observed owned carrier, or enter its actual system before plotting.

  2. 02

    Plot the journey

    Enter an exact destination system. EDCarrier requests a personal-carrier route from Spansh.

  3. 03

    Schedule the jump

    Paste the copied target into the carrier navigation map and schedule the jump yourself.

  4. 04

    Advance on arrival

    A confirmed carrier arrival advances the route and copies the following system.

Carrier navigation

Built around the jump cycle.

01

Clipboard progression

The next validated system is copied after plotting and after each confirmed carrier arrival.

02

Strict route checks

System identities, coordinates and every leg are checked before a route can be used. No leg may exceed 500 ly.

03

Off-route recovery

If the carrier arrives somewhere unexpected, EDCarrier can recalculate from its observed location.

04

Observed journey ETA

Arrival-to-arrival cycles build a per-carrier average for remaining-time estimates and scheduled-jump countdowns.

Release candidate

Test it deliberately.

This candidate is for acceptance testing before stable v1.0. It supports personal fleet carriers in the Live galaxy on Windows with EDMarketConnector 6.1.2 or later in the 6.x series.

  • Elite Dangerous Live on Windows
  • EDMarketConnector 6.1.2 or later in the 6.x series
  • A personal fleet carrier
  • HTTPS access to Spansh and cmdrtools.com
PACKAGEEDCARRIER
CHANNELRELEASE CANDIDATE
VERSION1.0.0-rc.2
SHA-256decd266086298c2874efbb472d6b8940c8caec71f0c123fecea611de539e30b5
Download verified ZIP

Checksum file · Automatic public updates are paused for release candidates.

Installation

Install in four steps.

Close EDMC before replacing an earlier EDCarrier folder. Keep only one enabled copy.

  1. 01

    Download the candidate

    Use the verified ZIP above and compare its SHA-256 checksum if desired.

  2. 02

    Open the plugins folder

    In EDMC, open File → Settings → Plugins, choose Open, then close EDMC.

  3. 03

    Extract the EDCarrier folder

    The result must be plugins\EDCarrier\load.py, without another nested EDCarrier folder.

  4. 04

    Restart EDMC and plot

    Confirm the displayed carrier ID and actual system, enter a destination, then choose Plot / Resume.

Cockpit operation

Simple controls for a long route.

Plot / Resume

Confirms the source and requests or resumes a route to the destination system.

Recalculate

Requests a fresh route from the carrier's current confirmed system.

Pause

Stops clipboard changes and holds the ETA without discarding the route.

Copy

Copies the current target again when another application has replaced the clipboard.

Data boundary

Routes go to Spansh. Commander identity does not.

EDCarrier does not need Frontier authentication and does not schedule or control carrier jumps.

SPANSH

Route request

Source and destination systems, their IDs and fixed personal-carrier parameters are sent over HTTPS.

NOT SENT

Private account data

Commander names, Frontier credentials, cargo and fuel data are not sent to Spansh.

LOCAL

Journey state

Selected carrier IDs, destinations, validated routes and measured durations remain in local EDMC profiles.

CMDRTOOLS

Update traffic

Update checks include the EDMC/plugin user agent, but not commander names, routes or carrier IDs.

Candidate status

Verified in software. Awaiting in-game acceptance.

The offline suite, EDMC's bundled runtime, release archive, theme palettes and four public Spansh routes passed validation.

Stable v1.0 still requires deliberate live carrier-jump, clipboard, schedule/cancel, restart, network-recovery and visual-theme acceptance. The stable signed update feed will not advertise this release candidate.

Troubleshooting

Fast checks before departure.

The system is unknown

Use the exact system name rather than a landmark nickname. For example, use Oevasy SG-Y d0, not Ishum's Reach.

The route did not advance

Check the displayed carrier ID and actual carrier system. Ship jumps and carrier jump requests do not count as confirmed carrier arrivals.

The clipboard target keeps changing

Pause automatic copying in other navigation plugins while EDCarrier is active.

Spansh is busy or unavailable

Wait briefly, then choose Recalculate. EDCarrier has no offline routing fallback.

Found a candidate problem?

Bring the installed version, the displayed carrier ID, the exact message and the action that produced it.

Report it in Discord ↗