MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
(Proposal archived)
 
Line 1: Line 1:
{{MarioWiki:Proposals/Header}}
{{/Header}}
 
==Writing guidelines==
==Writing guidelines==
''None at the moment.''
''None at the moment.''


==New features==
==New features==
===Introduce a new type of proposal===
{{early notice|February 14, 2025}}
While our wiki's proposal system is a pretty good way to democratize choices, it does have its limitations. A single-winner vote is simply not robust enough to support certain types of decisions, most notably with the ones that require settling various parts independently (such as [[Gallery_talk:Super_Mario_(Kodansha_manga)#Split_Waluigi_.28Super_Mario_Land_2:_6-tsu_no_Kinka_2.29|this proposal]], which had to decide on both the romanization and the identifier separately), or sorting several things at once (see [https://www.mariowiki.com/index.php?title=Talk:Frog&oldid=2568046#Split_Frog_and_cut_down_on_its_genericness.2C_take_2 this old proposal attempt] for a maximal worst-case scenario). So what do we do?
My suggestion is to create a second type of proposal, tentatively named '''poll proposals'''.
*Poll proposals can feature several options, much like regular proposals (which might also need their own name), but each option is its own binary vote.
*Instead of commenting "per proposal" or "per all" or giving some insight, voters must indicate "for" or "against" on each option they vote on. Further comments are allowed, of course.
**Abstaining from some options should be allowed too.
*Each vote is subject to the same approval percentages as a regular old Support/Oppose proposal.
*Early closures and term extensions get murkier when some options might meet the threshholds while others do not. This might warrant some further discussion, and I do not think I have the authority to decide how this should be settled. Up to staff, I guess?
*Poll proposals must be clearly marked as such, to make it clear how one is supposed to vote.
This allows us to more efficiently make several decisions at once, instead of having to string several follow-up proposals together. For an example, I'm sure many of you have seen proposals that do two changes at once and have the options marked as "A, B, both, neither". This would contract those to simply "A, B".
I've written down a [[User:EvieMaybe/Poll proposal|mockup poll proposal]] for those who need a more visual example. Of course, if this passes, staff is free to change aspects of the implementation as they see fit, particularly the specific word choices of "poll proposal", "for" and "against".
'''Proposer''': {{User|EvieMaybe}}<br>
'''Deadline''': February 21, 2025, 23:59 GMT
====Support====
#{{User|EvieMaybe}} Per proposal.
#{{User|RetroNintendo2008}} Mock-up looks pretty good! The more variety when it comes to how we make major decisions, the better.
#{{User|PopitTart}} For. Having templates as Camwoodstock suggests would also be good to make it easier to see at a glance how votes are distributed.
#{{User|Rykitu}} Neat idea, per all.
#{{User|Waluigi Time}} Per proposal, as long as the suggestion to have a better visual indicator for support/oppose votes is taken into account. I lean more towards Ahemtoday's suggestion since it'll be easier to keep count of them.
#{{User|ThePowerPlayer}} Per Waluigi Time.
#{{User|1468z}} Per all.
#{{User|Camwoodstock}} Per Waluigi Time and Ahtemtoday's suggestion; as long as tallying is made easier than the original example, we see no reason to not add these.
#{{User|Killer Moth}} Per all.
#{{User|Nintendo101}} Good idea for larger projects. Per proposal.
#{{User|Mushroom Head}}{{hide|show=For|hide=Per all.|shown=1}}
====Oppose====
====Comments on proposal proposal====
Our only complaint is in the mockup; we feel like it could be made a ''lot'' more clear which votes are for/against in some way. Maybe a pair of <nowiki>{{For}}</nowiki> and <nowiki>{{Against}}</nowiki> templates? (In this context, we think making these templates is fine; you already need to know how to use <nowiki>{{User}}</nowiki> to vote, after all, and we're imagining these will be very, very simple to use.) {{User:Camwoodstock/sig}} 17:41, February 7, 2025 (EST)
:That, but what purpose would "against" votes have compared to just not voting on that option? {{User:Mario/sig}} 17:42, February 7, 2025 (EST)
::Same as it would in a regular proposal, each option acts as an individual 2-option vote. If no one opposes an option (and it meets quorum requirements), then it passes. --[[User:PopitTart|PopitTart]] ([[User talk:PopitTart|talk]]) 17:56, February 7, 2025 (EST)
:I feel like the easiest solution is just "for" and "against" subheaders under each option. [[User:Ahemtoday|Ahemtoday]] ([[User talk:Ahemtoday|talk]]) 18:04, February 7, 2025 (EST)
::That would also work for us! Our only real concern is that this could result in level-5 subheaders on proposals on this page specifically, which... Don't look all that great. Even still, we just need ''something'' to disambiguate at a glance what is what, and this will do the job just well. {{User:Camwoodstock/sig}} 23:01, February 7, 2025 (EST)
:@Camwoodstock you're absolutely right and that's a very good idea! {{User:EvieMaybe/sig}} 18:44, February 7, 2025 (EST)
I'm a little bit stuck on what kind of use cases this type of proposal would be for. I've had to split a proposal into [[Category_talk:Music#Proposal:_Reorganize_this_category|three]] [[Category_talk:Musical_groups#Change_into_a_category_for_musical_groups|separate]] [[Category_talk:Sound_tests#Rename_to_.22Sound_tests.22|ones]] myself once, but even if this type of proposal existed at the time, I still feel like it would have made the most sense to do them separately. I suppose it would definitely help for [https://www.mariowiki.com/index.php?title=Talk:Frog&oldid=2568046#Split_Frog_and_cut_down_on_its_genericness.2C_take_2 the "split combinatorial explosion" example you gave], but I can't really envision what [[Gallery_talk:Super_Mario_(Kodansha_manga)#Split_Waluigi_.28Super_Mario_Land_2:_6-tsu_no_Kinka_2.29|your other example]] would look like as a poll proposal. [[User:Ahemtoday|Ahemtoday]] ([[User talk:Ahemtoday|talk]]) 18:04, February 7, 2025 (EST)
:well, the way i was thinking of is that it'd have one option for whether to use Waruiji or Waluigi, and another on which identifier to use. i admit it's not as clean bc there's more than two options for identifiers, but something like that could work for similar cases. i came up with this proposal idea while thinking about a proposal narrowing down if cultural/historical/mythological/folklore references count for [[List of references in the Super Mario franchise]], and thinking that it'd be great if we could vote on each of them individually without having to make a proposal for each. {{User:EvieMaybe/sig}} 18:44, February 7, 2025 (EST)
:I'm interested in using this to create a proposal for [[Dotted-Line Block]], options being "Split the ones that turn into ! Blocks", "Split the ones that are on a time limit", "Split the rhythm blocks from ''SMBW''", "Merge Color Block", and "Merge Switch Block (Mario & Wario)" --[[User:PopitTart|PopitTart]] ([[User talk:PopitTart|talk]]) 19:21, February 7, 2025 (EST)
{{@|EvieMaybe}} How would you prevent two opposing options from both passing with this type of proposal? How would you prevent the scenario that both Waruiji and Waluigi had enough support to succeed? Would users be expected to vote "for" on one option and "against" on its opposing option? I'm just not understanding how this is helpful, honestly. --{{User:Pizza Master/sig}} 17:01, February 13, 2025 (EST)
:I do not want to put words in eviemaybe's mouth, but I assume if you had a proposal with only two or three types of outcome, you would not use this type of proposal structure. It would be here if you need it for larger proposals that aim to resolve several related issues all at once, rather than make individual proposals for each one. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 17:09, February 13, 2025 (EST)
:i feel like you misunderstand how i proposed it. Why put Waruiji and Waluigi in two options, when you can just make an option where if it passes, you use Waruiji, and if it doesn't, you use Waluigi? {{User:EvieMaybe/sig}} 18:21, February 13, 2025 (EST)
==Removals==
''None at the moment.''
''None at the moment.''


==Removals==
==Changes==
===Remove "Koopa" and other name particles from Koopaling article titles===
===Merge the Ancient Beanbean Civilizations to List of implied species (and Hooroglyphs info to that)===
Starting with ''Mario Kart 8'' on Wii U hitherto the time of this proposal, Mario games have exclusively referred to Koopalings using their first names: [[Larry Koopa|Larry]], [[Ludwig von Koopa|Ludwig]], [[Wendy O. Koopa|Wendy]] etc. These games include ''Paper Mario: Color Splash'', ''Mario & Luigi'' games, ''Mario Kart Tour'', ''Dr. Mario World'', ''Super Smash Bros.'' games, and ''Mario & Sonic'' games (Rio 2016; Tokyo 2020).
Another multiple-way merge! This is about the following articles:
*[[List of implied species]]
*[[Hoohoo civilization]]
*[[Soybean civilization]]
*[[Hooroglyphs]]
 
Simply put, these are all ancient civilizations that we don't encounter in-game, since. Well. They're long-gone ancient civilizations that are only ever mentioned alongside occasional things that originate from them, most notably the statue [[Hoohooros]], but also [[Hooroglyphs]] and [[Beanstone]]s. While we can understand keeping Hoohooros and Beanstones split--the former is a full boss encounter, the latter is a key item involved in a sidequest--we're less sure about Hooroglyphs in particular. Merges for the civilizations have been called for since around late 2023, and we think the Hooroglyphs should be merged as their split mostly comes from the decision to make a page for them back in ''March 2007'', actually predating the Hoohoo civilization article. We've provided an option for keeping Hooroglyphs split, though we imagine it'd be better to merge this with the Hoohoo civilization information.
 
'''Proposer''': {{User|Camwoodstock}}<br>
'''Deadline''': February 13, 2025, 23:59 GMT
 
====Merge all (merge Hoohoo/Soybean Civilizations to List, merge Hooroglyphs to the Hoohoo Civilization section)====
#{{User|Camwoodstock}} Per ourselves; these civilizations don't have as much plot relevance nor lore behind them as something like, say, [[Squirpina XIV]] or the [[Flora Kingdom royalty]], at most serving as the origin for [[Hoohooros]].
 
====Merge civilizations, leave Hooroglyphs alone====
#{{User|LinkTheLefty}} The glyphs are actually seen, though.
#{{User|Jdtendo}} Per LinkTheLefty.
#{{User|Nintendo101}} Per LinkTheLefty.
#{{User|Camwoodstock}} Secondary option; admittedly, we're not quite sure how strong "you can ''see'' the glyphs in-game" is as a reason, but we would much rather the civilizations get merged than nothing at all.
#{{User|Power Flotzo}} Per all.
 
====Merge Hooroglyphs to Hoohoo civilization, leave civilizations alone====
 
====Merge none (do nothing)====
 
====Comments (Indus River Valley civilization joke here)====
 
===Include italics for category page titles for media that normally uses it===
Shouldn't category pages for media that uses italics (such as games, shows, movies, etc.) use italics for their category pages? I did start adding it to some pages already, but I thought it was worth proposing about it, possibly to make it policy. I feel like italics should be used though, as it is used everywhere else. For example, the page titled [[:Category:Donkey Kong 64]] should be [[:Category:Donkey Kong 64|Category:''Donkey Kong 64'']].
 
'''Proposer''': {{User|Kaptain Skurvy}}<br>'''Deadline''': February 20, 2025, 23:59 GMT
 
====Support====
#{{User|Kaptain Skurvy}} Per proposal.
#{{User|Camwoodstock}} Wait, this isn't already policy??? We think this lack of parity speaks a lot to how neglected categories can be in some regards. While yes, the category description isn't really meant to be the main point, we don't think ''slightly slanted text'' is distracting from the actual list of articles in the category, and just because categories are more utility than text doesn't excuse the text that ''is'' there looking below the standard of a usual article for being "lesser".
#{{User|Super Mario RPG}} Nothing wrong with having more consistency around the wiki.
#{{User|GuntherBayBeee}} Per all.
#{{User|Salmancer}} It is easier to figure out what the standards are from context alone when the standards are applied in every instance.
 
====Oppose====
#{{User|Nintendo101}} Categories are supposed to provide simple, direct, and utilitarian functions, not something to be read or presented to readers. I don't think italicizing them is necessary and would detract from their simplicity.
#{{User|Sparks}} Per Nintendo101. It doesn't feel necessary.
#{{User|OmegaRuby}} What is this supposed to change, exactly? Yes, it's in line with how pages about games are to have the subject italicized, but the change feels unneeded and especially arduous to implement for pretty much no reason. Per Nintendo101.
#{{User|SolemnStormcloud}} Per all.
#{{User|Rykitu}} Per Nintendo101
 
====Comments====
@Nintendo101: In that case, why do we italicise game titles in category descriptions? (Genuine question, I'm undecided on this proposal.) {{User:Hewer/sig}} 08:58, February 7, 2025 (EST)
:Because that is a proper sentence. It is not the tool itself. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 20:15, February 7, 2025 (EST)
::We mean... Wiki policy is to italicize game titles on their articles' names using <nowiki>{{Italic title}}</nowiki>, too, and those aren't proper sentences. They're article names. {{User:Camwoodstock/sig}} 19:00, February 8, 2025 (EST)
:::That's not the same situation in my eyes because the articles are what the site is for. That is what we are writing and presenting to the public. Of course we would italicize those. The categories are a tool, chiefly for site editors, not readers. We do not really gain anything from italicizing their titles. If anything, I worry this would lead to a lot of work to implement, either burdening site editors, porplemontage, or both. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 16:05, February 9, 2025 (EST)
::::So category names are just tools not meant for readers, but category descriptions aren't? {{User:Hewer/sig}} 18:08, February 9, 2025 (EST)
:::::The descriptions are just sentences, and I feel inclined to render those they way we would a sentence anywhere else on the site, be it on articles or in the description for image files. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 19:49, February 9, 2025 (EST)
::::We disagree with the notion categories are more for editors and not readers; while yes, all of the categories on the front page are maintenance categories from the to-do list, the sheer quantity of proposals for categories wouldn't make sense if they were moreso for editors, rather than your average reader; moves such as the reforms for the Look-alikes categories or the Thieves category wouldn't make sense if these weren't meant to be public-facing. And of course, there are the various categories that exist for users, but do ''not'' serve a utility purpose, such as the [[:Category:User es|various "users that know a given language" categories]].<br>As for difficulty implementing, considering the recent success stories with images without descriptions and categories without descriptions having gone from 4000+ and ≈100, to 0 and 0 respectively, we have it in good faith that this wouldn't be ''that'' hard to implement. Monotonous? Yes. But difficult? It's nothing a bit of caffeine and music can't solve. {{User:Camwoodstock/sig}} 18:22, February 9, 2025 (EST)
:::::Not only for editors, but chiefly for them. I don't exclude the idea of more curious readers utilizing them, but I suspect they are exceptions. I maintain that their ease of implementation is more important to the site than the formatting inconsistency. Like, are we to be expected to format category ourselves as "<nowiki>[[Category:Super Mario World screenshots|Category:''Super Mario World'' screenshots]]</nowiki>" instead of just "<nowiki>[[Category:Super Mario World screenshots]]</nowiki>" going forward? Would we do this for the articles that are in dozens of categories? Why? I would not want to do that, and I don't find the inconsistency a good enough reason to roll something like that out, and only brings downsides. It makes the tool where one types "<nowiki>[[Category:</nowiki>" almost entirely moot because we would still need to write out the whole name just to format it this way. Others are welcomed to think differently, but I personally think the way we format these names now in categories is perfectly fine. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 19:49, February 9, 2025 (EST)
even if this proposal doesn't pass, i think we should use [[Template:Italic title]] in the category pages. {{User:EvieMaybe/sig}} 10:16, February 12, 2025 (EST)
:I thought that was the whole proposal. {{User:Hewer/sig}} 03:32, February 13, 2025 (EST)
 
===Split the image quality category===
'''Issue 1:''' [[:Category:Images to be reuploaded with higher quality]] is a very big category, with nearly 4,000 images in it right now. Even if it's something you can help with, it's very difficult to actually find anything in here. '''Issue 2:''' All other things being equal, some types of images require specific methods or skills to get that all users may not have or be comfortable with. To aid in the overall usability of this category and make it easier for skilled users to find things they can help with, I'm proposing the following two subcategories:
*'''Screenshots to be uploaded with higher quality''' - Most Nintendo consoles don't have the ability to take native screenshots. That's all I'll say about that.
*'''Assets to be uploaded with higher quality''' - Sites like The Spriters Resource are helpful, but they don't have everything. Getting higher quality images requires being able to extract them from the game files and/or the ability to manipulate them afterwards. This will also include images that are currently screenshots meant to demonstrate an asset, such as [[:File:DKCTF Donkey Icon.png]].
Additionally, [[Template:Image-quality]] will be modified with an extra parameter to mark the image as a screenshot or asset and categorize them appropriately. Considering we already have the rewrite and stub categories organized for better navigation, I don't see this as an issue.
 
'''Proposer''': {{User|Waluigi Time}}<br>
'''Deadline''': February 20, 2025, 23:59 GMT
 
====Split both====
#{{User|Waluigi Time}} Category:Votes to be reuploaded with a better reason
#{{User|Technetium}} Per proposal.
#{{User|Camwoodstock}} We're a little surprised a split like this hasn't happened sooner, honestly; if for no other reason than it would be nice to have it organized. Per proposal.
#{{User|ThePowerPlayer}} Per proposal.
#{{User|Nintendo101}} Per proposal.
#{{User|LadySophie17}} Per all, which is mostly "per proposal"s anyway
#{{User|EvieMaybe}} makes perfect sense


The Koopaling article names on this wiki do not reflect this state of affairs: currently, they use the naming scheme established in old manuals, which is stylised by way of the word "Koopa" attached as a surname or nobiliary title of sorts. Said naming scheme has seen sparse use in more recent years, being specifically reserved to ancillary material such as the ''New Super Mario Bros. Wii'' Prima Guide, this [https://youtu.be/De9Z11mLo_A?t=105 video], and most likely more--I invite knowledgeable editors to expand this list for future reference. As dictated by [[MarioWiki:Naming#Acceptable sources for naming|the source priority policy]], this material should not override what the games themselves put forward. In addition, the more concise versions of these characters' names would better serve readers and contributors alike.
====Only split screenshots====


Given my statement above, the object of this proposal is to simply change Koopaling articles, and most pages directly related to the individual characters, to display only their first name. The page [[List of DIC cartoon episodes featuring Hip Koopa]] is excluded from the proposal's scope, as its title reflects the character's name used in the SMB3 cartoon. The following is a list of affected pages, with target titles in brackets:
====Only split assets====
{|
|-
|
*[[Larry Koopa]] ("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]] ("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")
|}


I would also like us to hash out how to phrase the opening paragraphs in their character articles; namely, whether to list the short name or the full name first. For this, I'm splitting the support option into two possible directions:
====Leave image quality alone====
#"<u>'''Larry''', referred to in full as '''Larry Koopa'''</u> and known as '''Cheatsy Koopa''' in the cartoons, [...]"
#"<u>'''Larry Koopa''', or simply '''Larry'''</u>, known as '''Cheatsy Koopa''' in the cartoons, [...]"


I suppose some editors may prefer the second direction, given that it's common practice in academic and academically-modeled resources to start out an article's text with the subject's full name, and not necessarily the best known version of the name.
====Comments on image quality proposal====
Silly question; will images that are of neither screenshots nor assets that have the image-quality tag, like scans, character art/renders, or merchandise, just remain as-is? There are already a few examples of those that are all presently tagged with image-quality, like so:
<gallery>
File:Mk64mario.png|Scan of 3D render, colors are washed out.
File:BIS Fawflopper Prima.png|Muddy scan of 2D illustration, and background cropped.
File:Mariocrouch2Dshade.png|Photoshop upscaled 2D promo art.
File:BulletBillTSHIRT.jpg|Too small image of merchandise.
</gallery>{{User:Camwoodstock/sig}} 15:30, February 6, 2025 (EST)
:Yes, anything that doesn't fall into either of the two subcategories will stay in the main one for now. I suppose we can look into splitting it further down the road, but I singled these two out because of the higher barrier to entry and also that they seem to be the bulk of the category's contents right now. --{{User:Waluigi Time/sig}} 15:37, February 6, 2025 (EST)
::I think this category should also be split by the media that it appears in (e.g: {{fake link|Category:Game screenshots to be reuploaded with higher quality}}. Something similar should also be done for the [[:Category:Articles with unsourced foreign names|Articles with unsourced foreign names category]]. [[User:Apikachu68|Apikachu68]] ([[User talk:Apikachu68|talk]]) 19:50, February 6, 2025 (EST)
:::Almost all of the screenshots in the category right now are from games so I don't think it needs to be narrowed down further just yet. --{{User:Waluigi Time/sig}} 20:09, February 6, 2025 (EST)


'''Proposer''': {{User|Koopa con Carne}}<br>
===Change "(game)" identifier to "(arcade)" on the articles of ''[[Donkey Kong (game)|Donkey Kong]]'', ''[[Donkey Kong Jr. (game)|Donkey Kong Jr.]]'' and ''[[Mario Bros. (game)|Mario Bros.]]''===
'''Deadline''': <s>September 25, 2022, 23:59 GMT</s> Extended to October 2, 2022, 23:59 GMT
I wouldn't consider "game" to be the best identifier for the arcade games ''Donkey Kong'', ''Donkey Kong Jr.'' and ''Mario Bros''. There's already a [[Donkey Kong (Game & Watch)|Game]] [[Donkey Kong Jr. (Game & Watch)|and]] [[Mario Bros. (Game & Watch)|Watch]] game that shares its title with each of the arcade games, but "''Donkey Kong''" is the name of various other games too! There's [[Donkey Kong (tabletop arcade game)|the tabletop game]], [[Donkey Kong (Game Boy)|the Game Boy game]], [[Donkey Kong (Nelsonic Game Watch)|the Nelsonic Game Watch game]] and [[Donkey Kong (slot machine)|the slot machine]]. I know the slot machine is technically an arcade game, but it's not a standard cabinet like the 1981 arcade game. "Game" is a broad identifier, especially for ''Donkey Kong''. Shouldn't a "game" identifier only be used if there's no other game with the same name? That's why we use consoles for identifiers instead, such as [[Mario & Sonic at the Olympic Games (Wii)|''Mario & Sonic at the Olympic Games'' (Wii)]] and [[Mario & Sonic at the Olympic Games (Nintendo DS)|''Mario & Sonic at the Olympic Games'' (Nintendo DS)]].


====Support (option 1)====
'''Proposer''': {{User|Kaptain Skurvy}}<br>'''Deadline''': February 22, 2025, 23:59 GMT
#{{User|Koopa con Carne}} Preferred option. Can't wait to make it easier to type out the names of these roster-padding sons of bitches.
#{{User|Spectrogram}} Per con Carne's proposal :)
#{{User|Tails777}} Honestly, either wording works for me, but could be best to roll with their first names only to match article titles.
#{{user|WildWario}} Per proposal.
#{{User|Hewer}} After some thought, per all and per the support voters [[Talk:Koopalings#Move_all_Koopaling_articles_to_just_their_first_names|here]].
#{{user|Doc von Schmeltwick}} - Full_name parameter exists for a reason and the full names are rarely used, unlike say [[Kammy Koopa]], who is referred to pretty much only as such.
#{{User|Platform}} - Per all.
#{{User|LinkTheLefty}} Strongly per "most commonly used English name" which has been the basis every single time this comes up (I would say "List of DIC cartoon episodes featuring Hip" too since I distinctly remember lines using his first name, but I'm not about to bingewatch to confirm if full name or first only is more common there).


====Support (option 2)====
====Support====
#{{User|Hewer}} Second choice.
#{{User|Kaptain Skurvy}} Per proposal.
#{{User|ThePowerPlayer}} I'm surprised no one has voted for the second support option; changing mentions of the Koopalings to just their first names would improve reader and editor convenience, while using their full names as the very first words of each of their articles would help make their full name immediately clear (and help clarify that the article {{fake link|Roy}} refers to Roy Koopa, not [[Roy (Fire Emblem)|Roy from ''Fire Emblem'']] or [[Roy (Mario Tennis: Power Tour)|Roy from ''Mario Tennis: Power Tour'']]). This option makes sense to me because their full names are still commonly used, unlike [[Mario|Mario Mario]], [[Princess Peach|Princess Peach Toadstool]], and [[Yoshi|T. Yoshisaur Munchakoopas]]. Additionally, it sets both an academic, professional standard and the standard already set by the edge cases of characters with intentionally long full names, like [[Squirps]] and [[The Old Psychic Lady]].
#{{User|LinkTheLefty}} My preference would be an approach closer to this (also considering that the given full names are subject to modification, especially in old western media appearances).
#{{user|Doc von Schmeltwick}} - Per
#{{user|Blinker}} Per all. (Professor E. Gadd on a similar boat?)


====Oppose====
====Oppose====
#{{User|Waluigi Time}} Per Mister Wu in the comments and the [[Talk:Koopalings#Move_all_Koopaling_articles_to_just_their_first_names|previous proposal over this]]. The names are still sometimes used in-game with recent examples, and this largely seems to stem from the extended names just not being used in Japan. (You could bring in the "it's closer to Japanese" argument, but I don't really like the idea of using that to decide which English names should be used.)
#{{User|Nintendo101}} Those articles also cover the game's release on Famicom, NES, Atari, etc., so "arcade" would not be a holistically accurate identifier.
#{{User|Killer Moth}} Per Waluigi Time. These names are still used quite frequently and don't need to be changed.
#{{User|Camwoodstock}} Per Nintendo101; "arcade" is kind of a misnomer when the non-arcade ports are covered on them.
#{{User|Swallow}} I would agree with not referring to them by the full names for games that don't use them at all, otherwise per all.
#{{User|ThePowerPlayer}} Per Nintendo101.
#{{User|SmokedChili}} If the full names had been completely out of use after the first appearance or so like [[Boo Diddly]], I would have supported this. And then there's few Koopa characters like [[Kylie Koopa]] whose first name was used in her follow-up appearance. I don't know the reason for Smash Bros. fighters having articles under their full names if they have any, but when I see an example like [[Wolf]] and [[Wolf O'Donnell]], using full names looks valid enough and better over identifiers (like this).
#{{User|PaperSplash}} Per ThePowerPlayer's comment.
#{{User|Wikiboy10}} Per Waluigi Time, the names are still used on occasion enough compared to [[Princess Peach|Princess Peach Toadstool]].
#{{User|Rykitu}} Per all
#{{User|RealStuffMister}} Per waluigi time
#{{User|MrConcreteDonkey}} - Really struggle to see any advantage to this. If the full names are still in use and there's no official confirmation they've been dropped, what's the point? How does typing "Koopa" on the end of the name, on the rare occasions you need to, waste any time at all? Also both example sentences provided for the support option are far more awkwardly worded than what's currently there.
#{{User|Bazooka Mario}} Until someone can elaborate on why policy discourages linking to redirects, I don't see the need to rename well-established names to simpler names that I feel were simplified for game-context reasons that aren't necessarily applicable to wikis.


====Comments====
====Comments====
I'd like to remind yet again that in ''Super Smash Bros. Ultimate'' [https://youtu.be/9HEisHGO1bk the full names are all acknowledged] - they also were acknowledged in the Wii U version of ''Mario & Sonic at the Rio 2016 Olympic Games'' that featured the ''Theme of Larry Koopa''.<s> Also, please, proposal votes based on personal hatred do no good to the wiki, especially since the only multi slot roster "padding" the Koopalings did since ''Mario Kart 8'' and its Deluxe version was in the now defunct ''Dr. Mario World'' and in ''Mario Kart Tour'' (where it's pretty bold to compare it to the actual padding of the variants). They share the slot with Bowser Jr. in the ''Smash Bros.'' games and they are guests in the ''Mario & Sonic'' games, meaning that they only occupy one slot.</s>--[[User:Mister Wu|Mister Wu]] ([[User talk:Mister Wu|talk]]) 15:31, September 18, 2022 (EDT)
Maybe "arcade game" would be a decent compromise? [[User:PaperSplash|PaperSplash]] ([[User talk:PaperSplash|talk]]) 18:02, February 8, 2025 (EST)
:Considering the tone of my statement of disdain and the fact that I added it at the tail end of a series of arguments made in good faith, I would say that it is very clearly meant to be taken as a joke. I have no strong attachments towards any video game characters, so your accusation that I'm using "hatred" as a thrust to my argument is not only insulting, but blown out of proportion. {{User:Koopa con Carne/Sig}} 19:10, September 18, 2022 (EDT)
::Fine, I take that part back (although just so you know, fan votes have been a thing in the past, so be wary that some users ''did'' vote out of attachment to characters, meaning that jokes like this one can be misunderstood). In any case, sorry for the misunderstanding.--[[User:Mister Wu|Mister Wu]] ([[User talk:Mister Wu|talk]]) 09:14, September 19, 2022 (EDT)
I'd actually like to take this a bit further by questioning Peach and Daisy; as of right now their article names are "Princess Peach"/"Princess Daisy", but much like how very few, if any, modern games ever refer to the Koopalings by their full names, very few, if any games references Peach and Daisy by their titles in game. Mario Kart, Mario Party, Mario Golf, Smash Bros, they all just refer to them as Peach and Daisy. And if the fact that it's a title has anything to do with it, why isn't Bowser's article named "King Bowser"? I'd wager we could probably move their articles to just Peach and Daisy for the same reasons. {{User:Tails777/sig}}
:''Origami King'' actually does use "Princess Peach" quite a bit: for example, there's Olivia saying "My brother and Princess Peach must both be in there..." and Bowser says "Anyway, where's Princess Peach?", both in the endgame. {{User:Scrooge200/sig}} 19:37, September 18, 2022 (EDT)
:The "Princess" title is still widely in use, such as in TOK as Scrooge said and on the Play Nintendo site. It would seem that only roster-heavy spin-offs refer to them with only their personal names. {{User:Koopa con Carne/Sig}} 19:42, September 18, 2022 (EDT)
::That example does help me see the difference in this situation, mainly cause I'm comparing a title to a full name. I guess it makes sense that Peach and Daisy use their princess title cause it's a title. And it makes sense that the Koopalings don't go by their full names often cause that would literally be like going up to your best friend and using their full name just to refer to them. So from a realistic standpoint, it makes sense that games like ''Paper Jam'' or ''Color Splash'' don't just have everyone referring to them by their full names in dialogue like they would when referring to Peach as "Princess Peach" (I guess it's also worth mentioning that in ''Color Splash'', Peach's introduction does use her full title while the Koopalings don't use their full names.) That being said, using spin-offs like ''Mario Kart'' might not be the best examples, since most characters go by their standard names anyway. {{User:Tails777/sig}}


@Opposition: The amount of media that refers to the Koopalings using only their first name (including, as mentioned in the proposal, almost every single game they appeared in during the last decade) far surpasses the number of instances where their full name is used. Participants to the previous proposal brought up isolated, relatively minor instances of the Koopalings' full names being used, particularly in merchandise and print media, and treated them as top-priority sources despite going counter to what the naming policy says. In the spirit of hopefully convincing people that it's misguided to do so, I raise another piece of merch, the [[Super Mario Trading Card Collection]], released in April 2022 (so pretty recent), which respects the naming model used in games. Shouldn't it similarly be taken into consideration, and be measured against a random Larry Koopa toy and a Monopoly set? Because it's clear that merchandise releases are not consistent among themselves in the least, so why not turn to what the games already very clearly establish? {{User:Koopa con Carne/Sig}} 19:10, September 18, 2022 (EDT)
What about [[Dr. Mario (game)|''Dr. Mario'']]? That game also has a [[Dr. Mario (Gamewatch Boy)|separate release also called ''Dr. Mario'']].--[[User:PopitTart|PopitTart]] ([[User talk:PopitTart|talk]]) 18:24, February 8, 2025 (EST)
:The thing is, they're not contradictory (or even different, technically) names, and it's not even really an inconsistency. Sometimes they use the full name, other times they use a shortened version. I don't see any harm in using the full one if it's still in use. --{{User:Waluigi Time/sig}} 19:51, September 18, 2022 (EDT)
::The reason why the games ''Donkey Kong'' and ''Dr. Mario'' should keep their identifier of "(game)" is because those are by far the most popular and commonly thought-of games under their respective titles; the other articles (aside from ''Donkey Kong'' on the Game Boy) are on much more obscure devices while being clearly separate from the original game. To put it another way, "''Dr. Mario'' (game)" is what people are looking for when they think about "the game featuring Dr. Mario"; meanwhile, you'd be forgiven for not knowing that the Gamewatch Boy game even exists at all. {{User:ThePowerPlayer/sig}} 22:15, February 8, 2025 (EST)


@Opposition: I'm challenging someone to explain why "the names are occasionally used" (in things like Smash Bros. and merchandise no less, which as I've demonstrated above aren't even consistent with themselves) is being so strongly bandied around as an argument against designating the ''names that are put front and center in most appearances of these characters'' to their wiki articles.{{footnote|main|a}} So far, zero proper rationale has been given for the former direction in either of the three proposals that have concerned this matter, other than a couple of arguments that can be best defined as mental gymnastics. Nobody is arguing that we should get rid of the names altogether, just that using them in such a representative fashion isn't the proper way to go--and I've already proposed two methods to handle their full names in their lead, because, much like LinkTheLefty has [[Talk:Koopalings#Move all Koopaling articles to just their first names|previously]] [[Talk:Koopalings#Stop consistently referring to the Koopalings with their full names|stated]], these names are significant enough to deserve a mention as such. That doesn't mean [[Squirps]] is a contender for a move to "Prince Squirp Korogaline Squirpina" though. {{User:Koopa con Carne/Sig}} 10:30, September 21, 2022 (EDT)<br>
what about Donkey Kong (1981)? {{User:EvieMaybe/sig}} 18:39, February 9, 2025 (EST)
{{footnote|note|a|Per [[MarioWiki:Naming#Naming an article|MarioWiki:Naming]]: "''the name of an article should correspond to the '''most commonly used English name''' of the subject''".}}
:That would work for ''Donkey Kong'', but the original ''Mario Bros.'' and the arcade game of the same title were both released in 1983. {{User:JanMisali/sig}} 12:49, February 12, 2025 (EST)
:I've already explained at least for my part that I think it's fine keeping the full names since the most commonly used ones are just simplifications of those names, and the full ones are still in use. If the full names had been dropped entirely for an extensive period of time, yeah I could see that, but they're clearly still around. I don't think that's mental gymnastics myself, but if you feel that the arguments presented so far aren't "proper rationale" I'm not sure there's much more to say. --{{User:Waluigi Time/sig}} 12:16, September 21, 2022 (EDT)
::"since the most commonly used ones are just simplifications of those names, and the full ones are still in use"<br>This straight up argues doing the opposite of what the policy I cited above says to do. {{User:Koopa con Carne/Sig}} 17:30, September 21, 2022 (EDT)
"How does typing "Koopa" on the end of the name, on the rare occasions you need to, waste any time at all?"<br>
Except they're not "rare" as you claim. I found myself piping links to their articles far more often than not, because--and I re-reiterate--their one-word names have seen infinitely more use in various media throughout the years. I didn't put a lot of focus on this point in the proposal, but having to only type in one word whenever I
link would definitely save some effort.<br>
"Also both example sentences provided for the support option are far more awkwardly worded than what's currently there."<br>
If you have anything better, provided a scenario in which this proposal passes, I'm open to it. {{User:Koopa con Carne/Sig}} 07:46, September 23, 2022 (EDT)
:Well... to address the second point, you don't need to change it at all? To address the first, this is all basically just opinion so there's no definitive answer to this, but it's just 5 extra letters. You would need to type it, at a stretch, once per article if it's not already linked - or you don't even need to type them at all, as their first names redirect to their articles anyway. Unless there's suddenly been a massive flood of new Koopaling media/appearances I'm not sure how this could cause any real issue, and the solution the proposal suggests is effectively already in place. If it's causing that much of a problem, you could just leave it for someone else to edit. {{User:MrConcreteDonkey/sig}} 10:54, September 23, 2022 (EDT)
::Those 5 letters, "Koopa", need to be typed out in addition to re-typing the Koopaling's unique name for the sake of piping the link to their article (the wording has to be apposite to what the game in question uses anyway--see [[MarioWiki:Naming#Name changes]]--and that's most games really). Piped linking has to be done because [[MarioWiki:Redirects#Linking to redirects|current policy discourages linking to redirect pages]]. "Unless there's suddenly been a massive flood of new Koopaling media/appearances" -- ''there '''has'''''. Assuredly, for almost a decade now. And there have been very, very few instances, verging on non-significant, in this past decade where their full names were used. <small>(This has to be about the fifth time I'm stating this.)</small> I encourage you to look at and compare the examples everyone brought up so far in this discussion as well as in [[Talk:Koopalings#Move all Koopaling articles to just their first names|previous]] relevant talks. {{User:Koopa con Carne/Sig}} 11:16, September 23, 2022 (EDT)
:::It might be the fifth time you've said that, but it's an assumption, not a fact. It's not even true if you count the Smash Ultimate and Mario & Sonic examples Mister Wu mentioned, or the merch where it's used. Why does it matter anyway, why does that justify changing the name? There's no sign the full names have been dropped completely, so it's nothing to do with the naming policy, and the fact that they were used in the past - in games that are often re-released - means they're relevant. Also, piping the link is... really not a huge task. If anything it's a very minor inconvenience, which would take at most a minute to resolve if you had to do it for all seven - and something you're unlikely to run into more than once every few months, at a stretch. It's also something you need to do everywhere on the website, why is it particularly bad in this case? Just feels like removing relevant info for a pointless reason, if I'm honest. {{User:MrConcreteDonkey/sig}} 11:30, September 24, 2022 (EDT)
::::When facts stated ad nauseam are being brushed off as "assumptions", and that they "don't justify changing the names", it's when I officially give up arguing. If a handful of (obscure) instances in a total of two/three titles out of 10 back to back + some 2017 Monopoly game are enough to overpower the rest, then fine: by all means go against policy if you so wish. This same line of thinking can be used to rename [[Squirps]] to the character's full name, as I've mentioned above.<br>"If anything it's a very minor inconvenience, which would take at most a minute to resolve if you had to do it for all seven"<br>''Most'' links concerning Koopalings have to be piped; it's as inconvenient as typing the same word twice everytime it comes up. I've been active enough around these parts for the past several years to know what I'm talking about. {{User:Koopa con Carne/Sig}} 12:10, September 24, 2022 (EDT)
::::@MrConcreteDonkey: No one is claiming that the full names have been completely dropped, nor is anyone calling for their removal from the wiki. We're just saying that most of the more recent games use the shortened names without mentioning the full ones, so we should retitle the articles while still making the full names immediately obvious in the lead and infobox. I don't see how this can be classified as 'removing relevant info for a pointless reason' when no info is being removed here. {{User:Hewer/sig}} 14:49, September 24, 2022 (EDT)


==Changes==
===Standardize the use of "English", "English (United States)" and/or "English (United Kingdom)" as languages in game infoboxes===
''None at the moment.''
So far, the use of "English (United States)" and "English (United Kingdom)" as language identifiers in game infoboxes on this wiki has been rather inconsistent and arbitrary, to say the least. While Nintendo is typically known for providing distinct English localizations for the United States (and other English-speaking territories in the Americas) and the United Kingdom (and other territories where Commonwealth English is standard, apart from Canada), the actual differences between them, if any, have varied over time.
 
Historically, many Nintendo games have featured minor English text differences between their releases in the Americas and Europe/Oceania; however, these were typically not wholly separate localizations to account for the differences between American and British (or Commonwealth) English – they tended to follow American English conventions for the most part regardless. Rather, they were simple amendments made by Nintendo of Europe to Nintendo of America's existing English scripts, usually either to rectify perceived shortcomings or to modify certain terminology based on internal preferences. These versions were typically stored separately on region-specific cartridges or discs, with occasional differences in how they were labeled in internal data.
 
Later, during the DS, Wii, 3DS and Wii U eras, more distinct localizations specifically for the United States and United Kingdom that also accounted for regional language differences became more commonplace. However, all of the aforementioned practices have largely faded with the advent of the region-free Nintendo Switch, where games now typically release simultaneously worldwide on identical cartridges. As a result, English scripts are now more often than not also identical across regions (or at most contain only very minor differences, such as the date format used; in many cases, the date format is the ''only'' difference), though they are still almost always stored and labeled separately in internal data, typically alongside each other.
 
This proposal aims to determine how we should handle cases of identical or nearly identical (American) English scripts between regions when identifying languages in game infoboxes. Should we list them both as "English (United States)", simply as "English" or adhere to how they are distinguished in internal data, even when actual differences are minimal?
 
'''Proposer''': {{User|PaperSplash}}<br>
'''Deadline''': February 23, 2025, 23:59 GMT
 
====Option 1: List largely identical American English localizations only as "English (United States)"====
#{{User|PaperSplash}} My third choice. I mean, when it really is just American English, I can see the argument.
 
====Option 2: List largely identical American English localizations as simply "English"====
#{{User|PaperSplash}} My first choice. I think it's the best compromise that makes the most sense, all things considered.
#{{User|Hewer}} I feel like this way is the most straightforward and accurate.
#{{User|CarlosYoshiBoi}} I mean, if it’s just the same thing and no changes (assuming it doesn’t include dates for save files), then I guess this one makes the most sense.
#{{User|Camwoodstock}} Primary option. It's the simplest, it seems reasonable enough, and is applicable across the board; while it isn't exactly in-line with how Nintendo is handling things as of the Switch era, it's reasonable ''enough'' and can easily account for pre-Switch cases very well.
#{{User|Jdtendo}} Per all. Especially if that means that we will stop using "English (United States)" for games that use a variety of English that is not specifically American and weren't even released in America such as ''[[Super Mario Bros.: The Lost Levels|SMBTLL]]'' or ''[[Mario & Wario]]''.
 
====Option 3: List both "English (United States)" and "English (United Kingdom)" if distinguished in internal data, otherwise simply list "English"====
#{{User|PaperSplash}} My second choice. When internal data classifies them that way, it ''could'' make sense to follow suit...
#{{User|Camwoodstock}} Secondary choice, as this seems to be Nintendo's official methodology as of the Switch; however, this ''exact'' rationale doesn't account for situations like, say, [[Mario Party 8]] and its infamous recall in the UK, which predates Nintendo's official distinguishing of NA English and UK English from the Switch era, leaving us at a bit of a loss for how to handle it exactly.
#{{User|CarlosYoshiBoi}} This option could also work if date formatting is different despite the game itself using the same script for the US and UK/Australia, like Mario & Luigi: Brothership.
 
====Option 4: Do nothing====
#{{User|CarlosYoshiBoi}} I’m actually surprised no one put anything in this option kind of like the title mentions “Do nothing.”
 
====Comments====
For better accuracy, "British English" should probably be "Commonwealth English." [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 22:13, February 8, 2025 (EST)
 
:Noted. Though I decided to focus mainly on the terminology used in game infoboxes, as I realized this wiki's use of the term "British English" is effectively its own can of worms... [[User:PaperSplash|PaperSplash]] ([[User talk:PaperSplash|talk]]) 15:35, February 9, 2025 (EST)
 
I'm a bit confused what this proposal is trying to change. Is it just about terminology used in game infoboxes? {{User:Hewer/sig}} 11:31, February 9, 2025 (EST)
 
:In hindsight, I realized this proposal was trying to change too many things at once, so I decided to tidy things up and focus on just the game infobox terminology for now. [[User:PaperSplash|PaperSplash]] ([[User talk:PaperSplash|talk]]) 15:35, February 9, 2025 (EST)
 
Realistically even though Canadian English does use British/Commonwealth spelling most of the time, they just get US English spelling in games as Nintendo groups Canada with North America and their English is pretty similar to English in the US, so Nintendo products in Canada are just the same as in the US.
 
In this case why don’t we also just group American English and Canadian English into one and call it "North American English" even if it’s moreso mainly American English? [[User:CarlosYoshiBoi|CarlosYoshiBoi]] ([[User talk:CarlosYoshiBoi|talk]]) 10:45, February 11, 2025 (PST)
 
:I'm not quite sure exactly what point you're trying to make here, but per [[Template:Languages/doc|the documentation for the "languages" template]], the reason they're labeled the way they currently are in game infoboxes is because they're the primary markets American English and British/Commonwealth English localizations are made for. And for what it's worth, whenever Nintendo specifically labels "North American English" as a selectable language whether in-game or in internal data, they usually refer to the United States or US specifically, not North America/NA as a whole. [[User:PaperSplash|PaperSplash]] ([[User talk:PaperSplash|talk]]) 16:27, February 11, 2025 (EST)
 
::I think I’m going with the fact that the English (United States) language for Nintendo is also intended for Canada (and it’s also applied onto the "Japan" and "Hong Kong/Taiwan/South Korea" regions on the Switch) despite just using American English. Kinda like with European French where although it’s just moreso referring to Standard French/French from France, it’s intended for all French-speaking regions in Europe (France, Belgium and Switzerland). [[User:CarlosYoshiBoi|CarlosYoshiBoi]] ([[User talk:CarlosYoshiBoi|talk]]) 14:58, February 11, 2025 (PST)
 
If Nintendo is also still adding English (United Kingdom) for their games despite there being almost no differences from the North American English versions aside from date or other words if needed, why do they keep American spelling? Wouldn’t it make more sense for British English spelling to be used even if it’s one of the only differences between English (United States) and English (United Kingdom)? [[User:CarlosYoshiBoi|CarlosYoshiBoi]] ([[User talk:CarlosYoshiBoi|talk]]) 22:00, February 12, 2025 (PST)
 
:Less work for something ultimately unimportant, I guess? It's not like American spelling is unintelligible to non-Americans. Anyway, what does this have to do with the proposal? {{User:Hewer/sig}} 03:39, February 13, 2025 (EST)
 
::Just came up to me somehow on the topic of American English and British English. Not as big of a problem anyways but just hit me. [[User:CarlosYoshiBoi|CarlosYoshiBoi]] ([[User talk:CarlosYoshiBoi|talk]]) 7:37, February 12, 2025 (PST)
 
===Make Dark Mode available to everyone===
Dark Mode is available to users with an account under preferences but it should be a toggle-able option for all users, even if they're not an editor. Wikipedia allows everyone regardless of role to toggle Dark Mode, so I don't see why [[Super Mario Wiki|this wiki]] shouldn't follow suit.
 
'''Proposer''': {{User|Pizza Master}}<br>
'''Deadline''': February 27, 2025, 23:59 GMT
 
====Support====
#{{User|Pizza Master}} per.
#{{User|Nintendo101}} nice idea, <s>though I would prefer if Light Mode was called "Ground Mode" and Dark Mode was called "Underground Mode" for our site.</s>
#{{User|Camwoodstock}} Wait, theme changes are unavailable to users not logged in? Just, at all? It's not just dark mode, it's ''any'' theme, since it's all on Preferences. This feels like something that, if it's possible, it shouldn't even be a proposal, it should just be added outright without vote. This is a very obvious quality-of-life change for users that don't happen to be logged in.
#{{User|Mushroom Head}}Why do we still need to create an account just to not torture your eyes when we use this wiki at night? It literally has zero effect to the users who are always logged in anyways.
#{{User|Rykitu}} Per all
 
====Oppose====
 
====Comments====
My question is: is it possible to enable this feature for non-logged-in visitors? I'm asking this because Dark Mode is considered a "[[Special:Preferences#mw-prefsection-gadgets|Gadget]]", and not a regular MediaWiki feature. They work with JavaScript though, so I suppose it ''could'' work in some way (given we have [[MediaWiki:Common.js]] and all), but I would still ask {{user|Porplemontage}} if a toggleable, easily accessible Dark Mode for everyone (including non-users) is possible, if I were you. {{User:Arend/sig}} 17:33, February 13, 2025 (EST)
 
:I've asked [[User:Porplemontage|Porple]] on his talk page, so we'll see when he answers. [[User:Pizza Master|Pizza Master]] ([[User talk:Pizza Master|talk]]) 17:40, February 13, 2025 (EST)
 
::Porple's response on his talk page seems to imply that it might be possible. [[User:Pizza Master|Pizza Master]] ([[User talk:Pizza Master|talk]])


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

Latest revision as of 13:34, February 14, 2025

Image used as a banner for the Proposals page
Current time:
Friday, February 14th, 21:53 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 its own mini-proposal with a deadline and Support/Oppose subheadings. The rules above apply to each option as if it were a its own 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 "Oppose" wins for that option by default. A poll proposal closes after all of its options have been settled. 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])====

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)
Add film and television ratings to Template:Ratings, TheUndescribableGhost (ended October 1, 2024)
Use the classic and classic link templates when discussing classic courses in Mario Kart Tour, YoYo (ended October 2, 2024)
Clarify coverage of the Super Smash Bros. series, Doc von Schmeltwick (ended October 17, 2024)
Remove all subpage and redirect links from all navigational templates, JanMisali (ended October 31, 2024)
Prioritize MESEN/NEStopia palette for NES sprites and screenshots, Doc von Schmeltwick (ended November 3, 2024)
Allow English names from closed captions, Koopa con Carne (ended November 12, 2024)
^ NOTE: A number of names coming from closed captions are listed here.
Split off the Mario Kart Tour template(s), MightyMario (ended November 24, 2024)
Split major RPG appearances of recurring locations, EvieMaybe (ended December 16, 2024)
Organize "List of implied" articles, EvieMaybe (ended January 12, 2025)
Split Mario & Luigi badges and remaining accessories, Camwoodstock (ended February 1, 2025)
Merge Chef Torte and Apprentice (Torte), Camwoodstock (ended February 3, 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)
Expand and rename List of characters by game to List of characters by first appearance, Hewer (ended November 20, 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)
Split the Ink Bomb, Camwoodstock (ended January 12, 2025)
Create a catch-all Poltergust article, Blinker (ended January 21, 2025)
Merge the two Clawing for More articles, Salmancer (ended January 27, 2025)
Merge Dangan Mario to Invincible Mario, PrincessPeachFan (ended January 30, 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)
Merge MC Ballyhoo and Big Top, Dive Rocket Launcher (ended February 13, 2025)

Writing guidelines

None at the moment.

New features

Introduce a new type of proposal

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

While our wiki's proposal system is a pretty good way to democratize choices, it does have its limitations. A single-winner vote is simply not robust enough to support certain types of decisions, most notably with the ones that require settling various parts independently (such as this proposal, which had to decide on both the romanization and the identifier separately), or sorting several things at once (see this old proposal attempt for a maximal worst-case scenario). So what do we do?

My suggestion is to create a second type of proposal, tentatively named poll proposals.

  • Poll proposals can feature several options, much like regular proposals (which might also need their own name), but each option is its own binary vote.
  • Instead of commenting "per proposal" or "per all" or giving some insight, voters must indicate "for" or "against" on each option they vote on. Further comments are allowed, of course.
    • Abstaining from some options should be allowed too.
  • Each vote is subject to the same approval percentages as a regular old Support/Oppose proposal.
  • Early closures and term extensions get murkier when some options might meet the threshholds while others do not. This might warrant some further discussion, and I do not think I have the authority to decide how this should be settled. Up to staff, I guess?
  • Poll proposals must be clearly marked as such, to make it clear how one is supposed to vote.

This allows us to more efficiently make several decisions at once, instead of having to string several follow-up proposals together. For an example, I'm sure many of you have seen proposals that do two changes at once and have the options marked as "A, B, both, neither". This would contract those to simply "A, B".

I've written down a mockup poll proposal for those who need a more visual example. Of course, if this passes, staff is free to change aspects of the implementation as they see fit, particularly the specific word choices of "poll proposal", "for" and "against".

Proposer: EvieMaybe (talk)
Deadline: February 21, 2025, 23:59 GMT

Support

  1. EvieMaybe (talk) Per proposal.
  2. RetroNintendo2008 (talk) Mock-up looks pretty good! The more variety when it comes to how we make major decisions, the better.
  3. PopitTart (talk) For. Having templates as Camwoodstock suggests would also be good to make it easier to see at a glance how votes are distributed.
  4. Rykitu (talk) Neat idea, per all.
  5. Waluigi Time (talk) Per proposal, as long as the suggestion to have a better visual indicator for support/oppose votes is taken into account. I lean more towards Ahemtoday's suggestion since it'll be easier to keep count of them.
  6. ThePowerPlayer (talk) Per Waluigi Time.
  7. 1468z (talk) Per all.
  8. Camwoodstock (talk) Per Waluigi Time and Ahtemtoday's suggestion; as long as tallying is made easier than the original example, we see no reason to not add these.
  9. Killer Moth (talk) Per all.
  10. Nintendo101 (talk) Good idea for larger projects. Per proposal.
  11. Mushroom Head (talk)

Oppose

Comments on proposal proposal

Our only complaint is in the mockup; we feel like it could be made a lot more clear which votes are for/against in some way. Maybe a pair of {{For}} and {{Against}} templates? (In this context, we think making these templates is fine; you already need to know how to use {{User}} to vote, after all, and we're imagining these will be very, very simple to use.) Camwoodstock-sigicon.png~Camwoodstock (talk) 17:41, February 7, 2025 (EST)

That, but what purpose would "against" votes have compared to just not voting on that option? Mario It's me, Mario! (Talk / Stalk) 17:42, February 7, 2025 (EST)
Same as it would in a regular proposal, each option acts as an individual 2-option vote. If no one opposes an option (and it meets quorum requirements), then it passes. --PopitTart (talk) 17:56, February 7, 2025 (EST)
I feel like the easiest solution is just "for" and "against" subheaders under each option. Ahemtoday (talk) 18:04, February 7, 2025 (EST)
That would also work for us! Our only real concern is that this could result in level-5 subheaders on proposals on this page specifically, which... Don't look all that great. Even still, we just need something to disambiguate at a glance what is what, and this will do the job just well. Camwoodstock-sigicon.png~Camwoodstock (talk) 23:01, February 7, 2025 (EST)
@Camwoodstock you're absolutely right and that's a very good idea! — Super Leaf stamp from Super Mario 3D World + Bowser's Fury.eviemaybe (talk / contributions) 18:44, February 7, 2025 (EST)

I'm a little bit stuck on what kind of use cases this type of proposal would be for. I've had to split a proposal into three separate ones myself once, but even if this type of proposal existed at the time, I still feel like it would have made the most sense to do them separately. I suppose it would definitely help for the "split combinatorial explosion" example you gave, but I can't really envision what your other example would look like as a poll proposal. Ahemtoday (talk) 18:04, February 7, 2025 (EST)

well, the way i was thinking of is that it'd have one option for whether to use Waruiji or Waluigi, and another on which identifier to use. i admit it's not as clean bc there's more than two options for identifiers, but something like that could work for similar cases. i came up with this proposal idea while thinking about a proposal narrowing down if cultural/historical/mythological/folklore references count for List of references in the Super Mario franchise, and thinking that it'd be great if we could vote on each of them individually without having to make a proposal for each. — Super Leaf stamp from Super Mario 3D World + Bowser's Fury.eviemaybe (talk / contributions) 18:44, February 7, 2025 (EST)
I'm interested in using this to create a proposal for Dotted-Line Block, options being "Split the ones that turn into ! Blocks", "Split the ones that are on a time limit", "Split the rhythm blocks from SMBW", "Merge Color Block", and "Merge Switch Block (Mario & Wario)" --PopitTart (talk) 19:21, February 7, 2025 (EST)

@EvieMaybe How would you prevent two opposing options from both passing with this type of proposal? How would you prevent the scenario that both Waruiji and Waluigi had enough support to succeed? Would users be expected to vote "for" on one option and "against" on its opposing option? I'm just not understanding how this is helpful, honestly. --Vampire Wario from Dr. Mario 64 Pizza Master Waluigi using the Bitsize Candy from Mario Party 8 17:01, February 13, 2025 (EST)

I do not want to put words in eviemaybe's mouth, but I assume if you had a proposal with only two or three types of outcome, you would not use this type of proposal structure. It would be here if you need it for larger proposals that aim to resolve several related issues all at once, rather than make individual proposals for each one. - Nintendo101 (talk) 17:09, February 13, 2025 (EST)
i feel like you misunderstand how i proposed it. Why put Waruiji and Waluigi in two options, when you can just make an option where if it passes, you use Waruiji, and if it doesn't, you use Waluigi? — Super Leaf stamp from Super Mario 3D World + Bowser's Fury.eviemaybe (talk / contributions) 18:21, February 13, 2025 (EST)

Removals

None at the moment.

Changes

Merge the Ancient Beanbean Civilizations to List of implied species (and Hooroglyphs info to that)

Another multiple-way merge! This is about the following articles:

Simply put, these are all ancient civilizations that we don't encounter in-game, since. Well. They're long-gone ancient civilizations that are only ever mentioned alongside occasional things that originate from them, most notably the statue Hoohooros, but also Hooroglyphs and Beanstones. While we can understand keeping Hoohooros and Beanstones split--the former is a full boss encounter, the latter is a key item involved in a sidequest--we're less sure about Hooroglyphs in particular. Merges for the civilizations have been called for since around late 2023, and we think the Hooroglyphs should be merged as their split mostly comes from the decision to make a page for them back in March 2007, actually predating the Hoohoo civilization article. We've provided an option for keeping Hooroglyphs split, though we imagine it'd be better to merge this with the Hoohoo civilization information.

Proposer: Camwoodstock (talk)
Deadline: February 13, 2025, 23:59 GMT

Merge all (merge Hoohoo/Soybean Civilizations to List, merge Hooroglyphs to the Hoohoo Civilization section)

  1. Camwoodstock (talk) Per ourselves; these civilizations don't have as much plot relevance nor lore behind them as something like, say, Squirpina XIV or the Flora Kingdom royalty, at most serving as the origin for Hoohooros.

Merge civilizations, leave Hooroglyphs alone

  1. LinkTheLefty (talk) The glyphs are actually seen, though.
  2. Jdtendo (talk) Per LinkTheLefty.
  3. Nintendo101 (talk) Per LinkTheLefty.
  4. Camwoodstock (talk) Secondary option; admittedly, we're not quite sure how strong "you can see the glyphs in-game" is as a reason, but we would much rather the civilizations get merged than nothing at all.
  5. Power Flotzo (talk) Per all.

Merge Hooroglyphs to Hoohoo civilization, leave civilizations alone

Merge none (do nothing)

Comments (Indus River Valley civilization joke here)

Include italics for category page titles for media that normally uses it

Shouldn't category pages for media that uses italics (such as games, shows, movies, etc.) use italics for their category pages? I did start adding it to some pages already, but I thought it was worth proposing about it, possibly to make it policy. I feel like italics should be used though, as it is used everywhere else. For example, the page titled Category:Donkey Kong 64 should be Category:Donkey Kong 64.

Proposer: Kaptain Skurvy (talk)
Deadline: February 20, 2025, 23:59 GMT

Support

  1. Kaptain Skurvy (talk) Per proposal.
  2. Camwoodstock (talk) Wait, this isn't already policy??? We think this lack of parity speaks a lot to how neglected categories can be in some regards. While yes, the category description isn't really meant to be the main point, we don't think slightly slanted text is distracting from the actual list of articles in the category, and just because categories are more utility than text doesn't excuse the text that is there looking below the standard of a usual article for being "lesser".
  3. Super Mario RPG (talk) Nothing wrong with having more consistency around the wiki.
  4. GuntherBayBeee (talk) Per all.
  5. Salmancer (talk) It is easier to figure out what the standards are from context alone when the standards are applied in every instance.

Oppose

  1. Nintendo101 (talk) Categories are supposed to provide simple, direct, and utilitarian functions, not something to be read or presented to readers. I don't think italicizing them is necessary and would detract from their simplicity.
  2. Sparks (talk) Per Nintendo101. It doesn't feel necessary.
  3. OmegaRuby (talk) What is this supposed to change, exactly? Yes, it's in line with how pages about games are to have the subject italicized, but the change feels unneeded and especially arduous to implement for pretty much no reason. Per Nintendo101.
  4. SolemnStormcloud (talk) Per all.
  5. Rykitu (talk) Per Nintendo101

Comments

@Nintendo101: In that case, why do we italicise game titles in category descriptions? (Genuine question, I'm undecided on this proposal.) Hewer (talk · contributions · edit count) 08:58, February 7, 2025 (EST)

Because that is a proper sentence. It is not the tool itself. - Nintendo101 (talk) 20:15, February 7, 2025 (EST)
We mean... Wiki policy is to italicize game titles on their articles' names using {{Italic title}}, too, and those aren't proper sentences. They're article names. Camwoodstock-sigicon.png~Camwoodstock (talk) 19:00, February 8, 2025 (EST)
That's not the same situation in my eyes because the articles are what the site is for. That is what we are writing and presenting to the public. Of course we would italicize those. The categories are a tool, chiefly for site editors, not readers. We do not really gain anything from italicizing their titles. If anything, I worry this would lead to a lot of work to implement, either burdening site editors, porplemontage, or both. - Nintendo101 (talk) 16:05, February 9, 2025 (EST)
So category names are just tools not meant for readers, but category descriptions aren't? Hewer (talk · contributions · edit count) 18:08, February 9, 2025 (EST)
The descriptions are just sentences, and I feel inclined to render those they way we would a sentence anywhere else on the site, be it on articles or in the description for image files. - Nintendo101 (talk) 19:49, February 9, 2025 (EST)
We disagree with the notion categories are more for editors and not readers; while yes, all of the categories on the front page are maintenance categories from the to-do list, the sheer quantity of proposals for categories wouldn't make sense if they were moreso for editors, rather than your average reader; moves such as the reforms for the Look-alikes categories or the Thieves category wouldn't make sense if these weren't meant to be public-facing. And of course, there are the various categories that exist for users, but do not serve a utility purpose, such as the various "users that know a given language" categories.
As for difficulty implementing, considering the recent success stories with images without descriptions and categories without descriptions having gone from 4000+ and ≈100, to 0 and 0 respectively, we have it in good faith that this wouldn't be that hard to implement. Monotonous? Yes. But difficult? It's nothing a bit of caffeine and music can't solve. Camwoodstock-sigicon.png~Camwoodstock (talk) 18:22, February 9, 2025 (EST)
Not only for editors, but chiefly for them. I don't exclude the idea of more curious readers utilizing them, but I suspect they are exceptions. I maintain that their ease of implementation is more important to the site than the formatting inconsistency. Like, are we to be expected to format category ourselves as "[[Category:Super Mario World screenshots|Category:''Super Mario World'' screenshots]]" instead of just "[[Category:Super Mario World screenshots]]" going forward? Would we do this for the articles that are in dozens of categories? Why? I would not want to do that, and I don't find the inconsistency a good enough reason to roll something like that out, and only brings downsides. It makes the tool where one types "[[Category:" almost entirely moot because we would still need to write out the whole name just to format it this way. Others are welcomed to think differently, but I personally think the way we format these names now in categories is perfectly fine. - Nintendo101 (talk) 19:49, February 9, 2025 (EST)

even if this proposal doesn't pass, i think we should use Template:Italic title in the category pages. — Super Leaf stamp from Super Mario 3D World + Bowser's Fury.eviemaybe (talk / contributions) 10:16, February 12, 2025 (EST)

I thought that was the whole proposal. Hewer (talk · contributions · edit count) 03:32, February 13, 2025 (EST)

Split the image quality category

Issue 1: Category:Images to be reuploaded with higher quality is a very big category, with nearly 4,000 images in it right now. Even if it's something you can help with, it's very difficult to actually find anything in here. Issue 2: All other things being equal, some types of images require specific methods or skills to get that all users may not have or be comfortable with. To aid in the overall usability of this category and make it easier for skilled users to find things they can help with, I'm proposing the following two subcategories:

  • Screenshots to be uploaded with higher quality - Most Nintendo consoles don't have the ability to take native screenshots. That's all I'll say about that.
  • Assets to be uploaded with higher quality - Sites like The Spriters Resource are helpful, but they don't have everything. Getting higher quality images requires being able to extract them from the game files and/or the ability to manipulate them afterwards. This will also include images that are currently screenshots meant to demonstrate an asset, such as File:DKCTF Donkey Icon.png.

Additionally, Template:Image-quality will be modified with an extra parameter to mark the image as a screenshot or asset and categorize them appropriately. Considering we already have the rewrite and stub categories organized for better navigation, I don't see this as an issue.

Proposer: Waluigi Time (talk)
Deadline: February 20, 2025, 23:59 GMT

Split both

  1. Waluigi Time (talk) Category:Votes to be reuploaded with a better reason
  2. Technetium (talk) Per proposal.
  3. Camwoodstock (talk) We're a little surprised a split like this hasn't happened sooner, honestly; if for no other reason than it would be nice to have it organized. Per proposal.
  4. ThePowerPlayer (talk) Per proposal.
  5. Nintendo101 (talk) Per proposal.
  6. LadySophie17 (talk) Per all, which is mostly "per proposal"s anyway
  7. EvieMaybe (talk) makes perfect sense

Only split screenshots

Only split assets

Leave image quality alone

Comments on image quality proposal

Silly question; will images that are of neither screenshots nor assets that have the image-quality tag, like scans, character art/renders, or merchandise, just remain as-is? There are already a few examples of those that are all presently tagged with image-quality, like so:

  • Scan of 3D render, colors are washed out.

    Scan of 3D render, colors are washed out.

  • Muddy scan of 2D illustration, and background cropped.

    Muddy scan of 2D illustration, and background cropped.

  • Photoshop upscaled 2D promo art.

    Photoshop upscaled 2D promo art.

  • Too small image of merchandise.

    Too small image of merchandise.

Camwoodstock-sigicon.png~Camwoodstock (talk) 15:30, February 6, 2025 (EST)

Yes, anything that doesn't fall into either of the two subcategories will stay in the main one for now. I suppose we can look into splitting it further down the road, but I singled these two out because of the higher barrier to entry and also that they seem to be the bulk of the category's contents right now. --Waluigi's head icon in Mario Kart 8 Deluxe. Too Bad! Waluigi Time! 15:37, February 6, 2025 (EST)
I think this category should also be split by the media that it appears in (e.g: Category:Game screenshots to be reuploaded with higher quality. Something similar should also be done for the Articles with unsourced foreign names category. Apikachu68 (talk) 19:50, February 6, 2025 (EST)
Almost all of the screenshots in the category right now are from games so I don't think it needs to be narrowed down further just yet. --Waluigi's head icon in Mario Kart 8 Deluxe. Too Bad! Waluigi Time! 20:09, February 6, 2025 (EST)

Change "(game)" identifier to "(arcade)" on the articles of Donkey Kong, Donkey Kong Jr. and Mario Bros.

I wouldn't consider "game" to be the best identifier for the arcade games Donkey Kong, Donkey Kong Jr. and Mario Bros. There's already a Game and Watch game that shares its title with each of the arcade games, but "Donkey Kong" is the name of various other games too! There's the tabletop game, the Game Boy game, the Nelsonic Game Watch game and the slot machine. I know the slot machine is technically an arcade game, but it's not a standard cabinet like the 1981 arcade game. "Game" is a broad identifier, especially for Donkey Kong. Shouldn't a "game" identifier only be used if there's no other game with the same name? That's why we use consoles for identifiers instead, such as Mario & Sonic at the Olympic Games (Wii) and Mario & Sonic at the Olympic Games (Nintendo DS).

Proposer: Kaptain Skurvy (talk)
Deadline: February 22, 2025, 23:59 GMT

Support

  1. Kaptain Skurvy (talk) Per proposal.

Oppose

  1. Nintendo101 (talk) Those articles also cover the game's release on Famicom, NES, Atari, etc., so "arcade" would not be a holistically accurate identifier.
  2. Camwoodstock (talk) Per Nintendo101; "arcade" is kind of a misnomer when the non-arcade ports are covered on them.
  3. ThePowerPlayer (talk) Per Nintendo101.
  4. PaperSplash (talk) Per ThePowerPlayer's comment.
  5. Rykitu (talk) Per all

Comments

Maybe "arcade game" would be a decent compromise? PaperSplash (talk) 18:02, February 8, 2025 (EST)

What about Dr. Mario? That game also has a separate release also called Dr. Mario.--PopitTart (talk) 18:24, February 8, 2025 (EST)

The reason why the games Donkey Kong and Dr. Mario should keep their identifier of "(game)" is because those are by far the most popular and commonly thought-of games under their respective titles; the other articles (aside from Donkey Kong on the Game Boy) are on much more obscure devices while being clearly separate from the original game. To put it another way, "Dr. Mario (game)" is what people are looking for when they think about "the game featuring Dr. Mario"; meanwhile, you'd be forgiven for not knowing that the Gamewatch Boy game even exists at all. ThePowerPlayer Slug.png ThePowerPlayer 22:15, February 8, 2025 (EST)

what about Donkey Kong (1981)? — Super Leaf stamp from Super Mario 3D World + Bowser's Fury.eviemaybe (talk / contributions) 18:39, February 9, 2025 (EST)

That would work for Donkey Kong, but the original Mario Bros. and the arcade game of the same title were both released in 1983. jan Misali (talk · contributions) 12:49, February 12, 2025 (EST)

Standardize the use of "English", "English (United States)" and/or "English (United Kingdom)" as languages in game infoboxes

So far, the use of "English (United States)" and "English (United Kingdom)" as language identifiers in game infoboxes on this wiki has been rather inconsistent and arbitrary, to say the least. While Nintendo is typically known for providing distinct English localizations for the United States (and other English-speaking territories in the Americas) and the United Kingdom (and other territories where Commonwealth English is standard, apart from Canada), the actual differences between them, if any, have varied over time.

Historically, many Nintendo games have featured minor English text differences between their releases in the Americas and Europe/Oceania; however, these were typically not wholly separate localizations to account for the differences between American and British (or Commonwealth) English – they tended to follow American English conventions for the most part regardless. Rather, they were simple amendments made by Nintendo of Europe to Nintendo of America's existing English scripts, usually either to rectify perceived shortcomings or to modify certain terminology based on internal preferences. These versions were typically stored separately on region-specific cartridges or discs, with occasional differences in how they were labeled in internal data.

Later, during the DS, Wii, 3DS and Wii U eras, more distinct localizations specifically for the United States and United Kingdom that also accounted for regional language differences became more commonplace. However, all of the aforementioned practices have largely faded with the advent of the region-free Nintendo Switch, where games now typically release simultaneously worldwide on identical cartridges. As a result, English scripts are now more often than not also identical across regions (or at most contain only very minor differences, such as the date format used; in many cases, the date format is the only difference), though they are still almost always stored and labeled separately in internal data, typically alongside each other.

This proposal aims to determine how we should handle cases of identical or nearly identical (American) English scripts between regions when identifying languages in game infoboxes. Should we list them both as "English (United States)", simply as "English" or adhere to how they are distinguished in internal data, even when actual differences are minimal?

Proposer: PaperSplash (talk)
Deadline: February 23, 2025, 23:59 GMT

Option 1: List largely identical American English localizations only as "English (United States)"

  1. PaperSplash (talk) My third choice. I mean, when it really is just American English, I can see the argument.

Option 2: List largely identical American English localizations as simply "English"

  1. PaperSplash (talk) My first choice. I think it's the best compromise that makes the most sense, all things considered.
  2. Hewer (talk) I feel like this way is the most straightforward and accurate.
  3. CarlosYoshiBoi (talk) I mean, if it’s just the same thing and no changes (assuming it doesn’t include dates for save files), then I guess this one makes the most sense.
  4. Camwoodstock (talk) Primary option. It's the simplest, it seems reasonable enough, and is applicable across the board; while it isn't exactly in-line with how Nintendo is handling things as of the Switch era, it's reasonable enough and can easily account for pre-Switch cases very well.
  5. Jdtendo (talk) Per all. Especially if that means that we will stop using "English (United States)" for games that use a variety of English that is not specifically American and weren't even released in America such as SMBTLL or Mario & Wario.

Option 3: List both "English (United States)" and "English (United Kingdom)" if distinguished in internal data, otherwise simply list "English"

  1. PaperSplash (talk) My second choice. When internal data classifies them that way, it could make sense to follow suit...
  2. Camwoodstock (talk) Secondary choice, as this seems to be Nintendo's official methodology as of the Switch; however, this exact rationale doesn't account for situations like, say, Mario Party 8 and its infamous recall in the UK, which predates Nintendo's official distinguishing of NA English and UK English from the Switch era, leaving us at a bit of a loss for how to handle it exactly.
  3. CarlosYoshiBoi (talk) This option could also work if date formatting is different despite the game itself using the same script for the US and UK/Australia, like Mario & Luigi: Brothership.

Option 4: Do nothing

  1. CarlosYoshiBoi (talk) I’m actually surprised no one put anything in this option kind of like the title mentions “Do nothing.”

Comments

For better accuracy, "British English" should probably be "Commonwealth English." Doc von Schmeltwick (talk) 22:13, February 8, 2025 (EST)

Noted. Though I decided to focus mainly on the terminology used in game infoboxes, as I realized this wiki's use of the term "British English" is effectively its own can of worms... PaperSplash (talk) 15:35, February 9, 2025 (EST)

I'm a bit confused what this proposal is trying to change. Is it just about terminology used in game infoboxes? Hewer (talk · contributions · edit count) 11:31, February 9, 2025 (EST)

In hindsight, I realized this proposal was trying to change too many things at once, so I decided to tidy things up and focus on just the game infobox terminology for now. PaperSplash (talk) 15:35, February 9, 2025 (EST)

Realistically even though Canadian English does use British/Commonwealth spelling most of the time, they just get US English spelling in games as Nintendo groups Canada with North America and their English is pretty similar to English in the US, so Nintendo products in Canada are just the same as in the US.

In this case why don’t we also just group American English and Canadian English into one and call it "North American English" even if it’s moreso mainly American English? CarlosYoshiBoi (talk) 10:45, February 11, 2025 (PST)

I'm not quite sure exactly what point you're trying to make here, but per the documentation for the "languages" template, the reason they're labeled the way they currently are in game infoboxes is because they're the primary markets American English and British/Commonwealth English localizations are made for. And for what it's worth, whenever Nintendo specifically labels "North American English" as a selectable language whether in-game or in internal data, they usually refer to the United States or US specifically, not North America/NA as a whole. PaperSplash (talk) 16:27, February 11, 2025 (EST)
I think I’m going with the fact that the English (United States) language for Nintendo is also intended for Canada (and it’s also applied onto the "Japan" and "Hong Kong/Taiwan/South Korea" regions on the Switch) despite just using American English. Kinda like with European French where although it’s just moreso referring to Standard French/French from France, it’s intended for all French-speaking regions in Europe (France, Belgium and Switzerland). CarlosYoshiBoi (talk) 14:58, February 11, 2025 (PST)

If Nintendo is also still adding English (United Kingdom) for their games despite there being almost no differences from the North American English versions aside from date or other words if needed, why do they keep American spelling? Wouldn’t it make more sense for British English spelling to be used even if it’s one of the only differences between English (United States) and English (United Kingdom)? CarlosYoshiBoi (talk) 22:00, February 12, 2025 (PST)

Less work for something ultimately unimportant, I guess? It's not like American spelling is unintelligible to non-Americans. Anyway, what does this have to do with the proposal? Hewer (talk · contributions · edit count) 03:39, February 13, 2025 (EST)
Just came up to me somehow on the topic of American English and British English. Not as big of a problem anyways but just hit me. CarlosYoshiBoi (talk) 7:37, February 12, 2025 (PST)

Make Dark Mode available to everyone

Dark Mode is available to users with an account under preferences but it should be a toggle-able option for all users, even if they're not an editor. Wikipedia allows everyone regardless of role to toggle Dark Mode, so I don't see why this wiki shouldn't follow suit.

Proposer: Pizza Master (talk)
Deadline: February 27, 2025, 23:59 GMT

Support

  1. Pizza Master (talk) per.
  2. Nintendo101 (talk) nice idea, though I would prefer if Light Mode was called "Ground Mode" and Dark Mode was called "Underground Mode" for our site.
  3. Camwoodstock (talk) Wait, theme changes are unavailable to users not logged in? Just, at all? It's not just dark mode, it's any theme, since it's all on Preferences. This feels like something that, if it's possible, it shouldn't even be a proposal, it should just be added outright without vote. This is a very obvious quality-of-life change for users that don't happen to be logged in.
  4. Mushroom Head (talk)Why do we still need to create an account just to not torture your eyes when we use this wiki at night? It literally has zero effect to the users who are always logged in anyways.
  5. Rykitu (talk) Per all

Oppose

Comments

My question is: is it possible to enable this feature for non-logged-in visitors? I'm asking this because Dark Mode is considered a "Gadget", and not a regular MediaWiki feature. They work with JavaScript though, so I suppose it could work in some way (given we have MediaWiki:Common.js and all), but I would still ask Porplemontage (talk) if a toggleable, easily accessible Dark Mode for everyone (including non-users) is possible, if I were you. ArendLogoTransparent.pngrend (talk) (edits) 17:33, February 13, 2025 (EST)

I've asked Porple on his talk page, so we'll see when he answers. Pizza Master (talk) 17:40, February 13, 2025 (EST)
Porple's response on his talk page seems to imply that it might be possible. Pizza Master (talk)

Miscellaneous

None at the moment.

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