Update Journal docs for v3.4

FWIW , It would be nice if the false declarations of various faction states could be eliminated from the log
My program adds comments and/or changes colors of relevant factions cells in the excel workbook that it manages and the continual errors of various states being reported in the log tends to mess it up and I sometimes have to view the log to see why and have seen numerous instances where it reports 1 faction in a conflict that does not in fact exist in said system.
even had a premonition one recently where on the 1st day of a pending election the log reported it as ongoing and listed the stakes, that was kind of neat knowing ahead of time but it was still wrong.
 
Can we also have a status.json flag for when we are in MultiCrew mode and when Landing overrides are active please?
 
Hi @hchalkley ,

I notice a couple of changes to the journal + status.json were included in the September release.
Will a new version of the journal doc be published here?

Is there a link to an updated doc I can access otherwise?

Cheers
Clicker
 
Hi @hchalkley ,

I notice a couple of changes to the journal + status.json were included in the September release.
Will a new version of the journal doc be published here?

Is there a link to an updated doc I can access otherwise?

Cheers
Clicker
Journal was at version 26 the last time I saw (posted on EDDN discord on 20th August)
http://hosting.zaonce.net/community/journal/v26/Journal-Manual-v26.pdf
http://hosting.zaonce.net/community/journal/v26/Journal-Manual-v26.doc
 
Thanks @BravadaCadelanne ,

a) Do you have a discord invite please?
(never mind, it's EDCD now, which I am already in)

b) As bit 4 represents "Supercruise", can I safely assume bit 30 (fsdJump) represents a Hyper/System jump?

Thanks
Clicker
 
Last edited:
An implicit effect appeared in the September update.
In the status.json file, Parameters - Flags - bit 21 (HasLatLong) is on, when the ship is inside the orbital station.
Should it be? Or is it bug?
 
Last edited:
has anyone got an example of the PowerplayVoucher Event .. the info in the docs is extremely poor and since I currently don't play powerplay it would be handy :) thanks in advance
 
has anyone got an example of the PowerplayVoucher Event .. the info in the docs is extremely poor and since I currently don't play powerplay it would be handy :) thanks in advance
you mean this ?
{ "timestamp":"2019-09-26T20:17:04Z", "event":"PowerplayJoin", "Power":"Denton Patreus" }

{ "timestamp":"2019-10-01T11:36:37Z", "event":"Powerplay", "Power":"Denton Patreus", "Rank":0, "Merits":0, "Votes":0, "TimePledged":400773 }
 
you mean this ?
{ "timestamp":"2019-09-26T20:17:04Z", "event":"PowerplayJoin", "Power":"Denton Patreus" }

{ "timestamp":"2019-10-01T11:36:37Z", "event":"Powerplay", "Power":"Denton Patreus", "Rank":0, "Merits":0, "Votes":0, "TimePledged":400773 }
Nope i'm afraid not .. its the one containing "event":"PowerplayVoucer" - the documentation says "When recieveing payment for powerplay combat"
 
Nope i'm afraid not .. its the one containing "event":"PowerplayVoucer" - the documentation says "When recieveing payment for powerplay combat"
i'm not a real PP player
currently, i'm with Denton Patreus (waiting to buy some advanced PA) and i don't know how to fight for this power,
if you tell me how to do that (combat merits ?), i'm willing to give it a try and send you the interesting lines of my journal.log :)
 
@hchalkley

Thanks for putting the number of remaining jumps of a route in the journal.
Would it also be possible to put the name of the final destination in.
For example I'm now at Luyten's Star.
When I select Khun the FSDTarget event reads:
Code:
{ "timestamp":"2019-10-30T17:16:26Z", "event":"FSDTarget", "Name":"Khun", "SystemAddress":3107241104074 }
but then when I plot a route to Khun it reads:
Code:
{ "timestamp":"2019-10-30T17:16:35Z", "event":"FSDTarget", "Name":"Sopdu", "SystemAddress":670149191065, "RemainingJumpsInRoute":4 }
The "Name" variable now contains the name of the first system on the route. It would be nice if the final system is also put in a variable, maybe something like this:
Code:
{ "timestamp":"2019-10-30T17:16:35Z", "event":"FSDTarget", "Name":"Sopdu", "SystemAddress":670149191065, "RemainingJumpsInRoute":4,"FinalSystemInRoute":"Khun" }
 
Top Bottom