MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
 
Line 1: Line 1:
<table style="background:#fefffe;color:black;-moz-border-radius:8px;border:2px solid black;padding:4px" width=100%><tr><td>
{{/Header}}
<div class="proposal">
==Writing guidelines==
<center>http://img33.picoodle.com/img/img33/9/9/17/f_propcopym_9045f2d.png</center>
''None at the moment.''
<br clear="all">
 
{| align="center" style="width: 85%; background-color: #f1f1de; border: 2px solid #996; padding: 5px; color:black"
==New features==
|'''Proposals''' can be new features (such as an extension), removal of a previously added feature that has tired out, or new policies that must be approved via [[Wikipedia:Wikipedia:Consensus|consensus]] before any action(s) are done.
===Establish a format for poll proposals on the archive lists===
*Any user can support or oppose, but must have a strong reason for doing so, not, e.g., "I like this idea!"
Something that's slipped through the cracks when we invented poll proposals was what we do when we add them to [[MarioWiki:Proposals/Archive|these]] [[MarioWiki:Proposals/TPP_archive|pages]]. We can't simply have one link to the poll proposal — the entire purpose of the format is that different parts of it can pass and fail independently of one another. What color do we put a proposal where one thing fails and another thing succeeds in?
*"Vote" periods last for one week.
 
*All past proposals are [[/Archive|archived]].
I have several pitches for you.
|}
 
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 <nowiki>{{user|</nowiki>''User name''<nowiki>}}</nowiki>. '''Signing with the signature code <nowiki>~~~(~)</nowiki> is not allowed''' due to technical issues.
<big>'''''OPTION ZERO'''''</big><br>
Do nothing. I'm putting this at the front because I want to leave room for any good-sounding solutions beyond the four I'm about to suggest. <s>It's here on the proposal at all because I'm pretty sure I'm legally obligated to put it here, but I'll be honest — I'm not entirely sure what this winning would... mean. Our hand will eventually be forced when our first poll proposal fully resolves, so a format will be established one way or the other.</s>
 
''EDIT: It has been helpfully pointed out that there is a [https://www.mariowiki.com/index.php?title=MarioWiki:Proposals/Header&diff=prev&oldid=4772367 current policy] — they are red if they all issues fail, gray if at least one passes and is unimplemented, and green if at least one passes and all issues are implemented. A "one issue changes the color" kind of rule. It's definitely not insensible, but I feel that we could be conveying more information. Still, even if  this if the "fail option", we have a policy now, so I got what I wanted even if this one wins.''
 
<big>'''''OPTION ONE'''''</big><br>
The different issues of a poll proposal share a number corresponding to when the first issue closes. They're listed separately, and distinguished from each other via letters. As an example, the three parts of [[Talk:Yoshi_(species)#Properly_define_Brown_Yoshi|the Brown Yoshi proposal]] would slot in at #83A, #83B, and #83C. (That would shove some other proposals down; we could also just append them to the end of the list like normal and brush off the inconsistency if y'all prefer.)
 
The Brown Yoshi proposal is also a handy demonstration of an edge case we have to contend with — if this proposal passed ''right now'', we would list #83A as red and #83B as gray, but what would happen with #83C, which is still ongoing? This is the aspect on which Options One and Two differ. In Option One, issues are not added to the archive page until they close. The page would only contain #83A and #83B if the proposal passed right now, with #83C being added later


<h2 style="color:black">How To</h2>
I would like to note that the Brown Yoshi proposal is a remarkably well-behaved example. If the issues were ordered differently, we may at one point have #83A and #83C on the list with no #83B until later.
#Actions that users feel are appropriate to have community approval first can be added by anyone, but they must have a strong argument.
#Users then vote and discuss on the issue during that week. The "deadline" for the proposal is one week from posting at:
##Monday to Thursday: 17:00 (5pm)
##Friday and Saturday: 20:00 (8pm)
##Sunday: 15:00 (3pm)
#Every vote should have a reason accompanying it.
#At any time a vote may be rejected if at least '''three''' active users believe the vote truly has no merit or was cast in bad faith. However, there must be strong reasons supporting the invalidation.
#"<nowiki>#&nbsp;</nowiki>" should be added under the last vote of each support/oppose section to show another blank line.
#At the deadline, the validity of each vote and the discussion is reviewed by the community.
#Any proposal that has three votes or less at deadline will automatically be listed as "[[Wikipedia:Quorum|NO QUORUM]]." The original proposer then has the option to relist said proposal to generate more discussion.
#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 a sysop, the proposer can ask for that help.


The times are in EDT, and are set so that the user is more likely to be online at those times (after school, weekend nights).
<big>'''''OPTION TWO'''''</big><br>
Option Two is identical to Option One except in how it handles open issues on partially closed poll proposals. In this option, they ''are'' added to the list alongside the other issues, and marked with a new color — let's say black.


So for example, if a proposal is added on Saturday night at 11:59 PM EDT, the deadline is the next Saturday night at 8:00 PM. If it is indeed a minute later, the deadline is a day plus 15 hours (Sunday), as opposed to a day minus 4 hours.  
This prevents the awkward gaps we would be susceptible to in Option One, but it ''is'' introducing a whole color for a temporary edge case.


Also,
<big>'''''OPTION THREE'''''</big><br>
<br><span style="font-family:sans-serif;font-size:30px;line-height:30px;font-weight:900;">NO PROPOSALS ABOUT HAVING BANJO AND CONKER ARTICLES</span> -The Management.
Option Three is simpler. We create a new color in the archive for poll proposals — I guess let's say black again. Poll proposals get added to the archive when all issues on them are closed.


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


<center><span style="font-size:200%">CURRENTLY: '''{{LOCALTIME}}, {{LOCALDAY}} {{LOCALMONTHNAME}} {{LOCALYEAR}} (EDT)'''</span></center>
''EDIT: Camwoodstock's pitch below of using three colors (and, implicitly, adding the poll proposal to the archive when it has any closed issues) doesn't entirely eliminate that negative, but it does seem much more useful than just having the one color.''


==New Features==
<big>'''''OPTION FOUR'''''</big><br>
''None at the moment.''
Option Four is simpler still. Each issue is treated as if it were an entirely separate proposal. Each gets numbered and appended to the list when it closes regardless of what anything else in the poll proposal is up to.


==Removals==
The negative of this way of doing it is that the issues of a poll proposal may end up strewn about the list in a way that doesn't really reflect that they're a related thing.
==="Repeal "Featured Article Voting Modification"===
I'll just cut to the chase here: I propose we repeal [[MarioWiki:Proposals/Archive#Featured_Article_Voting_Modification|this proposal]].


Now, this proposal was accepted very well. Many people thought that it would be the best option available for the wiki. It seemed so at the time. However, there are many faults in this system:
'''Proposer''': {{User|Ahemtoday}}<br>
'''Deadline''': March 18, 2025, 23:59 GMT


*As per [[MarioWiki_talk:Featured_Articles#Problem_with_New_Rules|this comment]], the votes can be removed as soon as three users call for the deletion of a vote. This can mean a five-minute discussion and then a deletion of any vote.  
====Option Zero====
*The original proposal said: <blockquote>ONLY FAN VOTES WITHOUT FURTHER REASONING [...] CAN BE REMOVED!</blockquote> Now look at one of the support votes for [[MarioWiki:Featured Articles/N/Paper Mario|Paper Mario]]: "''Awsome!''" It is obvious that it is a vote without further reasoning. It is anything but obvious, however, that it is a fan vote, because it possibly refers to the quality of the article. So, can this vote be removed or not? Pointless discussions could evolve around issues like this.
#{{User|Jdtendo}} Per Porple "Steve" Montage in the comments.
*Flame wars could be a big factor in this system. If a (*ahem* ''volatile'') user opposes a vote of another easily distressed user, it could be a long and bad flame war, and would probably draw other users in. This would cause tension and distrust between the users and may lead to other problems.
#{{User|Waluigi Time}} Per Porple.
*Anyone who opposes a removal does not need to give a reason. Take the comments of [[MarioWiki:Featured_Articles/N/Petey_Piranha|this page]] for example. Time Q is able to just oppose the removal and is not forced to give his thoughts on ''why'' it should stay.
#{{User|EvieMaybe}} perple montage
*It's a useless system. One single oppose vote can cancel out an infinite number of support votes. Which gives us the question: Why do we need this system in the first place? Also, only five support votes are necessary to Feature an article with no opposes. So, most of the time, there are already enough legit votes to feature an article even if all the fan votes are removed.
#{{User|Camwoodstock}} Per Porple in the comments, though admittedly this is more of a secondary option to our more robust version of Option Three we pitched. Status quo isn't the ''worst'' thing in the world, and we do acknowledge our more robust solution of "dark colors" may be a bit harder to convey as we've been slowly rolling out... Well, a dark mode for the ''whole wiki''. (If it was down to us, the poll proposals would use lighter colors in dark mode, before you ask; of course, if that option somehow wins, we'd be down to help fine-tune it.)
#{{User|Arend}} Per Porple.
#{{User|Nintendo101}} Per porplemontage.
#{{User|Salmancer}} Oh, huh. I suppose this is a solved problem then.  


To cut a long story short, the new system tries to regulate things ("useless" support votes) that don't need to be regulated (because support votes don't really matter). '''There is no need whatsoever to regulate support votes.''' If the rules were simple and clear, we could accept them (even though they would still be rather useless), but they pose several problems, as pointed out above. There was one good thing about this proposal, however. This was the following portion: <blockquote>[...]OPPOSE VOTES THAT ARE NOT CLARIFIED CAN BE REMOVED[...]</blockquote>This was the one good thing because it allowed users to get rid of oppose votes that were impossible to appease or unneeded to the article. I also propose that, after repealing the current system, that we restore this option for users. The restoration would come with some differences from the original proposal, however: '''Five''' users, including a sysop, must vote to remove the vote, and each remover must have a valid reason for the removal.
====Option One====
#{{User|Ahemtoday}} It's either this or Option Two for me — it's important to me that the issues end up next to each other on the archive ''and'' that the status of each one is visible on the page.
#{{User|Salmancer}} There's no rule saying a poll proposal has to be for small things, since part of the premise was reducing the need for large numbers of combination options. There could be poll proposals that have wide scopes, and as such I think we're going to have to stomach the poll proposals with 10+ proposals in them to make it easier to track policy without thumbing through old proposal pages. Also an archive is for the past, not the present.


You now have our opinions. Users of the MarioWiki, you must now vote on what you think is best. Take your time, review our points, and make sure that you make the best decision possible.
====Option Two====
#{{User|Ahemtoday}} See my note about Option One.
#{{User|Camwoodstock}} Secondary option, but we do think darker shades of the colors (a-la our pitch for Option Three) would be nice. Helps distinguish at a glance what was a poll proposal.


'''Proposers:''' {{user|InfectedShroom}} and {{user|Time Q}}<br>'''Deadline:''' Thursday, June 5<sup>th</sup>, 2008, 17:00
====Option Three====
#{{User|Camwoodstock}} We would like to pitch a more sophisticated variant of this; 3 new colors. One for a poll that has concluded, one for one that's partially ongoing, and one for a poll that has been partially overturned by a future proposal. Maybe dark green, dark gray/maybe a de-saturated dark green a-la the Shroom Spotlight template, and a dark yellow? The darker colors, of course, to contrast with the non-poll proposals. (On dark mode, we'd probably make these lighter, rather than darker, provided we actually even add dark mode compatibility to the proposal archive colors.)
#{{User|Rykitu}} Per all.
#{{User|Ahemtoday}} I definitely see the appeal in having poll proposals under a singular listing, but I think they'd be better served by having one or multiple new colors rather than using the standard red and green.


====Support (Repeal proposal and restore the option to discuss oppose votes)====
<s>#{{User|Jdtendo}} Listing every single poll would probably take a lot of space whereas the whole purpose of a poll proposal is bringing together many similar polls that would be too cumbersome to handle separately. I would prefer having a single proposal listed as "Determine what memes should be on the Internet references page" that users can click on to check the detailed results rather than cluttering the list with a dozen links.</s>
#{{user|InfectedShroom}} - My reasons above.
#{{user|Time Q}}: Per IS and myself. In short: There are several problems arising with the new system, some of which surely could be solved, but it's simply not worth the time and work, because it's a simple as that: Support votes don't change nothing, only oppose votes do. Even so-called "fan votes" don't hurt anyone, ergo no need to waste our time discussing them.
#{{user|Toadette 4evur}} Per IS and Time Q. Before we know it, all the FA nomination pages will be empty if we keep this system.
#{{user|Glitchman}} Per IS and Time Q.
#{{user|Pikax}} Now this is a much better solution to the problem than the previous proposal was.
#{{user|Blitzwing}} Per my opposition of the Proposal in the first place.
#{{user|Stooben Rooben}} - Per IS and Time Q.
#{{user|Clay Mario}} - Per my opposition of the proposal in the first place.


====Oppose (Keep everything how it already is)====
====Option Four====


====Comments====
====Comments====
=====Comment One=====
{{@|Camwoodstock}} — I definitely think your pitch for Option Three is better than the version I was suggesting. I'm not really sure about the pitch for Option Two, though — the letters already distinguish them, and I feel like they'd seem more like separate states rather than a "modifier" on some of the existing ones. Not to mention, wouldn't we need a darker version of every single color just in case? That's a lot of changes to make, and we'd end up running into problems with dark blue, teal, and dark teal; or "dark white", gray, and dark gray. [[User:Ahemtoday|Ahemtoday]] ([[User talk:Ahemtoday|talk]]) 03:20, March 4, 2025 (EST)
I'm beginning to think that I voted too quickly and rationally on the last proposal. I didn't really think through with ''what'' I was saying should be done to the FA pages. While I find it quite necessary to remove fan support votes (due to the fact that they are merely biased votes about the character and not the article itself), I also find non-descriptive oppose votes to be invalid. If a user merely states, "the article has bad writing", or "some areas need expansion" it does not help the decision to feature said article whatsoever. I feel that oppose votes should be quite informative as to what that user feels is wrong with the article. For example, rather than stating "some areas need expansion", one should state "while parts of the article are thoroughly written, I find that the ''Yoshi's Safari'', ''Super Mario Galaxy'', and ''Other Appearances'' sections are quite minimal". I'm not requesting that every opposer speak in "fancy words", I merely believe that the opposers state precisely '''which section(s)''' require work; by doing so, others can fix the "bad" area(s) of the article, making the article more suitable for an opposer to become a supporter. {{user|Stooben Rooben}} 18:59, 29 May 2008 (EDT)
:Well, that's what we are trying to fix here; if a oppose vote is too vague, the users shall discuss it, and if the original opposer does nothing about it, their vote can be removed, as we don't know which sections they are talking about. ;) {{user|InfectedShroom}}
::Thanks. I'll support then. {{User|Stooben Rooben}} 23:18, 30 May 2008 (EDT)


=====Comment Two=====
I don't quite understand option one and two, as the above rules for poll proposals state "A poll proposal closes after all of its options have been settled, and no action is taken until then. If all options fail, then nothing will be done." --[[User:PopitTart|PopitTart]] ([[User talk:PopitTart|talk]]) 07:09, March 4, 2025 (EST)
There is only one certain thing about our FA problem: there is no simple solution. It is our own users who are not as professional as Wookiepedia and the other successful non-Wikipedia wiki communities out there. We are more loose on purpose to make others feel welcome, and with the good things that come with it come some drawbacks as well. There may be no solution at all, as long as users continue to care mostly about their Userpedia content and their status in the community, not just how our articles are coming along. {{user|Wayoshi}} 21:53, 29 May 2008 (EDT)
:Could you explain the contradiction in greater detail? I don't see what you mean. [[User:Ahemtoday|Ahemtoday]] ([[User talk:Ahemtoday|talk]]) 12:01, March 4, 2025 (EST)
:(Yes, I know this is not related to the proposal, but I need to get it out of my chest)  
::The options say "The page would only contain #83A and #83B if the proposal passed right now, with #83C being added later" and "...how it handles open issues on partially closed poll proposals" there shouldn't be any instances of archiving partially closed poll proposals, they only close all at once when every entry has been resolved.--[[User:PopitTart|PopitTart]] ([[User talk:PopitTart|talk]]) 20:07, March 4, 2025 (EST)
:::So is your position that we should use the lettering scheme from Options One and Two, but only add poll proposals to the archive page when all of their issues are closed? I don't think I agree, but I can add that as Option Five if that's what you want to vote for. [[User:Ahemtoday|Ahemtoday]] ([[User talk:Ahemtoday|talk]]) 22:48, March 4, 2025 (EST)


:I see your point, but you're off by a bit. The users as a whole aren't any more professional at Wookiepedia, Bulbapedia, etc. than they are here. They just happen to be blessed with a large number of skilled editors, as we are. All communities have issues with users who care more about status than editing. All. Look at Wookiepedia that limits the amount edits to ones userspace, or Bulbapedia that has suspended all userspace edits entirely. What you seem to be expecting from the community is nearly impossible. -- {{user|Ghost Jam}}
I feel like [https://www.mariowiki.com/index.php?title=MarioWiki:Proposals/Header&diff=prev&oldid=4772367 this] is fine. Either it's red (no change from the status quo so nothing needs to be done), gray (''some'' change was established and there is work to do), or green (some change was established and it's all done). There are other proposals where people list [https://www.mariowiki.com/MarioWiki:Proposals/Archive/70#Clarify_coverage_of_the_Super_Smash_Bros._series several things] to be done, it's not that different, it's just that now we have the ability to vote on each individual thing. But in either case you just click the link to read exactly what was approved. --{{User:Porplemontage/sig}} 10:56, March 7, 2025 (EST)


I find kinda ironic (and rather hypocritical) that you patronise users over the "lack of proffesionalism" of their edits even thought you haven't yourself made any signifiant mainspace contribution in '''over a year'''. Hypocrisy much? {{User|Blitzwing}}
==Removals==
:I'll be the first to admit that I am in the same club as Wayoshi, but let's not turn this into anymore than just a discussion. -- {{user|Ghost Jam}}
 
==Splits & Merges==
''None at the moment.''
''None at the moment.''


==Changes==
==Changes==
===Humourous Image Captions===
===Give ''Taiko no Tatsujin'' an article===
'Nuff said. Nah, I'm just kidding. OK, so, a long, long time ago, we removed clever/witty/humourous image captions from the Wiki. The only one I can remember so far was the [[Groove Guy]] caption, which stated "Groovy.", but there were plenty across the Wiki, I'm sure. While most would consider this "unprofressional", with clever headers like "Sharp Shooting" or "Mario and the Seven Koopa Hotels", which were deemed allowed in a previous Proposal, surely we can stand to add humourous captions to images (of course, so long as it abides to the rules).
''Taiko no Tatsujin'' has had numerous crossovers with the ''Mario'' franchise throughout its history. This extends to not only the songs being playable, but actual ''Mario'' characters showing up and being animated in the accompanying videos in the earlier games.
 
*The DS version has "Super Mario Bros." as a track, [https://www.youtube.com/watch?v=870WLPGnnKs using imagery from the games].
*The Wii version includes "New Super Mario Bros. Wii Medley." and "[https://www.youtube.com/watch?v=RkcrnhCfrtw Super Mario Bros.]" Notably, the videos include [https://www.youtube.com/watch?v=zO31iswKX84 actual characters and imagery from the game showing up]. The former has nearly every enemy from the original ''Super Mario Bros.''
*''Taiko no Tatsujin Wii U Version!'' has "[[Fever]]" from ''[[Dr. Mario]]''. There are also Mario and Luigi costumes for Don-chan and Katsu-chan.
*''Nintendo Switch Version!'' has "[[Jump Up, Super Star!]]" from ''[[Super Mario Odyssey]]''.
*The 2020 version brings back "Super Mario Bros." and "Jump Up, Super Star!", also including a "Famicom Medley" track using "Fever" from ''Dr. Mario''. These tracks are present in many of the arcade versions. Playing "Super Mario Bros." will have mushrooms and [[Super Star]]s appear [https://www.youtube.com/watch?v=8jxXo0oHzZg when notes are hit].
*''Blue Version'' has [[Cappy]] has an equippable hat.
*''Rhythm Festival'' has a medley of music from ''Super Mario Bros.'', re-used from earlier games.
 
''Mario'' has paid it back with the serial-numbers-filed-off ''[[Donkey Konga]]'' and [[Don-chan]] being a playable character in ''[[Mario Kart Arcade GP DX]]''. Since there's overlap between the franchises, and they've had a decent history together, I think ''Taiko'' is deserving of its own article to cover all this in one place.
 
'''Proposer''': {{User|Scrooge200}}<br>
'''Deadline''': March 30, 2025, 23:59 GMT
 
====Support (Bring Us One Degree of Separation Closer to Jimmy Neutron)====
#{{User|Scrooge200}} Per proposal.
#{{User|Camwoodstock}} Makes sense to us; with how many cross references there are both ways, it seems only fair.
#{{User|Hewer}} This should probably be cancelled given the crossover article proposal but I'll support just in case. I previously wasn't sure whether it would get a page under that proposal because the only crossover I knew about was Don-chan being in Mario Kart (and his tiny Smash representation in one of Pac-Man's taunts), but all of this other stuff seems very comparable to what got [[Just Dance (series)]] a page. Now we just need to figure out whether [[Mametchi|Tamagotchi]] gets one...
#{{User|Killer Moth}} Per proposal.
 
====Oppose (No More Megalovania, Please)====
 
====Comments' Perfect Math Class====
{{@|Scrooge200}}, have you considered waiting until the proposal [[#Introducing the crossover article|immediately above]] is finished? You would not need to raise proposal for ''Taiko no Tatsujin'' at all if it were to be pass. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 15:23, March 16, 2025 (EDT)
:Oh, I noticed that, but figured it was more for just ''Zelda''. I'm glad to see we're finally making it out of the Stone Age with our crossover coverage, though. {{User:Scrooge200/sig}} 15:27, March 16, 2025 (EDT)
::''Zelda'' is just the example I worked with. The proposal itself applies to all manner of crossover. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 15:30, March 16, 2025 (EDT)
::{{@|Scrooge200}} By "stone age" I assume you mean it's one of the last steps to becoming a wiki centered completely on ''Super Mario''. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 15:38, March 16, 2025 (EDT)
 
===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 [[Cape Mario|swinging a cape]], [[Flying Squirrel Mario|jumping in the air]], or even a slew of [[Link|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 two 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? Would [[Penguin Mario]] be a stronger article if there was a second article dedicated to Belly Slide? If we gave the field form of [[Luiginoid Formation#Ball|Luiginary Ball]] a page, would it be.a stronger article if there was a second article dedicated to Ball Hammer?
 
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 <nowiki>{{main}}</nowiki> 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)]] ([https://www.mariowiki.com/index.php?title=Dash&diff=4431004&oldid=4421941 Relevant Edit]) and the [[Spin Dash]] ([https://www.mariowiki.com/index.php?title=Dash&diff=4435629&oldid=4431024 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 [[Crate]]s, 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 [[Super move|Supercharge]] and [[Charge (Donkey Kong Country series)|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 [[Crouching High Jump|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 <nowiki>{{main}}</nowiki> 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 [[User:Salmancer/List of methods of flight|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.
 
[[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. [[Tail]]s 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 [[Cape Mario]] and [[Superstar Mario]] into a listicle before this [[Talk:Cape#Clean up this article to include only information in the Super Smash Bros. series|proposal]] reduced it to 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.


And note, I'm only proposing humourous image captions. I'm not proposing any major changes to the article itself, just the images.
'''Proposer''': {{User|Salmancer}}<br>
'''Deadline''': March 31, 2025, 23:59 GMT


'''Proposer:''' {{User|Pokemon DP}}<br>
====Merge moves and Listify Fly: Merge moves to forms, and convert [[Fly]] into a list====
'''Deadline:''' June 5, 2008, 17:00
#{{User|Salmancer}} Per proposal.


==== Allow Humourous Image Captions ====
====Merge moves, Fly is free: Merge moves to forms, but keep Fly as is====
#{{User|Pokemon DP}} - I am the Proposer and my reasons are given... Blah blah blah blah, just vote.
#{{User|Jdrowlands}} - Per DP. This would certainly make the wiki a better place.
#{{User|Blitzwing}} - Per DP.  I agree that we should allow humorous caption It's better to have a witty comment that something retarded like "Mario in  a (game). But the (very few) '''actually informative captions''' (Such as the one on the [[Ninji]] article) shouldn't be destroyed to make way for "Witty" caption.
#{{User|Dom}} - Yeah, seriously, I agree with DP! I love funny captions, especially if they're random. The gaming magazine I read has heaps of good ones, and it really brightens it up. And most of the captions are pretty useless, like a picture of Mario would say something like "Mario wearing his trademark outfit" or something (I made that up).
#{{user|InfectedShroom}} - Hmm... Per Blitz. Captions can tell a lot about a picture. So long as good captions are not lost, this is a good idea.
#{{user|Toadette 4evur}} Per all.
#{{User|Walkazo}} - Per Blitzwing, et al.
#{{User|Glitchman}} - Despite the fact that this proposal seems a bit pointless, I'll side with DP.
#{{User|Wayoshi}} &ndash; see comment below
#{{User|Pikax}} Provided that users don't go over the top with this, I see no reason to oppose.
#{{User|Bob-omb buddy}}As long as it isn't made rude.
#{{User|YellowYoshi398}} - Per DP, but I'm gonna have to say I won't want captions like [http://www.mariowiki.com/index.php?title=Big_Bubble&oldid=40557 this] to reappear...
#{{User|WiiBoy7}} - I think it would be a great addition. It would improve the Wiki in my opinion.
#{{User|Storm Yoshi}} - Kirby Wiki has this and so does Zelda Wiki. I would say Zelda Wiki is more mature (the series being so) so why not here?
#{{User|Clay Mario}} - Per DP
#{{User|Uniju :D}} - Per all
#{{User|Super-Yoshi}} - It will give the wiki a nice touch.
#{{User|CountBlumiere}} - Per Pikax
#{{User|Mumbles}} - Per Blitzwing


==== Do Not Allow Humourous Image Captions ====
====Clip Fly's wings: Do not merge moves to forms, change Fly from an article to a list====


==== Comments ====
====Oppose: Status quo====
I don't know what you mean by "humorous" and I don't know which "rules" you're talking about the captions should abide. I love humor and funny image captions are appropriate for gaming magazines. But you should remember that the MarioWiki attempts to be an encyclopedia. Have you ever seen an encyclopedia with "funny" image captions? I haven't. I'm not saying that the wiki shouldn't be "fun", but when it comes to articles, they should be as neutral as possible. There's also a difference between the [[MarioWiki:Proposals/Archive 2#"Creative" header|"creative headers"]] you're mentioning and humorous image captions, in my opinion. The headers aren't humorous, they're merely an alternative to simply putting the game title as the header. I'm leaning towards oppose, but perhaps you could explain a bit further what you mean by "humorous"? {{user|Time Q}}
#[[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) - Many of the moves in question are used by multiple forms, <s>so attempting to merge them to all separately would violate [[Mariowiki:Once and only once]]</s> {{color|purple|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?
:Actually, the [http://transformers.wikia.com/wiki/Main_Page Transformers Wiki is an encyclopedia] with "funny" image captions, and it's '''used and edited''' by personallities that have worked on the ''Transformers'' brand, so please don't pull out the "IT'S NOT ENCYCLOPEDIC!!!!111!" bullcrap. {{User|Blitzwing}}
#{{User|Nintendo101}} 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.
::I wouldn't say it's bullcrap, 'cause that's how I think it is. Thanks for the example though. The image captions on this wiki (I randomly looked at [http://transformers.wikia.com/wiki/Decepticon Decepticon]) are '''way''' too "funny" in my opinion. I mean, nobody of us would want to change the general style of articles to a more "funny" style (at least I hope so), so why should we do that with image captions? It wouldn't fit the general style of the wiki. {{User|Time Q}}
#{{User|EvieMaybe}} 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.
:::Yeah, that Decepticon article ''was'' a bit too informal, but I dion't think that's what DP's going for with this proposal. His "Groovy" example's good, because it's funny but not unneccesary, especially when the alternative is "A Groove Guy": 99% of the time that would result in a "no duh" from the reader, sorta like "A Pirate Goomba is a pirate Goomba." If there's nothing worthwile to say about the picture, then there's no harm in a bit of wit; as long as its done in moderation. - {{User|Walkazo}}


What Walkazo said. {{User|Pokemon DP}}
====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. [[User:Salmancer|Salmancer]] ([[User talk:Salmancer|talk]]) 18:17, March 17, 2025 (EDT)


I see no problem with it, it adds to our reputation as carefree, not too strict on the rules like Wikipedia. {{User|Wayoshi}} 22:03, 29 May 2008 (EDT)
Question; would this merge [[Fireball Punch]], and would this failing result in re-instating [[Talk:Dangan Mario|Dangan Mario]]? These manga "forms" are kind of an edge case. {{User:Camwoodstock/sig}} 18:23, March 17, 2025 (EDT)
:I think Wayoshi is right, I mean, we're just a wiki about Mario, we don't always have to be super-serious. But is this just for allowing witty captions and leaving them alone, or would we try to hav mostly funny captions? The first would be okay, but the second would be overkill. Which one is it? {{User|CrystalYoshi}} 16:19, 30 May 2008 (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. [[User:Salmancer|Salmancer]] ([[User talk:Salmancer|talk]]) 18:56, March 17, 2025 (EDT)
::I'm pretty sure it means that if there's a good, reasonable caption, we don't change it to a witty one. If there's a bad caption, like "A Goomba," we shall add a more witty one.


::Also, (no to offense Blitz) the Tranformers wiki's captions ''are'' overkill. They, like Time Q said, are a bit ''too'' funny. We sholdn't go ''that'' far with them. Well, that's my opinion, at least. {{user|InfectedShroom}}
{{@|Doc von Schmeltwick}} for your own sake, you should know "once and only once" as a strict policy has been [https://www.mariowiki.com/index.php?title=MarioWiki:Once_and_only_once&diff=4723954&oldid=4372233 retired]. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 19:18, March 17, 2025 (EDT)
:::Well, I agree that the Transformers Wiki is maybe a bit too lax concerning images caption. I just brought it up because I think their policies influenced this proposal (I think). {{User|Blitzwing}}
:Thanks, wish I'd known that before. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 19:30, March 17, 2025 (EDT)
::Well okay, but would we start racking are brains for something clever just for image captions? That doesn't seem necessary. I mean, they're fine, and they should be allowed if someone thinks of one. But trying to think of one for every single image caption that doesn't really present information... I see a lot of bad jokes ahead. {{User|CrystalYoshi}}


...We don't need witty captions on ALL the images. Hell, we don't need a caption on all of them, full stop. This is kind of an optional thing; If the current image caption is pathetic (like the "A Goomba" example) or if there is no image caption, then feel free to add something clever and witty. It's not a neccessity. {{User|Pokemon DP}}
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..
<blockquote>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. </blockquote> - [[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". [[User:Salmancer|Salmancer]] ([[User talk:Salmancer|talk]]) 19:35, March 17, 2025 (EDT)


Yes, we can do without the really lame ones. (One example is, "Waluigi, in his normal attire, wearing a purple shirt, black overalls, and orange elf-like shoes." from the Waluigi page. Anyone with eyes enough to read can see that he's wearing that){{User|Mumbles}}
"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"? [[User:Salmancer|Salmancer]] ([[User talk:Salmancer|talk]]) 19:47, March 17, 2025 (EDT)


Well, that's okay. I'm not actually going to vote, but it's a landslide already. {{User|CrystalYoshi}}
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''? [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk: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. <blockquote>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. </blockquote> - [[Tanooki Mario]], ''Super Mario Bros. 3'' section.
:<blockquote>However, the form's mechanics are different from ''Super Mario Bros. 3'', as while Mario can still tail whip (by pressing {{button|3ds|X}} or {{button|3ds|Y}}) and glide (now done by holding {{button|3ds|A}} or {{button|3ds|B}}, as with [[Cape Mario|Caped Mario]], rather than tapping the buttons), he cannot fly during gameplay. </blockquote> - [[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. [[User:Salmancer|Salmancer]] ([[User talk: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? [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk: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. [[User:Salmancer|Salmancer]] ([[User talk: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. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk: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 <nowiki>{{main}}</nowiki> 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.[[User:Salmancer|Salmancer]] ([[User talk: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. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 22:02, March 17, 2025 (EDT)


==Miscellaneous==
==Miscellaneous==
''None at the moment.''
''None at the moment.''

Latest revision as of 12:17, March 18, 2025

Image used as a banner for the Proposals page
Current time:
Tuesday, March 18th, 17:00 GMT
Proposals can be new features, the removal of previously-added features that have tired out, or new policies that must be approved via consensus before any action is taken.
  • Voting periods last for two weeks, but can close early or be extended (see below).
  • Any autoconfirmed user can support or oppose, but must have a strong reason for doing so.
  • All proposals must be approved by a majority of voters, including proposals with more than two options.
  • For past proposals, see the proposal archive and the talk page proposal archive.

If you would like to get feedback on an idea before formally proposing it here, you may do so on the proposals talk. For talk page proposals, you can discuss the changes on the talk page itself before creating the TPP there.

How to

If someone has an idea about improving the wiki or managing its community, but feel that they need community approval before acting upon that idea, they may make a proposal about it. They must have a strong argument supporting their idea and be willing to discuss it in detail with other users, who will then vote on whether or not they think the idea should be implemented. Proposals should include links to all relevant pages and writing guidelines. Proposals must include a link to the draft page. Any pages that would be largely affected by the proposal should be marked with {{proposal notice}}.

Rules

  1. Only autoconfirmed users may create or vote on proposals. Proposals can be created by one user or co-authored by two users.
  2. Anyone is free to comment on proposals (provided that the page's protection level allows them to edit).
  3. Proposals conclude at the end of the day (23:59) two weeks after voting starts (all times GMT).
    • For example, if a proposal is added at any time on Monday, August 1, 2011, the voting starts immediately and the deadline is two weeks later on Monday, August 15, at 23:59 GMT.
  4. Users may vote for more than one option, but they may not vote for every option available.
  5. Every vote should have a strong, sensible reason accompanying it. Agreeing with a previously mentioned reason given by another user is acceptable (including "per" votes), but tangential comments, heavy sarcasm, and other misleading or irrelevant quips are just as invalid as providing no reason at all.
  6. Users who feel that certain votes were cast in bad faith or which truly have no merit can address the votes in the comments section. Users can ask a voter to clarify their position, point out mistakes or flaws in their arguments, or call for the outright removal of the vote if it lacks sufficient reasoning. Users may not remove or alter the content of anyone else's votes. Voters can remove or rewrite their own vote(s) at any time, but the final decision to remove another user's vote lies solely with the wiki staff.
    • Users can also use the comments section to bring up any concerns or mistakes in regards to the proposal itself. In such cases, it's important the proposer addresses any concerns raised as soon as possible. Even if the supporting side might be winning by a wide margin, that should be no reason for such questions to be left unanswered. They may point out any missing details that might have been overlooked by the proposer, so it's a good idea as the proposer to check them frequently to achieve the most accurate outcome possible.
  7. If a user makes a vote and is subsequently blocked for any amount of time, their vote is removed. However, if the block ends before the proposal ends, then the user in question holds the right to re-cast their vote. If a proposer is blocked, their vote is removed and "(blocked)" is added next to their name in the "Proposer:" line of the proposal, which runs until its deadline as normal. If the proposal passes, it falls to the supporters of the idea to enact any changes in a timely manner.
  8. Proposals cannot contradict an already ongoing proposal or overturn the decision of a previous proposal that concluded less than four weeks (28 days) ago.
  9. If one week before a proposal's initial deadline, the first place option is ahead of the second place option by eight or more votes and the first place option has at least 80% approval, then the proposal concludes early. Wiki staff may tag a proposal with "Do not close early" at any time to prevent an early close, if needed.
    • Tag the proposal with {{early notice}} if it is on track for an early close. Use {{proposal check|early=yes}} to perform the check.
  10. Any proposal where none of the options have at least four votes will be extended for another week. If after three extensions, no options have at least four votes, the proposal will be listed as "NO QUORUM." The original proposer then has the option to relist said proposal to generate more discussion.
  11. If a proposal reaches its deadline and there is a tie for first place, then the proposal is extended for another week.
  12. If a proposal reaches its deadline and the first place option is ahead of the second place option by three or more votes, then the first place option must have over 50% approval to win. If the margin is only one or two votes, then the first place option must have at least 60% approval to win. If the required approval threshold is not met, then the proposal is extended for another week.
    • Use {{proposal check}} to automate this calculation; see the template page for usage instructions and examples.
  13. Proposals can be extended a maximum of three times. If a consensus has not been reached by the fourth deadline, then the proposal fails and cannot be re-proposed until at least four weeks after the last deadline.
  14. All proposals are archived. The original proposer must take action accordingly if the outcome of the proposal dictates it. If it requires the help of an administrator, the proposer can ask for that help.
  15. After a proposal passes, it is added to the appropriate list of "unimplemented proposals" below and is removed once it has been sufficiently implemented.
  16. If the wiki staff deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to cancel it at any time.
  17. Proposals can only be rewritten or canceled by their proposer within the first four days of their creation. However, proposers can request that their proposal be canceled by a staff member at any time, provided they have a valid reason for it. Please note that canceled proposals must also be archived.
  18. Unless there is major disagreement about whether certain content should be included, there should not be proposals about creating, expanding, rewriting, or otherwise fixing up pages. To organize efforts about improving articles on neglected or completely missing subjects, try setting up a collaboration thread on the forums.
  19. Proposals cannot be made about promotions and demotions. Staff changes are discussed internally and handled by the bureaucrats.
  20. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
  21. Proposals must have a status quo option (e.g. Oppose, Do nothing) unless the status quo itself violates policy.

Basic proposal formatting

Copy and paste the formatting below to get started; your username and the proposal deadline will automatically be substituted when you save the page. Update the bracketed variables with actual information, and be sure to replace the whole variable including the square brackets, so "[insert info here]" becomes "This is the inserted information" and not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but the objective(s) of each voting option must be clearly defined. Such options should also be kept to a minimum, and if something comes up in the comments, the proposal can be amended as necessary. 

===[insert a title for your proposal here]===
[describe what issue this proposal is about and what changes you think should be made to improve how the wiki handles that issue]

'''Proposer''': {{User|{{subst:REVISIONUSER}}}}<br>
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT

====[option title (e.g. Support, Option 1)]: [brief summary of option]====
#{{User|{{subst:REVISIONUSER}}}} Per proposal.

====[option title (e.g. Oppose, Option 2)]: [brief summary of option]====

====Comments ([brief proposal title])====

Autoconfirmed users will now be able to vote on your proposal. Remember that you can vote on your own proposal just like the others.

To vote for an option, just insert #{{User|[your username here]}} at the bottom of the section of your choice. Just don't forget to add a valid reason for your vote behind that tag if you are voting on another user's proposal. If you are voting on your own proposal, you can simply say "Per proposal."

Poll proposal formatting

As an alternative to the basic proposal format, users may choose to create a poll proposal when one larger issue can be broken down into multiple sub-issues that can be resolved independently of each other. In a poll proposal, each option is essentially its own mini-proposal with a deadline and Support/Oppose subheadings. The rules above apply to each option as if it were a its a two-option proposal: users may vote Support or Oppose on any number of options they wish, and individual options may close early or be extended separately from the rest. If an option fails to achieve quorum or reach a consensus after three extensions, then the status quo wins for that option by default. A poll proposal closes after all of its options have been settled, and no action is taken until then. If all options fail, then nothing will be done.

To create a poll proposal, copy and paste the formatting below to get started; your username and the option deadlines will automatically be substituted when you save the page. Update the bracketed variables with actual information, and be sure to replace the whole variable including the square brackets, so "[insert info here]" becomes "This is the inserted information" and not "[This is the inserted information]". 

===[insert a title for your proposal here]===
[describe what issue this proposal is about and what changes you think should be made to improve how the wiki handles that issue]

'''Proposer''': {{User|{{subst:REVISIONUSER}}}}

====[option title (e.g. Option 1)]: [brief summary of option]====
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT

;Support
#{{User|{{subst:REVISIONUSER}}}} Per proposal.

;Oppose

====[option title (e.g. Option 2)]: [brief summary of option]====
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT

;Support
#{{User|{{subst:REVISIONUSER}}}} Per proposal.

;Oppose

====[option title (e.g. Option 3)]: [brief summary of option]====
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT

;Support
#{{User|{{subst:REVISIONUSER}}}} Per proposal.

;Oppose

====Comments ([brief proposal title])====

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

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)

Writing guidelines

None at the moment.

New features

Establish a format for poll proposals on the archive lists

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

I have several pitches for you.

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

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

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

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

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

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

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

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

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

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

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

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

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

Option Zero

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

Option One

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

Option Two

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

Option Three

  1. Camwoodstock (talk) We would like to pitch a more sophisticated variant of this; 3 new colors. One for a poll that has concluded, one for one that's partially ongoing, and one for a poll that has been partially overturned by a future proposal. Maybe dark green, dark gray/maybe a de-saturated dark green a-la the Shroom Spotlight template, and a dark yellow? The darker colors, of course, to contrast with the non-poll proposals. (On dark mode, we'd probably make these lighter, rather than darker, provided we actually even add dark mode compatibility to the proposal archive colors.)
  2. Rykitu (talk) Per all.
  3. Ahemtoday (talk) I definitely see the appeal in having poll proposals under a singular listing, but I think they'd be better served by having one or multiple new colors rather than using the standard red and green.

#Jdtendo (talk) Listing every single poll would probably take a lot of space whereas the whole purpose of a poll proposal is bringing together many similar polls that would be too cumbersome to handle separately. I would prefer having a single proposal listed as "Determine what memes should be on the Internet references page" that users can click on to check the detailed results rather than cluttering the list with a dozen links.

Option Four

Comments

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

I don't quite understand option one and two, as the above rules for poll proposals state "A poll proposal closes after all of its options have been settled, and no action is taken until then. If all options fail, then nothing will be done." --PopitTart (talk) 07:09, March 4, 2025 (EST)

Could you explain the contradiction in greater detail? I don't see what you mean. Ahemtoday (talk) 12:01, March 4, 2025 (EST)
The options say "The page would only contain #83A and #83B if the proposal passed right now, with #83C being added later" and "...how it handles open issues on partially closed poll proposals" there shouldn't be any instances of archiving partially closed poll proposals, they only close all at once when every entry has been resolved.--PopitTart (talk) 20:07, March 4, 2025 (EST)
So is your position that we should use the lettering scheme from Options One and Two, but only add poll proposals to the archive page when all of their issues are closed? I don't think I agree, but I can add that as Option Five if that's what you want to vote for. Ahemtoday (talk) 22:48, March 4, 2025 (EST)

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

Removals

None at the moment.

Changes

Give Taiko no Tatsujin an article

Taiko no Tatsujin has had numerous crossovers with the Mario franchise throughout its history. This extends to not only the songs being playable, but actual Mario characters showing up and being animated in the accompanying videos in the earlier games.

  • The DS version has "Super Mario Bros." as a track, using imagery from the games.
  • The Wii version includes "New Super Mario Bros. Wii Medley." and "Super Mario Bros." Notably, the videos include actual characters and imagery from the game showing up. The former has nearly every enemy from the original Super Mario Bros.
  • Taiko no Tatsujin Wii U Version! has "Fever" from Dr. Mario. There are also Mario and Luigi costumes for Don-chan and Katsu-chan.
  • Nintendo Switch Version! has "Jump Up, Super Star!" from Super Mario Odyssey.
  • The 2020 version brings back "Super Mario Bros." and "Jump Up, Super Star!", also including a "Famicom Medley" track using "Fever" from Dr. Mario. These tracks are present in many of the arcade versions. Playing "Super Mario Bros." will have mushrooms and Super Stars appear when notes are hit.
  • Blue Version has Cappy has an equippable hat.
  • Rhythm Festival has a medley of music from Super Mario Bros., re-used from earlier games.

Mario has paid it back with the serial-numbers-filed-off Donkey Konga and Don-chan being a playable character in Mario Kart Arcade GP DX. Since there's overlap between the franchises, and they've had a decent history together, I think Taiko is deserving of its own article to cover all this in one place.

Proposer: Scrooge200 (talk)
Deadline: March 30, 2025, 23:59 GMT

Support (Bring Us One Degree of Separation Closer to Jimmy Neutron)

  1. Scrooge200 (talk) Per proposal.
  2. Camwoodstock (talk) Makes sense to us; with how many cross references there are both ways, it seems only fair.
  3. Hewer (talk) This should probably be cancelled given the crossover article proposal but I'll support just in case. I previously wasn't sure whether it would get a page under that proposal because the only crossover I knew about was Don-chan being in Mario Kart (and his tiny Smash representation in one of Pac-Man's taunts), but all of this other stuff seems very comparable to what got Just Dance (series) a page. Now we just need to figure out whether Tamagotchi gets one...
  4. Killer Moth (talk) Per proposal.

Oppose (No More Megalovania, Please)

Comments' Perfect Math Class

@Scrooge200, have you considered waiting until the proposal immediately above is finished? You would not need to raise proposal for Taiko no Tatsujin at all if it were to be pass. - Nintendo101 (talk) 15:23, March 16, 2025 (EDT)

Oh, I noticed that, but figured it was more for just Zelda. I'm glad to see we're finally making it out of the Stone Age with our crossover coverage, though. Scrooge200 (talk) PMCS Mustard Cafe Sign.png 15:27, March 16, 2025 (EDT)
Zelda is just the example I worked with. The proposal itself applies to all manner of crossover. - Nintendo101 (talk) 15:30, March 16, 2025 (EDT)
@Scrooge200 By "stone age" I assume you mean it's one of the last steps to becoming a wiki centered completely on Super Mario. Super Mario RPG (talk) 15:38, March 16, 2025 (EDT)

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:

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 two 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? Would Penguin Mario be a stronger article if there was a second article dedicated to Belly Slide? 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?

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.

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 Cape Mario and Superstar Mario into a listicle before this proposal reduced it to 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

  1. Salmancer (talk) Per proposal.

Merge moves, Fly is free: Merge moves to forms, but keep Fly as is

Clip Fly's wings: Do not merge moves to forms, change Fly from an article to a list

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-sigicon.png~Camwoodstock (talk) 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 X Button or Y Button) and glide (now done by holding A Button or B Button, 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)

Miscellaneous

None at the moment.

Retrieved from "https://www.mariowiki.com/index.php?title=MarioWiki:Proposals&oldid=4788638"