Build Project Workflow

Build Project Workflow

This guide explains the normal player-facing project flow from EDMC.

What the Plugin Does

The plugin watches Elite Dangerous journal events and EDMC state while you work on colonization construction. It can:

• detect the docked construction project location
• create a RavenColonial build project from the depot snapshot
• link a RavenColonial plan location to the docked construction site
• update remaining project need from ColonisationConstructionDepot
• report commander contribution history from ColonisationContribution
• mark projects complete when completion is detected
• repair completed site Market Info after you re-dock at the finished location

Open Existing Build Project

When you dock at a construction site, the plugin probes RavenColonial for an existing project at the current system and market.

If a project exists, the main action becomes Open Build Page.

Use this when:

• the project already exists on RavenColonial
• you want to open the website page for the current dock
• you are delivering cargo to an active project

Create Build Project

Use Create Build Project when no existing project is found and you want to create a new project from the docked construction depot.

Before creating:

1. Dock at the construction ship.
2. Wait for EDMC to receive the depot journal data.
3. Confirm the plugin has the current system and station context.
4. Open the create dialog.
5. Choose construction type, model, and project name.

The create payload includes:

• system and market context
• commander name
• project name and build type
• depot snapshot from the journal
• remaining commodity need
• maximum need total

Link Build Location

Use Link Build Location when a RavenColonial plan location already exists and you are docked at the matching construction site.

Typical flow:

1. Dock at the construction ship.
2. Press plan-location refresh.
3. Choose the correct plan location.
4. Use Link Build Location.
5. The plugin creates the active project using the plan row plus the live depot snapshot.

The link worker performs live safety checks before it writes:

• the selected plan row must still be in plan status
• the dock location must not already have an active or completed project record
• the selected plan row must have enough data to create the build project

How Remaining Need Updates

The plugin treats the journal depot event as the source of truth for remaining need.

When ColonisationConstructionDepot changes, the plugin calculates:

remaining = RequiredAmount - ProvidedAmount

Then it PATCHes the project with:

• colonisationConstructionDepot
• commodities
• maxNeed

This is why the plugin does not use the web-style supply endpoint for journal-driven delivery. The depot journal already tells the truth about remaining need.

How Contribution History Updates

Contribution history is separate from remaining need.

When the game emits ColonisationContribution, the plugin reports commander contribution history to RavenColonial.

That contribution call does not reduce remaining need. Remaining need is handled by the depot PATCH described above.

Completed Sites and Market Info Repair

After construction completes, the finished station may need a final re-dock so RavenColonial can learn the finished station's MarketID or updated name.

The plugin can repair eligible completed site rows when:

• you dock at the finished station
• the journal MarketID is a player-colony style station MarketID
• the RavenColonial site row is complete or statusless
• the plugin can match exactly one eligible row safely

The repair uses targeted site PATCH behavior and avoids plan/build rows.