|
|
| Line 489: |
Line 489: |
| | <noinclude> | | <noinclude> |
| | | | |
| − | NOTE: This is a temporary location for this template. If accepted for use it will be moved to use a better name. | + | NOTE: This is a copy of the template created by Miranda McLaughlin. It is for testing purposes only!!!. See the real template here [[Template:MmTestFitTemplate]] |
| | | | |
| − | ==Features==
| |
| − | *Horizontally expandable to display EFT format and/or fitting notes
| |
| − | *Cliking on a module while using the in game browser will bring up info about that module
| |
| − | *Clicking EVE button while using the in game browser will display the fit in game
| |
| − | *Indicator of fitting difficulty for quickly determining if you can fit everything
| |
| − | *Indicator for whether or not the fit is acceptable under the WarSOP (and clicking the indicator brings you to the relevant section of the WarSOP)
| |
| − | *Keep track of when the fit was designed to quickly determine if the fit is still valid
| |
| − | *Mousing over a module will display the name of the module
| |
| − | *Distinguishes between filled, empty, and non-existent slots
| |
| − |
| |
| − | ==Using the Template==
| |
| − | With more features comes more complexity. A tool to automatically generate template code is currently in development. In the meantime, if you want to use this template you'll have to create the code manually. The format is as follows:
| |
| − |
| |
| − | <pre>
| |
| − | {{mmTestFitTemplate|
| |
| − | ship= |
| |
| − | fitName= |
| |
| − | high1name= |
| |
| − | high1filename= |
| |
| − | high1typeid= |
| |
| − | high2name= |
| |
| − | high2filename= |
| |
| − | high2typeid= |
| |
| − | ...
| |
| − | mid1name= |
| |
| − | mid1filename= |
| |
| − | mid1typeid= |
| |
| − | mid2name= |
| |
| − | mid2filename= |
| |
| − | mid2typeid= |
| |
| − | ...
| |
| − | low1name= |
| |
| − | low1filename= |
| |
| − | low1typeid= |
| |
| − | low2name= |
| |
| − | low2filename= |
| |
| − | low2typeid= |
| |
| − | ...
| |
| − | subsystem1name= |
| |
| − | subsystem1filename= |
| |
| − | subsystem1typeid= |
| |
| − | subsystem2name= |
| |
| − | subsystem2filename= |
| |
| − | subsystem2typeid= |
| |
| − | ...
| |
| − | rig1name= |
| |
| − | rig1filename= |
| |
| − | rig1typeid= |
| |
| − | rig2name= |
| |
| − | rig2filename= |
| |
| − | rig2typeid= |
| |
| − | ...
| |
| − | drone1name= |
| |
| − | drone1filename= |
| |
| − | drone1typeid= |
| |
| − | drone2name= |
| |
| − | drone2filename= |
| |
| − | drone2typeid= |
| |
| − | ...
| |
| − | charge1name= |
| |
| − | charge1filename= |
| |
| − | charge1typeid= |
| |
| − | charge2name= |
| |
| − | charge2filename= |
| |
| − | charge2typeid= |
| |
| − | difficulty= |
| |
| − | warsop= |
| |
| − | version= |
| |
| − | shipDNA= |
| |
| − | notes=
| |
| − | }}
| |
| − | </pre>
| |
| − |
| |
| − | The parameters are as follow:
| |
| − | *ship - The name of the ship
| |
| − | *fitName - The name of the fit
| |
| − | *Various modules - more on this below
| |
| − | *difficulty - The difficulty of fitting the ship in this way. Value can be are 0 (easy), 1 (medium), or 2 (hard)
| |
| − | *warsop - denotes whether the fit is approved for use during war. Value can be Y (approved), R (restricted/experienced pilots only), or N (not approved).
| |
| − | *version - An indicator for the version of eve the fir was designed under. I find that a three letter abbreviation of the expansion title followed by the expansion version number fits best.
| |
| − | *shipDNA - The shipDNA string for the fit. More info about shipDNA strings can be found <a href="http://wiki.eveonline.com/en/wiki/Ship_DNA">here</a>. Possibly the most troublesome part to get right.
| |
| − | *notes - A string of notes about the fit. This should be in the format "note 1</li><li>note 2</li><li>note 3" without the quotes.
| |
| − | <br />
| |
| − | Each modules is denoted using three parts:
| |
| − | *(slot name)(slot number)name (e.g. high1name)- The name of the module
| |
| − | *(slot name)(slot number)filename (e.g. high1filename) - The filename of the image to use for the module. For the sake of consistency it should be "Module icon (base item name) (tech1/tech2/faction/officer/deadspace).png" without quotes, e.g. Module icon heavy missile launcher tech1.png. NOTE: When the template goes into use I will be uploading more of the images and will attempt to create a list people can reference.
| |
| − | *(slot name)(slot number)typeid - The typeID of the module
| |
| − |
| |
| − | If a slot is to be left empty you can set the name as "open", minus quotes, and omit the filename and typeid in order to have an empty slot be displayed. If the ship does not have a certain slot (e.g. subsystems an eighth high slot) you can omit adding that slot to the code entirely.
| |
| − | <br />
| |
| − | An example of the template is as follows:
| |
| − | <pre>
| |
| − | NOTE: This fit is entirely made up to demonstrate how to use the fit.
| |
| − | <br />
| |
| − | {{mmTestFitTemplate|
| |
| − | ship=Drake|
| |
| − | fitName=Test|
| |
| − | high1name='Malkuth' Heavy Missile Launcher I|
| |
| − | high1filename=Module icon heavy missile launcher tech1.png|
| |
| − | high1typeid=8101|
| |
| − | high2name='Malkuth' Heavy Missile Launcher I|
| |
| − | high2filename=Module icon heavy missile launcher tech1.png|
| |
| − | high2typeid=8101|
| |
| − | high3name='Malkuth' Heavy Missile Launcher I|
| |
| − | high3filename=Module icon heavy missile launcher tech1.png|
| |
| − | high3typeid=8101|
| |
| − | high4name='Malkuth' Heavy Missile Launcher I|
| |
| − | high4filename=Module icon heavy missile launcher tech1.png|
| |
| − | high4typeid=8101|
| |
| − | high5name=open|
| |
| − | high6name=open|
| |
| − | mid1name=Adaptive Invulnerability Field II|
| |
| − | mid1filename=Module icon adaptive invulnerability field tech2.png|
| |
| − | mid1typeid=2281|
| |
| − | mid2name=Adaptive Invulnerability Field II|
| |
| − | mid2filename=Module icon adaptive invulnerability field tech2.png|
| |
| − | mid2typeid=2281|
| |
| − | mid3name=Large Shield Extender II|
| |
| − | mid3filename=Module icon shield extender tech2.png|
| |
| − | mid3typeid=3841|
| |
| − | mid4name=open|
| |
| − | mid5name=open|
| |
| − | low1name=Damage Control II|
| |
| − | low1filename=Module icon damage control tech2.png|
| |
| − | low1typeid=2048|
| |
| − | low2name=Ballistic Control System II|
| |
| − | low2filename=module icon ballistic control system tech2.png|
| |
| − | low2typeid=22291|
| |
| − | low3name=Ballistic Control System II|
| |
| − | low3filename=module icon ballistic control system tech2.png|
| |
| − | low3typeid=22291|
| |
| − | low4name=open|
| |
| − | rig1name=Medium Core Defense Field Extender I|
| |
| − | rig1filename=Module icon shield rig tech1.png|
| |
| − | rig1typeid=31790|
| |
| − | rig2name=Medium Core Defense Field Extender I|
| |
| − | rig2filename=Module icon shield rig tech1.png|
| |
| − | rig2typeid=31790|
| |
| − | rig3name=open|
| |
| − | drone1name=Hobgoblin I|
| |
| − | drone1filename=Module icon hobgoblin tech1.png|
| |
| − | drone1typeid=2454|
| |
| − | drone2name=open|
| |
| − | drone3name=open|
| |
| − | charge1name=Caldari Navy Scourge Heavy Missile|
| |
| − | charge1filename=Module icon scourge heavy missile faction.png|
| |
| − | charge1typeid=27441|
| |
| − | charge2name=open|
| |
| − | charge3name=open|
| |
| − | difficulty=1|
| |
| − | warsop=N|
| |
| − | version=RET 1.0.3|
| |
| − | shipDNA=24698:8101;4:2281;2:3841;1:2048;1:22291;2:31790;1:31754;1:2454;1:27441;1::|
| |
| − | notes=First note</li><li>Second note</li><li>Third Note
| |
| − | }}
| |
| − | </pre>
| |
| − |
| |
| − | If you have any questions, comments, or concerns please contact Miranda McLaughlin in game or via the E-UNI forums.
| |
| | </noinclude> | | </noinclude> |
