Discussion Commanders log manual and data sample

As an aside, the BOM is not recommended in UTF8.

Wikipedia said:
"The Unicode Standard 5.0, Chapter 2:General Structure" (PDF). p. 36. Retrieved 2008-11-30. Use of a BOM is neither required nor recommended for UTF-8, but may be encountered in contexts where UTF-8 data is converted from other encoding forms that use a BOM or where the BOM is used as a UTF-8 signature

Microsoft decided to shove it into files to differentiate them from the ASCII text UTF8 is intentionally compatible with (breaking this compatibility), even if no other content in the file requires such a distinction. The BOM is meant for wider encodings like UTF16 or 32.
 
As I am implementing the journal import for Inara and going deeper into what's provided, I discovered few additional "flaws" which are pretty important for accurate credits, commodities and material tracking across the session. Without these it's not possible to correctly track the changes and it would be nice to see it implemented.

8.10 MissionCompleted
- there should be also the list of other rewards like commodities and materials​
8.8 MissionAbandoned, 8.11 MissionFailed
- there should be penalty (in credits) added​
8.x EngineerDonation (???)
- there should be the new event for donations made to engineer for its unlocking with credits, commodities, materials spent​
 
I like to add:
8.17 RedeemVoucher
- Add the faction to the output, who pays the reward, as it is done at the 5.1 Bounty event.
7.3 EjectCargo
- Add 'stolen' to the output, like the CollectCargo event, to track either the cargo ejected was stolen or not. Otherwise it would not be possible to differ both and the Cargo events would become useless.
8.25 ShipyardSell
- Add the station name, where the ship is sold.
 
Last edited:
I tried to search but didn't find anything, apologies if already asked.

For Event FSDJump (Ref: 4.7 in manual). Does this trigger prior to jump or on arrival after jump? On Arrival makes sense but something Prior to jumping would be good as well.
 
(bookmark post)
I wonder if we can have marked data and faction data too.
something like
open marked -> log all marked data
open mission tab -> log all factions
 
Last edited:
I notice the latest manual still has the 'log' as a single JSON object indexed by time (Only - no date). I was under the impression this was a 'log' not a 'status dump'.

Can we please please please just have individual JSON objects appended in a simple list (No JSON structure around the entries). With (As requested previously) proper ISO format timestamps... In UTC... After all the OS has perfectly adequate tools for converting UTC to localtime. Why try to re-invent the wheel.

It's a log damnit!
 
I notice the latest manual still has the 'log' as a single JSON object indexed by time (Only - no date). I was under the impression this was a 'log' not a 'status dump'.

Can we please please please just have individual JSON objects appended in a simple list (No JSON structure around the entries). With (As requested previously) proper ISO format timestamps... In UTC... After all the OS has perfectly adequate tools for converting UTC to localtime. Why try to re-invent the wheel.

It's a log damnit!

The first post here wasn't updated, the latest manual and log sample is in this post: https://forums.frontier.co.uk/showt...ample/page14?p=4276171&viewfull=1#post4276171
 
I tried to search but didn't find anything, apologies if already asked.

For Event FSDJump (Ref: 4.7 in manual). Does this trigger prior to jump or on arrival after jump? On Arrival makes sense but something Prior to jumping would be good as well.

If it's based on the current system arrival stuff, it is a few seconds before you exit hyperspace (when the System: event is currently logged).
 
Will our player data be provided to us retroactively? So we can upload data from our past year etc? Many of us may have lost our net logs or never activated them until later.

Is this something in the future you are willing to provide us?
 
QQ... Will this be available on the Mac version?

It will probably be active on the Mac version as well (1.7 onwards), so I'll try to have my Mac version of Captain's Log changed for that - might be a week or three after the new version of ED goes live on the Mac though. You'll probably find the Mac version of EDDiscovery will arrive sooner.
 
I ran this through a JSON validator.... and got this.

Error: Parse error on line 8:
...uild": "r114753 "} { "timestamp": "201
----------------------^
Expecting 'EOF', '}', ',', ']', got '{'


The previous 1st version works fine.... (am trying to do a php json_decode) and the function balks at the formatting of the log.

http://php.net/manual/en/function.json-decode.php

Was this a single line? Or the entire file. I believe the new version is complete/correct JSON per line, not per file.
 
That would explain it... I ran the entire file.
I guess we are going to have to step through the file and read it line by line ? or will it be a complete JSON set of objects in one file ?
 
That would explain it... I ran the entire file.
I guess we are going to have to step through the file and read it line by line ? or will it be a complete JSON set of objects in one file ?

Yes, line by line. This enables a program to watch the file for changes and read only the new lines which have appeared rather than re-parsing the entire JSON file every time. All the lines will be individually valid JSON objects.
 
Back
Top Bottom