MarioWiki:Proposals

Current time: Thursday, March 20th, 15:58 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. 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])====

For the purposes of the ongoing proposals list, a poll proposal's deadline is the latest deadline of any ongoing option(s). A poll proposal is archived after all of its options have settled, and it is listed as one single proposal in the archive. It 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

• Properly define Brown Yoshi (discuss) Deadline: March 20, 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
• Determine what memes should be on the Internet references page (discuss) Deadline: March 22, 2025, 23:59 GMT
• Merge Beanbean Coin to Coin (discuss) Deadline: March 22, 2025, 23:59 GMT
• Split Toad (Mario Party 4) from Toad (discuss) Deadline: March 23, 2025, 23:59 GMT
• Move Big Fire Piranha to Big Fire Piranha Plant (discuss) Deadline: March 23, 2025, 23:59 GMT
• Create page for WarioWare, Inc.: Mega Microgame$! seaside location and split Tomorrow Hill (discuss) Deadline: March 27, 2025, 23:59 GMT
• Split GB from Game Boy (discuss) Deadline: March 28, 2025, 23:59 GMT
• Split Zap Ball from Big Amp (discuss) Deadline: March 29, 2025, 23:59 GMT
• Determine what language(s) to use for the Super Mario Bros. Special enemies (discuss) Deadline: March 29, 2025, 23:59 GMT
• Split Ruby Rock from Boulder (discuss) Deadline: March 30, 2025, 23:59 GMT
• Split Shark Chomp from Big Chain Chomp (discuss) Deadline: March 30, 2025, 23:59 GMT
• Delete Minecraft and split the Super Mario Mash-Up Pack (discuss) Deadline: March 31, 2025, 23:59 GMT
• Delete Donkey Kong, Donkey Kong Junior, Mario Bros. (discuss) Deadline: March 31, 2025, 23:59 GMT
• Split references that went unused into a list of references in video game pre-release and unused content (discuss) Deadline: March 31, 2025, 23:59 GMT
• Merge the Bears to the Brothers Bear (discuss) Deadline: April 1, 2025, 23:59 GMT
• Split Pokeynut from Big Pokey (discuss) Deadline: April 1, 2025, 23:59 GMT
• Split Pipe Cannon from Bill Blaster (discuss) Deadline: April 1, 2025, 23:59 GMT
• Split Piscatory Pete from Cheep Cheep (discuss) Deadline: April 1, 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)

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)

Implement crossover articles, Nintendo101 (ended March 17, 2025)

Add headings for first topics of talk pages that lack one, Jdtendo (ended March 17, 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)

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)

Split Super Mario Maker helmets from Buzzy Shell and Spiny Shell (red), PopitTart (ended March 12, 2025)

Restructure Yoshi's Island (series) into Yoshi (series), PopitTart (ended March 19, 2025)

Remove information on Super Mario Maker series big Para-Beetles from Heavy Para-Beetle, Blinker (ended March 18, 2025)

Writing guidelines

None at the moment.

New features

None at the moment.

Removals

None at the moment.

Changes

Decide how to add the Final Fantasy Wiki as an interwiki link

Since there are articles about subjects from the Final Fantasy series that have appeared in Mario Hoops 3-on-3, Mario Sports Mix, and/or certain Super Smash Bros. games (Nintendo 3DS / Wii U and/or Ultimate), I'm looking forward to add the Final Fantasy Wiki as an interwiki link. The issue is that there is also a wiki from Fandom (powered by Wikia) that is also named Final Fantasy Wiki. The good news, I've come up with three options:

Option 1

Change the text for Fandom's wiki from "Final Fantasy Wiki" to "Final Fantasy Wiki (Fandom)" on pages AND add the Final Fantasy Wiki as an interwiki link.

Option 2

ONLY add the Final Fantasy Wiki as an interwiki link (even if confusing).

Option 3

Do NOTHING.

Here is an example on the use of the interwiki link for the Final Fantasy Wiki:

{{iw|finalfantasywiki|Cactuar}}

Cactuar

{{iw|finalfantasywiki|Cloud Strife|Cloud}}

Cloud

That way, we'll be able to use the Final Fantasy Wiki interwiki link once it gets added right after either Option 1 or Option 2 passes, as well as change the text for Fandom's wiki from "Final Fantasy Wiki" to "Final Fantasy Wiki (Fandom)" on pages right after only Option 1 passes.

Proposer: GuntherBayBeee (talk)
Deadline: August 1, 2024, 23:59 GMT

Option 1

1. GuntherBayBeee (talk) My primary choice

Option 2

1. GuntherBayBeee (talk) My secondary choice

Option 3

1. SeanWheeler (talk) The independant Final Fantasy Wiki is full of red links and is incomplete compared to FANDOM's wiki.

Comments

The Fandom wiki is not actually called "Final Fantasy Wikia", not to mention that Fandom not even refers to itself as "Wikia" anymore, to the point that they also dropped that "Powered by Wikia" tagline. Wouldn't it be better to instead refer to it as "Final Fantasy Wiki (Fandom)" to differentiate the two wikis? rend (talk) (edits) 17:40, July 25, 2024 (EDT)

Also, what even is the "text" being referred to in the proposal that needs changing? When do we need to refer to the Fandom Final Fantasy Wiki? Hewer (talk · contributions · edit count) 17:43, July 25, 2024 (EDT)

I'm pretty sure they may be referring to External link sections, e.g. here. Currently, the Super Mario Wiki links to specifically the Fandom wiki when it comes to anything Final Fantasy (even outside External link sections), since we don't have an interwiki link for an independent Final Fantasy Wiki yet. I imagine they wouldn't simply replace the Fandom wiki link with the independent wiki link and rather include both wikis. rend (talk) (edits) 17:50, July 25, 2024 (EDT)

Last week, I replaced "Wikia" with "Wiki (Fandom)." How do you think the proposal looks? GuntherBayBeee 10:00, August 1, 2024 (EDT)

Why are you saying this a literal week after making the change, instead of (nearly) immediately after? Wouldn't that make more sense? Or are you asking this only now, because you're either subtly asking me to vote again, or trying to drum up more engagement again, because your proposal did not get any votes?
Either way, while it's good that you applied the change, I'm still abstaining because I'm unsure which option is better. And in case I need to make it clear, I'm NOT obligated to vote, and NOT obligated to say why I'm not voting, and I should NOT be obligated about either option JUST because I engaged in the comment section. As I said before: "no one is forced to vote for an option, even if they're joining in the conversation, so I'd appreciate it if I'm not being pressed into voting for something." And this feels like teetering into just that again.
I'm sorry if this was a genuine question, but after two previous times where you tried to drum up engagement (either by asking commenters to vote, or by bargaining other changes when people weren't disagreeing at all) after no one voted or commented on it, this feels like another feeble attempt to get more votes, and I personally think this vote-bargaining thing is getting really annoying. You probably should've said and asked this "How'd you think the proposal looks now" thing a LOT sooner, and/or at the very least answer Hewer's question (by corroborating what I told him, for example). That way I could suggest what could be added BEFORE the 3-day deadline of being able to change the proposal has reached, AND would've drummed up engagement in a more natural way. NOW, it feels like you're asking people to vote, and someone had gotten blocked for doing just that. rend (talk) (edits) 11:59, August 1, 2024 (EDT)

Amend notability threshold for recurring musical themes from external sources

Currently, the standard for coverage of recurring musical themes is that any theme appearing in at least eight pieces of Super Mario-related media is notable. This is a reasonable standard, but it leads to a somewhat strange edge case which could become more relevant in the long-term: what about musical themes that do not originate in the greater Super Mario franchise but have appeared in at least eight wiki-notable crossovers?

Here's a concrete example: "Gourmet Race" from the Kirby series has appeared in some form in every single Super Smash Bros. game. That alone counts as six pieces of Super Mario-related media (Super Smash Bros., Melee, Brawl, for Nintendo 3DS, for Wii U, and Ultimate), and its appearances in Nintendo All-Star! Dairantō Smash Brothers Original Soundtrack and Super Smash Bros. Melee: Smashing...Live! (which explicitly count separately according to the eligibility guidelines) bring that up to the threshold of eight appearances.

While music from outside the greater Super Mario franchise certainly can be notable enough to deserve coverage (Game Start A comes to mind), I don't think the "eight appearances" threshold is a good enough metric in these cases. As such, I propose that the notability requirements for musical themes be adjusted:

1. If the debut of the musical theme is a piece of Super Mario-related media (here meaning "a piece of media that has a dedicated article on this wiki"), the current system still applies unchanged. Crossovers still count towards the threshold in this case.
2. If the debut of the musical theme is not a piece of Super Mario-related media, it must appear in at least eight pieces of non-crossover Super Mario-related media. The classification of "crossovers" for this purpose should be consistent with how crossovers are classified elsewhere on the wiki: Super Smash Bros. and Nintendo Land are crossovers, but Mario Kart 8 Deluxe and WarioWare are not crossovers.

It might make sense to say that crossover appearances of a musical theme shouldn't count for themes from the greater Super Mario franchise either (and I have included this as a separate option), but I think it's reasonable to give those themes "preferential treatment" in this way.

Proposer: JanMisali (talk)
Deadline: August 8, 2024, 23:59 GMT

Amend

1. JanMisali (talk) As proposer.

Miscellaneous

None at the moment.