Difference between revisions of "Template:ShipFitting"
From EVE University Wiki
m (Fixed warsop hoverovers.) |
(Adding headers to allow indexing in table of contents.) |
||
| Line 71: | Line 71: | ||
.shipFitting .fittingHeader span { | .shipFitting .fittingHeader span { | ||
margin-left: 21px; | margin-left: 21px; | ||
| + | } | ||
| + | |||
| + | .shipFitting .fittingHeader span h5 { | ||
| + | color: #CCCCCC; | ||
| + | margin: 0px; | ||
| + | font-size: 14px; | ||
| + | border: none; | ||
| + | font-weight: normal; | ||
| + | padding: 0px; | ||
| + | display: none; | ||
} | } | ||
| Line 345: | Line 355: | ||
<div class="fittingHeader"> | <div class="fittingHeader"> | ||
<div class="uniLogo">[[File:E-UNI Emblem.png|x18px|middle|link=]]</div> | <div class="uniLogo">[[File:E-UNI Emblem.png|x18px|middle|link=]]</div> | ||
| − | <span>{{{ship}}}: {{{fitName}}}</span><div class="shipInfo" data-typeid="{{{shipTypeID}}}" title="View ship (in game)">SHIP INFO</div> | + | <span>{{{ship}}}: {{{fitName}}}<h5>{{{fitName}}}</h5></span><div class="shipInfo" data-typeid="{{{shipTypeID}}}" title="View ship (in game)">SHIP INFO</div> |
</div> | </div> | ||
| Line 600: | Line 610: | ||
</div> | </div> | ||
<noinclude> | <noinclude> | ||
| + | __NOTOC__ | ||
==Features== | ==Features== | ||
Revision as of 00:51, 23 March 2013
{{{fitName}}}
SHIP INFO
EFT
[{{{ship}}}, {{{fitName}}}]
FITTING DIFFICULTY
WARSOP APPROVED
EVE VERSION
unknown
RECOMMENDED SKILLS
NOTES
Features
- Item names on image hover
- Clicking on item picture brings up item info in-game
- Clicking SHIP INFO button brings up ship info in-game
- Clicking EVE button displays fitting in-game
- Clicking EFT, skills, or notes button opens respective panel
- Fitting difficulty indicator
- WarSOP compliance indicator with reason displayed on icon hover
- EVE version to determine if a fit is still valid
Template Format
To automatically generate template code from EFT code you can use the tool located here.
To format of the code is as follows:
{{ShipFitting|
ship=|
shipTypeID=|
fitName=|
fitID=|
high1name=|
high1typeID=|
mid1name=|
mid1typeID=|
low1name=|
low1typeID=|
subsystem1name=|
subsystem1typeID=|
drone1name=|
drone1typeID=|
charge1name=|
charge1typeID=|
rig1name=|
rig1typeID=|
difficulty=|
warsop=|
warsopReason=|
version=|
shipDNA=|
skills=|
notes=}}
The parameters are:
- ship - The name of the ship
- shipTypeID - The typeID of the ship
- fitName - The name of the fit
- fitID - A (hopefully) unique identifier for the fit. By appending "#(fitID)" to the end of a ship page of the wiki you can link directly to a specific fit. The automatic tool generates this by replacing all spaces in the fit name with a "-".
- high1name, mid1name, low1name, etc. - The name of the module in that slot. Set as "open" for an empty slot or omit is slot does not exist.
- high1typeID, mid1typeID, low1typeID, etc. - The typeID of the module in that slot. Can be omitted if the slot is empty or does not exist.
- difficulty - The difficulty of the fit. Possible values are "0" for beginner, "1" for advanced, and "2" for expert. Please use your best judgement when assigning difficulty levels.
- warsop - Whether or not the fit is approved for use during war. Possible values are "A" for approved for everyone, "S" for requires sophomore title, and "G" for required graduate title, and "D" for director authorization required.
- warsopReason - The reason for the indicated warsop rating. This will be displayed when hovering over the warsop icon on restricted and not approved fittings only.
- version - The version of EVE the fit was created for.
- shipDNA - The shipDNA string for the fit. More information can be found here
- skills - A list of recommended skills separated by "</li><li>".
- notes - A list of notes separated by "</li><li>".
If you want multiple fittings on the same line place the code for the second fitting directly after the first. e.g. like this:
shipDNA=|
skills=|
notes=}}{{ShipFitting|
ship=|
Example
An example of a proper fitting would be:
shipTypeID=24688| fitName=Vanguards a| fitID=Vanguards-a| high1name=Modal Mega Neutron Particle Accelerator I| high1typeID=7783| high2name=Modal Mega Neutron Particle Accelerator I| high2typeID=7783| high3name=Modal Mega Neutron Particle Accelerator I| high3typeID=7783| high4name=Modal Mega Neutron Particle Accelerator I| high4typeID=7783| high5name=Modal Mega Neutron Particle Accelerator I| high5typeID=7783| high6name=Modal Mega Neutron Particle Accelerator I| high6typeID=7783| high7name=Modal Mega Neutron Particle Accelerator I| high7typeID=7783| high8name=Modal Mega Neutron Particle Accelerator I| high8typeID=7783| mid1name=Adaptive Invulnerability Field II| mid1typeID=2281| mid2name=EM Ward Field II| mid2typeID=2301| mid3name=Federation Navy Stasis Webifier| mid3typeID=17559| mid4name=Federation Navy Stasis Webifier| mid4typeID=17559| mid5name=Sensor Booster II| mid5typeID=1952| mid6name=Tracking Computer II| mid6typeID=1978| low1name=Damage Control II| low1typeID=2048| low2name=Magnetic Field Stabilizer II| low2typeID=10190| low3name=Magnetic Field Stabilizer II| low3typeID=10190| low4name=Magnetic Field Stabilizer II| low4typeID=10190| low5name=Tracking Enhancer II| low5typeID=1999| drone1name=Hobgoblin I x5| drone1typeID=2454| drone2name=open| drone3name=open| drone4name=open| drone5name=open| charge1name=Scan Resolution Script| charge1typeID=29011| charge2name=Optimal Range Script| charge2typeID=28999| charge3name=Caldari Navy Antimatter Charge L| charge3typeID=21740| charge4name=open| charge5name=open| rig1name=Large Anti-Thermal Screen Reinforcer I| rig1typeID=26082| rig2name=Large Core Defense Field Extender I| rig2typeID=26088| rig3name=Large Core Defense Field Extender I| rig3typeID=26088| difficulty=1| warsop=Y| warsopReason=test| version=RET 1.0| shipDNA=24688:7783;8:1952;1:1978;1:2281;1:2301;1:17559;2:1999;1:2048;1:10190;3:26082;1:26088;2:2454;5:21740;1:28999;1:29011;1::| skills=Gunnery Supports IV</li><li>Caldari Battleship IV| notes=Short range blasters</li><li>Something else}}
If you have any questions or concerns or find any issues, please post in this thread on the E-UNI forums
