MarioWiki:Proposals

Current time: Sunday, December 1st, 00:11 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.

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

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. Anyone is free to comment on proposals (provided that the page's protection level allows them to edit).
2. 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.
3. Users may vote for more than one option, but they may not vote for every option available.
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 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.
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 "(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.
7. Proposals cannot contradict an already ongoing proposal or overturn the decision of a previous proposal that concluded less than four weeks (28 days) ago.
8. 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.
9. 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.
10. If a proposal reaches its deadline and there is a tie for first place, then the proposal is extended for another week.
11. 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.
12. 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.
13. 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.
14. After a proposal passes, it is added to the appropriate list of "unimplemented proposals" below and is removed once it has been sufficiently implemented.
15. 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.
16. 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.
17. 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.
18. Proposals cannot be made about promotions and demotions. Staff changes are discussed internally and handled by the bureaucrats.
19. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
20. 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: "December 1, 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. All of the above proposal rules also apply to talk page proposals. Place {{TPP}} under the section's header, 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 {{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.

List of ongoing talk page proposals

• Merge False Character and the Fighting Polygon/Wireframe/Alloy/Mii Teams to List of Super Smash Bros. series bosses (discuss) Deadline: December 2, 2024, 23:59 GMT
• Move Kolorado's father to Richard (discuss) Deadline: December 11, 2024, 23:59 GMT
• Move Mysterious Cloud to either Hat cloud or Cap cloud (discuss) Deadline: December 14, 2024, 23:59 GMT
• Split and trim the Vine article (discuss) Deadline: December 14, 2024, 23:59 GMT
• Move Bomb (species) to Bomb (Final Fantasy) (discuss) Deadline: December 14, 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)

Stop considering reused voice clips as references (usually), Waluigi Time (ended November 8, 2024)

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

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

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

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)

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

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

Create articles for "Ashita ni Nattara" and "Banana Tengoku" or list them in List of Donkey Kong Country (television series) songs, Starluxe (ended November 23, 2024)

Determine how to handle the Tattle Log images from Paper Mario: The Thousand-Year Door (Nintendo Switch), Technetium (ended November 30, 2024)

Writing guidelines

None at the moment.

New features

Create a template to crop images on-the-fly without having to tamper with the base file's dimensions

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

So Wildgoosespeeder (talk) shared this nifty template that TCRF has: tcrf:Template:CSS image crop, which allows images to be displayed in mainspace at a cut-out size from how they are on the image files themselves. This has two utilities: one is shrinking to a relevant entity in group textures such as this oneMedia:M&SatL2012OG Wii audience.png, and the other is to avoid blank space without having to crop the raw graphic parameters - thus allowing best-of-both-worlds for the previous proposal I attempted (and failed), as it satisfies the OCD itch of avoiding bad and/or inconsistent crops on the base files without taking up unnecessary space where the images are actually used. It also removes a lot of unnecessary work actually cropping/uncropping images since you don't have to save them to a machine/web address to upload a new version - you can just put in the parameters you want and go from there.

Proposer: Doc von Schmeltwick (talk)
Deadline: December 11, 2024, 23:59 GMT

C-S-Yes

1. Doc von Schmeltwick (talk) - Goes without saying I think this is a good idea.
2. Super Mario RPG (talk) Sounds like a reasonable compromise.
3. Jdtendo (talk) It's better to crop an existing image programmatically than having to upload a cropped version for a specific use case.
4. Ahemtoday (talk) Per proposal.
5. Pseudo (talk) Seems useful.
6. Wildgoosespeeder (talk) Sometimes I just find random things on other Wikis and remember a previously failed proposal. I hope this helps out!
7. EvieMaybe (talk) per Jdtendo! this seems very useful
8. Axii (talk) Per proposal.

Comments on CSS image crop

This appears to be similar to a template I have made in order to crop images to perfectly squared off icons for uses on pages such as Pipe Frame (e.g. displaying Mii Racing Suit icons in the same table as other character icons); however, the version you're presenting seems to include more options. I'm not gonna vote yet, but so far I don't see the harm to have this other template too. rend (talk) (edits) 06:42, November 27, 2024 (EST)

Removals

Remove video game console generations

I would imagine most people who have discussed video games in the past have heard of video game console generations. It is a tool to categorize video game hardware and its place in time. There is just one problem: the current video game console generation system is flawed. If you would like to further read into the specifics as to why I would recommend this Time Extension article by Jack Yarwood. But in short, the phrase "next generation" originates as a term used starting around the 1990s, as video games evolved over the many years, Wikipedia editors would create their own video game console generation system that has for the most part remained unchanged since its introduction in the early 2000s. This generation system would slowly be adopted by other sites, media, and the people who engage with video games.

Within the scope of the major Nintendo video game consoles, this is currently how the video game console generation system is categorized.

First generation: Color TV-Game
Second generation: Game & Watch
Third generation: Family Computer, Nintendo Entertainment System
Fourth generation: Super Famicom, Super Nintendo Entertainment System, Game Boy
Fifth generation: Nintendo 64, Game Boy Color
Sixth generation: Nintendo GameCube, Game Boy Advance
Seventh generation: Wii, Nintendo DS
Eighth generation: Wii U, Nintendo 3DS, Nintendo Switch
Ninth generation: Nintendo Switch

There is one obvious problem that you might have noticed. The Nintendo Switch is in the eighth and ninth generation. This is due to when the Nintendo Switch first released: March 3, 2017. The current system begins the ninth generation in November 2020 with the release of the Xbox Series X/S and PlayStation 5 consoles. This is despite how for most of the lifespan of the Nintendo Switch, it has actually been competing against consoles that under this system is a whole generation ahead. Because of this, it is not entirely clear where the Nintendo Switch is in the video game console generation system and the solution is to simply file it in both generations rather than one or the other.

Now the Nintendo Switch is a hybrid console, but what about portable consoles? The current video game console generation system lumps in both home and portable consoles. If the goal of the generation system was to be based on hardware specifications than it ultimately falls flat with consoles such as the 16-bit Super Famicom and Super Nintendo Entertainment System home consoles being in the same generation as the 8-bit Game Boy portable console. For home consoles there is absolutely nothing in the second generation, with the Color TV-Game consoles being in the first and the Family Computer and Nintendo Entertainment System consoles being in the third. Portable consoles have a similar issue with nothing in the third generation, with the Game & Watch line in the second and the Game Boy being in the fourth.

For these reasons, I think it should be considered to remove video game console generations from this wiki. It is ultimately a flawed tool that originates as something made up by various Wikipedia editors that stuck around for far too long without real consideration of its flaws. If video game console generations are removed, we should gravitate towards more factual descriptions that better represent the consoles.

Home consoles: 1. Color TV-Game 2. Family Computer, Nintendo Entertainment System 3. Super Famicom, Super Nintendo Entertainment System 4. Nintendo 64 5. Nintendo GameCube, 6. Wii 7. Wii U 8. Nintendo Switch
Portable consoles: 1. Game & Watch 2. Game Boy 3. Game Boy Color 4. Game Boy Advance 5. Nintendo DS 6. Nintendo 3DS 7. Nintendo Switch

Home console example: "The Nintendo 64 is the fourth Nintendo home console platform."
Portable console example: "The Nintendo DS is the fifth Nintendo portable console platform."
Hybrid console example: "The Nintendo Switch is the seventh portable and eighth home Nintendo console platform."

This alternative system does have flaws with the Switch being in two categories again, however that is due to the Switch being a hybrid between a home and portable console. The reason the console is in two video game generations according to Wikipedia is not as clear. Another much straightforward solution would be to simply list the predecessor and successor of each console.

Example: "The predecessor to the Nintendo 64 is the Super Famicom and Super Nintendo Entertainment System and the successor is the Nintendo GameCube."

This is the most likely solution if video game console generations were removed. It is easy to understand and already implemented to an extent. The work required is simply the removal process with minimal addition.

Proposer: Bro3256 (talk)
Deadline: December 13, 2024, 23:59 GMT

Support

1. Technetium (talk) Per proposal.
2. EvieMaybe (talk) console generations make more sense when comparing against several different consoles. for our use case, they're pretty irrelevant.
3. Super Mario RPG (talk) Per proposer and EvieMaybe.
4. Bro3256 (talk) Per proposal.
5. Hewer (talk) Per proposal, specifically the second suggested solution of not numbering consoles at all. Saves the unnecessary confusion.

Oppose

1. Doc von Schmeltwick (talk) - Regardless of contemporary awkwardness, it's still useful comparing the timelines for the ones of the past. I've still seen people not realize the GBC was in circulation around the same time of the N64 based on nothing but their respective bit-count.
2. Camwoodstock (talk) - This feels like a case of "if it ain't broke, don't fix it". While we've always found the "console generations" thing really, really strange (as you can expect from a metric born from Wikipedia itself), we can't deny that it is still useful to a degree, and unlike, say, calling unused content "beta" content, the term "console generation" is still a term that sees active use in gaming circles, even if as of late Nintendo's side of it has gotten a bit desynced. In addition, as was pointed out in the comments, the Philips CD-i is noticeably absent, but in addition to that, so is the Virtual Boy, which is even more directly Nintendo related? Not that we'd particularly like this even if both of these were accounted for, mind...
3. Ahemtoday (talk) Without the Virtual Boy in here, this numbering scheme just flat-out isn't actually true. As such, I can't support this proposal.
4. GuntherBayBeee (talk) Perhaps a better idea is to use Cross-generation ({{wp|Eighth generation of video game consoles|eighth}}—{{wp|Ninth generation of video game consoles|ninth}}) on the Nintendo Switch page and use {{wp|[No.] generation of video game consoles|[No.] generation}} on pages on all other systems. As such, I'm opposing this proposal.
5. FanOfYoshi (talk) Per Doc von Schmeltwick and Cam&woodstock.

Comments

I disagree with the premise, since a tool that is helpful but flawed is still helpful. Moreover, we do cover a couple of devices that do not fit on a Nintendo-exclusive relative timeline, namely the Philips CD-i and the Triforce arcade boards. I guess "contemporary to the _____" works just as well, but there's a level of "semantics over broader public" thing that I'm a little iffy about if that kind of phrasing has to be used. Salmancer (talk) 13:51, November 29, 2024 (EST)

Where the HECK is the Virtual Boy in all of this? Nintendo's actual third portable console and part of the fourth generation (or fifth? It was supposed to keep customers occupied while waiting for the Nintendo 64), as it was released in 1995? rend (talk) (edits) 15:43, November 29, 2024 (EST)

I didn't include select consoles in this proposal since my arguments mainly focused on the major Nintendo consoles. That is not to say consoles like the Virtual Boy and non-Nintendo consoles like the Philips CD-i aren't important (they are!), but I wanted to prioritize the issues present with how the video game geration system currently works with the major Nintendo consoles since these alone already present issues with the system without the additions of what was omitted for the purposes of this proposal.

Regarding Triforce, that is a whole different category of hardware. Arcade hardware for the most part has never worked with this generation system since it was primarly designed with home and portable consoles in mind. How do you even slot in arcade hardware to begin with? Arcade games had a completely different evolution to their console counterparts and were usually cutting edge at the time before any console equivalents made it to market, and even if they did unlike consoles, arcade hardware differs depending on the game. How can you be sure what a certain arcade game is running on is in a certain generation? --Bro3256 (talk) 18:04, November 29, 2024 (EST)

@Doc von Schmeltwick: I don't really see how that's an argument against this proposal. We have the release dates listed for the consoles, and the Game Boy Color article's very first sentence describes it as "the handheld counterpart of the Nintendo 64". Why is it also necessary to call them "fifth generation"? I'd argue that it's probably the least clear way of showing the connection, because I can't imagine "fifth generation" means anything to someone who doesn't know about when those consoles released. Not to mention that being in the same "generation" doesn't necessarily mean they were being sold at the same time, as the Wii U and Switch demonstrate. Hewer (talk · contributions · edit count) 17:30, November 29, 2024 (EST)

@Ahemtoday: Please read above the comment I made in regards to the absence of Virtual Boy. Keep and mind that I was presenting it as one possible solution if video game console generations were removed. That is not to say it should be the solution used hence why I provided another alternative one. If the first system was implemented into the wiki than I would imagine Virtual Boy being included. --Bro3256 (talk) 18:25, November 29, 2024 (EST)

Do we really discuss console generations extensively on the wiki? I do not know of any examples offhand. - Nintendo101 (talk) 23:40, November 29, 2024 (EST)

The Family Computer and Nintendo Entertainment System articles are obvious examples but there's this article's trivia section as an example of non-console articles.--Bro3256 (talk) 00:08, November 30, 2024 (EST)

"There is one obvious problem that you might have noticed. The Nintendo Switch is in the eighth and ninth generation. This is due to when the Nintendo Switch first released: March 3, 2017. The current system begins the ninth generation in November 2020 with the release of the Xbox Series X/S and PlayStation 5 consoles. This is despite how for most of the lifespan of the Nintendo Switch, it has actually been competing against consoles that under this system is a whole generation ahead."

But then I have to question: what about the SG-1000 and the Mark III/Master System releasing just shy of a few years? I know it has a very time span compared to the Wii U and Switch, but if they are bundled under the third-generation, the Switch should also be this way for the eighth, right? -- PanchamBro (talk • contributions) 01:00, November 30, 2024 (EST)

There have been countless debates regarding the SG-1000 in particular due to it sharing nearly the exact same hardware as the ColecoVision yet both consoles are in different generations despite being released within one year apart. However this side of the console generations debate is not relevant to the scope of this wiki.--Bro3256 (talk) 01:20, November 30, 2024 (EST)

The wiki actually does currently consider the Switch to be "eighth generation", as seen in the infobox on its page. Which is a bit confusing since it puts it in the same generation as the Wii U even though the only thing making them less separate is the release timing of other consoles not covered by this wiki. Hewer (talk · contributions · edit count) 07:42, November 30, 2024 (EST)

Changes

None at the moment.

Miscellaneous

None at the moment.