DarkFenX
commented
6 years ago I was thinking about what kind of information does mutated module name carry compared to base module name, and it's just the fact that module has been modified (while losing some info like exact base module type). So, i think that the best condensed format would be:
<base module name>
<abyssal extended data prefix><mutaplasmid grade name>: <comma-separated list of attributes and values (alphabet-sorted?)>Or, as example:
Gistii A-Type 1MN Afterburner
Unstable: capacitorNeed 21.3, cpu 16.2, speedFactor 179, power 13.5Biggest downside, as with any condensed form presented here, we have to find mutaplasmid using just base item name and mutaplasmid grade, but on the bright side it's very compact and clean. If we decide to stick to this format, two questions arise:
1) i have no idea how hard is it to get mutaplasmid from grade and base item name. Worst case we will have to create map {(base metagroup item, grade name): mutaplasmid} and maintain it manually. While we can do it ourselves as it's low-maintenance, if we expect other tools to support this format (eve client, if ccp ever gets to it), can we expect other developers to do it as well?
2) When exporting fits w/o mutated stats, do we export mutated item name (which points to item's metagroup and shows that it is modified) or base item name (exactly specifies type but omits that it has been mutated)? I feel that neither option is good, but we have to stick to one of these. Considering that mutated item name cannot be imported w/o additional data, i think that i prefer to just use base item name instead (and this will also be consistent with the extended format i just mentioned).
blitzmann
This one is VERY inconvenient because you have to pass abyssal stats to your friend along with the fit. I am mostly thinking about EFT-alike export-import because it's the one i see used the most often. Before actually implementing anything, wanted to share the idea and get feedback from interested parties.
For example, following format:
abyssal extended data prefix could be 2-4 spaces or some other way to visually separate/indent it, which is easy to parse and which doesn't produce visual clutter.
On UI export side, we could have single EFT radiobutton with two additional ticks below it (which become active when you select EFT format): export abyssal module stats and export implants (which should memorize their last used values, otherwise they will be very inconvenient).
Possible adjustments could be considered to compact it: 1) merge 1st and 2nd extended row (via comma or some other separator) 2) remove everything but mutaplasmid grade from mutaplasmid name
So with both applied, result would be:
But it would need smarter parser, as you will have to find appropriate mutaplasmid for specified typename based on partial mutaplasmid name.