Bulbapedia talk:Project Pokédex
What is the point of this?
I've never really gotten the point of why articles are titled like Pikachu (Pokémon) instead of just Pikachu. Can someone explain the reasoning behind this? CuteShaymin (talk) 21:27, 23 July 2024 (UTC)
- You can read up on our policy page here here. The reasoning is also given a much more in depth explanation by the Editor in Chief of the time here: Help talk:Disambiguation/Archive 1#Why we use the (Pokémon) in the first place?. MaverickNate 23:34, 23 July 2024 (UTC)
Upgraded Pokémon Infobox
We are upgrading the Pokémon infobox to be more user and mobile friendly, prioritize useful data, and shift some obsolete items elsewhere in the species articles. Our current sample from Tiddlywinks is here: Infobox Sample. Feedback is welcome, and opinions on what items should be included and why are appreciated. MaverickNate 04:02, 19 July 2024 (UTC)
- That is horribly useless it loses a whole bunch of data that isn't anywhere else. Catch Rate, Hatch Speed, EXP Yield, EXP Group, Color, Footprint, Friendship, Shape.AztecCroc (talk) 20:24, 19 August 2024 (UTC)
- I think we can reasonably move some of that info elsewhere without it needing to take up prime real estate in the infobox. Is there any info you've listed that you feel would be crucial for keeping at the top of the page? Personally, I think things like "footprint" really don't need to be there, and aren't useful/practical data that most players need or readers would be looking for. I'm happy to be proven wrong though. Landfish7 10:52, 20 August 2024 (UTC)
- Why should we move it elsewhere? As it stands currently you can get everything except moveset and stats just from looking at the infobox. Having everything about the Pokemon in one place is far more useful then having to jump around all over the place just because someone thought it looked better on mobile.AztecCroc (talk) 20:30, 25 August 2024 (UTC)
- This is just a draft, we might end up bringing some elements back, while moving others I think. In any case, the infobox will be remade not only for a better mobile experience, but also because it has a enormous technical debt under the hood. — Lakelimbo (talk) 00:00, 26 August 2024 (UTC)
- Why should we move it elsewhere? As it stands currently you can get everything except moveset and stats just from looking at the infobox. Having everything about the Pokemon in one place is far more useful then having to jump around all over the place just because someone thought it looked better on mobile.AztecCroc (talk) 20:30, 25 August 2024 (UTC)
- I think we can reasonably move some of that info elsewhere without it needing to take up prime real estate in the infobox. Is there any info you've listed that you feel would be crucial for keeping at the top of the page? Personally, I think things like "footprint" really don't need to be there, and aren't useful/practical data that most players need or readers would be looking for. I'm happy to be proven wrong though. Landfish7 10:52, 20 August 2024 (UTC)
Add tabbers for available Pokémon's learnsets by generation
Now that the TabberNeue has been set up, I am wondering if we can repurpose the learnset sections' structure using transcluded tabbers for available Pokémon's learnsets by generation.
Take the page Bulbasaur for example. If the proposal gets approved, then this is what the structure of the learnset section for the Bulbasaur page will look like:
===Learnset=== <tabbertransclude> Bulbasaur (Pokémon)/Generation IX learnset|Generation IX Bulbasaur (Pokémon)/Generation VIII learnset|Generation VIII Bulbasaur (Pokémon)/Generation VII learnset|Generation VII Bulbasaur (Pokémon)/Generation VI learnset|Generation VI Bulbasaur (Pokémon)/Generation V learnset|Generation V Bulbasaur (Pokémon)/Generation IV learnset|Generation IV Bulbasaur (Pokémon)/Generation III learnset|Generation III Bulbasaur (Pokémon)/Generation II learnset|Generation II Bulbasaur (Pokémon)/Generation I learnset|Generation I </tabbertransclude>
Next off is an example of the Oricorio page. Despite being unobtainable in Generation VIII, Oricorio is obtainable in the Generation IX games Pokémon Scarlet and Violet. As such, if the proposal gets approved, then this is what the structure of the learnset for the Oricorio page will look like:
===Learnset=== <tabbertransclude> Oricorio (Pokémon)/Generation IX learnset|Generation IX Oricorio (Pokémon)/Generation VII learnset|Generation VII </tabbertransclude>
Here's an example of the Xerneas page. Despite being obtainable in the Generation VIII games Pokémon Sword and Shield, Xerneas is unobtainable in the Generation IX games Pokémon Scarlet and Violet. If the proposal gets approved, then this is what the structure of the learnset section for the Xerneas page will look like:
===Learnset=== <tabbertransclude> Xerneas (Pokémon)/Generation VIII learnset|Generation VIII Xerneas (Pokémon)/Generation VII learnset|Generation VII Xerneas (Pokémon)/Generation VI learnset|Generation VI </tabbertransclude>
Last but not least, an example of the Furfrou page. Furfrou is unobtainable in the Generation VIII games Pokémon Sword, Shield, Brilliant Diamond, and Shining Pearl and Pokémon Legends: Arceus and the Generation IX games Pokémon Scarlet and Violet. If the proposal gets approved, then this is what the structure of the learnset section for the Furfrou page will look like:
===Learnset=== <tabbertransclude> Furfrou (Pokémon)/Generation VII learnset|Generation VII Furfrou (Pokémon)/Generation VI learnset|Generation VI </tabbertransclude>
It is important to know that the TabberNeue extension will be useful for learnset sections. That way, if the proposal gets approved, then we will not only create the Generation IX learnset subpages for Pokémon available in Scarlet and Violet, but also use the <noinclude> tags around the {{pokelinkback}} template. Would that be a great idea? SaturnMario, his talk and his contributions 01:43, 13 February 2025 (UTC)
- I already have a demo of this, over at Sandbox/Bulbasaur → Learnset.
- It uses
{{LearnsetTabber}}as a template, instead of having to add the<tabbertransclude>tag to manually pages. Having a template would also be easy to update for future generations. Note: The Template will currently only work for Gen 1 Pokemon, only because I haven't added the conditional yet (which should just be a simple#switch). I also had't considered Pokemon that were unobtainable in a middle generation, such as your other 3 examples above, so thank you for pointing that out. - I also suggest to wrap the actual learnset tables on learnset subpages in
<onlyinclude>s, to exclude any header info like{{pokelinkback}}s, and any footer info like Categories or Interwiki links. (Examples: 1, 2, 3, 4, 5, 6, 7, 8) As you said, we will need separate pages for the latest generation learnsets, which we currently don't have and will need to create. → SuperPikaPool13 22:22, 16 February 2025 (UTC)- However, there are a number of concerns with tabber-transcluding the learnsets this way:
- With 9 (right now) different pages with learnset tables to be included on the main species pages, there are concerns that this might break the max page size.
- The subheadings that are defined inside the
<tabbertransclude>tag don't show up in the TOC. This includes the subheadings such as "By leveling up", "By TM", etc. This would cause issues when linking directly to the section. - The demo did not consistently function correctly on the mobile skin at the time it was tested.
- Additionally, 9 tab headers would need horizontal scrolling on thinner screens, which is also something that is preferred to be prevented.
- The Tabber functionality (regular tabs as well as transcludes) needs JavaScript (JS) to be enabled for it to work. We would need to also consider a workaround in the case some readers have disabled JavaScript.
- I would like to your hear thoughts on this, as well as concerns and possible solutions from the wider community. In the meantime, feel free to use the Sandbox Demo linked above (or your own) to test out this feature or suggest improvements to it. → SuperPikaPool13 22:23, 16 February 2025 (UTC)
- However, there are a number of concerns with tabber-transcluding the learnsets this way:
Pokemon Ranger Sprites and Wild Pokemon Attacks
I'd like to add the sprite images for Pokemon from the Ranger games, as well as maybe including the attacks wild/ controlled Pokemon can use during captures. I know similar information for other games are included. Could the templates be updated so this information can be added? Drjwho (talk) 17:52, 20 July 2025 (UTC)
Inconsistency in the Pokemon Infobox image(s) for species with forms and gender differences
I first mentioned this to Coffee after noticing their name in some relevant page edit histories. After some discussion, they suggested I move the topic here. Our prior discussion can be found here.
In short, the images shown in the Pokemon Infobox are inconsistent across species and are misleading for some with multiple forms or gender differences. I used Wooper, Milotic, Hippopotas, Hippowdon, and Combee as specific examples with Coffee, but there are many others. Then there are Frillish, Unfezant, Meowstic, etc., which are inconsistent with the previous species by having their gender differences properly represented.
What is the rationale for this? Acetone15 (talk) 17:23, 21 April 2026 (UTC)
- A lot of this may fall under a potential
{{Pokémon Infobox}}update or an overall organizational and formatting overhaul for species pages. Perhaps in the future we will have a default image, but some sort of toggle to show gender differences or other forms, or we may decide to show gender differences in the Biology section. I think you bring about an important discrepancy, but it would likely be best addressed down the line (hopefully soon) alongside some of the other issues that have been brought up recently with the infobox. - For now though, I think it will provide the most stylistic consistency to use the official key artwork intended to represent the species. My concern otherwise is that we have cases like Torchic whose only different is a speck on its back sprite; I think most would agree that it would not be an excellent solution to prominently feature two back sprites of Torchic in the infobox at the top of the page to showcase this difference. Landfish7 17:36, 21 April 2026 (UTC)
- Ah, yeah, Torchic is a good counterexample.
- And to be clear, I agree that consistent art style is a valid rationale. Regardless, my suggestion is just to have a clear indicator of the existence of forms and gender differences near the infobox image(s), whether that is in the infobox, the introductory text, or an overall organizational and formatting overhaul.
- Are the other issues with the infobox you mentioned documented somewhere and, if so, is that where this discussion should be? Acetone15 (talk) 23:41, 22 April 2026 (UTC)
Add availability on Pokemon Champions?
Should there be a line in the game availability section for each Pokémon whether they are obtainable/usable in Pokemon Champions, in line with other side games? EpicScizor (talk) 11:21, 11 June 2026 (UTC)
Do not list a Pokémon's pronunciation in its trivia
A Pokémon's pronunciation is too insignificant to include as trivia. If it must be included somehow, a separate Pokémon pronunciation page could be made so that it's not in the trivia itself, because there is quite literally no reason to include it in a Pokémon's trivia section. Goyangi (talk) 13:04, 20 August 2026 (UTC)
- By definition, trivia is insignificant information. I think its interesting that Pokémon went out of their way to some extent to correct what they considered to be common mispronunciations, which I think justifies the inclusion. Minibug (talk) 13:15, 20 August 2026 (UTC)
- how is a Pokémon's pronunciation insignificant anyway? You usually have Wikipedia include phonetics for special words in their articles Superstarxalien (talk) 14:32, 20 August 2026 (UTC)
- Because it's not Bulbapedia's responsibility to dictate pronunciations. If it was, it does not belong on the Pokémon's page itself. A pronunciation guide article would be more in order if we must include something. Goyangi (talk) 14:37, 20 August 2026 (UTC)
- I'm not sure how the current phrasing implies we're dictating the pronunciation. Minibug (talk) 14:44, 20 August 2026 (UTC)
- Because it's not Bulbapedia's responsibility to dictate pronunciations. If it was, it does not belong on the Pokémon's page itself. A pronunciation guide article would be more in order if we must include something. Goyangi (talk) 14:37, 20 August 2026 (UTC)
- In that case, one could put in "Zekrom has elbows on its wings" in the trivia. In addition, you told me to come here. Goyangi (talk) 14:38, 20 August 2026 (UTC)
- Point taken, but I still don't know why you think this trivia is "too" insignificant. I did tell you to come here, and I'm giving my input on the proposed change. Minibug (talk) 14:59, 20 August 2026 (UTC)
- how is a Pokémon's pronunciation insignificant anyway? You usually have Wikipedia include phonetics for special words in their articles Superstarxalien (talk) 14:32, 20 August 2026 (UTC)
- I absolutely think every Pokemon page should have its pronunciation mentioned, even not as trivia but in the opening sentence at the top of the page as it is one of the most basic and crucial things people would like to look up... if there was a list of all official pronunciations at least. Let me just leave the link to this page User:SnorlaxMonster/Pronunciation we could mainspaced to solve that conflict. Rocket Grunt 15:34, 20 August 2026 (UTC)
- We can definitely mainspace that pronunciation page but I still think the trivia should stay as-is. In my opinion, the main purpose of those trivia points is to point out that TPCi considers them commonly mispronounced Pokémon, and if you're going to say that it's natural to mention what they say is the correct pronunciation. It's no different than us using official terminology to refer to things. Storm Aurora (talk) 16:26, 20 August 2026 (UTC)
- It's not crucial, it's imperious. Calling it crucial implies that people's lives depend on it. Goyangi (talk) 19:46, 20 August 2026 (UTC)
- It is not appropriate to nitpick people's word choices, as it adds nothing to the conversation and violates the spirit of the code of conduct. Please do not do this again. Minibug (talk) 19:55, 20 August 2026 (UTC)
- I do think the official English pronunciation is crucial information for a Pokémon's page. By that definition of "crucial", none of the information on this website would fall under it.
- I actually agree with Rocket Grunt that it should be in the introduction section besides the name itself, rather than pushed to Trivia as pronunciations are one of the basic pieces of information one would search up for a Pokémon. Chaogotchi (talk) 19:57, 20 August 2026 (UTC)
- It feels a little pushy to include it though, does it not? It's ultimately better go keep things as they currently are. Goyangi (talk) 20:06, 20 August 2026 (UTC)
- I don't see it as pushy? The goal of the site is to provide official and correct information. If one chooses to pronounce it differently or how they're used to pronouncing it, that's up to them. Chaogotchi (talk) 20:11, 20 August 2026 (UTC)
- The last sentence is mostly what I think as well, and as such, it does not have to be among the first things such readers see. Goyangi (talk) 20:29, 20 August 2026 (UTC)
- why does the wiki have to maintain the idea that pokemon names don't have an officially approved way to speak them, when they do Superstarxalien (talk) 20:30, 20 August 2026 (UTC)
- The last sentence is mostly what I think as well, and as such, it does not have to be among the first things such readers see. Goyangi (talk) 20:29, 20 August 2026 (UTC)
- I don't see it as pushy? The goal of the site is to provide official and correct information. If one chooses to pronounce it differently or how they're used to pronouncing it, that's up to them. Chaogotchi (talk) 20:11, 20 August 2026 (UTC)
- It feels a little pushy to include it though, does it not? It's ultimately better go keep things as they currently are. Goyangi (talk) 20:06, 20 August 2026 (UTC)
- That pronunciation page is a great idea, I hope that gets mainspaced (while keeping the trivia points for Pokémon included in official "common mispronunciations" lists). I've been meaning for a while to figure out a way to document the pronunciation info from the guidebooks, this would be good for filling that gap in our coverage. Hewer (talk) 22:15, 20 August 2026 (UTC)
When I originally added these trivia points, I deliberately worded them so that the fact the Pokémon was included in an official list of commonly mispronounced Pokémon was the focus of the trivia point (e.g. "X Pokémon was included in Y official list, where the pronunciation was given as Z"), as I think this is itself interesting information worth documenting. I also specifically chose to word it in a non-"pushy" way, by presenting it as just the pronunciation according to this particular source rather than the one true correct pronunciation. Someone else later reworded the trivia points to instead place focus on the pronunciation itself (e.g. "X Pokémon has Z pronunciation according to Y official list"), which I thought was a slight downgrade but not a big enough deal to bother changing back. I don't understand the argument that pronunciation information is too minor or uninteresting to include, it's a frequent topic of discussion among Pokémon fans (so much so that it's received official acknowledgement, which is what these trivia points are meant to be documenting). Hewer (talk) 21:56, 20 August 2026 (UTC)
Does anyone know which Pokemon pages have a "design variations" section?
I tried scraping the pages using the Python requests library but that didn't seem to work. sumwun (talk, contribs) 03:16, 10 November 2026 (UTC)