MarioWiki:Proposals

Current time: Saturday, February 15th, 20:17 GMT

Proposals can be new features, the removal of previously-added features that have tired out, or new policies that must be approved via consensus before any action is taken. Voting periods last for two weeks, but can close early or be extended (see below). Any autoconfirmed user can support or oppose, but must have a strong reason for doing so. All proposals must be approved by a majority of voters, including proposals with more than two options. For past proposals, see the proposal archive and the talk page proposal archive.

If you would like to get feedback on an idea before formally proposing it here, you may do so on the proposals talk. For talk page proposals, you can discuss the changes on the talk page itself before creating the TPP there.

How to

If someone has an idea about improving the wiki or managing its community, but feel that they need community approval before acting upon that idea, they may make a proposal about it. They must have a strong argument supporting their idea and be willing to discuss it in detail with other users, who will then vote on whether or not they think the idea should be implemented. Proposals should include links to all relevant pages and writing guidelines. Proposals must include a link to the draft page. Any pages that would be largely affected by the proposal should be marked with {{proposal notice}}.

Rules

1. Only autoconfirmed users may create or vote on proposals. Proposals can be created by one user or co-authored by two users.
2. Anyone is free to comment on proposals (provided that the page's protection level allows them to edit).
3. Proposals conclude at the end of the day (23:59) two weeks after voting starts (all times GMT).
   • For example, if a proposal is added at any time on Monday, August 1, 2011, the voting starts immediately and the deadline is two weeks later on Monday, August 15, at 23:59 GMT.
4. Users may vote for more than one option, but they may not vote for every option available.
5. Every vote should have a strong, sensible reason accompanying it. Agreeing with a previously mentioned reason given by another user is acceptable (including "per" votes), but tangential comments, heavy sarcasm, and other misleading or irrelevant quips are just as invalid as providing no reason at all.
6. Users who feel that certain votes were cast in bad faith or which truly have no merit can address the votes in the comments section. Users can ask a voter to clarify their position, point out mistakes or flaws in their arguments, or call for the outright removal of the vote if it lacks sufficient reasoning. Users may not remove or alter the content of anyone else's votes. Voters can remove or rewrite their own vote(s) at any time, but the final decision to remove another user's vote lies solely with the wiki staff.
   • Users can also use the comments section to bring up any concerns or mistakes in regards to the proposal itself. In such cases, it's important the proposer addresses any concerns raised as soon as possible. Even if the supporting side might be winning by a wide margin, that should be no reason for such questions to be left unanswered. They may point out any missing details that might have been overlooked by the proposer, so it's a good idea as the proposer to check them frequently to achieve the most accurate outcome possible.
7. If a user makes a vote and is subsequently blocked for any amount of time, their vote is removed. However, if the block ends before the proposal ends, then the user in question holds the right to re-cast their vote. If a proposer is blocked, their vote is removed and "(blocked)" is added next to their name in the "Proposer:" line of the proposal, which runs until its deadline as normal. If the proposal passes, it falls to the supporters of the idea to enact any changes in a timely manner.
8. Proposals cannot contradict an already ongoing proposal or overturn the decision of a previous proposal that concluded less than four weeks (28 days) ago.
9. If one week before a proposal's initial deadline, the first place option is ahead of the second place option by eight or more votes and the first place option has at least 80% approval, then the proposal concludes early. Wiki staff may tag a proposal with "Do not close early" at any time to prevent an early close, if needed.
   • Tag the proposal with {{early notice}} if it is on track for an early close. Use {{proposal check|early=yes}} to perform the check.
10. Any proposal where none of the options have at least four votes will be extended for another week. If after three extensions, no options have at least four votes, the proposal will be listed as "NO QUORUM." The original proposer then has the option to relist said proposal to generate more discussion.
11. If a proposal reaches its deadline and there is a tie for first place, then the proposal is extended for another week.
12. If a proposal reaches its deadline and the first place option is ahead of the second place option by three or more votes, then the first place option must have over 50% approval to win. If the margin is only one or two votes, then the first place option must have at least 60% approval to win. If the required approval threshold is not met, then the proposal is extended for another week.
    • Use {{proposal check}} to automate this calculation; see the template page for usage instructions and examples.
13. Proposals can be extended a maximum of three times. If a consensus has not been reached by the fourth deadline, then the proposal fails and cannot be re-proposed until at least four weeks after the last deadline.
14. All proposals are archived. The original proposer must take action accordingly if the outcome of the proposal dictates it. If it requires the help of an administrator, the proposer can ask for that help.
15. After a proposal passes, it is added to the appropriate list of "unimplemented proposals" below and is removed once it has been sufficiently implemented.
16. If the wiki staff deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to cancel it at any time.
17. Proposals can only be rewritten or canceled by their proposer within the first four days of their creation. However, proposers can request that their proposal be canceled by a staff member at any time, provided they have a valid reason for it. Please note that canceled proposals must also be archived.
18. Unless there is major disagreement about whether certain content should be included, there should not be proposals about creating, expanding, rewriting, or otherwise fixing up pages. To organize efforts about improving articles on neglected or completely missing subjects, try setting up a collaboration thread on the forums.
19. Proposals cannot be made about promotions and demotions. Staff changes are discussed internally and handled by the bureaucrats.
20. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
21. Proposals must have a status quo option (e.g. Oppose, Do nothing) unless the status quo itself violates policy.

Basic proposal formatting

Copy and paste the formatting below to get started; your username and the proposal deadline will automatically be substituted when you save the page. Update the bracketed variables with actual information, and be sure to replace the whole variable including the square brackets, so "[insert info here]" becomes "This is the inserted information" and not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but the objective(s) of each voting option must be clearly defined. Such options should also be kept to a minimum, and if something comes up in the comments, the proposal can be amended as necessary.

===[insert a title for your proposal here]===
[describe what issue this proposal is about and what changes you think should be made to improve how the wiki handles that issue]

'''Proposer''': {{User|{{subst:REVISIONUSER}}}}<br>
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT

====[option title (e.g. Support, Option 1)]: [brief summary of option]====
#{{User|{{subst:REVISIONUSER}}}} Per proposal.

====[option title (e.g. Oppose, Option 2)]: [brief summary of option]====

====Comments ([brief proposal title])====

Autoconfirmed users will now be able to vote on your proposal. Remember that you can vote on your own proposal just like the others.

To vote for an option, just insert #{{User|[your username here]}} at the bottom of the section of your choice. Just don't forget to add a valid reason for your vote behind that tag if you are voting on another user's proposal. If you are voting on your own proposal, you can simply say "Per proposal."

Poll proposal formatting

As an alternative to the basic proposal format, users may choose to create a poll proposal when one larger issue can be broken down into multiple sub-issues that can be resolved independently of each other. In a poll proposal, each option is its own mini-proposal with a deadline and Support/Oppose subheadings. The rules above apply to each option as if it were a its own two-option proposal: users may vote Support or Oppose on any number of options they wish, and individual options may close early or be extended separately from the rest. If an option fails to achieve quorum or reach a consensus after three extensions, then "Oppose" wins for that option by default. A poll proposal closes after all of its options have been settled, and no action is taken until then. If all options fail, then nothing will be done.

To create a poll proposal, copy and paste the formatting below to get started; your username and the option deadlines will automatically be substituted when you save the page. Update the bracketed variables with actual information, and be sure to replace the whole variable including the square brackets, so "[insert info here]" becomes "This is the inserted information" and not "[This is the inserted information]".

===[insert a title for your proposal here]===
[describe what issue this proposal is about and what changes you think should be made to improve how the wiki handles that issue]

'''Proposer''': {{User|{{subst:REVISIONUSER}}}}

====[option title (e.g. Option 1)]: [brief summary of option]====
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT

;Support
#{{User|{{subst:REVISIONUSER}}}} Per proposal.

;Oppose

====[option title (e.g. Option 2)]: [brief summary of option]====
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT

;Support
#{{User|{{subst:REVISIONUSER}}}} Per proposal.

;Oppose

====[option title (e.g. Option 3)]: [brief summary of option]====
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT

;Support
#{{User|{{subst:REVISIONUSER}}}} Per proposal.

;Oppose

====Comments ([brief proposal title])====

Talk page proposals

Proposals concerning a single page or a limited group of pages are held on the most relevant talk page regarding the matter. All of the above proposal rules also apply to talk page proposals. Place {{TPP}} under the section's heading, and once the proposal is over, replace the template with {{settled TPP}}. Proposals dealing with a large amount of splits, merges, or deletions across the wiki should still be held on this page.

All active talk page proposals must be listed below in chronological order (new proposals go at the bottom) using {{ongoing TPP}}. Include a brief description of the proposal while also mentioning any pages affected by it, a link to the talk page housing the discussion, and the deadline. If the proposal involves a page that is not yet made, use {{fake link}} to communicate its title in the description. Linking to pages not directly involved in the talk page proposal is not recommended, as it clutters the list with unnecessary links.

List of ongoing talk page proposals

• Remove information of Golf* for the Virtual Boy from Mario Golf (series) (discuss) Deadline: February 15, 2025, 23:59 GMT
• Move Kutlass to Kutlass (enemy) (discuss) Deadline: February 17, 2025, 23:59 GMT
• Resplit Birdo (species) (discuss) Deadline: February 18, 2025, 23:59 GMT
• Merge Jar (Mario Kart series) to Jar (discuss) Deadline: February 19, 2025, 23:59 GMT
• Merge Poochy Dash into Poochy & Yoshi's Woolly World and Poochy Hut (discuss) Deadline: February 19, 2025, 23:59 GMT
• Tighten Category:Power-ups and its subcategories (discuss) Deadline: February 20, 2025, 23:59 GMT
• Split Toad wearing headphones off from Jammin' Toad (discuss) Deadline: February 21, 2025, 23:59 GMT
• Split the 1337 HAMM3R BROZ. (discuss) Deadline: February 21, 2025, 23:59 GMT
• Split the modes in the Battle page (discuss) Deadline: February 22, 2025, 23:59 GMT
• Split Snifit or Whiffit: Seabed Edition from Snifit or Whiffit (discuss) Deadline: February 23, 2025, 23:59 GMT
• Figure out what to do with Category:Parasites (discuss) Deadline: February 24, 2025, 23:59 GMT
• Split the Monstro Town Mushroom from the normal Mushroom (discuss) Deadline: February 26, 2025, 23:59 GMT
• Merge Free-for-All Space with 4-Player Space (discuss) Deadline: February 26, 2025, 23:59 GMT

Unimplemented proposals

Proposals

Break alphabetical order in enemy lists to list enemy variants below their base form, EvieMaybe (ended May 21, 2024)

Standardize sectioning for Super Mario series game articles, Nintendo101 (ended July 3, 2024)

^ NOTE: Not yet integrated for the Super Mario Maker titles and Super Mario Run.

Create new sections for gallery pages to cover "unused/pre-release/prototype/etc." graphics separate from the ones that appear in the finalized games, Doc von Schmeltwick (ended September 2, 2024)

Add film and television ratings to Template:Ratings, TheUndescribableGhost (ended October 1, 2024)

Use the classic and classic link templates when discussing classic courses in Mario Kart Tour, YoYo (ended October 2, 2024)

Clarify coverage of the Super Smash Bros. series, Doc von Schmeltwick (ended October 17, 2024)

Remove all subpage and redirect links from all navigational templates, JanMisali (ended October 31, 2024)

Prioritize MESEN/NEStopia palette for NES sprites and screenshots, Doc von Schmeltwick (ended November 3, 2024)

Allow English names from closed captions, Koopa con Carne (ended November 12, 2024)

^ NOTE: A number of names coming from closed captions are listed here.

Split off the Mario Kart Tour template(s), MightyMario (ended November 24, 2024)

Split major RPG appearances of recurring locations, EvieMaybe (ended December 16, 2024)

Organize "List of implied" articles, EvieMaybe (ended January 12, 2025)

Split Mario & Luigi badges and remaining accessories, Camwoodstock (ended February 1, 2025)

Merge Chef Torte and Apprentice (Torte), Camwoodstock (ended February 3, 2025)

Merge the Ancient Beanbean Civilizations to List of implied species, Camwoodstock (ended February 13, 2025)

Talk page proposals

Split all the clothing, Doc von Schmeltwick (ended September 12, 2021)

Split machine parts, Robo-Rabbit, and flag from Super Duel Mode, Doc von Schmeltwick (ended September 30, 2022)

Make bestiary list pages for the Minion Quest and Bowser Jr.'s Journey modes, Doc von Schmeltwick (ended January 11, 2024)

Allow separate articles for Diddy Kong Pilot (2003)'s subjects, Doc von Schmeltwick (ended August 3, 2024)

Create articles for specified special buildings in Super Mario Run, Salmancer (ended November 15, 2024)

Expand and rename List of characters by game to List of characters by first appearance, Hewer (ended November 20, 2024)

Merge False Character and Fighting Polygon/Wireframe/Alloy/Mii Teams into List of Super Smash Bros. series bosses, Doc von Schmeltwick (ended December 2, 2024)

Merge Wiggler Family to Dimble Wood, Camwoodstock (ended January 11, 2025)

Split the Ink Bomb, Camwoodstock (ended January 12, 2025)

Create a catch-all Poltergust article, Blinker (ended January 21, 2025)

Merge the two Clawing for More articles, Salmancer (ended January 27, 2025)

Merge Dangan Mario to Invincible Mario, PrincessPeachFan (ended January 30, 2025)

Give the Cluck-A-Pop Prizes articles, Camwoodstock (ended January 31, 2025)

Reverse the proposal to trim White Shy Guy, Waluigi Time (ended February 8, 2025)

Split Animal Crossing (game), Kaptain Skurvy (ended February 12, 2025)

Writing guidelines

None at the moment.

New features

None at the moment.

Removals

None at the moment.

Changes

Include italics for category page titles for media that normally uses it

Shouldn't category pages for media that uses italics (such as games, shows, movies, etc.) use italics for their category pages? I did start adding it to some pages already, but I thought it was worth proposing about it, possibly to make it policy. I feel like italics should be used though, as it is used everywhere else. For example, the page titled Category:Donkey Kong 64 should be Category:Donkey Kong 64.

Proposer: Kaptain Skurvy (talk)
Deadline: February 20, 2025, 23:59 GMT

Support

1. Kaptain Skurvy (talk) Per proposal.
2. Camwoodstock (talk) Wait, this isn't already policy??? We think this lack of parity speaks a lot to how neglected categories can be in some regards. While yes, the category description isn't really meant to be the main point, we don't think slightly slanted text is distracting from the actual list of articles in the category, and just because categories are more utility than text doesn't excuse the text that is there looking below the standard of a usual article for being "lesser".
3. Super Mario RPG (talk) Nothing wrong with having more consistency around the wiki.
4. GuntherBayBeee (talk) Per all.
5. Salmancer (talk) It is easier to figure out what the standards are from context alone when the standards are applied in every instance.

Oppose

1. Nintendo101 (talk) Categories are supposed to provide simple, direct, and utilitarian functions, not something to be read or presented to readers. I don't think italicizing them is necessary and would detract from their simplicity.
2. Sparks (talk) Per Nintendo101. It doesn't feel necessary.
3. OmegaRuby (talk) What is this supposed to change, exactly? Yes, it's in line with how pages about games are to have the subject italicized, but the change feels unneeded and especially arduous to implement for pretty much no reason. Per Nintendo101.
4. SolemnStormcloud (talk) Per all.
5. Rykitu (talk) Per Nintendo101

Comments

@Nintendo101: In that case, why do we italicise game titles in category descriptions? (Genuine question, I'm undecided on this proposal.) Hewer (talk · contributions · edit count) 08:58, February 7, 2025 (EST)

Because that is a proper sentence. It is not the tool itself. - Nintendo101 (talk) 20:15, February 7, 2025 (EST)

We mean... Wiki policy is to italicize game titles on their articles' names using {{Italic title}}, too, and those aren't proper sentences. They're article names. ~Camwoodstock (talk) 19:00, February 8, 2025 (EST)

That's not the same situation in my eyes because the articles are what the site is for. That is what we are writing and presenting to the public. Of course we would italicize those. The categories are a tool, chiefly for site editors, not readers. We do not really gain anything from italicizing their titles. If anything, I worry this would lead to a lot of work to implement, either burdening site editors, porplemontage, or both. - Nintendo101 (talk) 16:05, February 9, 2025 (EST)

So category names are just tools not meant for readers, but category descriptions aren't? Hewer (talk · contributions · edit count) 18:08, February 9, 2025 (EST)

The descriptions are just sentences, and I feel inclined to render those they way we would a sentence anywhere else on the site, be it on articles or in the description for image files. - Nintendo101 (talk) 19:49, February 9, 2025 (EST)

We disagree with the notion categories are more for editors and not readers; while yes, all of the categories on the front page are maintenance categories from the to-do list, the sheer quantity of proposals for categories wouldn't make sense if they were moreso for editors, rather than your average reader; moves such as the reforms for the Look-alikes categories or the Thieves category wouldn't make sense if these weren't meant to be public-facing. And of course, there are the various categories that exist for users, but do not serve a utility purpose, such as the various "users that know a given language" categories.
As for difficulty implementing, considering the recent success stories with images without descriptions and categories without descriptions having gone from 4000+ and ≈100, to 0 and 0 respectively, we have it in good faith that this wouldn't be that hard to implement. Monotonous? Yes. But difficult? It's nothing a bit of caffeine and music can't solve. ~Camwoodstock (talk) 18:22, February 9, 2025 (EST)

Not only for editors, but chiefly for them. I don't exclude the idea of more curious readers utilizing them, but I suspect they are exceptions. I maintain that their ease of implementation is more important to the site than the formatting inconsistency. Like, are we to be expected to format category ourselves as "[[Category:Super Mario World screenshots|Category:''Super Mario World'' screenshots]]" instead of just "[[Category:Super Mario World screenshots]]" going forward? Would we do this for the articles that are in dozens of categories? Why? I would not want to do that, and I don't find the inconsistency a good enough reason to roll something like that out, and only brings downsides. It makes the tool where one types "[[Category:" almost entirely moot because we would still need to write out the whole name just to format it this way. Others are welcomed to think differently, but I personally think the way we format these names now in categories is perfectly fine. - Nintendo101 (talk) 19:49, February 9, 2025 (EST)

even if this proposal doesn't pass, i think we should use Template:Italic title in the category pages. — eviemaybe (talk / contributions) 10:16, February 12, 2025 (EST)

I thought that was the whole proposal. Hewer (talk · contributions · edit count) 03:32, February 13, 2025 (EST)

Split the image quality category

Issue 1: Category:Images to be reuploaded with higher quality is a very big category, with nearly 4,000 images in it right now. Even if it's something you can help with, it's very difficult to actually find anything in here. Issue 2: All other things being equal, some types of images require specific methods or skills to get that all users may not have or be comfortable with. To aid in the overall usability of this category and make it easier for skilled users to find things they can help with, I'm proposing the following two subcategories:

• Screenshots to be uploaded with higher quality - Most Nintendo consoles don't have the ability to take native screenshots. That's all I'll say about that.
• Assets to be uploaded with higher quality - Sites like The Spriters Resource are helpful, but they don't have everything. Getting higher quality images requires being able to extract them from the game files and/or the ability to manipulate them afterwards. This will also include images that are currently screenshots meant to demonstrate an asset, such as File:DKCTF Donkey Icon.png.

Additionally, Template:Image-quality will be modified with an extra parameter to mark the image as a screenshot or asset and categorize them appropriately. Considering we already have the rewrite and stub categories organized for better navigation, I don't see this as an issue.

Proposer: Waluigi Time (talk)
Deadline: February 20, 2025, 23:59 GMT

Split both

1. Waluigi Time (talk) Category:Votes to be reuploaded with a better reason
2. Technetium (talk) Per proposal.
3. Camwoodstock (talk) We're a little surprised a split like this hasn't happened sooner, honestly; if for no other reason than it would be nice to have it organized. Per proposal.
4. ThePowerPlayer (talk) Per proposal.
5. Nintendo101 (talk) Per proposal.
6. LadySophie17 (talk) Per all, which is mostly "per proposal"s anyway
7. EvieMaybe (talk) makes perfect sense

Comments on image quality proposal

Silly question; will images that are of neither screenshots nor assets that have the image-quality tag, like scans, character art/renders, or merchandise, just remain as-is? There are already a few examples of those that are all presently tagged with image-quality, like so:

• 

  Scan of 3D render, colors are washed out.

• 

  Muddy scan of 2D illustration, and background cropped.

• 

  Photoshop upscaled 2D promo art.

• 

  Too small image of merchandise.

~Camwoodstock (talk) 15:30, February 6, 2025 (EST)

Yes, anything that doesn't fall into either of the two subcategories will stay in the main one for now. I suppose we can look into splitting it further down the road, but I singled these two out because of the higher barrier to entry and also that they seem to be the bulk of the category's contents right now. -- Too Bad! Waluigi Time! 15:37, February 6, 2025 (EST)

I think this category should also be split by the media that it appears in (e.g: Category:Game screenshots to be reuploaded with higher quality. Something similar should also be done for the Articles with unsourced foreign names category. Apikachu68 (talk) 19:50, February 6, 2025 (EST)

Almost all of the screenshots in the category right now are from games so I don't think it needs to be narrowed down further just yet. -- Too Bad! Waluigi Time! 20:09, February 6, 2025 (EST)

Change "(game)" identifier to "(arcade)" on the articles of Donkey Kong, Donkey Kong Jr. and Mario Bros.

I wouldn't consider "game" to be the best identifier for the arcade games Donkey Kong, Donkey Kong Jr. and Mario Bros. There's already a Game and Watch game that shares its title with each of the arcade games, but "Donkey Kong" is the name of various other games too! There's the tabletop game, the Game Boy game, the Nelsonic Game Watch game and the slot machine. I know the slot machine is technically an arcade game, but it's not a standard cabinet like the 1981 arcade game. "Game" is a broad identifier, especially for Donkey Kong. Shouldn't a "game" identifier only be used if there's no other game with the same name? That's why we use consoles for identifiers instead, such as Mario & Sonic at the Olympic Games (Wii) and Mario & Sonic at the Olympic Games (Nintendo DS).

Proposer: Kaptain Skurvy (talk)
Deadline: February 22, 2025, 23:59 GMT

Support

1. Kaptain Skurvy (talk) Per proposal.

Oppose

1. Nintendo101 (talk) Those articles also cover the game's release on Famicom, NES, Atari, etc., so "arcade" would not be a holistically accurate identifier.
2. Camwoodstock (talk) Per Nintendo101; "arcade" is kind of a misnomer when the non-arcade ports are covered on them.
3. ThePowerPlayer (talk) Per Nintendo101.
4. PaperSplash (talk) Per ThePowerPlayer's comment.
5. Rykitu (talk) Per all

Comments

Maybe "arcade game" would be a decent compromise? PaperSplash (talk) 18:02, February 8, 2025 (EST)

What about Dr. Mario? That game also has a separate release also called Dr. Mario.--PopitTart (talk) 18:24, February 8, 2025 (EST)

The reason why the games Donkey Kong and Dr. Mario should keep their identifier of "(game)" is because those are by far the most popular and commonly thought-of games under their respective titles; the other articles (aside from Donkey Kong on the Game Boy) are on much more obscure devices while being clearly separate from the original game. To put it another way, "Dr. Mario (game)" is what people are looking for when they think about "the game featuring Dr. Mario"; meanwhile, you'd be forgiven for not knowing that the Gamewatch Boy game even exists at all. ThePowerPlayer 22:15, February 8, 2025 (EST)

what about Donkey Kong (1981)? — eviemaybe (talk / contributions) 18:39, February 9, 2025 (EST)

That would work for Donkey Kong, but the original Mario Bros. and the arcade game of the same title were both released in 1983. jan Misali (talk · contributions) 12:49, February 12, 2025 (EST)

Standardize the use of "English", "English (United States)" and/or "English (United Kingdom)" as languages in game infoboxes

So far, the use of "English (United States)" and "English (United Kingdom)" as language identifiers in game infoboxes on this wiki has been rather inconsistent and arbitrary, to say the least. While Nintendo is typically known for providing distinct English localizations for the United States (and other English-speaking territories in the Americas) and the United Kingdom (and other territories where Commonwealth English is standard, apart from Canada), the actual differences between them, if any, have varied over time.

Historically, many Nintendo games have featured minor English text differences between their releases in the Americas and Europe/Oceania; however, these were typically not wholly separate localizations to account for the differences between American and British (or Commonwealth) English – they tended to follow American English conventions for the most part regardless. Rather, they were simple amendments made by Nintendo of Europe to Nintendo of America's existing English scripts, usually either to rectify perceived shortcomings or to modify certain terminology based on internal preferences. These versions were typically stored separately on region-specific cartridges or discs, with occasional differences in how they were labeled in internal data.

Later, during the DS, Wii, 3DS and Wii U eras, more distinct localizations specifically for the United States and United Kingdom that also accounted for regional language differences became more commonplace. However, all of the aforementioned practices have largely faded with the advent of the region-free Nintendo Switch, where games now typically release simultaneously worldwide on identical cartridges. As a result, English scripts are now more often than not also identical across regions (or at most contain only very minor differences, such as the date format used; in many cases, the date format is the only difference), though they are still almost always stored and labeled separately in internal data, typically alongside each other.

This proposal aims to determine how we should handle cases of identical or nearly identical (American) English scripts between regions when identifying languages in game infoboxes. Should we list them both as "English (United States)", simply as "English" or adhere to how they are distinguished in internal data, even when actual differences are minimal?

Proposer: PaperSplash (talk)
Deadline: February 23, 2025, 23:59 GMT

Option 1: List largely identical American English localizations only as "English (United States)"

1. PaperSplash (talk) My third choice. I mean, when it really is just American English, I can see the argument.

Option 2: List largely identical American English localizations as simply "English"

1. PaperSplash (talk) My first choice. I think it's the best compromise that makes the most sense, all things considered.
2. Hewer (talk) I feel like this way is the most straightforward and accurate.
3. CarlosYoshiBoi (talk) I mean, if it’s just the same thing and no changes (assuming it doesn’t include dates for save files), then I guess this one makes the most sense.
4. Camwoodstock (talk) Primary option. It's the simplest, it seems reasonable enough, and is applicable across the board; while it isn't exactly in-line with how Nintendo is handling things as of the Switch era, it's reasonable enough and can easily account for pre-Switch cases very well.
5. Jdtendo (talk) Per all. Especially if that means that we will stop using "English (United States)" for games that use a variety of English that is not specifically American and weren't even released in America such as SMBTLL or Mario & Wario.

Option 3: List both "English (United States)" and "English (United Kingdom)" if distinguished in internal data, otherwise simply list "English"

1. PaperSplash (talk) My second choice. When internal data classifies them that way, it could make sense to follow suit...
2. Camwoodstock (talk) Secondary choice, as this seems to be Nintendo's official methodology as of the Switch; however, this exact rationale doesn't account for situations like, say, Mario Party 8 and its infamous recall in the UK, which predates Nintendo's official distinguishing of NA English and UK English from the Switch era, leaving us at a bit of a loss for how to handle it exactly.
3. CarlosYoshiBoi (talk) This option could also work if date formatting is different despite the game itself using the same script for the US and UK/Australia, like Mario & Luigi: Brothership.

Option 4: Do nothing

1. CarlosYoshiBoi (talk) I’m actually surprised no one put anything in this option kind of like the title mentions “Do nothing.”

Comments

For better accuracy, "British English" should probably be "Commonwealth English." Doc von Schmeltwick (talk) 22:13, February 8, 2025 (EST)

Noted. Though I decided to focus mainly on the terminology used in game infoboxes, as I realized this wiki's use of the term "British English" is effectively its own can of worms... PaperSplash (talk) 15:35, February 9, 2025 (EST)

I'm a bit confused what this proposal is trying to change. Is it just about terminology used in game infoboxes? Hewer (talk · contributions · edit count) 11:31, February 9, 2025 (EST)

In hindsight, I realized this proposal was trying to change too many things at once, so I decided to tidy things up and focus on just the game infobox terminology for now. PaperSplash (talk) 15:35, February 9, 2025 (EST)

Realistically even though Canadian English does use British/Commonwealth spelling most of the time, they just get US English spelling in games as Nintendo groups Canada with North America and their English is pretty similar to English in the US, so Nintendo products in Canada are just the same as in the US.

In this case why don’t we also just group American English and Canadian English into one and call it "North American English" even if it’s moreso mainly American English? CarlosYoshiBoi (talk) 10:45, February 11, 2025 (PST)

I'm not quite sure exactly what point you're trying to make here, but per the documentation for the "languages" template, the reason they're labeled the way they currently are in game infoboxes is because they're the primary markets American English and British/Commonwealth English localizations are made for. And for what it's worth, whenever Nintendo specifically labels "North American English" as a selectable language whether in-game or in internal data, they usually refer to the United States or US specifically, not North America/NA as a whole. PaperSplash (talk) 16:27, February 11, 2025 (EST)

I think I’m going with the fact that the English (United States) language for Nintendo is also intended for Canada (and it’s also applied onto the "Japan" and "Hong Kong/Taiwan/South Korea" regions on the Switch) despite just using American English. Kinda like with European French where although it’s just moreso referring to Standard French/French from France, it’s intended for all French-speaking regions in Europe (France, Belgium and Switzerland). CarlosYoshiBoi (talk) 14:58, February 11, 2025 (PST)

If Nintendo is also still adding English (United Kingdom) for their games despite there being almost no differences from the North American English versions aside from date or other words if needed, why do they keep American spelling? Wouldn’t it make more sense for British English spelling to be used even if it’s one of the only differences between English (United States) and English (United Kingdom)? CarlosYoshiBoi (talk) 22:00, February 12, 2025 (PST)

Less work for something ultimately unimportant, I guess? It's not like American spelling is unintelligible to non-Americans. Anyway, what does this have to do with the proposal? Hewer (talk · contributions · edit count) 03:39, February 13, 2025 (EST)

Just came up to me somehow on the topic of American English and British English. Not as big of a problem anyways but just hit me. CarlosYoshiBoi (talk) 7:37, February 12, 2025 (PST)

I don't work for Nintendo nor do I know anyone personally who does, so I can't exactly say for sure. But my best guess is that they simply don't feel like they need to anymore. The main problem with Nintendo not having separate US and UK English localizations before was that certain words considered offensive in the UK but not the US would show up in Nintendo of America's localizations that were also going to be largely reused in Europe, as seen with Mario Party 8 and Super Paper Mario. But now such words appear to get caught and edited out during Nintendo of America's initial English localization pass, like "welcher" in Mario & Luigi: Superstar Saga + Bowser's Minions, "bugger" in Super Mario RPG and "bummer" in Paper Mario: The Thousand-Year Door. Also, it seems that ever since at least Paper Mario: Color Splash or so, Nintendo of America and Nintendo of Europe have been working together more closely on English localizations from the start, as a couple English localization staff at NoE are now often also credited on NoA localizations and vice versa. With any potentially problematic words (regionally or otherwise) now seemingly being addressed much earlier on, there's no longer a really good reason they need to otherwise address differences between American English and British English during the localization process that would justify the extra time, effort and pay. While I'm sure it was appreciated by some, as Hewer mentioned, most people in the UK are used to reading and hearing US English and can understand it just fine (and the same goes vice versa to a lesser extent). It's not like Spanish where many Latin Americans genuinely struggle with understanding Spaniard slang and sometimes vice versa. As for why they still store UK or “EU” English scripts separately from the US ones in internal data despite being them being almost or outright entirely identical now, I think part of that is a remnant of the previous generation where more distinct localizations stored in folders labeled by both region and language was the standard (and it makes it easier for them to port over the more distinct localizations from older games whenever they bother doing so, like Mario Kart 8's for Mario Kart 8 Deluxe). But I think the other reason is to make it easy just in case something actually still needs changing between regions, most commonly the aforementioned date formats. Because that can be legitimately confusing, since they would essentially be backwards otherwise by the other region’s standards. PaperSplash (talk) 19:56, February 14, 2025 (EST)

Make Dark Mode available to everyone

Based on the vote so far, this proposal may be eligible to close one week early. Please use {{proposal check|early=yes}} on February 20 at 23:59 GMT and close the proposal if applicable.

Dark Mode is available to users with an account under preferences but it should be a toggle-able option for all users, even if they're not an editor. Wikipedia allows everyone regardless of role to toggle Dark Mode, so I don't see why this wiki shouldn't follow suit.

Proposer: Pizza Master (talk)
Deadline: February 27, 2025, 23:59 GMT

Support

1. Pizza Master (talk) per.
2. Nintendo101 (talk) nice idea, though I would prefer if Light Mode was called "Ground Mode" and Dark Mode was called "Underground Mode" for our site.
3. Camwoodstock (talk) Wait, theme changes are unavailable to users not logged in? Just, at all? It's not just dark mode, it's any theme, since it's all on Preferences. This feels like something that, if it's possible, it shouldn't even be a proposal, it should just be added outright without vote. This is a very obvious quality-of-life change for users that don't happen to be logged in.
4. Mushroom Head (talk)Why do we still need to create an account just to not torture your eyes when we use this wiki at night? It literally has zero effect to the users who are always logged in anyways.
5. Rykitu (talk) Per all
6. ThePowerPlayer (talk) The fact that this wiki has a Dark Mode and it still isn't available to everyone who uses the site is a crime.
7. PaperSplash (talk) Wikipedia does it and it serves as an accessibility feature for some people.
8. Arend (talk) Sounds like a good idea, and it seems feasible to implement...

Comments

My question is: is it possible to enable this feature for non-logged-in visitors? I'm asking this because Dark Mode is considered a "Gadget", and not a regular MediaWiki feature. They work with JavaScript though, so I suppose it could work in some way (given we have MediaWiki:Common.js and all), but I would still ask Porplemontage (talk) if a toggleable, easily accessible Dark Mode for everyone (including non-users) is possible, if I were you. rend (talk) (edits) 17:33, February 13, 2025 (EST)

I've asked Porple on his talk page, so we'll see when he answers. Pizza Master (talk) 17:40, February 13, 2025 (EST)

Porple's response on his talk page seems to imply that it might be possible. Pizza Master (talk)

Make about templates on New Super Mario Bros. U courses and New Super Luigi U courses link to each other instead of a disambiguation page, but keep the disambiguation page

"Where is that Star Coin in Jungle of the Giants? Oh, I’ll use Super Mario Wiki. Wait, I’m playing New Super Luigi U so it’s the counterpart Giant Swing-Along. How do I get from the Jungle’s page to Swing Along’s page? The about template should take me to… a disambig?"

What the hypothetical person above said. There’s only two courses with the code Soda Jungle-1, and since Nintendo does not reuse worlds in other games in the same role as worlds, the odds of there ever being a third Soda Jungle-1 are 0%. Given this is the case, if a user does go to a Mario U course when they meant a Luigi U course, having the about template point to a disambiguation page for a whopping two articles means the user has to click two times to reach the corresponding article for Luigi U. While this is a minor issue, there's a whole paragraph in MarioWiki:Naming dedicated to saving readers the clicks when searching for the most obvious topic of a group of topics that share a name. I think that philosophy should be extended to this curiosity.

We should carve out a special exception regarding the About template for this pair of games. About templates for levels from New Super Mario Bros. U and New Super Luigi U simply link to the other article, even though the articles in question do not share a name. The disambiguation page remains, because neither Soda Jungle-1 is more prominent than the other. (It also matches the relationship between Donkey Kong Country levels to Donkey Kong Land levels) As a result, this:

• "This article is about Jungle of the Giants, a level in New Super Mario Bros. U. For other uses, see Soda Jungle-1."

becomes this:

• "This article is about Jungle of the Giants, a level in New Super Mario Bros. U. For its New Super Luigi U counterpart, see Giant Swing-Along."

And so on and so forth for all... 90 or so courses.

Proposer: Salmancer (talk)
Deadline: February 28, 2025, 23:59 GMT

Support: Link the corresponding courses together with the about template

1. Salmancer (talk) I only have 100 seconds to beat the Luigi courses, for the love of hammers save me the click when I put in a Mario course by accident!
2. ThePowerPlayer (talk) If there are two and only two levels that correspond to the same world name and level number (e.g. "Soda Jungle-1"), then one should just immediately link to the other, just like pages that use the {{distinguish}} template such as Slug and Vine Slime. Seeing the disambiguation page should only be necessary if someone thinks to visit "Soda Jungle-1" first without remembering the level's exact name.
3. EvieMaybe (talk) one of those changes so obvious you question why they weren't done that way in the first place. per proposal!
4. Rykitu (talk) Per all
5. Ahemtoday (talk) Very sensible change to make.

Comments (Use {{about}} to cross-link Mario/Luigi U courses)

I know I'm on about swapping from "level" to "course". That's for another day, which is why the example doesn't change the word choice. Salmancer (talk) 18:54, February 14, 2025 (EST)

Miscellaneous

None at the moment.