Difference between revisions of "Ship DNA"
m (Protected "Ship DNA" [edit=sysop:move=sysop]) |
|||
| Line 1: | Line 1: | ||
| + | [[Category:Development]] | ||
The Ship DNA format is a short hand notation to describe a ship and its fitting purely through the use of the type id's of the modules, items and the ship itself. It follows this basic format. | The Ship DNA format is a short hand notation to describe a ship and its fitting purely through the use of the type id's of the modules, items and the ship itself. It follows this basic format. | ||
Revision as of 20:43, 5 October 2009
The Ship DNA format is a short hand notation to describe a ship and its fitting purely through the use of the type id's of the modules, items and the ship itself. It follows this basic format.
<shipID>:<subsystemID>:...:<subsytemID>:<highslotmoduleID>:<quantity>:...:<highslotmoduleID>;<quantity>:<medslotmoduleID>;<quantity>:...:<medslotmoduleID>;<quantity>:<lowslotmoduleID>;<quantity>:...:<lowslotmoduleID>;<quantity>:<rigslotmoduleID>;<quantity>:...:<rigslotmoduleID>;<quantity>:<charge/droneID>;<quantity>:...:<charge/droneID>;<quantity>
Condensed
Ship:Subsystems(x5):Highs:Mediums:Lows:Rigs:Charges and Drones
First in the format is the ship id. This is followed by a colon (:). If T3 then this is followed by a list of 5 subsystems seperated with colons. This is followed by a list of module ids and quantity with colons (:) separating them. Each module id/quantity is in the format of <moduleID>;<quantity> Charges and Drones can also be included by listing them in the same fashion as modules.
All modules are assumed to be fit, therefor only include modules that will fit in the ship itself.
Notes: this needs confirmation as to the expected structure when used within the IGB javascript call Client.ShowFitting(FittingID) Also needs to be formated and rewritten probably.