Discussion [Request] More JSON Key/Enum Value Data Dumps

Controllerface

Controllerface
I've made a similar request before regarding a desire to have a full dump of all the possible JSON values for materials, but after some time working on my little helper app, I would expand my request to cover all enumerable items that can appear in the JSON structure of events. In the current documentation, some of the values are already full enumerated (which has been very helpful) for example, there's an appendix entry showing all possible values for module attributes. There are also several related to exploration data, ranks etc. I just wish i had the same set of ALL possible values for what are clearly a finite set of enumerable values. I don't even necessarily need any plain text descriptions or anything like that, I just want to know what the possible values are so I can make an app that supports players who may use ships and weapons I don't care to use (like some of my wing mates) without needing to essentially get EVERYTHING in the game myself, just so i have an example data object in my own journal file.

- Engineering modifications: (ex: Armour_HeavyDuty, Engine_Dirty, Weapon_Efficient, etc.)
- Engineer Experimental Effects: (ex:special_armour_chunky, special_shield_regenerative, special_corrosive_shell, etc. )
- Hardpoint Modules: (ex: hpt_beamlaser_fixed_huge, hpt_pulselaserburst_turret_small, hpt_multicannon_gimbal_large, etc.)
- Internal Modules: (ex: int_hyperdrive_size8_class5, int_fueltank_size5_class3, int_dronecontrol_collection_size5_class5, etc.)

These are just the most useful ones I can think of right now that aren't enumerated but there's probably others as well that other developers such as myself might be interested in.

I know there are several places online where I can try and find these values, for example the Coriolis.io folks have a lot of their data on github, and this has proven pretty helpful for my project. But there are mistakes here and there in the data, and it's clear pretty much all of this data is being compiled by hand by people writing tools such as the one i'm working on, or webapps like Coriolis. I have to say, i'm actually really enjoying working on this app, it's already been quite useful for me and it's a great way to add more flavor to the game between updates. I just wish I could spend less time trying to reverse engineer all of this data when it should be possible to simply include all the possible values in the documentation.

Thanks,
CMDR Controllerface
 

Controllerface

Controllerface
Thanks, I've been using sites like this to get most of my data, and I do really appreciate the work they've put in. I still think it's not unreasonable to ask Frontier to dump the actual JSON keys they use.

https://github.com/EDCD/coriolis-data is another one i'll mention as useful, in case anyone else comes along here, just be mindful there's a few typos/errors here and there. That's not confined to coriolis' data either. ED hipyard and otehrs i've been scraping all have a few minor errors like that.

And that's really the issue I have mostly, not to knock the hard work the community has put in to compile these lists, but they really shouldn't need to do so much of it. I'm sure there's an enum (or several) that could simply be iterated and printed intot he Journal DOC that contains the entire range of possible names for things. The fact that it exists for some things, which again I appreciate, indicates that it is at least something Frontier realizes is useful.

I'm guessing that it's simply not a priority, which I understand. There's probably a million other things they are concerned with that are higher priority. I'm hoping if I just keep making enough noise they will find a spare moment to do it one of these days :)
 

Controllerface

Controllerface
was on vacation and just saw this. joined :)

I'm still tinkering away on my app, it's still a bit rough but I've got a very small group of friends helping me kick the tires. Once it's a little more polished I hope to get some feedback from the wider community.
 
You must log in or register to reply here.
Back
Top Bottom