Discussion Commanders log manual and data sample

[iveinsomnia]

Pas de problèmes. So, basically you grind materials to give to research?

Yep, as there is nothing to "give" material to the station, and as it's not a mission, they did this.
I didn't watched in an other station yet, and I don't know if there is any other utility for now.

But at least in the CMDR Log context it would help to track materials.

 

[Cyb]

CC from Bug Report :-

Describe the issue: The MissionCompleted event in the journal does not produce any output if the mission rewards were commodities. i.e mission reward of 4 Modular Terminals produces no output in the journal to reflect that.

Reproduction Steps: Complete a mission rewarding commodities, check journal.

 

[jgm]

CC from Bug Report :-

Describe the issue: The MissionCompleted event in the journal does not produce any output if the mission rewards were commodities. i.e mission reward of 4 Modular Terminals produces no output in the journal to reflect that.

Reproduction Steps: Complete a mission rewarding commodities, check journal.

Do you have a MaterialCollected event directly after the mission completed? I believe that it puts the reward on a separate line.

 

[Cyb]

Do you have a MaterialCollected event directly after the mission completed? I believe that it puts the reward on a separate line.

{ "timestamp":"2016-09-29T14:43:05Z", "event":"MissionCompleted", "Faction":"Nuenets Blue Crew", "Name":"Mission_Courier_War_name", "MissionID":26503975, "DestinationSystem":"Nuenets", "DestinationStation":"Shriver Hub", "Reward":213220 }
{ "timestamp":"2016-09-29T14:43:05Z", "event":"MaterialCollected", "Category":"Manufactured", "Name":"biotechconductors" }
{ "timestamp":"2016-09-29T14:49:38Z", "event":"Undocked", "StationName":"Shriver Hub", "StationType":"Coriolis" }

Material yes, commodities no.

 

[tresch]

I have a request. I would like a boolean value to be logged for Eject Cargo that says whether it was ejected while at a station or not. Not a super high priority as I'm sure this could be derived using other messages, but for ejecting cargo this is kind of a special case, since there's no chance to re-scoop the cargo. It's really just throwing it in the trash. It would be much simpler to be able to find these messages directly.

Suggestion:

{ "timestamp":"2016-06-10T14:32:03Z", "event":"EjectCargo", "Type":"tobacco", "Count":1, "Abandoned":true, "Docked":true }

 

[tresch]

Only other thing that I can think of right now, which is a slightly bigger request, is, upon logging on or when switching ships, having a packet of information that gives the full configuration of the ship and all its modules, so an app could sync up to and track the ship's configuration

 

[Andargor]

Only other thing that I can think of right now, which is a slightly bigger request, is, upon logging on or when switching ships, having a packet of information that gives the full configuration of the ship and all its modules, so an app could sync up to and track the ship's configuration

+1 Yes, been requested a few times, including cargo and mats, so that the deltas in the events match up.

 

[iveinsomnia]

I have a request. I would like a boolean value to be logged for Eject Cargo that says whether it was ejected while at a station or not. Not a super high priority as I'm sure this could be derived using other messages, but for ejecting cargo this is kind of a special case, since there's no chance to re-scoop the cargo. It's really just throwing it in the trash. It would be much simpler to be able to find these messages directly.

Suggestion:

{ "timestamp":"2016-06-10T14:32:03Z", "event":"EjectCargo", "Type":"tobacco", "Count":1, "Abandoned":true, "Docked":true }

You already can track if you are docked or not (when you login, when you dock, when land on planet) and all have the reverse you can know if you are not docked.

 

[hchalkley]

Changes in the journal for the next beta:
• MaterialCollected: add Count property
• Scan: include star's age and temperature, include orbital parameters for stars and other bodies, increase number of significant figures for rings statistics
• The "Bounty" event now lists rewards separately per Faction
• The "ReceiveText" event now logs text chat from NPCs, and indicates whether chat from other players is from wing, local, friend, or direct from another player
• Add a "BodyType" param to "Location" and "SupercruiseExit" events
• Add a "ScientificResearch" event
• Add CommodityReward data to MissionCompleted event
Fix bug with some player text missing from log
Fix bug with events recorded (eg overheating) from nonplayer ships

 

[themroc]

Changes in the journal for the next beta:
• MaterialCollected: add Count property
• Scan: include star's age and temperature, include orbital parameters for stars and other bodies, increase number of significant figures for rings statistics
• The "Bounty" event now lists rewards separately per Faction
• The "ReceiveText" event now logs text chat from NPCs, and indicates whether chat from other players is from wing, local, friend, or direct from another player
• Add a "BodyType" param to "Location" and "SupercruiseExit" events
• Add a "ScientificResearch" event
• Add CommodityReward data to MissionCompleted event
Fix bug with some player text missing from log
Fix bug with events recorded (eg overheating) from nonplayer ships

You're the man!

 

[Genar-Hofoen]

Changes in the journal for the next beta:
• MaterialCollected: add Count property
• Scan: include star's age and temperature, include orbital parameters for stars and other bodies, increase number of significant figures for rings statistics
• The "Bounty" event now lists rewards separately per Faction
• The "ReceiveText" event now logs text chat from NPCs, and indicates whether chat from other players is from wing, local, friend, or direct from another player
• Add a "BodyType" param to "Location" and "SupercruiseExit" events
• Add a "ScientificResearch" event
• Add CommodityReward data to MissionCompleted event
Fix bug with some player text missing from log
Fix bug with events recorded (eg overheating) from nonplayer ships

Have another updoot

Also - so glad I'm still at the "DB schema redesign" stage

 

[Toumal]

Curious about the events from nonplayer ships, could that be a general issue? I noticed receiving chat messages from NPCs that don't relate to my location, i.e. fight messages around stations when everything was idle. Perhaps sent/broadcast to the wrong island?

 

[Toumal]

Have another updoot

Also - so glad I'm still at the "DB schema redesign" stage

Use a k/v store, or work with ORM. If you use a mature language you can map json directly to your object structure and persist without worrying about db schemata.

 

[jgm]

Changes in the journal for the next beta:
• MaterialCollected: add Count property
• Scan: include star's age and temperature, include orbital parameters for stars and other bodies, increase number of significant figures for rings statistics
• The "Bounty" event now lists rewards separately per Faction
• The "ReceiveText" event now logs text chat from NPCs, and indicates whether chat from other players is from wing, local, friend, or direct from another player
• Add a "BodyType" param to "Location" and "SupercruiseExit" events
• Add a "ScientificResearch" event
• Add CommodityReward data to MissionCompleted event
Fix bug with some player text missing from log
Fix bug with events recorded (eg overheating) from nonplayer ships

This is a fantastic list. Don't suppose you know when the next beta is due to drop? I was thinking of pushing out a pre-release of EDDI this afternoon but won't bother if the beta is going to turn up before the weekend.

Also, I know I keep going on about it but did you have any thoughts on the timing of the FSDJump event? At the moment I'm having to read the netlog just so that I can trigger my script when the jump starts, and it doesn't have nearly as much info as the FSDJump event.

 

[Genar-Hofoen]

Use a k/v store, or work with ORM. If you use a mature language you can map json directly to your object structure and persist without worrying about db schemata.

So many technical jargon words

I'm using python, SQLAlchemy is my ORM of choice, and sqlite as the back-end. I'll be converting the JSON into data to be stored in the sqlite db. To me, the JSON is merely the way I retrieve the data, which is to be transmuted and stored in a form and manner I'll find more useful.

Regards.

 

[jgm]

So many technical jargon words

I'm using python, SQLAlchemy is my ORM of choice, and sqlite as the back-end. I'll be converting the JSON into data to be stored in the sqlite db. To me, the JSON is merely the way I retrieve the data, which is to be transmuted and stored in a form and manner I'll find more useful.

Regards.

I tried k/v once, got a division by zero exception...

 

[Toumal]

So many technical jargon words

I'm using python, SQLAlchemy is my ORM of choice, and sqlite as the back-end. I'll be converting the JSON into data to be stored in the sqlite db. To me, the JSON is merely the way I retrieve the data, which is to be transmuted and stored in a form and manner I'll find more useful.

Regards.

In that case, forget i said anything ^^ sqlalchemy is very cool.

 

[hchalkley]

This is a fantastic list. Don't suppose you know when the next beta is due to drop? I was thinking of pushing out a pre-release of EDDI this afternoon but won't bother if the beta is going to turn up before the weekend.

Also, I know I keep going on about it but did you have any thoughts on the timing of the FSDJump event? At the moment I'm having to read the netlog just so that I can trigger my script when the jump starts, and it doesn't have nearly as much info as the FSDJump event.

The next beta is still a few days away, but the exact time is subject to internal test plans being passed. Sorry, no plans to change the FSD jump event, we don't have all the data conveniently available earlier. The only remaining things to do in the Journal are module storage and retrieval events. Re events logged from NPC ships, there were a half-dozen or so cases that were fixed.

 

[jgm]

The next beta is still a few days away, but the exact time is subject to internal test plans being passed. Sorry, no plans to change the FSD jump event, we don't have all the data conveniently available earlier.

Yeah, I was afraid of that. Understand.

The only remaining things to do in the Journal are module storage and retrieval events. Re events logged from NPC ships, there were a half-dozen or so cases that were fixed.

It's great stuff, thanks again for all of your work on this feature.

 

[robbyp]

@hchalkley. Great work on the journal. During decoding for EDDiscovery i noted that Event:Location 'Docked' is 1 or 0, instead of true/false.

Also your document does not state what 'distance' units are used in the Shipyardtransfer are. We worked it out as meters! Such accuracy is commendable ;-)