Are there, or could there be, plans to create an additional file where factions, allegiances, governments, states and their influence levels data dumps can be made into?
Discussion Commanders log manual and data sample
- Thread starter Zac Antonaci
- Start date
Are there, or could there be, plans to create an additional file where factions, allegiances, governments, states and their influence levels data dumps can be made into?
Quick summary of latest journal changes in the works:
In 2.3 Beta 1:
• Include starsystem name in StartJump event
• (in doc) Include description of Passengers event
• Write a ship's Loadout when buying or swapping ships
• Loadout now includes ship type, id number, name; and the health and value of each module
• Loadout now includes non-user-editable modules (in particular, the cargo bay door) in order to show the power priority
To be Included in 2.3 Beta 2:
• Add an event in Helm's log when a player crew member launches a fighter: "CrewLaunchFighter"
• Add an event in Helm's log when another crew member changes role "CrewMemberRoleChange"
• The "StationType" value will now show "SurfaceStation" rather than a blank string
• The "Docked" event will now include the station's distance from the drop-in star as "DistFromStarLS"
To be Included in 2.3 Beta 3:
• The "Location"/"FSDJump" event now includes breakdown of all local minor factions, each with name, influence, govt, state, allegiance
In 2.3 Beta 1:
• Include starsystem name in StartJump event
• (in doc) Include description of Passengers event
• Write a ship's Loadout when buying or swapping ships
• Loadout now includes ship type, id number, name; and the health and value of each module
• Loadout now includes non-user-editable modules (in particular, the cargo bay door) in order to show the power priority
To be Included in 2.3 Beta 2:
• Add an event in Helm's log when a player crew member launches a fighter: "CrewLaunchFighter"
• Add an event in Helm's log when another crew member changes role "CrewMemberRoleChange"
• The "StationType" value will now show "SurfaceStation" rather than a blank string
• The "Docked" event will now include the station's distance from the drop-in star as "DistFromStarLS"
To be Included in 2.3 Beta 3:
• The "Location"/"FSDJump" event now includes breakdown of all local minor factions, each with name, influence, govt, state, allegiance
Last edited:
Hallelujah! Thanks for this Howard, especially if you had to argue the toss with the designers
.
Much obliged, sir.
You just made a lot of people very happy
ps; can it also include pending and recovering states?
Hallelujah!
This makes me think, though - earlier you made it clear, that the PowerPlay status request would be outside the scope of the journal, because it doesn't directly relate to the player's activities.
So - what about including the PowerPlay numbers in the FSDJump? We already get the power(s), if it's a control, exploited, expansion etc, so why not expand this, such that for control/expansion systems it has the fortification/expansion and undermining/opposition triggers and values, and that for preparation systems it has the preparation numbers for each power?
This directly relates to the player's activities, for most systems it won't add to the journal (most systems aren't in PowerPlay), and for most systems in PowerPlay it won't add anything either, because they are exploited and not controlled.
Awesome!
Can we also get the full stats of the componets, either as engineer modifications (+12% mass, +52 optimized mass etc) or absolute values? Either would do. Would be a huge game changer to get this exported automatically.
This is great. What would be greater, greatest even, would be the same when opening the system map (BGS trackers everywhere would love you much).
Best news I've had all day. I'd also like it to include pending and recovering states as well as active.
Hmm, I'm still opposed to making this available for the reasons I stated in the group leaders forum.
But now the flood gates have been opened, let's not fool ourselves in to thinking that we're limited to just the data we've collected personally. Within weeks there will be websites appearing to analyse all the data collected by CMDRs around the galaxy. So FD, why not just put all the influence, state values, and pendings/recoveries on the web yourselves. Now it's available in the logs, we all know this is going to end up the same as the many trading tools out there, so just bite the bullet and publish the data yourselves.
All you're achieving by making it available in the logs is forcing the community to do it themselves the hard way using the power of the crowd - but it will still happen. If you're going to do it (and I'm definitely NOT in favour) at least do the job properly.
Sorry, no: I think that information is only held on the server database - it's not present in the data structures I have available to me at the time you enter the system
I was asked by the designers not to include the details of engineer mods values, as the internal raw values I have access to are not the same as the results that are displayed in the GUI, this extra complexity adds support problems and potential future compatibility problems.
Please please reconsider. We already obtain the raw data from the companion API and it's incredibly useful for projects such as Coriolis and ED:Shipyard to accurately represent the ship build.
We're not asking you to provide something additional, we're just asking for equality with the existing API.
Link? Or is this a private forum? I am a group leader, tho my group is quite small.
I don't think it will be as bad as you think.
Most commanders (wild guess, 80%+) do not care about factions, at all, or if they do it's a transitory interest. Certainly not like they do trade data, shipyard or outfitting information. So, the motivation for 3rd party tool developers to add support to collect all of this is fairly low to start with. I'm still pretty certain it will happen, though, just because they already have faction lists per system and the completeness gremlin will goad them into it.
But, more importantly..
The commanders that do care about factions are only likely to care about their own faction, or factions in/around their systems. And.. they will want up to the day/tick information and will not be able to rely on crowd sourced information, especially for less visited systems which will be many days out of date. So, they will still have to gather it themselves regardless, this change will just make that process less of a chore. This fact, and the fact that the information is tied to FSDJump (instead of "opening system map") means commanders have to actually visit systems to gather it, which is for the best (it's why I've been asking for it on these events specifically) because then it still involves actual game play to achieve the collection of the information.. you have to send out your scouts.
TL;DR Crowd sourcing this information won't actually be a huge benefit to player factions who need more up-to-date information than this would provide.
So, the only way we could get these in the journal would be an event which fired when the player opened the RHS panel and selected a faction in the list of factions (where it displays these states). Any chance of that?
Edit: I have updated my earlier bug report here
Last edited:
The thread if you have access (sounds like you do):
- https://forums.frontier.co.uk/showthread.php/233486-Raw-Data-for-the-Background-Simulation
Apologies for linking to something that many won't have access to. My concerns may be over the top, it depends on how prevalent use of the apps become I guess. You may well be correct that it won't make a massive difference. It's a topic with many arguments that's for sure.
Last edited: