Repository navigation
Replies: 6 comments 3 replies
|
Doh, forgot to add the supply_price > 0 in that one, but there's still a lot of them. |
0 replies
|
supply_level != supply_units This is an artifact from .prices and ocr days. Supply Level is Low/Medium/High and we no longer get that data. We coerce that to zero, because it's another thing on the list of "needs tidying up in schema" but we haven't had time or energy. supply_level = 0 does not mean zero units. There is a basic flaw in the whole system, starting at the API. When a commander docks (or possibly when they open the market, I forget which, but same effect) we get the market data. Then they buy stuff and leave a market which isn't the same as the data that just got uploaded. Possibly they bought the thing which the great trade, because... well, it's a great trade. If supply_units was low, perhaps they bought ALL of it. Then you rock up ten minutes later because that cool trade dropped out of the calculation and sadly, there's nothing left for you. Unless you are being given trades where supply_units = 0, then that's likely what's happened. |
2 replies
|
I realize it's different (it gets called bracket at some point), but it's consistently items that are not actually there that I'm seeing like that. However - your explanation of coersion steals the wind out of my theory, that it was being used as a secret-sauce flag. Is there some kind of gated market pricing that I'm not seeing because I haven't played enough or unlocked something or something? Usually it's things like 'Tritium' or 'Titan Drive Component' - and the weird thing was the modified times were relatively fresh, but those items were absolutely not on the station commodities market for me (at least, not to buy) |
|
Titan drive component? Those things are vanishingly rare salvage commodities required for obtaining PESCO drives. I can only even in my wildest dreams imagine those being sold at a Fleet Carrier for outrageous sums of... ah Were these trades related to fleet carriers? You also mention Tritium which of course is FC fuel. Now, if there were ever seen a Titan Drive Component for sale, I guarantee it would be snapped up SO FAST you wouldn't see it for dust. See the wiki on the subject What you still didn't say though is what supply_units said about these trades. Was it a small number? If this was fleet carrier stuff, I strongly advise excluding them from your trading, as I do. So you need to look at and tell me what is being said in supply_units, not supply_level and if it is fleet carriers, just say --fc n, that's my advice. |
|
TODO: Remove supply and demand levels from the schema |
1 reply
|
Ok, I found an instance of this. I'm at HIP 31666/Shunkai Orbital. 
But the database: 
|
or ok - so - it looks eddblink, at least, should not be importing values where units is 0 on both sides? |
0 replies
|
we should also be forcefully setting price to 0 when units and level are 0? (in eddblink?) |
0 replies
|
Fixed a couple issues I was having - mostly that data/db_config.ini was last-minute redirecting my python database access to the place I'd copied everything over from, doh - and now I can see this: 
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
A couple of times, I've managed to get a route that looked stunning only to find the items weren't listed and when I checked the TD data, I noticed they're consistently supply_level==0.
All reactions