Discussion Commanders log manual and data sample

An interesting one: an old-style Bounty event showed up in a player's logs:

Code:
{ "timestamp":"2016-10-24T18:54:32Z", "event":"Bounty", "Target":"Skimmer", "Reward":0, "VictimFaction":"$faction_none;", "VictimFaction_Localised":"None" }

Given the information here I have to assume that it's a bug showing up at all, but it does suggest that there's a codepath out there where the Bounty event wasn't upgraded to the new-style format.
 
Holy crap I completely retract the semi snark in my previous post! I hadn't expected FD to update the base game so much, nor for them to add the Player Journal to it as well! I'm so excited to be able to start some actual work on my control panel idea beyond the planning phase, and especially so with all these helpful code tips from everyone!

One thing I was hoping for was an entry in the log for changes in player wanted status. For example, last night while popping bounties, I think I accidentally opened up on a system patrol vessel and earned a wanted status. Unfortunately I didn't see the tag show up on the dashboard, and my first clue was when the entire patrol opened up on me, wiping out my shields and 60% of my hull integrity before I could react and bug out.
I never did discover what exactly triggered the bounty on my head, but it would have been nice to know the second I became a criminal.

My control panel concept will be including audio alerts for things the ship doesn't indicate specifically already, such as gear, hard points or cargo scoop interfering with frame shift. I'd like to include a wanted status warning too, but didn't see anything in the API reference beyond crimes committed against me, not BY me.

Is there a way to detect that, or should that be a requested feature?

Thanks again all!
 
Holy crap I completely retract the semi snark in my previous post! I hadn't expected FD to update the base game so much, nor for them to add the Player Journal to it as well! I'm so excited to be able to start some actual work on my control panel idea beyond the planning phase, and especially so with all these helpful code tips from everyone!

One thing I was hoping for was an entry in the log for changes in player wanted status. For example, last night while popping bounties, I think I accidentally opened up on a system patrol vessel and earned a wanted status. Unfortunately I didn't see the tag show up on the dashboard, and my first clue was when the entire patrol opened up on me, wiping out my shields and 60% of my hull integrity before I could react and bug out.
I never did discover what exactly triggered the bounty on my head, but it would have been nice to know the second I became a criminal.

My control panel concept will be including audio alerts for things the ship doesn't indicate specifically already, such as gear, hard points or cargo scoop interfering with frame shift. I'd like to include a wanted status warning too, but didn't see anything in the API reference beyond crimes committed against me, not BY me.

Is there a way to detect that, or should that be a requested feature?

Thanks again all!

There is a CommitCrime event. If that contains a bounty then you're wanted.
 
There is a CommitCrime event. If that contains a bounty then you're wanted.

Thanks for replying! I admit I was so excited about this that I might have overlooked something, but doesn't that stat indicate crimes committed against me, as the right panel allows me to disable/enable? Or is this just a case of me getting confused by similar terminology?
Your way makes sense though, because if it worked the way I thought, it seems a bit redundant to record a "victim" if that's always me, hehe.
 
Our top ludoastrophysicists have been granted funding for a research project to look into this in-silico cosmological anomaly.

Awesome it got fixed! Thanks!

Here's another bug: On some occasions the atmosphere type reports "thick atmosphere" - with two spaces in between and without the info what actual atmosphere it is. Here are some samples:
https://ross.eddb.io/eddn/log/29347
https://ross.eddb.io/eddn/log/29130
https://ross.eddb.io/eddn/log/21212
https://ross.eddb.io/eddn/log/19486
https://ross.eddb.io/eddn/log/13371

I checked one body myself and ingame the atmosphere was "Ammonia and oxygen". Hope the information helps to fix this :)
 
Interesting bug in CM Draconis:

Code:
{ "timestamp":"2016-10-26T08:25:14Z"
, "event":"FSDJump"
, "StarSystem":"CM Draconis"
, "StarPos":[-35.688,30.938,2.156]
, "Allegiance":"PlayerPilots"
, "Economy":"$economy_None;"
, "Economy_Localised":"None"
, "Government":"$government_None;"
, "Government_Localised":"None"
, "Security":"$SYSTEM_SECURITY_low;"
, "Security_Localised":"Low Security"
, "JumpDist":27.517
, "FuelUsed":7.795260
, "FuelLevel":39.936310
, "Faction":"CM Draconis Clan"
, "FactionState":"Famine" }

This allegiance does not exist:
Code:
"Allegiance":"PlayerPilots"

The fact that CM Draconis has no stations, no planets and no population is mildly interesting as well, but shouldn't have an impact on the journal.
 
As a follow up to my last atmosphere issue, here is another atmosphere bug: Body Eoch Flyuae BN-A d14-852 6 in system Eoch Flyuae BN-A d14-852 reports as atmosphere entry: "Atmosphere":"" ... but the actual ingame descriptions says Suitable for water-based life.

Screenshot: http://i.imgur.com/sYkfJ0l.png

Journal entry:
Code:
{    "Atmosphere": "",
    "BodyName": "Eoch Flyuae BN-A d14-852 6",
    "DistanceFromArrivalLS": 1753.542358,
    "Eccentricity": 0.000417,
    "Landable": false,
    "MassEM": 1.39417,
    "OrbitalInclination": -0.114778,
    "OrbitalPeriod": 168387824.0,
    "Periapsis": 35.112717,
    "PlanetClass": "Earthlike body",
    "Radius": 6694928.0,
    "RotationPeriod": 60499.25,
    "SemiMajorAxis": 525652787200.0,
    "SurfaceGravity": 12.397474,
    "SurfacePressure": 66578.382813,
    "SurfaceTemperature": 285.660431,
    "TerraformState": "",
    "TidalLock": false,
    "Volcanism": "minor metallic magma volcanism",
    "event": "Scan",
    "timestamp": "2016-10-26T11:50:48Z"
}
 
Last bug for tonight, I promise :)

On rare occasions, the Faction entry is entirely missing on the Docking event. So far we recorded these stations:

Azeban City - Eranin
Romanek's Folly - Morgor
Chango Dock - i Bootis
Romanek's Folly - Morgor

For Azeban City we have different records from different users, so the outcome is reproducible.

In any case... The Commanders Log is an awesome addition and everybody is hard at work to make best use of the new data we receive. So again, thanks!
 
quick questions, my game non beta, does not seem to be making the journal.log file....... do i need to activate the creation of it somewhere?
 
quick questions, my game non beta, does not seem to be making the journal.log file....... do i need to activate the creation of it somewhere?
They're in %USERPROFILE%\Saved Games\Frontier Developments\Elite Dangerous\ NOT the same location as the netLog files.
 
Could we get an entry after scanning (and k-warrant/cargo scanning) a ship? Possible parameters:

  • Name
  • NPC/Player
  • Rating
  • Faction
  • Ship type
  • Alignment (Neutral/Friendly/Hostile)
  • Bounty rewards
  • Modules (Any information that is available to the player via the sub-targets menu)
  • Cargo (in the case of a cargo scan)
 
There's a mistake in the manual. For the event:

Code:
{ "timestamp":"2016-10-27T09:40:55Z", "event":"ShipyardNew", "ShipType":"sidewinder", "NewShipID":80 }

The manual says that the ship id is in 'ShipID' but as can be seen from the event it's actually 'NewShipID'.
 
Would it be asking too much to request the associated text from a tip-off or tourist beacon to show up in the player journal?

Right now, the most I've seen has been something like:
{ "timestamp":"2016-10-25T18:18:44Z", "event":"DataScanned", "Type":"TouristBeacon" }
 
Back
Top Bottom