Discussion Commanders log manual and data sample

djadjok

djadjok
hchalkley said:
I'll add an "ApproachSettlement" event that gives the Name of the settlement, but the game designers have asked that I do not include anything else (such as settlement type) because spoilers.
Click to expand...
Oh, thanks you, really excellent news and understandable position of game designers - at least about type and possible spoiler.
Some doubts about owning faction, size and security - are they also spoilers? So far both are available in-game while player is in the same system. Or size will be part of the name (in the form of "+" signs)? Ok-ok,no more questions=)
Anyway as I said I fully understnad - and appreciate - the "no spoilers" design approach and once again thank you for adding "ApproachSettlement" and clarification of the position of the design team.
 
Last edited:

Bravada Cadelanne

Bravada Cadelanne
Will the "ApproachSettlement" event occur when you approach within 400km of a settlement when in normal flight (i.e. when the current location indicator in the lower left of the HUD says you're at the settlement) or when the name becomes known, whichever comes later? Will it have the same information as is visible in the HUD (i.e. name and faction)?

LewisHorizons.png
 
Last edited:

outsidefactor

outsidefactor
Martin Schou said:
From the log sample:

,"09:28:21": { "event":"FSDJump", "StarSystem":"Cerno", "StarPos":[30.063,26.875,-82.938], "JumpDist":20.012, "Faction":"Cerno Transport Interstellar" }

Could that be expanded ever so slightly to this?

,"09:28:21": { "event":"FSDJump", "StarSystem":"Cerno", "StarPos":[30.063,26.875,-82.938], "JumpDist":20.012, "Faction":"Cerno Transport Interstellar", "Allegiance":"Federation", "Government":"Corporate" }

This would allow semi-automatic mapping of the distribution of super powers and government types in terms of factions that are in control.

Aiding the BGS a little bit could also be helpful:

,"09:28:21": { "event":"FSDJump", "StarSystem":"Cerno", "StarPos":[30.063,26.875,-82.938], "JumpDist":20.012, "Faction":"Cerno Transport Interstellar", "Allegiance":"Federation", "Government":"Corporate", "Influence":"25.3", "State":"Civil War" }
Click to expand...

The Influence data doesn't even need to be included in FSDJump or Location. It could be handled by a new event OpenSystemMap or equivalent. Thus to get updated data you just need to open a system's map and the data is captured.

Certainly the faction active states should be captured on FSDJump and upon docking, and the Cooldown and Pending states when you dock.
 

djadjok

djadjok
BravadaCadelanne said:
Will the "ApproachSettlement" event occur when you approach within 400km of a settlement when in normal flight (i.e. when the current location indicator in the lower left of the HUD says you're at the settlement) or when the name becomes known, whichever comes later? Will it have the same information as is visible in the HUD (i.e. name and faction)?

http://klightspeed.killerwolves.net/images/LewisHorizons.png
Click to expand...
Imo, the reasonable trigger generating distance can be less by orders of magnitude of the above mentioned by you, as two settlements can be placed pretty close to each other (<100 km). So, may be some kind of "direct visual contact" or about 20 km - if one follow the line of "no spoilers"? So far I don't know how this will be done, this is only my suggestions.
 

Special Circumstances

S
Actually, I have a request.

Thinking about tracking items for players (stock/profit/etc). It would be very useful to have as part of or following the startup events a couple of Inventory events, which list the current CMDRs inventory.

This would make initial states much easier to capture and maintain for companion apps, especially where materials, trade and crafting are concerned.

The Rank/Progress/Location events already do this for other elements.

Looking at the existing examples, I guess this would also be very useful to have for ship load-out and any bits of existing engineering.


Sorry sprawling text, I'm excited, so to summarise I'm asking if it would be possible to have a series of additional "current state" events in the Startup section, including:

Ship Loadout (modules and customisations)
Inventory (sections as per the game, Cargo, Materials, Data - also current balance)
Current Missions
Current Bounties/Fines

I'm hoping that would be fairly straightforward to do, but I think it would be extremely helpful :) I will buy you a cake if you do.

Are you also planning to publish a (no-exclusive) list of your reference values? (e.g. hpt_multicannon_gimbal_medium)?



EDIT: Oh well, see, I should have read the whole thread.... https://forums.frontier.co.uk/showt...sample/page5?p=4256011&viewfull=1#post4256011
 
Last edited:

Special Circumstances

S
Genar-Hofoen said:
Yes that's not a bad idea at all - I was thinking of suggesting something similar last week - but got caught in the JSON file momentum.

One of the other advantages of a UDP broadcast would be that you could have clients listening on other, different PC's, Macs, Android phones, Raspberry Pi's, wherever!

I too believe that some less powerful systems might find all the writing/flushing of a journal file might prove to be too much of a burden.

Configuring which events you want to know about might also be a good idea. Why not have both? Or even a choice between keeping a journal file, UDP broadcast, both if your system can handle it.

I don't know if it's too late for the UDP broadcast idea though - I certainly hope not. What say you, H Chalkley? :)

Regards o7
Click to expand...

Nothing to stop someone writing a little app to do that now though...
 

Bravada Cadelanne

Bravada Cadelanne
djadjok said:
Imo, the reasonable trigger generating distance can be less by orders of magnitude of the above mentioned by you, as two settlements can be placed pretty close to each other (<100 km). So, may be some kind of "direct visual contact" or about 20 km - if one follow the line of "no spoilers"? So far I don't know how this will be done, this is only my suggestions.
Click to expand...

I was just wondering if the ApproachSettlement event was linked to entering or dropping out of supercruise in the sphere of influence of the settlement, which extends to 400km from the settlement. It also appears that the name of a settlement is unknown until one scans the planet, no matter how close one gets to the settlement, so it would seem to only be fair to only trigger the ApproachSettlement event if the settlement name has been revealed by scanning the planet.
 

Scottworld

Scottworld
Can someone post a link to the latest... Data sample I see the format has changed a bit while I was away, so will need to re-jig a few things.
 

Andargor

Andargor
As I've mentioned in previous posts, I think that route information would be very valuable. For example, having another window open with a tool such as ED:Toolbox or perhaps EDSM or EDDB that show the route with additional information, such as other player's bookmarks, EDDB info, and so on.

Hence, I propose the addition of the following to the Travel section:

4.14 DestinationSet

When written: when a system or station is set as destination.

Parameters:
- SystemName: name of system
- StationName: name of station (if applicable)

Example:
{ "timestamp":"2016-06-10T14:32:03Z", "event":"DestinationSet", "SystemName":"Shinrarta Dehzra", "StationName":"Jameson Memorial" }

4.15 RouteSet

When written: when a route is created.

Parameters:
- Route: an Array of system names, including the destination system
- DestinationSystem: destination system
- DestinationStation: destination station (if applicable)

Example:
{ "timestamp":"2016-06-10T14:32:03Z", "event":"RouteSet", "DestinationSystem":"Shinrarta Dehzra", "DestinationStation":"Jameson Memorial", Route: [ "LFT 926", "Nuenets", "Bunda" ] }

NOTE: This may be altered a bit if there is a concern that too many systems would be listed in the route, e.g. only put the next 10 hops, and generate this event at every jump, or something similar

4.16 BookmarkSet

When written: When a bookmark is created or edited

Parameters:
- SystemName: name of system
- StationName: name of station (if applicable)
- Description: bookmark description

Example:
{ "timestamp":"2016-06-10T14:32:03Z", "event":"BookmarkSet", "SystemName":"Shinrarta Dehzra", "StationName":"Jameson Memorial", Description:"Home sweet home" }
 
Last edited:

iveinsomnia

iveinsomnia
Just wanted to add to scan the "Discoverer":"CMD_Name" simple str
And maybe a way to have the Discovery Scanner basic data (nothing more than you can have after a Discovery Scan on the system map) :
{ "timestamp":"2016-07-25T14:46:36Z", "event":"DiscoveryScan", "Systems":"Kaba", "bodies":[ "Kaba 1":["Discoverer":"CMD_Name","DistanceFromArrivalLS":123.456,"Landable":1], "Kaba 2":["DistanceFromArrivalLS":123.456], "Kaba 3":["DistanceFromArrivalLS":123.456]] }
Click to expand...
 

Micha

Micha
iveinsomnia said:
Just wanted to add to scan the "Discoverer":"CMD_Name" simple str
And maybe a way to have the Discovery Scanner basic data (nothing more than you can have after a Discovery Scan on the system map) :
Click to expand...

It would need to be an array of commander-names, since all commanders in a wing are credited with a first-discovery.
So: "bodies":[ "Kaba 1":{"Discoverers":["CMD_1_NAME","CMD_2_NAME",...], ...}, "Kaba 2":{...}, ... ]
 

peelt

P
I don't know if I missed someone else suggesting it, but I propose the following event which could be very useful for many people, especially those grinding for engineer mods:
Journal:Startup:ShipInventory
Written at startup, it would output all types of ship inventory and respective quantity shown at the right panel inventory tab (data, cargo etc).

This event, along with the MaterialCollected,MaterialDiscarded,MaterialDiscovered events would allow for full monitoring of the Ship Inventory. I hope it is reasonably easy to implement, it would certainly be really helpful.

Thanks for listening
 

peelt

P
peelt said:
I don't know if I missed someone else suggesting it, but I propose the following event which could be very useful for many people, especially those grinding for engineer mods:
Journal:Startup:ShipInventory
Written at startup, it would output all types of ship inventory and respective quantity shown at the right panel inventory tab (data, cargo etc).

This event, along with the MaterialCollected,MaterialDiscarded,MaterialDiscovered events would allow for full monitoring of the Ship Inventory. I hope it is reasonably easy to implement, it would certainly be really helpful.

Thanks for listening
Click to expand...

Obviously I mean :
Journal - Startup - ShipInventory
Damn Smileys :)
 

Labanden

Labanden
All good so far, Can I add my request for an up to date and more inclusive Data file please.

Also changes
4.8 and 4.12 (Liftoff and Touchdown) can we have System and Planet added please.

5.12 PVPKill can the same be created for NPC or just change to KILL and have both.

Under missions in section 8 there is no provision to record any penalties for Missions not being completed. Also some missions pay a bonus for completing early.
8.23 and 8.24 (Refuel All and Refuel Partial) initial or final fuel level would be nice.
 

_Flin_

_Flin_
The API is really brilliant.

There are, however, two things that i thoroughly miss:
- an OpenSystemMap event that logs the faction names, states and influence levels (in system or from galaxy map)
- an OpenFactionDetails event that logs the pending states when the faction details are opened in the right hand menu while in the system.

That'd be soooo wonderful and would save us so much time, if we could just read the influence and enter it into our tools, instead of having to type it manually.
 
You must log in or register to reply here.
Back
Top Bottom