MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
 
Line 1: Line 1:
{{/Header}}
{{/Header}}
==Writing guidelines==
==Writing guidelines==
===Revise how long proposals take: "IT'S ABOUT (how much) TIME (they take)"===
''None at the moment.''
Currently, the way our proposals are set up, there are two deadlines. On the main proposals page, they last for 1 week. On talk pages, or for writing guidelines proposals, 2 weeks. Now, this is ''fine.'' We're not going to claim this is like, some total deal-breaker or nothing. However, lately, [[MarioWiki talk:Proposals#Why the inconsistency?|there have been a few concerns raised about this inconsistency]], and we figured, what the hey, why not put it up to vote?
 
A few concerns we've seen, both from others and from us, in no particular order;
* The largest one to us is just that, unless a proposal is really specific, it's just not worth it to make a talk page proposal over a main page proposal, since it'll end faster. The only thing immune to this are writing guidelines proposals.
* While the proposals themselves are different lengths, the duration before you can make a second proposal on them remains the same.  Thusly, if you want to set a policy in stone, you would actually want to make it a writing guidelines/talk page proposal over an ordinary one, as that means it will last for, at least, 6 weeks (4 weeks for the cooldown, and 2 weeks to put it to proposal again.)
* Lastly, talk page proposals just inherently take longer to happen. This can be an issue if their changes are, overall, quite small (like a simple merge/split or rename), or the consensus is reached very quickly; this stings when an ordinary proposal would happen twice as fast with the exact same amount of votes!
 
Now, there's a few ways you can go about this, but there's one in particular we've taken a liking to: uh, just make all proposals take '''2''' weeks, lmao.
 
"BUT CAM & TORI!", we hear you shout, "BUT YOU SAID 2 WEEKS PROPOSALS TAKE TOO LONG??? WHY WOULD YOU CHANGE THEM TO SOMETHING YOU HATE???", and to that we say... No! We actually like the 2 weeks proposals! They have a distinct benefit to them! The problem is that they're juxtaposed with the 1 week proposals. Let's run through those same bullet points.
* If all proposals were 2 weeks, well, there's no real loss to making a talk page proposal over a main proposal page proposal, as they'll all last 2 weeks anyways. (Sure, a proposal can take longer if there's a tie, but that just happens for all proposals anyways.)
* There's also no incentive to make a talk page proposal/writing guideline proposal if you particularly want your porposal to stick around, as again, now ''every'' proposal is guaranteed to last for, at the very least, 6 weeks.
* Now. While it's annoying that all proposals will take 2 weeks, despite the inherent risk of some coming to their consensuses much faster than the deadlines, for one, [[Talk:Alien (Club Nintendo)#ANTI-ALIEN ALARM!!! (Delete this article)|this is also an issue with talk page proposals as-is]]. For two, the extra time can offer extra time for new information to come to light or for particularly close votes to make their cases and form a proper consensus, without needing a tiebreaker. Lastly, if it's really ''that'' big of an issue, we could perhaps create a rule that if a proposal comes to a particularly large consensus a week in, it'll pass early (the finer details would be created as necessary).
 
There is, of course, the alternative of making all proposals '''1''' week. While we realize this does also resolve a lot of things, it does also necessarily mean that some proposals that would want to happen slower, now don't have that time, and are rushed. Even making only talk page proposals take only 1 week means that Writing Guideline proposals will be at a unique disadvantage for how long they take/an advantage for how long they last if they pass. (And of course, we could just leave everything as they are, but that goes without saying.) That being said, we ''have'' provided options for these, and you're free to make your case for these.
 
'''Proposer''': {{User|Camwoodstock}}<br>
'''Deadline''': October 16, 2024, 23:59 GMT
 
====Make all proposals last for 2 weeks====
#{{User|Camwoodstock}} If it's not obvious, this is our primary option; we're a big fan of the idea of global 2 week proposals!. Even with their caveats, in the worst-case scenario, we could make a clause to prevent proposals for lasting too long if they reach their consensus early, or we could simply revert back to the current system. We think the added consistency and preventing of shenanigans is very potent, and it also means that you have to put a bit more thought into your proposal as you make it. Patience fans will be eating ''good'' if this passes.
#{{User|Hewer}} Per proposal and what was said [[MarioWiki talk:Proposals#Why the inconsistency?|here]]. However, I'd also be fine with an option to just shorten writing guidelines proposals to be one week. I don't really understand the third option here, writing guidelines proposals being two weeks felt to me like the worst inconsistency of the bunch. I still don't see what about "writing guidelines" specifically means they inherently need more time than the other categories on this page.
#{{User|OmegaRuby}} Regular proposals and TPPs are just as visible as one another and should be treated equally, ''especially'' when regular page proposals can be the home of very important decisions (such as this one!) and are just given 1 week. Per all.
#{{User|Waluigi Time}} 1 week proposals have always felt a little short to me. I'd rather err on the side of some proposals running a little longer than needed than not having enough discussion time (I don't like banking on a controversial proposal tying). Having to wait an extra week to implement a proposal isn't the end of the world anyway - proposals are rarely, if ever, urgent enough that an extra week with no change would be detrimental to the wiki (and if that were the case, the change should probably come immediately from wiki staff).
#{{User|Killer Moth}} Per all. Giving an extra week to discuss and vote on proposals is a good thing.
#{{User|Drago}} Per Waluigi Time.
#{{User|Doc von Schmeltwick}} - Per, I never got why sitewide ones always got ''less'' time to discuss.
 
====Make all proposals last for 1 week====
 
====Make all proposals except for writing guidelines proposals last for 1 week====
#{{User|Camwoodstock}} Secondary option. While we like this much less, we do see the merit of making Talk Page Proposals 1 week, and it's not exactly the end-all-be-all. However, we would ''vastly'' prefer 2-week proposals, and keeping Writing Guidelines proposals 2-week is kind of a necessary evil to prevent them from being too rushed for their own good. However, compared to truly ''all'' 1-week proposals, this is better... though, not as good as all 2-week proposals.
#{{user|7feetunder}} For me, it's either this or bust. [[Talk:Ankoopa#What_to_do_with_this_article|New information coming to light can still invalidate a proposal's entire premise too late and require a counterproposal even with a 2 week deadline]], so extending the deadline of main page props to 2 weeks won't stop that from happening from time to time. Most proposals that don't reach a consensus in a week will probably require extensions anyway. TPPs being less "visible" than main page proposals was more of an issue back when no quorums were immediate, [[MarioWiki:Proposals/Archive/58#Overhaul_the_no_quorum_proposal_rule_.28.238.29|but that's no longer the case]].
#{{User|Axii}} Voting for this just so the first option doesn't win.
 
====Do nothing====
#{{User|7feetunder}} If making TPPs last 1 week isn't desirable, I say just keep the status quo. While the current system ''does'' encourage making main page proposals over TPPs when possible if one wants their prop to pass faster, I'm fine with that. A controversial prop is not going to end in a week, and a prop with unanimous or near-unanimous support probably doesn't need that extra time in the oven. I'd be more open to global 2 weekers if a "early consensus = early pass" sub-rule was already in effect, but it isn't, and there's no guarantee that such a rule would be accepted by the community.
#{{User|Axii}} The solution isn't solving anything. There was never a problem with inconsistency. Talk page proposals last for two weeks because they're far less visible to people. Mainspace proposals page is frequently visited by many, having proposals last for 2 weeks instead of one doesn't change anything. It doesn't help the community settle on anything, one week is more than enough. Proposals that are tied already get extended automatically, if anything, I would argue writing guidelines proposals should last a week instead. I proposed a different solution on the talk page as well. If a user making a proposal (or an admin) feel like one week wouldn't be enough, they should be able to extend it to two. (I specifically added "or an admin", because most users don't want a proposal to last for two weeks.) Either way, the fact that users often choose mainspace proposals over talk page is perfectly fine as well. It's not about the time in the oven but the visibility of the proposal to the wiki community. Writing guidelines (if they remain at two weeks) could instead be clarified. Right now it is unclear what writing guidelines proposals even are, I think this is the main problem that should be looked at.
#{{User|Waluigi Time}} Secondary choice. The inconsistency isn't that bad and I prefer that to all proposals being shortened.
#{{User|Killer Moth}} Second choice.
#{{User|Nintendo101}} I think it is worth scrutinizing our policy proposals and the issues people brought up are valid, but I do not think setting the same time for everything is necessarily the best solution. I will elaborate on my thoughts below.
 
====Comments====
Something that occurred to me: The time allowed to edit TPPs was originally 3 like main page proposals, but [[MarioWiki:Proposals/Archive/48#Double_the_amount_of_time_a_proposer_can_edit_their_talk_page_proposals|eventually doubled to 6 to go with their extended duration]]. If TPPs are shortened to 1 week, would the time allotted to edit them be reverted? {{User:7feetunder/sig}} 19:30, October 2, 2024 (EDT)
:That seems only fair to put them back to 3 days if that option passes--after all, it would be a glaring oversight to retain that and effectively allow for proposals that were en route to pass suddenly being hijacked on the last day, and pivoting from the original purpose, while ''still retaining the vote''. The plan here is to de-jank the proposal time-lengths and make them more consistent--not to introduce ''even more shenanigans''! {{User:Camwoodstock/sig}} 20:18, October 2, 2024 (EDT)
 
@7feetunder: Of course there's still a chance for new information to come too late with any proposal length, but longer proposals mean the chance is lower. {{User:Hewer/sig}} 02:44, October 3, 2024 (EDT)
@7feetunder: On your reasoning under ''Do nothing'', the idea of an early-consensus-early-conclusion rule for proposals is intriguing... I feel as if we have 2-week proposals that can end early if everyone has a near unanimous consensus on what to do with the proposal, we'd have an ideal middle ground. --[[User:OmegaRuby|OmegaRuby]] ([[User talk:OmegaRuby|talk]]) 08:55, October 3, 2024 (EDT)
 
 
===Clarify coverage of the ''Super Smash Bros.'' series===
I've pitched this before, and it got a lot of approval (particularly in favor of one-at-a-time small proposals), so I'm making it a full proposal:<br>
I have thought long and hard about the "proper" way for us to cover ''Super Smash Bros.'' in a way that both respects the desire to focus primarily on ''Super Mario'' elements while also respecting the desire to not leave anything uncovered. As such, the main way to do this is to '''give pages only to ''Super Mario'' elements, whilst covering everything else on the pages for the individual ''Super Smash Bros.'' games; unless otherwise stated, they will instead link to other wikis, be if the base series' wiki or SmashWiki'''. For instance, Link will remain an internal link (no pun intended) because he's crossed over otherwise, Ganondorf will link to Zeldawiki because he hasn't. Link's moves (originating from the ''Legend of Zelda'' series) will link to Zeldawiki, while Ganondorf's moves (original moves due to being based on Captain Falcon's moves) will link to Smashwiki.<br>
Other specific aspects of this, which for the most part make the game pages' internal coverage be more consistent with how we handle other games':
#Change the "List of items in Smash" to how {{user|Super Mario RPG}} had it in [https://www.mariowiki.com/index.php?title=List_of_Super_Smash_Bros._series_items&oldid=4364118 this] edit, albeit with the remaining broken formatting fixed. That page always bothered me, and that version is a definite improvement.
#Merge the "enemies" pages to their respective game - they're already structured like any other game's enemy tables anyway. These pages ''also'' always bothered me.
#Merge the "Subspace Army" and "Subspace Stages" lists to each other to recreate a watered-down version of the Subspace Emissary page (to split from the Brawl page due to length and being exclusive to that campaign); it would also include a table for characters describing their role in said campaign, as well as objects/items found exclusively in it (Trophy Stands, the funny boxes, the metallic barrel cannons, etc... a lot of things from the deleted "List of Super Smash Bros. series objects" page, actually) - once again, all except ''Mario''-derived things will link elsewhere (mostly to Smashwiki in this case).
#Section each game akin to how I had the SSB64 page as of [https://www.mariowiki.com/index.php?title=Super_Smash_Bros.&oldid=4340069 this] edit, ''including'' sections for Pokemon, Assist Trophies, Bosses, etc., and links to other wikis for subjects that we don't need pages on. Other sections can be added as needed, and table structure is not specifically set, so further info can be added.
#Leave the lists for fighters, stages, and (series-wide) bosses alone (for now at least), as they make sense to have a series-wide representation on here in some capacity. Also, you never know when one of them is going to cross over otherwise, like Villager, Isabelle, and Inkling suddenly joining ''Mario Kart'', so it's good to keep that around in case a split is deemed necessary from something like that happening down the line.
#Have image galleries cover ''everything'' that can reasonably be included in an image gallery for the game, regardless of origin. This includes artwork, sprites, models, screenshots, etc, for any subject - yes, including Pokemon, so that will undo [[MarioWiki:Proposals/Archive/68#Remove lists of Poké Ball and stage-exclusive Pokémon on ''Smash Bros.'' game pages and allow each Poké Ball Pokémon only one representative artwork/screenshot|that one proposal from a month ago]]. Just like on the game pages, the labels will link to other sites as needed.
#Leave Stickers and Spirits alone, their pages are too large to merge and are fine as they are for the reasons that opposition to deleting them historically has brought up.
#Include the "minigame" stages (Break the Targets, Board the Platforms, Race to the Finish, Snag Trophies, Home Run Contest, Trophy Tussle, the Melee Adventure Mode stages) in the "list of stages debuting in [game]" articles. For ones like Targets, it would just explain how it worked and then have a gallery for the different layouts rather than describing each in detail (and if we later want to split the ''Mario''-based ones into their own articles, I guess we can at some point). Said minigame pages should be merged to a section in the SSB series article covering the series' minigames. The Subspace Emissary stages will get a section with a {{tem|main}} to the stage section of the Subspace Emissary article (detailed in an above point).
#Keep trophy, assist trophy, challenge, and soundtrack pages covering only ''Mario'' things, leave the remainder of the images in the game gallery (fun fact: Smashwiki does not have game galleries, nor does their community want them; we can base what we ''could'' do on if other wikis do something, but not base what we ''cannot'' do from those - nothing forbids coverage just because of that).
 
People may wonder, "What about Nintendo Land and Saturday Supercade? Why don't they get this level of coverage?" It's simple, really: In ''Smash'', you can have Mario throw a Deku Nut at Ridley in Lumiose City and nobody bats an eye at how absurd that situation is. In those other games, the different representations are very much split apart; all ''Mario''-related stuff is within a few minigames that do not overlap whatsoever with any of the other ones. In ''Nintendo Land'', you cannot have Mario fighting Ridley in the Lost Woods, despite (representations of) all of those things appearing in the game. In ''Smash'', anyone can interact with anything, regardless of origin, so ''Mario'' characters can interact with anything, and anyone can interact with ''Mario'' things. That's why ''Smash'', the melting pot it is, gets more focus than ''Nintendo Land'', where everything's more of a side dish.
 
'''Proposer''': {{User|Doc von Schmeltwick}}<br>
'''Deadline''': October 17, 2024, 23:59 GMT
 
====Support - clarify it like this====
#{{User|Doc von Schmeltwick}} - Per
#{{User|Axii}} Even though I disagree with points 6, 7, and especially 8 (''Mario''-themed minigames should be covered separately), I feel like this is the solution most would agree to compromise on.
#{{User|Camwoodstock}} While we would like to do some stuff of our own (cough cough, maybe a proper solution to Smash redirects clogging categories), this is a good start, we feel. If push comes to shove, we could always revert some of these changes in another proposal.
 
====Oppose - don't clarify it like this====
 
====Comments - clarify the clarification?====
<small>(I was gonna name the options "Smash" and "Pass," but I thought that might be too dirty)</small> - [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 15:38, October 3, 2024 (EDT)
 
{{@|Axii}} - I wouldn't say any of the minigames are really innately ''Mario''-themed, though. If any were, I'd have them stay separate. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 16:02, October 3, 2024 (EDT)


==New features==
==New features==
''None at the moment.''
===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 [[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?


==Removals==
I have several pitches for you.
''None at the moment.''


==Changes==
<big>'''''OPTION ZERO'''''</big><br>
=== Split articles for certain official single-game enemy behavior splits ===
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>
In the early days, before Nintendo was really sure how they wanted to classify enemies, there were some splits that didn't stick - namely, behaviors that were initially unique to a specific subtype, and then became normal alternatives to the base enemies. I'm specifically talking about:
*'''Sky Blooper''' - [[Blooper]] variant from ''Super Mario Bros.: The Lost Levels''
*'''Upside-down Buzzy Beetle''' - [[Buzzy Beetle]] variant from ''Super Mario Bros. 3''
*'''Upside-down Spiny''' - [[Spiny]] variant from ''Super Mario Bros. 3''
*'''Scattering Blooper''' - [[Blooper Nanny]] variant from ''Super Mario Bros. 3''
*'''Upside-down Piranha''' - [[Piranha Plant]] variant from ''Super Mario Land''


I make this mainly because [https://www.nintendo.co.jp/character/mario/archives/smb2/?lang=en the] [https://www.nintendo.co.jp/character/mario/archives/smb3/?lang=en Mario] [https://www.nintendo.co.jp/character/mario/archives/land/?lang=en Portal] splits each of these for these games specifically, across language borders, despite being a newer source (which is notably a lot more than Boss Bass/Big Bertha gets, so that merge remains correct), along with Upside-down Piranha making the ''Smash Bros.'' Piranha Plant list; other instances of similar things occurring that have not (yet) been corroborated by a source like Portal (such as ''[[Cheep Cheep|Tobipuku]]'' from ''New Super Mario Bros.'') will not be counted. Now, I want to clarify something important: '''this split only covers the appearances where the official word treats them as distinct enemies.''' Random upside-down Buzzy Beetles and Piranha Plants in ''New Super Mario Bros. Wii'' are not counted, as they are not distinguished from their base species in any way in that game. I see this as similar to [[Fire Nipper Plant]], another SMB3 enemy whose fire-breathing characteristics were given to normal [[Nipper Plant]]s in a few later games.
''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.''


I have a demo for these pages in the various sections of [[User:Doc von Schmeltwick/Projects/Early merges|this]] page, along with stuff for the below proposal.
<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.)


EDIT 9/28: Adding an option for only splitting the two Bloopers.
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


'''Proposer''': {{User|Doc von Schmeltwick}}<br>
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.
'''Deadline''': October 3, 2024, 23:59 GMT


====Scattering Support====
<big>'''''OPTION TWO'''''</big><br>
#{{User|Doc von Schmeltwick}} - Per
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.
#{{User|FanOfYoshi}} Per proposal.


====Bloopers only, no upside-down!====
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.
#{{User|Nintendo101}} I see no problem with this. Unlike the other proposed splits, normal Bloopers have not inherited the defining airborne traits of Sky Bloopers outside of the ''Super Mario Maker'' games, which breaks a lot of conventions for the sake of fun creative gameplay. I do not think it is the same situation as Upside-down Piranha Plant or Spiny.
#{{User|DryBonesBandit}} Agreed.
#{{User|Hewer}} Blooper proposal
#{{User|ThePowerPlayer}} If [[Super Blooper (boss)|this Blooper]] can be split, then so can the ones listed here. On the other hand, the upside-down variants are splitting hairs. Do we split [https://youtu.be/G-JHFcn3qWs?t=58 the Goombas from anti-gravity sections] just because they're upside down?
#{{User|FanOfYoshi}} Second pick, per all.
#{{User|Jazama}} Per all
#{{User|OmegaRuby}} Per all.


====Upside-down Oppose====
<big>'''''OPTION THREE'''''</big><br>
#{{User|Arend}} ''Maybe'' a case could be made for Scattering Blooper, but Sky Blooper and Upside-down Piranha Plant also behave (nearly) identical to their regular counterparts. Not to mention that nearly all the regular versions of these enemies have retroactively gained attributes of these enemies too (Buzzy Beetles and Spinies can appear commonly walking on ceilings and dropping down in various games, Piranha Plants can pop out upside down from a ceiling pipe in various games, nearly all Bloopers encountered on land float above the ground; none of these are regarded as distinct variants in those later games), so it's a little weird to me if only those specific versions of enemies are regarded as separate entities but regular versions of these enemies adapting these attributes aren't; feels inconsistent and confusing for a reader.
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.
#{{User|Axii}} Per Arend. I feel like it would be an unnecessary split. Nintendo doesn't refer to these enemies separately in any newer games. Sky Blooper may have had a chance, but ''Super Mario Maker'' clearly shows that they are just regular Bloopers. I can see Scattering Blooper being split in the future though.
#{{User|SolemnStormcloud}} Per opposition.
#{{User|Killer Moth}} Per all.
#{{User|EvieMaybe}} i can see the case for scattering blooper and MAYBE sky blooper, but i don't think i agree with the philosophy behind the proposal.
#{{User|DrippingYellow}} The idea of splitting certain minor behavior differences in enemies, but ''only'' in certain games where they are given a specific adjective relating to the thing they do, honestly just sounds ridiculous. If you're going to split some of them, you might as well split all of them, lest you create a glaring inconsistency in the wiki's coverage of these enemy variants.<br>Also keep in mind that these individual acknowledgements of upside-down enemies aren't consistent even between these similar-era games; Piranha Plants can be found upside-down as early as ''[[Super Mario Bros.: The Lost Levels|The Lost Levels]]'' and ''[[Super Mario Bros. 3]]'', yet would be confusingly absent from your proposed "Upside-down Piranha Plant" article due to not being called "Upside-down Piranha Plants" (and also kind of throws a wrench into your theory that these were originally special variants before being merged into the main enemy). These upside-down enemies are only listed on ''Mario Portal'' when the game's respective manual also mentions them (with apparently a single exception in SMB3's Upside-down Spiny), suggesting less of a confirmation as species and more of an attempt to parallel existing material.<br>The only potential exceptions I see here are the Bloopers, particularly the Sky Blooper with its actually distinct appearance. Though, if the red Koopa Troopa, an enemy that has had consistently has a different appearance and behavior from its green counterpart in all mainline games it has appeared in (the black-and-white SML2 with only the ledge-fearing green Koopa doesn't count due to there being no red Koopa to compare with), [[Talk:Koopa_Troopa#Split_Red_Koopa_Troopa_and_Green_Koopa_Troopa|is too minor a difference to get an article]], then how are these any different?
#{{User|Shoey}} Per all.
#{{User|Mario}} Some of these proposed splits are overkill.
#{{User|Sparks}} Per all.
#{{User|SeanWheeler}} Split enemies for one game each? Not unless we split everybody into singular game subpages like [[smashwiki:Mario (SSBB)|Smash Wiki's fighter pages]].
#{{User|LadySophie17}} Per all.
#{{User|Scrooge200}} I don't think there's a benefit to splitting Bloopers because the ''Super Mario Maker'' games treat them the same anyways. Plus, there's games like ''Paper Mario: The Origami King'' where Bloopers come from the water and are fought on land, and there's no specific place to put those.
<s>#{{User|Hewer}} Not opposed to all of these (I'd probably support splitting Sky Blooper), but while I do generally like following official classification of things, having an article for Buzzy Beetles that were upside down in SMB3 specifically and no other game just feels silly and confusing.</s><br>
<s>#{{User|DryBonesBandit}} Per all.</s>


====Sky Comments====
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.
I understand the rationale, but Mario Portal (and most game material) also recognizes things like green-shelled and red-shelled Koopas as distinct from one another and they also have different behaviors from one another. That'd probably be a bigger proposal than you'd be interested in executing, but how would you feel on those types of enemies being split? I at least like the idea of Sky Blooper getting its own article on the face of it. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 22:27, September 25, 2024 (EDT)
:Those shouldn't be by virtue of the functional distinctions being inconsistent, especially when you get into things like Shy Guys. Most of them use (identifiers) too rather than actual naming differences. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 23:09, September 25, 2024 (EDT)
::Fair (especially for Shy Guys), though generally, I'm pretty sure red-shelled Koopas mechanically are always the ones that turn when they reach an edge, whereas green-shelled ones don't.
::What if, for those enemies, there was a similar scenario as with [[Koopa Shell]]s, where there is one main article, but also smaller ones for [[Green Shell]]s and [[Red Shell]]s for scenarios where the shells have mechanical differences? We could have a main [[Koopa Troopa]] article, and then a Koopa Troopa (Green) and Koopa Troopa (Red). - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 23:50, September 25, 2024 (EDT)
:::You're only looking in terms of 2D platformers, there. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 00:02, September 26, 2024 (EDT)
::::(I hope this is isn't too tangential - I appreciate your insight on this) I think the only 3D platformer with both Koopa Troopas is Super Mario Galaxy, and they still have mechanical differences from one another in those games.
::::For platformers and spin-offs where colors are only cosmetic, I think it would be fine for them to share a single Koopa Troopa article (again, similar setup to Koopa Shell). But I understand the resistance to that idea, because it could be messy and difficult to curate. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 00:09, September 26, 2024 (EDT)
:::::And there's the black-and-white ''Super Mario Land 2'', where the art shows green, but the behavior's more like typical red ones. Then we get into Paratroopas, where originally green hopped or moved back-and-forth and red moved up-and-down, then games like ''Super Mario World'' have red ones moving horizontally or green ones moving vertically. And then there's Cheep Cheep - swimming Cheep Cheeps' colors in SMB1 were purely cosmetic, then SMB3 had lots of behavioral variation among red-colored ones and only one behavior for green-colored ones. I think keeping the "color" ones grouped unless a very notable difference is present (like the ''Paper Mario'' and ''Yoshi's Story'' versions of [[Black Shy Guy]]) is the best way to go in that regard. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 00:23, September 26, 2024 (EDT)


@Opposition I see this as a similar case to [[Gloomba]] only covering the blue underground Goombas when they are officially split, or [[Headbonk Goomba]] only covering headbonking Goombas when ''they'' are officially split. Same for the large-sized Chain Chomps and Wigglers sometimes being considered "big" versions and sometimes considered standard. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 22:09, September 26, 2024 (EDT)
''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.''
:I see those as a bit different since they have functional or other differences specific to those games, blue Goombas aren't normally stronger than the standard versions. As far as I can tell, the only way Upside-down Buzzy Beetle is more of a variant in SMB3 than it is any other game is in name. {{User:Hewer/sig}} 02:52, September 27, 2024 (EDT)
::The fact that Portal, which is recent, bothers to split them for those games specifically rather than ignore it in favor of following what later games do makes me think this is still valid. Especially since Upside-Down Piranhas were also differentiated in Viridi's Piranha Plant list in ''Smash Ultimate''. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 13:09, September 27, 2024 (EDT)
:::Technically, do we know whether Viridi was referring to specifically upside-down Piranha Plants from Super Mario Land, rather than just upside-down ones in general? Not sure if it's different in Japanese, but their placement in the list is notably odd especially if it was meant to be referring to just Mario Land, as they are the last variant listed before the three Petey Piranhas, rather than the roughly release date order the list mostly uses. As for Mario Portal, Nintendo101's point about red and green Koopa Troopas compels me to ignore that. {{User:Hewer/sig}} 15:12, September 27, 2024 (EDT)
::::They're the only ones that are named as such, so yes. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 20:36, September 27, 2024 (EDT)
:::::Uhhh, I'd find sources other than Super Mario Land and the Mario Portal before I confidently make claims like that. Personally, I doubt that these games are the only instances in which the Japanese word for "upside-down" immediately precedes the name of an enemy that happens to be upside-down. [[User:DrippingYellow|DrippingYellow]] ([[User talk:DrippingYellow|talk]]) 01:46, September 28, 2024 (EDT)
::::::Treating it as a label, there are none. Prose, perhaps, but not as a deliberate label. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 02:03, September 28, 2024 (EDT)
:::::::Again, sources???? The only evidence I could find vaguely supporting you (for the Piranha Plant in ''Lost Levels'' at least) is in a scan of the Japanese Super Mario All-Stars guide, which is after you claim they dropped the concept. [[User:DrippingYellow|DrippingYellow]] ([[User talk:DrippingYellow|talk]]) 11:47, September 28, 2024 (EDT)
::::::::What Portal is doing is enough, IMO. It shows their "current interpretation" is that they are different enough for a separate listing (without the parentheses, even) specifically in the respective games I listed, but not elsewhere. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 13:42, September 28, 2024 (EDT)


{{@|DrippingYellow}} - Technically, only the Upside-Down Piranha Plants in SML have the point bonus, which is part of how the game defines its enemies. Also, that "paralleling existing material" also doesn't split color, so this doesn't seem inconsistent to me. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 20:36, September 27, 2024 (EDT)
<big>'''''OPTION FOUR'''''</big><br>
:...Are you seriously trying to argue that the ''point value'' of the enemy is the clincher here? As though enemies are supposed to stay exactly the same with no changes between games? Maybe the developers of SML thought you deserved more of a reward for landing a Superball shot on these upside-down enemies, but how does that specifically support them being considered a unique variant of Piranha Plant in only Super Mario Land? And sure, they called the red Koopa Troopas "Koopa Troopa (Red)" or whatever instead of "Red Koopa Troopa", but simply having a unique name is not the end-all be-all of whether something gets an article or not ([[Black Shy Guy (Yoshi's Story)]], the countless articles that we had to give a conjectural name, to name a few).<br>The problem is simply that versions of enemies that are visually idential and behaviorally similar to their normal counterpart usually don't get split, regardless of whether they have a unique name or not. And somehow, what you're proposing is even more bizarre than that; that these specific enemies in these specific games are Upside-down with a capital "U", and should be split, and the others, lowercase "u", with the ''exact same behavior, attributes, and appearance'', should not. [[User:DrippingYellow|DrippingYellow]] ([[User talk:DrippingYellow|talk]]) 01:46, September 28, 2024 (EDT)
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.
::I see this as equivalent to [[Fire Nipper Plant]], which only appeared once in SMB3, and later RPGs gave normal Nipper Plants identical fire breath abilities. And the point value is a notable difference in function. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 02:03, September 28, 2024 (EDT)
:::Even if these truly are separate listed enemies in only these specific games, this is more like the Grinder/Ukiki situation if anything; two completely different enemies from different series that were eventually merged, and we treat them as the same thing. No "Grinder" article that only covers the monkeys in the ''Yoshi's Island'' games and not ''Wooly World''. This situation is even simpler than that debacle if you ask me, as we know exactly what to look for in terms of defining traits (that is, they are upside-down). See also: the [[Helper Monkey]] article, with all of the uniquely-named-in-Japan variants merged together for the sake of simplicity. [[User:DrippingYellow|DrippingYellow]] ([[User talk:DrippingYellow|talk]]) 11:47, September 28, 2024 (EDT)
::::The monkeys are mainly a snarl because YNI used both (O-saru-san in-game for a level name, Ucky in the guidebook), but in that case the "two separate enemies" weren't in a single game alongside each-other separately, so that situation is still different. There's also a reverse situation related to that, where Big Cheep Cheep lost its funny big mouth and its original design was eventually given to its derivative Cheep Chomp (in the same game that gave Grinder's design to Ukiki). Now, I do ''get'' where you're coming from, but I find this situation clean enough to enact this. Meanwhile, on the [https://triforcewiki.com/ Triforce Wiki], I list both of the "Zora" designs together, while Nintendo back-and-forths on whether they're different, the same, or different-looking clans of the same species (which as of ''Echoes of Wisdom'', is their current depiction) - I find that to be too much confusing mingling to bother attempting to split it. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 13:45, September 28, 2024 (EDT)
::I will say, Nintendo is inconsistent with whether they list colored variants as separate subjects or lumped together, but in the modern era (the mid-2010s onward), they generally do if there are mechanical differences between them. For example, the ''[[Super Mario Bros. Encyclopedia]]'' and Mario Portal list red and green Koopa Troopas separately for every game where they both appear (as well as yellow and blue ones in ''Super Mario World''), as well as the [https://ninten-switch.com/wp-content/uploads/2023/12/supar-mario-bros-wonder-for-nintendo-switch-kanzepki-guidebook-hanbai3.jpg Kadokawa guidebook for ''Super Mario Bros. Wonder'']. They do not do this for enemies that appear in multiple colors but have no mechanical differences between them, like [https://www.nintendo.com/jp/character/mario/en/history/3d_world/index.html Biddybuds, Para-Biddybuds, or Lava Bubbles in ''Super Mario 3D World''] (of note, they do recognize blue and red Lava Bubbles separately [https://www.nintendo.com/jp/character/mario/en/history/galaxy2/index.html in ''Super Mario Galaxy 2''], where they do have mechanical and behavioral differences with each other. I should also note that I have seen ''Super Mario 3D Land'' Biddybud figures sold with color denotations in their listed names in Japan, but it makes sense to do that for physical merchandise).
::I do not know the best approach for Super Mario Wiki. My gut feeling is that it would be best to stick to the systematics employed by the source material, and if that material is listing enemies separately by behavior or color or size, then it is not inherently unreasonable for them to get a dedicated article. What constitutes an "enemy" is not innate - it does not necessarily mean they are members of different species or anything like that (as apparent with [[Giant Goomba]]s, which can split into [[Hefty Goomba]]s, then normal [[Goomba]]s, indicating all Goombas have the capacity to mature into Giant Goombas and would be members of the same exact species, but they are not the same enemy). But our source material is inconsistent and fluid, adjusting based on the specific functions of individual games, as is the case with Lava Bubbles in SMG2 and SM3DW. They have flipflopped with whether they recognize different colors as separate enemies or the same ones (such as [https://imgur.com/32lQKbm here, in the bestiary for ''New Super Mario Bros.'' from 2006 that lumps Koopa Troopas together]) but they are also inconsistent in contemporary sources. In the encyclopedia, [[Big Deep Cheep]] is listed as a distinct enemy in the first ''New Super Mario Bros.'' and ''New Super Mario Bros. 2'' - it is lumped with the [[Deep Cheep|smaller one]] in ''New Super Mario Bros. Wii'' even though it has not undergone any behavioral changes, and this is in the same book. [[Dragoneel]]s are lumped as one enemy in the ''New Super Mario Bros. U'' section, even though there are fast, extremely long red Dragoneels and stout, slow-moving blue Dragoneels, which seems as valid a distinction as green and red Koopa Troopas. In the Kadokawa ''Super Mario Bros. Wonder'' excerpt I linked to above, it recognizes Red Koopa Troopas and Red Koopa Paratroopas as separate enemies from the green ones, but it lists brown and purple [[Trompette]]s as one enemy, as well as yellow and blue [[Konk]]s. This is despite the fact that the difference between the brown and purple Trombettes is that the latter turns around when it reaches the edge of a platform... just like red Koopa Troopas in the same game. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 13:18, September 28, 2024 (EDT)


{{@|ThePowerPlayer}} - Well those aren't given a different name, especially not in a consistent manner across multiple sources, which was the crux here. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 00:37, September 29, 2024 (EDT)
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.


@SeanWheeler: What? The proposal is about splitting particular enemy variants. It has nothing to do with what you said. {{User:Hewer/sig}} 09:24, September 30, 2024 (EDT)
'''Proposer''': {{User|Ahemtoday}}<br>
'''Deadline''': March 18, 2025, 23:59 GMT


{{@|Scrooge200}} - The SMM ones are to stay on the Blooper page, though. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 21:59, October 2, 2024 (EDT)
====Option Zero====
#{{User|Jdtendo}} Per Porple "Steve" Montage in the comments.
#{{User|Waluigi Time}} Per Porple.
#{{User|EvieMaybe}} perple montage
#{{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.


=== Split articles for the alternate-named reskins from ''All Night Nippon: Super Mario Bros.'' ===
====Option One====
''[[All Night Nippon: Super Mario Bros.]]'' has various alternatively named graphic swaps of things from ''Super Mario Bros.'', most of which relate to the cast and iconography of the show it is based on. These include:
#{{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.
*OkaP and Pakkun OkaP replacing Goomba and Piranha Plant ([[User:Doc von Schmeltwick/Projects/Early merges|split demoed here]] alongside stuff from the above proposal
#{{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.
*The ''Hiranya'' replacing the Star
*The various celebrities replacing the Toads (though admittedly the bonus one is unknown)


These are meant to be seen as different things from the originals, so the current system of lumping them in with them is awkward to say the least. The only real outlier here is the NBS logo replacing the axe, because from what I can tell [https://logos.fandom.com/wiki/Nippon_Broadcasting_System Katsu Yoshida never named the eye].
====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.


'''Proposer''': {{User|Doc von Schmeltwick}}<br>
====Option Three====
'''Deadline''': October 3, 2024, 23:59 GMT
#{{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.


====Sunplaza Support - all subjects====
<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|Doc von Schmeltwick}} - Per
#{{User|Ahemtoday}} Consistent with how we handle, say, [[Deku Baba]]s in ''[[Mario Kart 8]]''.
#{{User|Shoey}} I've always said the wiki needs more weirdo articles.
#{{User|Koopa con Carne}} Per. Don't see why not. Deku Baba is a good parallel.
#{{User|Mariuigi Khed}} Per.
#{{User|FanOfYoshi}} Per all.
#{{User|EvieMaybe}} i always thought we dont give ANNSMB enough coverage here. per all
#{{User|DrippingYellow}} I'm tempted to say this seems like unnecessary splitting of information, but I guess the information would still also be present in the main article, wouldn't it? This seems fine.
#{{User|ThePowerPlayer}} Per all.
#{{User|Camwoodstock}} Makes sense, and perhaps this could finally crack the mystery of who that unknown celebrity is! Per all.
#{{User|DryBonesBandit}} Per all, especially on [[Deku Baba]] and [[Keese]].
#{{User|Jazama}} Per all
#{{User|SeanWheeler}} Those look nothing like the original enemies.


====Sunplaza Support - only enemies====
====Option Four====
#{{User|Doc von Schmeltwick}} - Per


====OkaP Oppose====
====Comments====
#{{User|LinkTheLefty}} I'd personally not want to split these enemies since doing so is practically a degree away from re-splitting ''Super Mario World'''s "Fall" graphic swaps (and the ''Advance 2'' exclusives don't have their own names).
{{@|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)


====Katsu-eye Comments====
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)
: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)
::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)


===Remove "Koopa" and other name particles from Koopaling article titles - take 2===
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)
Since the [[MarioWiki:Proposals/Archive/60#Remove "Koopa" and other name particles from Koopaling article titles|last proposal]], other proposals have cropped up which sought to trim excess appellatives and nicknames from the titles of various character articles. As a result of these proposals, which saw little to no contention, the following changes were made:
*Professor Elvin Gadd [[Talk:Professor E. Gadd#Rename (proposal edition)|was moved to]] "Professor E. Gadd".
*Baby Donkey Kong [[Talk:Baby DK#Move to Baby DK|was moved to]] "Baby DK".
*Crossover characters with formerly descriptive titles (e.g. Sonic the Hedgehog, Fox McCloud) [[MarioWiki:Proposals/Archive/62#Change_full_names_of_crossover_characters_to_the_more_often_used_shortened_versions_in_article_titles|were moved to]] the shortened forms of their names (e.g. "Sonic", "Fox").


As well, before the aforementioned proposal:
On a vaguely related note, why do "tie" and "failed to reach consensus" have two separate colours in the proposal archive when the former is essentially a type of the latter? I don't really see the difference between them besides the fact that the wiki used to call them "ties". I also counted no more than four "tied" proposals in the entire archive, the last one having been in 2011, so it seems strange and confusing to still be using a separate colour for it. {{User:Hewer/sig}} 13:38, March 18, 2025 (EDT)
*Donkey Kong Country's Animal Friends [[MarioWiki:Proposals/Archive/56#Move_animal_names_from_the_Donkey_Kong_Country_series_to_just_their_normal_names|were moved to their shorthand names]].
:This is something I noticed as well while making the proposal — I kind of considered addressing it, but the proposal was already a bit sprawling, so bundling in a change to that seemed like a poor decision. If someone were to make a separate proposal to axe the "tie" color, I'd back it. [[User:Ahemtoday|Ahemtoday]] ([[User talk:Ahemtoday|talk]]) 14:10, March 18, 2025 (EDT)
*Conker the Squirrel [[Talk:Conker#Rename_to_Conker|was moved to]] "Conker".


Vigilant gamers and game lore extraordinaires will know why these changes were made: the short forms of these subjects' names have been much more prominent and recent in their relevant official works, and their display titles across the site did not reflect this predilection. The Koopalings, as well as [[Princess Daisy]], are now the outliers in this specific regard--but while [[Talk:Princess_Daisy#Move_to_"Daisy"|the sentiment against moving Daisy's name to its more common shortened form]] was the inconsistency that would arise with [[Princess Peach]] using her long title, I do not recall the Koopalings, as a group, having some special counterpart that would create a similar perceived inconsistency.
==Removals==
''None at the moment.''


Yeah, [[Larry]] was called "Larry Koopa" in a specific line of dialogue within Smash Ultimate, in a decade-and-a-half old licensed player's guide, and probably some 2010's toy that I'm sure users will name here in the comments, but the fact is, his short name has been promoted front-and-center within all of the games he has appeared from Mario Kart 8 back in 2014 until today, many of which are namedropped in the previous proposal. Same with his 6 siblings.
==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.


Besides, [[MarioWiki:Naming]] states plainly:
*The DS version has "Super Mario Bros." as a track, [https://www.youtube.com/watch?v=870WLPGnnKs using imagery from the games].
*"the name of an article should correspond to the '''most commonly used English name''' of the subject"
*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.''
*"the more commonly used modern name should be used as the title"
*''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.


and I believe it's only sensible for the wiki to mirror the more recent developments of the franchise in how a subject is introduced to readers.
''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.


Affected pages include:
'''Proposer''': {{User|Scrooge200}}<br>
{|
'''Deadline''': March 30, 2025, 23:59 GMT
|-
|
*[[Larry Koopa]] (will be moved to "Larry")
*[[Roy Koopa]] ("Roy")
*[[Wendy O. Koopa]] ("Wendy")
*[[Lemmy Koopa]] ("Lemmy")
*[[Morton Koopa Jr.]] ("Morton")
*[[Ludwig von Koopa]] ("Ludwig")
*[[Iggy Koopa]] ("Iggy")
|
*[[List of Larry Koopa profiles and statistics]] (will be moved to "List of Larry profiles and statistics")
*[[List of Roy Koopa profiles and statistics]] ("List of Roy profiles and statistics")
*[[List of Wendy O. Koopa profiles and statistics]] ("List of Wendy profiles and statistics")
*[[List of Lemmy Koopa profiles and statistics]] ("List of Lemmy profiles and statistics")
*[[List of Morton Koopa Jr. profiles and statistics]] ("List of Morton profiles and statistics")
*[[List of Ludwig von Koopa profiles and statistics]] ("List of Ludwig profiles and statistics")
*[[List of Iggy Koopa profiles and statistics]] ("List of Iggy profiles and statistics")
|}


Note:
====Support (Bring Us One Degree of Separation Closer to Jimmy Neutron)====
*This proposal targets only page titles. Even if it's a pass, articles can still acknowledge the full forms of these characters where appropriate, such as in Koopaling article openers.
#{{User|Scrooge200}} Per proposal.
*If this proposal passes, the templates in [[:Category:Koopaling content templates]] become obsolete and are to be abolished.
#{{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.


'''Proposer''': {{User|Koopa con Carne}}<br>
====Oppose (No More Megalovania, Please)====
'''Deadline''': October 4, 2024, 23:59 GMT


====Support====
====Comments' Perfect Math Class====
#{{User|Koopa con Carne}} per proposal, and per the former proposal as well, which I encourage participants to peruse. (Though, this time, with no multi-option shenanigans.)
{{@|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)
#{{User|Axii}} Per con Carne (like the last time).
: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)
#{{User|Nintendo101}} This may be controversial, but I think this is fine and in-line with our policies. These characters have largely only been referred to by their first names since ''Mario & Luigi: Superstar Saga''. This does not mean Ludwig's full name is not "Ludwig von Koopa" or that it does not see occasional use in marketing and in games - it just means the title of the article is just Ludwig. I personally do not think that is as systematically harmful or erroneous as previous proposals seemed to have suggested. Lots of reference material does this. For example, the name of the {{wp|Mark Twain}} article on Wikipedia is not "Samuel L. Clemens" in any language.
::''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)
#{{User|LinkTheLefty}} Needless to say, there have been a few changes since the last time this was proposed.
::{{@|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)
#{{User|Camwoodstock}} Per proposal. It seems only fair as we clamp down more and more on these elongated page titles.
#{{User|Tails777}} Supported once and I'll do it again. Per proposal.
#{{User|Hewer}} Per all. I never really understood the main argument against this last time ("the full names still exist", as though that means they should automatically take priority over their more common short counterparts).
#{{User|Technetium}} Per all.
#{{User|DesaMatt}} Per all von Koopa.
#{{User|EvieMaybe}} while i don't agree with the de-title-ification that's been going on, if we're going to do it we might as well be consistent with it.
#{{User|ThePowerPlayer}} The fact that there exists an entire category of templates just to circumvent a standard that violates MarioWiki:Naming is concerning, to say the least.
#{{User|Jdtendo}} Per all.
#{{User|YoYo}} per all
#{{User|BMfan08}} Per all.
#{{User|Nightwicked Bowser}} Per all, I know I opposed this before but I've changed my mind after several similar proposals since then have passed.
#{{User|Jazama}} Per all
#{{User|OmegaRuby}} Per Koopall


====Oppose====
===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.===
#{{User|SeanWheeler}} No. Okay, no. I'm trying to make a case for undoing the proposal that shortened the Sonic characters' names. I've got a strong case for Fox McCloud in that not only was his last name mentioned in every Smash game, his [[Costume Mario#92|costume]] in [[Super Mario Maker]] is the "Fox McCloud" costume, not the "Fox" costume. And I know that if this proposal passes, Peach and Daisy are next.
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]])


====Comments====
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!)  
To clarify my position on Daisy, it was not because I thought the proposal was unreasonable. To me, an analogous situation would be drafting a proposal to only change the name of Iggy Koopa's article and none of other Koopalings. Maybe others don't see Peach and Daisy as related to each other as sibling characters like the Koopalings, but that's how I feel at least. I would receive a proposal that included both Peach and Daisy differently. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 15:31, September 27, 2024 (EDT)
:I reworded that point about the Daisy vs. Peach situation to sound less like a potshot. Sorry. {{User:Koopa con Carne/Sig}} 15:34, September 27, 2024 (EDT)
::I thought it was funny :) Just wanted to clarify my position. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 15:37, September 27, 2024 (EDT)
:::I appreciate that you took it in good humor, but I've made a point that I'll try and be more careful with the way I word my statements. {{User:Koopa con Carne/Sig}} 15:41, September 27, 2024 (EDT)


@SeanWheeler: If Mario Maker costume names were the decider, [[Mr. Resetti]] would just be "Resetti", and indeed, Princess Peach and Princess Daisy would just be Peach and Daisy. But the main thing the Fox page covers isn't a costume in Mario Maker, it's his more common, prominent, and recent Smash appearances, in which the main name used to refer to him is always just "Fox". (Also, Sonic's Mario Maker costume is just called "Sonic", not "Sonic the Hedgehog".) {{User:Hewer/sig}} 09:03, September 30, 2024 (EDT)
But we’re already doing this, just under the veneer of putting it under existing articles. These articles, for example:
:It's not just the Mario Maker costumes. He's been referred to as "Fox McCloud" in Melee's trophies and Ultimate's spirits, plus in Snake's Codec and Palutena's Guidance. [[User:SeanWheeler|SeanWheeler]] ([[User talk:SeanWheeler|talk]]) 17:22, September 30, 2024 (EDT)
::And he's been referred to as "Fox" in his actual role as a playable character in every single Smash game. As I've repeated countless times in our [[MarioWiki:Proposals/Archive/62#Change full names of crossover characters to the more often used shortened versions in article titles|previous]] [[Talk:Shadow (character)#Rename to "Shadow"|debates]], this isn't an argument of whether the full name exists, it only matters which name is more common. Please stop cherry-picking the times when the full name was used in profiles and such and acting like that automatically outweighs the more common name. {{User:Hewer/sig}} 17:56, September 30, 2024 (EDT)
:::I feel like these proposals shortening names are meant to take the "common name" part of the naming policy to it's literal conclusion. The article names were fine before they were changed by proposals, and now we're changing very distinctive article names to generic names. That's not good for disambiguation. The shortened names could be used as redirects, but we are discouraged from linking redirects, making me confused why we have redirects at all. I mean, link templates for the Koopalings? In November, I'm going to make a proposal to encourage linking redirects. My proposal to overturn the crossover character naming was only delayed by me not having unlocked the Sonic Character Book at the Secret Shop in Mario & Sonic at the Olympic Winter Games. Yes, I was going to bank on the full names being used somewhere in the games being enough to outweigh the player names. Are Peach and Daisy are going to lose their princess titles for the sake of following the naming conventions? I think the naming rule should be changed. Problem is, I can't figure out how to word it in a way to have the pages moved back to the names I want. [[User:SeanWheeler|SeanWheeler]] ([[User talk:SeanWheeler|talk]]) 23:55, September 30, 2024 (EDT)
::::This proposal is trying to get rid of those Koopaling templates, though. We have redirects for search purposes, not for linking. And why shouldn't the common name policy be taken to its "literal conclusion"? Are you saying you'd rather we enforced it inconsistently? That we should only enforce it when you personally happen to prefer the common name? We shouldn't ignore official sources just so that we can use the names we prefer. Also (another thing I've repeated endlessly), calling these names "generic" is subjective at best and just false at worst. Nothing about "Larry" makes it inherently a more "generic" name than "Mario" or "Pauline", and if Nintendo is content to use the shorter names to identify the characters, we have no reason not to follow suit. "But Peach and Daisy" is also a bad counterargument when several of the users supporting this proposal also supported the Daisy proposal, myself included. {{User:Hewer/sig}} 06:07, October 1, 2024 (EDT)
:::::Redirects just for search purposes are practically useless when there's autofill and search results. Linking to a redirect would have less bytes then pipelinking wouldn't it? And no, I don't like inconsistent rules either. I'm still trying to figure out my proposal to the naming convention. I don't want the most frequently used names which would just reduce everyone to just their first names or nicknames. Wiki page titles should be more formal than that. But during the Shadow proposal, you have pointed out some awful full names, so giving literally everyone their full names would be out too. And I feel nostalgia for the names the wiki had for years, so I wouldn't want Bowser to be moved to King Bowser Koopa. What would be the best naming convention that would have us move most if not all these characters back to their original page titles? I thought maybe "the longest common-used name" as in the full name that was referenced in most of the characters' appearances, which would keep Peach at Princess Peach (because she hasn't used her Toadstool surname in a long time, and she has been referred to as Princess Peach at least once in most of the Mario games, right?) That would definitely move Fox back to Fox McCloud. But with that rule of naming the characters their fullest name used in the most appearances, that would force us to use the full names of one-time characters like [[Squirps]] becoming {{fake link|Prince Squirp Korogaline Squirpina}}, so that rule wouldn't work out with me either. I don't have that many Mario games, so it would be hard to verify when each name was used in each game. If I go for "best known name," that's probably going to rely too much on bias, so that wouldn't work either. And if I just make a proposal to undo every move in the wiki's history and make it so that every article name is simply the original title, I doubt anyone would be on board if there were more legitimate reasons those pages moved like if some page titles started out misspelled. I've voted to shorten parentheticals, so it would make me a hypocrite to revert all the moves I've supported. This is really hard, especially as we're moving articles on a case-by-case basis when the articles should already be following the naming rules. Instead of the case-by-case basis, we really need to clarify the naming rules and what we mean by the "most common name." If we mean by the given name most frequently said in every game, then maybe the rule should be changed. Tell me, how many games have the Koopalings been referred to as their full names at least once? How many manuals and guides have their full names? They use their first names in playable character data, so how do we count playable character data? I would like to only count the playable character data just once. But how will we count dialogue? If we count every instance in dialogue, would we shorten Diddy Kong to just Diddy? Would Bowser Jr. be called Junior? This is all so complicated. All it shows is that our current naming rules aren't good. [[User:SeanWheeler|SeanWheeler]] ([[User talk:SeanWheeler|talk]]) 23:06, October 1, 2024 (EDT)
::::::In my opinion, I think our approach to article names for characters has been a bit technocratic. I don't think we need a strict, blanketedly applied naming policy is as beneficial as some think, and I really deciding these things on a case by case basis is perfectly fine.
::::::I personally would be in favor of returning the [[Fox]] article to Fox McCloud, purely because the word "fox" alone as plenty of connotations on its own and including the surname is just immediately clarifying that it is the main character from ''Star Fox''. I similarly would feel fine with returning the ''Sonic'' characters to their full names because it is just immediately pretty clarifying what the article's subject is about, as opposed to something else in the ''Mario'' series called a shadow. Some of them had to have clarifications between parentheses attached to the end anyways, which wouldn't have been necessary if we just kept the full names.
::::::Making decisions like that does not have to have ramifications on the names of other character articles. Inconsistency is not inherently bad if it leads to better clarification for readers. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 23:50, October 1, 2024 (EDT)
:::::::Inconsistency is bad. Following your logic, we could end up with characters like "Sonic" and "Espio" keeping short names while others like "Shadow the Hedgehog" and "Big the Cat" get their full names, since only the latter share their names with other subjects. And wasn't inconsistency the main reason you didn't want to shorten "Princess Daisy"? Also, why would "Fox" cause clarification problems when he doesn't share that name with anything else on the wiki? Would we just arbitrarily decide which names do and don't need clarification? The best solution to all these problems is to stick to how official sources most commonly handle the names, i.e. the current naming policy (which I don't think needs changing, just enforcing). Also, @SeanWheeler, redirects are not "practically useless", they help significantly with streamlining the search process and helping people find what they're looking for. {{User:Hewer/sig}} 12:32, October 2, 2024 (EDT)
::::::::Well, looks like my naming conventions amendment proposal in November is going to have a bunch of options. And yes, Fox could cause clarification problems because that's his species. Sure, we don't have an article on the Fox species but we have articles on [[Dragon]], [[Elephant]], [[Goat]], and used to have pages on [[Talk:Human#Delete page|Human]] and [[Talk:Giraffe]]. Then again, those Dragon, Elephant and Goat pages are now more about enemies than the species. And [[wikipedia:20th Century Fox|20th Century Fox]] would be a bigger Fox name than Fox McCloud. I wouldn't be surprised if someone searched for the company only to end up on Fox McCloud's page. Sonic is also the name of a [[wikipedia:Sonic Drive-In|restaurant]], and is a [[wiktionary:sonic|word]] related to the concept of sound. It really does help clarify things to use the longer names. To take the common name part of the policy too literally, you'd find most characters having just their first names be the most common name. I'd vote to change the wording from "most common" name to "best known name." Yes, that would rely on bias of the users, but I really can't stand these proposals reducing names. At least if the "best known name" was followed instead of the "commonly used name," the move proposals made afterward wouldn't be so much about rule violations in the naming convention but what the wiki finds to be the more popular name for the characters. And of course, fan nicknames and speculation wouldn't count. [[User:SeanWheeler|SeanWheeler]] ([[User talk:SeanWheeler|talk]]) 02:36, October 3, 2024 (EDT)
:::::::::Your suggestion is to ignore official sources in favour of fan preferences (especially when they're your personal preferences), which goes against everything the naming policy and the wiki in general strive for. Besides, it's not like these characters' shortened names are obscure (all the results when I google "Sonic" are about the hedgehog, and I find it a bit hard to believe that "Miles "Tails" Prower" is a more well-known name than "Tails"). Also, who is looking up 20th Century Fox and Sonic Drive-In on the Super Mario Wiki??? [[Wikipedia:Mario (disambiguation)|Mario]] is two films, two TV series and two songs, is it time to rename his page?  {{User:Hewer/sig}} 03:06, October 3, 2024 (EDT)
::::::::::Well, since we have pages on [[Universal Pictures]] and [[Taco Bell]], maybe someone browsing the companies could be wondering if 20th Century Fox or its subsidiaries had ever made anything Mario related. And if the Sonic Drive-In were to ever make a Nintendo promotion with Mario toys, then we would have given the Sonic Drive-In a page like [[Taco Bell]], [[McDonald's]], [[Burger King]] and [[Wendy's]]. Oh yeah, we've got a [[Wendy's]] just like the [[Wendy O. Koopa|Koopaling]]. As for the case with Mario, those two films, TV series and songs have nothing to do with our Mario. Mario is the face of the wiki, so it would be obvious what Mario people would search for on this wiki. But Fox McCloud was just a character that Mario met in Super Smash Bros. As a Star Fox character, nobody would think to look for him on here without knowing how we handle crossover characters, would they? And for people who remembered the Nintendo and Sega rivalry in the nineties but were unaware of the Olympic series or Smash's use of third-party characters would be very surprised to find Sonic the Hedgehog on here. The crossover characters definitely need to be more distinguished than Mario himself. [[User:SeanWheeler|SeanWheeler]] ([[User talk:SeanWheeler|talk]]) 16:05, October 3, 2024 (EDT)


===Overturn the [[MarioWiki:Proposals/Archive/55#Delete_Category:User_eo|proposal]] that resulted in the deletion of [[:Category:User eo]] (category for speakers of {{wp|Esperanto}})===
*[[Shell dash]] ([[Shell Mario]])
Myself, I don't care about this language, and needless to say, neither do most people on the planet, but I take issue with the proposal that had it removed in the first place for a few reasons.
*[[Dive]] (Claw dives of [[Cat Mario]])
*The proposal argues that this language "is not a real language", that "nobody really picked it up", and likens it to the fictional language of Klingon. Despite its status as a constructed language, it is, in fact, very much a real language intended and created to be functional. It has a(n admittedly small) number of speakers across the planet, some of whom may well be potential editors on this wiki for all we know. The comparison to Klingon, which was created with an artistic purpose, is misleading.
*[[Drill Spin]] ([[Propeller Mario]])
*The proposer [[User talk:Doomhiker#Woah|was outed as an extremist]] (read up on the details at your own risk) who seemingly was planning to have other language-based user categories removed, as he followed up with another [[MarioWiki:Proposals/Archive/55#Delete_Category:User_ka|proposal targeting the Georgian user category]]. The wiki's policies outline that we shouldn't assume bad faith in users, but given the circumstances here, I hope you'll allow me the assumption that this user had ulterior motives in their little curatorial project, namely in altering the wiki ever so slightly according to their outlooks. Proposal failed and the user was banned for their concerning behavior, preventing further such proposals from being made.


Now, as you'd expect, the Esperanto user category certainly never saw much use--in fact, [https://web.archive.org/web/20140712133001/http://www.mariowiki.com/Category:User_eo only one user employed it as of 2014] <small>(archive.org)</small> and even then [https://web.archive.org/web/20140711152028/http://www.mariowiki.com/User:Pakkun only listed Esperanto as a second language] <small>(archive.org)</small> (though, the very point of Esperanto was to be an auxillary language between people who don't speak the same native language). That user, who goes by {{user|Pakkun}}, has since taken the category off their page, so you could argue that this proposal lacks a tangible purpose as "User eo" would be dead on arrival should it be recreated.
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.


The point of this proposal, however, isn't to recreate this language immediately; it is to negate the proposal that currently prevents its creation if someone ever considers they'd derive some use from it. '''This community should be open to anyone regardless of their cultural background.''' The previous proposal is contrary to that.
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?


'''Proposer''': {{User|Koopa con Carne}}<br>
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.
'''Deadline''': October 5, 2024, 23:59 GMT


====Support====
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.
#{{User|Koopa con Carne}} per proposal.
#{{User|Ahemtoday}} Per proposal.
#{{User|Camwoodstock}} Honestly, we would be down for ''more'' Conlangs to have user categories. We can't imagine the overlap of, say, Vötgil speakers to Mario Wiki users is very large, but like, in regards to a strictly English wiki, the Conlang categories in particular are just for-fun categories at the end of the day, and who the hey are we to ''expressly prohibit'' other people's fun? And even in the most generous reading of the events, it still feels like a bit of warped priorities when some categories have been in need of reforms for awhile now <small>(sorry about the Thieves category thing, we're still thinking of that and honestly at this point we wouldn't mind someone else chipping in with that)</small> and haven't gotten them, but we have an entire proposal dedicated to... Deleting a category for Esperanto speakers??? (And for the record, this was back when [[:Category:Canines]] was called Dogs--something something, obligatory mention of [[Penkoon]].)
#{{User|Shadow2}} We DID this? wtf??
#{{User|Nintendo101}} Per proposal.
#{{User|DryBonesBandit}} Per proposal.
#{{User|Hewer}} Per proposal.
#{{User|Arend}} With the provided context, something about Trig Jegman's proposals rubs me the wrong way. If it's true that he was trying to gradually remove other languages, where would he stop? He stated that Esperanto and Gregorian are languages not supported by Nintendo (a weak argument IMO, as Nintendo =/= this wiki), and not widely spoken, so would he first try to get all small-spoken languages removed? Would he eventually try to get larger languages removed just because Nintendo doesn't support these languages? Would he eventually go even further and get even languages that ''are'' supported by Nintendo removed because they're not as widely spoken as other languages? Would he eventually make it so that English is the ''only'' language remaining? Would he then remove that category too because if that's the only language category for users, then what's the point of keeping it? Or worse, is this a ploy to recognize who is native to other languages and would he try to get non-English users banned so only English-speaking users have access to the wiki (and ''then'' remove the English category)? ...Uh...fearmongering aside, per all.
#{{User|Waluigi Time}} No harm having it if people want to use it.
#{{User|TheFlameChomp}} Per all.
#{{User|ThePowerPlayer}} Per all.
#{{User|Axii}} Per all.
#{{User|Mario}} The more the Marior. That older proposal was dumb.
#{{User|Jazama}} Per all
#{{User|SeanWheeler}} I'm not a fan of banning users for off-site drama, especially when it's political. But if his proposal was bigoted, then maybe it should be overturned.
#{{User|FanOfYoshi}} Per all, especially Sean. This proposal was asinine at best, in retrospect, and harmful at worst. And that's coming from a man who doesn't have full context as to what happened.
#{{User|Shy Guy on Wheels}} Per all. That category never hurt nobody.
#{{User|Killer Moth}} Per all.


====Oppose====
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.


====Comments====
[[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.
The real question is if we can have a Klingon category (as [[User:Alex95|a certain other editor who is no longer with us due to concerning behavior]] mentioned on that proposal). [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 17:11, September 28, 2024 (EDT)
:Up for debate whether user categories can have some basis in fiction. {{User:Koopa con Carne/Sig}} 17:16, September 28, 2024 (EDT)
:We think that Conlangs in general should just be allowed, just because it both feels really, really weird to try to police ''what'' Conlangs "count" as languages, and because the idea of focusing even more proposals on such a for-fun topic feels.... A little too much, when that effort is best used elsewhere. ;P {{User:Camwoodstock/sig}} 18:14, September 28, 2024 (EDT)


<s>We should be open for Inklingese and Smurf.</s> {{User:Arend/sig}} 20:24, September 28, 2024 (EDT)
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.
:<s>Per Arend.</s> --{{User:FanOfYoshi/sig}} 05:50, September 30, 2024 (EDT)


===Lower the requirement for a disambiguation page from 5 to 4===
'''Proposer''': {{User|Salmancer}}<br>
As of now, the requirement for a disambiguation page's creation is five pages:
'''Deadline''': March 31, 2025, 23:59 GMT
:''"If there are five or more pages which could be reasonably associated with a given name, then a disambiguation page must be created"'' ([[MarioWiki:Naming]])
This rule feels needlessly restrictive, considering the amount of clutter links make at the very top of the page. "For a minigame in the ''WarioWare'' series, see X. For an object in ''Super Mario Odyssey'' found in the Luncheon Kingdom, see Y. For an underwater enemy from...", you get the idea. If this proposal passes, the threshold on MarioWiki:Naming will be lowered from 5 to 4.


'''Proposer''': {{User|Axii}}<br>
====Merge moves and Listify Fly: Merge moves to forms, and convert [[Fly]] into a list====
'''Deadline''': October 6, 2024, 23:59 GMT
#{{User|Salmancer}} Per proposal.


====Support====
====Merge moves, Fly is free: Merge moves to forms, but keep Fly as is====
#{{User|Axii}} ^
#{{User|ThePowerPlayer}} One or two other articles are fine, but having three separate articles in the <nowiki>{{about}}</nowiki> template at the top of the page is the point where a disambiguation page is ideal.
#{{User|SeanWheeler}} We don't need to clutter the {{tem|About}} template.
#{{User|Killer Moth}} Per proposal.
#{{User|Pseudo}} Frankly, I'd support bringing the requirement as low as 3. Per proposal.


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


====Comments====
====Oppose: Status quo====
Do you have any examples of how many subjects would be affected by this change? {{User:LadySophie17/sig}} 10:52, September 29, 2024 (EDT)
#[[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?
:I don't think there's an easy way to tell, but I can't imagine it being too many. [[User:Axii|Axii]] ([[User talk:Axii|talk]]) 12:05, September 29, 2024 (EDT)
#{{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.
#{{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.


===Shorten the disambiguation identifier for ''Yoshi's Island'' pages with the subtitle only - take two===
====Comments (Merge moves of forms to forms even if they are non-unique and replace Fly with a list)====
Last season, I had to cancel [[MarioWiki:Proposals/Archive/67#Use shorter disambiguation identifier (without subtitle) for Yoshi's Island pages|my last proposal]] since I was caught plagiarizing [[MarioWiki:Proposals/Archive/67#Use shorter disambiguation identifier (without subtitle) for Donkey Kong Country 2 and Donkey Kong Country 3 pages|someone else's proposal]]. This time, I've come up with another proposal that is not plagiarized.
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)


Take the "Choose a Game" screen and the main game's title screen in ''Yoshi's Island: Super Mario Advance 3'' for example. As you see, the logo for the main game on both screens ONLY reads ''Yoshi's Island'', not ''Super Mario World 2: Yoshi's Island''.
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)
: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)


The following pages will be affected:
{{@|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)
: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)


{| class="wikitable"
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..
! Current name
<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]]
! Will be moved to
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)
|-
| [[Fuzzy (Super Mario World 2: Yoshi's Island)|Fuzzy (''Super Mario World 2: Yoshi's Island'')]]
| {{fake link|Fuzzy (''Yoshi's Island'')|Fuzzy (Yoshi's Island)}}
|-
| [[King Bowser's Castle (Super Mario World 2: Yoshi's Island)|King Bowser's Castle (''Super Mario World 2: Yoshi's Island'')]]
| {{fake link|King Bowser's Castle (''Yoshi's Island'')|King Bowser's Castle (Yoshi's Island)}}
|-
| [[Magnifying Glass (Super Mario World 2: Yoshi's Island)|Magnifying Glass (''Super Mario World 2: Yoshi's Island'')]]
| {{fake link|Magnifying Glass (''Yoshi's Island'')|Magnifying Glass (Yoshi's Island)}}
|-
| [[Spiked Fun Guy (Super Mario World 2: Yoshi's Island)|Spiked Fun Guy (''Super Mario World 2: Yoshi's Island'')]]
| {{fake link|Spiked Fun Guy (''Yoshi's Island'')|Spiked Fun Guy (Yoshi's Island)}}
|-
| [[World 1 (Super Mario World 2: Yoshi's Island)|World 1 (''Super Mario World 2: Yoshi's Island'')]]
| {{fake link|World 1 (''Yoshi's Island'')|World 1 (Yoshi's Island)}}
|-
| [[World 2 (Super Mario World 2: Yoshi's Island)|World 2 (''Super Mario World 2: Yoshi's Island'')]]
| {{fake link|World 2 (''Yoshi's Island'')|World 2 (Yoshi's Island)}}
|-
| [[World 3 (Super Mario World 2: Yoshi's Island)|World 3 (''Super Mario World 2: Yoshi's Island'')]]
| {{fake link|World 3 (''Yoshi's Island'')|World 3 (Yoshi's Island)}}
|-
| [[World 4 (Super Mario World 2: Yoshi's Island)|World 4 (''Super Mario World 2: Yoshi's Island'')]]
| {{fake link|World 4 (''Yoshi's Island'')|World 4 (Yoshi's Island)}}
|-
| [[World 5 (Super Mario World 2: Yoshi's Island)|World 5 (''Super Mario World 2: Yoshi's Island'')]]
| {{fake link|World 5 (''Yoshi's Island'')|World 5 (Yoshi's Island)}}
|-
| [[World 6 (Super Mario World 2: Yoshi's Island)|World 6 (''Super Mario World 2: Yoshi's Island'')]]
| {{fake link|World 6 (''Yoshi's Island'')|World 6 (Yoshi's Island)}}
|}


Once this proposal passes, we'll be able to use the shorter disambiguation identifier with ONLY the subtitle for the ''Yoshi's Island'' pages.
"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)


'''Proposer''': {{User|GuntherBayBeee}}<br>
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)
'''Deadline''': October 10, 2024, 23:59 GMT
: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.
====Support (''Yoshi's Island'')====
: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)
#{{User|GuntherBayBeee}} Per proposal
::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!"
====Oppose (''Super Mario World 2: Yoshi's Island'')====
:::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)
====Comments====
:::::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 14:10, March 18, 2025

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

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

How to

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

Rules

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

Basic proposal formatting

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

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

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

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

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

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

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

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

Poll proposal formatting

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

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

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

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

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

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

;Oppose

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

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

;Oppose

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

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

;Oppose

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

For the purposes of the ongoing proposals list, a poll proposal's deadline is the latest deadline of any ongoing option(s). A poll proposal is archived after all of its options have settled, and it is listed as one single proposal in the archive. It is considered to have "passed" if one or more options were approved by voters (resulting in a change from the status quo), and it is considered to have "failed" if all options were rejected by voters and no change in the status quo was made.

Talk page proposals

Proposals concerning a single page or a limited group of pages are held on the most relevant talk page regarding the matter. All of the above proposal rules also apply to talk page proposals. Place {{TPP}} under the section's heading, and once the proposal is over, replace the template with {{settled TPP}}. Proposals dealing with a large amount of splits, merges, or deletions across the wiki should still be held on this page.

All active talk page proposals must be listed below in chronological order (new proposals go at the bottom) using {{ongoing TPP}}. Include a brief description of the proposal while also mentioning any pages affected by it, a link to the talk page housing the discussion, and the deadline. If the proposal involves a page that is not yet made, use {{fake link}} to communicate its title in the description. Linking to pages not directly involved in the talk page proposal is not recommended, as it clutters the list with unnecessary links.

List of ongoing talk page proposals

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)

On a vaguely related note, why do "tie" and "failed to reach consensus" have two separate colours in the proposal archive when the former is essentially a type of the latter? I don't really see the difference between them besides the fact that the wiki used to call them "ties". I also counted no more than four "tied" proposals in the entire archive, the last one having been in 2011, so it seems strange and confusing to still be using a separate colour for it. Hewer (talk · contributions · edit count) 13:38, March 18, 2025 (EDT)

This is something I noticed as well while making the proposal — I kind of considered addressing it, but the proposal was already a bit sprawling, so bundling in a change to that seemed like a poor decision. If someone were to make a separate proposal to axe the "tie" color, I'd back it. Ahemtoday (talk) 14:10, March 18, 2025 (EDT)

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=4788800"