Difference between revisions of "User:Luxxianna Seraph/Sandbox/MissionHoverBox/PVEArticle/doc"

From EVE University Wiki
Jump to: navigation, search
(Created page with "; Description : This Template is designed to be used similar to {{T|ShipArticle}} as the primary template for a PVE Site (Mission, Combat, Data, Relic, Event, ect). : It is us...")
 
m (Fix broken link.)
 
(10 intermediate revisions by 2 users not shown)
Line 11: Line 11:
 
:: {{T|Expected NPC}}
 
:: {{T|Expected NPC}}
 
:: {{T|MissionLinks}}
 
:: {{T|MissionLinks}}
 +
; Used in concert with:
 +
: {{T|PVE}}
 +
: {{T|PVEFooter}}
 +
: {{T|PVEBoxLarge}} (through template PVE)
 +
: {{T|PVEBoxTooltip}} (through template PVE)
  
  
Line 18: Line 23:
 
         | Faction    =
 
         | Faction    =
 
         | Name      =
 
         | Name      =
 +
        | SiteType  =
 
         | TypeDetail =
 
         | TypeDetail =
        | SiteType  =
 
 
         | Rating    =
 
         | Rating    =
 
         | Location  =
 
         | Location  =
Line 41: Line 46:
 
         | HighestIndividualEHP      =  
 
         | HighestIndividualEHP      =  
 
         | WarpDisrupt                =
 
         | WarpDisrupt                =
 +
        | Webs                      =
 
         | EWAR                      =
 
         | EWAR                      =
 +
        | EWARQuickTip              =
 +
        | EWAR2                      =
 +
        | EWARQuickTip2              =
 +
        | EWAR3                      =
 +
        | EWARQuickTip3              =
 
         | Timer                      =  
 
         | Timer                      =  
 
         | MissionRewards            =
 
         | MissionRewards            =
 
         | MissionObjective          =
 
         | MissionObjective          =
 
         | MissionBlitz              =
 
         | MissionBlitz              =
 +
        | StandingLoss              =
 +
        | Walkthrough                =
 
}}
 
}}
 
</pre>
 
</pre>
Line 56: Line 69:
 
::; Faction2  
 
::; Faction2  
 
::: Any secondary Faction. Same rules as above.
 
::: Any secondary Faction. Same rules as above.
 +
::; SiteType  ''(Required)''
 +
::: The Type of site (case in-sensitive): Combat | Mission | Data | Relic
 
::; TypeDetail ''(Required)''
 
::; TypeDetail ''(Required)''
::: The Type of site (case in-sensitive): Combat | Mission | Data | Relic
+
::: This parameter produces a link to the relative article. The parameter is not case-sensitive.
::; SiteType ''(Optional if Mission)''
+
::: If Combat Site: anomaly, chemical, COSMOS, DED, expedition or unrated.  
::: One of anomaly, chemical, COSMOS, DED, expedition or unrated. This parameter produces a link to the relative article for combat sites. The parameter is not case-sensitive.
+
::: If Mission: Courier, Encounter, Mining, Trade, Industry, Exploration, Travel, Branch
 +
::: If Data or Relic: pirate, drone, AEGIS, sleeper cache, ghost, sleeper wormhole, silent, event, special
 
::; Rating
 
::; Rating
 
::: The Rating of the Signal (i.e. Class 4 Level 2) or the level of the mission (i.e. 3). If a mission, just put the number.
 
::: The Rating of the Signal (i.e. Class 4 Level 2) or the level of the mission (i.e. 3). If a mission, just put the number.
Line 101: Line 117:
 
::; HighestWaveEHP
 
::; HighestWaveEHP
 
::: The wave with the largest ''total'' EHP, of all the waves; i.e. the wave that is the tankiest.
 
::: The wave with the largest ''total'' EHP, of all the waves; i.e. the wave that is the tankiest.
::; EWAR
+
::; EWAR 1,2, 3
 +
::: Values: TP, ECM, WEAP
 
::: If there is EWAR present - use Web or Webs only to trigger special tooltips, otherwise include things such as Target Painter, Weapon Disrupt
 
::: If there is EWAR present - use Web or Webs only to trigger special tooltips, otherwise include things such as Target Painter, Weapon Disrupt
 
::; WarpDisrupt
 
::; WarpDisrupt
 
::: Any Value will trigger special tooltips - if possible include the total number of points possible at any given time, otherwise leave blank if 0.
 
::: Any Value will trigger special tooltips - if possible include the total number of points possible at any given time, otherwise leave blank if 0.
 +
::; Webs
 +
::: Any value will trigger special tooltips.
  
 
::; Damage
 
::; Damage
::; The damage type dealt by Faction. Auto populated by Faction value, only include (and use {{T|Damagetype}} ) if the damage dealt differs from the standard for that Faction (or is specific for a site where the Faction usually varies)
+
::: The damage type dealt by Faction. Auto populated by Faction value, only include (and use {{T|Damagetype}} ) if the damage dealt differs from the standard for that Faction (or is specific for a site where the Faction usually varies)
 
::; Resist
 
::; Resist
 
::: The resist values of the Faction. Auto populated by Faction value, only include (and use {{T|Damagetype}} ) if the resistances differ from the standard for that Faction (or is specific for a site where the Faction usually varies)
 
::: The resist values of the Faction. Auto populated by Faction value, only include (and use {{T|Damagetype}} ) if the resistances differ from the standard for that Faction (or is specific for a site where the Faction usually varies)
Line 126: Line 145:
 
::; Extra
 
::; Extra
 
::: Any extra notes for Missions
 
::: Any extra notes for Missions
 +
 +
:; Wiki Code Editable
 +
::; Walkthrough
 +
::: Use Walkthrough to put ... anything. Tables are a potential issue, so use {{T|NPCTableHead}} {{T|NPCTableSeparator}} {{T|NPCTableRow}} {{T|EndTable}} or similar. Always use {{T|EndTable}} and not <nowiki>|}</nowiki> because that will mess up tables. {{T|EndTable}} is generic and will work for any Table set of templates
  
 
; Boilerplate
 
; Boilerplate
 
: This template is designed to work in concert with {{T|PVE}}, {{T|PVEBoxTooltip}}, and {{T|PVEBoxLarge}} as the base page that the others will draw from. (In the same manner as {{T|ShipArticle}} and the Ship Database)
 
: This template is designed to work in concert with {{T|PVE}}, {{T|PVEBoxTooltip}}, and {{T|PVEBoxLarge}} as the base page that the others will draw from. (In the same manner as {{T|ShipArticle}} and the Ship Database)
 
: As such, the following boilerplate should be used on every page that implements this template as its primary (ie: all individual pages for Anomaly Sites and Missions)
 
: As such, the following boilerplate should be used on every page that implements this template as its primary (ie: all individual pages for Anomaly Sites and Missions)
<pre>
+
<pre><! Checked with ShipArticle/doc these noinclude markup-set needs escaping -->
<onlyinclude>{{{{#if:{{lc: {{{mode|}}}}}|{{#switch:{{{mode}}}|box=PVEBoxLarge|#default=PVEBoxTooltip}}|/PVEArticle}} <!--  Template marker : DON'T EDIT LINE -->
+
&lt;onlyinclude>{{{{#if:{{{mode|}}}|{{#switch:{{lc: {{{mode}}}}}|box=PVEBoxLarge|#default=PVEBoxTooltip}}|<!--/ is this the reason doc doesn't work? partly. -->PVEArticle}} <!--  Template marker : DON'T EDIT LINE -->
  
 
  <!-----------------------------------------------------------
 
  <!-----------------------------------------------------------
Line 144: Line 167:
 
   | Rating  =  
 
   | Rating  =  
 
... all the attributes used  
 
... all the attributes used  
}}</onlyinclude> <!-- Template marker : DON'T EDIT LINE -->
+
}}&lt;/onlyinclude> <!-- Template marker : DON'T EDIT LINE -->
 
 
... all walkthrough and additional tables/information/ect goes here
 
  
{{PVEFooter|Type}}
 
 
</pre>
 
</pre>
  
 
+
; TODO
 +
: This template is wrapping around {{T|Missiondetails}} and {{T|CMBSiteInfo}} - they contain a lot of the same parameters, but named differently. They should be brought in line with each other.
 +
: This template makes use of {{T|Expected NPC}} - the fact that this floats off on its own table in the middle of Anomaly site pages feels off. It should probably be incorproated into {{T|CMBSiteInfo}} and {{T|Missiondetails}} directly as part of their boxes.
 +
: Mission Sites use a left side, top box for all their info and a right side nav box. Combat sites use a right side info box and a footer nav box. Can we bring these two in line?
  
 
<includeonly>[[Category:Template]]<!-- Any categories for the template itself --></includeonly>
 
<includeonly>[[Category:Template]]<!-- Any categories for the template itself --></includeonly>
 
<noinclude>[[Category:Template documentation]]</noinclude>
 
<noinclude>[[Category:Template documentation]]</noinclude>

Latest revision as of 10:14, 24 June 2024

Description
This Template is designed to be used similar to {{ShipArticle}} as the primary template for a PVE Site (Mission, Combat, Data, Relic, Event, ect).
It is used in combination with with a few other templates, so any page that implements this template should use the boilerplate described below.
Its currently wrapping and dynamically choosing between {{CMBSiteInfo}} and {{Missiondetails}}. So a TODO would be to bring these two templates in line with each other in terms of parameter names.
Dependencies
Uses
{{NPCTableCSS}}
{{CMBSiteInfo}}
{{Missiondetails}}
{{Expected NPC}}
{{MissionLinks}}
Used in concert with
{{PVE}}
{{PVEFooter}}
{{PVEBoxLarge}} (through template PVE)
{{PVEBoxTooltip}} (through template PVE)


Syntax
{{PVEArticle
        | Faction    =
        | Name       =
        | SiteType   =
        | TypeDetail =
        | Rating     =
        | Location   =
        | ShortDesc  =
        | ShipLimit  =
        | TotalExpEnemiesSectionText = 
        | TotalExpFrigates           =
        | TotalExpDestroyers         = 
        | TotalExpCruisers           =
        | TotalExpBattlecruisers     = 
        | TotalExpBattleships        =
        | TotalExpCapitals           = 
        | TotalExpSentries           =
        | AccelerationGate           = 
        | RatsOnLandingBeacon        =
        | NumberOfWaves              = 
        | NumberOfRooms              =
        | HighestAlphaStrike         = 
        | HighestAverageDPS          = 
        | HighestWaveEHP             = 
        | HighestIndividualEHP       = 
        | WarpDisrupt                =
        | Webs                       =
        | EWAR                       =
        | EWARQuickTip               =
        | EWAR2                      =
        | EWARQuickTip2              =
        | EWAR3                      =
        | EWARQuickTip3              =
        | Timer                      = 
        | MissionRewards             =
        | MissionObjective           =
        | MissionBlitz               =
        | StandingLoss               =
        | Walkthrough                =
}}
Parameters
Shared parameters between Missions and Anomalies
Name (Required)
The Name of the Site - this should be the full name (and usually the same name as the page).
Faction (Required)
The Main Faction involved. This has a pretty decent list of potential values, such as Angel, Angels, Angel Cartel. It also directly informs any Damage or Resistance type fields.
Faction2
Any secondary Faction. Same rules as above.
SiteType (Required)
The Type of site (case in-sensitive): Combat | Mission | Data | Relic
TypeDetail (Required)
This parameter produces a link to the relative article. The parameter is not case-sensitive.
If Combat Site: anomaly, chemical, COSMOS, DED, expedition or unrated.
If Mission: Courier, Encounter, Mining, Trade, Industry, Exploration, Travel, Branch
If Data or Relic: pirate, drone, AEGIS, sleeper cache, ghost, sleeper wormhole, silent, event, special
Rating
The Rating of the Signal (i.e. Class 4 Level 2) or the level of the mission (i.e. 3). If a mission, just put the number.
Location
Where this anomaly takes place. No set values.
ShortDesc
A small one line description of the mission.
ShipLimit
Any limit that an acceleration gate may impose.
ShipSuggestion
A suggested ship class or link to a fit.
TotalExpEnemiesSectionText
A small one line description of the total expected enemies.
TotalExpFrigates
Total number of Frigates
TotalExpDestroyers
# Destroyers
TotalExpCruisers
# Cruisers
TotalExpBattlecruisers
# Battlecruisers
TotalExpCapitals
# Capitals
TotalExpSentries
# Sentries
AccelerationGate
Any Value in this param indicates yes, there are Acceleration Gate. Leave blank if there are none.
RatsOnLandingBeacon
Any value in this param indicates that there will be rats yellow-boxing as soon as a ship warps in directly to the beacon. Leave blank if this is not the case.
NumberOfWaves
The number of waves that will spawn after triggers are destroyed | reached. Leave blank if everything starts on grid
Number of Rooms
The number of rooms beyond the initial acceleration gate. Leave blank if there is no acceleration gate. If AccelerationGate is blank this property is ignored.
HighestAverageDPS
The Highest possible DPS value of an individual ship in all the waves; i.e. the worst threat.
HighestAlphaStrike
The Highest Alpha Strike damage in total for the wave, of all waves; i.e. the wave with the most threat.
HighestIndividualEHP
The largest EHP value of an individual ship in all the waves; i.e. the tankiest ship.
HighestWaveEHP
The wave with the largest total EHP, of all the waves; i.e. the wave that is the tankiest.
EWAR 1,2, 3
Values: TP, ECM, WEAP
If there is EWAR present - use Web or Webs only to trigger special tooltips, otherwise include things such as Target Painter, Weapon Disrupt
WarpDisrupt
Any Value will trigger special tooltips - if possible include the total number of points possible at any given time, otherwise leave blank if 0.
Webs
Any value will trigger special tooltips.
Damage
The damage type dealt by Faction. Auto populated by Faction value, only include (and use {{Damagetype}} ) if the damage dealt differs from the standard for that Faction (or is specific for a site where the Faction usually varies)
Resist
The resist values of the Faction. Auto populated by Faction value, only include (and use {{Damagetype}} ) if the resistances differ from the standard for that Faction (or is specific for a site where the Faction usually varies)
Damage2
Same as Damage but linked to Faction2
Resist2
Same as Resist but linked to Faction2
For Missions Only
StandingLoss
What standing loss will occur from completing this mission
MissionRewards
Rewards (ISK, Items) for completing this mission.
MissionObjective
The objective - Should be exactly what the Neocom shows in game.
MissionBlitz
How to blitz this mission - i.e. Kill the cruiser.
Extra
Any extra notes for Missions
Wiki Code Editable
Walkthrough
Use Walkthrough to put ... anything. Tables are a potential issue, so use {{NPCTableHead}} {{NPCTableSeparator}} {{NPCTableRow}} {{EndTable}} or similar. Always use {{EndTable}} and not |} because that will mess up tables. {{EndTable}} is generic and will work for any Table set of templates
Boilerplate
This template is designed to work in concert with {{PVE}}, {{PVEBoxTooltip}}, and {{PVEBoxLarge}} as the base page that the others will draw from. (In the same manner as {{ShipArticle}} and the Ship Database)
As such, the following boilerplate should be used on every page that implements this template as its primary (ie: all individual pages for Anomaly Sites and Missions)
<! Checked with ShipArticle/doc these noinclude markup-set needs escaping -->
<onlyinclude>{{{{#if:{{{mode|}}}|{{#switch:{{lc: {{{mode}}}}}|box=PVEBoxLarge|#default=PVEBoxTooltip}}|<!--/ is this the reason doc doesn't work? partly. -->PVEArticle}} <!--  Template marker : DON'T EDIT LINE -->

 <!-----------------------------------------------------------
 * PVE SITE ATTRIBUTES SECTION (last update : 2023-06-02)
 -------------------------------------------------------------
 * on editing the attributes, please make sure that you don't
 * leave/mistype any tags required. please follow the same
 * format below and edit only the values (after the = sign).
 ------------------------------------------------------------->

   | Name    = 
   | Rating  = 
... all the attributes used 
}}</onlyinclude> <!-- Template marker : DON'T EDIT LINE -->

TODO
This template is wrapping around {{Missiondetails}} and {{CMBSiteInfo}} - they contain a lot of the same parameters, but named differently. They should be brought in line with each other.
This template makes use of {{Expected NPC}} - the fact that this floats off on its own table in the middle of Anomaly site pages feels off. It should probably be incorproated into {{CMBSiteInfo}} and {{Missiondetails}} directly as part of their boxes.
Mission Sites use a left side, top box for all their info and a right side nav box. Combat sites use a right side info box and a footer nav box. Can we bring these two in line?