EVE Technology Lab

Regarding the use of 'chargepresets', what's the purpose of using them this way? After all the name can be determined through the typeid with a lookup in SDE.
And in case it's just for loadout readability then why don't you add a 'modulepresets' for the same purpose?

Edit: Obviously I can't get the meaning of the 'chargepresets' element. Reading the specs again, names of modules and charges can be added optionally by specifying a 'typename' key-value pair. Still trying to wrap my head around it.

I've pushed an experimental validator to the repository. Feel free to test it, look at the source and share your insights.

@Desmont McCallock: the repo also contains an example, non-trivial loadout. Maybe looking at it will help you understand how charge presets work, because I couldn't make any sense of your two last posts ;)

The chargepresets key is there to store the name and description of the charge preset. Typically an entity could display something like this to allow the user to select a preset: screenie


I don't see how it's easier to "code a condition to discard any following duplicate" rather than just storing the presets in the specified order (and possibly overwriting any previous ones). Also, in my opinion, common sense expects the last declaration to always have the precedence.

As planned, the draft expired today and is now the official specification for CLF version 1.

This means that all non-trivial changes will be for the next version of the format.

To all the interested developers, you can now start supporting the format knowing it can no longer change!

Specification is here: http://artefact2.com/clf/spec-common-loadout-format-01 (and also in the git repository).

Enjoy your Sunday!

Is this still going forward? (sorry about the necro)

I had a question. In your introduction you mention "The common loadout format is designed to be easy to parse by programs and easy to read by humans.".

Whilst the former of this statement is true and I think the CLF is an excellent concept I do not believe that the later is necessarily true.

My question is; is it your intent by this statement that you expect humans to paste the JSON data into forums discussions and emails? The reason I ask is because the eve forums and email can eat up the tab formatting, rendering the code difficult to read.

Whilst the EFT format suffered the lack of typeid problem amongst others, it can be pasted into the forums and read by people easily.

{
"ship": {"typeid": 24698, "typename": "Drake" },
"presets": [
{
"presetname": "Meta 4 launchers",
"modules": [
{ "typeid": 8105, "charges": [{ "typeid": 209 }] },
{ "typeid": 8105, "charges": [{ "typeid": 209 }] },
{ "typeid": 8105, "charges": [{ "typeid": 209 }] },
{ "typeid": 8105, "charges": [{ "typeid": 209 }] },
{ "typeid": 8105, "charges": [{ "typeid": 209 }] },
{ "typeid": 8105, "charges": [{ "typeid": 209 }] },
{ "typeid": 8105, "charges": [{ "typeid": 209 }] }
],
"chargepresets": [
{ "id": 0, "name": "Scourge missiles" }
]
},
{
"presetname": "Tech II launchers",
"modules": [
{
"typeid": 2410,
"charges": [
{ "typeid": 209 },
{ "typeid": 2629, "cpid": 1 },
{ "typeid": 24513, "cpid": 2 }
]
},
{
"typeid": 2410,
"charges": [
{ "typeid": 209 },
{ "typeid": 2629, "cpid": 1 },
{ "typeid": 24513, "cpid": 2 }
]
},
{
"typeid": 2410,
"charges": [
{ "typeid": 209 },
{ "typeid": 2629, "cpid": 1 },
{ "typeid": 24513, "cpid": 2 }
]
},
{
"typeid": 2410,
"charges": [
{ "typeid": 209 },
{ "typeid": 2629, "cpid": 1 },
{ "typeid": 24513, "cpid": 2 }
]
},
{
"typeid": 2410,
"charges": [
{ "typeid": 209 },
{ "typeid": 2629, "cpid": 1 },
{ "typeid": 24513, "cpid": 2 }
]
},
{
"typeid": 2410,
"charges": [
{ "typeid": 209 },
{ "typeid": 2629, "cpid": 1 },
{ "typeid": 24513, "cpid": 2 }
]
},
{
"typeid": 2410,
"charges": [
{ "typeid": 209 },
{ "typeid": 2629, "cpid": 1 },
{ "typeid": 24513, "cpid": 2 }
]
}
],
"chargepresets": [
{ "id": 0, "name": "Scourge missiles" },
{ "id": 1, "name": "Scourge fury missiles" },
{ "id": 2, "name": "Scourge precision missiles" }
]
}
],
...
}