Template talk:Pokémon Infobox

From Bulbapedia, the community-driven Pokémon encyclopedia.
Jump to navigationJump to search


Any parameters which are unused should be left out. Calling but leaving blank unused parameters can lead to errors.

  • name : English name. If unknown, leave out.
  • jname : Japanese name.
  • tmname : Romanisation of Japanese name. Trademarked version if available.
  • jtranslit : Transliteration of Japanese name.
  • category : Category name, from the Pokédex.
  • forme : Number of images to display. Only to be used if the Pokémon has more than one form.
  • form1 : Name of form 1, if applicable. Not needed for Pokémon with no forms.
  • form2 : Name of form 2, if applicable.
  • form3 : Name of form 3, if applicable.
  • form4 : Name of form 4, if applicable.
  • form5 : Name of form 5, if applicable.
  • form6 : Name of form 6, if applicable.
  • image : Filename of image, if not at the default location.
  • image2 : Filename of form 2 (or Mega Evolution) image.
  • image3 : Filename of form 3 (or Mega Evolution 2) image.
  • image4 : Filename of form 4 image.
  • image5 : Filename of form 5 image.
  • image6 : Filename of form 6 image.
  • mega : Name of the Mega Stone (first Mega Stone where applicable). Also controls Mega Evolution related displays.
  • mega2 : Name of the second Mega Stone. Also controls Mega Evolution related displays.
  • generation : Generation Pokémon was introduced
  • ndex : National Pokédex number
  • jdex : Johto Pokédex number. New number, where applicable.
  • oldjdex : Old Johto Pokédex number.
  • hdex : Hoenn Pokédex number
  • sdex : Sinnoh Pokédex number
  • udex : Unova (BW) Pokédex number
  • u2dex : Unova (B2W2) Pokédex number
  • karea : Kalos Pokédex area (Central, Coastal, or Mountain)
  • kdex : Kalos Pokédex number
  • adex : Alola Pokédex number
  • fbrow : Fiore Browser number
  • abrow : Almia Browser number
  • obrow : Oblivia (Present) Browser number
  • opbrow : Oblivia (Past) Browser number, including prefix
  • type1 : Type. (First type listed in the Pokédex, where applicable)
  • type2 : Second type, if applicable.
  • form2type1 : Form 2 type. (First type listed in the Pokédex, where applicable)
  • form2type2 : Form 2 second type, if applicable.
  • form3type1 : Form 3 type. (First type listed in the Pokédex, where applicable)
  • form3type2 : Form 3 second type, if applicable.
  • form4type1 : Form 4 type. (First type listed in the Pokédex, where applicable)
  • form4type2 : Form 4 second type, if applicable.
  • form5type1 : Form 5 type. (First type listed in the Pokédex, where applicable)
  • form5type2 : Form 5 second type, if applicable.
  • form6type1 : Form 6 type. (First type listed in the Pokédex, where applicable)
  • form6type2 : Form 6 second type, if applicable.
  • abilitylayout : The basic desired layout of the Abilities, in the form "cells_in_first_row+cells_in_second_row". (Each cell can contain one or two Abilities per form, or a Mega or Hidden Ability, mainly depending on which Ability parameters are set.)
  • abilitycold : If the Pokémon has a Hidden Ability that will be the only cell in the second row, set this to 2 so it spans both cells above
  • abilitycolm : If the Pokémon has a Mega Ability that will be the only cell in the second row, set this to 2 so it spans both cells above
  • ability1 : First (or only) standard Ability
  • ability2 : Second standard Ability
  • ability2-1 : Form 2 first (or only) Ability
  • ability2-2 : Form 2 second Ability
  • ability3-1 : Form 3 first (or only) Ability
  • ability3-2 : Form 3 second Ability
  • abilityd : Hidden Ability
  • abilitydcaption : A caption prefixed to the label for abilityd
  • abilityd2 : Second Hidden Ability (for an alternate form)
  • abilityd2caption : A caption prefixed to the label for abilityd2
  • abilitym : First (only) Mega Evolution Ability
  • abilitym2 : Second Mega Evolution Ability
  • gendercode : Byte setting for the species' gender ratios:
    • 256 = unknown, 255 = genderless, 254 = all female, 223 = 1 male:7 female, 191 = 1 male:3 female, 127 = 1 male:1 female, 63 = 3 male:1 female, 31 = 7 male:1 female, 0 = male only.
  • catchrate : Catch rate
  • egggroupn : Number of Egg Groups. 0 if "Undiscovered group" (i.e., no Eggs)
  • egggroup1 : Egg Group 1
  • egggroup2 : Egg Group 2
  • eggcycles : How many Egg cycles it takes for an Egg to hatch.
  • height-ftin : Imperial height
  • height-m : Metric height
  • height-ftin2 : Form 2 imperial height
  • height-m2 : Form 2 metric height
  • height-ftin3 : Form 3 imperial height
  • height-m3 : Form 3 metric height
  • weight-lbs : Imperial weight
  • weight-kg : Metric weight
  • weight-lbs2 : Form 2 imperial weight
  • weight-kg2 : Form 2 metric weight
  • weight-lbs3 : Form 3 imperial weight
  • weight-kg3 : Form 3 metric weight
  • expyield : Experience yield
  • oldexp : Experience yield prior to Gen V
  • g4exp : Experience yield in Gen IV, if Pokémon is available and has a different yield prior to Gen IV.
  • lv100exp : Total experience required to reach level 100. Sets levelling rate.
  • evforms : Number of forms which have different EV yield.
  • evtotal : Total EV yield
  • evhp : HP EV yield
  • evat : Attack EV yield
  • evde : Defence EV yield
  • evsa : Special attack EV yield
  • evsd : Special defence EV yield
  • evsp : Speed EV yield
  • evhp2 : Form 2 HP EV yield
  • evat2 : Form 2 attack EV yield
  • evde2 : Form 2 defence EV yield
  • evsa2 : Form 2 special attack EV yield
  • evsd2 : Form 2 special defence EV yield
  • evsp2 : Form 2 speed EV yield
  • evhp3 : Form 3 HP EV yield
  • evat3 : Form 3 attack EV yield
  • evde3 : Form 3 defence EV yield
  • evsa3 : Form 3 special attack EV yield
  • evsd3 : Form 3 special defence EV yield
  • evsp3 : Form 3 speed EV yield
  • evhp4 : Form 4 HP EV yield
  • evat4 : Form 4 attack EV yield
  • evde4 : Form 4 defence EV yield
  • evsa4 : Form 4 special attack EV yield
  • evsd4 : Form 4 special defence EV yield
  • evsp4 : Form 4 speed EV yield
  • body : Body style (number)
  • body2 : Form 2 body style (number)
  • foot2 : Second footprint file name, not including the leading F or file extension.
  • color : Color listed in the Pokédex.
  • formcolors : Set to "yes" if any forms have different colors.
  • friendship : Base friendship value.
  • pokefordex : Name for external links which don't use the standard name or ndex number

Let me know if there are any issues. Werdnae (talk) 08:09, 9 October 2013 (UTC)


Just wondered if maybe the border should be made 3px, and also, that the border woudl be that if the Pokémon has a secondary type the border would be the same color as the second type. Just so the Pokémon articles keep cohesive with the templates etc. ----samm :D 15:07, 4 November 2013 (UTC)

Also, when I edited Flabébé/Floette/Florges article, there is a mysterious 4 next to one of the images, despite there being no error in the code on the articles (or I seem to be missing) ----samm :D 19:17, 10 November 2013 (UTC)

Hidden Abilities.

So Duskull line gained Frisk in G6 (despite being a G4 Ability), while Litwick family got Shadow Tag changed to Infiltrator. There should be something to note that. Uploader (talk) 14:08, 28 November 2013 (UTC)

Footprint data for X/Y Pokémon

I'm not sure if this is technically possibly via MediaWiki, but if it is one could make the footprint area disappear, stretching the body style template if the national dex number is above 649. I propose this to remove all those broken file links. Pikachu Bros. (talk) 16:06, 28 February 2014 (UTC)

Yeah, it's certainly possible, and needs to be done. --Abcboy (talk) 21:11, 3 May 2014 (UTC)
It is possible, but may require some rearranging to implement. I'll speak with the other staff members to see about a solution. Berrenta (talk) 21:27, 21 August 2014 (UTC)

Missing padding for main page text

On my end, at least, the infoboxes don't seem to have left-edge padding, causing text in a page to run up to the edge, which makes a bit of text hard to read. I would attempt to fix it, but I am neither very familiar with table formatting, nor do I have the permissions to do so. Can someone who is able to make sure there is enough padding? --TruePikachu (talk) 04:23, 1 March 2014 (UTC)

Hoopa's form changes

Would it be possible for someone to please edit the template to account for the names of Hoopa's alternate forms (similar to what was done for Charizard and Mewtwo's dual Mega Evolutions)? The correct form names are "Hoopa Confined" and "Hoopa Unbound", though as it is now, the template displays them as "Confined Hoopa" and "Unbound Hoopa".

Xérnéas (talk) 22:46, 23 June 2015 (UTC)

How do the heights of the boxes in this template work?

Hi, sorry for asking a question like this, but I wonder, how do you make it so that the boxes that display the stats are the same height no matter what, in every resolution, browser and zoom %? For example, in the Sylveon (Pokémon) page, the gender and the catch rate boxes [the white boxes that contain the actual information] are the exact same size--symmetrical--even though the "Gender" box is larger than the "Catch rate" box; I assume that the "Catch rate" box automatically adjusted to the same height as the "Gender" box. How do you do this? I can't seem to find a solution for this problem that's in another wiki I'm part of. Over on that wiki, whenever one box has more info than the one next to it, they don't automatically adjust, and the only solution would be to add exact pixel heights, which would be unbelievably cumbersome for over 2,000 pages. I hope you find the time to answer my question, and if you don't want to, I understand. Thanks! ♥ 493Darkrai (talk) 01:11, 8 August 2015 (UTC)

Some updates

I just want to leave this somewhere it will hopefully be easy to remember. There are a couple things that need updating in this template. Whenever an update becomes convenient (perhaps whenever Gen VII info like the Pokedex/region name is added), hopefully these can be incorporated.

Form names

Some Pokemon like Hoopa should properly have "backwards" form names to how most other form names are constructed. The simple solution would be to just do something like replace

<small>{{{forme4|}}} {{{name|{{{tmname|}}}}}}</small>


<small>{{{override4|{{{forme4|}}} {{{name|{{{tmname|}}}}}}}}}</small>

(Or what-have-you. And that for each forme1-5 parameter, and perhaps forme6 for good measure.)

Hatch time

The hatch time has been wrong for a while (but then, so was Egg cycle). To fix this, these two pieces of code:


Should be changed to:

{{#expr: 257*{{{eggcycles|0}}}}}
{{#expr: 257*{{{eggcycles|0}}}+256}}

Tiddlywinks (talk) 03:53, 18 April 2016 (UTC)

As a couple of more trivial suggestions, I think it might be nice to change {{tt|*|Not legitimately obtainable as an Egg}} to <br><small>Egg not obtainable</small> just so that's not hidden (for smartphone users and such); and just for a sort of consistency, <span style="color:#000;">Undiscovered group</span> could be changed to <span style="color:#000;">Undiscovered</span> (this is shown if egggroupn is set to 0, but without that, Egg Groups are just displayed like "Field" and "Undiscovered"). Tiddlywinks (talk) 04:58, 18 April 2016 (UTC)
I am wondering if the parameters have been passed wrongly in some of the existing articles of legendary Pokemon? Hoopa, for example, passes
egggroupn=1 |
egggroup1=Undiscovered |
while if egggroupn was 0 in the first place, egggroup1 would not be necessary and would be automatically filled in by the template, along with the "not obtainable as egg" text. Chenzw (talk) 05:02, 18 April 2016 (UTC)
They're not exactly wrong. But at any rate, I'd ask you to just leave those egggroup1 parameters for now for the possibility of the changes below. =P (Hell, I should probably just make my own userpage for this template.)
Perhaps Ditto/Ditto's Egg Group could also receive a similar note when egggroupn is set to 0... |0=[[Undiscovered (Egg Group)|<span style="color:#000;">Undiscovered group</span>]] could be removed (it'll fall through to call on egggroup1) along with =[[Category:Undiscovered group Pokémon]] (the 0 case will then be grouped with 1, and work the same so long as egggroup1 has been set.
(Also, the Egg Group categories line could be shorter just by using <!--Egg Groups-->[[Category:{{{egggroup1}}} group Pokémon]] {{#ifeq: {{{egggroupn|0}}}|2|[[Category:{{{egggroup2}}} group Pokémon]]}} instead... Again, so long as egggroup1 has been set.) Tiddlywinks (talk) 05:22, 18 April 2016 (UTC)
I've mocked up the changes above at User:Tiddlywinks/Pokémon Infobox, excluding the form override (I'll set about just reworking that entirely later so we just need a parameter for each full form name). You can test it on any species pages by substituting my userspace template name and previewing (it might be quickest to just copy the template call to an empty/dummy page and preview there).
Removing the Not legitimately obtainable as an Egg note from hovertext kind of required an extra parser function to work (perhaps) best, so it may be preferred to leave out that extra #ifeq and the change to the note... Tiddlywinks (talk) 23:40, 28 April 2016 (UTC)

Alola Dex

Since the Alola Pokédex is split up into areas like the Kalos dex, should this template be updated to allow for specifying the dex region? N. Onymous (talk) 23:19, 1 December 2016 (UTC)

Pokemon can be in multiple island dexes. That would just get too messy to be worth anything. Tiddlywinks (talk) 00:17, 2 December 2016 (UTC)
Besides the official numbering from the original Alola Pokédex list remains the same despite the how the Pokémon are listed in each of the different four variants such as Pikipek remaining listed as 010 despite being presented first for the other three variants and therefore unlike Kalos each area does not have it's own separate numbering, which unfortunately renders this unnecessary. -Tyler53841 (talk) 07:19, 3 December 2016 (UTC)

body style

zygarde has 3 body style due to its forme. can someone update the template so we can add the third forme in? the current template only support 2 body style. -Pokeant (talk) 02:52, 26 January 2017 (UTC)

Is the catch probability still accurate in Generation VI?

It is noted in the 'Catch rate' page that the formula was changed to make the catch probability approximately the same as in Generation V, which only did three shake checks instead of four. Thus, wouldn't the probabilities be slightly higher than those indicated by this template?

For example, the probability of catching a fully healthy Pidgey with a basic Poké Ball works out to 43.9%, not 33.3%.

- Andrio Celos (talk) 09:56, 23 April 2017 (UTC)

I haven't done the numbers, but I think that article says that basically, the lowered shake probability (exactly) makes up for an additional shake check, so that the overall catch probability remains largely unchanged. I imagine you've just made an error somewhere in your calculation!? Nescientist (talk) 11:15, 23 April 2017 (UTC)
Generation V changed the system so that three shake checks were done instead of four. The success chance of each shake check is almost exactly the same ((a/256)^(1/4)). This means that the chance of catching a Pokémon actually increased a little ((a/256)^(3/4)), compared to Generation IV.
Generation VI does four shake checks again, but the success chance of each shake check was increased ((a/256)^(3/16)) so that the overall chance of catching the Pokémon didn't change ((a/256)^(3/4)).
- Andrio Celos (talk) 14:06, 23 April 2017 (UTC)

Catch rate formula error

Like Generation V, the catch probability for an ordinary Poké Ball at full HP in Generation VI–VII is very nearly (C / 765)^.75, where C is the species catch rate. However, the formula used in the infobox — C/255 * 1/3 — does not include the exponent. This means the probability given is lower than the actual probability; for instance, Pokémon with a catch rate of 30 are listed as having a 3.9% chance to be caught, when the correct value 8.8%.

To correct this, I'm pretty sure the line just needs to be changed from

| {{#iferror: {{#expr:{{{catchrate|Unknown}}} - 1}}|Unknown|{{{catchrate|3}}} <small>({{tt|{{#expr: ({{{catchrate|3}}}/255 * 1/3 * 100) round 1}}%|When an ordinary Poké Ball is thrown at full health}})</small>}}


| {{#iferror: {{#expr:{{{catchrate|Unknown}}} - 1}}|Unknown|{{{catchrate|3}}} <small>({{tt|{{#expr: (({{{catchrate|3}}}/765)^.75 * 100) round 1}}%|When an ordinary Poké Ball is thrown at full health}})</small>}}

Randomwaffle23 (talk) 22:31, 17 January 2018 (UTC)

Can someone please correct this? I get at least one person a month asking me why my catch rate calculators (which do the math correctly) don't agree with Bulbapedia. Dragonfree (talk) 07:06, 16 May 2019 (UTC)
I've updated this to use the code provided by Randomwaffle23 (which I checked against the formula on Dragonfree's site The Cave of the Dragonflies to confirm it was correct). I've also explicitly mentioned the generation for which it is applicable in the tooltip now, so that when it falls out of date again, at least it will state the generation for which it was true. It will still be wrong for Ultra Beasts, because standard Poké Balls do not have a 1× catch rate against them (and I'm not really sure whether it makes more sense to show the probability of using a Poké Ball or a Beast Ball on them).
Furthermore, I think it's worth re-evaluating whether a full-health catch rate is actually helpful to readers. The assumptions made are not the conditions under which people normally catch Pokémon. The percentage seems rather pointless. --SnorlaxMonster 12:26, 16 May 2019 (UTC)

Why hasn't this template been updated for USUM yet?

Pokemon Ultra Sun and Ultra Moon have been out for two months now. This template still hasn't been updated for those games. What gives? MasterBraixen96 (talk) 21:34, 20 January 2018 (UTC)

Bumping this. This and the held items template are still outdated, and should be relatively easy to update.Lanthanum (talk) 17:48, 23 January 2018 (UTC)
7 months and still nothing. I think it's time for an update. Oneofthosedf (talk) 19:59, 11 June 2018 (UTC)
It hasn't been updated as we are working on moving the numbers to the Pokedex boxes. The technicalities of this are taking slightly longer then expected. --Spriteit (talk) 08:16, 12 June 2018 (UTC)

Kanto Pokedex expansion

I think that Kanto formula should be updated, as in LGPE Meltan and Melmetal are respectively #152 and #153. Asmod96 (talk) 01:00, 18 November 2018 (UTC)

The problem is that there's no kanto variable in the template. Changing the {{{ndex|000}}} to {{{ndex|{{{kantodex|000}}}}}} in

| style="{{#ifexpr: {{{ndex|999}}} < 152||display: none;}}" | <nowiki>#{{{ndex|000}}}<br/><small>[[List of Pokémon by Kanto Pokédex number|<span style="color:#000;">Kanto</span>]]</small></nowiki>


<!--Regional Pokédex-->{{#ifexpr: {{{ndex|999}}} < 152|[[Category:Pokémon in the Kanto Pokédex|{{{ndex|}}}]]}}


<!--Regional Pokédex-->{{#if: {{{kantodex|}}}|[[Category:Pokémon in the Kanto Pokédex|{{{kantodex|}}}]]|{{#ifexpr: {{{ndex|999}}} < 152|[[Category:Pokémon in the Kanto Pokédex|{{{ndex|}}}]]}}}}

...would basically do it, I think (kantodex since kdex is taken by Kalos). If a different category was wanted for the two Pokemon in question (ala Black 2/White 2 having separate categories from Black/White), it would even be simpler since you just add another line to the second part rather than messing with an extra #if. - Reboot (talk) 18:33, 27 November 2018 (UTC)

PS: I can't remove the messed-up copy/paste error in the first line of my own post? Seriously? - Reboot (talk) 18:35, 27 November 2018 (UTC)

I fixed for you wrote, as mentioned in the comment above yours however the Number section won't be getting an update as we are planning to display them elsewhere on the page. --Spriteit (talk) 05:13, 28 November 2018 (UTC)
If we are going to update, we need to update the body style too. The template still only show two body style, but with zygarde complete, we need to update it to include three instead. -Pokeant (talk) 09:21, 24 December 2018 (UTC)

USUM Pokedex numbers and ability changes

The template needs an a2dex parameter for USUM Pokedex numbers and some way to say that Pelipper can't have drizzle before Generation 7. sumwun (talk) 18:21, 30 March 2019 (UTC)

The numbers are now in the Pokedex entry templates (if you haven't noticed), the numbers in the infobox will eventually be taken out. We're still working on updating the templates.--ForceFire 04:54, 31 March 2019 (UTC)
The same discussion is happening here, just so we keep most of it in one page. Suic12- (talk) 13:45, 31 March 2019 (UTC)
Is anyone still working on making the template say Pelipper can't have drizzle in gen 6? sumwun (talk, contribs) 03:36, 13 February 2020 (UTC)

Fix for Toxtricity

Due to the way that the infobox is set up, the form names are incorrect for abilities, types, heights, and weights if there are more than 2 forms, the first 2 forms are in one image, and the data listed are different between forms. This can be seen on Toxtricity's page, where Amped Form's abilities are listed as just "Toxtricity" and Low Key Form's ablities are listed as "Gigantamax Toxtricity", because those are the two images in the infobox.

I have made a fix that (hopefully) should not interfere with anything else, but would fix the above problem and also allow us to implement similar ideas on pages like Urshifu. It adds new parameters, "form1alt", "form2alt", etc, which will change the name of the forms except for the images at the top.

I have tested this with Toxtricity and it does work.

The updated template can be found here. --celadonk (talk) 17:44, 12 January 2020 (UTC)

Update to hatch time calculation

As per Egg cycle, an egg cycle is now 256 steps in Gen 7 (no word on Gen 8). This template's calculation currently uses 257 steps per cycle, which is from Gens 5 and 6. This should be a quick fix. ~ Serial Colour (talk) 13:57, 25 May 2020 (UTC)

Not enough freedom to set experience yields for different gens

Some Pokémon (like Delcatty) had their exp yields change in gen 7, and others (like Gardevoir) had their exp yields change in gen 8. In the current template, there is no way to display these differences. TotalPotato (talk) 10:37, 29 May 2020 (UTC)

We do have plans in the works for this infobox and I've noted down this issue as well as the previous ones. Increasing changes within the games and forms add an increasing amount of issues. We're trying to come up with a capable compromise. --Spriteit (talk) 04:59, 6 June 2020 (UTC)

An oversight

So I was looking at the page for Slowbro, and I noticed an oversight with this template. Since Galarian Slowbro now takes the place of the "form2" variable, the template says that Galarian Slowbro has the "Pokémon consisting of a head and arms" body shape instead of Mega Slowbro like it's supposed to since Mega Slowbro is now "form3" instead of the "form2" and the "body2" variable only accounts for the "form2" variable, so I think that a "body3" variable should be added to the template to fix this issue. Luigi1234 (talk) 16:17, 4 July 2020 (UTC)

ability1note and ability2note

Can someone add ability1note and ability2note parameters similar to egggroup1note? sumwun (talk, contribs) 05:26, 6 March 2021 (UTC)

3 or more Body Shapes

As of right now, Slowbro's Galarian form is given the body form of the Mega, as the Mega has a different body form, but the Galarian form does not, which presents inaccurate information. Additionally, in many cases where Pokémon have three or more forms, such as Necrozma and Zygarde, those additional forms are not covered at all. A simple solution to both of these issues would be to add something similar to how Vivillon's different colors are handled:

{{#if: {{{formbody|}}}|<br><small>Other forms may have other shapes.</small>}}

WOLKsite (talk) 11:26, 6 March 2021 (UTC)