Update Journal docs for v3.4

not sure if bug reports for the Journal API go in this forum or on the new issue tracker, but I have found one with the
ApproachSetllement event. Recently the event was updated to contain latitude and longitude, which is nice for the mapping tool i'm working on. However, when starting up the game already landed on a planet, it seems to not have this info present.


{ "timestamp":"2019-05-22T02:17:15Z", "event":"ApproachSettlement", "Name":"$Ancient_Medium_003:#index=1;", "Name_Localised":"Guardian Structure", "SystemAddress":3309179996515, "BodyID":35, "BodyName":"Synuefe EN-H d11-96 7 a" }
 
Issue with "Fuel Low" flag in status.json when in SRV.

This flag is set depending on "FuelMain" key value being less than 25% of the main ship's fuel capacity.
When in SRV this value is always 0 and therefore the flag is always set.
The "Fuel Low" flag should use the SRV Reservoir% (when in SRV).

Clicker
 
not sure if bug reports for the Journal API go in this forum or on the new issue tracker, but I have found one with the
ApproachSetllement event. Recently the event was updated to contain latitude and longitude, which is nice for the mapping tool i'm working on. However, when starting up the game already landed on a planet, it seems to not have this info present.


{ "timestamp":"2019-05-22T02:17:15Z", "event":"ApproachSettlement", "Name":"$Ancient_Medium_003:#index=1;", "Name_Localised":"Guardian Structure", "SystemAddress":3309179996515, "BodyID":35, "BodyName":"Synuefe EN-H d11-96 7 a" }
@Controllerface ...

Work-around might be to use status.json file which does have latitude/longitude on startup (where appropriate) until they fix this?

Clicker
 
@Controllerface ...

Work-around might be to use status.json file which does have latitude/longitude on startup (where appropriate) until they fix this?

Clicker
Thanks, I ended up falling back to status.json later that day. I hope they open a proper bug forum for this portion of the game. I don't think they have a lot of people on this API though, so I doubt they will be able to be as reactive to requests for changes. Which is a shame, but I understand as a dev.
 
The MultiSellExplorationData event is broken. The array of discovered systems has blank names for all but the last one listed. Also with this new format, there doesn't seem to be any way to know which individual bodies you got discovery credit for, just the total number. I sold all my DW2 data last night, and this is a representative entry:

{ "timestamp":"2019-07-07T03:58:06Z", "event":"MultiSellExplorationData", "Discovered":[ { "SystemName":"", "NumBodies":27 }, { "SystemName":"", "NumBodies":15 }, { "SystemName":"", "NumBodies":2 }, { "SystemName":"", "NumBodies":1 }, { "SystemName":"", "NumBodies":1 }, { "SystemName":"", "NumBodies":2 }, { "SystemName":"", "NumBodies":3 }, { "SystemName":"", "NumBodies":19 }, { "SystemName":"", "NumBodies":4 }, { "SystemName":"", "NumBodies":3 }, { "SystemName":"", "NumBodies":15 }, { "SystemName":"", "NumBodies":1 }, { "SystemName":"", "NumBodies":13 }, { "SystemName":"", "NumBodies":34 }, { "SystemName":"", "NumBodies":25 }, { "SystemName":"", "NumBodies":23 }, { "SystemName":"", "NumBodies":10 }, { "SystemName":"", "NumBodies":2 }, { "SystemName":"", "NumBodies":12 }, { "SystemName":"", "NumBodies":8 }, { "SystemName":"", "NumBodies":27 }, { "SystemName":"", "NumBodies":4 }, { "SystemName":"", "NumBodies":1 }, { "SystemName":"", "NumBodies":23 }, { "SystemName":"", "NumBodies":4 }, { "SystemName":"", "NumBodies":4 }, { "SystemName":"", "NumBodies":13 }, { "SystemName":"", "NumBodies":2 }, { "SystemName":"", "NumBodies":9 }, { "SystemName":"", "NumBodies":11 }, { "SystemName":"", "NumBodies":8 }, { "SystemName":"", "NumBodies":1 }, { "SystemName":"", "NumBodies":12 }, { "SystemName":"", "NumBodies":48 }, { "SystemName":"", "NumBodies":2 }, { "SystemName":"", "NumBodies":9 }, { "SystemName":"", "NumBodies":23 }, { "SystemName":"", "NumBodies":19 }, { "SystemName":"", "NumBodies":1 }, { "SystemName":"", "NumBodies":31 }, { "SystemName":"", "NumBodies":54 }, { "SystemName":"", "NumBodies":11 }, { "SystemName":"", "NumBodies":2 }, { "SystemName":"", "NumBodies":1 }, { "SystemName":"", "NumBodies":1 }, { "SystemName":"", "NumBodies":4 }, { "SystemName":"", "NumBodies":28 }, { "SystemName":"", "NumBodies":21 }, { "SystemName":"", "NumBodies":9 }, { "SystemName":"Eowrairks EB-E d12-0", "NumBodies":12 } ], "BaseValue":29702006, "Bonus":2809455, "TotalEarnings":29260336 }
 
Please add a status flag or other signal for glide mode? (we used to be able to detect this from a mass lock that occurred when entering normal space at the beginning of a glide, but mass lock no longer occurs in this circumstance)
 
For status.json, the Hud in Analysis mode flag should be set when toggling analysis mode while in an SRV but at present the flag is always off/false while in an SRV.
 
Hello everyone!

Another flag request here... I'm trying to teach my own voice assistant to launch off the pad, slide up for a while and give the controls back to player. Or, if docking computer is installed, just rely on it and do nothing.

I can check the existence of advanced docking computer, but there's no way to tell if landing/takeoff assist is actually enabled in the menu! That actually breaks the logic...

The simplest solution is to add another flag to status.json: something like docking_assist, and set it when auto docking or auto launch is in progress.

Perhaps I'm not the first to ask this? Anyway, thanks for this wonderful Journal API, I'm having sooo much fun with it! :)
 
I'm new to the Elite tools scene and barely started delving into the journal and such, so I could be wrong, but... seems like the station bounty boards are not written to the journal? I was looking into building something aggregating bounty information, but apparently the bounty information is only present when the player scans someone? Getting the station bounty board information would be so much more useful.
 
I'm new to the Elite tools scene and barely started delving into the journal and such, so I could be wrong, but... seems like the station bounty boards are not written to the journal? I was looking into building something aggregating bounty information, but apparently the bounty information is only present when the player scans someone? Getting the station bounty board information would be so much more useful.
Bounty board information would be very useful in station jsons indeed.
 
Top Bottom