Plugin Options

---

Currently supported TD import plugins are eddblink and spansh.

For nearly all end users, eddblink is the recommended choice.

spansh is fully supported and an important current part of the TD ecosystem, especially for bulk/server-side authoritative imports, but it is usually slower and less convenient for ordinary user machines.

edmc_batch still works for legacy .prices workflows, but it is deprecated. Solo players (people who only want TD to reflect their own travels) should now prefer bgol's UpdateTD plugin for EDMarketConnector (EDMC).

At time of writing edmc_batch has received its last compatibility fix. If future changes cause it to cease correct function, it will be dropped. As of now, this plugin is unsupported and is subject to the same disclaimer as "Other plugins" below.

Other plugins are included "as is"; use them at your own risk.

---

You can get plugin-specific help at any time with:

trade import -P <plugin> -O help

EDDBlink

Despite the historical name, eddblink no longer talks to EDDB. The old EDDB website is now defunct, but we continued to supply files in the same format, so that users could continue with their existing workflow. This has now become our standard import plugin and we've kept the name. It updates TD using data files served from Tromador's Trading Dangerously server, including listings derived from TD's current import pipeline.

For nearly all end users, this is the recommended import plugin.

Basic usage:

trade import -P eddblink
  The normal/recommended update path for most users.

trade import -P eddblink -O all
  Refresh everything from the current server-side dump files.

trade import -P eddblink -O all,skipvend
  Like `-O all`, but skips the vendor tables. This can help on slower machines.

trade import -P eddblink -O clean,skipvend
  Wipes the database and rebuilds it from the downloaded files.
  This is the "nuclear option" and is only for when you really mean it.

trade import -P eddblink -O solo
  Refreshes the static/reference data without downloading crowd-sourced
  market listings.

Recommended usage

For most users:

trade import -P eddblink

That is usually all you need.

Use -O all when there have been significant game-data changes, or when you want to force a full metadata refresh.

On slower computers, skipvend can save a lot of time.

-O clean completely rebuilds the database from scratch. Use it only if you really want to wipe and rebuild everything.

-O solo is for users who do not want crowd-sourced market listings. If you are building a personal database from your own travels, that can be useful for the static tables, but for the actual market-data workflow we now recommend EDMC + UpdateTD instead of the old .prices path.

Options (-O)

item
  Update Items from the current server files.
  (Implies `system,station`.)

ship
  Update Ships from the current server files.

system
  Update Systems from the current server files.

station
  Update Stations from the current server files.
  (Implies `system`.)

shipvend
  Update ShipVendors from the current server files.
  (Implies `system,station,ship`.)

listings
  Update market data from the current listings dump.
  (Implies `item,system,station`.)

all
  Update everything from the current dump files.

clean
  Erase the database and rebuild it from scratch from the current dump files.

skipvend
  Skip ShipVendor regeneration.

force
  Force regeneration even if TD thinks the source files have not changed.

purge
  Remove empty systems that previously held fleet carriers.

optimize
  Vacuum/optimize the database after processing.

solo
  Do not download crowd-sourced market data.
  (Also implies `skipvend` and overrides `all`, `clean`, and `listings`.)

7days
  Ignore listing data older than 7 days and expire old records after import.

units
  Treat listing entries with zero units as unavailable, zeroing the corresponding
  demand/supply price.

Spansh

The Spansh plugin imports market/station data from the Spansh galaxy dump, currently:

https://downloads.spansh.co.uk/galaxy_stations.json

spansh is fully supported.

It is an important part of the modern TD ecosystem, especially for bulk refreshes, server-side processing, and authoritative resets of data. It is not, however, usually the best choice for ordinary end users: the dump is very large, imports can take a long time, and eddblink is a better fit for most day-to-day use.

Basic Usage

# download and import the current dump from the default location:
trade import -P spansh

# download the data from an alternate location:
trade import -P spansh -O url=https://example.com/alternate/source/galaxy_stations.json

# import the data from a previously downloaded file:
trade import -P spansh -O file=previously/downloaded/galaxy_stations.json

# ignore service entries older than a given number of days:
trade import -P spansh -O maxage=7

Notes

• For most users, prefer eddblink.
• spansh is still a perfectly valid import path if you explicitly want a full bulk import from the Spansh dump.
• Advanced/server-oriented options exist; use trade import -P spansh -O help for the current full list.

Common Options (-O)

url=<URL>
  Download the dump from the specified URL instead of the default one.

file=<PATH>
  Import from a local dump file instead of downloading it.

maxage=<days>
  Skip per-service data older than the specified age in days.

Everything else should be considered advanced/special-purpose; use -O help if you need it.

EDMC_Batch

edmc_batch exists to support the old .prices workflow.

This is mainly relevant for so-called "solo" players: people who do not want a large shared market database and instead want TD to reflect only their own travels and discoveries.

EDMarketConnector (EDMC) can still read market data from the game and write .prices files from it. Those files can then be imported into TD.

That workflow still works, but it is now considered deprecated.

Strong Recommendation For Solo Players

If you want a TD database built from your own journeys rather than from crowd-sourced listings, the preferred modern solution is now UpdateTD, Bernd "Gazelle" Gollesch's EDMC plugin.

It updates a TD database directly, without using .prices as an intermediate format, and is the route we now recommend to solo/self-curated users.

Use edmc_batch only if you specifically want or need the older .prices workflow.

What edmc_batch does

This plugin imports multiple EDMC-generated .prices files at once, either by passing:

• a list of files,
• a folder containing multiple files,
• or both.

It only works with files that contain one and only one station per file, which is the format EDMC typically generates.

If you only have a single .prices file, you do not need edmc_batch; you can just use the normal import command:

trade import somefile.prices

Options

edmc_batch accepts two options:

files
  A `;` separated list of `.prices` files to import.

folder
  A folder containing `.prices` files to import.

For both options, if the folder or any of the files contain spaces in the path, quote the whole value.

Examples

trade import -P edmc_batch -O files=test.prices
trade import -P edmc_batch -O files=test.prices;..\test2\test2.prices
trade import -P edmc_batch -O files="test.prices;..\test2\test2.prices;..\test3\test with space.prices"
trade import -P edmc_batch -O folder=C:\Users\eyeonus\Documents\EDMC
trade import -P edmc_batch -O folder="L:\custom EDMC logging folder"
trade import -P edmc_batch -O folder=C:\Users\eyeonus\Documents\EDMC -O files="test.prices;..\test2\test2.prices;..\test3\test with space.prices"

Other plugins

A few other import plugins are still present in the repository, but they are not supported.

If they work for you, great. If they don't, you are very much on your own.

journal

journal reads the local live market JSON and imports the values it finds.

Basic usage:

trade import -P journal

It does not support any plugin options.

edcd

edcd downloads and processes EDCD CSV files.

Basic usage:

trade import -P edcd -O csvs

Supported options are:

local
  Use local EDCD CSV files.

shipyard
  Download/process `shipyard.csv`.

commodity
  Download/process `commodity.csv`.

outfitting
  Download/process `outfitting.csv`.

csvs
  Download/process all supported EDCD CSV files.

For normal users, this plugin should not be necessary. Current supported workflows already ship the needed reference data through the supported import paths.

Older docs and removed plugins

Older copies of this page may mention plugins such as edapi or netlog.

Those are not current TD import plugins and should be considered obsolete for present-day TD documentation.