User talk:Machampionship
| Welcome to Bulbapedia, Machampionship! |
|
Thank you for joining our community! By creating an account you are now able to edit pages, join discussions, and expand the community-driven Pokémon encyclopedia. This is a brief introduction to Bulbapedia's rules and resources to help you get started:
|
|
Thank you, and have a good time editing here!
|
Raichu images
Please stop removing images from the Raichu page just because you don't think the captions are fitting. It'd be much more constructive to improve the captions instead. The images are included because they display interesting biological details not seen in the key art. Additionally, instead of repeatedly removing content, it'd be nice if you could bring it up on the talk page or discuss it with the user who added it, that way we can try to reach a common agreement. Landfish7 02:49, 19 November 2025 (UTC)
- Okay, I'll try using the talk page more often. Still, I don't see how these images add anything interesting to Mega Raichu's lore. They're just illustrations of Raichu running, and they don't depict it emitting electricity or doing anything particularly interesting.Machampionship (talk) 16:22, 19 November 2025 (UTC)
- Appreciate that. To explain, unlike their main 3D renders, the stylized key art shows what parts of their body glow, including an interesting detail in particular with Mega Raichu Y in that its fangs are shown glowing as well (its fangs aren't shown at all in the render). Moreover, the parts that are glowing are the exact parts shown to glow while they're discharging massive amount of electricity in the trailer, even if nothing is actually shown being discharged in the artwork. Hope this makes things more clear. Landfish7 17:45, 19 November 2025 (UTC)
Regarding revisions to my edits
Was just wondering what the reasoning was for reverting my changes to the articles for single stage Pokémon capable of Mega Evolution? Chaogotchi (talk) 18:45, 27 November 2025 (UTC)
- A Pokémon cannot logically be fully evolved if it is unable to evolve in the first place. For Pokémon that do not evolve, we simply say "It is not known to evolve into or from any Pokémon." For Pokémon that only evolve once, we don't use "It is the final form of [Pokémon]." for its evolved form unless it is one of multiple possible branched evolutions.Machampionship (talk) 16:11, 28 November 2025 (UTC)
- That's fair, my wording was off on single stages. I had intended to write that to emphasize that they cannot evolve further as Mega Evolution only works on Pokemon at their final stage, hence why I gave it to Pokemon that evolve once. Pokemon with no evolutions currently have better wording now. Chaogotchi (talk) 06:55, 29 November 2025 (UTC)
Peakychu / Gendered pronouns
Official marketing on social media currently refers to Peakychu with gender neutral pronouns.[1] I'm happy to wait until we get conclusive evidence from actual game screenshots/footage, but I do want to note that we generally don't assume that a Pokémon character uses gendered pronouns, as that tends to be a rare exception in the franchise, and we usually do our best to draw the language we use from official source material. Landfish7 21:08, 3 December 2025 (UTC)
Pokédex Entries
Hello,
I am interesting in know how you acquired the Pokédex entries for the new Mega Dimension forms. Is there a pastebin of the entries somewhere? A source would be appreciated. Mjmannella (talk) 15:41, 10 December 2025 (UTC)
- YouTube videos. I do not have access to the game, so I'm just finding whatever I can online to help out with the Mega Evolutions.Machampionship (talk) 15:43, 10 December 2025 (UTC)
Edit warring
Hey, I just wanted to let you know that if you have been reverted twice and disagree with the change, the thing to do is bring it to the talk page. Continuously reverting edits back and forth is considered edit warring and is a blockable offence. It's also much easier and more productive to ease disputes through the talk page. I have reverted the edit to maintain clarity and consistency with how the games refer to the base form of a Pokémon which has multiple regional forms. "Kantonian" doesn't literally mean "caught in Kanto" it means that the form originated from the region and there are many instances within the games backing up this terminology which is why we also use it on the wiki. 4iamking 23:47, 11 December 2025 (UTC)
- My reasoning was that "Kantonian Raichu can Mega Evolve" implies that a Raichu that has Mega Evolved is inherently from Kanto when it can also be from any other region besides Alola. That being said, I understand that I was wrong, and I will try to remember to use talk pages.Machampionship (talk) 01:13, 12 December 2025 (UTC)
Mega Meowstic
Hello! I just wanted to talk about the internal forms of Mega Meowstic while avoiding a potential edit war. Honestly, I do not have the information in full, since I wasn't the one to add it to the page, but if it actually is treated internally as two distinct forms (something I myself cannot confirm), then it simply is, and it probably should be added to the page. I'm saying this due to the way you justified the edit, which made me think it was something you thought was subjective. And, as I said, some other Pokémon have visually indistinct forms (such as Rockruff, for its regular Abilities and Own Tempo, or Scatterbug and Spewpa, which determines the form of Vivillon they evolve into), so it isn't something new. Shinka (talk) 03:21, 20 December 2025 (UTC)
- I'm aware that some Pokémon have "forms" that don't look any different from their regular counterparts, such as Rockruff. The issue here is that I think that it's erroneous to claim that Mega Meowstic has two "forms" for both genders simply because its base form has gender differences. A male Meowstic has different stats and moves than a female Meowstic, and they also have different appearances, so it makes sense to call them different forms. Mega Meowstic, on the other hand, is still a Mega Meowstic regardless of its gender. Unlike Tatsugiri and Magearna, who have different Mega Evolutions for each of their forms, Mega Meowstic's characteristics (stats, Pokédex entries, etc.) don't vary depending on whether its a boy or a girl. Machampionship (talk) 04:08, 20 December 2025 (UTC)
- It's probably more productive to move this conversation to Meowstic's talk page, and I'm sorry for starting it here instead of there. Shinka (talk) 20:05, 20 December 2025 (UTC)
Minor edits & previewing
Good morning. I noticed you made 8 edits on Minior's page in less than an hour, mostly small changes. Just as a recommendation, you can mark an edit as "minor", as well as previewing changes before submitting, which will help keeping the page's history more clear. :D — Lakelimbo (talk) 13:57, 4 January 2026 (UTC)
- I usually do that, but I forgot to, so I'll keep this in mind. Thanks. Machampionship (talk) 16:19, 4 January 2026 (UTC)
Tatsugiri And Magearna
Hi could you not change what was done on the pages of Magearna and Tatsugri. The reason for that was it was decided on Discord, that both pages do not need all of their forms representing on top page when it already did in biology. The reason for for just two picture in each page as that is more that enough for representation and makes top page look less cluttered up and nicer. Does this makes sense? Because I liked the changes already done on page before you undid it. Does this clarify things? Jacob9594 (talk) 18:17, 9 January 2026 (UTC)
- I still don't really see the point, but okay. Machampionship (talk) 18:39, 9 January 2026 (UTC)
- Thanks for understanding. Jacob9594 (talk) 19:08, 9 January 2026 (UTC)
- If the extra forms are functionally different and aren't otherwise interfering with the data in the infobox, I don't think we should exclude them. Landfish7 20:01, 9 January 2026 (UTC)
- i edited it before to look consistent, but considering how the main art for Mega Tatsugiri isn't even what was considered the "base" form (curly), i agree even more now Chaogotchi (talk) 22:23, 14 January 2026 (UTC)
- If the extra forms are functionally different and aren't otherwise interfering with the data in the infobox, I don't think we should exclude them. Landfish7 20:01, 9 January 2026 (UTC)
- Thanks for understanding. Jacob9594 (talk) 19:08, 9 January 2026 (UTC)
Zygarde's Core Enforcer
Hello, we've been repeatedly editing Zygarde's page because of the Core Enforcer's description. I had a talk to the others in Discord and we decided that it was better to maintain it, specially since the description of Zygarde's other signature moves are already in the page. Trainersurrel0409 (talk) 18:37, 11 January 2026 (UTC)
- I don't see the point. You cite Zygarde's ability to charge up Core Enforcer as a reason why it should be mentioned, but charging up moves is a common thing. It's not like Zygarde is doing something that was previously unseen in the entire Pokémon series. Machampionship (talk) 19:21, 11 January 2026 (UTC)
- The thing about the Core Enforcer Zygarde used against Ange is that it wasn't a beam, it's different enough to be mentioned in the Biology alongside the standard one. Trainersurrel0409 (talk) 20:38, 11 January 2026 (UTC)
Creating talk pages
Please note that when creating talk pages to include the welcome template, you can do this by posting {{subst:Welcome}} at the start, you don't need to sign it as it comes with your signature.--BigDocFan, Junior Admin Bulbapedia (talk) 19:16, 11 January 2026 (UTC)
- Oh, okay. Thanks for telling me. Machampionship (talk) 19:18, 11 January 2026 (UTC)
Edits on the type pages
I'm a bit irritated that you've been reverting my form-name-related edits on the type pages (Normal (type), Fighting (type), Flying (type)) while giving reasons in your edit summaries that are flat-out incorrect. Your claim that this is "not the proper way to write these forms' names" doesn't hold water given these are how the forms are named in the in-game Pokédex and other Bulbapedia pages, and your claim that the Pokédex uses "Gigantamax Eevee" as a form name is just outright false. You also told me that "Mewtwo Mega X" is not a form name despite the fact I never added it to the page (I added "Mega Mewtwo X"), which gives the impression you reverted my edit without actually looking at it, or at least without looking very closely.
In the hopes of avoiding edit wars, I will explain to you here that my intention with these edits is to make the type articles consistent with other articles that list Pokémon, such as the National Pokédex list and several of the regional Pokédex pages. These pages use a consistent style of listing a Pokémon's species name, followed by the form name as presented by the Pokédex in smaller text. The type pages currently don't follow this standard, which makes them annoying to read. They also often do not abide by the official names, such as referring to "Gulping Cramorant" rather than Cramorant's "Gulping Form". This is what I'm trying to fix with my edits.
I hope this doesn't come across as too hostile. You're welcome to tell me if you have any legitimate problems with my edits, just please ensure you actually look at the edit first and check that you're correct before telling me I'm wrong about something. This video is a handy reference for official names for the majority of Pokémon forms (notice Venusaur's forms, for example, are called "Mega Venusaur" and "Gigantamax"). Hewer (talk) 22:02, 12 January 2026 (UTC)
- For whatever its worth "Gigantamax Eevee" is as correct as "Mega Mewtwo X"; this terminology is directly used in for example in the move description of G-Max Cuddle. 4iamking 22:20, 12 January 2026 (UTC)
- I'm talking specifically about Pokédex form names (which Machampionship also specified in their edit summary). The Pokédex calls Mewtwo's forms "Mega Mewtwo X" and "Mega Mewtwo Y", and Eevee's form "Gigantamax" (these can be seen alongside each other in Pokémon HOME, so this isn't just a difference between games). All the Pokédex listing pages on the wiki accept the Pokédex form names, so I don't see why the type pages shouldn't follow suit. (Also, the way the type pages are currently set out where "Mega" is small and "Mewtwo X" is large looks awful in my opinion and inaccurately implies "Mewtwo X" to be the species name.) Hewer (talk) 22:55, 12 January 2026 (UTC)
- When it comes to Pokémon forms, this wiki appears to use their official names rather than their descriptors in the Pokédex; for example, it's much more common to see "Alolan Raichu" than "Raichu (Alolan Form)", as it's easier and less awkward to say. In the video you provided regarding Gigantamax Eevee, the Pokédex only uses "Gigantamax", not "Eevee Gigantamax". I thought I saw you change the names of Mega Pokémon such as Mega Mewtwo X, so I apologize for that oversight. That being said, the Pokémon section for each type page is a list of Pokémon of said type, not an indication of a Pokémon's order in a specific Pokédex, so the way they display Pokémon form names doesn't have to be exactly like the Pokédex. Machampionship (talk) 00:31, 13 January 2026 (UTC)
- You seem to still not fully understand. My edits aren't meant to suggest that "Eevee Gigantamax" is the form name, they suggest that "Eevee" is the species name and "Gigantamax" is the form name, using the convention established on other pages where the normal text is a Pokémon's species name followed by the form name in small text. The way the type pages are currently laid out has no consistency in this regard, with bits of form names randomly shoved in before or after the species name (including in cases where this is never done officially to my knowledge like "Gulping Cramorant"). Since the format of the type pages' Pokémon lists matches that of the Pokédex pages, it makes intuitive sense to me that forms would be named consistently with those pages. I also don't understand why you're using "Alolan Raichu" as an argument when the current type pages already have "Raichu Alolan Form", as they should. Hewer (talk) 08:40, 13 January 2026 (UTC)
- In this case, I don't think type pages need to display form names the exact same way the Pokédex does. The type pages are not meant to mimic the Pokédex, just show the reader a list of Pokémon belonging to said type, and as I said before, it's less awkward to say "Alolan Raichu" than "Raichu (Alolan Form)" (which I changed). Machampionship (talk) 14:55, 13 January 2026 (UTC)
- Okay, forget the consistency with other pages argument then. I would still argue that the current state of the type pages where form names are completely arbitrary, besides looking really bad, results in there being no internal consistency within the page. Your recent edits adding in unnecessary parentheses to some of the form names (even though the small text already serves the purpose of de-emphasising them) don't help in this regard, and nor does the arbitrary decision of whether to put the form name before or after the species name. A consistent formatting is helpful for conveying information clearly to the reader without unnecessarily confusing them. The Pokédex provides a consistent and non-arbitrary way of referring to Pokémon forms, but these pages in particular refuse to use it for no real reason, and I think this harms their readability (and, in several cases, their accuracy).
That's my opinion anyway. I might bring this up on one of the type talk pages for other users to comment since it's clear we aren't agreeing on this. Hewer (talk) 23:14, 13 January 2026 (UTC)- Can you define "internal consistency"? I don't see what's so confusing about seeing something like "Paldean Tauros (Combat Breed)". Also, there are certain form names where the form descriptor comes after the Pokémon's name rather than before it; for example, Zygarde's 50% Forme is officially called "Zygarde 50% Forme" and not "50% Forme Zygarde". I think the parenthesis are helpful for making the exact naming of some forms clear, such as "Landorus (Incarnate Forme)" instead of "Landorus Incarnate Forme". Machampionship (talk) 00:44, 14 January 2026 (UTC)
- By "internal consistency", I mean having a consistent guideline for the type pages on what form names to use, rather than picking arbitrarily based on vibes or selectively trusting only some official uses. Hewer (talk) 07:45, 14 January 2026 (UTC)
- I see, now I understand. That being said, I still don't think that it's absolutely necessary to follow the Pokédex naming conventions, and that most people would be more familiar with something like "Hisuian Qwilfish" instead of "Qwilfish (Hisuian form). Machampionship (talk) 16:52, 14 January 2026 (UTC)
- By "internal consistency", I mean having a consistent guideline for the type pages on what form names to use, rather than picking arbitrarily based on vibes or selectively trusting only some official uses. Hewer (talk) 07:45, 14 January 2026 (UTC)
- Can you define "internal consistency"? I don't see what's so confusing about seeing something like "Paldean Tauros (Combat Breed)". Also, there are certain form names where the form descriptor comes after the Pokémon's name rather than before it; for example, Zygarde's 50% Forme is officially called "Zygarde 50% Forme" and not "50% Forme Zygarde". I think the parenthesis are helpful for making the exact naming of some forms clear, such as "Landorus (Incarnate Forme)" instead of "Landorus Incarnate Forme". Machampionship (talk) 00:44, 14 January 2026 (UTC)
- Okay, forget the consistency with other pages argument then. I would still argue that the current state of the type pages where form names are completely arbitrary, besides looking really bad, results in there being no internal consistency within the page. Your recent edits adding in unnecessary parentheses to some of the form names (even though the small text already serves the purpose of de-emphasising them) don't help in this regard, and nor does the arbitrary decision of whether to put the form name before or after the species name. A consistent formatting is helpful for conveying information clearly to the reader without unnecessarily confusing them. The Pokédex provides a consistent and non-arbitrary way of referring to Pokémon forms, but these pages in particular refuse to use it for no real reason, and I think this harms their readability (and, in several cases, their accuracy).
- In this case, I don't think type pages need to display form names the exact same way the Pokédex does. The type pages are not meant to mimic the Pokédex, just show the reader a list of Pokémon belonging to said type, and as I said before, it's less awkward to say "Alolan Raichu" than "Raichu (Alolan Form)" (which I changed). Machampionship (talk) 14:55, 13 January 2026 (UTC)
- You seem to still not fully understand. My edits aren't meant to suggest that "Eevee Gigantamax" is the form name, they suggest that "Eevee" is the species name and "Gigantamax" is the form name, using the convention established on other pages where the normal text is a Pokémon's species name followed by the form name in small text. The way the type pages are currently laid out has no consistency in this regard, with bits of form names randomly shoved in before or after the species name (including in cases where this is never done officially to my knowledge like "Gulping Cramorant"). Since the format of the type pages' Pokémon lists matches that of the Pokédex pages, it makes intuitive sense to me that forms would be named consistently with those pages. I also don't understand why you're using "Alolan Raichu" as an argument when the current type pages already have "Raichu Alolan Form", as they should. Hewer (talk) 08:40, 13 January 2026 (UTC)
Partial Block
Look, you have been warned before that if you find yourself getting reverted, the thing to do is to bring the dispute to the talk page. Given the extensive history of edit warring on Zygarde, I have issued a partial block from editing this page for a period of 3 months. Especially after someone added a protection template to the page, the dispute really should have gone to the talk page but this did not happen. Also I should note that we are aware of past history and know that you have had an account blocked on the Bulbapedia in the past for edit warring. If this conduct continues going forward, it will happen again. 4iamking 05:40, 16 January 2026 (UTC)
Type
Hello, I would like to know why you keep changing the text in the Terastal phenomenon page from "<typename> type" to "<typename>-type", when this is not the convention held by Bulbapedia for types being used as nouns (see here on the manual of style). You had done it previously and I reverted it, citing an in-game example of this convention being used in the games, but you still keep at it. Is there anything I'm missing about this? Shinka (talk) 22:21, 29 April 2026 (UTC)
- I didn't see the example you provided, and to my understanding, normally, when a type is used to refer to a move or Pokémon, it's formatted as <typename>-type, and it's otherwise written as <typename> type when referring to the type itself. That's why I made that change. Machampionship (talk) 00:36, 30 April 2026 (UTC)
- From what I've understood from the manual of style and editing over time, you're totally right, but appear to be applying it wrongly in this case. For example, in your last edit to the Terastal phenomenon page, you changed the caption of the head image to "Juliana Terastallizing Eevee into a Normal-type", but the term should be kept without a hyphen because it's referring to the actual Normal type. If it was written as "Juliana Terastallizing Eevee into a Normal-type Pokémon", however, it would be correct. The in-game example I mentioned was "These beautiful flowers blooming above Professor Gible's head show that it has now become a Grass type." Usually, I tend to think whether the type is being used as an adjective or a noun; if it is preceded by "a/an" or "the", it's a noun and therefore should not be hyphenated, though there could be an exception I don't know about. Shinka (talk) 01:56, 30 April 2026 (UTC)
- In this case, "Normal-type" is used as a shortened form of "Normal-type Pokémon"; "Normal type" without the hyphen is only used when referring to the type itself. Are you sure that the quote you provided is fully accurate? Machampionship (talk) 02:50, 30 April 2026 (UTC)
- Yes, in this case, "Normal type" means the same as "Normal-type Pokémon", but it should still go without the hyphen, as you can see exemplified in the manual of style: "Squirtle is a Water type" (which is the shortened form of "Squirtle is a Water-type Pokémon"; they ultimately mean the same thing, but follow a slightly different convention). I pasted the quote directly from Hassel's quote page, but you can see it here directly from the games. Shinka (talk) 05:11, 30 April 2026 (UTC)
- In cases such like this, I treat the word "type" to actually mean "Pokémon" rather than type, so saying "Squirtle is a Water type" is the same as "Squirtle is a Water Pokémon", and this is why it's not hyphenated - it's basically two words rather than a single descriptor "Water-type". Kikugi (talk) 09:52, 30 April 2026 (UTC)
- Yes, in this case, "Normal type" means the same as "Normal-type Pokémon", but it should still go without the hyphen, as you can see exemplified in the manual of style: "Squirtle is a Water type" (which is the shortened form of "Squirtle is a Water-type Pokémon"; they ultimately mean the same thing, but follow a slightly different convention). I pasted the quote directly from Hassel's quote page, but you can see it here directly from the games. Shinka (talk) 05:11, 30 April 2026 (UTC)
- In this case, "Normal-type" is used as a shortened form of "Normal-type Pokémon"; "Normal type" without the hyphen is only used when referring to the type itself. Are you sure that the quote you provided is fully accurate? Machampionship (talk) 02:50, 30 April 2026 (UTC)
- From what I've understood from the manual of style and editing over time, you're totally right, but appear to be applying it wrongly in this case. For example, in your last edit to the Terastal phenomenon page, you changed the caption of the head image to "Juliana Terastallizing Eevee into a Normal-type", but the term should be kept without a hyphen because it's referring to the actual Normal type. If it was written as "Juliana Terastallizing Eevee into a Normal-type Pokémon", however, it would be correct. The in-game example I mentioned was "These beautiful flowers blooming above Professor Gible's head show that it has now become a Grass type." Usually, I tend to think whether the type is being used as an adjective or a noun; if it is preceded by "a/an" or "the", it's a noun and therefore should not be hyphenated, though there could be an exception I don't know about. Shinka (talk) 01:56, 30 April 2026 (UTC)
Zygarde
If you don't like something, edit it out, don't revert everything without a good reason. Trainersurrel0409 (talk) 22:14, 4 May 2026 (UTC)
- I make sure to provide a reason for something being unnecessary before reverting it. Machampionship (talk) 16:40, 5 May 2026 (UTC)
- Trainersurrel0409 is correct here: please do not flat revert an edit when there's only one part of that edit you're wanting to revert. Instead, you should manually make the changes to the page that you want to make. Landfish7 17:17, 5 May 2026 (UTC)
Floette
I don't know what the issue is, but you keep tacking off "an" on the Floette page for anyone attempting to make it grammatically correct, and none of your revisions have suggested a reason. Please stop creating an edit war over something so simple. TrainerSplash (talk) 17:10, 17 May 2026 (UTC)
- I just don't see a reason to keep it. Like, we don't say "a Zygarde played a major role in Pokémon Legends: Z-A" or something like that. Machampionship (talk) 18:20, 17 May 2026 (UTC)
- I would like to ask you, to in the future, either explain on your edits as to why you'd like a change, tell someone on the talk page why it's important in order to avoid conflict, and/or stop engaging in revisions. Edit wars are never an answer to this. It's really petty to keep reverting changes with no reason other than "I don't like it." And looking at your above messages, this has been a recurring problem with you on Zygarde pages.
- The An should be kept because it IS a specific Floette, it's not the whole species with that form, and the same should be said with Zygarde. "Eternal Flower Floette" isn't the name of the character, but a specific form. Since the form is part of the description, but is referring to the specific Floette, we should make it have grammatical sense. If there's any other reason than "I don't like it" I willing to hear this out. I'd rather not have a petty argument over a two letter word, and I don't think it's very fair to revert someone's edits because you don't like it. TrainerSplash (talk) 20:26, 17 May 2026 (UTC)
- I never said that I dislike it, and I wouldn't revert an edit without a reason. We don't typically use "an" when referring to a specific individual, so you won't see stuff like "Lysandre and a Zygarde" or "Lusamine and a Necrozma", which is why I removed it. Machampionship (talk) 22:50, 17 May 2026 (UTC)
- I just want to say, Eternal Flower Floette is the species, not the character which makes the "An" a grammatical requirement for that sentence. However more importantly if you find yourself in an edit war and people reach out to you on your talk page about it you should make an effort to resolve that dispute rather than continue to double down on it. This is what got your original account blocked and I reiterate what I said earlier that if this continues it can happen again. 4iamking 16:37, 18 May 2026 (UTC)
- We can and should, they are using the species name there not the formal name. "A Cosmog, nicknamed Nebby by Lillie" would be grammatically correct, as would be "Nebby, a Cosmog, plays an important role" or "Nebby plays an important role" would be. Starting a sentence with a character name on a page about the species would be rather awkward, it's important to make it clear that we are talking about that specific Floette, so an a or an an would identify that it is a *specific* Floette that is being mentioned here. I am more lenient on Zygarde because it's actually a collective, but we should still refer to it with an a if it's about a specific collective. Zygarde's page should be updated, to an include an a, and even then the following sentence after it says "A Zygarde Core" rather than the actual nickname, Squishy. You used Necrozma as your other example and this just wouldn't work here, it's a specific Necrozma in USUM, but in any case, Necrozma's page doesn't identify that a specific one is important to the games, just that the species is displayed on the box art. I can understand the confusion, because both Zygarde and Necrozma are also the species name, so it can arguably be speaking the Pokemon on a species scale or on a personal scale. Floette is not like this, otherwise every character would be calling her "Eternal Flower Floette" at any given moment, it's awkward, which is why an an would be important there. TrainerSplash (talk) 22:16, 18 May 2026 (UTC)
- I never said that I dislike it, and I wouldn't revert an edit without a reason. We don't typically use "an" when referring to a specific individual, so you won't see stuff like "Lysandre and a Zygarde" or "Lusamine and a Necrozma", which is why I removed it. Machampionship (talk) 22:50, 17 May 2026 (UTC)
