-
Notifications
You must be signed in to change notification settings - Fork 31
CookBook
Please note; the first line always has everything written out fully, the following variants are short-cuts to do the same thing, this is followed by some additional options that can make the output more useful.
Recipes:
Use local with "--ly 0". So if you wanted to see Sol, you might use:
$ trade.py local sol --ly 0 -vv
System Dist
/ Station Dist Age/days BMkt Pad Itms
-----------------------------------------------------------------------
SOL 0.00
/ Abraham Lincoln 506ls 4.32 ? Lrg 26
/ Burnell Station 364ls 4.22 ? ? 55
/ Columbus 2474ls 4.08 ? ? 54
/ Daedalus 225ls 4.02 ? Lrg 55
/ Galileo 505ls 0.01 No Lrg 55
/ Li Qing Jao 506ls 4.25 ? Lrg 26
/ M.Gorbachev 506ls 0.00 No Lrg 26
/ Mars High 699ls 4.30 ? ? 26
/ Titan City 4589ls 4.19 ? ? 55
If you are using the Bash Scripts, this is tdloc sol 0 -vv.
We can use the "--unique" option to run and --jumps 0 to tell it not to make any inter-system jumps.
Lets say you're in Sol, where there are 9 stations, which means 8 hops. We can either specify a starting station:
$ trade.py run --jumps 0 --capacity 50 --credits 40000 --from "mars high" --hops 8 --unique
or better still we can let TD do its thing and find the most profitable route, including which station we start from:
$ trade.py run --ju 0 --cap 50 --cr 40000 --from sol --hops 8 --uni -vv
SOL/Daedalus -> SOL/Mars High:
Load from SOL/Daedalus:
49 x Titanium 801cr each, 39,249cr total (4days)
1 x Copper 329cr each, 329cr total (4days)
Unload at SOL/Columbus (2,474ls) => Gain 7,333cr (146.66cr/ton) => 47,333cr
Load from SOL/Columbus:
9 x Silver 4,867cr each, 43,803cr total (4days)
Unload at SOL/M.Gorbachev (506ls) => Gain 5,571cr (619cr/ton) => 52,904cr
Load from SOL/M.Gorbachev:
50 x Hydrogen Fuel 124cr each, 6,200cr total (4days)
Unload at SOL/Burnell Station (364ls) => Gain 50cr (1cr/ton) => 52,954cr
Load from SOL/Burnell Station:
36 x Lithium 1,434cr each, 51,624cr total (4days)
5 x Aluminium 248cr each, 1,240cr total (4days)
Unload at SOL/Galileo (505ls) => Gain 3,278cr (79.9512cr/ton) => 56,232cr
Load from SOL/Galileo:
11 x Silver 4,914cr each, 54,054cr total (4days)
Unload at SOL/Abraham Lincoln (506ls) => Gain 4,312cr (392cr/ton) => 60,544cr
Load from SOL/Abraham Lincoln:
50 x Hydrogen Fuel 113cr each, 5,650cr total (4days)
Unload at SOL/Titan City (4,589ls) => Gain 1,550cr (31cr/ton) => 62,094cr
Load from SOL/Titan City:
12 x Silver 4,925cr each, 59,100cr total (4days)
Unload at SOL/Li Qing Jao (506ls) => Gain 1,056cr (88cr/ton) => 63,150cr
Load from SOL/Li Qing Jao:
50 x Hydrogen Fuel 100cr each, 5,000cr total (4days)
Unload at SOL/Mars High (699ls) => Gain 1,250cr (25cr/ton) => 64,400cr
----------------------------------------------------------------------------
Finish at SOL/Mars High gaining 24,400cr => est 64,400cr total
If you are using Bash Scripts: tdrun sol --ju 0 --hops 8 --uni
Assuming you are in 'Lave':
$ trade.py local --ly=8 "@Lave"
$ trade.py local --ly 8 lave
System Dist
----------------------
ALPHA CENTAURI 0.00
LUHMAN 16 3.65
WISE 0855-0714 4.22
SOL 4.38
BARNARD'S STAR 6.49
Note: Specifying a Station is equivalent to specifying the system it is in,
$ trade.py local --ly=0 "@Mokosh" --detail
$ trade.py local --ly 0 mokosh -v
System Dist
/ Station Dist Age/days BMkt Pad
------------------------------------------------------------------
MOKOSH 0.00
/ Bethe Station 2500ls 8.27 Y M
/ Lubin Orbital ? 0.86 ? ?
-
There are two stations in the system, someone has reported the distance to Bethe Station as being 2500ls from the nav beacon.*
-
The data for Bethe is over 8 days old, it has a confirmed black market but can only accomodate ships that need small/medium landing pads.*
-
Lubin Orbital's distance is unknown, its data is less than a day old, but we don't know if it has a black market or what pad size it supports.*
-
You want to make a trade run (in your brand spanking new Asp with no insurance) that will take you on a circular route back to your origin. This can be done fairly easily, with various options available.
-
Simply put, you can use the same system as a origin and destination. You can then use the --via and --avoid options, along with --hops and --jumps, as well as --unique, to either precisely define the route you want, or let TD pick the systems you visit and what order. For example, this will give you a roughly circular route around Alioth, about 2 jumps in radius. --progress gives us a display so we can see that something really is happening in there ... .:
$ trade.py run -vv --ly=14.18 --empty=15.92 --cap=52 --cr=268224 --from="alioth" --via lagunnosso --to alioth --hops 7 --jumps 2 --progress
Gives us:
* Hop 1: .........6 origins
* Hop 2: .......119 origins
* Hop 3: .......249 origins
* Hop 4: .......485 origins
* Hop 5: .......869 origins
* Hop 6: .....1,511 origins
* Hop 7: .....2,302 origins
ALIOTH/Golden Gate -> ALIOTH/Donaldson (score: 457097.461440)
Load from ALIOTH/Golden Gate (7.8Kls/star, No/bm, Lrg/pad):
49 x Resonating Separators 5,401cr vs 6,615cr, 11 days vs 18 hrs
2 x Non-Lethal Weapons 1,557cr vs 2,188cr, 11 days vs 18 hrs
1 x Microbial Furnaces 104cr vs 334cr, 11 days vs 18 hrs
Jump ALIOTH -> BEI DOU SECTOR EB-X B1-2 -> HR 5451
Unload at HR 5451/MacDonald Hub (362ls/star, Yes/bm, Lrg/pad) => Gain 60,978cr (1,172.65cr/ton) => 329,202cr
Load from HR 5451/MacDonald Hub (362ls/star, Yes/bm, Lrg/pad):
52 x Superconductors 6,191cr vs 7,516cr, 18 hrs vs 35 hrs
Jump HR 5451 -> BEI DOU SECTOR FW-W B1-1 -> G 224-46
Unload at G 224-46/Zebrowski Ring (no details) => Gain 68,900cr (1,325cr/ton) => 398,102cr
Load from G 224-46/Zebrowski Ring (no details):
52 x Silver 4,501cr vs 5,434cr, 35 hrs vs 5 days
Jump G 224-46 -> ALYUTO -> 78 URSAE MAJORIS
Unload at 78 URSAE MAJORIS/Arrhenius Orbital (660ls/star, No/bm, Med/pad) => Gain 48,516cr (933cr/ton) => 446,618cr
Load from 78 URSAE MAJORIS/Arrhenius Orbital (660ls/star, No/bm, Med/pad):
43 x Slaves 10,159cr vs 11,771cr, 5 days vs 17 days
7 x Water Purifiers 182cr vs 458cr, 5 days vs 3 days
2 x Personal Weapons 4,031cr vs 4,842cr, 5 days vs 17 days
Jump 78 URSAE MAJORIS -> AMBER -> OLWAIN
Unload at OLWAIN/Cabot Hub (959ls/star, Yes/bm, Lrg/pad) => Gain 72,870cr (1,401.35cr/ton) => 519,488cr
Load from OLWAIN/Cabot Hub (959ls/star, Yes/bm, Lrg/pad):
52 x Gold 8,883cr vs 10,299cr, 3 days vs 5 days
Jump OLWAIN -> AMBER -> 78 URSAE MAJORIS
Unload at 78 URSAE MAJORIS/Arrhenius Orbital (660ls/star, No/bm, Med/pad) => Gain 73,632cr (1,416cr/ton) => 593,120cr
Load from 78 URSAE MAJORIS/Arrhenius Orbital (660ls/star, No/bm, Med/pad):
52 x Slaves 10,159cr vs 11,842cr, 5 days vs 19 days
Jump 78 URSAE MAJORIS -> DO CANUM VENATICORUM -> LAGUNNOSSO
Unload at LAGUNNOSSO/Bulgarin Terminal (424ls/star, No/bm, Med/pad) => Gain 87,516cr (1,683cr/ton) => 680,636cr
Load from LAGUNNOSSO/Bulgarin Terminal (424ls/star, No/bm, Med/pad):
52 x Silver 4,321cr vs 5,207cr, 13 days vs 36 days
Jump LAGUNNOSSO -> DO CANUM VENATICORUM -> ALIOTH
Unload at ALIOTH/Donaldson (4.7Kls/star, No/bm, Lrg/pad) => Gain 46,072cr (886cr/ton) => 726,708cr
----------------------------------------------------------------------------
Finish at ALIOTH/Donaldson (4.7Kls/star, No/bm, Lrg/pad) gaining 458,484cr => est 726,708cr total
-
If you use --via you need to ensure that you have at least as many hops as you have systems listed in --via
-
--unique and --avoid are also useful in helping to define your route more precisely
-
Please kids, don't try this at home without using the --insurance option
The following options (everything below here) should be considered deprecated.
In the early days of E:D we did not have tools which hooked directly into the API for easy and automatic
uploading of price and navigation data. We would highly recommend using a tool such as Elite Dangerous Market Connector (EDMC)
or EDDiscovery to add to the EDDN crowdsourced pricing database.
The commands listed below reflect the state of play circa 2015 and a lot has changed since then.
When you use the update command with either a text editor or
the built-in UI, a text file called updated.prices is created:
$ trade.py update -GF WhiteOrbital
NOTE:
. The Update UI is still somewhat experimental.
. Press CTRL-C here to abort editing, or else just close the window to save.
. Use '-q' to hide this message,
. '-F' to make the update window appear infront of Elite: Dangerous (Windowed),
. '-A' to force all items to show if stuff is missing from a station.
< you make your edits >
- Copy of changes saved as 'updated.prices'
You should be able to upload this file to your favorite site.
When you use one of the text-editor options to update, e.g.
C:\Dev\Trade\> trade.py update --notepad whiteorb
It creates a temporary file, prices.tmp, which you can edit
and import:
C:\Dev\Trade\> trade.py update --notepad whiteorb
< you accidentally type 'herp' into a demand column >
ERROR: prices.tmp:19 Unrecognized line/syntax,
got: 'Hydrogen Fuel 102 107 derp ?'.
*** YOUR UPDATES WILL BE SAVED AS prices.last ***
To recover, edit the file with a text editor and use the
import command to load the data.
C:\Dev\Trade\> start notepad prices.last
< edit the data >
C:\Dev\Trade\> trade.py import prices.last
Caveat Emptor - Buyer Beware
This is an area where TradeDangerous needs some improvement, work which is unlikely to ever happen.
To add a station to your local system, use the station sub-command.
$ trade.py station --add i bootis / fake port --ls-from-star 1234 --blackmarket y --pad m
or for short
$ trade.py station -a i bootis/fake port --ls 1234 --bm y --pad m
If you know them, you can specify the station's distance from it's host start (--ls-from-star or --ls for short), indicate whether it has a black market (--blackmarket or --bm with a value of 'Y' if you know it has a black market or 'N' if you know it doesn't) or specify the maximum pad size the station supports (--pad with a value of 'S' for small, 'M' for medium or 'L' for large).
Beware: This is one of the few times where TD requires you to enter the complete station name accurately.
Note that you don't have to use the long switch names TD is very aggressive at doing best-guess matching.
$ trade.py st -a --ls 123 "sys/stn" (don't know the bm or pad)
$ trade.py st -u --bm y "sys/stn" (just want to update the bm flag)
If you are adding a station that looks roughly similar to an existing station, you may be told to use a confirmation code.
$ trade.py station --add i bootis/chinga
./trade.py: ERROR: "I BOOTIS" contains similar station names:
CHANGO DOCK
If you want to add this station anyway, re-run the command and add:
--conf 3C29
Do exactly as the messages suggests, it is not case sensitive:
$ trade.py station --add i bootis/chinga --conf 3c29
**N.B. This only updates your local .db and .csv files; if you overwrite your .csv file later without first contributing your additions, your changes will be lost
Users who choose to obtain their .csv files from other sources - such as eddb - should check whether that source has a mechanism for contributing additions. eddb, for instance, allows you to edit systems using the ROSS backend.**
This is an area where TradeDangerous needs some improvement, work which is unlikely to ever happen.
So you've noticed that the "Oliver Station" in "SMITH" system is actually 100ls from the star, not 10,000; or perhaps you've visited a station that had '?' for the pad or blackmarket values and you want to correct that?
You can use the station --update command (or station -u for short):
$ trade.py station --update smith / oliver station --ls-from-star=100
or for short
$ trade.py station -u smith/oliver station --ls 100
This is an area where TradeDangerous needs some improvement, work which is unlikely to ever happen.
To add a station to your local system, use the station sub-command.
$ trade.py station --remove i bootis / fake port
or for short
$ trade.py station -rm i bootis/fake port