MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
 
Line 1: Line 1:
<center>http://i143.photobucket.com/albums/r149/Deadringerforlove/dessert1.jpg</center>
{{/Header}}
<br clear="all">
==Writing guidelines==
{| align="center" style="width: 85%; background-color: #f1f1de; border: 2px solid #996; padding: 5px; color:black"
''None at the moment.''
|'''Proposals''' can be new features (such as an extension), removal of a previously added feature that has tired out, or new policies that must be approved via [[Wikipedia:Wikipedia:Consensus|consensus]] before any action(s) are done.
*Any user can support or oppose, but must have a strong reason for doing so, not, e.g., "I like this idea!"
*"Vote" periods last for one week.
*All past proposals are [[/Archive|archived]].
|}
A proposal section works like a discussion page: comments are brought up and replied to using indents (colons, such as : or ::::) and all edits are signed using the code <nowiki>{{user|</nowiki>''User name''<nowiki>}}</nowiki>.


This page observes the [[MarioWiki:No-Signature Policy|No-Signature Policy]].
==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?


<h2 style="color:black">How To</h2>
My suggestion is to create a second type of proposal, tentatively named '''poll proposals'''.  
#Actions that users feel are appropriate to have community approval first can be added by anyone, but they must have a strong argument.
*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.  
#Users then vote and discuss on the issue during that week. The "deadline" for the proposal is one week from posting at:
*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.
#*Monday to Thursday: 17:00 (5pm)
**Abstaining from some options should be allowed too.
#*Friday and Saturday: 20:00 (8pm)
*Each vote is subject to the same approval percentages as a regular old Support/Oppose proposal.
#*Sunday: 15:00 (3pm)
*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?
#Every vote should have a reason accompanying it.
*Poll proposals must be clearly marked as such, to make it clear how one is supposed to vote.
#At any time a vote may be rejected if at least '''three''' active users believe the vote truly has no merit or was cast in bad faith. However, there must be strong reasons supporting the invalidation.
#"<nowiki>#&nbsp;</nowiki>" should be added under the last vote of each support/oppose section to show another blank line.
#All proposals that end up in a tie will be extended for another week.
#If a proposal has more than ten votes, it can only pass or fail by a margin of '''three''' votes. If a proposal reaches the deadline and the total number of votes for each option differ by two or less votes, the deadline will be extended for another week.
#Any proposal that has three votes or less at deadline will automatically be listed as "[[Wikipedia:Quorum|NO QUORUM]]." The original proposer then has the option to relist said proposal to generate more discussion.
#No proposal can overturn the decision of a previous proposal that is less than '''4 weeks''' ('''28 days''') old.
#Proposals can only be rewritten or deleted by their proposer within the first three days of their creation. However, the proposer can request that their proposal be deleted by a [[MarioWiki:Administrators|Sysop]] at any time, provided they have a valid reason for it.
#All proposals are archived. The original proposer must '''''take action''''' accordingly if the outcome of the proposal dictates it. If it requires the help of a Sysop, the proposer can ask for that help.
#There shouldn't be proposals about creating articles on a underrepresented or completely absent subject, unless there is major disagreement about whether the content should be included. To organize efforts about completing articles on missing subjects, try creating a [[MarioWiki:PipeProject|PipeProject]].
#Proposals can not be made about [[MarioWiki:Administrators|System Operator]] promotions and demotions. Sysops can only be promoted and demoted by the will of [[MarioWiki:Bureaucrats|Bureaucrats]].
#If the Sysops deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to remove it at any time.
#No joke proposals. Proposals are serious wiki matters, and should be handled professionally. Joke proposals will be deleted on sight.


The times are in EDT (UTC -4:00), and are set so that the user is more likely to be online at those times (after work/school, weekend nights). If a proposal is added on Saturday night at 11:59 PM EDT, the deadline is the next Saturday night at 8:00 PM. If it is a minute later, the deadline is a day plus 15 hours (Sunday), as opposed to a day minus 4 hours.
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".  


__TOC__
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".


<center><span style="font-size:200%">CURRENTLY: '''{{LOCALTIME}}, {{LOCALDAY}} {{LOCALMONTHNAME}} {{LOCALYEAR}} (EDT)'''</span></center>
'''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.


==New Features==
====Oppose====
===Create a Definition of Stub Articles===
This Proposal is actually a mere bureaucratic issue, but in order to keep up the democratic structure, we will go through this procedure first.


This proposal concerns Stubs, those annoying articles that make our wiki look unproffessional. Regarding the fact that we have about 1'000 of these articles, it sort of becomes necessary to have a definition for them. At the moment, articles are at the users' mercy to get tagged as stubs or not. An article might get flagged by one user, while another one disagrees. Of course, both sides have their own equally right definitions, and the situation would turn into an edit war if the tag would be removed again. Using Stub tags seems to be based upon decisions made by subjectivity and vastly differs from case to case.
====Comments on proposal proposal====
Our only complaint is in the mockup; we feel like it could be made a ''lot'' more clear which votes are for/against in some way. Maybe a pair of <nowiki>{{For}}</nowiki> and <nowiki>{{Against}}</nowiki> templates? (In this context, we think making these templates is fine; you already need to know how to use <nowiki>{{User}}</nowiki> to vote, after all, and we're imagining these will be very, very simple to use.) {{User:Camwoodstock/sig}} 17:41, February 7, 2025 (EST)
:That, but what purpose would "against" votes have compared to just not voting on that option? {{User:Mario/sig}} 17:42, February 7, 2025 (EST)
::Same as it would in a regular proposal, each option acts as an individual 2-option vote. If no one opposes an option (and it meets quorum requirements), then it passes. --[[User:PopitTart|PopitTart]] ([[User talk:PopitTart|talk]]) 17:56, February 7, 2025 (EST)
:I feel like the easiest solution is just "for" and "against" subheaders under each option. [[User:Ahemtoday|Ahemtoday]] ([[User talk:Ahemtoday|talk]]) 18:04, February 7, 2025 (EST)
::That would also work for us! Our only real concern is that this could result in level-5 subheaders on proposals on this page specifically, which... Don't look all that great. Even still, we just need ''something'' to disambiguate at a glance what is what, and this will do the job just well. {{User:Camwoodstock/sig}} 23:01, February 7, 2025 (EST)
:@Camwoodstock you're absolutely right and that's a very good idea! {{User:EvieMaybe/sig}} 18:44, February 7, 2025 (EST)


This Proposal's purpose is to take these decisions out of subjectivity's hands and to hand them over to a Guideline that will help us to identify Stubs, without having those horrendous differences between cases. I think this is necessary. How are you supposed to fight something if you cannot even identify it?
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)


As for the contents of this definition, I think the guidelines from [[PipeProject: Unstubify|Knife's PipeProject]] would give us a '''general idea''' what it could be like. With this, every article that doesn't provide the viewer with answers to the most basic questions becomes stub material; basic questions like:
{{@|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)
#What is the origin of the subject?
: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)
#Where is it located? How is it accessed? How can it be unlocked?
: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)
#What does it do? What is its purpose?
#Which characters can it be used by? What things are a part of it?
#What templates or categories can be applied within possibility? If possible, what images can be added?


Of course the resulting definition will not be a mere rip-off of this questions. Something like this needs to be planned thoroughly. '''This Proposal's point is just to check what users think about a Stub definition in general, !'''
==Removals==
''None at the moment.''


And now, to end this load of text: Since I based this Proposal largely on a definition from {{User|Knife}}, I bestow the same rights as the proposer holds upon him, meaning that he can edit or remove this Proposal like he pleases.
==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:
*[[List of implied species]]
*[[Hoohoo civilization]]
*[[Soybean civilization]]
*[[Hooroglyphs]]


'''Proposer:''' {{User|Edofenrir}} (with {{User|Knife}} holding the same rights)<br>
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.
'''Deadline:''' 26. November 2009, 17:00


====A Definition of Stubs will be helpful====
'''Proposer''': {{User|Camwoodstock}}<br>
#{{User|Edofenrir}} - Having a four-didgit amount of them makes it kind of necessary. I think we will profit from this.
'''Deadline''': February 13, 2025, 23:59 GMT


====We don't need a Definition====
====Merge all (merge Hoohoo/Soybean Civilizations to List, merge Hooroglyphs to the Hoohoo Civilization section)====
#{{User|Time Q}}: Firstly, I really don't think we need an objective definition of what a stub is. Seems like a lot of trouble we could avoid by just going on the way we always did it. I can't think of any "flame wars" that arose due to the "stub" notion. Secondly, I don't think we can find a proper definition. Stubs can appear in vastly different forms (mostly depending on the article's subject's prominence), and I can't imagine a way to subsume all the different possibilities under a common definition. Thirdly, I think this is a strange proposal. What if we decide to establish a definition, but then fail to find a good one?
#{{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]].


====Comments====
====Merge civilizations, leave Hooroglyphs alone====
I don't get it. What exactly are we voting for? [[User:Panchito|Panchito]]
#{{User|LinkTheLefty}} The glyphs are actually seen, though.
:A more simplified version of the Proposal is: "Do you want a clear definition for what a stub is, or do you want that everyone decides on his/her own about that (which would result in very different opinions)." I hoped I didn't make it too complicated. - {{User|Edofenrir}}
#{{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.


==Removals==
====Merge Hooroglyphs to Hoohoo civilization, leave civilizations alone====
''None at the moment.


==Splits & Merges==
====Merge none (do nothing)====
===Put Waffle Kingdom and all the related places into "List of Implied Locations"===
Some of you may know [[Waffle Kingdom]]. I propose this article and all the locations related to it to be merged with [[List of Implied Locations]].


The reason is quite simple: The Waffle Kingdom is never actually visited in any game, and is therefore an implied location (duh). If that isn't enough reason, then there are plenty of other ones. It is f.e. impossible to add images to these articles and there's not much info available for them. Too few to fill a whole article. So, for the sake of fighting stubs and such, let us merge this articles.
====Comments (Indus River Valley civilization joke here)====


'''Another thing''': Since I can change this proposal within the first three days, I will use this to add another thing. Like SMB said, Princess Eclaire should also be merged with the [[List of Implied Characters]] if this proposal passes. Not sure about the Chestnut King, because this could also be a mistranslation of the [[Goomba King]].
===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|Edofenrir}}<br>
'''Proposer''': {{User|Kaptain Skurvy}}<br>'''Deadline''': February 20, 2025, 23:59 GMT
'''Deadline:''' 21. November 2009, 15:00


====Merge them====
====Support====
#{{User|Edofenrir}} - Per consistency and myself.
#{{User|Kaptain Skurvy}} Per proposal.
#{{User|Super Mario Bros.}} Per Edofenrir, and we also would have to merge the Princess Eclair page and the Chestnut King into List of Implied Characters.
#{{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|Zero777}} I am Zero! Merge them, no picture and little info, belongs to implied locations. Zero signing out.
#{{User|Super Mario RPG}} Nothing wrong with having more consistency around the wiki.
#{{User|Marioguy1}} - Per Edo. If this proposal somehow fails then I am adding an image tag!</tryingtolooktough>
#{{User|GuntherBayBeee}} Per all.
#{{User|Gamefreak75}} - PEr Edo.
#{{User|Salmancer}} It is easier to figure out what the standards are from context alone when the standards are applied in every instance.
#{{User|Vini64}} Per all.
#{{User|Grandy02}} Per Edo.
#{{User|T.c.w7468}} Per Edo.
#{{User|Stooben Rooben}} - Per Edo; I've always meant to make a proposal just like this for the exact same reason.
#{{User|Karinmij}} Per all of the above.


====Don't merge them====
====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====
Regarding the "Chestnut King", this is a mistranslation for Goomba King/Goomboss for sure, his Japanese name is always the same, while his English name changes from Goomba King to Chestnut King to Goomboss. There could still be a reference for that in the List of Implied Characters, but information about "Chestnut King" should go to the Goomboss article. --{{User|Grandy02}}
@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)


==Changes==
===Split the image quality category===
===Update Character-infobox Templates===
'''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:
I'm proposing we update the character info boxes a bit; in different areas.
*'''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.


They are currently set up so it has:  
'''Proposer''': {{User|Waluigi Time}}<br>
'''Deadline''': February 20, 2025, 23:59 GMT


*character's name
====Split both====
*a current image with a small description
#{{User|Waluigi Time}} Category:Votes to be reuploaded with a better reason
*their full name
#{{User|Technetium}} Per proposal.
*their first appearance
#{{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.
*their species, all media
#{{User|ThePowerPlayer}} Per proposal.
*their affiliations, any amount
#{{User|Nintendo101}} Per proposal.
*their latest appearance
#{{User|LadySophie17}} Per all, which is mostly "per proposal"s anyway
*who they are portrayed by, ever
#{{User|EvieMaybe}} makes perfect sense


Will be changed to:
====Only split screenshots====


*character's name
====Only split assets====
*a current image with a small description
*their full name
*their first appearance
*their species, current depiction only unless first appearance is different
*their affiliations, set amount
*their latest appearance
*who they are portrayed by, most recently


I'm proposing we change it so that unless their first appearance was in a media type other than a video game, it not be mentioned what they may have been in that media type. Sure it makes sense to mention what a character's species was in the film, but that's what the film section is for. To mention that difference. On the other hand if for some reason a character has showed up in the film first, it would make sense to mention that in their species category in the template box. Otherwise you're focusing on information that is widely far apart from their actual design. Toad and Daisy are two good examples of characters that should not have this information in their infoboxes. Neither of them are actually reptilian(dinosaur) in any manner of speaking, so why mention it here rather than where it is relevant?
====Leave image quality alone====


Next, I'm proposing to change it so that affiliations can have no more than three things listed. Some articles seem to mention far too much such as Wario's. Naming one friend, one enemy, and one location is not hard. And it's not like it doesn't explain interactions in the section for this information. That doesn't mean it has to be a friend an enemy then a place, but it means the list can not exceed three things(friend, friend, place/enemy, enemy, friend/etc.)
====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)


Change portrayed by section to latest portrayal. There's a reason there are sections explaining who portrayed characters in what game on each page. It's so viewers can read who played who in what. However, stating in the infobox EVERY person that has played the character in EVERYTHING they've ever been in is unnecessary and messy. Stating who their latest voice actor is should be no problem. If somebody wanted to know who played Toad in the film, they could go to either the film or portrayals section and find out. But if somebody just wants to know who most recently voiced Toad, they should be able to look at his infobox, and then know instantly. Oh, that's the actress who currently(most recently) voices Toad. Also, this will go along with their latest appearance because that way they know who voiced them in what game most recently.  
===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)]].


Each section change or addition will be broken up into numerous different proposals below.
'''Proposer''': {{User|Kaptain Skurvy}}<br>'''Deadline''': February 22, 2025, 23:59 GMT


'''Proposer:''' [[User:ForeverDaisy09|FD09]]<br>
====Support====
'''Deadline:''' 20 November 2009, 20:00
#{{User|Kaptain Skurvy}} Per proposal.


====Species====
====Oppose====
=====Change It=====
#{{User|Nintendo101}} Those articles also cover the game's release on Famicom, NES, Atari, etc., so "arcade" would not be a holistically accurate identifier.
Species section will only give the characters actual species; unless first appearance is media outside of current appearance.
#{{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


#[[User:ForeverDaisy09|FD09]] Per above.
====Comments====
#{{User|Edofenrir}} If this will keep Bowser from being classified as human, I'll support. Besides, exceptions made in one single installment shouldn't be in the infobox. If fits better in the respective section.
Maybe "arcade game" would be a decent compromise? [[User:PaperSplash|PaperSplash]] ([[User talk:PaperSplash|talk]]) 18:02, February 8, 2025 (EST)
#{{User|Gamefreak75}} - I agree with Zero, but then I agree with Edo. Bowser a HUMAN!?!? O_o
#{{User|Marioguy1}} - The information would still be in the page but just closer to the bottom.
#[[User:Toadine|Toadine]] - Per all. This wiki desperately needs some new organisation methods..
#{{User|Walkazo}} - Per all. The infobox is for general facts-at-a-glance, but if a character was a different species in 1 out of 100 depictions, that's more of a minor detail that may confuse people without the context it needs up in that list.
#{{User|Stooben Rooben}} - Per all.
#[[User:Panchito|Panchito]] - Per All.
#{{User|T.c.w7468}}- Per all.
#{{User|Dodoman}} - Per Edofenrir.


=====No Change=====
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)
Species section will give list of species from all appearances; even if they are not current.
::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)


#{{User|Zero777}} I am Zero! Even though I like the idea of changing species into there current appearence because I hate of what I heard about the Super Mario Movie's generic version of each character I oppose, the reason why is, even though we should treat the SMW as a community don't forget we are still a free online encyclopedia, so I oppose because we need to show to the guests every bit of information about that article they are looking at, and plus the info-box is like a short summary of only that person or thing on the article, so why should the guest have to look in a enormouse page or a regular size one to find out in one appearence that character has made in, he was another species? Zero signing out.
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)


=====Comments=====
===Standardize the use of "English", "English (United States)" and/or "English (United Kingdom)" as languages in game infoboxes===
(Since these are actually four proposals, I will make my comment here because it specifically applies to only this section). <br> Gamefreak75: Bowser was a human, or rather a human evolved from a dinosaur in the live-action movie, just like Toad and Princess Daisy. <br>Marioguy1: The point of this proposal is not to ban these informations from the article, it's about moving them. The meaning of a characterbox is to provide the viewer with '''basic''' information about a character, so the reader can get a picture of the chara quickly. Listing exceptions within the infobox would be distracting, so the info should rather be moved to the section where this exception applies. No information is lost that way, and more structure is gained. - {{user|Edofenrir}}
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.


====Affiliations====
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.
=====Change It=====
Affiliations section will only list three things.  
(Not so much a change, as it is simply setting order)


#[[User:ForeverDaisy09|FD09]] Per above.
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.
#{{User|Super Mario Bros.}} Sounds good to me. Per FD09.
#[[User:Toadine|Toadine]] - Per FD09.


=====No Change=====
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?
Self explanatory.


#{{User|Zero777}} I am Zero! The reason why goes the same as the one about the character's species above, although we need to organize some character's affiliations somehow. Zero signing out.
'''Proposer''': {{User|PaperSplash}}<br>
#{{User|Marioguy1}} - If they are affiliated with more than three things then why limit them to three?
'''Deadline''': February 23, 2025, 23:59 GMT
#{{User|Gamefreak75}} - Per Zero and Marioguy.
#{{User|Edofenrir}} - I would actually support this if it was slightly different. Instead of limiting them to a specific number, they should be limited down to the most basic affiliations (which in some rare cases can be more than three).
#{{User|Walkazo}} - Per Edofenrir. Using common sense and discretion is the best way to deal with subjective cases like these.
#{{User|Stooben Rooben}} - Per Edo.
#{{User|Dodoman}} - Per Edo.


====Portrayed By====
====Option 1: List largely identical American English localizations only as "English (United States)"====
=====Change It=====
#{{User|PaperSplash}} My third choice. I mean, when it really is just American English, I can see the argument.
Portrayed By section will be change to Latest Portrayal and will list only the most recent portrayal of the character.


#[[User:ForeverDaisy09|FD09]] Per above.
====Option 2: List largely identical American English localizations as simply "English"====
#{{User|Super Mario Bros.}} As long as the other earlier portrayals are mentioned in the article itself, that sounds organized.
#{{User|PaperSplash}} My first choice. I think it's the best compromise that makes the most sense, all things considered.
#{{User|Dodoman}} YES! Mario's had like, what, 10 voice actors? That's a huge clutter for that tiny infobox. Keep portrayals in their designated section.
#{{User|Hewer}} I feel like this way is the most straightforward and accurate.
#{{User|Edofenrir}} - Per SMB. Only if the other portrayals are listed somewhere else.
#{{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|Marioguy1}} - As I said above; the information would be in the article just not in the infobox.
#{{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:Toadine|Toadine]] - Per SMB. I like the change as long as we still have earlier portrayals mentioned.
#{{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]]''.
#{{User|Stooben Rooben}} - Per SMB.
#[[User:Panchito|Panchito]] - Per All.


=====No Change=====
====Option 3: List both "English (United States)" and "English (United Kingdom)" if distinguished in internal data, otherwise simply list "English"====
Portrayed By section will not change and will list every single actor that has portrayed the character, ever.
#{{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.


#{{User|Zero777}} I am Zero! The maximum portrayals I seen is about ten, even though it will make the info-box a little long, I see no promblem of just putting the portrayer's name, what game or appearence did they made that portrayal (in parenthases of course), and then put <nowiki><br></nowiki> at the end of each portrayer's appearence to make a nice clean list of all the portrayists if you can do that. Zero signing out.
====Option 4: Do nothing====
#{{User|Walkazo}} - Per Zero: ten names isn't so bad a list, and simply getting them over with in the infobox is the simplest and most concise way to include the actors in the article (as opposed to writing a clunky list in the introduction, making an entire "portrayals" section later on, burying them in the History or stuffing them into the unwanted Trivia catch-all). Also, naming only one actor seems like we're side-lining the rest of them, many of whom were the voices of our iconic characters for years... it just feels wrong.
#{{User|CarlosYoshiBoi}} I’m actually surprised no one put anything in this option kind of like the title mentions “Do nothing.”


====Comments====
====Comments====
One vote per user - srry {{User|Marioguy1}}
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)
:lol I know that, clearly. While I have this set up as One Proposal it is basically divided into different proposals. They just all happen to concern the same thing. Is it really that confusing? [[User:ForeverDaisy09|FD09]]
 
::I once made the same thing but it got deleted {{User|Marioguy1}}
: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)
:::Nah, I don't find it confusing at all. It is actually kind of clever to divide this proposal into more than one, or else people might have conflicting opinions about the different points which would prevent them from voting. Don't know what the other admins will say though. - {{user|Edofenrir}}
 
Ah, I see, that doesn't sound good. Should I actually make a diff. proposal for each one though?[[User:ForeverDaisy09|FD09]]
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)
:Hm, yeah it makes sense...I'll vote tomorrow though, I'm pretty beat. I PWND my classmates in Brawl today. XD Different proposals won't be good because then this place would be cluttered and it's organized all right already. :/ {{User|Gamefreak75}}
::OK - I guess the all-in-one version works. Anyhow, how will this be archived? {{User|Marioguy1}}


I am Zero! Even though I oppose most of the sections, I just like to say this proposal is welled polished, confusing at first but it's polished really good. Zero signing out. {{User|Zero777}}
: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)
:OK, back to my question - will it be called a pass if even one of the sections passes or will it be a fail if one fails? Or will you put pass/fail for every single one of the sub-proposals? Maybe a big long thing like CHANGE SPECIES | DO NOT CHANGE HAIR COLOR... {{User|Marioguy1}}
::It'd probably be archived as pass/fail for each section, as if they were separate proposals. Leaving them together like the way it is now should be fine, though, seeing as they really are dealing with the same thing. Maybe the paragraphs pertaining to the specific changes could be moved down to the appropriate section (i.e. the reasoning behind changing the species listing would go under the "Species" header, before the voting sections). That would help with reading the proposal (the huge amount of text at the beginning is daunting), voting (one could easily forget the details by the time they make their way down to the later voting sections), and archiving (then what changes have passed or failed will be right besides the pass/fail announcement for that section). Other than that, I think it's a pretty good set-up. - {{User|Walkazo}}


Format looks great, IMO. FD09: May I have an example of what it would look like on one specific article? It's much easier to visualize when I can see exactly how it'll be. {{user|Bloc Partier}}
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.  


==Miscellaneous==
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)
===Add Shortcuts for Mario Kart Wii tracks===
My first proposal.
'''Add shortcuts to Mario Kart Wii tracks.'''<br/>
This will help struggling racers get the fast staff ghosts, or beat an annoying sibling's best time. <br/>Add more spots if necessary.


'''Proposer:''' {{User|lllkkklll}}<br>
: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)
'''Deadline:''' 20 November 2009, 20:00


====Add Shortcuts====
::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)
#{{user|lllkkklll}}  as per above, and for the people who can't find them on their own.
#{{User|Pie Shroom}} If nothing else, it's more encyclopedic.


====Don't add Shortcuts====
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|Super Mario Bros.}} Per Coincollector and FunkyK38's comments below.
#{{User|Edofenrir}} Ok, since the proposer didn't explain his/her intentions further, I have to conclude what it means. And judging from how the proposal is written, I think he/she wants to add mere tricks to get to the goal quickly, instead of built-in shortcuts. And as stated below, I oppose this.
#{{User|Zero777}} I am Zero! Like Funky said, were not a strategy wiki, and I think there are alrady shortcuts on some courses on MKWii, but only if there notable enough. Even though there is such thing as a spoiler section we don't want to spoil the player too much they end up as an ass on online play and are now roten and had to be thrown away (metaphor right there). Zero signing out.
#{{User|Gamefreak75}} Much easier to look up on YouTube. ;D And per Funky's and Coin's comments below.
#{{User|Dodoman}} The 'W' in 'SMW' stands for "Wiki," not "Walkthrough."
#{{User|Vini64}} Per Dodoman.
#{{User|T.c.w7468}} Per all. Shortcuts should be found elsewhere, not here.


====Comments====
: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)
What do you mean with shortcuts specificly? Are you talking about shortcuts implemented in the tracks (like secret tunnels) or just driving tricks that help you getting to the finish faster? I'd support the first and oppose the latter one. - {{User|Edofenrir}}
:Per Edo. Also, your reasoning makes it sound like you're trying to turn those articles into game guides. :/ -- {{User|Stooben Rooben}}
::Aren't shortcuts already [[Moo Moo Meadows|in]] [[Mushroom Gorge|some]] [[Toad's Factory|of]] [[Dry Dry Ruins (course)|the]] [[Maple Treeway|racecourse]] [[DK's Snowboard Cross|articles]]? {{User|Marioguy1}}
The tone of this proposal makes me to think like a joke (or a walkthrough issue, like explaining bug shortcuts or glitches, eg: the worst shortcut glitch of Grumble Volcano) and that's not a valid question to propose. {{user|Coincollector}}
:There's already mentioned shortcuts in articles. I think he's trying to say that he wants EVERY article with a shortcut-explanation guide. {{User|Vini64}}
::We don't really have to put those on there, this isn't a strategy Wiki, we're the Mario wiki. {{User|FunkyK38}}
:::This proposal is not described well enough for me to vote. Describe it better or I will not vote. {{User|Marioguy1}}
::::<s>Same here</s> {{User|Vini64}}


===Staff pages===
::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)


I've noticed how we have a bunch of separate articles on the staff of video games. I believe this is fine, but why do we need stand alone articles on the staff pages? Why not just move them to subpages of the games' articles, kinda like the [[Beta elements]] sub-pages? The only page they are linked from is the game anyways (the template doesn't count).
===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|Knife}}<br>
'''Proposer''': {{User|Pizza Master}}<br>
'''Deadline:''' 24 November 2009, 20:00
'''Deadline''': February 27, 2025, 23:59 GMT


====Support====  
====Support====
#{{User|Knife}} &ndash; Per proposal suggestion
#{{User|Pizza Master}} per.
#{{User|Time Q}}: There's no need for a stand-alone page. Making it a sub-page of the game article makes more sense. Per Knife.
#{{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|Edofenrir}} - This should actually go without saying, but of course we can't skip the proper channels...
#{{User|Camwoodstock}} Wait, theme changes are unavailable to users not logged in? Just, at all? It's not just dark mode, it's ''any'' theme, since it's all on Preferences. This feels like something that, if it's possible, it shouldn't even be a proposal, it should just be added outright without vote. This is a very obvious quality-of-life change for users that don't happen to be logged in.
#{{User|Vini64}} Per Knife.
#{{User|T.c.w7468}} Per Knife's proposal.
#{{User|Gamefreak75}} - Per all.
#{{User|Marioguy1}} - Sounds good :D
#{{User|Stooben Rooben}} - Per Knife.


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


====Comments====
====Comments====
Vini64: You seem to misunderstand the proposal. It's not about putting the staff information into the game articles themselves. Rather, they would go on a sub-page of the game articles (e.g. {{fakelink|Super Mario World/Staff}}), just like it's already done with the beta elements: [[Super Mario World/Beta elements]]. {{user|Time Q}}
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)
: Ohh, now I understood. Sorry about the misunderstanding. {{User|Vini64}}
::No problem! {{User|Time Q}}


<s>Vini64: It's not about merging those pages with the article, it's about making the standalone pages to subpages for organisatory meanings. That doesn't consume any room on the original article at all.</s> I was too slow, so, what Time Q just said. - {{User|Edofenrir}}
: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)
<!-- Please do not remove, archive or place comments below this message. -->
 
&nbsp;
==Miscellaneous==
''None at the moment.''

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

Image used as a banner for the Proposals page
Current time:
Friday, February 14th, 04:29 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)
Merge MC Ballyhoo and Big Top, Dive Rocket Launcher (ended February 13, 2025)

Writing guidelines

None at the moment.

New features

Introduce a new type of proposal

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

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

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

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

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

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

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

Support

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

Oppose

Comments on proposal proposal

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

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

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

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

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

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

Removals

None at the moment.

Changes

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

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

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

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

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

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

Merge civilizations, leave Hooroglyphs alone

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

Merge Hooroglyphs to Hoohoo civilization, leave civilizations alone

Merge none (do nothing)

Comments (Indus River Valley civilization joke here)

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

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

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

Support

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

Oppose

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

Comments

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

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

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

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

Split the image quality category

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

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

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

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

Split both

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

Only split screenshots

Only split assets

Leave image quality alone

Comments on image quality proposal

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

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

    Scan of 3D render, colors are washed out.

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

    Muddy scan of 2D illustration, and background cropped.

  • Photoshop upscaled 2D promo art.

    Photoshop upscaled 2D promo art.

  • Too small image of merchandise.

    Too small image of merchandise.

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

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

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

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

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

Support

  1. Kaptain Skurvy (talk) Per proposal.

Oppose

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

Comments

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Option 4: Do nothing

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

Comments

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

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

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

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

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

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

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

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

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

Make Dark Mode available to everyone

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

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

Support

  1. Pizza Master (talk) per.
  2. Nintendo101 (talk) nice idea, though I would prefer if Light Mode was called "Ground Mode" and Dark Mode was called "Underground Mode" for our site.
  3. Camwoodstock (talk) Wait, theme changes are unavailable to users not logged in? Just, at all? It's not just dark mode, it's any theme, since it's all on Preferences. This feels like something that, if it's possible, it shouldn't even be a proposal, it should just be added outright without vote. This is a very obvious quality-of-life change for users that don't happen to be logged in.

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.

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