MarioWiki:Proposals/Archive/84
Determine if certain "notable" versions of characters and species without their own articles should have their specific sections linked to[edit]
Establish policy discouraging such linking 1-9-0-0
To quote myself from a year ago:
So, a user (who I will not name to avoid harassment of them) has been updating links for Pauline in the context of her younger appearance in Donkey Kong Bananza so that they link to that game's section of her article, like so:
[[Pauline#Donkey_Kong_Bananza|Pauline]]
My sentiment on doing this is...more negative than positive. While I see the rationale behind it—a prominent younger version of a character that isn't portrayed as a distinct entity is somewhat unprecedented for this franchise, and thus linking to a page where the infobox artwork depicts said character with their usual adult appearance could be considered a little weird—it also has problems of its own. There's no indication that these links would lead to just a section of Pauline's article instead of the beginning of it until they are hovered over—and said article beginning happens to include relevant information for her appearance in Bananza, such as her voice actress, Jenny Kidd.My biggest complaint with this, however, is also my hook for this discussion: Why single out Pauline? While we often link to certain sections of recurring locations in the context of specific games (though this is becoming less common as more iterations of such locations are being split off via proposals), this is the first time (to my knowledge) we're consistently doing this with a character. One would think some of the articles we chose to merge—such as some of the 1993 live-action film versions of characters and species (relevant proposal here) or the various representations of species as individual characters in the Mario Party series (relevant proposals here, here, and here)—would be ripe for this treatment. However, besides articles where we forgot to update links following a merge like John Leguizamo, the only article I could find with such a link was Koopa Krag in reference to his grandson...but Koopa Troopa is already linked there twice without a redirect in reference to Koopa Krag's species, so that probably doesn't count either.
I do recognize that we have no rule for or against linking to a specific version of a character or species when needed. Still, given the potential user-unfriendliness of doing this with Pauline, yet also considering the possibility of applying it to more versions of characters and species, I do think some action must be taken. Heck, even though I agree to merging the 1993 film characters with their main counterparts, they're probably more at odds with them than 13-year-old Pauline is with her adult self. Assuming we do establish an official policy for this kind of linking instead of nipping it in the bud, where would we put said policy? Could it be added to one of our existing policy pages, or would it take a new one? How would we determine if a version of a character or species is notable enough to have their specific section linked to? Such a policy may well encourage people to link every instance of King Boo in the Luigi's Mansion series to
King Boo#Luigi's Mansion series(or a specific game therewithin) because of his different design and crueler characterization there, or further subjects down the slippery slope.
One year later (and with some advice from LadySophie17 (talk) on Discord), I'm finally ready to discuss adding a potential policy for this! To summarize my long spiel above, there have been a few instances where a character or species is portrayed in a way that is exceptionally different from their usual depictions, yet this portrayal is not treated as distinct from their usual self in the way that, say, Baby Mario is considered a distinct subject from adult Mario. Whether or not links for such depictions of a subject are piped to the specific section involving said depiction is inconsistent across the wiki; there are pros and cons to each approach, yet we have no official policy encouraging one or the other. This proposal seeks to remedy that.
If the addition of a policy encouraging piped links to specific version of characters passes, this paragraph (or a reworded version of it) would be added to the "Linking, linking, linking!" section of MarioWiki:Manual of Style:
Occasionally, a character or species may be portrayed in a way that is notably different from their usual depictions, yet still not treated with enough distinction for their own article. Examples include Pauline as a 13-year-old girl in Donkey Kong Bananza, or Bowser as a human-like evolved dinosaur known as "President Koopa" in the 1993 film Super Mario Bros. For such instances, it is encouraged to use piped links to the specific section of the subject's article where this depiction applies (e.g.
[[Pauline#Donkey Kong Bananza|Pauline]]), or that of said subject's history article if they have one (e.g.[[History of Bowser#Super Mario Bros. (film)|President Koopa]]). This can also apply to certain depictions of species as individual characters, such as the Goomba who serves as one of the hosts in Mario Party 4.
Inversely, if we choose to discourage piped links to specific version of characters, something like this would be added instead:
Occasionally, a character or species may be portrayed in a way that is notably different from their usual depictions, yet still not treated with enough distinction for their own article. Examples include Pauline as a 13-year-old girl in Donkey Kong Bananza, or Bowser as a human-like evolved dinosaur known as "President Koopa" in the 1993 film Super Mario Bros. While it may be enticing to use piped links to the specific section of the subject's article (or separate history article) where this depiction applies to avoid possible confusion, doing so is discouraged to avoid confusing those looking for more general information on the subject instead, as well as to prevent skipping information earlier in the article that may also be relevant to the specific version of them in question. This also applies to certain depictions of species as individual characters, such as the Goomba who serves as one of the hosts in Mario Party 4.
Proposer: SolemnStormcloud (talk)
Deadline: August 22, 2026, 23:59 (UTC) Closed early on August 15, 2026, 23:59 (UTC)
Establish a policy encouraging linking to such sections[edit]
- Wandering Poplin (talk) I think I prefer this option the best. For instance, if I am currently trying to find information and images relating to Nurse Toadstool, it would be more helpful to be redirected the the relevant section of the History of Princess Peach page which covers the character (albeit somewhat poorly, but that's a separate issue for another time.) than immediately being linked to Princess Peach, wasting time fruitlessly searching the page for any info on Nurse Toadstool and not finding it, opening the History of Princess Peach article, and then having to scroll through walls and walls of text until I finally find what I'm looking for.
Establish a policy discouraging linking to such sections, and remove piped links in question[edit]
- Hewer (talk) Full vote reasoning moved to comments per request. Tldr, this style of linking is unhelpful for finding information and invites weird inconsistencies.
- LadySophie17 (talk) Per Hewer. Pauline and President Koopa seem like reasonable use cases but Goombob and Nurse Toadstool being brought up as examples convinced me this guideline will be abused from the start. As per Arend in the comments, I also disagree with the use of section linking in navboxes.
- SolemnStormcloud (talk) Per Hewer, as well as myself from a year ago. Unless we were to have dedicated proposals on who should or shouldn't receive this treatment, it'd just be a slippery slope as to who does.
- Rykitu (talk) Per all.
- Arend (talk) Per all. As I explained in the comments, I would prefer to avoid linking to specific section of an article in navbox templates (at least until we have a link template that can convert anchor links to bold text when you're on its page, which may be more trouble than it's worth), and with Hewer pointing out that certain notable versions of a character can appear in multiple games (sometimes alongside the character's normal version!), then I think even splitting that notable version in its own article would be more preferable than this. Also, as they and LadySophie pointed out, this could be further abused to a ridiculous degree.
- Ahemtoday (talk) Per Hewer.
- Wilben (talk) Per all.
- Dominoes § 2026 (talk) Per all.
- Yoshi18 (2026 appearance) (talk) Per all.
Do not create a policy, and remove piped links in question[edit]
Do not create a policy, but keep existing piped links (status quo)[edit]
Notable comments that should be linked to specifically[edit]
My main concern is whether or not navigation templates will be affected. Navboxes are usually a whole collection of links, and normally, when you check such a template on a page featured in there, that link will be made bold and unclickable to indicate you're already there, which helps quite a bit with navigating through the template. However, when you make it a link to a section instead, this does not happen: instead, it's an anchor link, which means you can still click it when you're still on said page, given that it directs you to a specific section instead of the page as a whole (even when you're already in that section). This is a bit of a pet peeve of mine given that it makes navboxes more difficult to navigate than necessary, and in the end wouldn't be all that helpful: it's kind of like putting a redirect link in a navbox template.
So if we were to make a policy in which linking to sections like this is encouraged for specific versions, I'm kinda hoping that navboxes would be exempt from this.
rend (talk) (edits) 23:24, August 8, 2026 (UTC)
- Huh. I originally imagined that the piping would apply to navboxes as well (I can imagine it would make sense to link Goombob in {{MPA}} to the Mario Party Advance section of Galoomba's article, especially since "Goomba (Super Mario World)" is also linked in the "Enemies and species" row), but this is a valid issue. Honestly, something like this seems like it would require a second proposal—lest I complicate this one any more. Do note that this issue of yours currently affects Pauline in {{DKB}}, but not Mario, Luigi, Yoshi, Bowser/President Koopa, Goombas, and Snifits in {{SMB film}}. (See what I mean by this piping currently being treated inconsistently?) —
SolemnStormcloud (talk) 23:42, August 8, 2026 (UTC)
That's because one uses an anchor link while the other uses links proper, the former perfectly showcasing the problem I'm talking about. I'm really not talking about how we're treating the linking to specific versions thing inconsistently (that much is obvious and should be handled), but rather how we should treat this in navboxes. While I think using anchor links is really useful in various cases, I personally think we should avoid using them in navboxes for the reasons I stated earlier. Again, it's like using redirects in navboxes.Do note that this issue of yours currently affects Pauline in {{DKB}}, but not Mario, Luigi, Yoshi, Bowser/President Koopa, Goombas, and Snifits in {{SMB film}}.
rend (talk) (edits) 11:43, August 9, 2026 (UTC)
- I was mainly just pointing out an instance of an anchor link currently in one of our navboxes. —
SolemnStormcloud (talk) 12:43, August 9, 2026 (UTC)
- I was mainly just pointing out an instance of an anchor link currently in one of our navboxes. —
@Wandering Poplin: I think this issue is better solved by using Ctrl+F than by implementing these sorts of links. Hewer (talk · contributions · edit count) 09:48, August 9, 2026 (UTC)
- Or simply using the table of contents...
rend (talk) (edits) 11:43, August 9, 2026 (UTC)
- Yes. But that "solution" assumes that the average casual reader would:
- Know which page the information is stored on to begin with. (The main page, the History of [subject] page, etc.)
- Knows which section of the table of contents that the information is contained in. This issue isn't the most important point, but it is a supporting problem found on pages with literal dozens of listings.
- Actually knows about the "Ctrl+F" feature, and what it does. (I didn't until you brought it up, just now. And I doubt the average casual viewer knows about it either.)
- Is actively using a device which even has the aforementioned "Ctrl+F" feature. Not all devices do.
- This issue also gets worse if you account for [subject-the-character], alter-ego appearances, and other such subjects which do not have their own pages, or even their own redirects. (Which is something I wish I'd brought up when casting my vote.)
- I do acknowledge the concerns brought up by the opposition, but I feel that abolishing these links outright isn't the most favorable solution, as it does not provide a (suitable) alternative for the navigation issues which these links had otherwise resolved. I am not saying this system should be used everywhere, and for everything, but it does have some use cases which should not be ignored. Wandering Poplin (talk) 16:50, August 10, 2026 (UTC)
- I had also assumed that the fact that a guideline for "what subject qualifies for being specifically linked to" and would need to be created ... was kind of a given.
- The reason I never brought it up during my vote is because I'd assumed it was something we were already planning to do if this proposal succeeded. Perhaps I was mistaken. Wandering Poplin (talk) 16:50, August 10, 2026 (UTC)
- The issue is that creating such a guideline would be more trouble than it's worth due to all the arbitrary judgement calls it would require about what is and isn't a "notable version". It's not something that can be easily defined, and I can't imagine there being a consistent set of criteria that would determine whether or not something "counts".
Regarding your other comment: if the reader actually knows what information they're looking for when they click on a link (which I think is a reasonable assumption) then they should probably be able to find it with a little scrolling. In the Nurse Toadstool example, I assume a reader who knows what Nurse Toadstool is would know that she's from the Dr. Mario series, so they could go to Peach's history page and click the section for the Dr. Mario series. Or alternatively, if they were really trying to find Nurse Toadstool coverage, they could just type "Nurse Toadstool" into the search bar. I don't think it's the job of regular links to do this kind of basic navigation for the reader, especially since, as I've already pointed out, linking to history sub-sections like this will usually still miss out other relevant information that the reader could've been looking for, due to the way character articles are organised. (I will note that I'm actually not a huge fan of the history page splits myself because of the hindrance to navigation, but I don't think this is the solution to that issue.) Hewer (talk · contributions · edit count) 17:58, August 10, 2026 (UTC)
- The issue is that creating such a guideline would be more trouble than it's worth due to all the arbitrary judgement calls it would require about what is and isn't a "notable version". It's not something that can be easily defined, and I can't imagine there being a consistent set of criteria that would determine whether or not something "counts".
- Yes. But that "solution" assumes that the average casual reader would:
@Hewer Could please truncate your vote and leave your entire comment here? It is a bit too lengthy for a vote section. — Lady Sophie_17
(T|C) 11:52, August 9, 2026 (UTC)
- Didn't know there was a length limit for votes now, but sure I guess. Here's my full vote reasoning:
- I don't like this style of linking because I find it strange and unhelpful to link to a specific part of a character's history section rather than linking to the character normally, as the way that character articles are structured means not all information specific to that appearance will necessarily be confined to that section on the article (such as the proposal's example of Bananza-specific information being covered in the intro to Pauline's article, and other cases like profile and statistics sections). It's especially annoying for characters like Bowser whose history sections are now split into separate articles, meaning the link doesn't even take you to the article about the character. Another problem with linking things in this way is that it arbitrarily implies some appearances of the character to be more "distinct" than others, despite the fact they're all appearances of the same subject, otherwise they wouldn't be covered on the same article. What actually determines whether any given appearance is a "notable version" or not? There's really no more reason to always link Pauline's appearance in Bananza to that game's section than there is to always link her appearance in, say, Mario Tennis Aces to that game's section, or to distinguish her appearance in the original Donkey Kong (after all, her name and design were different in that game). I also don't like the mention in the proposed policy addition that "This can also apply to certain depictions of species as individual characters", because those concepts really aren't as distinct as the wiki often makes them out to be. Would that apply to, say, Koopa Troopa's appearance in Super Mario Kart? Better to cut out the ambiguity and just link to things normally. EDIT: Oh yeah, another issue is that sometimes the same "notable version" will make multiple appearances, meaning linking to a single appearance in a history section doesn't even encompass all the appearances of that version of the subject. For example, links to Dr. Bowser originally led to Bowser's Dr. Mario World section, which was later complicated by Dr. Bowser showing up again in Mario Kart Tour. What do you do in that situation? Hewer (talk · contributions · edit count) 15:13, August 9, 2026 (UTC)
- There is no strict length limit for votes (yet), but making several paragraph-length arguments opposing a proposal can be disruptive to the voting section, and might not provide a decent space for debates and clarifications. Typing the reasoning in the comments section also allows voters to use paragraph breaks, which make for better legibility. — Lady Sophie_17
(T|C) 16:13, August 9, 2026 (UTC)
- There is no strict length limit for votes (yet), but making several paragraph-length arguments opposing a proposal can be disruptive to the voting section, and might not provide a decent space for debates and clarifications. Typing the reasoning in the comments section also allows voters to use paragraph breaks, which make for better legibility. — Lady Sophie_17
I'm just now realizing: If the policy to discourage this usage of piped links passes, how would we treat the one on Koopa Krag's article in reference to his grandson? Since Koopa Troopa is already linked in the context of Krag's species, should we remove the link outright; have a redundant, second link to Koopa Troopa; or even keep the piped link anyways? —
SolemnStormcloud (talk) 18:26, August 9, 2026 (UTC)
- Just unlink it, I suppose. That's how it was initially presented anyway, after all, until a link was added six years ago when it turns out MPDS Koopa was split into its own article years prior... until 2022 that is, when it merged back to Koopa Troopa.
rend (talk) (edits) 15:26, August 10, 2026 (UTC)
Remove composer credits that are not officially known for music from Super Mario 3D World[edit]
do not remove 1-8
The wiki currently credits the composers for each music from Super Mario 3D World, and claims that it is from Super Mario 3D World Original Soundtrack. However, the actual album doesn't actually credit any composers, so the composers are technically still unknown. So far, the info for who the composers are are actually entirely based on internal file names. You can see how they obtained them here: https://nintendo.fandom.com/wiki/Super_Mario_3D_World_%2B_Bowser%27s_Fury/soundtrack - these are obtained through internal file names, not any official confirmation, so they are still technically unconfirmed, so we can't technically put them here yet.
So far, we use the VGMdb pages (here and here) for their information, but they likely obtain them from the file names.
An analogy is how the Nintendo Wiki (https://nintendo.fandom.com/wiki/New_Super_Mario_Bros./soundtrack) claims that the composers for New Super Mario Bros. are known based on internal file names (like "does not use samples", "mentioned by Koji Kondo", etc.), but we don't use them for this. (e.g. our Underwater Theme page still says the composer is unknown, even though the Nintendo Wiki says that the composer is Asuka Hayazaki, based on the sole fact "does not use SWAR “WAVE_WAKAI_SHARE” samples; when discussing the "Ground Theme" composition, Koji Kondo mentions that "the other songs were made by other staff members"").
Proposer: GamermanX2354 (talk)
Deadline: August 23, 2026, 23:59 (UTC)
Remove the composer credits for those that are unknown[edit]
- GamermanX2354 (talk) Per proposal.
Keep the composer credits[edit]
- Hewer (talk) If we know the composers, we should document that. Doesn't matter what the source of that information is (as long as it's reliable, which the filenames appear to be). It's true that we should stop citing the soundtrack release for this information if that's not actually where it's from, but let's not throw the baby out with the bathwater.
- Ahemtoday (talk) Per Hewer.
- Wilben (talk) Per Hewer.
- The Dab Master (talk) Per Hewer.
- Yoshi18 (talk) Per Hewer.
- maybe Iand255 (talk) Per Hewer, and The Dab Master's comment.
- Wandering Poplin (talk) Per Hewer.
- PaperSplash (talk) Per all.
Comments[edit]
Super Mario 3D World, Captain Toad: Treasure Tracker, and Super Mario Odyssey all contain composer initials in track file names. The credits given in the Super Mario Odyssey Original Soundtrack match up with that game's track file names, so why not treat the other file names as reliable sources of composer credits? B700465189a9 (talk) 15:09, August 9, 2026 (UTC)
- Mario Kart Wii and New Super Mario Bros. Wii as well, apparently. PaperSplash (talk) 23:34, August 19, 2026 (UTC)
We should definitely start incorporating internal name sections in theme articles to use as citations for composer credits. The references could simply say "See § Internal names."
The Dab Master 17:09, August 9, 2026 (UTC)
@Hewer @Ahemtoday @Wilben @The Dab Master @Yoshi18 @Iand255 @Wandering Poplin @PaperSplash @B700465189a9 so since you guys do agree to treat internal file names as a reliable source, does that mean that we have to add composer credits to the individual music pages for Super Mario 3D World, Captain Toad: Treasure Tracker, Mario Kart Wii, and New Super Mario Bros. Wii?
(But for Mario Kart Wii, I don't really know how the file naming system works, since the prefixes are n_, o_, and r_, and there are only two known composers for Mario Kart Wii.)
Additionally, how about for New Super Mario Bros. (with the claims made in https://nintendo.fandom.com/wiki/New_Super_Mario_Bros./soundtrack)? GamermanX2354 (talk) 08:22, August 20, 2026 (UTC)
- In the case of Mario Kart Wii, as far as I can tell; the prefixes have to do with what the track is used for. "n_" stands for "New" as in "New Circuit" for "Luigi Circuit" and "New Farm" for "Moo Moo Meadows". "r_" means "Retro" as in "Retro 64 Circuit" for "N64 Mario Raceway" and "Retro DS Desert" for "DS Desert Hills" (both of which I had to dig into the game files myself to figure out because I couldn't find any internal names for MKWii's Retro Courses on the wiki). And "o_" seems to stand for something like "Options" or "Other" or something, because all of the files attached to it seem to be menu music and fanfares. And since all of the suffixes have to do with when/where it plays, so I have a feeling that Mario Kart Wii having composer signatures in the file names is a misunderstanding. But the fact that Super Mario Odyssey does have them and it matches with the credits in the original soundtrack tells me that it's probably not the only one, and internal names are a valid method so long as we make sure to compare the prefixes/suffixes to the list of staff to make sure that it all matches up, which would mitigate misunderstandings such as Mario Kart Wii.
IanD255 (talk | contribs) 09:05, August 20, 2026 (UTC)
Delete a handful of unnecessary horizontal infoboxes[edit]
Now, I suppose it may seem a bit strange to tackle a bunch of infobox templates at the same time, but I do believe these have a good amount of things in common: all of these (with the exception of one) have been created by disgraced user Super Mario RPG (talk) (who had also proposed other highly unnecessary templates, which either failed spectacularly, or succeeded only to be reverted later); all of them use the same horizontal infobox template style used on {{SMG boss}} created by Doc von Schmeltwick (talk) (admittedly not a bad design per se, as seen with the Smash Bros-related infoboxes such as {{SSB4 trophy}} and {{Spirit}}), and, most importantly, these tend to either convey non-profile statistics that can easily be conveyed in the History section (or don't seem all too necessary to be conveyed at all), or seems to convey profile information and stats that can be easily conveyed without the need for an infobox template like that, often having a (unnecessarily large) space for an (often tiny) image as an excuse for its existence.
Here's the templates being covered for this proposal, alongside my reasons for why I think they're unnecessary:
- {{SPP enemy}} - As can be seen in videos such as this one, the only information the Glossary provides beyond the enemy's image, is a short description, and the number of the entry out of 89 entries, yet this infobox also has parameters for the Vibe (something that the article itself already clarifies), and the levels it appears in (which could be conveyed in the History section). The template also seems to display specific Vibe icons depending on which Vibe the enemy has, so the excuse to use more images may have been a factor here as well. Moreover, not every enemy seems to use this template at all either.
- {{DKC GBA enemy}} - The GBA versions for the DKC games have no official in-game profiles (not even in its two Scrapbooks), so mostly this is just an excuse to convey the levels and worlds an enemy appears in, in a fancy template instead of the History section. I say "mostly", because the infobox also provides information about the page of the scrapbook the enemy appears on, and how to unlock said photo, as well as the points the enemy provides in DK Attack, which I'm sure can be conveyed without the need of this template (maybe in a template w/ the actual scrapbook photo would be nice). Neither of these appear in DKC3... and so, this template hasn't been used on any DKC3 enemy, either
- {{DK boss}} - This uh, seems even less necessary to me than the previous one. It display the world and level it appears in (always just the one they appear in), the amount of hits it takes to defeat it, and the... reward after defeating it (this is often just a big Banana or just the next world, or Completion if it's a final boss). This is quite clearly the most like {{SMG boss}} in the way that it has an unnecessary reward parameter, and a somewhat strange replacement for the mission parameter (of which there is no equivalent of in DKC), and it shows how this template just doesn't work for these type of bosses. Moreover, it's only been used for DKC1 and Tropical Freeze bosses
- {{WL4 enemy}} - Again seems to only be listing the worlds and levels it appears in, the difficulty in which it appears in, and the money you get from defeating it. As Spear-Mask shows (the one enemy I'm aware of which appearance rate is affected by the difficulty setting), you don't need to convey this information in that infobox. It's not used for every enemy in WL4, and those that do use this infobox appear in every difficulty in the game, proving how useless that particular parameter really is
- {{WL4 item}} - By far the most baffling one to me. It provides the amount of damage a particular item deals against a boss. Why can't this be conveyed in a simple list?!
- {{Constellation}} - The one template not by Super Mario RPG (instead, it's by GuntherBayBeee (talk), who has had his fair share of proposals for unnecessary templates too). The only relevant parameters for this Mario Party 9 template are the constellation name, image of the constellation itself, and the shorty description. Given that we don't have infobox templates for other Mario Party profile things (as seen with List of Goomba profiles and statistics#Mario Party series), this couldn't have been a simple table as well... why?
Delete SPP enemy template?[edit]
Delete Super Princess Peach enemy template 8-0
Deadline: September 5, 2026, 23:59 (UTC) Closed early on August 29, 2026, 23:59 (UTC)
- Delete
- Arend (talk) Per proposal.
- LadySophie17 (talk) Per proposal. Some of those would be analogous to having templates for Super Mario Bros. enemies. All this info about level appearances are never conveyed on tables and descriptions already have their own sections.
- Illuminoid (talk) Per all.
- Calm Wandering Poplin (talk) Per all.
- Camwoodstock (talk) The only thing this actually adds is a list of levels these enemies are present in, which could easily be listed as a bullet-pointed list on the enemy's page, or its History section for Super Princess Peach. Glossary numbers and entries could be specified in the form of simply... Listing it as a single bullet in a section dedicated to glossary entries. You won't believe what some of these pages did before this template.
- Wilben (talk) Per all.
- BMfan08 (talk) Per all.
- Yoshi18 (talk) Per all.
- Keep
Delete DKC GBA enemy template?[edit]
Delete Donkey Kong Country (Game Boy Advance) enemy template 8-0
Deadline: September 5, 2026, 23:59 (UTC) Closed early on August 29, 2026, 23:59 (UTC)
- Delete
- Arend (talk) Per proposal.
- LadySophie17 (talk) Per proposal and my first vote.
- Illuminoid (talk) Per all.
- Wandering Poplin (GBA) How was this even made in the first place. If it was for both the SNES and GBA combined, I would almost understand. But solely the Game Boy Advance specifically??
- Camwoodstock (talk) We think this only exists to specify the Scrapbook page, the unlock condition for them, and the score values in DK Attack... All of which could be specified in prose in like, two sentences.
- Wilben (talk) Per all.
- BMfan08 (talk) Per all.
- Yoshi18 (talk) Per all.
- Keep
Delete DK boss template?[edit]
Delete Donkey Kong boss template 8-0
Deadline: September 5, 2026, 23:59 (UTC) Closed early on August 29, 2026, 23:59 (UTC)
- Delete
- Arend (talk) Per proposal.
- LadySophie17 (talk) Per proposal and my first vote.
- Illuminoid (talk) Per all. This template's page has rather odd and mobile-unfriendly formatting.
- Wandering Poplin (boss) Per all.
- Camwoodstock (talk) ...this literally isn't even listing anything that can't just be explained in text?????
- Wilben (talk) Per all.
- BMfan08 (talk) Per all.
- Yoshi18 (talk) Per all.
- Keep
Delete WL4 enemy template?[edit]
Delete Wario Land 4 enemy template 8-0
Deadline: September 5, 2026, 23:59 (UTC) Closed early on August 29, 2026, 23:59 (UTC)
- Delete
- Arend (talk) Per proposal.
- LadySophie17 (talk) Per proposal and my first vote.
- Illuminoid (talk) Per all.
- WA-ndering Poplin (talk) Per all.
- Camwoodstock (talk) This one, we will admit, does have the best argument for keeping it, just because displaying all the levels an enemy appears in is kind of weird otherwise, thanks to the 3 difficulty levels changing enemy locations. Even still... Just make it a bullet pointed list.
- Wilben (talk) Per all.
- BMfan08 (talk) Per all.
- Yoshi18 (talk) Per all.
- Keep
Delete WL4 item template?[edit]
Delete Wario Land 4 item template 8-0
Deadline: September 5, 2026, 23:59 (UTC) Closed early on August 29, 2026, 23:59 (UTC)
- Delete
- Arend (talk) Per proposal.
- LadySophie17 (talk) Per proposal and my first vote.
- Illuminoid (talk) Per all.
- Wandering Collecter (talk) Another useless template. Per all.
- Camwoodstock (talk) You could genuinely write a regex equation to convert all of this information into a bullet-pointed list to display this exact same information, trivially... In fact, look at the comments.
- Wilben (talk) Per all.
- BMfan08 (talk) Per all.
- Yoshi18 (talk) Per all.
- Keep
Delete Constellation template?[edit]
Delete Constellation template 8-0
Deadline: September 5, 2026, 23:59 (UTC) Closed early on August 29, 2026, 23:59 (UTC)
- Delete
- Arend (talk) Per proposal.
- LadySophie17 (talk) Per proposal and my first vote. This one is particularly egregious.
- Illuminoid (talk) Per all.
- Wandering Stargazer (talk) Completely, utterly, and absolutely unnecessary. Per all.
- Camwoodstock (talk) This one speaks to what we feel like is the ultimate problem with each of these templates, in that they're trying to "profiles and statistics"-ify random descriptions or elements that really don't... Need to be wedged into the profiles and statistics sections or pages? And being way too complicated about it, in some misguided attempt to be "professional" or something, when the end-result is just more annoying to work with or read. This one could be a single bullet-pointed description and the images could go on List of constellations in Mario Party 9, which is already an actual table.
- Wilben (talk) Per all.
- BMfan08 (talk) Per all.
- Yoshi18 (talk) Per all.
- Keep
Comments (Horizontal temps)[edit]
This is a bit of a hack, but the regex to replace the information in {{WL4 item}} with a bullet-pointed list would just be to replace {{WL4 item\|spoiled_rotten=(.*?)\|cractus=(.*?)\|cuckoo_condor=(.*?)\|aerodent=(.*?)\|catbat=(.*?)\|golden_diva=(.*?)}} with *[[Spoiled Rotten]]: $1\n*[[Cractus]]: $2\n*[[Cuckoo Condor]]: $3\n*[[Aerodent]]: $4\n*[[Catbat]]: $5\n*[[Golden Diva]]: $6.
~Camwoodstock ( talk ☯ contribs )
17:22, August 24, 2026 (UTC)
- I uh, don't know how to use regex here, but I imagine it wouldn't be incredibly difficult for those that can implement it, either.
rend (talk) (edits) 18:07, August 24, 2026 (UTC)
Merge multiplayer variants of New Super Mario Bros. minigames[edit]
Merge all minigames that are multiplayer versions 9-0
Vs. Lakitu Launch, Jumping Brothers, Vs. Pair-a-Gone, Vs. Mario's Slides, Bob-omb Sudden Death and Vs. Trampoline Time are essentially multiplayer versions of Lakitu Launch, Bounce and Trounce, Pair-a-Gone, Mario's Slides, Sort or 'Splode and Trampoline Time respectively. Danger, Bob-omb! Danger! is named Run, Bob-omb, Run! in multiplayer, so I don’t see why these minigames shouldn’t be merged.
Proposer: Remembered Old Buddy (talk)
Deadline: September 5, 2026, 23:59 (UTC) Closed early on August 29, 2026, 23:59 (UTC)
Merge all minigames[edit]
- Remembered Old Buddy (talk) Per proposal.
- Camwoodstock (talk) Per proposal, as well as the original TPP this was based on. These all feel like fairly standard merges.
- Bretts (talk) Per proposal.
- The OTHER R.O.B. (talk) Per my comments on the original proposal.
- Wilben (talk) I don't see why not.
- VS. Iand255 (talk) Per all and my comments on the original TPP.
- Drago (talk) These are all the same as the single-player versions, with some small changes to accommodate multiple players.
- Vs. Yoshi18 (talk) Per my comments on the original TPP.
- The Wandering Poplins (talk) Per all. It seems like these are less "slightly differents variants of the minigame" and more "alternate mode of the minigame which is played under different circumstances.
Don’t merge the minigames[edit]
Comments[edit]
Why is this a poll proposal?
The Dab Master 13:32, August 22, 2026 (UTC)
- And also, which minigames fall under "some minigames, but not all"?
rend (talk) (edits) 14:48, August 22, 2026 (UTC)
- Was going to make it all or nothing but was thinking some users would find an argument for why some minigames should be merged but not others so included a “some minigames” option thinking people would make a “why isn’t there an option to merge some minigames but not others” comment.
Remembered Old Buddy
15:45, August 22, 2026 (UTC)
- ...That still doesn't answer my question which minigames would have to be merged. You can't just put it there as an option without clarifying which minigames would be affected: especially if everyone has different ideas which minigames have to merge with their singleplayer counterpart. Imagine if that option won out, but all the votes in there wanted different minigames to be kept split (e.g. one might want to have all but Vs. Lakitu Launch be merged, another might want only Lakitu Launch be merged, a third might even want Run, Bob-omb, Run be split off fsr, etc).
If you really wanted to be thorough about this, you might as well make it a poll proposal, but w/ each subtopic representing the affected minigames (e.g. one topic being "Vs. Lakitu Launch", another being "Jumping Brothers", etc). That way, you can have a clear view who wants which minigames to be merged or kept split without anything being slowed down.
To put it simply: please avoid vague proposal options; all your options must be clear in what they affect. If you have an option that sounds vague, you have to clarify exactly what would be affected. Otherwise, you might as well not include it at all.
rend (talk) (edits) 17:05, August 22, 2026 (UTC)
- ...That still doesn't answer my question which minigames would have to be merged. You can't just put it there as an option without clarifying which minigames would be affected: especially if everyone has different ideas which minigames have to merge with their singleplayer counterpart. Imagine if that option won out, but all the votes in there wanted different minigames to be kept split (e.g. one might want to have all but Vs. Lakitu Launch be merged, another might want only Lakitu Launch be merged, a third might even want Run, Bob-omb, Run be split off fsr, etc).
- Was going to make it all or nothing but was thinking some users would find an argument for why some minigames should be merged but not others so included a “some minigames” option thinking people would make a “why isn’t there an option to merge some minigames but not others” comment.
- How do I close proposal early?
Remembered Old Buddy
15:18, August 29, 2026 (UTC)
- @Remembered Old Buddy The same way you would close a regular proposal, by removing it from here, archiving it in the proposal archive (in this case, MarioWiki:Proposals/Archive/84), and adding the proposal to the unimplemented proposal list if necessary. --Illuminoid (talk) 15:35, August 29, 2026 (UTC)
- Also don't forget to strikethrough the text stating the original end date (if it wouldn't have been closed early) and replace it with the early close end date. If you want, I can do it for you (though it depends if you're online when it closes, cause if not, then someone else will do it anyway).
Yoshi18 (talk | contribs) 15:53, August 29, 2026 (UTC)
- Also don't forget to strikethrough the text stating the original end date (if it wouldn't have been closed early) and replace it with the early close end date. If you want, I can do it for you (though it depends if you're online when it closes, cause if not, then someone else will do it anyway).
- @Remembered Old Buddy The same way you would close a regular proposal, by removing it from here, archiving it in the proposal archive (in this case, MarioWiki:Proposals/Archive/84), and adding the proposal to the unimplemented proposal list if necessary. --Illuminoid (talk) 15:35, August 29, 2026 (UTC)
Representative galleries on category pages[edit]
do not add representative galleries 1-9
[I think that category pages can look rather dry, making them unattractive as references to the average user and it's rather hard to know what can be considered the most representative or important subjects - a recommended list of subjects in the category to look at first. That's why I am proposing that category pages can have a gallery of three to five representative images of important subjects and links to those pages at the bottom.
It should have the format of a representative image of the subject, then a hyperlink to the article in question.
If the category has a "base page" (i.e. Shy Guy for Category:Shy Guys), it should be considered the first important subject. The rest are up to user discretion; good rules of thumb on considering what would be important subjects are breadth (i.e. there are many Snifits, including an entire subcategory, so they would be a good important variety for Shy Guys) and game presence (i.e. Snifits are in many games, so they can be considered an important variety of Shy Guy).
A "representative image" of a subject is ideally the same as the article image, but it can be changed for specific emphasis as to how it pertains to the category, such as a page that falls into multiple categories (such as Cosmic Clone being both a Mario Lookalike and a Luigi Lookalike, so if Cosmic Clones are chosen as an important subject for Category:Luigi Lookalikes, an image of the Luigi Cosmic Clone can be used instead of the page's image that depicts a Mario Cosmic Clone.)
In the case that the representative itself has its own subcategory, perhaps it can be linked to instead of the article proper (i.e. Category:Snifits instead of just Snifit).
See above for an example of how the Shy Guy and four of its important derivatives are shown using an image and linked to at the beginning of Category:Shy Guys.]
EDIT: I do agree that choosing important subjects and representative images is somewhat subjective. However, this ambiguity is already tolerated for aesthetic effect in various galleries in the wiki, such as the example images for each page of Gallery:Mario and the example galleries, such as the one at the bottom of Goomba. The true ideal might be to show a random selection, but I think the editor base can generally be trusted to come up with five "good enough" images that are not divisive enough to cause edit wars.
Proposer: P-Tux7 (talk)
Deadline: September 9, 2026, 23:59 (UTC) Closed early on September 2, 2026, 23:59 (UTC)
Agree: Yes[edit]
Disagree: No[edit]
- Wandering Poplin (talk) While the category pages do have some issues, I do not think that this is the way to solve them. Firstly, the category pages are solely meant for navigation, not to look "attractive", so the gallery is wholly unnecessary. There is also question of how you would even define the concept of "most important subject" for certain galleries. It is so subjective that it is practically begging to cause some kind of trouble eventually, and leaving it solely up to "user discretion" is not an acceptable answer in this case. I do think there should a a better way of clarifying certain... unusual inclusions on those pages (Strange things such as Princess Daisy being a "form", Mario's Cap being a "power-up", Bowser being a "marital artist", etc... all of which make no sense without context.) but that is a separate issue for another time.
- Wilben (talk) Per Wandering Poplin. I don't really see a point in this.
- Ahemtoday (talk) Per Wandering Poplin.
- EvieMaybe (talk) this seems like an unnecessary amount of effort for how little benefit it would bring.
- Camwoodstock (talk) While we do like the idea on paper, there'd have to be some actual method to curating what the most important subjects are, which this sorely lacks. It kinda chafes against the same thing that's holding back the idea of bringing back Featured Images, in that this would require a lot more premeditation and planning than this proposal really provides. And, no, cramming
<option>into a gallery (if that even works?) isn't a decent substitute for that in our mind. - Hewer (talk) The point of a category is navigation and adding these images would distract from that, unlike a gallery section where the point is to show images. The reason we have "representative galleries" like this in those sections is because they're a shortened version of the full gallery page being linked to, so the reader has some examples of what they're getting into before clicking the gallery link and we avoid having page sections that are just a single link, per this policy. The application of them here doesn't really fulfil a purpose like that, and I don't foresee it being much fun trying to decide which entries in a category are the "important subjects".
- Iand255 (talk) Per all.
- Illuminoid (talk) This is completely unnecessary. Per all.
- Yoshi18 (talk) Per all.
Comments (category galleries)[edit]
Also, for the record, Cosmic Clone isn't a Luigi lookalike. In both games they appear in, they always resemble Mario, regardless of which brother you are currently playing as. The reason it remained in the category for so long is because of a false claim on the article which went unchanged for years before a recent 'Shroom Spotlight fixed it up. Wandering Poplin (talk) 00:40, August 27, 2026 (UTC)
Create subject-based subcategories for the Gallery and Multimedia categories[edit]
Create subcategories 8-0
For clarity's sake! This has no relation to the presently-ongoing "Representative galleries on category pages" category proposal. It did give us the idea for this proposal during a Discord conversation that happened regarding it, but in the event either both pass, or this passes and that one doesn't, neither of these things should interfere with one another. Just want to make this clear immediately, since we imagine people might get confused seeing two proposals involving the words "Gallery" and "Categories".
No, what this is about are the literal categories for Gallery and Multimedia pages, the aptly named Category:Galleries and Category:Multimedia. These are two super-categories which pertain to every single Gallery and Multimedia page, and contain 790 and 165 pages at time of writing... They are also entirely unorganized beyond this single category, making navigating these rather difficult. While categories aren't exactly the end-all-be-all of our wiki's organization, they're not unimportant, either. Especially for a pair of categories whose only real categories above them are the Main one, for all fictional elements, making it pretty likely someone might actually find these categories while using the system as intended, the lack of any further attempt at organization here really sticks out like a sore thumb.
What we want is relatively straightforward. Just make a few sub-categories, based on subject, and to sort these pages accordingly to them. If one gallery/multimedia page doesn't fit a category that has its own sub-category, then it just stays in the root Galleries category or Multimedia category, since that's how we usually handle things. In particular, we plan to create each of the following:
- Game (galleries/multimedia)
- Character (galleries/multimedia)
- Ally (galleries)
- Enemy (galleries)
- Location (galleries)
- Object (galleries)
- Item (galleries)
Note that some of these don't have Multimedia listed as an option yet, for one key reason; there's just not enough examples of locations/items with Multimedia pages to warrant a category for them yet, and the Character one is only just scraping by as-is, hence no sub-sub-categories for allies/enemies. It should go without saying, but in case it needs to be said, in the event that we end up with enough multimedia pages for each of these subjects, those could be made without an proposal (provided this one passes, of course).
Proposer: Camwoodstock (talk)
Deadline: September 10, 2026, 23:59 (UTC)
Create subcategories[edit]
- Camwoodstock (talk) Per ourselves, of course. Normally we wouldn't even think to propose this, but considering this would impact roughly 950 gallery and multimedia pages, no matter how minor the changes actually are, we figure it's better to ask than to not. ;P
- Illuminoid (talk) It is good to clean up categories. If someone does want to view an unsorted list of galleries or multimedia pages, they can simply visit Special:AllPages or Special:PrefixIndex.
- P-Tux7 (talk) I agree. I think it would be best to hew to the categories (Characters, Species, Objects, Locations, etc.) seen in Template:Galleries. If this is judged lacking, perhaps the template itself can be edited. All I care about is that it provides a consistent experience for the user.
- Iand255 (talk) Per all. This seems no different realistically than the way a category like Category:Music is sorted.
- Yoshi18 (talk) Per all.
- Brett (talk) Per all. These categories contain way too much pages.
- Spencer PK (talk) Per all. This would really help the usability of this part of the wiki.
- The Dab Master (talk) Per all.
Don't create subcategories (status quo)[edit]
Comments (when will they let us itemize these pages, anyways?)[edit]
Merging Fiery Block, Bonfire Block, and Flame Block[edit]
Only merge Fiery Block and Bonfire Block 3-7-0
This is mostly following up on an old talk page conversation for the Fiery block, but seeing as we're proposing a change that'll impact a whole third page, we reckon it should be a mainspace proposal.
The Fiery Block and Bonfire Block are mostly split for two reasons: their names, and the mechanical difference... of how fire abilities work in Wario games, versus the Fire Flower's. Both of these are similar in terms of their own mechanics, being destroyed by using the corresponding game's Fire power, but because of the difference between Fire Mario and Flaming Wario, as well as the ever so slightly different names (the Bonfire Block being occasionally called the "Flame Block" and "Fire Block", but never the "Fiery Block"), they remain split.
...Except, uh, is that really that much of a mechanical difference? Even if the actual usage in levels varies, and the context of the surrounding game is different, the fundamentals are still identical. These are blocks destroyed by fire abilities. That is their sole function. And while a power-up is different from one of Wario's reactions... In comes Virtual Boy Wario Land, which has blocks that function identically, are visually similar, and are in a game that doesn't have Wario's reactions. You need a Dragon Crystal, turning Wario into either Sea Dragon Wario or King Dragon Wario, to destroy the blocks. This is a very standard power-up ability! And to boot, these blocks are visually similar to the Bonfire Blocks of Wario Land 4. The arguments for splitting the two apart don't really apply to Virtual Boy Wario Land, and since it's the first appearance of the subject... You can see where this is going, right?
Lastly, there's the Flame block from Wario Land 3. It's a block that is destroyed by Hot Wario, and if you hover over the link in question, you can probably see why we've opted to include it in this proposal, even if it wasn't originally in the conversation. In short, if we're going to merge Bonfire Block to Fiery Block, there's no reason to keep Flame Block split off from it just because Flaming Wario was called "Hot Wario" in Wario Land 3.
UPDATE: We've created a rough draft for the tri-merged page for those curious. It's still a work-in-progress, of course, but this is what you can roughly expect the resulting page to look like.
UPDATE 2: As Doc Von pointed out in the comments, Flame Blocks do technically have one thing going for them; you destroy them by igniting all of the Torches in the room, not just the blocks themselves. While we're not too hot (hah) on it, we will acknowledge this is at least a bespoke mechanical difference beyond "the way the game's fire power is formatted", and have provided an option to keep it split off. It's worth noting that, should that option pass, we will probably still mention the Flame Block in the resulting merged page, albeit in a much different context since explaining its mechanics and where it appears would naturally be reserved for its own page; the mention would be more along the lines of the Snowman Block mention currently on the draft.
Proposer: Camwoodstock (talk)
Deadline: September 14, 2026, 23:59 (UTC)
Merge all (flames burn brighter together!)[edit]
- Camwoodstock (talk) Secondary option. We do think this is still ultimately defensible, but we can see the merit in keeping the Flame Block split after having its mechanics illuminated. Like some kinda torch.
- Yoshi Block (talk) Secondary choice. Per proposal.
- Iand255 (talk) Per proposal.
#Mr. Sorbetti (talk) Per proposal.
#Wilben (talk) They are all blocks that can be destroyed exclusively with fire. Seems pretty cut and dried to me.
Merge Fiery and Bonfire Blocks, keep the Flame Blocks split (flames of a feather, uh, scald together?)[edit]
- Camwoodstock (talk) Hey, these actually have A unique gameplay element to them! ...Sure, it's not much, and it's tied in with Torches, which already have their own page, but the difference in gameplay is significant enough, especially compared to "well, one's from a Mario game, and one's from a Wario game", that we think keeping these two split up is justifiable... Though, the similarities should definitely be acknowledged, of course.
- Hewer (talk) I'm neutral on Fiery Block but the Bonfire Block and Flame Block should stay split because they are two separate objects that both appear in the same game (Wario Land 3).
- LinkTheLefty (talk) The rest are similar enough, but the torch version definitely is dissimilar and functions more like a barrier that has a totally separate requirement (and the other block is in the same game).
- Doc von Schmeltwick (talk) - Per my comments and prior discussion.
- Mr. Sorbetti (talk) Per Doc.
- Wilben (talk) Per all.
- Yoshi Block (talk) Primary choice. Per all.
Keep split (status quo) (it's a controlled burn!)[edit]
Comments (it burns, burns, burns)[edit]
- WLIII's giant, "fades out of existence when a group of torches nearby are lit" Flame Block appears alongside the smaller, recurring "touch directly with fire to destroy" Flame Blocks. Different appearance and function within the same game. That's why I didn't include it in the prior conversation. Doc von Schmeltwick (talk) 23:17, September 3, 2026 (UTC)
- The wording on the actual page was a little ambiguous about that. We would still personally merge them, especially since the two are meant to be fairly similar in terms of gameplay, even if one happens to have the extra condition of "you light the Torches and not the blocks themselves", but we could understand wanting a split for that, since it's certainly more different gameplay-wise than Fiery Blocks and Bonfire Blocks are.
~Camwoodstock ( talk ☯ contribs )
00:12, September 4, 2026 (UTC)
- Wonder why that could be... Doc von Schmeltwick (talk) 00:27, September 4, 2026 (UTC)
- The wording on the actual page was a little ambiguous about that. We would still personally merge them, especially since the two are meant to be fairly similar in terms of gameplay, even if one happens to have the extra condition of "you light the Torches and not the blocks themselves", but we could understand wanting a split for that, since it's certainly more different gameplay-wise than Fiery Blocks and Bonfire Blocks are.
- Can we actually add an option that just moves the Virtual Boy Wario Land block over to fiery block (possibly with a part-conjecture)? Those are functionally identical and the argument isn't as strong when the also-similar-looking flame block is a separate object. LinkTheLefty (talk) 14:44, September 4, 2026 (UTC)
Create screenshot subcategories for the Mario & Luigi games to contain collectable location screenshots[edit]
create subcategories 7-0
I went to use the category containing Mario & Luigi: Dream Team screenshots to see what giant battle screenshots the wiki has, but I encountered a problem as I tried looking: the category is flooded with screenshots intended to show the locations of collectables. I noticed how Category talk:Mario & Luigi: Dream Team images featured a discussion pointing out this same problem, but it went nowhere. I revived that discussion, which made it clear that a proposal should probably be made regarding this. These "collectable location screenshots" as I will be calling them basically show where every block, bean, item given by an NPC, coin, rocks that give a coin when broken, and each petrified Pi'illo are. What makes these screenshots a pain to sift through are that:
- These screenshots all have a filename structure that does not group them all together. Each area's set of screenshots are together, but the screenshots as a whole are not in a row, meaning they constantly interrupt the non-collectable screenshots.
- These screenshots are formatted in a way that makes them unfit for use other than showing the location of a specific collectable. They arrange the screens into a horizontal layout to better fit into tables when viewing the wiki with a computer. The minimaps being in these screenshots is a big problem; many screenshots crop out an entire screen as it hurts the ability to present something in the game.
- There are hundreds, potentially over a thousand of these screenshots.
Now...let us take a step back and look at the other Mario & Luigi games' screenshots categories and the same problem is happening to all eight games. The screenshots for the GBA version of Superstar Saga do not have minimaps in their screenshots, so they are more flexible, but there are still a lot of them. Brothership is on the Switch, so it does not have a bottom screen minimap, but its pause menu does feature a map of each area. Each Brothership collectable location screenshot is actually two screenshots, one of normal gameplay showing the collectable, one of the full screen pause menu map, and the two screenshots are then arranged horizontally into one file making them function in a similar way to the DS and 3DS game screenshots. For Partners in Time, of the 764 files in its screenshots category, I counted that 607 are these collectable location screenshots.
Stepping even further back, it seems like this problem is also happening with Super Mario RPG and the Paper Mario series. I do not feel comfortable broadening the scope of this proposal this much, so I want to keep it focused on Mario & Luigi, which is what I am most familiar with. Additionally, I want to make it clear that this proposal is not aiming to set the precedent that there should be subcategories broadly made for screenshots of collectable locations. This proposal aims to solve the usability problems with the Mario & Luigi screenshot categories; the usability problems just so happen to be collectable location screenshots. The proper precedent that should be set from this proposal is that screenshot subcategories should be considered if a large number of screenshots are causing a disruption.
This proposal aims to solve the problem with the Mario & Luigi screenshot categories by creating a subcategory for each affected game that would be named GAME collectable location screenshots. This name makes it clear what it contains, while also being more loose, as some collectables are not tangible items that are collected, like Pi'illos and item patches. The text of the category itself would be something like "This category contains screenshots from GAME showing the location of a collectable.".
Here are helpful links to view the current state of each game's screenshots category.
- Category:Mario & Luigi: Superstar Saga screenshots
- Category:Mario & Luigi: Partners in Time screenshots
- Category:Mario & Luigi: Bowser's Inside Story screenshots
- Category:Mario & Luigi: Dream Team screenshots
- Category:Mario & Luigi: Paper Jam screenshots
- Category:Mario & Luigi: Superstar Saga + Bowser's Minions screenshots
- Category:Mario & Luigi: Bowser's Inside Story + Bowser Jr.'s Journey screenshots
- Category:Mario & Luigi: Brothership screenshots
Should this proposal pass, I think the only realistic way to properly recategorize everything would be combing through each category, making a list of file prefixes that belong to what need recategorizing, then having PorpleBot go though it. For Partners in Time and beyond, maybe recategorizing files with a specific resolution, because these images are arrange the screens in a unique way, would work?
Proposer: Spencer PK (talk)
Deadline: September 15, 2026, 23:59 (UTC)
Collect the collectable location screenshots and place them in subcategories[edit]
- Spencer PK (talk) Per proposal. The scope of this being thousands of files spanning eight games makes a proposal needed to verify if this should be done.
- The Real Mario & Luigi Fan (talk) Per proposal.
- LadySophie17 (talk) Having created Category:Mario Kart World mission screenshots for screenshots of specific things that don't work as general gameplay screenshots, I support this standardization.
- Camwoodstock (talk) What, is September Category Season now? ...Us cracking jokes aside, this definitely makes sense to us. Was kinda silently hoping this'd get proposed after seeing it got brought up in Discord about a week ago. Per proposal.
- Collectable Brett (talk) Per all.
- Mario (talk) Sure. Do it.
- Ba (talk) Yes.
Do nothing[edit]
Collectable comment screenshots[edit]
- I feel like this should extend beyond the Mario & Luigi series. Games such as Super Mario Odyssey and Donkey Kong Bananza feature a lot of collectibles, and therefore have nearly thousands of collectible screenshots that could and should probably receive their own categories.
The Dab Master 14:52, September 1, 2026 (UTC)
- The idea behind this proposal could be applied really broadly (I just forgot to include a mention of more than just the Mario RPGs). I did not want to expand this proposal even further because I do not have a good idea of just how much would be affected. Power Moons and Banandium Gems are clearly in this at first, but then what about the 240 blue coins of Super Mario Sunshine? And I just realized as I was writing this comment that this could even apply to each colored banana from Donkey Kong 64. By limiting the scope of this proposal to Mario & Luigi where the problem is clearly happening, should the proposal pass, the idea can be tested and implemented with limited scope, and the idea can then be taken further by others who better know other games. --Spencer PK (talk) 17:04, September 1, 2026 (UTC)
Remove "theme" from the identifier of various staff credits themes[edit]
Remove "theme" identifier 8-0
8 out of 8 voters (100%) approve the first place option.
A while back, various staff credits themes such as Staff Roll (Super Mario 64 theme) and Staff Credits (Mario Kart 64 theme) were moved to add "theme" to their identifiers, because their titles "can be interpreted as the list of staff for the game", as Mario jc (talk) states in this edit summary. The problem is that no other article pertaining to those themes' respective origin games share the exact title "Staff Roll" or "Staff Credits", and, as Jdtendo (talk) states in this edit summary, clarifying the subject of an article is what the {{about}} template is for, making the "theme" identifier superfluous. "Bowser's Fury Credits" and "Staff Credits (Booster Course Pass)" both lack the "theme" identifier and use the {{about}} template to clarify that the articles are about the musical themes, so why can't themes such as Staff Roll (Super Mario 64 theme) and Staff Credits (Mario Kart 64 theme) do the same?
Here are the following musical themes that would be effected if this proposal passes:
- Credits (Mario Party 2 theme) to Credits (Mario Party 2)
- Staff Credits (Mario Kart 8 theme) to Staff Credits (Mario Kart 8)
- Staff Credits (Mario Kart 64 theme) to Staff Credits (Mario Kart 64)
- Staff Credits (Mario Kart DS theme) to Staff Credits (Mario Kart DS)
- Staff Credits (Mario Kart World theme) to Staff Credits (Mario Kart World)
- Staff Credits (Mario Party 3 theme) to Staff Credits (Mario Party 3)
- Staff Credits (Paper Mario: The Origami King theme) to Staff Credits (Paper Mario: The Origami King)
- Staff Credits (Super Mario Kart theme) to Staff Credits (Super Mario Kart)
- Staff Credits (Super Mario Sunshine theme) to Staff Credits (Super Mario Sunshine)
- Staff Roll (Super Mario 64 theme) to Staff Roll (Super Mario 64)
I didn't include Staff Credit Roll (New Super Mario Bros. Wii theme) in this list, as there is a separate discussion deciding if that article should remove its identifier altogether due to no other subject sharing the exact name "Staff Credit Roll". But rest assured if its identifier stays and this proposal passes, it will be moved to Staff Credit Roll (New Super Mario Bros. Wii).
Proposer: Wilben (talk)
Deadline: September 21, 2026, 23:59 (UTC)
Support[edit]
- Wilben (talk) As proposer.
- The Dab Master (talk) Was thinking of making this exact proposal.
- Yoshi18 (theme) I don't see why not.
- Staff Credits (IanD255 theme) (talk) Per all. I'm actually surprised this proposal didn't get made sooner; but better late than never.
- Jdtendo (talk) Per proposal. Moreover, actual staff lists are called "List of [game] staff", so their names cannot collide with an article called "Staff Credits ([game])" anyway.
- Arend (talk) Makes sense. In the off-chance that someone happens to actually want to look for a game's staff, we can just use {{about}} to redirect them to the list pages that Jdtendo mentioned.
- Sargent Deez (talk) Per all, especially Jdtedno and Arend.
- Polley001 (talk) Per all.
Oppose[edit]
Comments[edit]
Identity file category[edit]
Create category 10-0
As of now, several files are in the personal files that I do not think should be in there. These files include various identity markers, such as and
. (
is marked as a Shroom file, and thus gets around the issue in a way that cannot be repeated for other pride flags.) I consider this to be a problem for several reasons:
- Making such "identity files" count against one of a user's personal files disincentivizes them to be proud of their identity.
- A limit of five personal files is intended to cut down on images that can only be used by one user; identity files, by definition, are something that can apply and be useful to more than one user.
- Identity files being tagged as a personal file by one user can make them feel possessive of that file. If someone wants to have their own version of the cross file, they ideally should be able to.
I propose that we have a heavily-monitored "identity file" tag for such files. This would allow for freer uploading and usage of such identity files without there being any negative incentives for users to upload files to express their identity. Such identity files should ideally express a sincerely-held religious, gender, sexual, locational, etc. identity (so this means that you can't upload something like ThisUserIsASpongeBobFan.png as an identity file).
Proposer: P-Tux7 (talk)
Deadline: September 30, 2026, 23:59 (UTC) Closed early on September 23, 2026, 23:59 (UTC)
Support: Add the identity file category[edit]
- P-Tux7 (talk) Per proposal.
- Iand255 (talk) Per proposal. These symbols and flags should be considered integral to all user pages, and have no reason to continue clogging up people's personal files, especially in 2026, a time when people are arguably the most open with their identities they've been in all of recorded human history.
- Camwoodstock (talk) We can get behind having a category of images like this. We did feel kinda weird hijacking an image from a random 'Shroom issue for our own userbox, and we imagine many people have come across similar issues with having to effectively leech off another user's "personal image" like this.
- SuperGamer18 (talk) Per all, particularly Iand255.
Also I didn't expect one of my personal files here and I don't know what to say about that - Illuminoid (talk) Per all. This would make finding these files easier, preventing duplicate uploads.
- The Real Color Splash Fan (talk) Per all.
- Maw-Ray Master (talk) Per all.
- The Garlic Bread Master (talk) Per all.
- Yoshi2026 (talk) Per all, especially Iand255.
- Aomaf (talk) Also Per all
Oppose: Do not add the identity file category[edit]
Comments (identity file category)[edit]
If we're going to use that particular cross image for identity instead of for personal use, I do feel like it needs to be reuploaded to not only be bigger, but also be transparent (it sticks out like a sore thumb in Dark mode), and I'm not sure if we can find an exact replica with those two conditions. Though, making it a public file does have the benefit of finding a better cross symbol to upload over it, I guess.
rend (talk) (edits) 10:22, September 16, 2026 (UTC)
- The transgender flag colors are ever so slightly off in the 'Shroom image and it's been bothering us we can't fix it because, well, that's a 'Shroom image. Having a version that's de-coupled from that baggage would be very nice to have, is all we're saying. ;P
~Camwoodstock ( talk ☯ contribs )
15:53, September 16, 2026 (UTC)
- Yeah, I noticed that as well. The trans pride flag's light blue is supposed to be close to baby blue, but the image on our wiki is closer to the Luxembourg flag's sky blue.
rend (talk) (edits) 18:01, September 16, 2026 (UTC)
- Yeah, I noticed that as well. The trans pride flag's light blue is supposed to be close to baby blue, but the image on our wiki is closer to the Luxembourg flag's sky blue.
Also, I think creating a file notice template such as {{personal-file}} for these kind of images would be useful as well. It could say something along the lines of "This file is in use as an indicator for a user's personal identity, and can be used by any user for their user page. It is not being counted as a personal file; please do not delete this."
rend (talk) (edits) 15:33, September 16, 2026 (UTC)
Don't we have a flag category used for, like, national flags? Most of these are still flag-ish, so don't they kinda qualify? Doc von Schmeltwick (talk) 17:42, September 16, 2026 (UTC)
So this gives such images {{template-image}} (Category:Template images) and/or {{project-image}} (Category:Project images) status? --Wildgoosespeeder (talk) (Stats - Contribs) 00:42, September 17, 2026 (UTC)
Introduce update history guidelines[edit]
Introduce guidelines 5-0
As early as the Family Computer, game developers were able to make changes to their games after release. Historically, these changes came in the form of revisions made to cartridges between different print runs. However, game developers were often opaque about the mere existence of revisions, leaving fans to discover the differences between two revisions of the same game themselves.
Eventually, consoles gained the ability to download game updates from the Internet. For Nintendo games, these downloadable updates became easier to document because they came accompanied with release notes. Unfortunately, some articles on the Super Mario Wiki have become too reliant on these release notes and, as a result, often fail to mention unlisted changes. These articles simply note that "several issues have been addressed to improve the gameplay experience."
Additionally, outside of these lists of rehashed release notes that are confined to game articles, articles on the wiki often do not adequately take game updates into account. Some articles might describe a mechanic only in the context of a game's initial version or its last. Other articles might indicate that a mechanic was changed in some update but not specify which update. If an update is specified, the relevant update history section might not even be linked. Finally, the ways that we refer to updates by name are incredibly inconsistent. All of the following examples are currently used on the wiki:
- "1.2.3 update"
- "an update"
- "Ver 1.2.3 update"
- "Ver 1.2.3"
- "1.2.3 patch"
- "Ver. 1.2.3 patch"
- "Ver. 1.2.3 update"
- "Ver. 1.2.3"
- "version 1.2.3 update"
- "version 1.2.3"
- "Version 1.2.3"
These issues are gradually improving across the wiki. I would say that our coverage of the update history of Mario Kart World excels at accurately providing both official context into updates and analysis down to statistic changes and changes to names in other languages.
In light of these aspects, I've written guidelines that formalize the current framework used to document update histories while also clarifying related terms and specifying how this documentation should be referenced. I propose turning these guidelines, included below, into a policy for the wiki.
This page provides an overview of how updates and revisions for games can be described and organized on the Super Mario Wiki.
In the early days of gaming, once a physical game is sold, its data could not be changed. If a game-breaking glitch were to be discovered in a game, for example, players who had already bought that game would have to suffer the glitch indefinitely. To combat this limitation, publishers would print new runs of a game, known as revisions, with updated data to fix glitches and make other changes.
Modern consoles support Internet connectivity, and game data on these consoles can be stored digitally. Every Nintendo console since the Nintendo 3DS supports some form of updates. Internet connectivity is also used to implement features such as downloadable content and other new content for existing copies of games through updates. Like revisions, updates may be distributed as part of later print runs of a game.
Revisions and updates are distinct from reissues, which encompass ports, remakes, and other versions of a game that are typically sold under a different title or for a different console. Changes made in the context of emulators such as Virtual Console are also not considered revisions or updates.
While Nintendo historically did not provide information about revisions, it provides support articles that document each game's update history. However, the wiki strives to provide complete, detailed information about both revisions and updates under the frameworks detailed below.
Revision differencesGame articles can describe a game's revision differences in a section titled "Revision differences".
As revisions are not typically identified in an official capacity, their information does not need to be organized in a particular manner. Unless an official name of a revision can be found, it should be referred to simply as the "first revision", "second revision", or so on. Distinct cartridge identifiers do not count as revision names, but they should be mentioned as an aid to identify a cartridge's revision.
Update historyGame articles can describe a game's update history in a section titled "Update history".
The start of the section should provide a brief introduction to the game's updates and how they are treated. If a support article exists, it should be cited in this introduction. The following template serves as an example, though statements can be removed or modified to fit the game being discussed.
This is a detailed list of updates that Game has received since launch. To play online, players must use the latest version of the game.
If an update has been applied, the game's current version is shown on the game's title screen.
This overview should be followed by individual sections for each update. The heading of each section should be the update's official title. If multiple titles have been used to refer to the same version, the title from the cited support article (typically in the format "Ver. 1.2.3") should be prioritized. If a version has received a unique name (such as version 2.0.0 of Super Mario Maker 2 being dubbed "A Legendary Update"), that name can be mentioned within the section and even serve as a redirect to the section. Some games, like Mario Kart 8, format version titles within the game differently compared to the relevant support article; in this scenario, the formatting difference can simply be explained once within the update history section's introduction.
Each section should describe the circumstances of the update, such as when, why, and how the update released. If the update released prior to the game's release (in what is often referred to as a "day-one patch"), that information should be noted. If the update was announced in a Nintendo Direct, that detail should also be explained. Trailers and articles for the update should be cited.
Each section should attempt to summarize notable features added by the update. Then, if official release notes are available, the section should specify that "the following release notes were provided" and include those notes within <blockquote>. The formatting of these release notes should match their source as much as possible, and like other quotes on the wiki, the contents of these notes should not be modified other than to point out mistakes with {{sic}} or provide links to relevant articles. Finally, any unlisted minor changes can be noted at the end of the update's section.
If an update history section becomes sufficiently long, it can be split to a different article titled "Game update history". The remaining section in the game article should give a brief overview of the nature of the content added across all updates while using {{main}} to link to the full article. On the split article, the introduction should contain the date that the game was released; this date serves as context to the timing of the game's updates. Additionally, all update sections should be moved under a single "Versions" heading. The split article can be categorized into the update history pages category.
Any changes not tied to a version number but still relevant to the game's update history can be listed in a final "Other changes" section.
When referring to updates in other articles, the standard wording "version 1.2.3" should be used and link to the relevant update section. Depending on the context, specifying "version 1.2.3 of Game" or simply "version 1.2.3 of the game" is more clear. Alternate terms like "patch" should be avoided.
Proposer: B700465189a9 (talk)
Deadline: September 24, 2026, 23:59 (UTC)
Support: Introduce update history guidelines[edit]
- B700465189a9 (talk) Per proposal.
- Iand255 (talk) This all seems fairly reasonable. I personally see no reason to not standardize the coverage of update history.
- SuperGamer18 (version 1.8) We DESPERATELY need this. Per proposal.
- The Dab Master (Ver. 2.8.7) Per proposal.
- Yoshi18 (Ver. 10.0.0) I'm in for this, as long as "Ver. [number]" becomes the (main) way we refer to updates by name.
Oppose: Reject update history guidelines[edit]
Comments (update history guidelines)[edit]
In your proposed page, you're missing examples of what features internet connectivity can implement ("Internet connectivity is also used to implement features such as and other new content[sic] [...]"). Additionally, what if a game only gets a single revision? How would that be worded in the Revision differences section? SuperGamer18 (talk) 17:39, September 10, 2026 (UTC)
- That sentence has been corrected. If a game only has a single revision, then the relevant section would simply list all of the differences of that single revision. B700465189a9 (talk) 20:56, September 18, 2026 (UTC)
3DS Mario & Luigi duplicate file removal[edit]
Remove duplicate files 6-0
If you look in multi-game galleries, such as Gallery:Koopa Troopa, you begin to notice something odd: many of the sprites for the Mario & Luigi Nintendo 3DS games have identical appearances. Of course, this is likely due to AlphaDream's budget-saving measures incentivizing them to reuse sprites between the four 3DS games. But the really odd thing for wiki purposes is, these reused sprites are uploaded as separate files despite being completely identical. I think these images need some cleanup to condense them to one file that has multiple game categories. Of course, the exception is if the images are of certain unique, game-specific poses of that character or enemy that are unique to only one game, which can still maintain their separate file status and separate gallery entry. It is also likely that some sprites received minor revisions between games, and so it is fine for such sprites to be split into multiple files to illustrate the differences.
Proposer: P-Tux7 (talk)
Deadline: October 1, 2026, 23:59 (UTC)
Agree: Reduce identical appearances across games to only one file[edit]
- P-Tux7 (talk) Per proposal.
- Yoshi & Paper (talk) Per proposal. We also do this for things like render and model reuse, so I don't see why we shouldn't do it here.
- Brett (talk) Per proposal.
- Iand255 (talk) Per all.
- Tails777 (talk) Per proposal. I've seen this and always disagreed with it. There's no reason we can't just state the sprite comes from multiple games and use only one. Unless it has noticeable differences (with something like appearance or animation), we don't need five uploads of the same Goomba sprite from five games.
- Doc von Schmeltwick (talk) - While obviously specific to when they are outright reused (occasional tweaks do happen uncommonly), just take a look at Big Tail Goomba's page. There's four games using the same sprite covered there, which is four of five of the enemy's total appearances!
Disagree: Keep appearances from separate games as separate files even if they are identical[edit]
Comments (3DS Mario & Luigi duplicate file removal)[edit]
Did You Know? factoid pool and manager role[edit]
do not implement changes 1-8
As it currently is, the "Did You Know?" template on the main page is just edited by one person per week, with no structural organization to ensure a variety of sources for facts. Not only that, but this carte blanche has led to some really boring "fun facts" such as "Did you know LEGO Mario has been around since 2020?" or "Did you know that Super Mario 64 is famous for being the first 3D Mario game?" because no one actually vets the factoids before they get on the main page. Since this section is on the main page, it serves to give prospective wiki readers and editors a good or bad first impression of how scrupulous we are as a wiki. Since we're a wiki about various series and mediums, it seems obvious to me that the current method can lead to biases and blind spots based on whoever is doing it that week. I propose that we have future "Did You Know?" factoids submitted via a system (such as DMs to one user, a spreadsheet, or a Google Poll) and a manager whose role it not only is to randomly choose several of these factoids from the pool per week in order that the sources of factoids, but also to be able to factually verify the factoids with other Super Mario Wiki staff and throw out any that are obvious information or too niche. The role of manager also allows for someone to be held responsible for disappointing or erroneous "Did You Know?" sections while not discouraging ordinary users from submitting facts. While I have a master's degree and am willing to use my preexisting research experience to be in the role of the Did You Know? manager, I am more than happy to support anyone else who would like to claim priority to the role.
Proposer: P-Tux7 (talk)
Deadline: October 9, 2026, 23:59 (UTC)
Support: Implement these changes to Did You Know?[edit]
Oppose: Keep Did You Know? as first-come, first-serve[edit]
- Xiahou Ba, The Nasty Warrior (talk) Mirroring what Salmancer said in the comments, this is an unnecessary position that doesn't necessarily address quality points, and how it worked hasn't really been an issue in the first place aside from a few bad points here and there (which are easily corrected by editing out the points). We should keep the DYK as straightforward and open as it is, edit accordingly if you feel there are bad points, or discuss it with others if you come to a disagreement.
- Hewer (talk) I agree that there's been some lame Did You Knows lately but this is an unnecessarily complex solution. Just replace the bad points with better ones.
- Camwoodstock (talk) Per Xiahou Ba and Hewer. We feel like trying to make this more "official" in how it's handled just kind of makes it more annoying for everybody. We haven't really viewed the Did You Know section as first-come-first-serve or been that particular about individual points being underwhelming. In the latter case, just ask around and if the vibe is "this should be replaced", come up with a decent replacement yourself if you're feeling up to it. In the former case, if you want a week of the Did You Know to yourself, literally just ask, and provided there's ample time before the request and enough people can vouch for it, go for it. Heck, that's how we did our first Did You Know section. We just asked nicely. It really is as simple as "you can ask nicely for things, and provided you have decent writing to back it up and can make sure you're not over-stepping someone else, you can generally just do it."
- Iand255 (talk) Per all.
- Illuminoid (talk) Per all. The Did You Know template is such a minor portion of the wiki. Giving it a manager overcomplicates things.
- Wandering Poplin (talk) Overkill solution to a relatively minor "problem." Reminiscent of a somewhat similar proposal from earlier this year, for all the wrong reasons. Per all.
- Dominoes (talk) Per all.
- Did Yoshi Know? (talk) Per all.
Comments (Did You Know? factoid pool and manager role)[edit]
This feels like a lot of bureaucracy and off-wiki messaging that would bog down a fairly lean system. It would make it harder to have a theme when the situation calls for it. And I don't think anyone wants to be singled out for being bad at Did You Know updates. (There's a reason all the callout posts being referenced don't note the editor who added the bullet point). I think just making it so that each user can only make a full new Did You Know section once per month would be a leaner way to get the same results. Since it would make sure different users are making Did You Know sections, its less likely for the updater to run out of good ideas for bullet points. It also would ensure more than one person gets to make Did You Know sections. This system could be easily managed using a single on-wiki page, rather than an entire off-wiki pipeline. Salmancer (talk) 23:26, September 25, 2026 (UTC)
- I don't think narrowing down to once per month per user is a good idea (that's four weeks of restricted editing, it's a very bloody long time). What would happen is if, say, one person is managing the template, that means it will stay unedited for days, potentially until someone notices and updates it. There are better ways to vet editing of the template than essentially ban people from editing.
Xiahou Ba(the Nasty Warrior) 00:13, September 26, 2026 (UTC) - As written, rejected facts wouldn't require a "callout" unless the user had a history of spamming the system.P-Tux7 (talk) 00:59, September 26, 2026 (UTC)
- If the manager role is publicly known, presumably placed somewhere on MarioWiki:Maintenance/Main page instead of just being in Did You Know's edit history, held by exactly one person, and that one person is the single point of failure for bad Did You Know bullet points reaching the main page, then its absolutely 100% only the manager's fault when bad Did You Know bullet points reach the main page. The more unscrupulous of people on the internet will be happy to target that manager. Further, putting all the responsibility for culling bad trivia points on one person is sure to result in that one person using a provided weak trivia point because their lack of knowledge regarding a specific branch of the franchise led to the trivia point looking better than it is. Salmancer (talk) 14:58, September 26, 2026 (UTC)
Merge some articles for arrangements of recurring themes, and clarify when to split them[edit]
do nothing 3-7-9
9 out of 13 voters (69.2%) approve the first place option.
I've observed that some users have been a bit overzealous with the splitting recurring arrangements portion of our music coverage policy, which has resulted in oddities like the Underground BGM being split across multiple pages because the Super Mario Bros. 3 and New Super Mario Bros. Wii arrangements were considered distinct enough to split, without prior discussion as far as I'm aware. This is pretty confusing for casual readers who aren't super attuned to the musical differences and/or aware of the specifics of wiki policy to understand when and why these splits happen, and needlessly scatters information on the same subject across multiple articles. If you go to the Underground BGM page right now, it doesn't mention New Super Mario Bros. U or Puzzle & Dragons: Super Mario Bros. Edition at all, because that information has either intentionally or by oversight been shuffled over to the page for the New Super Mario Bros. Wii arrangement. It is interesting when a particular arrangement carries its influence forward or recurs in a later game, but I would consider that a part of the history for the original theme and it can easily be communicated to the reader in a sentence or two. We don't need an entire page for that.
The recurring theme guideline (that a theme appearing in 8 or more games and/or soundtrack releases is considered recurring), in general, is very outdated and based on a lot of arbitrary standards and piecemeal decisions over several years. For example, Super Mario Galaxy and Super Mario Galaxy 2 alone are enough to boost a track to "recurring" status because those games and their soundtracks have been re-released so many times. Originally it was the only way a music piece could get an article on the wiki at all, but now we're at the point where a track doesn't even have to be named or recurring to get an article, so it doesn't serve a whole lot of purpose anymore.
There are probably more than these along the same lines, but these are the articles I'm currently aware of and would like to merge back to their original themes should this pass:
- Airship BGM
- Ground BGM (Super Mario Bros.)
- P Switch BGM / Toad's House
- Underground BGM (Super Mario Bros.)
Please note that this is not meant to target notably distinct arrangements (e.g. Metal Mario), themes that happen to quote other tracks (e.g. Purple Comet), or medleys of multiple themes. Rather, I'm trying to avoid having multiple articles for "here's the original Ground Theme again".
So then, when does a recurring arrangement get split? Putting this to policy on paper is actually more difficult than it sounds, but something has to be done here, so here's what I propose for now: Notable arrangements of existing themes can still be split on a case-by-case basis, requiring a discussion beforehand. In essence, the goal is shifting the default away from splitting as soon as possible, and encouraging editors to use their best judgment instead of trying to define a specific line in the sand and dealing with inevitable edge cases.
- Option 1: The case-by-case basis rule goes into effect, and the pages listed above are merged.
- Option 2: The case-by-case basis rule goes into effect, while the pages listed above are left alone to be discussed later. I'm willing to add/remove articles from the list based on feedback, but if you vehemently disagree with any of the merges I've proposed, you can pick this option.
- Option 3: Nothing changes, any arrangement meeting the recurring guideline can continue to be split without discussion.
Proposer: Waluigi Time (talk)
Deadline: October 17, 2026, 23:59 (UTC)
Option 1: Enact case-by-case rule and merge listed pages[edit]
- Camwoodstock (talk) Seems fair to us. Per proposal
- The Real Color Splash Fan (talk) Secondary option. Per proposal..
- Ninja Squid (talk) Per proposal.
#The Dab Master (talk) Primary choice; per proposal.
#Waluigi Time (talk) Per proposal.
Option 2: Enact case-by-case rule, individual pages to be discussed later[edit]
- The Dab Master (talk) Primary choice; a few of the articles listed are about themes that have some very extensive history, and splitting arrangements admittedly does make larger articles easier to manage.
- Mr. Sorbetti (talk) I agree that most of the splits , like Attack of the Airships, Airship Theme (New Super Mario Bros. Wii), Super Mario 2007, Toad House (Super Mario 3D Land theme), Underground BGM (Super Mario Bros. 3), Underground Theme (New Super Mario Bros. Wii), and Space Athletic, seem unnecessary, as these arrangements basically sound almost the same as the music from which they were arranged. However, for the others, I can't really say the same. Hazy Maze Cave is very, very different from your normal underground arrangement, and I would compare it to Purple Comet (theme). Toad House Minigame (New Super Mario Bros. Wii) seems to be different enough from the normal overworld bgm to grant it its own page and also fulfills a different consistent role. For the rest, I agree, and I also agree that there should be rules in place to prevent unnecessary splits, but I think Hazy Maze Cave and Toad House Minigame need their own discussion imo.
- The Real Color Splash Fan (talk) Primary option. I think if a theme hasn't received any new arrangements and was just reused at least seven times, like the arrangements of "Invincibility BGM" from Super Mario Bros. 3 and Super Mario World, (which don't have articles but were put on Template:Themes) that doesn't mean we should make a whole article for it. However, not all the themes listed above fall into this criteria, in my opinion.
- Wandering Poplin (talk) Secondary option. Per all.
- Iand255 (talk) Primary choice; Per all, specifically Mr. Sorbetti's vote and my own comment (see in the threads below).
- PipesTheVlob (talk) Per all, especially Mr. Sorbetti.
- Waluigi Time (talk) Secondary choice.
Option 3: Do nothing (Oppose)[edit]
- Hewer (talk) This proposal doesn't "clarify" when to split recurring arrangements at all, it actively makes it less clear by removing the rule we already have (that 8 appearances warrants a split). The fact this proposal has already invited disagreement over what arrangements are worthy of splits demonstrates this. The current setup isn't perfect, I get that the "8 appearances" criteria is quite arbitrary (and I do think it's silly how we count soundtrack releases as separate appearances), but I still think having some kind of rule to base this on is better than going solely off of vibes, which would result in disagreements that can't really be settled.
(Also, the proposal's claim that "now we're at the point where a track doesn't even have to be named or recurring to get an article" is misleading, as the current rule is that a track must be named and/or recurring to get an article. So a track that is neither wouldn't get one.) - Wandering Poplin (talk) Primary option. Per Hewer.
- Polley001 (talk) While I'm glad to see that the issues with music theme pages are being looked at, I don't think this proposal is tackling the real problems here. Having pages for notable arrangements, even ones that aren't insanely different, shouldn't inherently be a problem. What makes it a problem is how these articles are structured fundamentally. At present they largely only exist to be appearance lists, and hardly have anything to say about the pieces or arrangements themselves, something which is (bizarrely, in my opinion) outright encouraged by the style guide. And even when accepting them as the glorified appearance lists they typically are, as this proposal does, many of them are terrible and don't actually convey everywhere that they have appeared. I actually think that Space Athletic for example is quite a decent article, it's the fact that Underground BGM (Super Mario Bros.) doesn't acknowledge any of the arrangements of "Space Athletic" in any way that I take immense issue with. Worries around content duplication are fine and all, but there are a multitude of ways around that (main article directions, transclusion) and at the bare minimum that really shouldn't apply to the appearance table of all things.
- Nelsonic (talk) Per all.
- The Dab Master (talk) Secondary choice; per all and my own vote above.
- Wilben (talk) Per all. Most, if not all, of the arrangements suggested to be merged have their own distinct instrumentations and histories to warrant their own dedicated articles (particularly Attack of the Airships and Airship Theme (New Super Mario Bros. Wii), which both have additional unique melodies at the end), and splitting them when they become recurring just makes larger articles easier to manage. I really don't see what this proposal is trying to accomplish.
- Iand255 (talk) I think the arguments made by more recent voters on this option are far more convincing than before. Secondary choice; Per all.
- Mr. Sorbetti (talk) Secondary option. Per all.
- Waluigi Time (talk) Per Polley001 specifically. The core issue in my opinion is that these splits are gutting the history sections and appearances tables of the original theme pages, leaving readers with no indication that the information exists or where to find it. If we can address that directly, I don't really have a problem with these articles existing, although I would still suggest a re-examination of the recurring theme guidelines at some point.
Comments (Super Mario Bros. 3 arrangement)[edit]
I don't think that the "Toad House Minigame" and "Hazy Maze Cave" articles should be merged. @Mr. Sorbetti also voiced disagreement with merging those articles while I was writing this comment, so I'll provide my thoughts as well:
- Although the Super Mario Galaxy and New Super Mario Bros. Wii arrangements of "Airship BGM" have distinct musical elements, they both serve the same role as an airship theme within their respective games. These two iterations, in terms of both arrangement and role, make sense to be covered on the "Airship BGM" article.
- On the other hand, "Toad House Minigame" doesn't serve the same role as a ground theme or main theme that "Ground BGM" fulfills. "Toad House Minigame" is distinctly a minigame theme, and its light instrumentation works in service of that role.
- One could mistake "Hazy Maze Cave" for being simply an underground theme like "Underground BGM". However, "Hazy Maze Cave" isn't even solely an arrangement of "Underground BGM", as the "Underground BGM" portion of "Hazy Maze Cave" is adaptively added to the theme when Mario is in certain areas of a course. "Hazy Maze Cave" and "Underground BGM" both create a moody effect through use of silence and ambiguity, but the distinct portions of "Hazy Maze Cave" feature a rhythm resembling a waltz. Waltzes are typically associated with underwater themes and cheery waterscapes, so a moody waltz might suggest the idea of suffocation. The strange clouds in Hazy Maze Cave and Goomboss Battle, the water in Wet-Dry World, and the quicksand in Shifting Sand Land certainly reinforce this theme.
B700465189a9 (talk) 20:04, October 3, 2026 (UTC)
Uh @Hewer, staff threw the "only named or recurring themes can get articles" rule into the garbage just a few days ago. Literally any song can have an article if someone writes it now. Check out PipeProject talk:Music#Clarifying page creation & theme naming rules for the rundown. It also updated MarioWiki:Article naming#Musical theme titles accordingly. Salmancer (talk) 01:27, October 4, 2026 (UTC)
- My bad, I haven't been paying attention to PipeProjects. I do think it's weird that this change was just spontaneously made with no proposal, when the previous rules had been decided on via proposals. Hewer (talk · contributions · edit count) 10:53, October 4, 2026 (UTC)
My opinion on the matter, for what its worth since I rarely if ever deal in the music mines (which just got very deep following the new rule change!), is that we should split the difference. Original themes can have articles, arrangements of original themes that meet the recurring theme rules can have articles, but arrangements of arrangements of original themes should be dealt with on the article of the original theme and not the article of the arrangement of the original theme because it makes the arrangements of arrangements of original themes harder to find when they are not on the page of the original theme. The page about the arrangement of an original theme can note the further arrangements of arrangements of original themes, but it would not be the primary place for the arrangements of arrangements of original themes on the wiki, and thus the level of detail would be truncated. Salmancer (talk) 01:27, October 4, 2026 (UTC)
- So like, Bonus: Coins Galore! and the Mario Kart World version of Slider should be covered on Main Theme (Super Mario 64) rather than on Slider? I would think it would more intuitively be the other way round: arrangements of arrangements get covered on the arrangement page with a brief mention on the original theme page. If an arrangement is distinct enough to have further arrangements of its own, I'd think that would help the case for splitting that arrangement so you could have a place to cover them, with a brief mention on the original theme page to solve the issue you mentioned of making the arrangements of the original theme harder to find. Hewer (talk · contributions · edit count) 11:42, October 4, 2026 (UTC)
@Mr. Sorbetti @B700465189a9 @Iand255 Thanks for your input. You raise some valid points, so I've struck Toad House Minigame and Hazy Maze Cave from option 1. --
Too Bad! Waluigi Time! 17:07, October 4, 2026 (UTC)
- @Waluigi Time I think that's great; those articles, to me, make the most sense out of all of these to stay around. However, I think these articles' fates should still be decided individually later on. For me personally, I think that Attack of the Airships should be merged back into Airship BGM, but Airship Theme (New Super Mario Bros. Wii) should stay separate. As an Underground BGM savant, I think that, on top of Hazy Maze Cave, Space Athletic and Underground Theme (New Super Mario Bros. Wii) both have merit to potentially staying around, but Underground BGM (Super Mario Bros. 3) should be merged back. And I imagine a lot of other people, similarly, have vastly differing opinions of what is and isn't worth keeping around, so I think the best course of action here would be to put the rule in place and vote on everything separately afterwards.
IanD255 (talk | contribs) 02:12, October 5, 2026 (UTC)
@Hewer Perhaps clarify wasn't the right choice of words? My concern isn't that editors don't know when to split them (that's not currently an issue), or even trying to establish consistency (I know a premium is often placed on that, but bear with me here). What I am concerned about is that the policy as written being followed to the letter is resulting in the creation of articles that don't really need to exist and making navigation more cumbersome for it. I actually think it's great that there's some disagreement on some of the specific arrangements mentioned here, and it's already demonstrating what I would like to see moving forward under this change. There are actual points being raised in favor of a couple of the arrangements remaining split, but nobody's going to bat for most of them which speaks to their actual usefulness. Ultimately, what I want is for these splits to be the result of editors agreeing that there is a good reason for them (like most splits and merges that happen on the wiki!), instead of automatically happening just because an arbitrary set of guidelines says so. --
Too Bad! Waluigi Time! 17:07, October 4, 2026 (UTC)
- Then it would good to at least have some idea of what a "good reason" is. Like, why should Super Mario 2007 be merged but not Secret Course? What's wrong with Space Athletic, which is distinct enough to have been able to have further arrangements of specifically that version? Airship Theme adds a whole extra bit to the melody, why should that be considered less of a distinct theme than, say, Athletic Theme (New Super Mario Bros.) or Metal Mario? Would it not be better to avoid these kinds of arguments by having some kind of rule instead of trying to determine whether something feels split-worthy based on no particular criteria? It doesn't specifically have to be the "8 appearances" rule but I still think it would be better to have something rather than just telling people to puzzle it out themselves. Hewer (talk · contributions · edit count) 17:48, October 4, 2026 (UTC)
- As I see it, the Airship theme NSMBWii has the same "global" melody as its original version and is expanded upon. I truly do not see the issue in this being covered into one main article that could be further expanded upon than separating any different variations into different articles. If anything, this is only making it a whole hassle to seek out information when this could easily be further simplified. The Athletic theme from NSMB is obviously different from say, SMB3's athletic theme, so I presume that can get its own article. Now, I say this, but I also understand that I think having an overall policy or guideline about soundtracks might be a bit of a complicated thing, with perhaps some grey areas about how to proceed, so I do think having some sort of consensus on a case-by-case basis is a worthwhile approach over doing nothing.
(TALK)
- I brought up the NSMB Athletic Theme because it's an arrangement of Ground Theme (New Super Mario Bros.), from which it is split. And what you say about the Airship Theme I feel applies equally to the Metal Mario theme (a version of Invincibility BGM), yet the proposal uses this theme as its example for a "notably distinct arrangement" that would stay split. I'm unsure why themes such as NSMBWii Airship Theme are not also "notably distinct". Hewer (talk · contributions · edit count) 20:01, October 4, 2026 (UTC)
- As I see it, the Airship theme NSMBWii has the same "global" melody as its original version and is expanded upon. I truly do not see the issue in this being covered into one main article that could be further expanded upon than separating any different variations into different articles. If anything, this is only making it a whole hassle to seek out information when this could easily be further simplified. The Athletic theme from NSMB is obviously different from say, SMB3's athletic theme, so I presume that can get its own article. Now, I say this, but I also understand that I think having an overall policy or guideline about soundtracks might be a bit of a complicated thing, with perhaps some grey areas about how to proceed, so I do think having some sort of consensus on a case-by-case basis is a worthwhile approach over doing nothing.
Refer to lost media in the past tense[edit]
Refer to all lost media in the present tense 1-2-9-3
This is a pretty straightforward idea. I personally find it a little bit confusing to see things that in a sense don't actually exist anymore referred to with "is" instead of "was". I think it would be more elegant to say "Mario Kart Tour was a mobile game" instead of "Mario Kart Tour is a discontinued mobile game", for the same reason that "Gunpei Yokoi was a game designer" is better writing than "Gunpei Yokoi is a deceased game designer".
This would, if implemented, apply to everything in the lost media category, but I recognize that "lost media" is a somewhat broad concept and it might make more sense to instead only do this for some types of lost media. If the consensus is that only some lost media should be referred to in past tense, I'll make a second proposal covering different cases separately, based on what people bring up in the comments.
Proposer: janMisali (talk)
Deadline: October 20, 2026, 23:59 (UTC)
Refer to all lost media in the past tense[edit]
Refer to some, but not all, lost media in the past tense (and make a second proposal after this one closes to decide exactly how that would work)[edit]
- janMisali (talk) Second choice, as proposer.
- Nelsonic (talk) I don't believe stuff like Mario Kart Tour can be considered lost media; the game'll likely get a continued-interest server, and I'm pretty sure it's been datamined to high heck at this point. As far as I'm aware, most truly lost media already is referred to in the past tense (for instance, Chuck Quizmo's Quiz).
#Wandering Poplin (talk) Very, very tertiary. See below vote for reasoning.
Refer to all lost media in the present tense[edit]
- P-Tux7 (talk)I believe that "was" should only refer to services that have explicitly shut down, such as WarioWare DIY and Mario Kart Tour. Since it is possible for lost media to still exist, saying "was" is presumptive and would require edits whenever lost media is found.
- Wandering Poplin (talk) Primary option. Per this discussion. This still feels like all it is going to do is further encourage "editorial panicking." And to quote Camwoodstock from that very discussion, "It's not like Mario Kart Tour ontologically ceased to be a video game the moment the servers were pulled on it. "
- Salmancer (talk) "My limited scholarly experience says that writing about fictional works should always be done in present tense." Lost or not, the only reason we should talk about fiction in the past tense is because of its release date, its creation, its reception or temporal relation to the creation or reception or other fictional works. And again, does anyone really want to go through the trouble of updating articles from present tense to past tense every time something gets discontinued?
- Camwoodstock (talk) Per our past selves when we say that it's not like lost media ontologically stops being a thing the moment it's no longer available to the public. Both in the event of server closures, but also in regards to things that are like, physically lost. Consider something like Mario Kart XXL, which, for a period of time, had only one known copy that was being hoarded by a collector. Even though this individual could literally hold the cartridge in their hands and play it on a Game Boy Advance, since it wasn't yet available to the public, it would still qualify as "lost media"... And it wouldn't make much sense to say that the game "was", or that they "owned" it. They clearly had it in their possession at that present moment.
- Illuminoid (talk) Per the discussion about this on Talk:Mario Kart Tour.
- Yoshi18 (talk) Primary choice. Per all.
- Iand255 (talk) Primary choice; per all.
- Past Brett (talk) Per all. Just because a media is no longer fully accessible doesn't means it no longer exists.
- The Dab Paster (talk) Per all.
Do nothing[edit]
- Wandering Poplin (talk) Secondary option. Same reasoning as above. I'm just not really a fan of this idea...
- Iand255 (talk) Secondary choice; per all.
- Yoshi18 (talk) Secondary choice. Per all.
This was the comments section for the lost media tense proposal[edit]
@janMisali You are citing the wrong Mario Kart game in your proposal's example.
- Mario Kart World is the game released on the Nintendo Switch 2 last year.
- Mario Kart Tour is the mobile game which was recently shut down.
Wandering Poplin (talk) 19:15, October 6, 2026 (UTC)
- @janMisali You still have a leftover instance of "Mario Kart World" in the proposal's prose. Wandering Poplin (talk) 23:20, October 6, 2026 (UTC)
- Thanks, I can't believe I didn't spot that. jan Misali (talk · contributions) 16:14, October 7, 2026 (UTC)
If the third option passes, will real-life closed physical locations (Casa de Mario and Mario Factory (arcade)) also be referred to in present tense? 1468z (talk) 19:35, October 6, 2026 (UTC)
- I feel like those being called lost media in the first place is a bit misleading. I don't think that timed real world physical events that can't be experienced anymore because time did it's thing and passed should be lumped in with lost video games, movies, books, etc. Those things can be emulated, or archived in their entirety, or converted to a digital e-book. I can't emulate Christmas of 2012, just like I can't emulate going to Casa de Mario; they're not really lost media in the same way works of arts are, but there isn't really much of a better way of classifying them, so they get referred to as lost media anyway.
IanD255 (talk | contribs) 21:53, October 6, 2026 (UTC)
- Agreed. Mario Factory isn't really "lost media", because it really wasn't even "media" to begin with. Wandering Poplin (talk) 22:08, October 6, 2026 (UTC)
Change the name of the Hello, Mario! / Hello, Yoshi! / Hello, Luigi! / Hello, Peach! template[edit]
do not change the template name 2-2-8
As it is, these four My Mario games have the clunky title of "Hello, Mario! / Hello, Yoshi! / Hello, Luigi! / Hello, Peach!" in their template. I think we could stand to reduce this to a shorter, catchier name that doesn't look weird when stacked with other templates. I think folding them into a series makes sense based on how the games are not only named after each other, but contain very similar gameplay.
Proposer: P-Tux7 (talk)
Deadline: October 20, 2026, 23:59 (UTC)
Hello, Mario! (series)[edit]
- P-Tux7 (talk) Per proposal. I consider this to be the most "future-proof" option just in case there are more My Mario games that aren't based on the model set forth by Hello, Mario!.
- Hello, Yoshi18! (talk) Primary choice. Per P-Tux7. Considering we just got 2 new games (and already have gotten 4 in the span of a year), it seems like Nintendo doesn't wanna abandon this gameplay style and will likely apply it to more characters in the future, thus this indeed being the safest future-proof option.
My Mario games[edit]
- P-Tux7 (talk) Per proposal. Suggested by User:LadySophie17.
- Hello, Yoshi18 (talk) Secondary choice. Per Camwoodstock.
#Camwoodstock (talk) This one makes the most sense to us, considering how we handle other templates of this ilk, like {{Wario games}}.
#Illuminoid (talk) "Hello, Mario (series)" appears to be conjectural. "My Mario games" name is shorter than the status quo and accurately describes the navbox.
Do not change the name of the Hello, Mario! / Hello, Yoshi! / Hello, Luigi! / Hello, Peach! template[edit]
- Hello, Dab Master! (talk) I feel like "series" implies it is an actual series navbox, such as {{Wario games}} or {{Yoshi games}}, which is not the case here.
- LadySophie17 (talk) I gave this some thought, per my comment below. (TLDR: I think its better to have an all-encompassing My Mario template rather than focus only on the games)
- The Real Hello, Mario/Yoshi/Luigi/Peach! Fan (talk) No one has complained about the name of
{{MIM}}{{MEY}} since it wascreatedchangedeightseven years ago, which means {{Hello, Mario!}} is perfectly fine with the current name. - Hello, Wandering Poplin! (talk) Per all.
- Hello, Ian! / Hello, D! / Hello, 255! (talk) Per all. I don't oppose the idea itself, but the way this proposal is going about it doesn't sit right with me.
- Camwoodstock (talk) On second thought, per Sophie's idea. Having a united navbox for all My Mario stuff is probably for the best long-term, especially if Nintendo plans to keep supporting this line. (If Sophie's idea of turning this navbox into an all-encompassing one were made an option, we'd vote for it in a heartbeat.)
- Illuminoid (talk) Per all.
- Hello, Rykitu! (talk) Per all.
Comments ([Change the name of the Hello, Mario! / Hello, Yoshi! / Hello, Luigi! / Hello, Peach! template])[edit]
Reminder that we may also need a nav template for the My Mario product line as a whole, not only including these four Hello, [name]! games, but also the My Mario (book series), and presumably the It's Me, Mario! Stop Motion Shorts as well.
rend (talk) (edits) 20:48, October 6, 2026 (UTC)
Alright, perhaps this proposal was not worded as well as it could have been. My original idea was to use the My Mario name as the umbrella term for all of those games, to avoid having a section header called ==Hello, Mario! / Hello, Yoshi! / Hello, Luigi! / Hello, Peach!==. The reasoning behind it is that using all four names is unwieldy and does not scale well if more of those apps are released. The official My Mario website explicitly states "My Mario™ is a collection of products, games, and experiences [...]" and includes the Hello quartet of apps in its Games & Apps section, which solidifies them as being under that brand name. Since "My Mario" is not a game series, "My Mario (series)" would be incorrect in my view, so I offered "My Mario games", essentially meaning "games under the My Mario brand" as an alternative. I don't know where the idea of simply "Hello, Mario!" came from.
I was not aware this also concerned the navbox, but I see no reason not to name it that. Taking what Arend said into consideration, I think our best path in this scenario is to have a single "My Mario" navbox for the entire brand, with a section for the games and elements which appear in them. — Lady Sophie_17
(T|C) 21:08, October 6, 2026 (UTC)
- You know what's kinda funny? I think that I sort-of suggested exactly that before.
rend (talk) (edits) 08:02, October 10, 2026 (UTC)
@User:The Real Color Splash Fan this is a poor argument because the title of that Navbox was only changed to what it is now two years ago. [1] WACCA Lily R (Talk)
12:48, October 7, 2026 (UTC)
Remove overall first and latest appearances from crossover subject articles[edit]
canceled by proposer
Decided the changes proposed were unnecessary
Currently, crossover subject articles list the overall first/latest appearance of them, followed by the first/latest appearance within the Super Mario franchise. I personaly do not like this, as it means we have to keep track of multiple games that arn't within coverage. To solve this, I feel like we should remove the overall first/latest appearances and only describe their first/latest appearance within the Super Mario franchise, and modify the infobox to something like "First/Latest Super Mario related appearance" to match.
Proposer: Setta3434 (talk)
Deadline: November 10, 2026, 23:59 (UTC)
Support[edit]
Oppose[edit]
- Wandering Poplin (talk) Personally, I do not see why keeping track of the origin of non-Mario characters as a separate listing is that much of an issue. If you dislike having to write those sections, surely another editor on this wiki would be glad to handle it instead. Additionally, my analysis of the writing left me with the impression that this proposal is rooted a bit too deeply in "personal preference", rather than "tangible problem", and removing unambiguously valuable information from the wiki due to something like that is simply not a matter I can support. I'm sorry.
- The Real Color Splash Fan (talk) Per Wandering Poplin.
- Camwoodstock (talk) We could sort of understand for latest appearances specifically, and only for stuff that's from the Mario franchise, considering there's plenty of things that had their latest appearance in the Minecraft Mash-Up Pack that clog the latest appearance in the Mario franchise. (Looking at you, Volcano Lotus.) The problem is that this proposal is going after stuff that is not from the Mario franchise... And then doesn't have the dignity to actually go after things in the case something is from the Mario franchise? It's just making that particular flavor of Wiki Jank even more confusing, and doesn't even really fix it. No thanks.
Comments[edit]
@Setta3434, your proposal contains a few several grammatical errors, formatting errors, and other logical fallacies. I had to fix an entire section before writing this comment, much less submitting my vote. You might want to try and correct some of them while there's still time, because all collectively, they kind of erode the foundation of your argument. Wandering Poplin (talk) 01:27, October 27, 2026 (UTC)
Remove the "theme" in the identifier for Game Over themes[edit]
Remove "theme" identifier 8-0
For some reason, back in August, all the Game Over theme articles were moved to have "theme" in their identifier. There was no proposal related to this change, but I assume it was because people could interpret the title as an actual Game Over from the specific game, rather than the theme. That argument is flawed because the biggest reasons someone would even be looking for a specific Game Over would be the specific theme or the Game Over screen itself. The musical theme articles cover both of these, because every musical theme article is about the theme and an image of where it plays in the infobox, which in this case is the Game Over screen. Finally, if it is likely that people would be searching for the specific instance of a Game Over, then {{about}} could be placed at the top of the page, like this:
{{about|the theme from [[New Super Mario Bros.]]|information about the specific instance of a Game Over in that game|{{section|Game Over|New Super Mario Bros.}}}}
Finally, these are the pages that would be moved if this proposal were to pass:
- Game Over (Donkey Kong Jr. Math theme) to Game Over (Donkey Kong Jr. Math)
- Game Over (Donkey Kong Country 2: Diddy's Kong Quest theme) to Game Over (Donkey Kong Country 2: Diddy's Kong Quest)
- Game Over (Donkey Kong Country 3 for Game Boy Advance theme) to Game Over (Donkey Kong Country 3 for Game Boy Advance)
- Game Over (Super Mario Bros. theme) to Game Over (Super Mario Bros.)
- Game Over (Super Mario Bros. 2 theme) to Game Over (Super Mario Bros. 2)
- Game Over (Super Mario Bros. 3 theme) to Game Over (Super Mario Bros. 3)
- Game Over (Super Mario World theme) to Game Over (Super Mario World)
- Game Over (Super Mario 64 theme) to Game Over (Super Mario 64)
- Game Over (New Super Mario Bros. theme) to Game Over (New Super Mario Bros.)
- Game Over (New Super Mario Bros. Wii theme) to Game Over (New Super Mario Bros. Wii)
- Game Over (Wrecking Crew theme) to Game Over (Wrecking Crew)
- Game Over (Dr. Mario theme) to Game Over (Dr. Mario)
- Game Over (Mario Clash theme) to Game Over (Mario Clash)
- Game Over (Paper Mario: Sticker Star theme) to Game Over (Paper Mario: Sticker Star)
- Game Over (Paper Mario: Color Splash theme) to Game Over (Paper Mario: Color Splash)
- Game Over (Paper Mario: The Origami King theme) to Game Over (Paper Mario: The Origami King)
- Game Over (Captain Toad: Treasure Tracker theme) to Game Over (Captain Toad: Treasure Tracker)
- Game Over (Super Mario Land 2 - 6 Golden Coins theme) to Game Over (Super Mario Land 2 - 6 Golden Coins)
Also, Game Over (Super Mario Land 2 - 6 Golden Coins) never had "theme" at the end to begin with, I guess.
Proposer: The Real Color Splash Fan (talk)
Deadline: November 8, 2026, 23:59 (UTC) Closed early on November 1, 2026, 23:59 (UTC)
Game Over (Support)[edit]
- Game Over (Paper Mario: Color Splash) Per proposal.
- Camwoodstock (talk) Makes sense to us, it's pretty unlikely someone would assume that there's individual pages for each game over screen, and anyone that somehow is expecting that could just take the proposed {{about}} link to the actual section. Continue! (Per proposal.)
- Arend (talk) This sounds familiar... Anyway, per that familiarity, I suppose, for the sake of consistency.
- Iand255 (talk) Per proposal.
- Wilben (talk) Per all.
- Wandering Poplin (talk) ...You mean we weren't already doing this already? Perhaps I've confused it with the aforementioned staff credits proposal...? Anyway, per all.
- Brett (talk) Per all.
- Game Over, Yoshi (talk) Per all.
Game Over (Oppose theme)[edit]
Game Over (Comments)[edit]
For context, discussion to move these pages was held here. Also, you don't need to manually pipe the section link like that; {{section}} can do that for you, like this: {{section|Game Over|New Super Mario Bros.}}.
The Dab Master 13:33, October 26, 2026 (UTC)
On the subject of proposal limits[edit]
Remove proposal limits 0-0-10-0-0
Alright, I want to preface this by saying I am not necessarily suggesting we get rid of limits on proposals altogether. That will be a choice in this proposal, but I will say I can understand why they exist in the first place.
The issue I have does not come from that they exist, but more so how they are handled. Presently, if a user creates more than five proposals, counting either ongoing or unimplemented proposals, their new proposal is immediately canceled, and they cannot re-propose it until one of their five either concludes or is implemented. Sure.
However, I have seen valid discussions (including one of mine) during such proposals, and, in the case of my own, the proposal was re-proposed by another user soon after and passed with unanimous support. I cannot quite remember the user who stated this, but I remember that somebody said that this new rule seems to occasionally stifle and end valid discussions. Again, I can understand the why (there were over 400 proposals held last year, and I am not exempt from being part of the overflow), but I do feel like the how needs to be fixed up a little bit.
Personally, I don't feel like I've seen this limit solve issues. It caused multiple; the one I mentioned above about stifling of discussions, as well as general confusion because this new rule was not widely communicated when it was implemented.
Therefore, I have the following suggestions;
- Avoid outright canceling these proposals. Perhaps a new color code - maybe, say, pink text - can be created, that states that the proposal has been suspended. Not canceled, but put on hold until one of the user's proposals has ended or has been implemented. (I am open to different words to be used in place of "suspended" if need be). It could look something like this;
SUSPENDED
During a proposal's suspension, it cannot be voted on or edited, though comments can still be added. After the proposal's suspension date ends [whenever the user implements one of their five, or if one of their ongoing five ends], voting resumes on the proposal with the two-week deadline (which can be moved depending on when the proposal becomes active again) active again. Of course, there would also need to be a deadline of suspension in case users never implement anything. I feel two weeks is fair.
Granted, there would need to be a rule added against relentlessly creating proposals and getting them suspended, though I don't see why anyone would want to - they couldn't raise their issues in any form for what could end up being at least two weeks, more if they do not implement their proposals right away. I am open to suggestions on this part, but perhaps this could be worthy of a reminder, and a warning if it continues happening?
- My second option is to simply avoid canceling proposals that have received more than four votes - the minimum required to pass or fail - before being canceled. If the proposal is on track to pass/fail, it should be allowed to pass/fail and should not have to start from scratch. If a proposal receives less than the required number of votes to pass or fail, it can be canceled like any other over-the-limit proposal.
- My third and final option is the nuclear one; end proposal limits, period. I know what this can bring - I saw it last year - but, at the same time, I've seen a steep decline in proposals. Nobody really seems to be creating proposals to the extent that this rule even needs to come into play for the most part. Counting my own, I think I've only really seen two or three proposals get canceled due to this rule. I don't feel like the volume of proposals being created really requires this rule, especially considering that the volume of proposals (still counting my own) relatively persisted to the end of 2025 and then faced a steep decline in 2026. There have been 189 talk page proposals this year, down 54% from the 415 in 2025. Additionally, 2024 had 242 proposals, which was over 150 less than 2025. 2025 appears to have been the exception, not the status quo. I also do recall that one of the reasons that this was put into place was because of the potential to clog archives, and also, if I remember, it may have been related to repeatedly canceling proposals before they fail and/or leaving a mountain of unimplemented proposals.
Additionally, I feel I should add that even when there were a ton of proposals, these were all genuine attempts to improve the wiki. I've only seen really one user create frivolous proposals (whom I will not name), and they have since been blocked. There may have been a lot, but I do not recall seeing any proposals created that wouldn't help something, or at least weren't attempting to.
- On that last subject, I will add a variant of this option. Remove proposal limits, but require that at least X number of proposals are implemented after a certain timeframe. This would solve that last issue.
Proposer: Nelsonic (talk)
Deadline: November 12, 2026, 23:59 (UTC) Closed early on November 5, 2026, 23:59 (UTC)
Implement the "Suspended" option[edit]
#Nelsonic (talk) Per proposal.
Avoid canceling proposals that receive more than four votes prior to going up for cancelation[edit]
#Nelsonic (talk) Per proposal.
Remove proposal limits[edit]
- Nelsonic (talk) I don't personally think this would bring about what the limits were put in place to prevent.
- Hewer (talk) I was never a fan of this rule. I can understand the desire to incentivise people to implement their proposals but I don't think this rule ever really achieved anything beyond pointlessly delaying decisions and wasting time for no real benefit, and making the proposal process more bureaucratic than it needs to be. If someone really is making an unreasonably large number of proposals then I think it can be dealt with on a case-by-case basis rather than just automatically killing proposals that may have been genuinely useful and forcing them to be re-proposed later. I also don't think there was any discussion among users about adding this rule (at least not that I was aware of), it was just suddenly there one day.
- Iand255 (talk) Per all. As pointed out by Hewer, the kind of behavior this rule is meant to prevent should fall under not shooting your foot off, and it's existence only truly serves to prevent people with good intentions as well. As well, if someone really is just spamming proposals endlessly, I don't see why that wouldn't fall under vandalism, which only further shows this serves no purpose when it comes to actually upholding the integrity of the proposal system.
- Mr. Sorbetti (talk) Per proposal and Hewer. As pointed out by Hewer and as I may elaborate based on my experience, this rule appeared suddenly out of nowhere. While I think it may have been discussed on Discord (though I do not remember), that is not enough for changes like this to be applied to everyone. I only found out at the time by pure chance while I was still active on there. While I barely knew about the rule, another change was made to add unimplemented proposals to the count. I do not recall this being discussed anywhere. This rule is not helping anyone and hasn't even achieved getting users to implement their old proposals. As I have seen and experienced, even if you have 3 large unimplemented proposals, you can still make two more proposals that you rapidly implement while keeping the other three gathering dust. And that's not taking into account that some proposals that haven't been implemented and could be considered old were made by users who are not that active editing the wiki or do not make proposals so often. So this isn't pushing them to implement their proposals. I really do not see any benefit to this rule.
- Wandering Poplin (talk)...I was unsure about this at first, (I don't think this rule was created by accident, after all) but the rationality expressed in above votes, and my analysis of the proposals mentioned in Hewer's vote have more-or less convinced me: This rule is just not really necessary. If a user has too many unimplemented proposals, surely there are other ways of dealing with that issue, right? A {{Reminder}}, a {{Warning}} or someone else implementing the proposal themselves would probably suffice.
- The Dab Master (talk) Per all.
- Wilben (talk) Per all.
- The Real Color Splash Fan (talk) Per all.
- Mario (talk) Feels like an entire rule that was designed to address one or two users' behavior and not to fix something systemically wrong.
- Yoshi18 (talk) Per all, especially Mario.
Remove proposal limits, but require implementation by a deadline[edit]
Do nothing[edit]
Proposal Comments[edit]
On the subject of unimplemented proposals... what if we've had some kind of a PipeProject thing for this? That someone can submit a big, unimplemented or yet-to-be completed proposal to ve worked on by a large amount of users and make it a group effort?
rend (talk) (edits) 10:53, October 31, 2026 (UTC)
Change how conjecturally named music articles are titled[edit]
passed 8-0
Currently, ever since the wiki's policies were changed to allow for the creation of articles about musical themes without the need of officially confirmed names, those articles have been named without an identifier. This means that, for something such as Greenhorn Forest's theme, it is titled Greenhorn Forest's theme.
This proposal aims to change that, and came about after this discussion on the talk page for Lakeside Park's theme.
To try and summarize; I think that the titles of these pages should be changed because I see no reason why we shouldn't keep conjecturally named pages, even those for themes, consistent with officially named ones, since all doing otherwise serves to do is make things extremely confusing. I personally feel like the bare minimum for a conjectural name should be to have it be consistent with the official names Nintendo has given to similar things, and it is incredibly clear to me that this naming style is not that. For example, something like "Greenhorn Forest's theme" should be "Greenhorn Forest (theme)", because, based on how Nintendo names similar tracks officially, it's pretty clear that they wouldn't call it "Greenhorn Forest's theme" and would likely just call it "Greenhorn Forest". As well, it was pointed out several times in previous discussion that the fact that the title is conjectural is made incredibly clear by the already present conjectural title template.
Adding the "'s theme" suffix to the page name really just makes it wordier and inconsistent with the rest of the wiki. There have been arguments that it's better for avoiding using quotation marks, but I just don't agree; I feel like there are better other ways to avoid using quotation marks around the name that don't actively butcher the page's name in the process. I mean, realistically, the easiest way to do it would be to just do it the same way officially named pages do, but omitting the quotation marks so it doesn't imply it's offical.
It's like I said at the end of my paragraph in the previous discussion; it's incredibly telling that officially named musical theme pages, like "Waluigi Pinball" for example, don't have a conjectural title redirect for "Waluigi Pinball's theme", but most conjecturally named pages like this have a redirect with an identifier rather than the "'s theme" suffix.
I do wanna make it clear though that this proposal is not trying to argue that any and all pages with "'s theme" suffix should be moved to a name using the regular "(theme)" identifier. There are genuinely some pages that make sense to use it, such as Rambi's theme, where the theme is, quite literally, Rambi's theme, and it's consistent with other similar types of musical themes and how Nintendo officially names them.
The proposed change I have here is simple; move the pages that this proposal pertains to, and set the standard that all future conjecturally named theme pages should be kept consistent with officially named themes.
Being specific, if this proposal passes, these pages will be moved:
- Lakeside Park's theme to Lakeside Park (theme)
- Greenhorn Forest's theme to Greenhorn Forest (theme)
- Crescent Moon Village's theme to Crescent Moon Village (theme)
- Pinball Zone's theme to Pinball Zone (theme)
- Thwomp Volcano's theme to Thwomp Volcano (theme)
Additionally, if this proposal passes, a TPP will be started for World 2-3's theme on whether or not it should be moved to World 2-3 (theme), as it is in much more of a grey area than the rest of these pages.
Update (October 30, 2026): Per a comment by @The Dab Master; I have added moving World 2-3's theme to Bonus Area (Super Mario 3D Land) to the list of moves this proposal passing will make happen.
Update (October 31, 2026): While I still think the name from my previous update is good, there seems to be a kit of ideas getting thrown around in the comments for what the page's name should be, so I'm changing it so that, if this proposal passes, World 2-3 will be moved, but it will have it's own TPP to decide on the new name.
Update (November 2, 2026): While I was compiling my list of pages which are already adhering to this proposal's goals, which can be found in the comments, I came across a large number of articles which I accidentally missed when making this proposal which it will effect. And, while I have had a couple mentioned in the comments of this proposal up until now, the number is now big enough that I feel the need to edit the proposal to mention them loud and clear.
So, here is a further list of pages which will be moved if this proposal passes:
- Greenhorn Ruins' theme to Greenhorn Ruins (theme)
- Toad Highlands' theme to Toad Highlands (theme)
- Out of the Woods' theme to Out of the Woods (theme)
There are also some minor moves which will be done purely for consistency purposes:
- Castle theme (Super Mario 3D Land) to Castle Theme (Super Mario 3D Land)
- Unlock fanfare to Unlock Fanfare
Similar to Rambi's theme, Count Cannoli's theme will be unaffected due to the nature of it's title making sense for the subject.
Additionally, TPPs, similar to the one for World 2-3's theme, will be held for Remix 10 theme and Chain Chomp theme on where they'll be moved, albeit being much simpler. As well, while not being immediately moved or opening a TPP, discussions should be opened on what to do with and how to handle Nintendo Switch Parental Controls theme, Super Mario Bros. 3 snow theme, and Super Mario Bros. Ghost House theme. It should be noted that the location of Menu Theme will not be affected regardless of if this proposal passes or fails.
Proposer: Iand255 (talk)
Deadline: November 13, 2026, 23:59 (UTC) Closed early on November 6, 2026, 23:59 (UTC)
Support (theme)[edit]
- Iand255 (talk) Per proposal.
- Wilben (talk) It should also be noted how conjecturally-named commercial songs such as "Better Than Dirty" and "Kraft Macaroni & Cheese Presents..." both lack the "[subject]'s theme" naming and use quotations, so if those can get away with it, why not themes such as Greenhorn Forest's theme and Out of the Woods' theme?
- The Real Color Splash Fan (theme) The current way it's being done makes themes for locations that belong to a character such as Yoob's Belly's theme sound kind of weird. Per all.
- Ahemtoday (talk) Per proposal. I will say that I would find using quotation marks for these conjectural music titles odd, but I'm a noted opponent of doing that for music in general, so...
- Wandering Poplin's theme (talk) Per all. There is such a thing as "too generic", and this rather odd-looking inconsistency isn't really helping anything/anyone. In my opinion, at least.
- Arend (talk) This is more in line with how Nintendo names themes for locations and levels/stages, which are often just the name of said location, sometimes also with "Theme" added after, but almost NEVER in possessive form like the current format of "[NAME]'s theme" we currently use. That, is more common with character themes instead.
- Yoshi18 (theme) Per all.
- PaperSplash (talk) Per all.
Oppose's theme[edit]
#The Dab Master (talk) I think it's better to name a theme generically if it lacks an official title, and that generic name should always be used to refer to the theme, including the article title. If Castle theme (Super Mario 3D Land) names the theme generically, so should these articles. And writing "An arrangement of Greenhorn Forest plays…" just looks weird.
Comments (insert funny joke here)[edit]
I think a better name for World 2-3's theme would be "Bonus Area", as it serves a similar purpose to "Bonus Area" from New Super Mario Bros. Wii.
The Dab Master 11:56, October 30, 2026 (UTC)
- @The Dab Master That is a fair point, and I do agree; I will update the proposal to including moving that page as well.
IanD255 (talk | contribs) 23:25, October 30, 2026 (UTC) - In my opinion, I disagree. I think the theme should be called "Coin Heaven / Retro area" because Coin Heavens are the bonus areas in Super Mario 3D Land and I think mentioning World 2-3 and Special 1-3 in the title is also necessary. The Real Color Splash Fan
23:42, October 30, 2026 (UTC)
@The Dab Master I mean, I don't see how saying "an arrangement of Greenhorn Forest..." is any different, let alone weirder, than saying "an arrangement of "Gusty Garden Galaxy"..." or "an arrangement of "Super Bell Hill"..."
Wilben
(talk • edits) 12:47, October 30, 2026 (UTC)
- @Wilben I as well. Regardless of if the name is conjectural or not, it is the currently accepted name. We're just not putting it in quotes to avoid insinuating that it's official, which is, as pointed out in your vote reasoning, also something worth rethinking.
IanD255 (talk | contribs) 23:25, October 30, 2026 (UTC)
So, to clarify, conjectural location theme titles will follow the format "[NAME] (theme)", whereas conjectural character theme names will follow the format "[NAME]'s theme"; That's what this proposal is aiming for, right?
rend (talk) (edits) 13:49, October 30, 2026 (UTC)
- @Arend When boiled down to the bare essentials; yes, that is the gist of the baseline this proposal is attempting to try and establish. There will obviously be edge cases where a different decision can be made if the consensus is that it makes more sense another way for that specific page, but buy and large this is the format most pages will fit into.
IanD255 (talk | contribs) 23:25, October 30, 2026 (UTC)
What if we use {{derived}} instead? I think it would fit better considering the reasoning of this proposal.
The Dab Master 15:38, October 30, 2026 (UTC)
- I'm pretty sure that's not how derived names work. Derived names are about combining bits of a name from different sources (e.g. Comet Luma, Fire Incoming Chomp), which would not be applicable for Greenhorn Forest's theme or Out of the Woods' theme, as they lack official names altogether.
Wilben
(talk • edits) 16:02, October 30, 2026 (UTC)
- As pointed out by @Wilben, that's not how derivative names work. I would be open to classifying them under the term "derivative", but that would require change of the wiki's policies on derivatively named articles, an update to {{derived title}}, and some tweaks to the policy on conjectural names to account for the change in format on derivative titles; all of which are far beyond the scope of this proposal. For the moment, I am fine with leaving it as conjectural, and potentially coming back to the conversation of updating what it means to be a "derived title" later on. After all; there's no point in figuring out such a massive change before this proposal reaches a decision.
IanD255 (talk | contribs) 23:25, October 30, 2026 (UTC)
If this proposal passes, will conjecturally named musical themes be allowed to use quotations? Like I said in my vote, multiple commercial songs such as "Better Than Dirty" and "Kraft Macaroni & Cheese Presents..." currently use quotations despite being conjectural.
Wilben
(talk • edits) 03:25, November 1, 2026 (UTC)
- While it wasn't initially on my mind to change it when making this proposal; now that I've been made aware of the standard these pages set for conjecturally named music, I think my answer is a solid yes. It makes it easier to talk about and refer to the theme anyway, as quotation marks have become a way around the wiki to signify that something is "a song".
IanD255 (talk | contribs) 17:56, November 1, 2026 (UTC)
Music articles aren't my scene, but I don't like it when conjectural titles look like normal titles. I think it allows for confusing a conjectural title for a normal title. Salmancer (talk) 18:28, November 1, 2026 (UTC)
- @Salmancer I don't really agree. I'll be honest; the {{conjectural title}} template exists for a reason, and I feel like it is a very big and obvious indicator of an article's title being conjectural. I don't want to make it seem like I'm trying to discount the experiences of anyone who does get confused like this or anything, but, I feel like missing the notice at the top of the page and getting the name of the article confused for an officially confirmed one would take a significant amount of willful ignorance. To me, it feels similar to if someone didn't notice the infobox on a page; it's so big and prominent, I just can't see a world where that's actually a problem.
IanD255 (talk | contribs) 21:37, November 1, 2026 (UTC) - My thoughts exactly. Surrounding a name in quotation marks feels like treating it as official, and the use of {{conjectural title}} doesn't really make that the case any less for me.
The Dab Master 16:43, November 2, 2026 (UTC)
- Personally, I see adding quotations as less of making it seem like an official name and more of indicating that it is a theme or song. Also, we can always just add the {{conjectural}} tag next to the theme's name when linking it (e.g. "An arrangement of "Greenhorn Forest"[conjectural] plays..."). And, if nothing else, this would make these themes consistent with the songs I've mentioned above that currently use quotations despite being conjectural.
Wilben
(talk • edits) 01:03, November 3, 2026 (UTC)
- Exactly how I see it. The quotes aren't so much an insinuation of legitimacy so much as they are a replacement for saying "a song named" or "the theme by the name" or whatever other convoluted ways there would be to refer to it while making it clear that it is a song. The way we use quotation marks for songs, to me, feels like their equivalent of game names being italicized; which, in the case of those, would probably be consistently italicized regardless of if a name is conjectural or not if it weren't for the fact that I can't think of a single instance of a game having a conjectural name.
IanD255 (talk | contribs) 02:53, November 3, 2026 (UTC)
- Exactly how I see it. The quotes aren't so much an insinuation of legitimacy so much as they are a replacement for saying "a song named" or "the theme by the name" or whatever other convoluted ways there would be to refer to it while making it clear that it is a song. The way we use quotation marks for songs, to me, feels like their equivalent of game names being italicized; which, in the case of those, would probably be consistently italicized regardless of if a name is conjectural or not if it weren't for the fact that I can't think of a single instance of a game having a conjectural name.
- Personally, I see adding quotations as less of making it seem like an official name and more of indicating that it is a theme or song. Also, we can always just add the {{conjectural}} tag next to the theme's name when linking it (e.g. "An arrangement of "Greenhorn Forest"[conjectural] plays..."). And, if nothing else, this would make these themes consistent with the songs I've mentioned above that currently use quotations despite being conjectural.
Since it's continued to be talked about, I'd like to expand on @Wilben's list of conjecturally named musical themes which already didn't and don't follow the format that this proposal is attempting to get rid of:
- "Anyone Can Dance"
- "Baby, I'm Back!"
- "Be Bad!"
- "Being Together Forever"
- "Better Than Dirty"
- "Bluebeard Baboon's Curse of the Double Doubloon"
- "Bluster the Benevolent"
- Bowser Castle
- "Can You Ever Forgive Me?"
- "Castles & Forts BGM"
- "'Cause I'm Cranky"
- "Charades"
- "Club Mario"
- "Cranky's Gonna Show Ya"
- "Creeping"
- "Diddy to the Rescue"
- "Do You Know What This Means?"
- "Don't Lose Heart"
- "Feel the Power!"
- "Game Boy"
- "Game Over"
- "Gotta Get it Back!"
- "Have We Got a Deal?"
- "Head Games"
- "His Name is Donkey"
- "His Name is Kong"
- "Holograms"
- "I Got No Family Tree"
- "I Gotta Eat!"
- "I Haven't Got a Friend in the World
- "I Like Evil"
- "I'm Candy Kong's Clone"
- "I'm Leo Luster"
- "I'm Nobody's Hero"
- "I've Got it All!"
- "If I Wasn't Around"
- "Interplanetary Visitor Dudes"
- "Is There Someone I Can Truly Call a Friend?"
- "Just Remember Me"
- "Just Remember Who You Are"
- "Key Item Obtained"
- "Kongo Bongo Gone Wrongo"
- "Konnichiwa Super Famicom"
- "Kraft Macaroni & Cheese Presents..."
- "Let Me Go Back to My Home"
- "Listen to Funky"
- "Look Out, Baby Kong!"
- "Look Out, World ('Cause Here I Come!)"
- "Mario and Luigi"
- "Me Like You"
- "Metal Head"
- "Mixing Your Cares Away"
- "My Finest Hour"
- "My Wittle Evil One"
- "Mystic Oracle Summoning Chant"
- "Nintendo"
- "No One's Going to Make a Monkey Out of Me"
- "One of Us"
- "Our Love is Stronger Than a Golden Banana"
- "Over the Hill"
- "Reading the Letter"
- "Riches Galore (Let's Go!)"
- "San Francisco, New York"
- "Second Banana"
- "Something's Gumming Up the Plumbing"
- "Spellbound"
- "Super Mario
- "Super Mario RPG
- "Tell Me Everything"
- "That's Why He'd Rather Be With Me"
- "The Ape on a Mission"
- "The Banana Do-si-do"
- "The Big Bog Monster"
- "The Booty Boogie"
- "The Coconut is Cursed!"
- "The Curse of the Golden Banana"
- "The Diddy Drop Rap"
- "The Island of Kongo Bongo"
- "The Mirror Never Lies"
- "This Friendship is Wrong"
- "Vote for Me"
- "Wake Up!"
- "Watch the Skies"
- "We'll Always Be Friends!"
- "What Do You Love the Most?"
- "Why'd I Have to Fall for a Hero?"
- "With These Riches"
- "Yes Means No"
- "You'll Love the Crunch!"
It is also worth noting that the only song on this entire list which doesn't use quotation marks is Bowser Castle from Mario Kart DS, but that is an article that I personally made and deployed to mainspace, and can tell you that the only reason it doesn't is because it was deployed after I found about this strange new format that had come up, which, while I didn't agree with it and still don't, I did want to make sure I stayed consistent with until I could get around to making this proposal.
While most of these are from the extremely odd Donkey Kong Country television series, I think the most convincing of these are the songs from video games, those being "Castles & Forts BGM" from Yoshi's Island DS, "Game Over" from Paper Mario: Sticker Star, "Key Item Obtained" from Mario & Luigi: Bowser's Inside Story, "Reading the Letter" from Hotel Mario, and "San Francisco, New York" from Mario is Missing!.
Personally, seeing the sheer number of these makes it honestly baffling how this format which, as stated in my proposal, I think is highly unnecessary and confusing, picked up momentum to begin with.
IanD255 (talk | contribs) 02:53, November 3, 2026 (UTC)
- For the record, out of all of these, I do believe "Reading the Letter" would have to be renamed to "Bowser's theme (Hotel Mario)", because it's simply a better, more encapsulating title for it. The theme also plays for the cutscene when Mario and Luigi are about to enter Bowser's Seizure Palace Hotel, which also uses an extended version of the theme as one of the three stage themes (the remaining two also happen to be arrangements of this theme. While its most well-known use is in fact when Mario reads Bowser's letter in the opening cutscene, "Reading the Letter" is a rather limiting title when you consider its overall use, as well as its intended use.
rend (talk) (edits) 10:19, November 4, 2026 (UTC)
