FANDOM


Template documentation follows
Note: the template above may sometimes be partially or fully invisible.
ViewEditHistory

Description

Use this template to create an Infobox for Fanon pages. It covers Fanon Tanks, Bosses, Enemies, Game Modes, structures, & more. It can be used to insert background music, set up a mini-navbox from within the Infobox itself (that works in Mobile) & it can also be used to designate the author of a conception. If used properly, it can also apply categories automatically (only in certain namespaces), so be sure to read the syntax section carefully for usage information.

Syntax

All values

{{Fanon
<!-- Main Section -->
|main title                     =
|main image                     =
|main image caption             =
|author-username                =
|author-nickname                =
|adoptee-username               =
|adoptee-nickname               =
|collaborators                  =

<!-- For Tanks -->
|nottank                        =
|tank details title             =
|tank image                     =
|tank image caption             =
|tier?                          =
|tank icon image                =
|tank weapons?                  =
|tank attacks?                  =
|other tank info?               =
|previous tank upgrade          =
|next tank upgrade              =

<!-- For Bosses & Enemies -->
|notboss                        =
|boss details title             =
|boss image                     =
|boss image caption             =
|boss HP?                       =
|boss health regen?             =
|boss body damage?              =
|boss damage resistance?        =
|boss speed?                    =
|boss detection range?          =
|boss EXP?                      =
|boss game modes?               =
|boss spawn locations?          =
|spawn message?                 =
|boss chance of spawning        =
|specials?                      =
|boss ammunition?               =
|boss weapons?                  =
|game ends when killed?         =
|intro                          =

<!-- For Structures -->
|structure details title        =
|structure image                =
|structure image caption        =
|structure number               =
|suggested level                =
|structure purpose              =
|structure rarity               =
|structure entities             =
|structure enemies              =
|structure bosses               =
|structure landmarks            =
|structure spawn rate           =
|previous structure             =
|next structure                 =

<!-- For Polygons -->
|notpolygon                     =
|polygon details title          =
|polygon image                  =
|polygon image caption          =
|polygon rarity?                =
|polygon spawn locations?       =
|polygon HP?                    =
|polygon health regen?          =
|polygon body damage?           =
|polygon EXP?                   =
|polygon variants?              =
|polygon nicknames?             =

<!-- For Game Modes -->
|notmode                        =
|game mode details title        =
|game mode image                =
|game mode image caption        =
|game mode closes?              =
|win condition?                 =
|number of teams?               =
|game mode button image         =
|bosses spawn in the mode?      =
|special tanks in the mode?     =
|other details about the mode?  =

<!-- For Events -->
|event details title            =
|event image                    =
|event image caption            =
|event start                    =
|start trigger?                 =
|event end                      =
|end trigger?                   =
|event start message            =
|event end message              =

<!-- For Background Music -->
|background music title         =
|music                          =

<!-- For Navigation -->
|related conceptions title      =
|nav                            =
}}

Main Section

  • |main title =
    • Controls the text at the top of the template.
    • Accepts any values.
  • |main image =
    • Controls the image directly below the title.
    • Accepts only image file names.
  • |main image caption =
    • Controls the text directly below the aforementioned image.
    • Accepts any values.
  • |author-username =
    • Creates a field that links to the author’s message wall.
    • Accepts only the exact username, no templates.
  • |author-nickname =
    • Changes the display text of the aforementioned field.
    • Accepts text only.
  • |adoptee-username =
    • Creates a field that links to the adoptee’s message wall.
    • Accepts only the exact username, no templates.
  • |adoptee-nickname =
    • Changes the display text of the aforementioned field.
    • Accepts text only.
  • |collaborators =
    • Creates a “Conception Collaborators” field.
    • Accepts lists.
    • Alternatively, inputting public will replace the output & categorize the page as Public Fanon instead of the usual Collaborative Fanon.
    • Using this field disables the author & adoptee fields.


For Tanks

  • |nottank =
    • Category controller. Input anything in this field to stop the Fanon Tank Category from being added when Tanks fields are used.
    • Accepts any values.
  • |tank details title =
    • Changes the default “Tank Details” section header.
    • Accepts short text values.
  • |tank image =
    • Controls the image directly below the “Tank Details” section header.
    • Accepts only image file names.
  • |tank image caption =
    • Controls the text directly below the aforementioned image.
    • Accepts any values.
  • |tier? =
    • Use of this field will override the nottank field & force the Fanon Tanks Category always!
    • Creates a “Tier” field.
    • Accepts integers from 1 to 7, applying appropriate Categories based on the input.
    • It can accept other values, but it will not Categorize the page properly if the value isn’t 1, 2, 3, 4, 5, 6, or 7.
  • |tank icon image =
    • Creates a small icon of the tank being described.
    • Accepts only file names.
  • |tank weapons? =
    • Creates a “Weapon(s)” field.
    • Accepts any values.
  • |tank attacks? =
    • Creates an “Attack(s)” field.
    • Accepts any values.
  • |other tank info? =
    • Creates an “Other Info” field.
    • Accepts any values.
  • |previous tank upgrade =
    • Creates an “Upgrades from” field.
    • Accepts any values.
    • This field will always be on the left at the bottom of the Tanks section.
  • |next tank upgrade =
    • Creates an “Upgrades to” field.
    • Accepts any values.
    • This field will always be at the bottom of the Tanks section.


For Bosses & Enemies

  • |notboss =
  • |boss details title =
    • Changes the default “Boss Details” section header. For example, |boss details title = Enemy Details will change the text to “Enemy Details”.
    • Accepts short text values.
  • |boss image =
    • Controls the image directly below the “Boss Details” section header.
    • Accepts only image file names.
  • |boss image caption =
    • Controls the text directly below the aforementioned image.
    • Accepts any values.
  • |boss HP? =
    • Creates an “HP” field.
    • Accepts any values.
  • |boss health regen? =
    • Creates a “Health Regen” field.
    • Accepts any values.
  • |boss body damage? =
    • Creates a “Body Damage” field.
    • Accepts any values.
  • |boss damage resistance? =
    • Creates a “Damage Resistance” field.
    • Accepts any values.
  • |boss speed? =
    • Creates a “Movement Speed” field.
    • Accepts any values.
  • |boss detection range? =
    • Creates a “Detection Range” field.
    • Accepts any values.
  • |boss EXP? =
    • Creates an “EXP Reward” field.
    • Accepts any values.
  • |boss game modes? =
    • Creates a “Gamemode(s)” field.
    • Accepts any values.
  • |boss spawn locations? =
    • Creates a “Spawn Location(s)” field.
    • Accepts any values.
  • |spawn message? =
    • Creates a “Spawn Message” field.
    • Accepts any values.
  • |boss chance of spawning =
    • Creates a “Chance of Spawning” field.
    • Accepts any values.
  • |specials? =
    • Creates a “Specials” field.
    • Accepts any values.
  • |boss ammunition? =
    • Creates an “Ammunition” field.
    • Accepts any values.
  • |boss weapons? =
    • Creates a “Weapon(s)” field.
    • Accepts any values.
  • |game ends when killed? =
    • Creates a “Game ends when killed?” field.
    • Accepts any values.
  • |intro =
    • Creates a new section with “Intro” as the header, along with an empty field below which spans both columns, in order to allow a (short) paragraph to be inputted.
    • Accepts any values.
    • This output will always be italicized.


For Structures

  • |structure details title =
    • Changes the default “Structure Details” section header.
    • Accepts short text values.
  • |structure image =
    • Controls the image directly below the “Structure Details” section header.
    • Accepts only image file names.
  • |structure image caption =
    • Controls the text directly below the aforementioned image.
    • Accepts any values.
  • |structure number =
    • Creates a “Number” field.
    • Accepts any values.
  • |suggested level =
    • Creates a “Suggested Level” field.
    • Accepts any values.
  • |structure purpose =
    • Creates a “Purpose” field.
    • Accepts any values.
  • |structure rarity =
    • Creates a “Rarity” field.
    • Accepts any values.
  • |structure entities =
    • Creates an “Entities within” field.
    • Accepts any values.
  • |structure enemies =
    • Creates an “Enemies within” field.
    • Accepts any values.
  • |structure bosses =
    • Creates a “Bosses within” field.
    • Accepts any values.
  • |structure landmarks =
    • Creates a “Landmarks” field.
    • Accepts any values.
  • |structure spawn rate =
    • Creates a “Spawn Rate” field.
    • Accepts any values.
  • |previous structure =
    • Creates a “Previous” field.
    • Accepts any values.
    • This field will always be on the left at the bottom of the Structures section.
  • |next structure =
    • Creates a “Next” field.
    • Accepts any values.
    • This field will always be at the bottom of the Structures section.


For Polygons

  • |notpolygon =
    • Category controller. Input anything in this field to stop the Fanon Polygons Category from being added when Polygon fields are used.
    • Accepts any values.
  • |polygon details title =
    • Changes the default “Polygon Details” section header.
    • Accepts short text values.
  • |polygon image =
    • Controls the image directly below the “Polygon Details” section header.
    • Accepts only image file names.
  • |polygon image caption =
    • Controls the text directly below the aforementioned image.
    • Accepts any values.
  • |polygon rarity? =
    • Creates a “Rarity” field.
    • Accepts any values.
  • |polygon spawn locations? =
    • Creates a “Spawn Location(s)” field.
    • Accepts any values.
  • |polygon HP? =
    • Creates an “HP” field.
    • Accepts any values.
  • |polygon health regen? =
    • Creates a “Health Regen” field.
    • Accepts any values.
  • |polygon body damage? =
    • Creates a “Body Damage” field.
    • Accepts any values.
  • |polygon EXP? =
    • Creates an “EXP Reward” field.
    • Accepts any values.
  • |polygon variants? =
    • Creates a “Variants” field.
    • Accepts any values.
  • |polygon nicknames? =
    • Creates a “Nickname(s)” field.
    • Accepts any values.


For Game Modes

  • |notmode =
    • Category controller. Input anything in this field to stop the Fanon Game Modes Category from being added when Game Mode fields are used.
    • Accepts any values.
  • |game mode details title =
    • Changes the default “Game Mode Details” section header.
    • Accepts short text values.
  • |game mode image =
    • Controls the image directly below the “Game Mode Details” section header.
    • Accepts only image file names.
  • |game mode image caption =
    • Controls the text directly below the aforementioned image.
    • Accepts any values.
  • |game mode closes? =
    • Creates a new field whose label is either “Arena Closure” or “Win Condition” depending on the next value.
    • Accepts any values.
  • |win condition? =
    • Changes the above field’s label from “Arena Closure” (the default) to “Win Condition” if true.
    • Accepts boolean expressions only (true / false or yes / no).
  • |number of teams? =
    • Creates a “# of Teams” field.
    • Accepts any values.
  • |game mode button image =
    • Creates a small icon of the Game Mode Button, like in diep.io.
    • Accepts only file names.
  • |bosses spawn in the mode? =
    • Creates a “Bosses Spawn?” field.
    • Accepts boolean expressions only (true / false or yes / no).
  • |special tanks in the mode? =
    • Creates a “Special Tanks” field.
    • Accepts any values.
  • |other details about the mode? =
    • Creates a horizontal “Other Details” field that will never be beside other fields, to allow it to be a bit longer if necessary.
    • Accepts any values.


For Events

  • |event details title =
    • Changes the default “Event Details” section header.
    • Accepts short text values.
  • |event image =
    • Controls the image directly below the “Event Details” section header.
    • Accepts only image file names.
  • |event image caption =
    • Controls the text directly below the aforementioned image.
    • Accepts any values.
  • |event start =
    • Creates a new field whose label is either “Start Time” or “Start Trigger” depending on the next value.
    • Accepts any values.
  • |start trigger? =
    • Changes the above field’s label from “Start Time” (the default) to “Start Trigger” if true.
    • Accepts boolean expressions only (true / false or yes / no).
  • |event end =
    • Creates a new field whose label is either “End Time” or “End Trigger” depending on the next value.
    • Accepts any values.
  • |end trigger? =
    • Changes the above field’s label from “End Time” (the default) to “End Trigger” if true.
    • Accepts boolean expressions only (true / false or yes / no).
  • |event start message =
    • Creates a “Start Message” field.
    • Accepts any values.
    • This output will always be italicized.
  • |event end message =
    • Creates an “End Message” field.
    • Accepts any values.
    • This output will always be italicized.


For Background Music

  • |background music title =
    • Changes the default “Background Music” section header.
    • Accepts short text values.
  • |music =
    • Creates an empty field in which to input SoundCloud & Spotify modules.
    • Accepts any values, however, it is designed to accept <soundcloud> & <spotify> entries especially, which can be inserted verbatim & have them work properly in desktop & mobile.
    • EXAMPLE:
      |music = <soundcloud url="https://soundcloud.com/kalarus/sets/music-i-like-1" height="" width="100%"/>
    • Multiple modules can be inserted, but the assumption is that you will only use one, or perhaps two at the most.


For Navigation (IMPORTANT! READ ALL!)

  • |related conceptions title =
    • Changes the default “Related Conceptions” section header.
    • Accepts short text values, such as “Ursuul’s Conceptions”.
  • |nav =
    • Allows you to input a subtemplate into this field. By specifying the conceptions you want to be in the nav in the subtemplate, & inserting the subtemplate in this field each time, you only need to make one edit to the subtemplate in order to update the navigation on all of your conceptions that use that subtemplate.
    • EXAMPLE SUBTEMPLATE: Template:Fanon/Ursuul.
    • EXAMPLE SYNTAX:
      {{Fanon|nav = {{Fanon/Ursuul}} }}
    • EXAMPLE OUTPUT:
    • Make sure the subtemplate is always categorized as Non-article, Data, or Design; otherwise the subtemplate will not show up in mobile.
    • Please do not use any inline styles (i.e. <div style="styles"></div>, <center></center>, et cetera) in your subtemplate, since there will eventually be default styling to make it look nice & standard across the site, so please only use links, text characters, or Info Icons (very small images with a link). Using inline styles will disrupt & possibly break the template in mobile.
    • If you absolutely must have special styles to make your navigation look fancy, please read the CSS section of this article.

Example

Input

{{Fanon
<!-- Main Section -->
|main title                     = Amphibian
|main image                     = AmphibianPhases.png
|main image caption             = Cool tank
|author-username                = Ursuul
|author-nickname                = Urthphuul
|adoptee-username               = Tacocat247
|adoptee-nickname               = Taco

<!-- For Tanks -->
|nottank                        = opahuvwbqbv
|tank details title             = Tanky Details
|tank image                     = Booster.png
|tank image caption             = Wrong image LoL
|tier?                          = 5
|tank icon image                = Booster.svg
|tank weapons?                  = Cannons (5)
|tank attacks?                  = Attacks with uhhhhhhhh idk
|other tank info?               = I b0rked the icon image too LoL
|previous tank upgrade          = {{f|Auto Flank}}
|next tank upgrade              = God Himself

<!-- For Bosses & Enemies -->
|notboss                        = IsEnemy
|boss details title             = Enemy Description
|boss image                     = Archprohet.png
|boss image caption             = Whut lmao
|boss HP?                       = 2 trillion
|boss health regen?             = 2 trillion/second
|boss body damage?              = Negative 1,000,000 (think about it)
|boss damage resistance?        = #Un
#Deux
#Trois
|boss speed?                    = 4
|boss detection range?          = OmNiSCieNCe ;D
|boss EXP?                      = .1 EXP
|boss game modes?               = [[Sandbox]]
|boss spawn locations?          = Down the street next to the homeless guy.
|spawn message?                 = Gimme yer belt
|specials?                      = He is a special boy :)
|boss ammunition?               = Bake’d Potatoes (no sour cream)
|boss weapons?                  = Catapult
|game ends when killed?         = idk probably
|intro                          = To be fair, you have to have a very high IQ to understand Rick and Morty. The humour is extremely subtle, and without a solid grasp of theoretical physics most of the jokes will go over a typical viewer’s head. There’s also Rick’s nihilistic outlook, which is deftly woven into his characterisation- his personal philosophy draws heavily from Narodnaya Volya literature, for instance. The fans understand this stuff; they have the intellectual capacity to truly appreciate the depths of these jokes, to realise that they’re not just funny- they say something deep about LIFE. As a consequence people who dislike Rick & Morty truly ARE idiots- of course they wouldn’t appreciate, for instance, the humour in Rick’s existential catchphrase “Wubba Lubba Dub Dub,” which itself is a cryptic reference to Turgenev’s Russian epic Fathers and Sons. I’m smirking right now just imagining one of those addlepated simpletons scratching their heads in confusion as Dan Harmon’s genius wit unfolds itself on their television screens. What fools.. how I pity them. 😂

<!-- For Game Modes -->
|notmode                        = afteahgf9egqbv9uervbpq
|game mode details title        = Da Best Mode
|game mode image                = YellowNicksSandbox2.png
|game mode image caption        = I don’t see any sand.
|game mode closes?              = Acquire 4 quintillion RappyBucks
|win condition?                 = true
|number of teams?               = idk 5
|game mode button image         = SandButton.png
|bosses spawn in the mode?      = yes
|special tanks in the mode?     = Lady Gaga
|other details about the mode?  = And yes, by the way, i DO have a Rick & Morty tattoo. And no, you cannot see it. It’s for the ladies’ eyes only- and even then they have to demonstrate that they’re within 5 IQ points of my own (preferably lower) beforehand. Nothin personnel kid 😎

<!-- For Structures -->
|structure details title        = Wallz n stuff
|structure image                = Walls.png
|structure image caption        = w8 those aren’t legit wallz
|structure number               = 1776
|suggested level                = 45-60
|structure purpose              = To annoy Drone users -_-
|structure rarity               = Grow like weeds
|structure entities             = It’s got some [[Polygons]] innit.
|structure enemies              = {{d|Nonagon Phages|Nonagons}} top waifu
|structure bosses               = [[Defender]] is worst girl
|structure landmarks            = *🅱️ig
*🅱️ol🅱️ous
*P L O T
|structure spawn rate           = They spawn pretty slowleh.
|previous structure             = None
|next structure                 = Yeah lemme get uhhhhhhhhh

<!-- For Events -->
|event details title            = It’s habbening
|event image                    = Suffering.png
|event image caption            = o
|event start                    = Donald Trump elected
|start trigger?                 = false
|event end                      = Cheeto Hitler impeached!!!11!1!!
|end trigger?                   = true
|event start message            = “Guys things are actually going pretty well”
|event end message              = “haha get rekt Blumpf”

<!-- For Background Music -->
|background music title         = M E M E
|music                          = <soundcloud url="https://soundcloud.com/xdefconx/we-are-number-one-xdefconx-synthesia-link-in-description" height="" width="100%"/>

<!-- For Navigation -->
|related conceptions title      = Ursuul’s Tankz
|nav                            = {{Fanon/Ursuul}}
}}

Output


Dependencies

This template relies upon several subtemplates in order to function.

Note about Categories

This template is designed to only apply Categories in the Fanon & Tale of Diep namespaces. This means that if all Categories are removed from a page in favor of this template, it can be moved in & out of the Fanon namespaces without unduly categorizing anything.

CSS

Sitewide CSS is used to construct each Infobox’s look & feel. Since this template is meant to be a replacement (or at least a supplement to) Navboxes, which typically have very personalized styles, you may desire for your Navigation section to be aesthetically unique. Your first assumption to accomplish this might be to simply make your subtemplate really fancy using tables & inline styling.

This, objectively speaking, is the worst approach to Portable Infobox aesthetics. Due to how Mercury works, your styles will die a fiery death the moment the skin is loaded, & may appear broken or not show up at all, to say nothing of how bad a table within an Infobox might look just within desktop.

So how to make it look unique? Sitewide CSS; it can be used to apply the styles to your Nav, & in Mercury the styles are simply peeled away, leaving behind useful links. Code Administrators have access to it, but normal users do not. So how can you get your Nav styled?

Imports. Artificial stylesheets (such as this one) can be made as subpages of your subtemplate (so, Template:Fanon/MyNavSubtemplate/code.css) which can be imported by Code Administrators into sitewide use, but this comes with security risks (since we are basically allowing anyone to write CSS for the entire website) so it has to be regulated. If you really need these styles (& by need, we mean that you are using a given nav on at least 30 pages) then we can import the stylesheet.

Once we have imported the stylesheet, you have to make it, which you can do by putting this in the /code.css subpage:

/* <syntaxhighlight lang="CSS"> */
.portable-infobox.pi-theme-InsertNameHere .pi-navigation {
    styles for the surrounding nav go here
}

.portable-infobox.pi-theme-InsertNameHere .pi-navigation .randomClass {
    styles for specific parts of the nav go here
}
/* </syntaxhighlight> */
InsertNameHere you would replace with the name of your subtemplate, but you’re not quite done. All you have to do now is apply |stylesheet = InsertNameHere to each Infobox which uses that nav, then bam, the styles will be applied.
If you are confused about how that works, or if you know how to use inline CSS but stylesheet CSS confuses you, you can take your questions to an Admin.
Community content is available under CC-BY-SA unless otherwise noted.