Ravencolonial EDMC Plugin

An Elite Dangerous Market Connector (EDMC) plugin that tracks colonization activity and Fleet Carrier stock, and syncs with Ravencolonial—similar goals to SrvSurvey while running inside EDMC.

Source, issues, and releases: github.com/Fenris159/ravencolonial_edmc
Download the latest build: GitHub Releases
More documentation: docs/README.md (manual install, auto-update, release checklist, API reference, logging notes)

---

Features

The plugin adds a Ravencolonial tab to EDMC while you play. You keep EDMC running as usual; it watches your game and can push updates to ravencolonial.com when you want that extra sync.

What you get	In practice
Colonization builds	When you’re involved with a colonization construction megaship and deliveries, the site can stay in sync with what the game says you still need and what you’ve dropped off—so your squad sees the same picture you do in-game.
Start a new build (Create)	Docked at the right ship, you can open a form in EDMC to register a new colonization project on Ravencolonial (name, build type, architect, notes, optional Discord link, and similar fields the site expects).
Plan sites (refresh)	Tap refresh to pull the latest planning list from Ravencolonial. System architects see every site still in plan—orbitals, surface ports, stations, and the rest—plus Create New. Anyone else only sees orbital plan sites in the list (a narrowed picker for helpers; see Link build at dock).
Link build at dock	Link Build Site ties the plan site you selected to where you are docked now on the server, including depot commodities on first link and the planner’s body when the site row has one. If you are the system architect, your selection includes the full plans list (orbitals, surface ports, stations, etc.). If you are not the architect, you only get orbital plan rows (No Orbitals when that list is empty). Linked sites drop out of the dropdown immediately after a successful link.
Finished-site Market Info	Ravencolonial ties colonization sites to in-game Market Info via each location’s MarketID. When construction finishes, dock once at the finished outpost (the completed station—not the construction depot) so the plugin can link your journal MarketID to that system site row. Works for new completions and older completed builds that never got Market Info backfilled. Needs your Ravencolonial API key; after completion the status line asks you to re-dock at the finished location.
Build tracker overlay/popout	Optional tracker table for a selected build project, or Track All aggregate totals across active build projects. Use Enable Overlay for the in-game HUD via EDMCModernOverlay, or Popout Tracker for the same layout in an EDMC-dark secondary window. The tracker groups remaining commodities by Elite market category, shows Need, current Ship cargo, optional FC's surplus/deficit, assignment hints, row bands, column dividers, localized commodity names where available, a trip footer based on your current cargo capacity, and a Fleet Carrier jump countdown as the last footer row when you have a scheduled jump. The popout remembers its position, can appear on the taskbar, and has a copy button for Discord-friendly fixed-width output.
Collapsible plugin panel	A chevron on the Ravencolonial header collapses the main-tab body to a single row when you want more EDMC space; separator lines stay visible while collapsed.
Fleet carriers	If you link your carriers on Ravencolonial, trades and transfers can update the cargo the site shows for those hulls—your personal carrier and squadron carriers you use in a similar way to other tools. You need your Ravencolonial API key in the plugin settings for this.
Your ship’s cargo	Optional: keep the site informed about which ship you’re in, how much cargo space you have, and what’s in the hold (handy next to colonization tools). Needs the API key.
Privacy (stealth)	Three separate toggles: stop sending fleet carrier cargo updates, stop sending ship hold snapshots, or stop sending construction depot / delivery reporting—mix and match what you’re comfortable sharing.
Updates	Optional check on startup for a newer plugin build on GitHub, a banner when one exists, and one-click style install (restart EDMC afterward). Details: docs/AUTO_UPDATE_FEATURE.md.
Languages	Buttons, messages, and the overlay HUD follow EDMC’s language when possible (French, German, Russian, etc.). Closing EDMC Settings with OK refreshes plugin-owned labels after a language change; some overlay commodities use official EDDI game-string resources where available, with English fallback for unsupported locales.

Screenshots

EDMC Plugin Controls

In-Game Build Tracker Overlay

---

Technical

For developers, contributors, and anyone who wants journal event names and API-shaped detail.

EDMC integration

• The plugin uses EDMC’s journal_entry stream (same ordering and state as the core app). It does not read the journal file on its own for normal operation.
• Optional Frontier CAPI (Companion) snapshots are used only through supported EDMC hooks (cmdr_data, cmdr_data_legacy, and capi_fleetcarrier), mainly for fleet carrier cargo alignment. Squadron carrier cargo tracking is journal-driven through the same linked marketId path as regular Fleet Carriers, not the unsupported Companion /squadron path.

Colonization (construction sites)

• Journal: ColonisationConstructionDepot drives remaining need via PATCH /api/project/{buildId} (full depot snapshot). ColonisationContribution records commander delivery history via POST …/contribute/{cmdr} (does not change need). The plugin does not use POST …/supply/{cmdr}.
• Dock / project state: GET /api/system/{id64}/{marketId} and related client normalization (see api/client.py, docs/ACTION_MAP_API_FLOWS.md).
• Legacy completed site repair: on Docked / docked Location only (not construction-depot journal lines), when a Ravencolonial API key is set, the plugin can backfill missing or incorrect marketId on complete or statusless /api/v2/system/{SystemAddress}/sites rows (e.g. depot 396… left on a row after the finished outpost uses 43…). Matching is normalized station name only (not BodyID/bodyNum—finished station names and MarketID prefixes differ from depot docks, and multiple sites can share a body). Repair runs when exactly one /sites row matches and its stored marketId is missing or differs from the dock journal; duplicate names skip the update. If that path does not apply, the same fetched rows are checked for exactly one row whose marketId already matches the journal, and that row can be patched with the normalized journal station name; duplicate marketId rows skip the rename. Eligible journal MarketIDs use colonization prefixes 395/396/397/42/43; fleet carriers, megaships, construction depots, and colonisation ships are excluded. One successful /sites GET is matched once; the GET is retried up to three times only on request failure (timeout/latency), then the row is patched with only the field being repaired; the last 50 dock (MarketID, normalized station name) contexts are remembered to limit repeat lookups while still allowing later name changes to be repaired.

Create project & plan-site refresh

• Create (dialog): PUT /api/project with fields aligned to the Ravencolonial OpenAPI (build type, architect, optional pre-planned site, etc.).
• Plan-site row (↻): GET /api/v2/system/{id64}/architect then GET /api/v2/system/{id64}/sites. Architect match → all plan rows + Create New (plan_sites_allow_create_new): orbitals, surface ports, stations, etc. Non-architect → plan rows whose buildType passes orbital_allowlist.is_orbital_build_type only; no Create New; empty → No Orbitals (helper path at orbital construction docks).
• Link Build Site: same PUT /api/project link for everyone after selection (includes depot snapshot, commodities, maxNeed, normalized dock buildName, and plan-site bodyNum / bodyName when available); the architect simply had the full plan list to choose from, the non-architect had an orbital-filtered list. Live GET .../sites preflight (row must still be plan), fresh GET /api/system/..., then PUT with architectName from the EDMC commander string. See docs/ACTION_MAP_API_FLOWS.md for the full guard sequence.

Fleet carriers

• Auth: Ravencolonial API key in settings (same rcc-key style usage as SrvSurvey for authenticated writes).
• Journal: MarketSell, MarketBuy, and CargoTransfer update linked Fleet Carrier cargo by docked MarketID. Squadron Carriers use the same marketId-based signed cargo delta path as regular linked Fleet Carriers.
• Endpoints: e.g. PATCH /api/fc/{marketId}/cargo, GET /api/cmdr/{cmdr}/fc/all for linked carriers and baselines—see the action map.

Commander ship snapshot

• Journal / state: Cargo, Loadout, SetUserShipName (via EDMC state) drive optional POST /api/cmdr/currentShip-style payloads when enabled.

Further reading

• docs/ACTION_MAP_API_FLOWS.md — journal events ↔ RavenColonial routes.
• docs/README.md — install variants, logging, API reference, release notes.
• docs/OVERLAY.md — build tracker overlay setup and behavior.

---

Requirements

• EDMC 6.1.2 or newer (releases).
• Python bundled with EDMC. For local dev/CI this repo targets requires-python >=3.11,<3.14 in pyproject.toml; see also .python-version for the maintainer venv version.
• Ravencolonial account if you use an API key, create projects, or sync FC / ship data.
• EDMCModernOverlay (optional) only if you use the in-game build commodity HUD - install separately from SweetJonnySauce/EDMCModernOverlay. The Popout Tracker works as an EDMC-native window without Modern Overlay. On some Linux distributions the overlay stack can require extra troubleshooting around compositor/window mode dependencies; use borderless/windowed Elite and see docs/OVERLAY.md.

---

Installation

1. Download RavenColonial_EDMC-v*.zip from the latest GitHub release (use the plugin asset, not a source archive, unless the release notes say otherwise).

2. Extract so you have a single folder named RavenColonial_EDMC containing load.py and the rest of the plugin.

3. Copy that folder into your EDMC plugins directory:

   • Windows: %LOCALAPPDATA%\EDMarketConnector\plugins\
   • Linux: ~/.local/share/EDMarketConnector/plugins/
   • macOS: ~/Library/Application Support/EDMarketConnector/plugins/

4. Restart EDMC. Enable the plugin under File → Settings → Plugins if needed.

If in-app auto-update fails (network, permissions, or GitHub), use docs/MANUAL_UPDATE_INSTRUCTIONS.md for a clean manual replace of the plugin folder.

Maintainers can build the same zip with make_release.py from anywhere (it writes build/release/RavenColonial_EDMC-v{version}.zip next to the repo; the zip contains a top-level RavenColonial_EDMC/ folder), or use GitHub Actions -> Build release. For stable releases, build from main with release_channel=stable and version/tag shape vX.Y.Z. For active-development pre-releases, build from development with release_channel=prerelease and version/tag shape such as vX.Y.Z-beta.1 or vX.Y.Z-rc.1; GitHub will mark those releases as pre-releases, and the plugin only offers them when Include pre-release versions is enabled.

To drop local __pycache__, dist/, egg-info metadata, and setuptools outputs under build/ (such as build/lib/) without touching release artifacts, run python scripts/clean_build_artifacts.py. That script always keeps build/release/ (including shipped zips). Optional --include-stray-root-zips only removes legacy RavenColonial_EDMC-v*.zip files sitting in the repo root, not under build/release/.

For local lint and unit checks, install developer tooling with python -m pip install -r requirements-dev.txt and run:

.\.venv\Scripts\python.exe -m flake8 . --statistics --count
.\.venv\Scripts\python.exe -m pytest -q

---

Configuration (File → Settings → Ravencolonial tab)

API key (ravencolonial_api_key)

• Get it from Ravencolonial → account / user settings (same key SrvSurvey uses as rcc-key for authenticated writes).
• Required for: Fleet Carrier cargo updates (personal or linked squadron carriers), commander current ship hold sync, and any server-side features that expect your account context.
• Project creation and many read/update flows still need the game + journal context; some calls work without a key depending on server policy—set the key for the full experience.

Optional API base URL (ravencolonial_api_url)

• Advanced: override the default Ravencolonial API host (see PluginConfig.DEFAULT_API_BASE in [plugin_config/settings.py](plugin_config/settings.py)).

Privacy — three stealth toggles

Setting	Config key	When enabled
Stealth: Fleet Carrier data	ravencolonial_stealth_mode	No FC commodity journal handlers and no CAPI FC cargo uploads to Ravencolonial.
Stealth: commander ship cargo	ravencolonial_stealth_ship_cargo	No POST /api/cmdr/currentShip (hold / loadout snapshot).
Stealth: all construction delivery reporting	ravencolonial_stealth_construction_reporting	No processing of ColonisationConstructionDepot, ColonisationContribution, or CargoDepot for Ravencolonial API updates from the journal. (Create Project from the dialog is unchanged—it is a deliberate UI action.)

Click Save Settings (or OK on the main Settings dialog—prefs are persisted on dismiss).

Update settings

• Check for updates on startup — queries GitHub Releases for a newer tag.
• Automatically install updates — downloads and stages the update, then promotes it during EDMC shutdown/restart after plugin resources are released.
• Include pre-release versions — treat beta/rc tags as candidates when comparing versions.

Details: docs/AUTO_UPDATE_FEATURE.md.

---

Usage

1. Run EDMC while playing (or before launching the game).
2. Dock at colonization construction sites and deliver cargo as usual; watch the plugin status line for confirmations.
3. Open ravencolonial.com for project progress and FC/ship data the server exposes.

Create Project

When docked at a construction site, use Create Build Project (or open project link when a build already exists—labels depend on state):

1. Choose build type (full tiered list in the dialog).
2. Project name, architect, optional pre-planned site, body, notes, Discord link as needed.
3. Create submits PUT /api/project with journal-backed depot data when available. On success the main tab switches to Open Build Page when the server reports the new project at your dock.

Plan sites and Link Build Site

When docked at a colonization construction location (construction megaship, and other eligible construction docks), the plugin shows Select Plan Site above the main button row when the flow applies.

Who sees what after Refresh (↻)

Refresh always loads GET /api/v2/system/{id64}/architect (who Ravencolonial lists as this system’s architect) and GET /api/v2/system/{id64}/sites, then compares the architect name to your commander in EDMC (case-insensitive).

• You are the system architect (names match): the dropdown lists all sites in plan status—orbital and surface types (ports, stations, megaships, and anything else the API returns as planning rows)—plus Create New for a scratch Create Build Project from the main tab. When you use Link Build Site, you are binding whichever plan row you picked to this dock, so it can match whatever construction site you are actually docked at, not only megaships.
• You are not the system architect: the dropdown lists only plan sites whose buildType is an orbital (same allowlist as the RavenColonial web client’s orbital set—see orbital_allowlist.py in this plugin). Create New is not shown on this path—that remains for the architect on the website or in the scratch dialog. That narrower list is so a helper docked at an orbital construction ship can still Link an orbital the architect pre-planned on Ravencolonial—including when the architect has moved the site forward remotely and wants someone in-game to finish the link-at-dock step—without being offered incompatible surface plan rows for that dock. Surface-only plan rows are omitted from this picker, not from the architect’s picker.
• If you are not the architect and no orbital plan rows exist, the row shows No Orbitals (disabled), not a false “nothing to do” architect error.

If refresh fails (network, HTTP error, or no commander context yet), a themed popup explains what went wrong; use Copy Error Msg for bug reports. The combobox keeps a short status label so the window layout stays stable.

Steps

1. Tap Refresh (↻) when you need an up-to-date list for the current system.
2. Pick a site from the dropdown (or Create New, when you are the architect and it is shown).
3. Link Build Site sends PUT /api/project so Ravencolonial connects the selected systemSiteId to this dock (marketId / systemAddress), with architectName set from your commander string in EDMC—normal LoadGame / journal flow must have loaded your name. The same button is used whether you are the architect (any plan row you could pick) or a helper (orbital plan rows only).

Safety checks before Create / Link

These steps reduce accidental duplicate projects when the website and game state don’t quite line up:

• The plugin asks Ravencolonial whether a build already exists for this dock. It only trusts a clear “yes, here’s the project” answer (including common buildId spellings and wrapped JSON shapes). Vague “nothing active” messages are treated as no active link—not as proof the slot is free to reuse if something is still registered on the server.
• Immediately before opening Create Build Project or starting Link Build Site, it re-checks that dock slot on the network so a build that appeared while you were still docked is detected and the flow switches to Open Build Page instead.
• Right before sending the link, it looks up your plan site again on Ravencolonial. If that site is no longer in the planning stage (construction has started or finished), linking stops and you’ll see a message instead of creating a second project.

Technical details (which journal events call which URLs): docs/ACTION_MAP_API_FLOWS.md.

Build tracker overlay and popout

The optional build tracker row is designed for commanders hauling build commodities who want current project needs visible while they work. You can render the tracker in Elite via EDMCModernOverlay, or in a separate EDMC-dark window with Popout Tracker. Both modes use the same selected project, Track All aggregation, carrier tracking, cargo data, trip footer, and Fleet Carrier jump countdown. The Ravencolonial header also has a collapse chevron to hide the rest of the plugin panel when you need more EDMC space.

Main-tab controls:

• Enable Overlay turns the in-game HUD on for a selected project. This mode requires EDMCModernOverlay.
• Popout Tracker opens the same tracker layout in a secondary EDMC-dark window. When active, Enable Overlay is hidden, and Always On is removed because the popout is a normal window. When Enable Overlay is active, Popout Tracker is hidden.
• Always On keeps the in-game HUD visible while undocked; otherwise it is intended for docked build work.
• Search lets you type a system name and refresh build projects outside your current journal system context.
• Select Build Project lists Ravencolonial rows in build status for the current or searched system, with Track All as the first active option when build rows are available.
• Enable Carrier Tracking adds an FC's column and footer line for All linked carriers or one selected carrier callsign. The refresh button beside the carrier dropdown manually reloads the selected carrier manifest from Ravencolonial, or every linked carrier when All is selected; after use it shows a live 60-second countdown before it can be clicked again.
• The overlay refresh (↻) loads build projects only; the plan-location refresh also updates this list when it has build rows.

Tracker contents:

• Build name, build type, and system/station context.
• Remaining commodities grouped under Elite market categories such as Chemicals, Foods, Industrial Materials, Machinery, and Metals.
• Need shows remaining project demand; Ship shows your current hold; FC's shows carrier surplus/deficit when carrier tracking is enabled.
• Assignment hints appear when the Ravencolonial project has commander assignments (📌 for yours, x for another commander).
• Fulfilled commodities are hidden, zero ship cargo is blank, and subtle row bands/column dividers improve readability.
• Footer shows total remaining units and estimated trips in this ship from EDMC’s current CargoCapacity; with carrier tracking it also shows the selected carrier deficit and trips.
• Fleet Carrier jump countdown (always last footer row): when you schedule a jump, shows departure time to destination, then sub-lines for jump initiation (under 10 minutes), pad lockdown (under 3m20s), and pads locked—matching BGS-Tally-style timing. Cancelling a jump shows a 60-second cooldown; the HUD ticks every second while a timer is active.
• Overlay/popout text and commodity names follow EDMC's language where plugin translations exist. For several Latin/Cyrillic locales, commodity/category names use EDDI's extracted Elite Dangerous game strings; unsupported locales fall back to English.

The popout uses the plugin's bundled Oxanium font where Tk can register it, otherwise falls back to the EDMC default font, and keeps an EDMC-dark window style no matter which EDMC theme is active. It closes when Popout Tracker is unchecked or the popout window is closed. Its last position is remembered across toggles and EDMC restarts, and it appears on the taskbar where the platform supports separate tool windows.

The popout title bar includes a copy button. It copies the current tracker as a Discord-friendly fixed-width code block, omitting the Ship column, the trips in this ship footer row, and Fleet Carrier jump-timer rows. If carrier tracking has enough data, the copied text keeps the FC deficit line so squadmates can see what still needs moving from carriers.

Track All aggregates commodity needs from every active build project in the refreshed list. Carrier tracking still supports All carriers or one callsign, and duplicate linked carriers are shown once. The overlay does not poll Ravencolonial continuously: local construction depot journal updates keep the docked project live, the carrier manifest refresh button is available as a manual fallback, and a full Track All refresh runs after qualifying construction-depot or fleet-carrier undock. Background changes made by other commanders appear after refresh or the next qualifying event-driven refresh.

Tracker themes, including Elite Orange and Cerulean Gold, are configured under File → Settings → Ravencolonial. For deeper setup and troubleshooting, see docs/OVERLAY.md.

Linux note: EDMCModernOverlay may need distro-specific troubleshooting depending on compositor, desktop environment, graphics stack, and Elite window mode. Start with Elite in borderless or windowed mode, confirm EDMCModernOverlay itself is drawing, then use docs/OVERLAY.md for plugin-specific setup.

Fleet Carriers

Link each carrier you care about (personal or squadron fleet carrier) on Ravencolonial under your commander profile so the server returns it in /fc/all or as an active-project linkedFC. With an API key set, the plugin mirrors FC trades/transfers and optional supported-hook CAPI cargo refresh. Journal cargo updates are keyed by marketId; Squadron Carriers do not use a separate cargo endpoint or an inferred Cargo snapshot resync fallback.

Commander ship snapshot

With an API key, cargo and capacity updates (after Loadout provides capacity) are sent so Ravencolonial can show your current ship loadout context alongside colonization tools.

---

Troubleshooting

• Missing RavenColonial-only log: if RavenColonial_EDMC.log is absent because the plugin folder is read-only or logging initialization failed, use the EDMC main log instead.
• RavenColonial-only log (bug reports): the plugin writes a dedicated rotating log next to its install: plugins/<RavenColonial_EDMC folder>/logs/RavenColonial_EDMC.log (for example on Windows %LOCALAPPDATA%\EDMarketConnector\plugins\RavenColonial_EDMC\logs\RavenColonial_EDMC.log). It includes main plugin messages plus API and fleet carrier module lines (not mixed into EDMC’s global log). Attach the latest file when opening a GitHub issue (redact your API key if you pasted it into chat).
• Plugin errors: EDMC main log — on Windows typically %TEMP%\EDMarketConnector\EDMarketConnector.log; on Linux/macOS typically under ~/.local/share/EDMarketConnector/ or ~/Library/Application Support/EDMarketConnector/ (see EDMC docs if your install differs).
• API / auth: confirm API key and that stealth toggles match what you intend to upload.
• Overlay on Linux: if EDMCModernOverlay works on Windows but not on your Linux distro, first verify Elite is borderless/windowed and EDMCModernOverlay can render any test overlay. Some compositor/window manager combinations need distro-specific overlay troubleshooting before this plugin's HUD can appear. Use Popout Tracker when you want the same tracker data without the external overlay stack.
• Manual install: docs/MANUAL_UPDATE_INSTRUCTIONS.md.

---

Credits

• SrvSurvey — reference colonization client by grinning2001 / njthomson.
• Ravencolonial — platform by grinning2001.
• EDMC — EDCD.
• This plugin — maintained by Fenris159; builds on earlier community work (CMDR Dirk Pitt13 / toemaus313 and related forks).

---

License

This project is licensed under the MIT License.

EDMC itself is distributed under its own terms (see the EDMarketConnector repository). This plugin’s MIT license applies to this repository’s code only.

---

Support

• Issues: github.com/Fenris159/ravencolonial_edmc/issues
• EDMC plugins: EDMC Wiki — Plugins
• Ravencolonial: ravencolonial.com

---

Version history

See CHANGELOG.md for the full record.

Version	Summary
1.8.2	Stable tracker reliability release. Rolls up selected-project cache fixes, Track All popout-only aggregation, and off-screen Popout Tracker recovery (including Reset and show Popout Tracker), and adds Tier 3: Dodec Starport (dodec / quint_truss / dec_truss) to Create Project.
1.8.2-rc.3	Popout Tracker recovery hotfix. Automatically recenters positions stranded by display changes, preserves valid multi-monitor positions, avoids persisting minimized positions, and adds Reset and show Popout Tracker in plugin settings.
1.8.2-rc.2	Track All popout hotfix. Builds the combined needs in the shared project cache so Track All works when the Popout Tracker is active without a Modern Overlay renderer.
1.8.2-rc.1	Build tracker pre-release. Project and Track All selections supersede older in-flight fetches, demand rows follow the selected cache, and depot journal/PATCH/completion updates stay scoped to the matching build id. GitHub marks this as a pre-release, and in-app update checks only offer it when Include pre-release versions is enabled.
1.8.1	Fleet Carrier cargo tracking release. Treats Squadron Carrier CargoTransfer events the same as regular linked carriers by marketId, removes the Squadron-only Cargo snapshot resync fallback to prevent double-counting, improves cargo transfer diagnostics, and keeps the rc.4 manifest editor and dock-baseline safeguards.
1.8.1-rc.4	Active-development pre-release candidate for the 1.8.1 Fleet Carrier cargo tracking, safety, and compatibility release. Adds the theme-aware Edit Carrier Manifest window, server/cache dock baselines for startup-while-docked cases, and clearer current-ship cargo debug logging. GitHub marks this as a pre-release, and in-app update checks only offer it when Include pre-release versions is enabled.
1.8.0	Popout Tracker adds an EDMC-dark secondary window with the same build tracker layout as the in-game overlay, keeps Track All/carrier controls available, uses bundled Oxanium where possible, remembers window position, appears on the taskbar where supported, dynamically resizes to content, and includes Discord-friendly copy output.
1.7.9	Auto-update integrity checks that reject incomplete update packages before restart, plus a manual-install prompt when update installation fails.
1.7.7	Fleet Carrier cargo safety release: active-project linkedFC market IDs are cargo PATCH eligible, profile/project duplicates are deduped, overlay FC cargo uses guarded local manifests plus journal deltas and a manual manifest refresh cooldown, plan-site refresh rows clear on system change, and API docs include targeted v2 site PATCH repair.
1.7.6	Hotfix: Track All appears directly below the Select Build Project placeholder, and the themed build-project dropdown no longer hides larger lists behind a fixed popup height.
1.7.5	Track All overlay mode aggregates active build-project needs and linked carriers, keeps a per-build cache, excludes completed projects, and refreshes full project details after qualifying construction-depot or fleet-carrier undock.
1.7.3	Completed-site repair now writes through targeted PATCH /api/v2/system/{nameOrNum}/sites/{siteId} with journal SystemAddress ID64 routing; name-matched MarketID repairs patch only marketId, and unique marketId-matched rows can patch only name.
1.7.2	Hotfix: fixes v1.7.1 legacy MarketID repair (name-only matching, eligibility gates, retry worker); construction-complete status asks commanders to re-dock at the finished location; locale strings updated.
1.6.5	Plan-site themed error dialog and short combobox labels; click-time location re-fetch before Create/Link; project-location cache throttling; resolve_build_id and wrapped GET /api/system/... parsing; main tab refresh after successful Create Project; docked button resolve/apply split; no client /sites merge for dock lookup; action-map docs aligned (see changelog).
1.6.4	Auto-update on Windows: release CAPI cache and issue log before folder replace (WinError 32); update banner v display; shorter error dialog text; status line wrap; Select Plan Site themed combobox (see changelog).
1.6.3	Link Build Site: architectName on PUT, /sites preflight, 404 completion hints; normalized /api/system/...; short-lived project GET cache; depot supply dedup; undock status shows station name; docs (see changelog).
1.6.2	CAPI snapshot cache (capi_cache/) for analysis; squadron fleet carrier journal tracking (SrvSurvey-style), MIT license, README refresh (see changelog).
1.6.1	Commander ship currentShip sync; three-way stealth (FC / ship cargo / construction reporting); UI in many languages (follows EDMC’s language); docs refresh.
1.6.0	Maintainer/repo handoff to Fenris159/ravencolonial_edmc, packaging and HTTP alignment, auto-update UX.

Older releases remain listed in the changelog.