MarioWiki:Proposals

Current time: Thursday, March 20th, 04:15 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)

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

Merge moves exclusive to forms with their respective forms, leaving main article links if they are part of another article. Also replace the Fly article with a list.

Mario’s many, many forms have granted him oh so many forms. These forms grant him many new moves, like swinging a cape, jumping in the air, or even a slew of Link’s moves! Now, how many of these have articles? (Excluding Tail whip)

If you guessed zero, +/- Tail whip, you’re right. This makes sense: If I go to an article on a form, then I want to see all of that form’s nuances. What good is it to have some parts of the benefits conferred by a power-up on a separate page? Imagine if Builder Mario had an article dedicated to swinging its hammer, a core portion of the abilities Builder Mario grants. Imagine if Mole Yoshi had an entire article dedicated to its ability to dig, despite that being the sole move it can do with a button press and digging being its entire point of existing. Imagine if operating the Super Pickax had an entire article separate from the Super Pickax, even though the player doesn’t even have the choice to hold a Super Pickax without using it. (Yes, the act of using a Super Pickax has a name!)

But we’re already doing this, just under the veneer of putting it under existing articles. These articles, for example:

• Shell dash (Shell Mario)
• Dive (Claw dives of Cat Mario)
• Drill Spin (Propeller Mario)

I think this is a flawed line of thinking. For a much as shell dashing and Drill Spinning are moves that can be used by specific forms, they are also benefits conferred by specific forms and power-ups. We should be focusing efforts to improve coverage for such moves on the page for the power-up, as someone who wants to learn everything Shell Mario can do probably shouldn’t have to also check shell dash. Shell Mario should say that shell dashing enemies doesn’t start a point chain. Shell Mario should say if how many hits it takes to defeat a boss with the shell dash. Shell Mario should mention the unique movement opportunities/restrictions of the shell dash compared to base Mario. There shouldn’t be two different articles going into technical detail on a single topic if we can help it, not least because of the potential of a correction to one article not being applied to the other. And if we can only have one super detailed article, then it ought to be the form.

Imagine if we extended the current situation to other named moves of forms? Would Mega Yoshi be a stronger article if there was a second article dedicated to Tail Swipe, on the basis of it having the technical detail of stalling Yoshi’s fall? Even though one needs to know how to Tail Swipe to beat all Mega Yoshi areas? Would Penguin Mario be a stronger article if there was a second article dedicated to Belly Slide? Which is main unique thing about it, given Ice Balls are from Ice Mario and good swimming is from Frog Mario? If we gave the field form of Luiginary Ball a page, would it be.a stronger article if there was a second article dedicated to Ball Hammer? Again, something necessary to complete the ball's tutorial area?

As such, this proposal aims to just move all the technical details of moves that can only be performed by power-up forms to the form’s page. The section remains, because it’s a part of the move’s conceptual history, using a {{main}} article link to move over to the form for the nitty gritty on how everything about that specific implementation works. For reference look at how Dash handles the Dash (Mario & Luigi: Superstar Saga) (Relevant Edit) and the Spin Dash (Relevant Edit). Instead of restating the entire move but trying to be a little looser about the mechanics than the main article, it has a note saying “this exists and is a version of the thing this article is about”, and then sends the reader to the main article. It's a more efficient use of bits and our readers' time.

This does not affect moves of non-powered up characters that are modified by the power-up. Flying Squirrel Mario’s high Spin Jumps stay on Spin Jump, Frog Mario's and Penguin Mario’s swimming stay on Swim, Tanooki Mario’s Tail Spin stays on Roll, and so on. This is in addition to these modified versions of moves being written about on their form’s pages. (No, shell dash is not a modified dash. It's a new action that dashing happens to trigger, as indicated by the requirement of dashing and alternate method of crouching on a slope) This proposal does not affect projectiles whose existence is broader than their associated power-up, namely Fireball, Ice Ball, Hammer, and Bubble. Builder Boxes are Crates, so they fall into this bucket. (Superball would be included, but it was merged with Superball Mario years ago and is not included.) This also does not affect character/power-up hybrids. Yoshi's Swallow, Egg Throw, et al, Baby DK's DK Dash Attack, Diddy Kong's Diddy Attack and Barrel Jet, and Rambi's Supercharge and Charge are examples of these exclusions. This is because in some cases the character can use the move without being a power-up, usually because they are playable in a non-power-up capacity. While this isn’t true in every case, it makes sense to extend this grace to all character/power-up hybrids. SMB2 Mario is bizarre, but charge jump is ultimately unaffected. It’s a move of the normal player characters in Super Mario Bros. 2 proper, and the article doesn’t have a Super Mario Maker 2 section to cut down anyway. I’d advocate for adding more charge jump content to the SMB2 Mario article, but that’s not part of the proposal.

Perceptive readers probably realize that this policy would gut Fly, an article entirely about a recurring skill of certain forms/capability of items. An article consisting entirely of {{main}} templates would be bad, right? Au contraire, for this is by design. Fly is trapped in a purgatory where it can’t actually say anything meaningful because all of the data for each of the forms, abilities, and items it’s trying to cover should be on the articles for those things. So it’s a listicle of every game you can fly in with cliff notes about how they work. I guess its a directory for all of the flying skills, but having it be a traditional article makes using Fly as a directory inefficient. At this point, we should embrace the list structure and use it for something lists are good for, comparisons between games. I have compiled a list version of Fly on a userpage, based on the existing List of power-ups. It’s messy and incomplete but I think it’s better than the Fly article. Should this proposal pass, this list will replace the article. As the various contexts of Fly are not the same kind of action to begin with, the article will become List of methods of flight. This broadens the scope to fit all of the components. (Note how "flight" is not a proper noun).

Tail whip was created after I planned this proposal but before I proposed it. If this proposal passes, it gets merged into Raccoon Mario for 2D games and Tanooki Mario for 3D games. This policy devastates Tail Whip in the same way Fly is. Tail Whip can keep its categories as a redirect. While the move may be used by multiple forms, the most basic forms with the attack are more than capable of storing Tail whip's mechanics for the improved versions of White Raccoon Mario and White Tanooki Mario to refer to later. This matches how Penguin Mario defers to Ice Mario and Ice Ball. Tails are also on Tail Whip, but Tail handles using Tail and has no need to be listed on another article. Even if we wanted a complete list of games with with tail attacks, Raccoon Mario already mentions Tail. (The situation is also similar to Cape, which used to compile the yellow capes of Cape Mario and Superstar Mario into a listicle before this proposal reduced it to only the Smash Bros. attack.)

Oh yeah and I guess Strike of Intuition is caught in the crosshairs of this since it is a move exclusive to Detective Peach. Given everything else, it gets merged too.

Proposer: Salmancer (talk)
Deadline: March 31, 2025, 23:59 GMT

Merge moves and Listify Fly: Merge moves to forms, and convert Fly into a list with the name List of methods of flight

1. Salmancer (talk) Per proposal.

Oppose: Status quo

1. Doc von Schmeltwick (talk) - Many of the moves in question are used by multiple forms, so attempting to merge them to all separately would violate Mariowiki:Once and only once EDIT: which makes determining appearances of the move across different games more difficult to find. Furthermore, we do not merge character-specific moves to their respective pages (other than non-Mario characters in the Super Smash Bros. series) - for instance, look at Scuttle and Flutter Jump - so why should we do so with forms?
2. Nintendo101 (talk) I don't think we cover moves and other actions particularly well, and I would rather see what that looks like before proposing mergers. Moves are not strictly the same as the form itself (i.e. Flying Squirrel Mario, Power Squirrel Mario, and captured Glydon can all "glide"), and it would be nice to see detail on what the moves are in isolation. Sometimes different power-uped forms perform the same move. A quick look through the fly article indicates there are things lumped together there that really aren't the same thing.
3. EvieMaybe (talk) per all. the current state of the wiki's move coverage just isn't good enough right now to determine whether this proposal would have any benefits. would love to see this proposal again in the future when we have more ground to stand on, but it's not the time right now.

Comments (Merge moves of forms to forms even if they are non-unique and replace Fly with a list)

I am sorry this proposal planned for a while is going to merge an article that was just made. It kind of jumped further up my list of priorities given I don't want people to put hard work into adding to Tail whip if I'm about to try to merge it. Salmancer (talk) 18:17, March 17, 2025 (EDT)

Question; would this merge Fireball Punch, and would this failing result in re-instating Dangan Mario? These manga "forms" are kind of an edge case. ~Camwoodstock ( talk • contribs ) 18:23, March 17, 2025 (EDT)

Oh dear manga questions. From what I understand of things, I think nothing should happen either way. Dangan Mario was an article as a form, so unless it's getting reevaluated to be a named move it stays where it lies. Fireball Punch is tricky. The thing is that this proposal exists because of pressures from the medium of video games. Fireball Punch is from a linear narrative story, there's not really much of a benefit readers gain from merging Fireball Punch because odds are someone looking at Super Mario Wiki to read about Fireball Mario doesn't need to know what a Fireball Punch is soon after. They might not even be reading the fifth chapter of Volume 1, the only place with a Fireball Punch. You can hardly consider the Fireball Punch to be a core part of Fireball Mario like all of the moves involved in the proposal. Fireball Punch is free from this proposal, though someone else might think the lack of length means it should be merged into Fireball Mario given this proposal is merging many longer articles or sections of articles into their home forms. Salmancer (talk) 18:56, March 17, 2025 (EDT)

@Doc von Schmeltwick for your own sake, you should know "once and only once" as a strict policy has been retired. - Nintendo101 (talk) 19:18, March 17, 2025 (EDT)

Thanks, wish I'd known that before. Doc von Schmeltwick (talk) 19:30, March 17, 2025 (EDT)

Characters aren't forms, so their moves are unaffected by this proposal, which means Scuttle isn't involved, Character/power-ups are unaffected, so Flutter Jump also isn't affected and you can't loophole abuse your way to merging Scuttle through the Luigi Cap. Forms that are improved versions of other forms already defer to the base form for unchanged abilities they inherit. Ice Mario has two paragraphs dedicated to using Ice Balls See example text of everything Penguin Mario has to say about Ice Balls..

After Mario has become this form, he can throw Ice Balls at enemies and freeze them. Mario can then use the frozen enemies as platforms or pick them up and throw them against the wall or other enemies.

- Penguin Mario

The system works! It's repeated for White Raccoon Mario in relation to Raccoon Mario, as per the line, "It gives the player Raccoon Mario's abilities, causes the P-Meter to charge more quickly, allows the player to run and stand on water (like Mini Mario), and grants invincibility for the stage". It's also done for Power Squirrel Mario to Flying Squirrel Mario, with "As Power Squirrel Mario, Mario has all of the abilities of Flying Squirrel Mario, though he never loses the ability to glide and can perform Flying Squirrel Jumps continuously without landing". Salmancer (talk) 19:35, March 17, 2025 (EDT)

"List of methods of flight" as a name for the userpage was designed to be aware that not everything on Fly is the same kind of move. (and also it managed to morph into a list of all ways to get from point A to point B if point B is higher than point A... and then an extra addendum for hovering over hazards.) Would it be better if it were placed in mainspace as "List of methods of flight"? Salmancer (talk) 19:47, March 17, 2025 (EDT)

Regarding your saying that tail whip's info would be moved to Raccoon Mario for 2D games and Tanooki Mario for 3D games, would that not mean that Tanooki Mario's page would not discuss the tail whip until Super Mario 3D Land, despite it being usable by that form in Super Mario Bros. 3? Doc von Schmeltwick (talk) 19:53, March 17, 2025 (EDT)

Tanooki Mario is already doing exactly that. I don't see anything that makes the article hard to follow, short of it going "there is mandatory reading before reading this article." Which White Raccoon Mario and White Tanooki Mario have been doing as well. It's fine.

In this form, he can turn into an invulnerable statue by holding +Control Pad down and pressing B Button at the same time, in addition to using Raccoon Mario's moves, making it an improved version of Raccoon Mario.

- Tanooki Mario, Super Mario Bros. 3 section.

However, the form's mechanics are different from Super Mario Bros. 3, as while Mario can still tail whip (by pressing or ) and glide (now done by holding or , as with Caped Mario, rather than tapping the buttons), he cannot fly during gameplay.

- Tanooki Mario, Super Mario 3D Land section.

Uh, filler text for sig. I guess I'm advocating for building the 3D Land text up more, since that game shouldn't be deferring to Raccoon Mario as it sort of does now. Salmancer (talk) 20:05, March 17, 2025 (EDT)

But how is it superior to do so compared to just having an article for the move? Doc von Schmeltwick (talk) 20:17, March 17, 2025 (EDT)

Hypothetical: "Wow! Tanooki Mario is so cool! What does he do?/I just beat 3D Land, is there any nuance to it I missed?/Are there any bugs in 3D Land I can exploit with it? I know, I'll go to the Tanooki Mario page on Super Mario Wiki!"

In the current wiki, the three hypothetical people with varying interest in Super Mario read both an article on Tanooki Mario and an article on Tail whip to find everything they want to know. This proposal wants to make all of them only read one article, Tanooki Mario. I think this is better because it saves them the additional click and additional loading time and appeals to lower attention spans. I value these hypothetical readers over the hypothetical reader who is a Mario historian who wants to see the evolution of Tail whip across every game of the franchise. Keep in mind, redirects exist so the earlier three hypotheticals can mostly get to the right page if they zig where I think they'd zag and search for a move name. Okay except for Tail whip in specific because of the 2D/3D split, oof moment. I guess disambiguation pages still let my example work since while there would still be two pages to look at the first of them would be short and quick to load because its a disambig and therefore still superior to having Tail whip as full article alongside Raccoon Mario and Tanooki Mario. Salmancer (talk) 20:59, March 17, 2025 (EDT)

"Gee, I wonder if that cool thing Tanooki Mario does appears in any other games for any other forms?" This is the more likely question that would be asked. Which is why the move page makes more sense. Doc von Schmeltwick (talk) 21:01, March 17, 2025 (EDT)

I think my system still lets that person get to the answers reasonably intuitively. Tanooki Mario says it's super duper Raccoon Mario, so navigating to that page seems reasonable if one wants more tail whipping action. From Raccoon Mario they'll hit Tail. The only odd one out is Mario Kart Super Leaf, which is exclusively covered on Super Leaf, except thanks to Tanooki Mario being playable in Mario Kart Tour with the Super Leaf as his special skill that hypothetical person should still hit Super Leaf. We could just add a Mario Kart series "sentence long section with a {{main}} link" to Raccoon Mario to patch that hole up, and maybe note that giving Tanooki Mario the Super Leaf as a special skill closely reflects the platforming video games, meaning we have all the links the Tail whip article would have without needing to make a Tail whip article.Salmancer (talk) 21:22, March 17, 2025 (EDT)

IMO this just sounds like a lot of confounding mental gymnastics to me and just having a page for the move removes most of the leaps of logic and assumptions on what people will and will not know. Doc von Schmeltwick (talk) 22:02, March 17, 2025 (EDT)

On the leading "Princess" for Peach/Daisy/Rosalina, and/or lackthereof

Brace yourselves--this is gonna be a long one.

In July of last year, jan Misali created a proposal to remove the leading "Princess" from the article name for "Princess Daisy". This failed 15-18, as people were interested in a proposal to move Peach alongside this. In November of last year, jan Misali created a follow-up proposal do exactly this, which failed again; among other concerns regarding redirects, most of the support was split between moving both Peach and Daisy to their Princess-less counterparts, and just moving Daisy, leaving the opposition in the lead. Guess third time's the charm.

The question is simple; do we remove "Princess" from the names of the Princess Peach and Princess Daisy articles? Time and time again, we've removed or truncated full names or particles to more common names. However, for whatever reason, the "Princess" particles for Peach and Daisy stick, despite Nintendo being very hit-or-miss about how required these are, especially for Daisy, whose "Princess, despite never doing anything royal outside of her debut" status has been acknowledged, officially, multiple times.

To recap the cases in favor of these renames for people that didn't read those first two proposals, the case for Daisy in particular is very strong, so we'll start with her. Simply put, Nintendo so rarely calls her by the name of "Princess Daisy" that it's starting to become a surprise when they do call her that in things like HotWheels character cars. To re-iterate a point made in jan Misali's original proposal, the count of times where Daisy is overtly referred to as "Princess Daisy" outside of manuals or other such paratexts can be counted on two hands, and even then, only barely; once in Super Mario Bros. Print World (which also erroneously calls Peach "Daisy" at one point), the two baseball games and Fortune Street interchange "Daisy" and "Princess Daisy" in dialogue but all UI uses just "Daisy", Super Mario Run being in a similar boat but with in-game descriptions for Remix 10 instead of dialogue, and Super Smash Bros. Ultimate, where Palutena calls her that. In every other case, including her own debut game, she is generally called "Daisy".

For Daisy, there is also the strange asterisk that is her film equivalent, but given the context of the plot of the film itself--that Daisy is unaware of her own royal status for the bulk of the film, and is simply referred to as just "Daisy" for most of it, we personally think it's fair to move her to "Daisy (film character) and add a Full Name parameter to clarify her "Princess Daisy" title she has towards the end. That being said, even her own official trading card just calls her Daisy, and apparently the "Princess Daisy" title only gets dropped on the back of "Sad Goodbyes", which we lack an image for.

The case for Princess Peach is less strong, partially thanks to the release of Princess Peach: Showtime!, a game in 2024 that makes rather overt use of "Princess Peach"; however, it is worth noting that Nintendo still does play rather fast-and-loose with the "Princess" particle for her as well. Most spinoffs will truncate the "Princess" off of her name, as far back as Mario Kart 64 and even after the release of Showtime, later that same year, Super Mario Party Jamboree also truncated the "Princess" off of Peach's name. While we acknowledge it's odd to laser in on exactly one game, Mario Kart 8 Deluxe just calls her "Peach", and that is one of the best-selling games in the entire Mario franchise.

We've seen various arguments against these, and aside from "personal preference for preferring particles", which we obviously can't argue with (at least, not without looking silly), we can't say we understand the majority of them:

• Concerns were risen about removing royalty particles from other article names, such as Princess Shokora or Princess Shroob or King Bob-omb or Prince Mush (never mind that in his case, it's a stage name and not royalty). In those cases, the characters have never been referred to without their particles that we could find unless there was already an older name in the first place, such as "Big Bob-omb" for "King Bob-omb" (it's possible there's remote dialogue or an obscure Manga appearance we don't have on-record, but we're doubtful). These would retain their particles, as per our Naming policies determining that the most common English name is what is used, and in these cases, the particle is included almost 100% of the time. In contrast, Nintendo has been fairly interchangeable with Peach and Daisy's "princess" particles, and in Daisy's case, her particle has only become increasingly rarer as time goes on. If instances were located where the aforementioned characters lacked their particles short of the Big/King Bob-omb example, that would be something worth acknowledging, but in their cases, the particles being excluded is overwhelmingly the exception, not the norm.
• Concerns have been risen about the Peach and Daisy article titles potentially referring to generic subjects; however, as of writing this proposal, both "Peach" and "Daisy" directly lead to their corresponding princesses anyways by means of redirects. Other subjects are instead given a "For <x>, see <y>" in the Princess' articles introductions. These redirects are already present as-is, and these changes wouldn't change how a search lands.
• For internet traffic, given Peach and Daisy already lead to these articles, we still fail to see how this would impact much, unless we intentionally chose to not leave a redirect after a move; it should go without saying that, if we were to make a move of this magnitude, we would absolutely be leaving a redirect.
• On a meta level, for the "would prefer one, but not the other" angle that was part of the reason the second proposal failed, we have since introduced a poll format to more adequately determine more nuanced situations like this, without risking support being split between two groups and being out-numbered overall.
• While this was not mentioned in the original proposals to our awareness, we do acknowledge that some people may be concerned about the costs of labor of changing a bunch of links; however, not only could this trivially be an automated rename, something our proprietor already does fairly regularly with template names, even if this were somehow unworkable, we already have ample tools to manually perform such a change built into MediaWiki itself. We are well-aware of what this wiki's userbase can do when it comes to making these mass-changes, and we think we have a very capable userbase when it comes to deploying a change like this, either automatically or by hand.

There are also two characters we think are worth acknowledging, one brought up by jan Misali when we shared this proposal's draft with them, and one we noticed ourselves. For jan Misali's part, there's Bowser, or rather, King Bowser... Or rather, how in-frequently Bowser is known as "King Bowser". It's to the point where mentions of "King Koopa" as he appears in the DiC cartoons severely outnumber the amount of times Bowser is actually called "King Bowser" outright. This is exceedingly non-contentious, and while a King Bowser redirect has existed since 2006, we can't tell when the last time "King Bowser" was overtly used in dialogue. All we can really say is, having played Minion Quest: The Search for Bowser recently, it's not in that, with Bowser usually just being referred to as, well, Bowser, with the occasional uses of "Lord" or other offbeat honorifics instead of "King".

However, to us, the real smoking gun for why a move like this would not only make sense, but be perfectly fine for the wiki, has been sitting right underneath our noses the entire time. Rosalina, or should we say Princess Rosalina? Rosalina has been called a Princess from sources dating as far back as 2010 and as recently as 2023. She's commonly colloquially known as a Princess by fans. Heck, Princess Rosalina is, as of writing this proposal, a valid redirect to her article, and her infobox states her full name is "Princess Rosalina". However, her article has sat at the title of "Rosalina" since its inception back in 2007, with the Princess redirect only being made in 2014. Rosalina is a Featured Article, so her page naturally receives a lot of traffic and scrutiny, but nobody seems to have questioned if it would be worth moving her article to "Princess Rosalina" to match the other two princesses; and while one could argue that Rosalina is "not much of a princess", that naturally begets the response that neither is Daisy, who keeps the particle anyways. There's not really any reason we can think of why Daisy should keep her particle if Rosalina hasn't ever held one and it's seemingly never been questioned, and from there, we could understand removing the particle from Peach's name for parity's sake. (Even still, if you really wanted to, we've provided an option to, in addition for what to do to the "Princess" particles in Peach & Daisy's names, if we should add one to Rosalina's name, or keep it absent. We don't really intend to include something like this for "King Bowser" as, while "Princess Rosalina" at least has a plurality number of cases we could find of that name being used, we could literally only find one "King Bowser", in Nintendo Comics System.)

Proposer: Camwoodstock (talk)

Do we have a "Princess" particle for Princess Peach?

Deadline: April 2, 2025, 23:59 GMT

Yes Princess (status quo)

1. Waluigi Time (talk) Per past me: "I don't think focusing in so heavily on the exact places or times the full names vs. the shortened names are used is beneficial if those names are still in frequent use. [...] Princess Peach is still very commonly used, the average person knows her by that name, I don't see a need to change it." Considering Nintendo used her full name in a game title last year, this would be a really odd time to do it, and it sheds some light on how awkward it is putting so much focus squabbling over the specifics of character select screens and the like, IMO. I don't see a consistency issue with Daisy regardless of what happens with her, they weren't designed to be perfect analogues to each other and are used in different contexts, which also informs Nintendo's usage of their full titles.
2. Technetium (talk) Per Waluigi Time, past and present.
3. Nintendo101 (talk) Much like Daisy, "princess" is scrapped in material where you play as Peach, potentially because they want a more familial sounding moniker for such contexts where you play as her, or they want to be conservative with text on character selection screens. That does not make "Princess Peach" erroneous, archaic, unused, or inappropriate for the title of an article. This is an even stronger case for Peach because she shows up more often in non-playable appearances, where she is typically called "Princess Peach," and they represent the bulk of her history. It is the name used in most instruction booklets, toys, and even in-game. It is not the end of the world for her article to simply go by "Peach," but there is also nothing incorrect or erroneous with maintaining that. "Peach" is more so a shorter derivative of "Princess Peach" than "Bowser" ever was of "King Bowser" or anything like that (and certainly more so than "Princess Rosalina" is for "Rosalina.") You can probably count the number of sources that prefer using that name for him on one hand, unlike Peach.
4. Rykitu (talk) All 5 Princess Peach games have "Princess" before "Peach" (with the exception of Peach's Puzzle and Parasol Fall, unless you count it's full title being Super Princess Peach — Parasol Fall). It is also used way too commonly by Nintendo so I think it should stay the way it is.
5. LadySophie17 (talk) Per Waluigi Time and Nintendo101
6. SGoW (talk) Per all.
7. Pseudo (talk) While I can understand the desire for consistency with the other two princesses, Princess Peach is clearly her full name, being used in the titles of games as well as regularly in various bits of dialogue and paratext. It's true that she's usually just Peach in a character select screen, but I don't think this defines how she is overall perceived... in my subjective experience, she would usually be known by the average person aware of Mario as Princess Peach.

No Princess

1. Camwoodstock (talk) Per proposal. While we think the arguments for keeping Peach's particle are the strongest, namely since we have an entire game from 2024 with the particle in the name, we do think if we remove this from Daisy, we should naturally remove this from Peach for the sake of parity.
2. LinkTheLefty (talk) Abolish the monarchy.
3. JanMisali (talk) Per proposal, and per my previous proposals.
4. Super Mario RPG (talk) "Princess" is not part of the name, it's just a title and not as integral to Peach's identity as, for example, Dr. Mario.
5. Ahemtoday (talk) It's just "Peach" on stuff like character select screens, which I think are the most comparable source for article title formatting.
6. EvieMaybe (talk) per all
7. Blinker (talk) Per all. And the use of "Peach" in character select screens is an intentional choice, not due to character constraints, as shown by the existance of names like "Light-blue Shy Guy (Explorer)".
8. SolemnStormcloud (talk) Per all. I'm still not a fan of using abridged names—especially for crossover characters like Fox, Sonic, etc.—but if we want to be consistent about it, something's gotta give.
9. Pizza Master (talk) per all

Do we have a "Princess" particle for Princess Daisy?

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

Deadline: April 2, 2025, 23:59 GMT

Yes Princess (status quo)

1. Nintendo101 (talk) In my view, "Princess" is scrapped in material where you play as Daisy, which happen to represent the bulk of her appearances. Perhaps they want a more familial sounding moniker for such contexts, or they want to be conservative with space on character selection screens. That does not make "Princess Daisy" erroneous, archaic, or unused. It is the name used in Super Mario Land, the Super Mario Bros. Encyclopedia, and licensed promotional toys and products of Daisy, where she is called "Princess Daisy." It is not the end of the world for her name to go by something else, but there is also nothing incorrect or erroneous with maintaining the status quo.
2. LadySophie17 (talk) Per Nintendo101
3. Pseudo (talk) Even if she is to be referred to as Daisy most of the time, Princess Daisy is still clearly her "proper" name in my view. This falls into a similar category to my views on the Peach situation (or Princess Peach, as the case may be); even though it's less supported by in-game usage and the like, this is still the main name that she is known by.

No Princess

1. Camwoodstock (talk) Per proposal. To be honest, this has never been a contest for us; as far back as flavor text in Mario Party 9, Nintendo has acknowledged the weird lack of Damsel-in-distress-ness to Daisy's character, and the usage of "Daisy" in lieu of "Princess Daisy" is as old as Super Mario Land itself. That Daisy's royalty is bordering on in-name only post-Land is practically a defining trait of hers.
2. Hewer (talk) Per the trilogy of proposals, this is the name that is almost always used for this major character and it is bizarre that we aren't reflecting that. This should've happened long ago, hopefully this new poll format will finally allow it to. I think I'm neutral regarding whether to move Peach, since it's much less immediately obvious which of her two names is most commonly used.
3. LinkTheLefty (talk) Per last times.
4. JanMisali (talk) Per proposal, and per my previous proposals.
5. Super Mario RPG (talk) Since I'm supportive of "Princess" being removed from Peach's article title, the same would apply to Daisy, who has made fewer appearances, including with the "Princess" title.
6. Cadrega86 (talk) Per all three past proposals.
7. Ahemtoday (talk) Forgive the copy-paste job, but: it's just "Daisy" on stuff like character select screens, which I think are the most comparable source for article title formatting.
8. EvieMaybe (talk) per all
9. Blinker (talk) Per all
10. Tails777 (talk) Per all the points made on past proposals. I feel nothing more needs to be added.
11. Rykitu (talk) Per proposal.
12. SolemnStormcloud (talk) Per all.
13. Pizza Master (talk) per all.

Do we have a "Princess" particle for Princess Rosalina?

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

Deadline: April 2, 2025, 23:59 GMT

Yes Princess

No Princess (status quo)

1. Camwoodstock (talk) Per proposal. We hope we've made it apparent that we think adding the particle to Rosalina's article is very silly indeed, especially decades after the fact, when Rosalina has obtained a featured article without the particle, and when Rosalina is about as much of a princess as Daisy.
2. Hewer (talk) She's barely ever called that.
3. LinkTheLefty (talk) Queen it up.
4. Nintendo101 (talk) Unlike the other two, there is no substantial media that refers to Rosalina as "Princess Rosalina." It is presented only in larger descriptive material on Rosalina, and even then, only occassionally.
5. Waluigi Time (talk) If anything, cases where Princess Rosalina is used are the clear outlier.
6. Doc von Schmeltwick (talk) - She's clearly a queen, just sometimes lumped as one of "the princesses" for convenience.
7. JanMisali (talk) Per proposal. It's unclear if Rosalina is even really a princess in the first place.
8. Super Mario RPG (talk) I don't think I ever recall it being used.
9. Cadrega86 (talk) Per all.
10. Ahemtoday (talk) Princess of what, by the way? Princess of space? Can you be the princess of space?
11. EvieMaybe (talk) princess of acoustic rock, obviously.
12. Blinker (talk) Per all
13. Tails777 (talk) Per all.
14. Rykitu (talk) Per all.
15. LadySophie17 (talk) Per all. Her backstory implies she was one, and she carries the appearance of one, but it is certainly not one of her defining characteristics.
16. SolemnStormcloud (talk) Per all.
17. Pseudo (talk) She's straight-up never referred to this way except in supplementary material like websites, not even the Super Mario Galaxy manual calls her Princess Rosalina. This is pretty clear cut to me.
18. Pizza Master (talk) In Chapter 7 of Rosalina's Story, there is a castle in the background that is implied to be Rosalina's house. Quote Rosalina, "I want to go back to my house by the hill!" The only visible "house" by the hill is the castle. So it's likely that she was born to royalty on her home planet. That said, Daisy has no princess particle, so Rosalina shouldn't either just going off precedence.

Comments (Princess Particle Party!)

Should be of note that Palutena's Guidance is not the only part in Ultimate in which Daisy is referred to as "Princess Daisy" (obviously this also applies to Peach). rend (talk) (edits) 14:23, March 19, 2025 (EDT)

I can't track down the article (iirc, it was translated by SourceGaming), Masahiro Sakurai prefers dropping royal monikers in Smash Bros. games. If I recall correctly, it is to make the character more familial to the player and conserve textual space on the character selection screen. King Dedede is only called "Dedede" in the Japanese releases of the Super Smash Bros. games. That does not mean "King Dedede" is not a more complete rendering of his name. - Nintendo101 (talk) 14:44, March 19, 2025 (EDT)

King K. Rool is called that in Smash, so it's clearly case-by-case (and I thought the "saving space on the character select screen" argument was debunked last time by Light-blue Shy Guy (Explorer)). Anyway, why should a "complete" name automatically be more desirable than the name that is actually used in pretty much every appearance of the character? As was mentioned in the proposal, we've established in cases like the Koopalings that the longest name doesn't have to be the name we use. What makes Daisy different? (Honestly, "Princess Daisy" probably has less of a claim to being an article title than the Koopalings' full names do.) Hewer (talk · contributions · edit count) 15:01, March 19, 2025 (EDT)

@Hewer I was referring to the Super Smash Bros. series and the people involved in the decisions for that series. None of them made Mario Kart Tour, a more contemporaneous game. Peach has been playable in spinoffs since the 1990s and Daisy has been since 2000, where trends like this would be established on hardware more limited, and by people who may have different views on how to render their characters' name on selection screens. In Melee, for example, a game with Peach, they call Captain Falcon "C. Falcon" on the selection screen. They probably could have rendered his name in full like they did for the Ice Climbers, but they didn't. - Nintendo101 (talk) 15:15, March 19, 2025 (EDT)

I was replying to your vote on Daisy as well as your comment, sorry if that wasn't clear. Either way, I don't really understand the point you're making here. My point stands that Light-blue Shy Guy (Explorer) is in the same game as just Daisy. Captain Falcon is in Super Smash Bros. Ultimate with just Daisy. Can you name any games that call her "Princess Daisy" on a select screen (or other similarly prominent context besides "random line of dialogue", for that matter)? I'm not aware of any. Surely if all the different people working on different games came to the same conclusion that it should be Daisy rather than Princess Daisy, that's more reason for us to move it? Hewer (talk · contributions · edit count) 15:32, March 19, 2025 (EDT)

@Hewer In regards to "King K. Rool" - that's probably because every single language literally calls him that (at least in-game). In contrast, the reason Peach, Bowser and Dedede aren't Princess Peach, King Bowser and (JP-set) King Dedede is likely because they're literally Peach-hime, Daimaō Koopa and Dedede-daiō, respectively. Yes, these are simplified translations, but the nuance is different. The titles are probably getting mostly phased out because Nintendo likes it when the names of their major characters don't have to change much between regions. For example, one interview where Takaya Imamura regretted not unifying Star Fox's Andorf as "Andross" from the start. This was also done with the big Legendary Pokémon, as I recall, etc. LinkTheLefty (talk) 17:10, March 19, 2025 (EDT)

How is Rosalina a queen, exactly? I don't think that's ever been stated anywhere, and Peach is still Princess even though she explicitly rules the Mushroom Kingdom, so Rosalina ruling something wouldn't make her Queen necessarily. Speaking of, even if she's not technically ruling anything now, she's still a princess by birth (backstory and Baby Rosalina's design), and I don't think titles become null and void like that / "oh it's been (blank) years I guess I'm not a princess anymore". Technetium (talk) 16:03, March 19, 2025 (EDT)

Miscellaneous

None at the moment.