MarioWiki:Proposals

Current time: Saturday, November 9th, 10:47 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. Any user can support or oppose, but must have a strong reason for doing so (not, e.g., "I like this idea!"). 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.

A proposal section works like a discussion page: comments are brought up and replied to using indents (colons, such as : or ::::) and all edits are signed using the code {{User|User name}}.

How to

Rules

1. If users have 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 the other users, who will then vote about whether or not they think the idea should be used. 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}}.
2. Only registered, autoconfirmed users can create, comment in, or vote on proposals and talk page proposals. Users may vote for more than one option, but they may not vote for every option available.
3. Proposals end 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. Every vote should have a strong, sensible reason accompanying it. Agreeing with a previously mentioned reason given by another user is accepted (including "per" votes), but tangential comments, heavy sarcasm, and other misleading or irrelevant quips are just as invalid as providing no reason at all.
5. 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 administrators.
   • 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.
6. 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 "(banned)" 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.
7. No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old.
8. 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.
9. If a proposal reaches its deadline and there is a tie for first place, then the proposal is extended for another week.
10. 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 the {{proposal check}} tool to automate this calculation; see the template page for usage instructions and examples.
11. 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 can only be re-proposed after four weeks (at the earliest).
12. 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.
13. If the administrators deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to remove it at any time.
14. Proposals can only be rewritten or canceled by their proposer within the first six days of their creation. However, proposers can request that their proposal be canceled by an administrator at any time, provided they have a valid reason for it. Please note that canceled proposals must also be archived.
15. 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.
16. Proposals cannot be made about promotions and demotions. Users can only be promoted and demoted by the will of the administration.
17. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
18. Proposals must have a status quo option (e.g. Oppose, Do nothing) unless the status quo itself violates policy.

Basic proposal and support/oppose format

This is an example of what your proposal must look like, if you want it to be acknowledged. If you are inexperienced or unsure how to set up this format, simply copy the following and paste it into the fitting section. Then replace the [subject] - variables with information to customize your proposal, so it says what you wish. If you insert the information, be sure to replace the whole variable including the squared brackets, so "[insert info here]" becomes "This is the inserted information", not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but what each voting section is supporting 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|[enter your username here]}}<br>
'''Deadline''': [insert a deadline here, 14 days after the proposal was created, at 23:59 GMT, in the format: "November 9, 2024, 23:59 GMT"]

====Support====
#{{User|[enter your username here]}} [make a statement indicating that you support your proposal]

====Oppose====

====Comments====

---

Users will now be able to vote on your proposal, until the set deadline is reached. Remember, you are a user as well, so you can vote on your own proposal just like the others.

To support, or oppose, just insert "#{{User|[add 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 just say "Per my proposal".

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. Proposals dealing with a large amount of splits, merges, or deletions across the wiki should still be held on this page.

For a list of all settled talk page proposals, see MarioWiki:Proposals/TPP archive and Category:Settled talk page proposals.

Rules

1. All active talk page proposals must be listed below in chronological order (new proposals go at the bottom) using {{TPP discuss}}. 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. Place {{TPP}} under the section's header, and once the proposal is over, replace the template with {{settled TPP}}.
2. All rules for talk page proposals are the same as mainspace proposals (see the "How to" section above), with the exceptions made by Rules 3 and 4 as follows:
3. The talk page proposal must pertain to the subject page of the talk page it is posted on.
4. When a talk page proposal passes, it should be removed from this list and included in the list under the "Unimplemented proposals" section until the proposed changes have been enacted.

List of ongoing talk page proposals

• Split sections between Tanooki Mario and Kitsune Luigi (discuss) Deadline: November 10, 2024, 23:59 GMT
• Determine what to do with Jamboree Buddy (discuss) Deadline: November 12, 2024, 23:59 GMT
• Split Cursed Mushroom from Poison Mushroom (discuss) Deadline: November 12, 2024, 23:59 GMT
• Merge Orbs that share names with pre-existing Mario Party series items with those items (discuss) Deadline: November 14, 2024, 23:59 GMT
• Create a number of articles for special buildings in Super Mario Run (discuss) Deadline: November 15, 2024, 23:59 GMT
• Consider Deep Cheeps' appearance in the Super Mario Maker series a design cameo rather than a full appearance (without Blurps being affected) (discuss) Deadline: November 15, 2024, 23:59 GMT
• Merge Mushroom, Dash Mushroom, and most of Super Mushroom (discuss) Deadline: November 18, 2024, 23:59 GMT
• Expand and rename List of characters by game (discuss) Deadline: November 20, 2024, 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, Super Mario Run, and Super Mario Bros. Wonder.

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 articles for the alternate-named reskins from All Night Nippon: Super Mario Bros., Doc von Schmeltwick (ended October 3, 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)

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)

Split Banana Peel from Banana, Doc von Schmeltwick (ended September 18, 2024)

Merge Spiked Thwomp with Thwomp, Blinker (ended November 2, 2024)

List of Talk Page Proposals

• Separate Wii U audio files from the ones on the GBA (Discuss) Passed
• Merge Choco Cake with Chocolate Cake (Discuss) Passed
• Split the Paper Mario boos from Big Boo into a separate article. (Discuss) Passed
• Decide if Bandits are a sub-species of Shy Guys (Discuss) Deadline: June 7, 2015, 23:59 GMT
• Decide if Porcupuffers are Cheep Cheeps (Discuss) Deadline: June 16, 2015, 23:59 GMT
• Seperate Payday Waystation into a separate article (Discuss) Deadline: June 18, 2015, 23:59 GMT

Writing Guidelines

None at the moment.

New features

None at the moment.

Removals

Stop using the term "sub-species" on the wiki

For pretty much the wiki's entire run, "sub-species" (or "subspecies") has been used as shorthand to denote species like Gloomba or Fire Bro from the more basic species they're derived from (i.e. Goomba and Hammer Bro), but it's high time we put and end to it, and here's why:

1. It's wrong - In science, "subspecies" denotes different populations of a species that are genetically, geographically, behaviourally, and/or morphologically distinct, yet still similar enough for interbreeding to occur freely when possible. What we call "subspecies" are not actually subspecies at all: they are completely different species, whether we're comparing Lakitus to Koopa Troopas or Deep Cheeps to Cheep Cheeps. There is no reason why we should so wilfully misuse very specific scientific terminology incorrectly when there are other options available like simply "type", "variation" or just plain "species". It's not like "beta elements" where there is no umbrella term and we have to make due with what readers are most familiar with: everyone already understands what "species" means, unlike the muddled "subspecies" (which even scientists argue about).
2. It's speculation - It's clear enough when things are based on other things to whatever extent, but classifying some enemies as "subspecies" instead of "species" has always struck me as presumptuous. Where exactly does the line get drawn? Some things like Koopa Paratroopas are rather basic and fundamental in their own rights, with many derived species of their own, yet are still called "subspecies". And what about things like Shady Paratroopa that could be a subspecies of Koopa Paratroopas or Shady Koopas? Only a few sets of differently-coloured/powered RPG enemies and things like the red and blue PM Spike Tops really fit the proper "subspecies" definition, but we already established that we're not using science here, so all that's left are judgment calls being passed off as hard distinctions that don't actually exist in official material.
3. It's misleading - Despite the liberties we're taking with the term, "subspecies" still inherently sounds like it requires close relatedness between species (based on their names and/or appearances), but for the sake of navigation and connectivity between articles, sometimes it's useful to be able to reflect the conceptual relatedness between rather different species, such as Clubbas and Chargin' Chucks being related to the more standard Koopa species. Having relaxed terminology would make this easier (i.e. potentially avoiding some TPPs and other such discussions) and result in less cross-talk between users operating on differing definitions of "subspecies".
4. It's inconsistent - As well as murky definitions and three different ways to spell the term ("subspecies"/"sub-species"/"sub species") being found across the wiki, and even side-by-side in single articles, there are also plenty of cases where single subjects are being called both "species" and "subspecies". For example, Ice Piranha Plant bears both Category:Sub-Species and Category:NSMBU Species, is listed as a "sub-species" in the Piranha Plant infobox, and is part of the "species" list in {{Piranha Plants}}. This is not good.

Between the disconnect with how the real world uses the word, and the different definitions, applications and spellings throughout the wiki, there is really only one way to sum up the use of "subspecies" around here: it's confusing, and we should get rid of it. Specifically, we should do the following:

• Remove all occurrences of "subspecies", "sub-species" or "sub species" from the articles. Instead, everything should be called plain "species", and described informally as being based on and/or related to other species with words like "type", "variety", "kind", etc.
• Delete Category:Sub-Species, Category:Yoshi Sub-Species, Category:Donkey Kong Sub-Species and Category:Wario Sub-Species. The equivalent "Species" categories exist for all four cases, but ideally, game-specific "Species" categories should be used to replace everything (but that's another kettle of fish altogether).
• Replace the "sub_species" variable in {{Species-infobox}} with "derived_species". At the same time, "species_origin" should be replaced with "parent_species", for the sake of uniformity (there's already a "related species" variable for similar species not directly based on or providing the basis for the subject in question) and killing two birds with one stone since we'll have to fix the infoboxes anyway; this second change is from this cancelled proposal and its corresponding forum thread (both of which debate the use of "subspecies").
• Add "subspecies" to the list of frequently misused terms.

This will affect A LOT of articles and will take time to gradually roll out, but I think it's worth doing. There is no good reason why we need to stay inconsistent, confusing and misinformed about how we go about defining the species of the Mario series.

Proposer: Walkazo (talk)
Deadline: June 11, 2015

Support

1. Walkazo (talk) - Per proposal. The zoologist half of me has wanted to eradicate this accursed term from the wiki for over seven years now. No more.
2. Baby Luigi (talk) Per Walkazo. And yes, even though the term is used to described fictional species, it still gave me misinformation when thinking about actual sub-species. That's not right. I admit I am a bit pedantic when it comes to vocabulary and jargon but honestly, I'm pedantic for the very reason of being fed misinformation, which isn't the ideal way to learn things.
3. ShyGuy8 (talk) Per Walkazo and Baby Luigi. Yes, that's not right. In fact, I think it should be related spiecies instead of subspiecies.
4. Kart Player 2011 (talk) Per Walkazo.
5. Mario (talk) Yes, remove ALL instances of it. I was misinformed about the true definition of "subspecies" this entire time I was in this wiki. This is a personal account, but if it confuses me, it's bound to confuse a lot of other readers. This wiki leads us to think "subspecies" means a derived or related organism even though the technical term is "some differences but capable of interbreeding and producing fertile offspring", especially provided that the "producing fertile offspring" part is the fundamental definition of a species. In that sense, subspecies do NOT denote separate species; the basic Linnaeus names have two names, but a third one is given if it's a subspecies. "Derived species", "parent species", "related species", these are all more correct and much more precise substitutes, making them vastly superior to the vague, confusing, incorrect "subspecies". In writing, we aim for precision and accuracy, and this proposed changes does exactly what is the gold standard in writing, so, as someone who admits of being very pedantic at times (the scathing criticism to singular "they" and contractions), it's not surprising that I want these changed enacted. This time, though, it's not pedantry, it's about being precise and accurate. It's been seven years, but better late than never to undo all that damage.
6. SmokedChili (talk) Per all, but take note of the rare few official cases.
7. Jazama (talk) Per all
8. Andymii (talk) Per all; a nicely crafted argument. I just find it funny that we are now debating over scientific terminology in a wiki about talking mushrooms and turtle kings.
9. LinkTheLefty (talk) Per proposal. (I also notice a bit of support due to the inadvertent spread of misinformation - "Beta" is rightfully considered a misused term as well, but I really do think a better label than "Beta elements" should be considered since it's a somewhat similar situation.)
10. Mr. Ice Bro. (talk) Per all.
11. Binarystep (talk) my younger self would hate me for this Per all.

Comments

@SmokedChili: We can make an exception, but it's going to break consistency, and it won't be unreasonable to assume it's another species (just how people assumed all those dark-eyed juncos were separate species), and, besides, Nintendo was very wrong about terminology before (most blatantly, the most egregious and irresponsible usage of "remix" I've ever seen in official media: Super Smash Bros. 4). It's me, Mario! (Talk / Stalk) 15:09, 5 June 2015 (EDT)

Changes

Super Mario Land 1 and 2 confirmed apart of the main series by Nintendo: Super Mario wiki should change accordingly

For years it has been debated whether Nintendo considered the Super Mario Land games apart of the main Mario series or not. Super Mario Wiki, and rightfully so, chose that the Super Mario Land games are not apart of the main Mario series but rather considered its own series most likely because of the Nintendo sources below.

https://www.youtube.com/watch?v=nzERrLY-_9s
[1]

As one can see, Nintendo did not include the land games as part of the main Mario series titles during Mario's 25th anniversary 5 years ago. This has lead people such as myself to believe that the Super Mario Land games are indeed apart of their own series. However, as of May 29, 2015. Nintendo has updated Mario's 30th anniversary site to include all the main series Mario titles. In this list is Super Mario Land and Super Mario Land 2: 6 Golden Coins. As shown, this is included in both the American and Japanese versions of the site.

http://www.nintendo.co.jp/mario30th/index.html#/history/
http://supermario.nintendo.com/#/history/

Due to this confirmation by Nintendo, all articles on Super Mario Wiki should be changed to fit this new information. Such articles as the Super Mario Series articles should be changed to add the two Land games, and articles such as Super Mario Land Series articles should most likely be deleted entirely due to their interference of the first two Super Mario Land games being apart of the main Mario series. Other changes being the chronological order of Mario titles. An example being, changing "New Super Mario Bros. is the eighth installment in the Super Mario series." To. "New Super Mario Bros. is the tenth installment in the Super Mario series."

These things might change from time to time, but it's the company's current view that should be reflected on the articles. This is why the Super Mario Land games should now officially be considered apart of the main Mario series by Super Mario wiki.

Proposer: thenintendostooge (talk)
Deadline: June 14, 2015, 23:59 GMT

Support

1. thenintendostooge (talk) Per my proposal. Due to the recent confirmation by Nintendo themselves, the wiki should have articles changed to fit this new confirmation.

Ban the term beta* and rename pages in the Beta namespace

There was a proposal suggesting to change the name of the "beta elements" page to something more accurate. Despite being close to succeeding, it was vetoed by the admins with the reason being that "it's not meant to be taken literally" and "it works".

Except. no. The suggestion was perfectly cogent, the rationale provided for the veto was bad and the proposal should never have been reversed. Here's why

1: It's a bad, innacurate term: "Beta" in programming language refers to a prerelease build that's feature-complete and is being bugtested. It's not even a particularly representative term: the beta period happens near the end of development, long after production ideas are shot down, games are overhauled, unique characters and objects are removed... etc, which is what the "beta" pages usually cover.

Some may argue that "language evolves" and that "beta as it is used here is not meant to be taken literally", but I don't think it's a strong arguments. Sites focused on the documentation of unused/prelease content such as Unseen 64 and TCRF have mocked the usage of "beta" as a catch-all term and lower-quality ressources that use it that way. Other fan wikis like SegaRetro also do not use "beta" as a generic term. Fact is, "beta" is nowhere near accepted in professional circles and that's what the wiki claims to be - a professional ressource. Furthermore, why would you use an inacurate and potentially misleading term when dozens of accurate, non-misleading alternatives exist?

2: It leads to muddy, vague writing. Whenever you see "beta" used on other pages, its catch-all nature muddies the information. "Dread Kong did not exist in the beta version of Donkey Kong Jungle Beat" - nevermind that referring to a singular "beta version" betrays a gross ignorance of how game development works, what's the "beta" in question? A preview in a magazine? A proto leaked on the internet? Something suggested in pre-production that was rejected and never programmed into the game? Banning the generic beta and forcing editors to be more specific (as opposed to the current wishy-washy stance that "we know it's bad, but we still use it because reasons I guess") will improve the quality of the information.

3: The "grandfather clause" is never a good excuse: Similar to this case, "sub-species" is a long-used term that was found to be inaccurate and cause inconsistencies, and the current community consensus is that it should be replaced despite its longstanding nature. "It's what we've always used" is not a good refutation when the usage of a term is proven to lower the credibility and quality of the information, as is the case here.

As a replacement, I propose beta pages to be renamed List of prerelease and unused content. "Prelease" perfectly encansuplates the varieties of content that's not present in the final code, and it's wordier, yes, but not overly so. Generic mention of "beta" should not be robotically replaced with a generic "In prelease/unused content of [game]", but rather with a specific term ("magazine preview", "prototype", "unused"), with a piped link to the "List of..." pages.

(*: This of course doesn't apply to actual beta builds, but as none of the specific builds documented here are specifically said to be real betas, that precision is kinda irrelevant.)

Proposer: Glowsquid (talk)
Deadline: June 15, 2015

Move beta pages to "List of prelease and unused content" and ban the generic "beta" in mainspace articles

1. Glowsquid (talk)
2. thenintendostooge (talk) Simply because something works does not make it professional or the most efficient. The simple term beta used on the wiki goes against basic definition and term of the word that is beta.

Miscellaneous

None at the moment.