MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
 
Line 1: Line 1:
{{MarioWiki:Proposals/Header}}
{{/Header}}
==Writing guidelines==
''None at the moment.''
 
==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.
 
====Oppose====


===List of Talk Page Proposals===
====Comments on proposal proposal====
*Separate [[Wii U]] audio files from the ones on the [[GBA]] ([[Talk:Mario Circuit (GBA)#Separate Audio Files|Discuss]]) '''Passed'''
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)
*Merge [[Choco Cake]] with [[Chocolate Cake]] ([[Talk: Choco Cake#Merge Choco Cake with Chocolate Cake|Discuss]]) '''Passed'''
: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)
*Split the Paper Mario boos from [[Big Boo]] into a separate article. ([[Talk:Big_Boo#Split_the_Paper_Mario_boos_into_a_separate_article|Discuss]]) '''Passed'''
::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)
*Decide if [[Bandit]]s are a sub-species of [[Shy Guy]]s ([[Talk:Bandit#Decide if Bandits are a sub-species of Shy Guys|Discuss]]) '''Deadline''': June 7, 2015, 23:59 GMT
: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)
*Decide if [[Porcupuffer]]s are [[Cheep Cheep]]s ([[Talk:Porcupuffer#Decide if Porcupuffers are Cheep Cheeps|Discuss]]) '''Deadline''': June 16, 2015, 23:59 GMT
::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)
*Seperate [[Payday Waystation]] into a separate article ([[Talk:Shy Guy's Perplex Express|Discuss]]) '''Deadline''': June 18, 2015, 23:59 GMT
:@Camwoodstock you're absolutely right and that's a very good idea! {{User:EvieMaybe/sig}} 18:44, February 7, 2025 (EST)
*Recreate [[List of Saffron and Dyllis Recipes by ingredient]] ([[Talk:List of Saffron and Dyllis Recipes by ingredient#Keeping this article|Discuss]]) '''Deadline''': June 21, 2015, 23:59 GMT
*Merge [[Blurp (Yoshi's Story)]] with [[Cheep Cheep]] ([[Talk:Blurp (Yoshi's Story)#Merge Blurp (Yoshi's Story) with Cheep Cheep|Discuss]]) '''Deadline''': June 21, 2015, 23:59 GMT


==Writing Guidelines==
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.''


==New features==
==Changes==
''None at the moment.''
===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:
*[[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]].


==Removals==
====Merge civilizations, leave Hooroglyphs alone====
===Stop using the term "sub-species" on the wiki===
#{{User|LinkTheLefty}} The glyphs are actually seen, though.
For pretty much the wiki's entire run, "sub-species" (or "subspecies") has been used as shorthand to denote species like [[Gloomba]] or [[Fire Bro]] from the more basic species they're derived from (i.e. [[Goomba]] and [[Hammer Bro]]), but it's high time we put and end to it, and here's why:
#{{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.


#'''It's wrong''' - In science, "subspecies" denotes different populations of a species that are genetically, geographically, behaviourally, and/or morphologically distinct, yet still similar enough for interbreeding to occur freely when possible. What ''we'' call "subspecies" are ''not'' actually subspecies at all: they are completely different species, whether we're comparing [[Lakitu]]s to [[Koopa Troopa]]s or [[Deep Cheep]]s to [[Cheep Cheep]]s. There is no reason why we should so wilfully misuse very specific scientific terminology incorrectly when there are other options available like simply "type", "variation" or just plain "species". It's not like "beta elements" where there is no umbrella term and we have to make due with what readers are most familiar with: everyone already understands what "species" means, unlike the muddled "subspecies" (which even scientists argue about).
====Merge Hooroglyphs to Hoohoo civilization, leave civilizations alone====
#'''It's speculation''' - It's clear enough when things are based on other things to whatever extent, but classifying some enemies as "subspecies" instead of "species" has always struck me as presumptuous. Where exactly does the line get drawn? Some things like [[Koopa Paratroopa]]s are rather basic and fundamental in their own rights, with many derived species of their own, yet are still called "subspecies". And what about things like [[Shady Paratroopa]] that could be a subspecies of Koopa Paratroopas ''or'' Shady Koopas? Only a few sets of differently-coloured/powered RPG enemies and things like the red and blue ''PM'' [[Spike Top#Official profiles and statistics|Spike Top]]s really fit the proper "subspecies" definition, but we already established that we're not using science here, so all that's left are judgment calls being passed off as hard distinctions that don't actually exist in official material.
#'''It's misleading''' - Despite the liberties we're taking with the term, "subspecies" still inherently sounds like it requires close relatedness between species (based on their names and/or appearances), but for the sake of navigation and connectivity between articles, sometimes it's useful to be able to reflect the conceptual relatedness between rather different species, such as [[Clubba]]s and [[Chargin' Chuck]]s being related to the more standard Koopa species. Having relaxed terminology would make this easier (i.e. potentially [[Talk:Bandit#Decide if Bandits are a sub-species of Shy Guys|avoiding]] some [[Talk:Porcupuffer#Decide if Porcupuffers are Cheep Cheeps|TPPs]] and [[Talk:Snifit#Are_they_Shy_Guys.3F|other such discussions]]) and result in less cross-talk between users operating on differing definitions of "subspecies".
#'''It's inconsistent''' - As well as murky definitions and three different ways to spell the term ("subspecies"/"sub-species"/"sub species") being found across the wiki, and even side-by-side in single articles, there are also plenty of cases where single subjects are being called both "species" and "subspecies". For example, [[Ice Piranha Plant]] bears both [[:Category:Sub-Species]] and [[:Category:New Super Mario Bros. U Species|Category:NSMBU Species]], is listed as a "sub-species" in the [[Piranha Plant]] infobox, and is part of the "species" list in {{tem|Piranha Plants}}. This is not good.


Between the disconnect with how the real world uses the word, and the different definitions, applications and spellings throughout the wiki, there is really only one way to sum up the use of "subspecies" around here: '''''it's confusing''''', and we should get rid of it. Specifically, we should do the following:
====Merge none (do nothing)====


*Remove all occurrences of "subspecies", "sub-species" or "sub species" from the articles. Instead, everything should be called plain "species", and described informally as being based on and/or related to other species with words like "type", "variety", "kind", etc.
====Comments (Indus River Valley civilization joke here)====
*Delete [[:Category:Sub-Species]], [[:Category:Yoshi Sub-Species]], [[:Category:Donkey Kong Sub-Species]] and [[:Category:Wario Sub-Species]]. The equivalent "Species" categories exist [[:Category:Species|for]] [[:Category:Yoshi Species|all]] [[:Category:Donkey Kong Species|four]] [[:Category:Wario Species|cases]], but ideally, ''game-specific'' "Species" categories should be used to replace everything (but that's another kettle of fish altogether).
*Replace the "sub_species" variable in {{tem|Species-infobox}} with "derived_species". At the same time, "species_origin" should be replaced with "parent_species", for the sake of uniformity (there's already a "related species" variable for similar species not directly based on or providing the basis for the subject in question) and killing two birds with one stone since we'll have to fix the infoboxes anyway; this second change is from [[MarioWiki:Proposals/Archive_42#Set_Clear_Rules_as_to_What_.22Species_Origin.22_Means|this cancelled proposal]] and its [[forum:34578.0|corresponding forum thread]] (both of which debate the use of "subspecies").
*Add "subspecies" to [[MarioWiki:Good_Writing#Frequently_misused_terms|the list of frequently misused terms]].


This will affect A LOT of articles and will take time to gradually roll out, but I think it's worth doing. There is no good reason why we need to stay inconsistent, confusing and misinformed about how we go about defining the species of the ''Mario'' series.
===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|Walkazo}}<br>
'''Proposer''': {{User|Kaptain Skurvy}}<br>'''Deadline''': February 20, 2025, 23:59 GMT
'''Deadline''': June 11, 2015, 23:59 GMT


====Support====
====Support====
#{{User|Walkazo}} - Per proposal. The zoologist half of me has wanted to eradicate this accursed term from the wiki for over seven years now. No more.
#{{User|Kaptain Skurvy}} Per proposal.
#{{User|Baby Luigi}} Per Walkazo. And yes, even though the term is used to described fictional species, it still gave me misinformation when thinking about actual sub-species. That's not right. I admit I am a bit pedantic when it comes to vocabulary and jargon but honestly, I'm pedantic for the very reason of being fed misinformation, which isn't the ideal way to learn things.
#{{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|ShyGuy8}} Per Walkazo and Baby Luigi. Yes, that's not right. In fact, I think it should be ''related spiecies'' instead of ''subspiecies''.
#{{User|Super Mario RPG}} Nothing wrong with having more consistency around the wiki.
#{{User|Kart Player 2011}} Per Walkazo.
#{{User|GuntherBayBeee}} Per all.
#{{User|Mario}} Yes, remove ALL instances of it. I was misinformed about the true definition of "subspecies" this entire time I was in this wiki. This is a personal account, but if it confuses me, it's bound to confuse a lot of other readers. This wiki leads us to think "subspecies" means a derived or related organism even though the technical term is "some differences but capable of interbreeding and producing fertile offspring", especially provided that the "producing fertile offspring" part is the fundamental definition of a species. In that sense, subspecies do NOT denote separate species; the basic Linnaeus names have two names, but a third one is given if it's a subspecies. "Derived species", "parent species", "related species", these are all more correct and much more precise substitutes, making them vastly superior to the vague, confusing, incorrect "subspecies". In writing, we aim for precision and accuracy, and this proposed changes does exactly what is the gold standard in writing, so, as someone who admits of being very pedantic at times (the scathing criticism to singular "they" and contractions), it's not surprising that I want these changed enacted. This time, though, it's not pedantry, it's about being precise and accurate. It's been seven years, but better late than never to undo all that damage.
#{{User|Salmancer}} It is easier to figure out what the standards are from context alone when the standards are applied in every instance.
#{{User|SmokedChili}} Per all, but take note of the rare few [[Pale Piranha|official]] cases.
#{{User|Jazama}} Per all
#{{User|Andymii}} Per all; a nicely crafted argument. I just find it funny that we are now debating over scientific terminology in a wiki about talking mushrooms and turtle kings.
#{{User|LinkTheLefty}} Per proposal. (I also notice a bit of support due to the inadvertent spread of misinformation - "Beta" is rightfully considered a misused term as well, but I really do think a better label than "Beta elements" should be considered since it's a somewhat similar situation.)
#{{User|Mr. Ice Bro.}} Per all.
#{{User|Binarystep}} <s>my younger self would hate me for this</s> Per all.


====Oppose====
====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====
====Comments====
@SmokedChili: We ''can'' make an exception, but it's going to break consistency, and it won't be unreasonable to assume it's another species (just how people assumed all those [http://en.wikipedia.org/wiki/Dark-eyed_junco dark-eyed juncos] were separate species), and, besides, Nintendo was ''very'' wrong about terminology before (most blatantly, the most egregious and irresponsible usage of "remix" I've ever seen in official media: ''Super Smash Bros. 4''). {{User:Mario/sig}} 15:09, 5 June 2015 (EDT)
@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)


Commenting on the Shady Paratroopa part, I think we should just use the most basic enemy and say its a derivative (or whatever word we decide on using) of Koopa Troopa. {{User|Magikrazy}}
===Split the image quality category===
:I actually feel like it'd be better to say it's a derivative of both Shady Koopa and Paratroopa, rather than listing derivatives of derivatives on the most basic pages, at that makes for some potentially unwieldy lists. - {{User|Walkazo}}
'''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.


==Changes==
'''Proposer''': {{User|Waluigi Time}}<br>
===Super Mario Land 1 and 2 confirmed apart of the ''main series'' by Nintendo: Super Mario wiki should change accordingly===
'''Deadline''': February 20, 2025, 23:59 GMT
For years it has been debated whether Nintendo considered the Super Mario Land games apart of the main Mario series or not. Super Mario Wiki, and rightfully so, chose that the Super Mario Land games are not apart of the main Mario series but rather considered its own series most likely because of the Nintendo sources below.
 
====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


https://www.youtube.com/watch?v=nzERrLY-_9s <br>
====Only split screenshots====
[http://videogamemm.com/main/sites/default/files/images/DSCN1748.preview.JPG]


As one can see, Nintendo did not include the land games as part of the main Mario series titles during Mario's 25th anniversary 5 years ago. This has lead people such as myself to believe that the Super Mario Land games are indeed apart of their own series. However, as of May 29, 2015. Nintendo has updated Mario's 30th anniversary site to include all the main series Mario titles. In this list is Super Mario Land and Super Mario Land 2: 6 Golden Coins. As shown, this is included in both the American and Japanese versions of the site.
====Only split assets====


http://www.nintendo.co.jp/mario30th/index.html#/history/ <br>
====Leave image quality alone====
http://supermario.nintendo.com/#/history/


Due to this confirmation by Nintendo, all articles on Super Mario Wiki should be changed to fit this new information. Such articles as the [[Super Mario (series)|''Super Mario Series'']] articles should be changed to add the two Land games, and articles such as ''[[Super Mario Land (series)|Super Mario Land Series]]'' articles should most likely be deleted entirely due to their interference of the first two Super Mario Land games being apart of the main Mario series. Other changes being the chronological order of Mario titles. An example being, changing "New Super Mario Bros. is the eighth installment in the Super Mario series." To. "New Super Mario Bros. is the tenth installment in the Super Mario series."
====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)


These things might change from time to time, but it's the company's current view that should be reflected on the articles. This is why the Super Mario Land games should now officially be considered apart of the main Mario series by Super Mario wiki.
===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.]]''===
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)]].


'''Proposer''': {{User|thenintendostooge}}<br>
'''Proposer''': {{User|Kaptain Skurvy}}<br>'''Deadline''': February 22, 2025, 23:59 GMT
'''Deadline''': June 14, 2015, 23:59 GMT


====Support====
====Support====
#{{User|thenintendostooge}} Per my proposal. Due to the recent confirmation by Nintendo themselves, the wiki should have articles changed to fit this new confirmation.
#{{User|Kaptain Skurvy}} Per proposal.
#{{User|Aokage}} More recent stuff takes precedence. It doesn't really make sense to exclude the Land games from the main series, anyway.


====Oppose====
====Oppose====
#{{User|Walkazo}} - While the 30th anniversary stuff is more recent, the fact that the 25th anniversary excluded the ''SML'' games shouldn't be ignored, and it should be kept in mind that unlike the ''[[Super Mario History 1985-2010]]'' booklet (which is more complete than the linked-to poster and video), the 30th anniversary stuff leaves out all the remakes (i.e. ''SMAS'' and the ''SMA'' series), and the US version of the website also leaves out ''Lost Levels''. Plus, neither celebration included [[Super_Mario_(series)#Ports.2C_remakes.2C_and_downloadable_content|all the random ''SMB'' remakes and whatnot]], whereas ''we'' '''do''' need to take everything into account, from the remakes to the conflicting and ever-changing stances Nintendo takes on its material, and then organize them in the way that makes the most sense. And I still think it makes more sense to keep the ''SML'' games separate in History sections, templates and categories (this is actually a big change with far-reaching consequences being proposed here: not just [[Super Mario (series)]] and a few articles' opening lines), given how different the series is, its historic separation from the rest of the games, and most of all, the fact that the series straddles both ''SM'' and ''[[Wario Land (series)|Wario Land]]'' (awkward at the best of times, but it'd be worse if no bridge series is used or acknowledged). And for all we know, the 35th anniversary will be back to separating them anyway. But I ''do'' think the ''SM'' series page should include ''SML'' (and ''Yoshi's Island'') somehow, like how it's got the remakes listed separately - but certainly not ''instead'' of the [[Super Mario Land (series)|''SML'' series page]], especially considering that ''WL:SML3'' and ''VB:WL'' definitely '''aren't''' ''SM'' material, yet should still be grouped with the first two games ''somewhere'', as well as in appropriate History sections (same reason why [[Super Mario Advance (series)|''SMA'' gets its own series page]], despite being mostly part of ''SM'' and otherwise part of [[Yoshi (series)|''Yoshi'']]).
#{{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|ShyGuy8}} Per Walkazo
#{{User|Camwoodstock}} Per Nintendo101; "arcade" is kind of a misnomer when the non-arcade ports are covered on them.
#{{User|ThePowerPlayer}} Per Nintendo101.
#{{User|PaperSplash}} Per ThePowerPlayer's comment.
#{{User|Rykitu}} Per all


====Comments====
====Comments====
@Walkazo. Potential change does not warrant the act of keeping something the same. The wiki is to be based on current viewpoints of Nintendo which is the lore creator. It's the company's current view that should be reflected on the articles. If we were to not follow Nintendo's viewpoint, any viewpoint could be established based on the person's own imagination. "What if Nintendo decides to officially change Birdo to Ostro to avoid confusion?" This is irrelevant as it is based on what Nintendo finds true and not true. "If" cannot be a factor of whether or not we apply the land games or not. That would be based on our own assumptions and our assumptions are endless. We must use Nintendo's current viewpoint to stay relevant in the Mario franchise. If not the wiki becomes outdated with old information. {{unsigned|Thenintendostooge}}
Maybe "arcade game" would be a decent compromise? [[User:PaperSplash|PaperSplash]] ([[User talk:PaperSplash|talk]]) 18:02, February 8, 2025 (EST)
:My point isn't that Nintendo ''might'' change their minds again, but rather, that they really doesn't give a crap about "lore", "true"ness or keeping its stories straight when it comes to ''Mario'': they flip-flop about stuff all the time and information is often inconsistent, and as a result, the only way to maintain easy, logical organization is for the wiki to think for ourselves sometimes, like with splitting, merging and grouping enemies based on facts other than plain names, or deciding on how to organize our game pages. For in-universe stuff like the Kooplaings' paternity, our hands are tied and we need to give the new story prominence (but still mention the old story), but this is a different matter: as long as we acknowledge on all the relevant pages that Nintendo currently considers ''SML'' 1 & 2 as part of the ''SM'' series, and didn't before, whether or not we follow up with shuffling History sections, categories, lists and templates is up to us, based on whether we think it will or won't be a better way to present and organize the information. - {{User|Walkazo}}
 
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 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)
 
what about Donkey Kong (1981)? {{User:EvieMaybe/sig}} 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. {{User:JanMisali/sig}} 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.


Whether Nintendo cares about the Mario canon or not is not for us to decide. We can mention how Nintendo used to not consider the Land games being apart of the main series, but we must also tell the reader Nintendo's current stand point. An example being starwars. The lore is changing all the time, however, the star wars wiki does not keep the old lore as canon. It mentions how it used to be canon, but supports the current standpoint of lucas film if we like it or not. There is much Mario lore that Nintendo has dropped that has been official in the past. This is not a situation like the koopalings where the creator of Mario says they are not Bowsers kids, but this is the whole company of Nintendo saying that the Super Mario Land games are indeed apart of the main series. Both in Japan, and all over the World. I know it sounds like a lot of work for us to have to update so many articles. If there is official information with no way to disprove it, it CANNOT be denied. All official Mario information must be used in Mario wiki. One could argue that the past has more info, but that does not make it relevant. Over time things become outdated and it is Nintendo that updates it. We must accept what Nintendo updates. {{User|Thenintendostooge}}
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?


@Walkazo - I'm not completely confident in either choice right now, but remakes/rereleases were never a necessary mention in official celebrations since it's understood that they're not exactly the original titles (we certainly don't count them as such, either), so I'm not sure why they're factored in the counter-argument... (I must say, ''Super Mario 3D Land'' makes sense with its namesake included.) [[User:LinkTheLefty|LinkTheLefty]] ([[User talk:LinkTheLefty|talk]]) 17:54, 7 June 2015 (EDT)
'''Proposer''': {{User|PaperSplash}}<br>
'''Deadline''': February 23, 2025, 23:59 GMT


@LinkTheLefty- Indeed, the remakes have never been mentioned to be apart of the main Super Mario titles. As we all know, Super Mario Land 1 and 2 are not remakes of any main series Mario game. Unless someone has any evidence to prove that Super Mario Land 1 and 2 are not apart of the main series, and since Nintendo has stated they are apart of the main series as of now, it is only right to have Super Mario wiki state the same. {{User|Thenintendostooge}}
====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.


:My point is that what works for Nintendo for their celebration stuff doesn't necessarily work for us, since they're cherry-picking lists of showy platformers while we're trying to document every single game and present all that info in the clearest way possible. They already cut out plenty of remakes and obscure games that we can't, and they don't need to worry about awkward things like ''SML'' and ''SML2'' having a direct sequel (''WK:SML3'') that's also the start of a separate series, and another followup that never got finished (''VB Mario Land'') and wouldn't've fit in either ''SM'' or ''WL'' anyway. As long as we're basing out decisions on facts, we're allowed to make judgment calls when splitting, merging or reclassifying iffy enemy situations and whatnot, and similarly, we're also allowed to think outside the box a bit when it comes to dealing with iffy series situations. Like I said in my vote, the first two ''SML'' series games should be acknowledged on [[Super Mario (series)]] (that page is missing a lot of remakes too, but I digress), but they should remain separate when it comes to overall wiki organization. (On a side note, my guess is that ''SM3DL'' is the reason why the games are included this time around, unlike in 2010, although besides the name, like every other ''SM'' game, it has nothing to do with ''SML'' or its sequel at all.) - {{User|Walkazo}}
====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]]''.


===Ban the term beta<nowiki>*</nowiki> and rename pages in the Beta namespace===
====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.


[http://www.mariowiki.com/MarioWiki:Proposals/Archive_36#Correct_use_of_the_term_.22Beta.22 There was a proposal] suggesting to change the name of the "beta elements" page to something more accurate. Despite being close to succeeding, it was vetoed by the admins with the reason being that "it's not meant to be taken literally" and "it works".
====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.


Except. no. The suggestion was perfectly cogent, the rationale provided for the veto was bad and the proposal should never have been reversed. Here's why
====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)


1: '''It's a bad, innacurate term''': "Beta" in programming language refers to a prerelease build that's feature-complete and is being bugtested. It's not even a particularly representative term: the beta period happens near the end of development, long after production ideas are shot down, games are overhauled, unique characters and objects are removed... etc, which is what the "beta" pages usually cover.
: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)


Some may argue that "language evolves" and that "beta as it is used here is not meant to be taken literally", but I don't think it's a strong arguments. Sites focused on the documentation of unused/prelease content such as Unseen 64 and TCRF have mocked the usage of "beta" as a catch-all term and lower-quality ressources that use it that way. Other fan wikis like SegaRetro also [http://segaretro.org/Beta do not use] "beta" as a generic term. Fact is, "beta" is nowhere near accepted in professional circles and that's what the wiki claims to be - a professional ressource. Furthermore, why would you use an inacurate and potentially misleading term when dozens of accurate, non-misleading alternatives exist?
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)


2: '''It leads to muddy, vague writing.''' Whenever you see "beta" used on other pages, its catch-all nature muddies the information. "[[Dread Kong|Dread Kong did not exist in the beta version of Donkey Kong Jungle Beat]]" - nevermind that referring to a singular "beta version" betrays a gross ignorance of how game development works, what's the "beta" in question? A preview in a magazine? A proto leaked on the internet? Something suggested in pre-production that was rejected and never programmed into the game? Banning the generic beta  and forcing editors to be more specific (as opposed to the current [[Mariowiki:Good Writing|wishy-washy stance]] that "we know it's bad, but we still use it because reasons I guess") will improve the quality of the information.
: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)


3: '''The "grandfather clause" is never a good excuse:''' Similar to this case, "sub-species" is a long-used term that was found to be innacurate and cause inconsistencies, and the current community concensus is that it should be replaced despite its longstanding nature. "It's what we've always used" is not a good refutation when the usage of a term is proven to lower the credibility and quality of the information, as is the case here.
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.  


As a replacement, I propose beta pages to be renamed '''List of prerelease and unused content'''. "Prelease" perfectly encansuplates the varieties of content that's not present in the final code, and it's wordier, yes, but not overly so. Generic mention of "beta" should not be robotically replaced with a generic "In prelease/unused content of [game]", but rather with a specific term ("magazine preview", "prototype", "unused"), with a piped link to the "List of..." pages.
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)


(<nowiki>*</nowiki>: This of course doesn't apply to actual beta builds, but as none of the specific builds documented here are specifically said to be real betas, that precision is kinda irrelevant.)
: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)


'''Proposer''': {{User|Glowsquid}}<br>
::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)
'''Deadline''': June 15, 2015, 23:59 GMT


====Move beta pages to "List of prelease and unused content" and ban the generic "beta" in mainspace articles====
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)
#{{User|Glowsquid}}
 
#{{User|thenintendostooge}} Simply because something works does not make it professional or the most efficient. The simple term beta used on the wiki goes against basic definition and term of the word that is beta.
: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)
#{{User|LinkTheLefty}} "Beta" probably could be validated ''if'' it was actual developer terminology that refers to a specific point of development or build, but since Nintendo doesn't and won't do that publicly, I am completely okay with Beta banning for those reasons. Per proposal.
 
#{{User|ShyGuy8}}I am okay with this. beta is a bad term but I don't know what it will be after this. Per [[User:Glowsquid|Glowsquid]].
::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)
#{{User|Mario}} Okay, I'll let it out: I felt cheated when I saw that veto and I agree that it should've never happened, and ''it should not happen again''. This poorly-handled veto deserves ''all'' the criticism it gets for using administrative powers to shut down legit debate. Anyhow, nonstaff user's opinions aside, by keeping the term "beta" as "a-okay", we're contradicting our own policy, the [[MarioWiki:Good Writing#Frequently misused terms|Good writing's frequently misused terms]]. This policy will cause confusion for newer users by saying it's not okay to use "beta" while in the same time, using that term in the same way. Now, I'm feeling confident to lambast the staff team's reasoning and decision, hear me out. This is the reasoning: ''"'Beta' was never meant to be taken literally as the specific beta version, but as a convenient umbrella term synonymous with 'pre-release'. It works perfectly well as-is; there is no need to change the name.''" This reasoning has several problems. "It's never meant to be taken literally" is dodging the basic argument, that "the terminology has never been a problem in the first place" when that there was an entire proposal about it that garnered massive support (only to be shut down by a handful of people) about the usage of that term. It doesn't matter if we "intended" the term to be "taken literally"; this term certainly confuses, misleads, and misinforms our readers, just as how "subspecies", apparently, is never meant to be taken literally in this wiki. The usage of "beta" as a convenient umbrella term ''is'' the entire problem with that forsaken word. We have a much better umbrella term "pre-release and unused elements" that is not only far superior, but does not flirt with the line into pedantry.
 
===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.


====Oppose====
====Oppose====


====Comments====
====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)


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

Latest revision as of 18:21, February 13, 2025

Image used as a banner for the Proposals page

Current time:
Thursday, February 13rd, 23:21 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."

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)

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.

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:

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.

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)

Miscellaneous

None at the moment.