MarioWiki:Proposals

Current time: Monday, March 10th, 10:35 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 essentially its own mini-proposal with a deadline and Support/Oppose subheadings. The rules above apply to each option as if it were a its a 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 the status quo 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])====

A poll proposal is archived after all of its options have settled, and it is listed as one single proposal in the archive. The proposal is considered to have "passed" if one or more options were approved by voters (resulting in a change from the status quo), and it is considered to have "failed" if all options were rejected by voters and no change in the status quo was made.

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

• Split Ossan from Captain Rainbow (discuss) Deadline: March 12, 2025, 23:59 GMT
• Split Super Mario Maker helmets from Buzzy Shell and Spiny Shell (red) (discuss) Deadline: March 12, 2025, 23:59 GMT
• Increase the maximum amount of personal images to 10 per user (discuss) Deadline: March 12, 2025, 23:59 GMT
• Consider the POW Block item in Mario + Rabbids Sparks of Hope to be a Red POW Block (discuss) Deadline: March 12, 2025, 23:59 GMT
• Properly define Brown Yoshi (discuss) Deadline: March 13, 2025, 23:59 GMT
• Split the Giant Mushroom/Refreshroom from BIS that is merged with the normal Mushroom into its own article (discuss) Deadline: March 13, 2025, 23:59 GMT
• Determine what memes should be on the Internet references page (discuss) Deadline: March 15, 2025, 23:59 GMT
• Move the Adobe Flash version of Donkey Konga 2 to the "Windows" section of the list of games page (discuss) Deadline: March 15, 2025, 23:59 GMT
• Split rejected pitches and titles that never began development on the list of unreleased media into a list of proposed media (discuss) Deadline: March 16, 2025, 23:59 GMT
• Remove information on Super Mario Maker series big Para-Beetles from Heavy Para-Beetle (discuss) Deadline: March 18, 2025, 23:59 GMT
• New subsections for games in the Super Mario series (discuss) Deadline: March 18, 2025, 23:59 GMT
• Split Sal Out (WarioWare: Touched!) from Sal Out (discuss) Deadline: March 19, 2025, 23:59 GMT
• Split Space Mine from Mikey Mine (discuss) Deadline: March 19, 2025, 23:59 GMT
• Split Small Cosmic Clone from Cosmic Clone (discuss) Deadline: March 22, 2025, 23:59 GMT
• Create an article for the cat enemies in Bowser's Fury (discuss) Deadline: March 22, 2025, 23:59 GMT
• Split the enemy/obstacle ice block of Yoshi's Woolly World from Ice Block (discuss) Deadline: March 22, 2025, 23:59 GMT
• Split the Sleepy Sheep Mistake from the "normal" Mistake (discuss) Deadline: March 23, 2025, 23:59 GMT
• Split Toad (Mario Party 4) from Toad (discuss) Deadline: March 23, 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)

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)

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

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

Merge intro/outro sections, rename Gameplay section to "Overview" for Mario Party minigame articles, ToxBoxity64 (ended March 1, 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)

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)

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)

Split the modes in the Battles page, Mario (ended February 15, 2025)

Count ongoing serialized comics for latest appearances, Rykitu (ended March 2, 2025)

Split Toad wearing headphones off from Jammin' Toad, PrincessPeachFan (ended March 7, 2025)

Writing guidelines

None at the moment.

New features

Establish a format for poll proposals on the archive lists

Something that's slipped through the cracks when we invented poll proposals was what we do when we add them to these pages. We can't simply have one link to the poll proposal — the entire purpose of the format is that different parts of it can pass and fail independently of one another. What color do we put a proposal where one thing fails and another thing succeeds in?

I have several pitches for you.

OPTION ZERO
Do nothing. I'm putting this at the front because I want to leave room for any good-sounding solutions beyond the four I'm about to suggest. It's here on the proposal at all because I'm pretty sure I'm legally obligated to put it here, but I'll be honest — I'm not entirely sure what this winning would... mean. Our hand will eventually be forced when our first poll proposal fully resolves, so a format will be established one way or the other.

EDIT: It has been helpfully pointed out that there is a current policy — they are red if they all issues fail, gray if at least one passes and is unimplemented, and green if at least one passes and all issues are implemented. A "one issue changes the color" kind of rule. It's definitely not insensible, but I feel that we could be conveying more information. Still, even if this if the "fail option", we have a policy now, so I got what I wanted even if this one wins.

OPTION ONE
The different issues of a poll proposal share a number corresponding to when the first issue closes. They're listed separately, and distinguished from each other via letters. As an example, the three parts of the Brown Yoshi proposal would slot in at #83A, #83B, and #83C. (That would shove some other proposals down; we could also just append them to the end of the list like normal and brush off the inconsistency if y'all prefer.)

The Brown Yoshi proposal is also a handy demonstration of an edge case we have to contend with — if this proposal passed right now, we would list #83A as red and #83B as gray, but what would happen with #83C, which is still ongoing? This is the aspect on which Options One and Two differ. In Option One, issues are not added to the archive page until they close. The page would only contain #83A and #83B if the proposal passed right now, with #83C being added later

I would like to note that the Brown Yoshi proposal is a remarkably well-behaved example. If the issues were ordered differently, we may at one point have #83A and #83C on the list with no #83B until later.

OPTION TWO
Option Two is identical to Option One except in how it handles open issues on partially closed poll proposals. In this option, they are added to the list alongside the other issues, and marked with a new color — let's say black.

This prevents the awkward gaps we would be susceptible to in Option One, but it is introducing a whole color for a temporary edge case.

OPTION THREE
Option Three is simpler. We create a new color in the archive for poll proposals — I guess let's say black again. Poll proposals get added to the archive when all issues on them are closed.

This saves space (the other options will have to give fourteen entries to this proposal, but it means the entry on the list doesn't reflect anything about any individual issue's status, such as whether it's been implemented or not.

EDIT: Camwoodstock's pitch below of using three colors (and, implicitly, adding the poll proposal to the archive when it has any closed issues) doesn't entirely eliminate that negative, but it does seem much more useful than just having the one color.

OPTION FOUR
Option Four is simpler still. Each issue is treated as if it were an entirely separate proposal. Each gets numbered and appended to the list when it closes regardless of what anything else in the poll proposal is up to.

The negative of this way of doing it is that the issues of a poll proposal may end up strewn about the list in a way that doesn't really reflect that they're a related thing.

Proposer: Ahemtoday (talk)
Deadline: March 18, 2025, 23:59 GMT

Option Zero

1. Jdtendo (talk) Per Porple "Steve" Montage in the comments.
2. Waluigi Time (talk) Per Porple.
3. EvieMaybe (talk) perple montage
4. Camwoodstock (talk) Per Porple in the comments, though admittedly this is more of a secondary option to our more robust version of Option Three we pitched. Status quo isn't the worst thing in the world, and we do acknowledge our more robust solution of "dark colors" may be a bit harder to convey as we've been slowly rolling out... Well, a dark mode for the whole wiki. (If it was down to us, the poll proposals would use lighter colors in dark mode, before you ask; of course, if that option somehow wins, we'd be down to help fine-tune it.)
5. Arend (talk) Per Porple.
6. Nintendo101 (talk) Per porplemontage.

Option One

1. Ahemtoday (talk) It's either this or Option Two for me — it's important to me that the issues end up next to each other on the archive and that the status of each one is visible on the page.
2. Salmancer (talk) There's no rule saying a poll proposal has to be for small things, since part of the premise was reducing the need for large numbers of combination options. There could be poll proposals that have wide scopes, and as such I think we're going to have to stomach the poll proposals with 10+ proposals in them to make it easier to track policy without thumbing through old proposal pages. Also an archive is for the past, not the present.

Option Two

1. Ahemtoday (talk) See my note about Option One.
2. Camwoodstock (talk) Secondary option, but we do think darker shades of the colors (a-la our pitch for Option Three) would be nice. Helps distinguish at a glance what was a poll proposal.

Option Three

1. Camwoodstock (talk) We would like to pitch a more sophisticated variant of this; 3 new colors. One for a poll that has concluded, one for one that's partially ongoing, and one for a poll that has been partially overturned by a future proposal. Maybe dark green, dark gray/maybe a de-saturated dark green a-la the Shroom Spotlight template, and a dark yellow? The darker colors, of course, to contrast with the non-poll proposals. (On dark mode, we'd probably make these lighter, rather than darker, provided we actually even add dark mode compatibility to the proposal archive colors.)
2. Jdtendo (talk) Listing every single poll would probably take a lot of space whereas the whole purpose of a poll proposal is bringing together many similar polls that would be too cumbersome to handle separately. I would prefer having a single proposal listed as "Determine what memes should be on the Internet references page" that users can click on to check the detailed results rather than cluttering the list with a dozen links.
3. Rykitu (talk) Per all.
4. Ahemtoday (talk) I definitely see the appeal in having poll proposals under a singular listing, but I think they'd be better served by having one or multiple new colors rather than using the standard red and green.

Comments

@Camwoodstock — I definitely think your pitch for Option Three is better than the version I was suggesting. I'm not really sure about the pitch for Option Two, though — the letters already distinguish them, and I feel like they'd seem more like separate states rather than a "modifier" on some of the existing ones. Not to mention, wouldn't we need a darker version of every single color just in case? That's a lot of changes to make, and we'd end up running into problems with dark blue, teal, and dark teal; or "dark white", gray, and dark gray. Ahemtoday (talk) 03:20, March 4, 2025 (EST)

I don't quite understand option one and two, as the above rules for poll proposals state "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." --PopitTart (talk) 07:09, March 4, 2025 (EST)

Could you explain the contradiction in greater detail? I don't see what you mean. Ahemtoday (talk) 12:01, March 4, 2025 (EST)

The options say "The page would only contain #83A and #83B if the proposal passed right now, with #83C being added later" and "...how it handles open issues on partially closed poll proposals" there shouldn't be any instances of archiving partially closed poll proposals, they only close all at once when every entry has been resolved.--PopitTart (talk) 20:07, March 4, 2025 (EST)

So is your position that we should use the lettering scheme from Options One and Two, but only add poll proposals to the archive page when all of their issues are closed? I don't think I agree, but I can add that as Option Five if that's what you want to vote for. Ahemtoday (talk) 22:48, March 4, 2025 (EST)

I feel like this is fine. Either it's red (no change from the status quo so nothing needs to be done), gray (some change was established and there is work to do), or green (some change was established and it's all done). There are other proposals where people list several things to be done, it's not that different, it's just that now we have the ability to vote on each individual thing. But in either case you just click the link to read exactly what was approved. --Steve (talk) 10:56, March 7, 2025 (EST)

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 Extended to February 27, 2025, 23:59 GMT Extended to March 6, 2025, 23:59 GMT Extended to March 13, 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.
6. Hewer (talk) The proposer has confirmed on their talk page that the goal of the proposal is just to put Template:Italic title on category pages, so concerns about formatting the category links on articles are moot (and I'm not sure applying it there would even be possible anyway). With that cleared up, per all, I don't see the harm in some more consistency.
7. EvieMaybe (talk) per Hewer
8. Shy Guy on Wheels (talk) sure, for consistencies sake
9. LadySophie17 (talk) Per Hewer, then.
10. Scrooge200 (talk) Makes it way easier to tell what's part of the game title and what's part of the category descriptor or not at a glance.

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
6. Mushroom Head (talk) Per all
7. Technetium (talk) Per all.
8. Pseudo (talk) Per Nintendo101.
9. LinkTheLefty (talk) Pertendo101.
10. ThePowerPlayer (talk) Per Nintendo101.
11. wildgoosespeeder (talk) Totally unnecessary maintenance. Also, I don't think that it even works. I just tested it without the colon [[Category:Donkey Kong 64|Category:''Donkey Kong 64'']], unless you mean to use {{DISPLAYTITLE:Category:''Donkey Kong 64''}}, which does work on the category page.
12. Fun With Despair (talk) Not only does this seem like a massive pain in the ass for astoundingly little gain on either the user or backend side, but honestly it looks pretty ugly.
13. Arend (talk) I am aware that the proposer only meant to have the italics show up on a category itself with {{DISPLAYTITLE}}, but honestly, I think that would make things a bit too confusing or cumbersome. As wildgoodespeeder said, one is unable to force a category name to be displayed in italics when put on other pages (or displayed in other categories), so if you're unable or unwilling to have that match, then what's the point? Not only that, but pages in categories are already forced by the system to be displayed in italics when they're redirects (remember when we still had those Pokémon redirects in categories, and they were all displayed in italics?). I would honestly think that is going to confuse readers even further than if we just leave the game titles in categories without italics.

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)

@Kaptain Skurvy: Could you please clarify whether the proposal's goal is simply to add italic title to categories, or to also do something else as well? Hewer (talk · contributions · edit count) 20:14, February 17, 2025 (EST)

The proposer has clarified on their talk page that adding the italic title template to categories is all the proposal would do if it passed. Hewer (talk · contributions · edit count) 15:21, February 23, 2025 (EST)

Introducing the crossover article

The passing of this proposal would accomplish seven things:

1. See the publication of the drafted Zelda article discussed in this proposal, titled "crossovers with The Legend of Zelda." (The draft can be viewed here.)
2. Funnel redirects and disambiguation pages pertaining to Zelda on the wiki to the published Zelda article (i.e., searches for The Legend of Zelda, Octoroks, etc. Fully covered crossover subjects like Link would keep their articles, and this would not preclude a crossover subject from receiving an article of their own in the future if warranted, such as the inclusion of Princess Zelda in a future Mario Tennis or something like that).
3. Move details pertaining to Zelda from list articles on the site to this one (i.e. all information pertaining to Sheik on the list of fighters debuting in Super Smash Bros. Melee article would be cleared, and searching for "Sheik" on the site would bring you to this article. Zelda info on the list of references in Nintendo video games article would similarly be cleared. Visitors to that article would be directed towards the published Zelda one when they reach that section of the list article).
4. Establish a navbox for crossover articles (either a wholly dedicated one, an incorporation into "Template:Culture," or a retooling of "Template:Crossover characters").
5. Establish the precedent where this can be done for other IPs with which the Super Mario franchise has crossed-over.
6. Establish a 'Crossover article" section to the MarioWiki:Manual of Style that explains the framework for crossover articles described below. This is to be the standard structure for how other articles are to be structured.
7. Note that this framework exists on the the crossover section of our coverage policy, and provide a link directing readers to it.

The Super Mario franchise is very much the IP tentpole for Nintendo Co., Ltd. and at least one of the ones for the Japanese video game industry as a whole. Consequently, Super Mario as a franchise and brand has crossed-over with many other franchises, brands, and series over its nearly fifty years of existence - not only sister series developed by Nintendo EAD and R&D, and their successor EPD (i.e. Duck Hunt, Punch-Out!!, Exictebike, Metroid, F-ZERO, Animal Crossing, Pikmin, Splatoon, etc.) and those of their external creative partners (i.e. Ape Inc.'s EarthBound, HAL Laboratory's Kirby, Game Freak's Pokémon, etc.), but also fellow ones from other studios like Square Enix, Sega, Bandai Namco, Koei Tecmo, Chunsoft, Ubisoft, Konami, and Hudson Soft. This is not groundbreaking news: Most folks interested in gaming history already know this, especially the curators of the Super Mario Wiki. However, I do not feel like we handle this information particularly well on the site.

A lot of coverage of Super Mario references, homages, allusions, and cameos are nestled within various list articles, inexplicitly at the end of dedicated game articles, or in Super Smash Bros. articles with which there seemed to have been effort to bury on the site and are not wholly about Super Smash Bros. anyways. This coverage, exasperated by recent efforts to reduce coverage on the Super Smash Bros. series: (1.) obfuscates the fact that Super Mario has made references and is referenced in many other franchises outside of Smash Bros. contexts, often in very meaningful ways that are interesting and fun to read about; (2.) mitigates how Mario has been an influence behind some of these other franchises; and (3.) makes finding some bits of information just very difficult. If I, as a visitor of the site, wanted to understand scenarios where Splatoon and Mario have crossed-over, I would not have an easy way to find that all in one place, and I think that is a shame.

To better cover and consolidate crossover info on the site, and I have been drafting what I would like to call a "crossover article" using The Legend of Zelda franchise as an example (with contributions from Salmancer, DryBonesBandit, Memelord2020, RHG1951, LeftyGreenMario, and LadySophie17, and feedback from Super Mario RPG, Doc von Schmeltwick, and Koopa con Carne). This is a long article, and it is not wholly completed yet, but I think it is serviceable example of what I would like us to do going forward. Crossover articles take inspiration from the universe articles from our affiliate Smash Wiki and, as apparent in the Zelda draft, consist of the following sections:

• Overview : A brief description of what the crossover franchise/series is for those not well versed in the subject and would like to know a little more about it without visiting another site, and how this relates to Mario. It is the create a foundation so the reader is not confused by descriptions or terminology in the other areas of the article. For Zelda, this section may be a bit lengthier than it would be for others because Mario had a lot of direct influence on Zelda as a series.
• Recurring crossover subjects: for subjects like characters, enemies, bosses, or items that make substantial appearances in or alongside Mario-related media, such as subjects that used to have their own articles on the site. Each subject would be briefly explained so readers understand who they are when mentioned in other parts of the article, have explicit conceptual or design connections with Mario highlighted, and summarize areas where they specifically crossover with Mario.
• History in the Super Mario franchise: a history section for where the crossover subject is referenced in the Super Mario franchise itself.
• History in the subject series/franchise: a history section for the inverse, where Super Mario is referenced in the franchise subject of the article. In this case, it is Zelda.
• Shared history (if applicable): a history section for mutual space where both subjects appear, such as the Super Smash Bros. series, Tetris series, NES Remix series, or other media.

Zelda is uniquely related to Mario and nearly as old, but crossover articles can be written for smaller franchises/series as well. The only requirement for a series/franchise to receive an article of its own is for it to directly crossover with Super Mario within an officially licensed capacity. Articles of this nature should not be written for series/franchise that simply make homages to Super Mario or have elements inspired by it, such as Celeste, Gears of War, or Astro Bot.

I offer three options:

1. Support: I like the idea of crossover articles and want to see them implemented as described.
2. Support: I like the idea of crossover articles, but list articles for the Super Smash Bros. series should be left alone.
3. Oppose: I do not like the idea of the crossover article and do not want to see them implemented.

I know this was a long one, folks. Sorry about that, but the ideas behind this idea are multifaceted. Please let me know if you need additional clarity on anything or if you have any recommended amendments. (Also, if you would like, I welcome you to contribute to the drafted Zelda article! It is in my "community garden" sandbox for a reason.)

Proposer: Nintendo101 (talk)
Deadline: March 17, 2025, 23:59 GMT

Support: let's implement crossover articles!

1. Nintendo101 (talk)
2. Super Mario RPG (talk) Per proposer.
3. Koopa con Carne (talk) Per proposal with absolutely no second thought. Aside from the obvious value such articles would bring, this practice may incidentally just be the silver bullet for the community's differences on how to cover Smash Bros. content. Nintendo101, even with your inspiration from SmashWiki, I'd say you still managed to think out of the box here.
4. Waluigi Time (talk) Per all.
5. EvieMaybe (talk) been waiting a long time for this one. per proposal!
6. LadySophie17 (talk) Secondary choice, I suppose. Better than no article.
7. Camwoodstock (talk) Secondary option; we'd rather these articles exist, even if the Smash coverage is confusing, than these articles not exist at all.
8. PopitTart (talk) It has always felt absurd to me that Captain Olimar's presence on the wiki is entirely an entry in List of fighters debuting in Super Smash Bros. Brawl, despite being directly based on Mario himself and having appearances in Luigi's Mansion, WarioWare: D.I.Y., Super Mario Maker, Yoshi's Woolly World, Mario Kart 8, and WarioWare Move It!
9. Jdtendo (talk) Crossover articles are a great idea, and if it can also declutter Smash Bros. list articles, it's even better.
10. Arend (talk) As long as the content from the list pages are preserved in SOME way or another, I am perfectly fine with this. I think this is a great idea, and the well-detailed draft really sold me on this.
11. Nelsonic (talk) Makes perfect sense.
12. Kaptain Skurvy (talk) Sounds good to me.
13. Shy Guy on Wheels (talk) Per all. death to the smash bros lists
14. Mario (talk) Those list pages are a spaghetti of sadness, mama mia. I love the idea of these crossover pages, wonderful idea (similar to those decade splits for the gallery pages), and they're going to be a massive step up from that mess we currently have. I don't want to keep those lists at all. Their tolerated existence makes our wiki look bad, although absolutely delicious, if you ask me.

Support: let's implement crossover articles, but leave Smash Bros. lists alone

1. LadySophie17 (talk) Per proposal. I believe the articles would be better focused on the relationship between their respective series and Mario. Detailing all their character's Smash histories (which could get quite lengthy with something like Pokémon) would be better left in the List articles they currently are in.
2. Sparks (talk) Per Sophie.
3. Doc von Schmeltwick (talk) - Per Soph
4. Camwoodstock (talk) Primary option; per Sophie, we worry about the length of some Smash sections, and we feel the organization is fine enough as it is right now for Smash-related subjects.
5. Tails777 (talk) Per Sophie. I fully agree with making crossover articles to cover the relations another franchise has with Mario, but Smash in of itself is also a crossover and covering the details of these characters in a place that relates to Smash feels better.
6. Arend (talk) Second option. I'm personally not a huge fan of loss of content, and this option allows this to be fully preserved by leaving it be. While I have been assured that the history sections will be preserved in a form better suited for the article and other details such as Classic Mode routes and stickers/trophies/spirits might be reimplemented, I'm still keeping this as a secondary option to be safe.
7. Okapii (talk) Per Sophie.
8. Nelsonic (talk) Second opinion.
9. LinkTheLefty (talk) This proposal is pretty close to how I imagined covering Zelda subjects had Link's Awakening failed!
10. Killer Moth (talk) Per all.

Crossover comments

I also happened to start a draft for a Pikmin series article the other day, inspired by Nintendo101's Zelda draft. It's in a much... much rougher state, but I hope it gives an idea what these crossover articles can provide.--PopitTart (talk) 19:31, March 3, 2025 (EST)

@Koopa con Carne thank you for the kind words! - Nintendo101 (talk) 20:30, March 3, 2025 (EST)

-- KOOPA CON CARNE 11:32, March 4, 2025 (EST)

Question: One of the proposed points is to "Move details pertaining to Zelda from list articles on the site to this one", but the i.e. states that "all information pertaining to Sheik on the list of fighters debuting in Super Smash Bros. Melee article would be cleared". Characters on these fighter lists have extensive history sections; will these be moved to the crossover pages as well, or will these be nixed altogether?
Also, what about franchises which currently only have a connection with Mario through Smash Bros., such as ARMS? Will these get a crossover article as well or not? rend (talk) (edits) 12:10, March 4, 2025 (EST)

I don't know. Perhaps we'll cross that bridge when we get there. Ultimately, very few of the franchises within Smash Bros. have only crossed-over with Mario within Smash Bros., and that was at the front of my mind for this proposal. ARMS is one of the few exceptions. I should probably make some sort of list to parse what other series and franchises are within that boat. But what would you want to see, @Arend? - Nintendo101 (talk) 15:52, March 4, 2025 (EST)

I don't know... I'd understand not giving those an article given how they only crossover in Smash, but it would be strange to do with ARMS considering it's probably the only franchise with such a distinction that is directly from Nintendo. I can see us making an exception and allowing a crossover article for ARMS regardless, considering how most of the ARMS development team is basically Mario Kart 8 alumni anyway, but that same excuse probably wouldn't work with Kingdom Hearts. Then again, maybe so few franchises would be left that we might as well make crossover pages for those anyway.
Anyway @Nintendo101, you didn't answer my first question regarding the fighters' history sections on the fighter lists, so I ask again: would they be moved to the crossover pages as well, or be deleted altogether and not being covered at all? Knowing precisely what's going to happen to those (as the proposal hasn't really elaborated well on what will happen to those) is pivotal for me to pick which option to choose for, you see. That's kind of why I haven't voted yet. rend (talk) (edits) 20:07, March 4, 2025 (EST)

I personally envisioned the history sections for each fighter being disseminated within history sections as described in this proposal (one section for Mario, one section for the other franchise, and one section for mutual space where both franchises crossover together). Individual characters would not have the full history sections as present in those list articles, but the individual info would largely be preserved. (I did not think it was important to reiterate granular Smash Bros. info about Stickers, Trophies, Classic Mode routes, etc. because that seemed more about Zelda in Smash Bros. and less about Zelda with Mario in Smash Bros., but Hewer had reservations on that info being discarded, so maybe that can be reincorporated. But everything else, especially info outside of Smash Bros., would be retained.) For example, in my Zelda draft, Ganon is described under the "recurring crossover subject" section, and Ganondorf is mentioned in the relevant sections below where he shows up, like Super Mario Maker, Mario Artist: Paint Studio, Yoshi's Woolly World, and the Super Smash Bros. series. That info is just being presented alongside other relevant Zelda info in those games and others, and I suspect that is the type of info someone searching for "Ganondorf" on the Super Mario Wiki would be interested in. How does that sound? What do you think of the draft? - Nintendo101 (talk) 21:16, March 4, 2025 (EST)

I suppose that works. So long as the content on the original pages is preserved (one way or another), I'm perfectly fine with this. Also, I think the draft looks amazing so far. There are a couple things missing of course (it is a draft, after all), but what is there is very well-detailed. rend (talk) (edits) 06:16, March 5, 2025 (EST)

So is the ultimate plan for these to effectively be a replacement for the Smash list pages? I imagine the lists would start looking a bit barren if things on them get moved to crossover franchise articles. Hewer (talk · contributions · edit count) 16:07, March 4, 2025 (EST)

I am admittedly not a fan of the fighter list articles on the wiki and I think the information on them would be better served in articles more directly focused on the Super Mario franchise, both for readers and editors. However, I respect the will of those who would rather we keep those articles around. I am not sure if you looked at my Zelda draft, but it does omit more granular information specific to the Super Smash Bros. series, like stickers, trophies, Classic Mode routes, special moves, or NIOLs for individual characters. I would rather this article emphasize how Zelda engages with Mario in other contexts. If folks would rather Super Mario Wiki continue to hold onto the more granular Smash Bros. info on the fighter list articles, they could be retained for those purposes, I imagine. - Nintendo101 (talk) 16:47, March 4, 2025 (EST)

Well, there are two voting options for people who want both. Super Mario RPG (talk) 16:52, March 4, 2025 (EST)

I find Classic Mode routes in particular a bit odd to remove since they often involve Mario characters/stages/etc. (and I guess a similar argument could possibly be made for stickers), but I understand for the stuff with no particular Mario relevance.
Another thing I just thought of: we already have Pushmo (series) and Just Dance (series) as guest appearances, and this proposal passed to make a page for the Animal Crossing series (technically the proposal was just to make a page on the game, but every single voter agreed to do a series page instead). Would this proposal affect these pages? Hewer (talk · contributions · edit count) 18:44, March 4, 2025 (EST)

I had touched base with some of the users involved in those proposals. I do personally think it would make sense for all of these articles to have similar structure to one another - I think that uniformity would make them easier for readers to jump between them and find what they are looking for. However, maybe @Kaptain Skurvy, @Nelsonic, and @Mushzoom can provide their two cents. Would you want the Pushmo, Just Dance, and Animal Crossing articles be grandfathered into this proposal? It would just provide some structural guidelines and inform how redirects and disambiguation pages relevant to these series would be handled on the wiki. - Nintendo101 (talk) 20:01, March 4, 2025 (EST)

Yeah, it would make sense to apply this to those articles for consistency (and Pushmo technically crosses over in Smash as well, as a spirit). So a list of franchises to split could look something like:
Major non-Smash crossovers ("major" meaning "would take more than a couple of sentences to fully explain"): The Legend of Zelda, Animal Crossing, Splatoon, Sonic the Hedgehog, F-Zero, Dragon Quest, Final Fantasy, Pikmin, Punch-Out!!, Rhythm Heaven, Kirby, Metroid, Excitebike, Pushmo, Just Dance, EarthBound, Kid Icarus, Mega Man, Pac-Man, Banjo-Kazooie, maybe Star Fox, maybe Duck Hunt, maybe Balloon Fight, maybe Clu Clu Land, maybe Fire Emblem, maybe Street Fighter, maybe Ice Climber, maybe Bayonetta?, not sure if "Game & Watch" really counts as a franchise, Minecraft technically counts but would probably be redundant to split
Minor non-Smash crossovers and/or appearances only as amiibo costumes: Pokémon, Wii Fit, Xenoblade Chronicles
Minor non-Smash crossovers: Metal Gear, Castlevania, Tekken
No non-Smash crossovers: Persona, Fatal Fury, ARMS, Kingdom Hearts
I probably missed something. I'm assuming that franchises whose only crossover is non-fighter representation in Smash (like a stage or Assist Trophy or something) don't count. Hewer (talk · contributions · edit count) 05:29, March 5, 2025 (EST)

Forgot about The Legendary Starfy, that would qualify. There's also I Choose You! from Mario Maker, which might barely push Pokémon up to "major". Hewer (talk · contributions · edit count) 07:13, March 5, 2025 (EST)

@Nintendo101 Yes. This makes perfect sense, and the grandfathering approach would allow these series to get more mainstream attention, which is never a bad thing. New series with a significant amount of Super Mario content would also likely be considered for a crossover article as opposed to being relegated to the list of references in Nintendo video games or the list of references in third-party video games. Being placed on said lists works for games with small amounts of Super Mario content (i.e. Drill Dozer or Borderlands 2), but doesn't for games with larger amounts of Super Mario content (i.e. Punch-Out!! or Mobile Golf). Nelsonic (talk) 11:31, March 5, 2025 (EST)

This is probably a separate proposal, but should the Link's Awakening article be outright merged with the new crossover one? LinkTheLefty (talk) 07:14, March 6, 2025 (EST)

Not an invalid idea, but I agree that is better the focus of a future proposal. This one does not address non-list articles. - Nintendo101 (talk) 20:35, March 7, 2025 (EST)

Color-code game, series and franchise infoboxes to match their navigation template colors

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

The color coding used in navigation templates could be used for more cases outside navigation templates. Since the wiki covers all the distinct branches of the Mario franchise (which are numerous), using those theme colors more often to sectionalize and identify them may make things easier to navigate through in some cases. While I don't think there are cases where this would have a high impact right now, we could apply them to the game, series and franchise infoboxes, where they are fitting.

As it currently stands, the light red color of the game infobox specifically implies "Mario" to me at least, while the purple color of the series and franchise templates I suppose is arbitrary. This change would make it possibly more intuitive from a glance at the top of the article to which Mario branch the article belongs. It would also establish a common element to the introduction of articles belonging to the same set, while also establishing a color consistency between the very top and the very bottom of the article.

As for the colors themselves, I imagine something like:

• infobox background: the navigation template's lighter background (e.g. #FFF5EE for Mario);
• darker cell background: the navigation template's darker background color (e.g. bisque for Mario);
• header: the navigation template's header color (e.g. #CC0000 for miscellaneous Mario, #FF2400 for Super Mario);
• border: #aac, #aca, #acc, #caa, #cac or #cca, depending on the most closely matching color.

Proposer: Bro Hammer (talk)
Deadline: March 17, 2025, 23:59 GMT

Support: implement color coding for game, series and franchise infoboxes

1. Bro Hammer (talk): Per my proposal
2. Super Mario RPG (talk): Per proposer.

Oppose: do not implement color coding for game, series and franchise infoboxes

1. Nintendo101 (talk) I honestly prefer keeping infoboxes color coordinated to what type of the subject the article is about. It is intuitive and helpful. I feel like allowing too many colors for this infobox would only dilute that structure across the board. I would support some sort of quick way to jump between entries in the same series at the bottom of the infobox, similar to our level and world infoboxes, but I'd rather all game articles share the same colored infobox.
2. EvieMaybe (talk) per Nintendo101
3. Technetium (talk) Per Nintendo101.
4. Hewer (talk) Per, and I also already find the navbox colours for most series to be quite random and arbitrary.
5. Rykitu (talk) Per Nintendo101 and Hewer.
6. Jdtendo (talk) Per Nintendo101. Btw, the salmon pink color of the game infobox does not scream "Mario" to me.
7. Sparks (talk) Per all.
8. ThePowerPlayer (talk) Per Nintendo101.
9. Camwoodstock (talk) Per Nintendo101; we prefer color-coding on subject, rather than series.
10. Power Flotzo (talk) Per all.

Comments

I'm gonna be completely honest...I don't understand what this proposal is asking for. Shadow2 (talk) 19:08, March 6, 2025 (EST)

Changing the colors of {{Game infobox}}, {{Series infobox}}, and {{Franchise infobox}} depending on the game series, so that they match the color schemes currently in use for navigation templates. Jdtendo^(T|C) 10:53, March 7, 2025 (EST)

Miscellaneous

None at the moment.