Discussion Journal Docs for v3.3

East Riding

E
Howard, would it be possible to have an event for when we target a body in the navigation panel, system map/orrery or when in flight.


Something like -


{ "timestamp":"2018-11-15T00:45:03Z", "event":"TargetBody", "StarSystem":"31 d1 Virginis", "SystemAddress":181699355828, "Body":"31 d1 Virginis 10 a", "BodyID":42 }


Many thanks.
 

dobbo

dobbo
Hi Howard

Thanks for the update to the journal document.

I was looking through the new exploration stuff and found something confusing.

The new MultiSellExplorationData event works as expected, BaseValue + Bonus = TotalEarnings,
but I found in my SellExplorationData events that this was not the case when Bonus was non-zero.

Here are a few examples (selling as Cmdr OBBOD

{ "timestamp":"2018-11-22T09:39:02Z", "event":"SellExplorationData", "Systems":[ "Wregoe SZ-O c19-2" ], "Discovered":[ "Wregoe SZ-O c19-2 C", "Wregoe SZ-O c19-2 C 4", "Wregoe SZ-O c19-2 C 7", "Wregoe SZ-O c19-2 C 2", "Wregoe SZ-O c19-2 C 6", "Wregoe SZ-O c19-2 C 3", "Wregoe SZ-O c19-2 C 5", "Wregoe SZ-O c19-2 C 1", "Wregoe SZ-O c19-2 AB 1", "Wregoe SZ-O c19-2 C 1 a", "Wregoe SZ-O c19-2 A", "Wregoe SZ-O c19-2 B" ], "BaseValue":27153, "Bonus":22182, "TotalEarnings":39153 }

{ "timestamp":"2018-11-22T09:39:16Z", "event":"SellExplorationData", "Systems":[ "Synuefe RF-L d9-19" ], "Discovered":[ "Synuefe RF-L d9-19 1", "Synuefe RF-L d9-19 2", "Synuefe RF-L d9-19 5", "Synuefe RF-L d9-19", "Synuefe RF-L d9-19 3", "Synuefe RF-L d9-19 4", "Synuefe RF-L d9-19 8", "Synuefe RF-L d9-19 6", "Synuefe RF-L d9-19 7" ], "BaseValue":953196, "Bonus":366446, "TotalEarnings":962196 }

{ "timestamp":"2018-11-22T09:39:40Z", "event":"SellExplorationData", "Systems":[ "Synuefe BQ-Y b20-0" ], "Discovered":[ "Synuefe BQ-Y b20-0 3", "Synuefe BQ-Y b20-0 4", "Synuefe BQ-Y b20-0", "Synuefe BQ-Y b20-0 1" ], "BaseValue":85673, "Bonus":32127, "TotalEarnings":85673 }

{ "timestamp":"2018-11-22T09:39:47Z", "event":"SellExplorationData", "Systems":[ "Synuefe AW-D b32-0" ], "Discovered":[ "Synuefe AW-D b32-0" ], "BaseValue":1928, "Bonus":1723, "TotalEarnings":2928 }

{ "timestamp":"2018-11-22T09:39:56Z", "event":"SellExplorationData", "Systems":[ "Col 140 Sector ZZ-W b2-0" ], "Discovered":[ "Col 140 Sector ZZ-W b2-0 B 2", "Col 140 Sector ZZ-W b2-0 C 6", "Col 140 Sector ZZ-W b2-0 A", "Col 140 Sector ZZ-W b2-0 C 4", "Col 140 Sector ZZ-W b2-0 B", "Col 140 Sector ZZ-W b2-0 B 1", "Col 140 Sector ZZ-W b2-0 B 4", "Col 140 Sector ZZ-W b2-0 C 9", "Col 140 Sector ZZ-W b2-0 C 1", "Col 140 Sector ZZ-W b2-0 AB 1", "Col 140 Sector ZZ-W b2-0 C 5", "Col 140 Sector ZZ-W b2-0 C 2", "Col 140 Sector ZZ-W b2-0 B 3", "Col 140 Sector ZZ-W b2-0 C 8", "Col 140 Sector ZZ-W b2-0 C 3", "Col 140 Sector ZZ-W b2-0 C A Belt Cluster 6", "Col 140 Sector ZZ-W b2-0 C 7", "Col 140 Sector ZZ-W b2-0 C" ], "BaseValue":126897, "Bonus":47584, "TotalEarnings":126897 }

{ "timestamp":"2018-11-22T09:40:10Z", "event":"SellExplorationData", "Systems":[ "Col 132 Sector HC-U d3-26" ], "Discovered":[ "Col 132 Sector HC-U d3-26 2", "Col 132 Sector HC-U d3-26 1", "Col 132 Sector HC-U d3-26" ], "BaseValue":11782, "Bonus":4418, "TotalEarnings":11782 }

{ "timestamp":"2018-11-22T09:40:27Z", "event":"SellExplorationData", "Systems":[ "Synuefe JN-Q d6-35" ], "Discovered":[ "Synuefe JN-Q d6-35 1 a", "Synuefe JN-Q d6-35 7", "Synuefe JN-Q d6-35 3", "Synuefe JN-Q d6-35 8", "Synuefe JN-Q d6-35 2", "Synuefe JN-Q d6-35", "Synuefe JN-Q d6-35 4", "Synuefe JN-Q d6-35 9", "Synuefe JN-Q d6-35 7 a", "Synuefe JN-Q d6-35 6", "Synuefe JN-Q d6-35 1", "Synuefe JN-Q d6-35 5" ], "BaseValue":5530137, "Bonus":6888083, "TotalEarnings":5542137 }

{ "timestamp":"2018-11-22T09:40:39Z", "event":"SellExplorationData", "Systems":[ "Col 132 Sector OX-R c5-5" ], "Discovered":[ "Col 132 Sector OX-R c5-5 A 3", "Col 132 Sector OX-R c5-5 B 7", "Col 132 Sector OX-R c5-5 B 3", "Col 132 Sector OX-R c5-5 A 2", "Col 132 Sector OX-R c5-5 A", "Col 132 Sector OX-R c5-5 A A Belt Cluster 1", "Col 132 Sector OX-R c5-5 A 1", "Col 132 Sector OX-R c5-5 A A Belt Cluster 2", "Col 132 Sector OX-R c5-5 B 2", "Col 132 Sector OX-R c5-5 B 1", "Col 132 Sector OX-R c5-5 B 6", "Col 132 Sector OX-R c5-5 A A Belt Cluster 3", "Col 132 Sector OX-R c5-5 B 4", "Col 132 Sector OX-R c5-5 B 5", "Col 132 Sector OX-R c5-5 A 4", "Col 132 Sector OX-R c5-5 A 3 a", "Col 132 Sector OX-R c5-5 B" ], "BaseValue":506882, "Bonus":207078, "TotalEarnings":523882 }

{ "timestamp":"2018-11-22T09:40:56Z", "event":"SellExplorationData", "Systems":[ "Synuefe QF-L d9-47" ], "Discovered":[ "Synuefe QF-L d9-47 A", "Synuefe QF-L d9-47 B" ], "BaseValue":4539, "Bonus":3702, "TotalEarnings":6539 }

{ "timestamp":"2018-11-22T09:41:28Z", "event":"SellExplorationData", "Systems":[ "Col 132 Sector PV-K c9-9" ], "Discovered":[ "Col 132 Sector PV-K c9-9 A", "Col 132 Sector PV-K c9-9 B" ], "BaseValue":175397, "Bonus":65773, "TotalEarnings":175397 }

{ "timestamp":"2018-11-22T09:41:44Z", "event":"SellExplorationData", "Systems":[ "Wregoe WP-G d10-78" ], "Discovered":[ "Wregoe WP-G d10-78 C", "Wregoe WP-G d10-78 D", "Wregoe WP-G d10-78 B", "Wregoe WP-G d10-78 A" ], "BaseValue":9649, "Bonus":7617, "TotalEarnings":13649 }

{ "timestamp":"2018-11-22T09:41:53Z", "event":"SellExplorationData", "Systems":[ "Synuefe GO-R b24-1" ], "Discovered":[ "Synuefe GO-R b24-1 B", "Synuefe GO-R b24-1 C", "Synuefe GO-R b24-1 D", "Synuefe GO-R b24-1 A" ], "BaseValue":9620, "Bonus":7606, "TotalEarnings":13620 }
Click to expand...

When I run through the journal file and manually calculate my new credit balance it looks like the bonus are not being added correctly.
I computed a new balance of 490,852,275, the game reports 490,846,275 - looks to me like I mistyped one digit! Given the bonus reported
is much higher (the 2018-11-22T09:40:27Z event has a 6,888,083 value alone) it looks to me as if there is a bug somewhere!
 

Renderer

Renderer
GuiFocus bug

All new GuiFocus stats work fine, except for "codex" (value 11).

GuiFocus is set to zero when in Codex mode.

New status flags (analysis mode and night vision) work fine.
 

stormyuk

Volunteer Moderator
stormyuk
Is there any documentation available for the newly available console API work? They obviously don't have a local log file and must be doing some interaction server side for the EDSM current version to work.
 

Becky

Becky
Where is the list of station types? They don't seem to match any more? EG: LTT 9795 -> Smith Port In-game it says Ocellus starport in-journal it says "Bernal" I'm using station type to determine if the station has a "Coriolis Style" landing pads, and it's all changed without notification or documentation of the new station types.

You can ignore this ; it's my bad - I'm pulling the data now from journal docked request where previously i was getting it from a 3rd party API.
 
Last edited:

ansi4713

ansi4713
Just saw it:
{ "timestamp":"2018-12-31T17:42:36Z", "event":"MissionCompleted", "Faction":"United German Commanders", "Name":"Mission_Delivery_Democracy_name", "MissionID":447332267, "Commodity":"$Coffee_Name;", "Commodity_Localised":"Kaffee", "Count":72, "TargetFaction":"Tetela Limited", "DestinationSystem":"Khampti", "DestinationStation":"Babcock Gateway", "Reward":1104369, "FactionEffects":[ { "Faction":"United German Commanders", "Effects":[ { "Effect":"$MISSIONUTIL_Interaction_Summary_EP_up;", "Effect_Localised":"Die Wirtschaft von $#MinorFaction; im $#System;-System hat sich verbessert.", "Trend":"UpGood" } ], "Influence":[ { "SystemAddress":285372025195, "Trend":"UpGood", "Influence":"+++++" } ], "ReputationTrend":"UpGood", "Reputation":"++" }, { "Faction":"Tetela Limited", "Effects":[ { "Effect":"$MISSIONUTIL_Interaction_Summary_EP_up;", "Effect_Localised":"Die Wirtschaft von $#MinorFaction; im $#System;-System hat sich verbessert.", "Trend":"UpGood" } ], "Influence":[ ], "ReputationTrend":"UpGood", "Reputation":"++" } ] }

Influence Startfaction: "Influence":[ { "SystemAddress":285372025195, "Trend":"UpGood", "Influence":"+++++" } ],
Influence Targetfaction: "Influence":[ ],

Correct Influence for System/Faction is great (Thumb up)... But why is the Influence for the Targetfaction empty?


UPDATE: I figured it out... The other Faction was in the State of CivilWar. So the empty value is absolutly correct. Perfect.
 
Last edited:

floozie

floozie
Is there any way to find out the reputation to a minor faction in the journal files? this would be so helpful. I was looking for ReceiveText events. But it looks like the message that is incoming when you gain reputation with a minor faction is not showing up in the journals ;(
 

Icytoad

I
floozie said:
Is there any way to find out the reputation to a minor faction in the journal files? this would be so helpful. I was looking for ReceiveText events. But it looks like the message that is incoming when you gain reputation with a minor faction is not showing up in the journals ;(
Click to expand...

The 4.8 FSDJump section of the journal doc might give you what you want.
 

hchalkley

Senior Programmer
Frontier
In v3.3.03, the SystemFaction and StationFaction values in FSDJump, Docked and Location events have changed: they now have an object as a value, with Name and FactionState sub-values. The FactionState may be omitted of state is 'None'

This was because in some cases, events were getting two FactionState values

For example:
"StationFaction":"Union of Luhman 16 Values Party", "FactionState":"CivilWar",
"SystemFaction":"Mob of Eranin", "FactionState":"CivilLiberty"

Changed to:
"StationFaction": { “Name”:"Union of Luhman 16 Values Party", "FactionState":"CivilWar" },
"SystemFaction": { “Name:”"Mob of Eranin", "FactionState":"CivilLiberty" }
 

Micha

Micha
Requesting that the number of POIs on a planet are added to the detailed scan event.

eg: "PointsOfInterest": [ { "Type": "Geological", "Number": 42 } ]
 

MattG

MattG
Pre 3.3, the SellExplorationData event used to contain enough information to decipher which bodies you'd got First Discoverer on.

Since 3.3, MultiSellExplorationData doesn't provide this information. Can a FirstDiscovered (and maybe FirstMapped) array be added for each System in MultiSellExplorationData please.
 

Clicker

Clicker
Hi,

Since the lights in the SRV have three states (off/low/high), may I request the inclusion of an SRV_HighBeam bit within the Flags value in status.json?

Cheers
Clicker
 
Last edited:
You must log in or register to reply here.
Top Bottom