Discussion Commanders log manual and data sample

[eventure]

How it is possible to gain planetary or star data through a Detail Surface Scanner for already scanned bodies, before the journal was available?

ED does not allow another scan of bodies, you already have scanned or their data is available from the release of ED.
For me, it is now illogical and unimmersive that my scanner stop working on already known bodies. Without the jounal, there was no reason to question, because all data was enclosed into ED.
But now things changed and all known data should also be made available through a scanner.

The only chance is to write down all data from the screen by hand and manually input this data into a 3rd party tool and we all know, this is not, what we devs want!

The main question is, why we can't make use of a Detail Surface Scanner on any body at the game, as often as we want?
I would like to see this changed to the game, for the sake of all players, using 3rd party tools.

 

[Hoodathunk]

I'm consistency not seeing a "DockFighter" event timestamp in the Journal Log when the fighter docks with the AI crewman piloting ("PlayerControlled":false). I'm reasonably sure this is not intended. Has this already been reported?

 

[wolverine2710]

I do not see a signature

I think he meant this blog. https://elitedangerous2016.wordpress.com/author/thebarkingmadness/.
Result of Google search: Elite Dangerous Development blog Barking Mad

 

[wolverine2710]

How it is possible to gain planetary or star data through a Detail Surface Scanner for already scanned bodies, before the journal was available?

ED does not allow another scan of bodies, you already have scanned or their data is available from the release of ED.
For me, it is now illogical and unimmersive that my scanner stop working on already known bodies. Without the jounal, there was no reason to question, because all data was enclosed into ED.
But now things changed and all known data should also be made available through a scanner.

The only chance is to write down all data from the screen by hand and manually input this data into a 3rd party tool and we all know, this is not, what we devs want!

The main question is, why we can't make use of a Detail Surface Scanner on any body at the game, as often as we want?
I would like to see this changed to the game, for the sake of all players, using 3rd party tools.

For the reasons mentioned by Eventure I totally agree with the request.

 

[AnthorNet]

How it is possible to gain planetary or star data through a Detail Surface Scanner for already scanned bodies, before the journal was available?

ED does not allow another scan of bodies, you already have scanned or their data is available from the release of ED.
For me, it is now illogical and unimmersive that my scanner stop working on already known bodies. Without the jounal, there was no reason to question, because all data was enclosed into ED.
But now things changed and all known data should also be made available through a scanner.

The only chance is to write down all data from the screen by hand and manually input this data into a 3rd party tool and we all know, this is not, what we devs want!

The main question is, why we can't make use of a Detail Surface Scanner on any body at the game, as often as we want?
I would like to see this changed to the game, for the sake of all players, using 3rd party tools.

Agree on that one.

 

[Andargor]

How it is possible to gain planetary or star data through a Detail Surface Scanner for already scanned bodies, before the journal was available?

ED does not allow another scan of bodies, you already have scanned or their data is available from the release of ED.
For me, it is now illogical and unimmersive that my scanner stop working on already known bodies. Without the jounal, there was no reason to question, because all data was enclosed into ED.
But now things changed and all known data should also be made available through a scanner.

The only chance is to write down all data from the screen by hand and manually input this data into a 3rd party tool and we all know, this is not, what we devs want!

The main question is, why we can't make use of a Detail Surface Scanner on any body at the game, as often as we want?
I would like to see this changed to the game, for the sake of all players, using 3rd party tools.

How about triggering the journal event when the body is consulted in the System view, even if it was previously scanned?

 

[iveinsomnia]

How about triggering the journal event when the body is consulted in the System view, even if it was previously scanned?

I'm almost sure I suggested something like that (can't search I'm at work).
In my first suggestion to add the know systems in the Journal, hchalkley said he don't want to spam the Journal and want avoid big files.
Then I suggested a separate file in the same folder to have this information like "system.log" jump > clear the file > dump datas in the file > Jump > clear > dump etc ...
Any app have totally the time to grab the infos, the player will not get enormous files, the data are here by request from the game. No cheat, or spoil possible. Maybe complicated to include, but doable.
But he said the same day he will not add features anymore ...

 

[eventure]

I'm almost sure I suggested something like that (can't search I'm at work).
In my first suggestion to add the know systems in the Journal, hchalkley said he don't want to spam the Journal and want avoid big files.
Then I suggested a separate file in the same folder to have this information like "system.log" jump > clear the file > dump datas in the file > Jump > clear > dump etc ...
Any app have totally the time to grab the infos, the player will not get enormous files, the data are here by request from the game. No cheat, or spoil possible. Maybe complicated to include, but doable.
But he said the same day he will not add features anymore ...

More than complicated and not necessary at all. For me, it's only required to allow scans on all present stellar bodies (should be simple).
Because normally the scan is done automatically, when close to ca. 30 LS of an object, but it could be changed to a hotkey or
by adding a sub command to UNEXPLORED entries of the Navigation or Contact list, if the body is the target and the scanner is installed.

That requires a little more work, but feels more reasonable to activate the scanner by a key or command.

 

[Athan]

More than complicated and not necessary at all. For me, it's only required to allow scans on all present stellar bodies (should be simple).
Because normally the scan is done automatically, when close to ca. 30 LS of an object, but it could be changed to a hotkey or
by adding a sub command to UNEXPLORED entries of the Navigation or Contact list, if the body is the target and the scanner is installed.

That requires a little more work, but feels more reasonable to activate the scanner by a key or command.

How about actually having an Advanced Discovery Scanner event, and when that's triggered it not only logs all the bodies in the system, but with all the detail currently available to the player. That way if they had it already, via DSS, Nav Beacon, whatever, it would go in the log. That way FDev don't have to mess with the way that Surface Scans currently work.

 

[eventure]

How about actually having an Advanced Discovery Scanner event, and when that's triggered it not only logs all the bodies in the system, but with all the detail currently available to the player. That way if they had it already, via DSS, Nav Beacon, whatever, it would go in the log. That way FDev don't have to mess with the way that Surface Scans currently work.

I am happy with that too, as long as we get all data, not only from unknowns.

 

[Moleculor]

It would be extra lovely if we could somehow trigger this data while looking at a map of a system we have the data on and have visited previously. So I don't have to travel 8,000Ly to rescan a system I already have data on.

 

[Deadweasel]

Kind of a bummer this is only available in a Beta that's only accessible if you pay for it, and if you've already dropped the additional $30 to buy Horizons. I'd love to, but can't justify the cost yet. Meanwhile, I've been working on a custom control panel project that could have benefited greatly from being able to access this player log. Sadly, while I kept finding references to an official API (of sorts), and finally landing at the Codex page describing the journal's layout, I then discovered that it's not a general E feature, but rather one limited only to this latest version.

I don't suppose there are any plans in the works to make the player journal a feature accessible to the vanilla E players? I really have a lot of fun with the game as it is, and would like to see how far I can take it (and this control panel project) before I see about adding a ton of things I won't touch for quite some time anyway...

 

[jgm]

Kind of a bummer this is only available in a Beta that's only accessible if you pay for it, and if you've already dropped the additional $30 to buy Horizons. I'd love to, but can't justify the cost yet. Meanwhile, I've been working on a custom control panel project that could have benefited greatly from being able to access this player log. Sadly, while I kept finding references to an official API (of sorts), and finally landing at the Codex page describing the journal's layout, I then discovered that it's not a general E feature, but rather one limited only to this latest version.

I don't suppose there are any plans in the works to make the player journal a feature accessible to the vanilla E players? I really have a lot of fun with the game as it is, and would like to see how far I can take it (and this control panel project) before I see about adding a ton of things I won't touch for quite some time anyway...

The journal is a new feature that is coming to Elite with the 2.2 release. It's only available in beta at the moment because the 2.2 release is being beta tested. It will become available to everyone, along with the rest of the 2.2 features, when it goes live (which we believe will be in the next week although there has been no official announcement).

 

[gazelle]

I am happy with that too, as long as we get all data, not only from unknowns.

You could clear your savegame and start over. You should be able to scan everything again.

 

[eventure]

You could clear your savegame and start over. You should be able to scan everything again.

Please tell that every player, who played nearly 2 years with his commander. I think, you are not welcome with your suggestion.

 

[Genar-Hofoen]

Howard, I had a shower-thought recently...

What's going to happen in the future, if/when (heheh) FDEV make more planet types landable?

I'm thinking of my previous ELW discoveries for example - eventually they should be landable, which has implications for any data that's been collected in the period from when 2.2 goes live to $whatever_version of the game makes more planets landable - because the way it works now, data can't be updated on previously-scanned planets because you can't currently re-detail-scan them - and hence no Journal entry will be produced.

Has anyone at FDEV Towers thought about that scenario yet?

Regards o7

We'll cross that bridge when we get to it ("Agile Development" and all that)

PS: the broken key strings in ModuleRetrieve, FetchRemoteModule and JetConeDamage have been fixed for next release - thanks all for pointing them out

How it is possible to gain planetary or star data through a Detail Surface Scanner for already scanned bodies, before the journal was available?

ED does not allow another scan of bodies, you already have scanned or their data is available from the release of ED.
For me, it is now illogical and unimmersive that my scanner stop working on already known bodies. Without the jounal, there was no reason to question, because all data was enclosed into ED.
But now things changed and all known data should also be made available through a scanner.

The only chance is to write down all data from the screen by hand and manually input this data into a 3rd party tool and we all know, this is not, what we devs want!

The main question is, why we can't make use of a Detail Surface Scanner on any body at the game, as often as we want?
I would like to see this changed to the game, for the sake of all players, using 3rd party tools.

Eventure hits the nail on the head. +rep

This is related to my previous question I quoted above for whenever more planets change from non-landable to becoming landable. The real problem is not being able to trigger the surface scanners on previously-scanned or already-known bodies.

The quickest solution would be to be able to trigger the surface scanner on previously scanned bodies. Even if we already have data on a body, it's trivial to check if the new data is different from existing data we have, just by comparing the new data from the Journal file with what we have in our databases, and update/refresh our DB's with any difference in the data.

If it's too late to make this change now, perhaps this is something which could be done in a 2.2.x update or even a 2.3 onwards release.

Regards.

 

[MartinG]

You could clear your savegame and start over. You should be able to scan everything again.

Please tell that every player, who played nearly 2 years with his commander. I think, you are not welcome with your suggestion.

Not to mention even a new CMDR cannot scan everything – a lot of systems have full data available from the start, and scanners won’t trigger there.

 

[ChaosCloud]

Oh this is awesome news, just stumbled over the files myself by accident xD

This will be great for collecting data for EdMaterializer and such

Though for that matter, could an event be added for SRV mining? There's currently one for gathering a material which is nice but for EdMat's use a bit bothersome especially since the source node type is not present.
Something along this:

{ "timestamp":"2016-06-10T14:32:03Z", "event":"MaterialMined", "Category":"Raw", "Source":"Bronze Chondrite", {"sulphur":1, "iron":2, "nickel":1} }

With the amounts being the actual objects being thrown out, not the result you'd get from picking them up.
This would help gathering the mining data sooo much easier
Atleast as long as both outcrops won't share the same name anymore...

Yeah I know we have the system map data and that's fine, though I find it should only tell us WHAT is there and not the percentages on top, but whatever, for now I'd be happy with this mining event being added to the log ^^


PS: I based the entry off of this one from the doc { "timestamp":"2016-06-10T14:32:03Z", "event":"MaterialCollected", "Category":"Raw", "Name":"sulphur" }
and I was wondering: why's "timestamp" and "event" full lowercase but "Category", "Raw" and "Name" not? o.o seems like a mix of standards.

 

[tehface]

is the scan body journal bit broken? I can never get mine to go into the log ( "event":"Scan" )

 

[jgm]

is the scan body journal bit broken? I can never get mine to go into the log ( "event":"Scan" )

Do you have a detailed surface scanner?