Discussion Commanders log manual and data sample

CMDR HG

CMDR HG
Andargor said:
We haven't had any feedback whether this thread is really being monitored or not. Howard has moved on to other deliverables. Perhaps posting formal bugs is the way to go.

Nice work on EDEngineer btw, I've been using it extensively, bugs and all. :)
Click to expand...

I sent a direct message to Howard, we'll see if he replies :)
Regarding EDEngineer, I think all bugs have been fixed (some common issues here) ! Only the localization is missing before I can safely release a good version (to get rid of these pesky 1.0.0.XX version, and reach 1.0.1).
 

eventure

eventure
Maybe I am repeating myself, but it is not possible to track bounties properly without adding to the RedeemVoucher event a faction name list, from where you got the bounty.
Only adding "bounties" and a value doesn't tell you anything.
 

hchalkley

Senior Programmer
Frontier
There's an update to the game being released this morning, with a few bug fixes - the full change notes will be posted in the usual place, but the changes specifically in the player journal are as follows:
• DockFighter event - fixed when piloted by AI
• Add a MaterialCollected event when material is first discovered
• Docked event - report data about station's faction as StationFaction, StationGovernment, StationEconomy, StationAllegiance; note Security is an attribute on the starsystem
• and for clarity, the data in Location and FSDJump events is now named SystemAllegiance, SystemEconomy, SystemGovernment, SystemSecurity

v7 of the journal docs here: http://hosting.zaonce.net/community/journal/v7/Journal_Manual.doc

Please report bugs through the normal bug reporting process, I am no longer monitoring this thread regularly
 

AnthorNet

AnthorNet
hchalkley said:
There's an update to the game being released this morning, with a few bug fixes - the full change notes will be posted in the usual place, but the changes specifically in the player journal are as follows:
• DockFighter event - fixed when piloted by AI
• Add a MaterialCollected event when material is first discovered
• Docked event - report data about station's faction as StationFaction, StationGovernment, StationEconomy, StationAllegiance; note Security is an attribute on the starsystem
• and for clarity, the data in Location and FSDJump events is now named SystemAllegiance, SystemEconomy, SystemGovernment, SystemSecurity

v7 of the journal docs here: http://hosting.zaonce.net/community/journal/v7/Journal_Manual.doc

Please report bugs through the normal bug reporting process, I am no longer monitoring this thread regularly
Click to expand...

Can we say well done on breaking third party apps? :D
 

Athan

Athan
I think what Anthornet meant to say was "can you give third party app authors a bit of a heads up on such changes in future, so they can have a released version that will handle both old and new name schemes?".
 

eventure

eventure
hchalkley said:
Please report bugs through the normal bug reporting process, I am no longer monitoring this thread regularly
Click to expand...

Okay, we will do it, but how about on improvement requests? Where should we post them?
Asking, because this thread will be no longer monitored and there is much room for improvements!!!
 

Genar-Hofoen

Genar-Hofoen
All the above comments are good.

Also - changing JSON key values during the live game, and unannounced until release? Tut-tut!

Anyways, Captain's Log 2 beta 6 released to take into account the JSON key changes :/
 

robbyp

robbyp
We (EDDiscovery) got caught with also (thankfully just broke the EDDN upload), but I think we have to think about it like this.

We can't control the input coming from Frontier journals. They could change stuff whenever.

So i've been making sure to be as defensive as possible in coding reading the entries in the journals. So no crashing if the data is not there. Default values etc.
 

Andargor

Andargor
Eventure said:
For me I think, it sounds like "No more comments please! We have done enough for you all, so please shut up."
Click to expand...

I'm gonna go glass half-full here, and still be grateful we got something, which is infinitely more than zero. This said Howard mentioned submitting bugs, but I guess this also means improvements would need to go to the Suggestions forum.

To get maximum exposure, I would suggest posting ideas/specs in this thread and then also posting in the Suggestions forum, but linking back to here for context. That should keep the message alive, hopefully without incurring the Wrath of the Mods.
 

nrage

nrage
C'mon guys, it's really not that hard to understand:

1. "Please report bugs through the normal bug reporting process"

If there are issues report them as a bugs via the normal bug reporting process, here:
https://forums.frontier.co.uk/forumdisplay.php/124-Elite-Dangerous-Bug-Reporting

This is likely because any further changes will need to be scheduled (think compete) with other new features/improvements for development time.

2. "I am no longer monitoring this thread regularly"

Don't expect responses from hchalkley, s/he is busy doing something else.


I suspect we're going to continue to see minor improvements on the log with each minor update. But, those improvements do have to compete with other features/improvements for development time. So, when we do report issues as bugs we should make sure to make it clear which issues are the most annoying so as to help with that scheduling.
 

Animator-Jonny

Frontier Animator
Frontier
Eventure said:
Okay, we will do it, but how about on improvement requests? Where should we post them?
Asking, because this thread will be no longer monitored and there is much room for improvements!!!
Click to expand...

Hey Eventure, if you write a report on the bug reporting section and it is valid suggestion, I will be sure to pass this onto hchalkley. :)

Eventure said:
For me I think, it sounds like "No more comments please! We have done enough for you all, so please shut up."
Click to expand...

Not at all, the bug reporting forums are looked at daily by a large amount of devs. So feel free to place your player journal feedback on there; plus QA-Mitch, QA-Mark and myself try and comment on all reports to let you know we have looked. :)
 
Last edited:

eventure

eventure
QA-Jonny said:
Hey Eventure, if you write a report on the bug reporting section and it is valid suggestion, I will be sure to pass this onto hchalkley. :)

Not at all, the bug reporting forums are looked at daily by a large amount of devs. So feel free to place your player journal feedback on there; plus QA-Mitch, QA-Mark and myself try and comment on all reports to let you know we have looked. :)
Click to expand...

Thank you, that gives me hope. Will do as requested, so keep an eye open.
 

GIF

GIF
Hey!
Please,
1. Add a marker of name planet for this events:
4.8 Lift Off & 4.12 Takedown.
2. Add a profit value for 7.5 Marketsell (it pilot can saw in game then sell cargo)
 

Playbahnosh

Playbahnosh
GIF said:
Hey!
Please,
1. Add a marker of name planet for this events:
4.8 Lift Off & 4.12 Takedown.
2. Add a profit value for 7.5 Marketsell (it pilot can saw in game then sell cargo)
Click to expand...

1, You already get the data of the body/station/system when you exit orbital cruise with the "4.11 SupercruiseExit" event (since you have to drop out of orbital/supercruise to land). You can reference that when you land or take off.

2, You can already get your profit margin with a simple calculation, the numbers are all there. TotalSale is basically (Count * SellPrice) and AvgPricePaid is what you paid per unit when you bought them. So the formula for calculating profit is TotalSale - (Count * AvgPricePaid).
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom