MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
m (→‎Support: per all)
Tag: Mobile edit
 
Line 1: Line 1:
<center>[[File:Proposals.png]]</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'''.
#If users have 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 the other users, who will then vote about whether or not they think the idea should be used.
*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.  
#Each proposal ends at the end of the day ('''All times GMT.''')
*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.
#*For example, if a proposal is added on Monday, August 1, 2011, at 22:22 GMT, the voting starts immediately and the deadline is one week later on Tuesday, August 9, at 23:59 GMT.
**Abstaining from some options should be allowed too.
#Every vote should have a reason accompanying it. Agreeing with or seconding a previously mentioned reason given by another user is accepted.
*Each vote is subject to the same approval percentages as a regular old Support/Oppose proposal.
#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 at any time, but the final decision to remove another user's vote lies solely with the [[MarioWiki:Administrators|Administrators]].
*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?
#All proposals that end up in a tie will be extended for another week.
*Poll proposals must be clearly marked as such, to make it clear how one is supposed to vote.
#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, proposers can request that their proposal be deleted by an [[MarioWiki:Administrators|admin]] 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 an administrator, the proposer can ask for that help.
#There should not be proposals about creating articles on an 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 cannot be made about promotions and demotions. Users can only be promoted and demoted by the will of the [[MarioWiki:Administrators|Administration]].
#If the admins 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.


<h3 style="color:black">Basic Proposal and Support/Oppose Format</h3>
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".  
This is an example of what your proposal should look like, if you want it to be acknowledged. If you are inexperienced or unsure how to set up this format, simply copy the following and paste it into the fitting section. Then replace the [subject] - variables with information to customize your proposal, so it says what you wish. If you insert the information, be sure to <u>replace the whole variable including the squared brackets</u>, so "[insert info here]" becomes "This is the inserted information", not "[This is the inserted information]".
-----
<nowiki>===[insert a title for your Proposal here]===</nowiki><br>
<nowiki>[describe what issue this Proposal is about and what changes you think should be made to improve how the Wiki handles that issue]</nowiki>


<nowiki>'''Proposer''': {{User|[enter your username here]}}<br></nowiki><br>
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".
<nowiki>'''Deadline''': [insert a deadline here, 7 days after the proposal was created, at 23:59 GMT.]</nowiki>


<nowiki>====Support====</nowiki><br>
'''Proposer''': {{User|EvieMaybe}}<br>
<nowiki>#{{User|[enter your username here]}} [make a statement indicating that you support your proposal]</nowiki>
'''Deadline''': February 21, 2025, 23:59 GMT


<nowiki>====Oppose====</nowiki>
====Support====
#{{User|EvieMaybe}} Per proposal.
#{{User|RetroNintendo2008}} Mock-up looks pretty good! The more variety when it comes to how we make major decisions, the better.
#{{User|PopitTart}} For. Having templates as Camwoodstock suggests would also be good to make it easier to see at a glance how votes are distributed.
#{{User|Rykitu}} Neat idea, per all.
#{{User|Waluigi Time}} Per proposal, as long as the suggestion to have a better visual indicator for support/oppose votes is taken into account. I lean more towards Ahemtoday's suggestion since it'll be easier to keep count of them.
#{{User|ThePowerPlayer}} Per Waluigi Time.
#{{User|1468z}} Per all.
#{{User|Camwoodstock}} Per Waluigi Time and Ahtemtoday's suggestion; as long as tallying is made easier than the original example, we see no reason to not add these.
#{{User|Killer Moth}} Per all.
#{{User|Nintendo101}} Good idea for larger projects. Per proposal.
#{{User|Mushroom Head}}{{hide|show=For|hide=Per all.|shown=1}}


<nowiki>====Comments====</nowiki>
====Oppose====
-----
Users will now be able to vote on your Proposal, until the set deadline is reached. Remember, you are a user as well, so you can vote on your own Proposal just like the others.


To support, or oppose, just insert "<nowiki>#{{User|[add your username here]}}</nowiki> 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 just say "Per my Proposal".
====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)


__TOC__<!--
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)


<center><span style="font-size:200%">CURRENTLY: '''{{#time: H:i, d M Y}} (GMT)'''</span></center>
{{@|EvieMaybe}} How would you prevent two opposing options from both passing with this type of proposal? How would you prevent the scenario that both Waruiji and Waluigi had enough support to succeed? Would users be expected to vote "for" on one option and "against" on its opposing option? I'm just not understanding how this is helpful, honestly. --{{User:Pizza Master/sig}} 17:01, February 13, 2025 (EST)
:I do not want to put words in eviemaybe's mouth, but I assume if you had a proposal with only two or three types of outcome, you would not use this type of proposal structure. It would be here if you need it for larger proposals that aim to resolve several related issues all at once, rather than make individual proposals for each one. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 17:09, February 13, 2025 (EST)
:i feel like you misunderstand how i proposed it. Why put Waruiji and Waluigi in two options, when you can just make an option where if it passes, you use Waruiji, and if it doesn't, you use Waluigi? {{User:EvieMaybe/sig}} 18:21, February 13, 2025 (EST)


==Removals==
''None at the moment.''


==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]]


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


<h2 style="color:black">Talk Page Proposals</h2>
'''Proposer''': {{User|Camwoodstock}}<br>
All proposals dealing with a single article or a specific group of articles are held on the talk page of one of the articles in question. Proposals dealing with massive amounts of splits, merges or deletions across the Wiki should still be held on this page.
'''Deadline''': February 13, 2025, 23:59 GMT


:''For a list of all settled Talk Page Proposals, see [[:Category:Settled Talk Page Proposals|here]].''
====Merge all (merge Hoohoo/Soybean Civilizations to List, merge Hooroglyphs to the Hoohoo Civilization section)====
#{{User|Camwoodstock}} Per ourselves; these civilizations don't have as much plot relevance nor lore behind them as something like, say, [[Squirpina XIV]] or the [[Flora Kingdom royalty]], at most serving as the origin for [[Hoohooros]].


<h3 style="color:black">How To</h3>
====Merge civilizations, leave Hooroglyphs alone====
#All active talk page proposals must be listed below in chronological order (new proposals go at the bottom). All pages affected must be mentioned in the ''brief'' description, with the talk page housing the discussion linked to directly via "({{fakelink|Discuss}})". If the proposal involved a page that is not yet made, use {{tem|fakelink}} to communicate its title. The '''Deadline''' must also be included in the entry. Linking to pages not directly involved in the talk page proposal is not recommended, as it clutters the list with unnecessary links. Place {{tem|TPP}} under the heading.
#{{User|LinkTheLefty}} The glyphs are actually seen, though.
#All rules for talk page proposals are the same as mainspace proposals (see the "How To" section above), with the exceptions made by Rules 3 and 4 as follows:
#{{User|Jdtendo}} Per LinkTheLefty.
#Voting in talk page proposals will be open for two weeks, not one. ('''All times GMT.''')
#{{User|Nintendo101}} Per LinkTheLefty.
#*For example, if a proposal is added any time on Monday, August 1, 2011, it ends two weeks later on Monday, August 15, 2011, at 23:59 GMT.
#{{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.
#Talk page proposals may be closed by the proposer at any time if both the support ''and'' the oppose sides each have fewer than five votes.
#{{User|Power Flotzo}} Per all.
#The talk page proposal '''must''' pertain to the article it is posted on.


===List of Talk Page Proposals===
====Merge Hooroglyphs to Hoohoo civilization, leave civilizations alone====
*Merge [[Adventure Tours]] with [[Mario %26 Sonic at the Olympic Winter Games]] ([[Talk:Adventure Tours|Discuss]]) '''Passed'''
*Merge [[Co-Star Mode]] to [[Super Mario Galaxy]] and [[Super Mario Galaxy 2]] ([[Talk:Co-Star Mode|Discuss]]) '''Passed'''
*Merge [[Multi-Man Brawl]] to [[Super Smash Bros. Melee]] and [[Super Smash Bros. Brawl]] ([[Talk:Multi-Man Brawl|Discuss]]) '''Passed'''
*Merge [[Adventure Mode: The Subspace Emissary]] with [[Super Smash Bros. Brawl]] ([[Talk:Adventure Mode: The Subspace Emissary|Discuss]]) '''Passed'''
*Split then Merge Voice Cast and Music Staff, from [[Super Smash Bros. Brawl]], into the staff  sub-article ([[Talk:Super Smash Bros. Brawl#Merge|Discuss]]) '''Deadline''': May 1, 2011, 23:59 GMT
*Merge [[Double Dash!!]] to [[Rocket Start]] ([[Talk:Double Dash!!|Discuss]]) <s>'''Deadline''': April 29, 2011, 23:59 GMT</s> '''Extended''': May 6, 2011, 23:59 GMT
*Merge [[Kraid]] with [[Brinstar Depths]] ([[Talk:Kraid|Discuss]]) '''Deadline''': May 7, 2011, 23:59 GMT
*Split [[Pale Piranha]] from [[Piranha Plant]] and merge [[Piranha Plant (Paper Mario: The Thousand-Year Door)]] with [[Piranha Plant]] ([[Talk:Pale Piranha|Discuss]]) '''Deadline''': May 10, 2011, 23:59 (GMT)


==New Features==
====Merge none (do nothing)====
==Removals==
===Less Merging and Unmerge some merged Articles===


====Comments (Indus River Valley civilization joke here)====


===Rules===
===Include italics for category page titles for media that normally uses it===
*Do not merge or Propose to merge non-stub articles.Especially [[Enemies]]
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'']].
*Un-merge Previously merged non-stub articles such as [[Lava Bubble]] and [[Pale Piranha]]
*The 1st rule do not apply to Administrators
I think most of the time, Merging Hurts the Wiki. For Example, Merging [[Lava Bubble]] and [[Podoboo]]
deleted most of the information on Lava Bubble. I propose that there should be less suggestions of merging stuff, especially with good articles. Just because something looks similar or the "japanese names are the same" doesnt mean that one of the articles should be ruined.
(If merging prevents '''stubs''',then it is OK)


'''Proposer''': {{User|yoshiyoshiyoshi}}<br>
'''Proposer''': {{User|Kaptain Skurvy}}<br>'''Deadline''': February 20, 2025, 23:59 GMT
'''Deadline''': May 4, 2011, 23:59 GMT  


====Support====
====Support====
#{{User|yoshiyoshiyoshi}}Per My Proposal
#{{User|Kaptain Skurvy}} Per proposal.
#{{User|Holyromanemperortatan}} Per Proposal. Side note: if this will help the wiki by not having important info removed then sure.
#{{User|Camwoodstock}} Wait, this isn't already policy??? We think this lack of parity speaks a lot to how neglected categories can be in some regards. While yes, the category description isn't really meant to be the main point, we don't think ''slightly slanted text'' is distracting from the actual list of articles in the category, and just because categories are more utility than text doesn't excuse the text that ''is'' there looking below the standard of a usual article for being "lesser".
#{{User|Super Mario RPG}} Nothing wrong with having more consistency around the wiki.
#{{User|GuntherBayBeee}} Per all.
#{{User|Salmancer}} It is easier to figure out what the standards are from context alone when the standards are applied in every instance.


====Oppose====
====Oppose====
#{{User|Bop1996}} Per my comment. I don't see what this proposal is based off of, except one example where, if my memory serves, there was a good reason for merging.
#{{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|Goomba's Shoe15}} We already have a system for this it's called the talk page proposal
#{{User|Sparks}} Per Nintendo101. It doesn't feel necessary.
#{{User|Yoshiwaker}} Per my comment.
#{{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|Zero777}} You're taking away the common user's free speech and replacing it with a communism-esque replacement with this proposal. Also, it states in your proposal ''" I think most of the time, Merging Hurts the Wiki. For Example, Merging [[Lava Bubble]] and [[Podoboo]] deleted most of the information on Lava Bubble."'' So what do you think you should do, A) Report this to a staff in their talk page or chat OR B) Start editing the freaking article!! Don't just sit around and complain that some info was taken out of the article. Also I'm getting the feeling that you assumed what "stub" means.
#{{User|SolemnStormcloud}} Per all.
#{{User|Walkazo}} - Merging is not harmful if it's done right; perhaps mistakes ''are'' made sometimes, but they can be fixed with subsequent edits or new TPPs if re-splitting them is necessary. Merging is a case by case process: general statements like "merging hurts the wiki" or assumptions like non-stubs all deserve to stay is going completely against how the wiki is run; sometimes, larger articles just need to be merged - it's not based on size, but on content. Also, there is no good reason for limiting merge proposals to admins only: everyone should always be able to make suggestions and TPPs.
#{{User|Rykitu}} Per Nintendo101
#{{User|UltraMario3000}} Per Walkazo. *sniffle* Oh my, that was a beautiful speech. I loved it.;~;
#{{user|Xzelion}} Per Walkazo!
#{{User|Mario4Ever}} Per Walkazo.
#{{User|Nicke8}} Per Walkazo.
#{{User|Edofenrir}} - You cannot subdue suggestions, intended for the wiki's improvement, through a proposal. I won't stand for this.
#{{User|Reddragon19k}} - Leave it! Per Walkazo! I love this speech, it's so beautiful! I'm going to cry. (Crying in tears)
#{{User|Superfiremario}} Per my comments below.
#{{User|Phoenix}} Per everyone.
#{{User|Luigi is OSAM}} Per Walkazo. (Nice speech! It rocked) Since when does merdging HURT the WIki? It helps it!  Walkazo
#{{User|redyoshi911}} Per Walkazo
#{{User|Reversinator}} Per all.


====Comments====
====Comments====
first things first which articles are to be un-merged is that up to you or who is that going to be decided by also your starting time is wrong and so is your end time 
@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)
{{User|Goomba's Shoe15}}
: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)


We can't put a limit on how many things can be merged. If something needs to be merged, we have to merge it. {{User|Fawfulfury65}}
===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.


Plus isnt that why we have talk pages to determine whether or not we need an article {{User|Goomba's Shoe15}}
'''Proposer''': {{User|Waluigi Time}}<br>
'''Deadline''': February 20, 2025, 23:59 GMT


From what I understand, you want to make sure merging is a last resort because the articles we're merging are good? We merge articles for various reasons. Some of those reasons could be considered invalid today, but you can't put a limit on merging. Suppose someone makes lavish articles for all the trophies in the Super Smash Bros. series. If this proposal succeded, we wouldn't be able to merge them because it would merge too much and the articles are too good to merge, which, if you didn't realize yet, are not good reasons. {{User|Reversinator}}
====Split both====
#{{User|Waluigi Time}} Category:Votes to be reuploaded with a better reason
#{{User|Technetium}} Per proposal.
#{{User|Camwoodstock}} We're a little surprised a split like this hasn't happened sooner, honestly; if for no other reason than it would be nice to have it organized. Per proposal.
#{{User|ThePowerPlayer}} Per proposal.
#{{User|Nintendo101}} Per proposal.
#{{User|LadySophie17}} Per all, which is mostly "per proposal"s anyway
#{{User|EvieMaybe}} makes perfect sense


First of all, this proposal is vague. You do not specify which types of articles you want merged; instead, you make some vague reference to an article that is "good enough."
====Only split screenshots====


Second, you don't mention what type of limit is being enforced, only that one needs to be.
====Only split assets====


Third, sometimes merging is necessary. It's important to look at all the evidence and make a rational decision based off all the evidence.
====Leave image quality alone====


Fourth, what articles are you planning on un-merging?
====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)


All in all, I see no reason whatsoever to support this, or to even have it proposed... {{User|Bop1996}}
===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)]].


@bop1996 I plan on having articles such as [[Lava Bubble]] and [[Pale Piranha]] unmerged.Also,the [[Badge]] page needs to be broken up by game,or by badge.
'''Proposer''': {{User|Kaptain Skurvy}}<br>'''Deadline''': February 22, 2025, 23:59 GMT
I think Stubs still need to be merged though.
 
@Reversinator I think good articles should remain independent.but stubs should be merged together. {{user|yoshiyoshiyoshi}}
 
@Yoshiyoshiyoshi What constitutes a good article? As for Badges, a single comprehensive article is, in my opinion, more beneficial than a series of short ones. {{User|Mario4Ever}}
 
And you still haven't explained who get's to decide what articles get to be un-merged or why we need to change the system when we have talk pages for this
{{User|Goomba's Shoe15}}
 
@Yoshiyoshiyoshi Question what doesnt apply to Admins and another Question why not just make talk page proposals about this
{{User|Goomba's Shoe15}}
 
@goombasshoe Only Administrators get to make merging TTPs,but anyone can vote on them.And most of the Non-Stub articles that were previously merged get un-merged
{{User|yoshiyoshiyoshi}}
 
 
Then make a TPP if you want that. The badge page works very well with the current situation, no need to mess it up. If you think stubs need to be merged, then look at the power shot proposal below, in the comments. I.e. Marioguy's comment. Also, you still are using the ambiguous term "good article." {{User|Bop1996}}
 
and who gets to decide what get unmerged also why should admins be the only people to be able to make merging proposals
{{User|Goomba's Shoe15}}
 
This whole proposal is based on your opinion that merging is always bad. Basically, you are just trying to impose ''your'' will on the whole wiki. Also, I wholeheartedly agree with GS15. Just because some people are admins does not mean that they are the only people who can make good decisions regarding splitting and merging.{{User|Yoshiwaker}}
 
All of the Non-Stub Articles that were merged get un-merged.And I think Admins should only get to make Merging TTPs because it would make less unnecesary merging{{user|yoshiyoshiyoshi}}
 
@yoshiwalker Merging isnt always bad.I think that Meging things that dont need to be merged is though{{user|yoshiyoshiyoshi}}
 
If a proposal was made for an unnecessary merge, it would be opposed. As a reply to your second comment, you said yourself that "Merging hurts the wiki". {{User|Yoshiwaker}}
 
well i meant stuff like the Lava Bubbe thing.Read the talk on Lava bubble to know what i mean {{user|yoshiyoshiyoshi}}
 
all i see is that 13 people said yes and 5 said no which makes me believe they should be merged
{{User|Goomba's Shoe15}}
 
In japan,all magikoopas are called kamek.Does this mean kamek should be merged with magikoopa?i think not
 
'''@Holyromanemperortatan:''' That will actually hurt the wiki. {{User|Zero777}}
 
@Zero777  yeah prolly since it will cause confusion as to what articles should be merged and which ones shouldnt
{{User|Goomba's Shoe15}}
 
What are you trying to say?! This proposal is way to vauge. {{User|Superfiremario}}
 
:@Yoshiyoshiyoshi - On the contrary, merging is often used to ''help'' the Wiki, not to hurt it; we wouldn't be merging as many things as we do as often as we merge them if it wasn't completely necessary. Any merges that are unnecessary are usually obvious and will most likely not be enacted anyway, so this proposal is kind of pointless... {{User|Phoenix}} 19:07, 28 April 2011 (EDT)
 
==Changes==
 
===Merge the special shots of Mario Power Tennis (Gamecube) into one article===
This situation is just like the Super Strikes from Mario Smash Football. All the power shots don't need their own articles, they just creat stubs.
 
'''Proposer''': {{User|Tails777}}<br>
'''Deadline''': <s>April 23, 2011</s> '''Extended''': April 30, 2011, 23:59 GMT<br>


====Support====
====Support====
#{{User|Tails777}} Per me.
#{{User|Kaptain Skurvy}} Per proposal.
#{{User|SWFlash}} <s>First!</s> Per proposal.
#{{User|Zero777}} They are not stubs, but per my reason in the Super Strike Merge proposal.
#{{User|Reddragon19k}} Per all and myself! If the Super Strikes are merged, so does this!
#{{User|Joeypmario}}Per all.
#{{User|Doopliss101}} Per all
#{{User|Superfiremario}} Per comments.
#{{User|Al24136}} There should be one page that discusses all of the character's power shots.


====Oppose====
====Oppose====
#{{User|DK and Diddy Kong vs Bowser and Bowser Jr.}} Comparing differences between two Power Shots gives a bigger difference than comparing two Super Strikes/Mega Strikes to each other. So for example, [[Koopa Troopa]]'s [[Water Bomb]] is '''always''' a drop shot and it slows the opponent down, while [[Koopa Paratroopa]]'s [[Energy Ball]] is '''always''' a lob shot and it spins the opponent around. Besides, there are 14 characters in [[Mario Power Tennis (Nintendo GameCube)|Mario Power Tennis]], and each character has '''both''' an offensive power shot and a defensive power shot. That would merge 28 shots into one article. The difference between [[Super Strike]]s and [[Mega Strike]]s are just aesthetic, they're no different to each other besides the way they look. This is why they were merged.
#{{User|Nintendo101}} Those articles also cover the game's release on Famicom, NES, Atari, etc., so "arcade" would not be a holistically accurate identifier.
#{{User|Goomba's Shoe15}} Per all
#{{User|Camwoodstock}} Per Nintendo101; "arcade" is kind of a misnomer when the non-arcade ports are covered on them.
#{{User|Nicke8}} Per all.
#{{User|ThePowerPlayer}} Per Nintendo101.
#{{User|UltraMario3000}} Per all.
#{{User|PaperSplash}} Per ThePowerPlayer's comment.
#{{User|MeritC}} Per all.
#{{User|Rykitu}} Per all
#{{User|Mario4Ever}} Per the user with the ridiculously long username.
#{{User|Luigi is OSAM}} Per DK and Diddy Kong vs Bowser and Bowser Jr.
#{{User|DKPetey99}} Per DK and DK vs B and BJ
#{{User|Kaptain K. Rool}} - Because.... theat clutters the articles together and makes it look bad.
#{{User|MarioMaster15}} Per all.
#{{User|Bop1996}} Per first opposer.
#{{User|Reversinator}} Per all.


====Comments====
====Comments====
The dates were all wrong. Voting start is a day after the proposal was made, which means it starts on the 16th, not the 15th; you also forgot to convert the time from EST to GMT (or incorrectly converted from some other time zone). And finally, mainspace proposals only go for one week, so this ends on the 23rd, not the 29th. How to format these dates and times is clearly explained in Rule 2: I encourage everyone to read it before making proposals. - {{User|Walkazo}}
Maybe "arcade game" would be a decent compromise? [[User:PaperSplash|PaperSplash]] ([[User talk:PaperSplash|talk]]) 18:02, February 8, 2025 (EST)


I hate when I have to say this, but '''a stub is not a short article'''. A stub is an article that, regardless of length, lacks information. If a short article does have all its information, it is not a stub. Get it right, people. {{User|Reversinator}}
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)
:I seriously have to get a hammer and pound that sentence into people's heads >_>
::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)


:A long time ago, we thought that all stubs were bad. We decided to merge all stubs into bigger articles; thinking that it would be great and we'd have no stubs. You know what resulted? Stuff like [[Gnat Attack#Watinga|this]]. Seriously, a boss of a game is merged into the game that it appears in! If the Shadow Queen article was a stub, would we merge that into PM:TTYD? I mean, honestly, sometimes stubs can be tolerated, but if you go overboard and constantly think "stubs = death" then you are bound to make [[Gnat Attack|mistakes]]. {{User|Marioguy1}}
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)


::Well sorry, I just don't understand these things, I didn't know what stub means and I only say it on small articles/short sections of articles so I assumed they were small articles. {{User|Tails777}}
===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.


I don't find this to be useful. If this proposal passes, what will happen to [[Bowser#Fire Breath|Fire Breath]]? It appears in Smash Bros. as well. {{User|DK and Diddy Kong vs Bowser and Bowser Jr.}}
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.


@DK and Diddy Kong vs Bowser and Bowser Jr.: If Fire Breath appears in Smash Bros Brawl, it would be in Bowser's article. All characters special attacks are on their own articles. {{User|Tails777}}
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.


@Tails777 Fire Breath has it's [[Fire Breath|own article]]. Besides, every Power Shot is different enough. {{User|DK and Diddy Kong vs Bowser and Bowser Jr.}}
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?


===Merge all of [[Wario|Wario's]] Transformations Into one Article===
'''Proposer''': {{User|PaperSplash}}<br>
This is similar to King Koopa's alter egos. I'm not talking about [[Tiny Wario]] and those transformations from the ''[[Wario Land]]'' series. I'm talking about transformations from ''[[Wario: Master of Disguise]]'' such as [[Thief Wario]] and [[Sparky Wario]]. Like the page, [[King Koopa's alter egos]], I think we should make a page called "Wario's Transformations" or just merge them to [[Wario]], or keep them. Three options I'll make. <br>
'''Deadline''': February 23, 2025, 23:59 GMT


'''Proposer''': {{User|DKPetey99}}<br>
====Option 1: List largely identical American English localizations only as "English (United States)"====
'''Deadline''': May 6, 2011 23:59 GMT
#{{User|PaperSplash}} My third choice. I mean, when it really is just American English, I can see the argument.


====Merge to Wario's Transformations====
====Option 2: List largely identical American English localizations as simply "English"====
#{{User|DKPetey99}} I think it will be better to make one article instead of the 8 disguises he has.
#{{User|PaperSplash}} My first choice. I think it's the best compromise that makes the most sense, all things considered.
#{{User|Hewer}} I feel like this way is the most straightforward and accurate.
#{{User|CarlosYoshiBoi}} I mean, if it’s just the same thing and no changes (assuming it doesn’t include dates for save files), then I guess this one makes the most sense.
#{{User|Camwoodstock}} Primary option. It's the simplest, it seems reasonable enough, and is applicable across the board; while it isn't exactly in-line with how Nintendo is handling things as of the Switch era, it's reasonable ''enough'' and can easily account for pre-Switch cases very well.
#{{User|Jdtendo}} Per all. Especially if that means that we will stop using "English (United States)" for games that use a variety of English that is not specifically American and weren't even released in America such as ''[[Super Mario Bros.: The Lost Levels|SMBTLL]]'' or ''[[Mario & Wario]]''.


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


====Keep it the Same====
====Option 4: Do nothing====
#{{User|Zero777}} Per Reversinator.
#{{User|CarlosYoshiBoi}} I’m actually surprised no one put anything in this option kind of like the title mentions “Do nothing.”
#{{user|SWFlash}} Transformations and power shots are ''not'' the same! They should be splitted.
#{{User|Bop1996}} Per Reversinator... Trying to add something on.. can't think of anything to add to that.
#{{User|Goomba's Shoe15}} Per Revrsinator nothing left to add
#{{User|Tom The Atum}} I mean, I don't know if there is a Mario Transformations article, and Wario isn't as "important" as Mario, no offense to Wario worshipers.
#{{User|Mario4Ever}} Per those who per Reversinator.
#{{User|Superfiremario}} Per Reversinator's comments.
#{{User|Luigi is OSAM}} Per Tom The Atum and Reversinator
#{{User|Reversinator}} Per myself.
#{{User|Nicke8}} Per everyone.
#{{User|Arend}} Per Reversinator. Plus the fact that a lot of Wario's power-ups are Transformations. People get confused and will merge every single Transformation to that page that [the proposer] wants to create, while he only wants to merge the ones from ''Wario: Master of Disguise''.
#{{User|Reddragon19k}} - Leave it the way as it is! Per all!
#{{User|Walkazo}} - Per Reversinator's comment.
#{{User|UltraMario3000}} Per the dark Kirby.


====Comments====
====Comments====
The reason I proposed to merge King Koopa's alter egos was because it was literally just King Koopa in a costume. This costume didn't grant him any special powers or anything even similar to that, so they got merged. These forms, on the other hand, all have distinct powers, like [[Fire Mario]], [[Metal Mario (form)|Metal Mario]], or [[Ice Mario]]. Also like those forms, these powers are obtained by obtaining a specific item. Yes, you can choose that power from anywhere after getting the item, but that doesn't make them any different than the other powers. Also, can you give a reason as to why you want them merged? Simply that they are similar to the alter egos of King Koopa, which is not true as I explained, is not a substantial reason. Bottom line, they should be kept separate. {{User|Reversinator}}
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)
 
==Miscellaneous==
===Blocked Users' Votes===
Ach, headache. A headache is whatever I get when there is something on the wiki that does not fall under any policies. In this case, that thing would be the votes pertaining to blocked users. In the past, I have seen blocked users with their votes removed for being blocked, they have kept their votes there, I've even seen several times where the procedure was changed depending on the length of the block. I'm here to set something in stone about blocked users; specifically, how their votes are treated.
 
Now I have several options that I would consider accurate so let me explain them all:
 
#All blocked users' votes are removed; no matter the length of the block.
#All permanently blocked users' votes are removed, but if a user's block expires before the end of the proposal, their vote remains.
#All permanently blocked users' votes are removed, but if a user's block expires <u>two or more days before</u> the end of the proposal, then their vote remains.


All three options have their pros and cons; the first option will simplify things greatly, but it will unfairly treat users who are blocked for (hypothetically) one day. The second option will fairly treat everyone, isn't too complicated, but if a user is unblocked an hour before the proposal ends, will they really have time to change their vote (if they want to change it)?
: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)


Finally the third point covers all possible problems and fairly treats all users, but it is very complicated. It depends what kind of balance we want.
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)


'''Proposer:''' {{User|Marioguy1}}<br>
: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)
'''Deadline:''' May 5, 2011 (23:59 GMT)


====Option 1====
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.  
#{{User|Mario4Ever}} If a user has committed an offense that results in his or her being blocked, I see no reason for said user's votes to remain on proposals under any circumstances (except for ones that pass/fail prior to the blocking). In the user's absence, he or she is unable to communicate with other users, so any issues brought up during the time the user is blocked until his or her return can't be addressed. Even if the user's block expires before a proposal passes/fails, I do not believe the user should have the privilege to re-add/change his or her vote.
#{{User|Zero777}} They chose to break the rules and that will not be tolerated, per my comment, why should we make it convenient for punished users? Even if the user was blocked for less then seven days, I don't see what's the big deal on just putting back your vote.
#{{User|Mario304}} Per all. If a user is blocked, then he can't vote on proposals. That can serve as punishment for the blocked user.
#{{User|ThirdMarioBro}} If a user is bad enough to get blocked, chances are that the user does not have a reasonable vote.


====Option 2====
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)
#{{User|Marioguy1}} - I think this option represents an accurate balance between the other two; and the chance of the blocked user being blocked until right before a proposal passes AND THEN wanting to change their vote are very minimal.
#{{User|Yoshiwaker}} - Per MG1.
#{{User|LeftyGreenMario}} There is really no point to remove a user's vote if his or her blocktime expires before his or her proposal's deadline. If the user gets unblocked, he or she will just vote again. I will support, but I hope to see a rule added regarding a user getting blocked in an old FA nomination that is about to die.
#{{User|New Super Mario}} Per MG1
#{{User|Al24136}} Well, if somebody unintentionally causes harm to this wiki and gets a minor-scale block, I see no reason in removing their votes. That just seems a bit unjustified, and could alter the success of the proposal, which wouldn't be fair toward the proposer.
#{{user|SWFlash}} Per MG1.
#{{User|DK and Diddy Kong vs Bowser and Bowser Jr.}} Per LGM.
#{{User|Superfiremario}} Per all.
#{{User|Luigi is OSAM}} Per all
#{{User|redyoshi911}} Per all
#{{User|UltraMario3000}} Per all.
#{{User|Reddragon19k}} - Per all!
#{{User|Nicke8}} Per all above me.
#{{User|PoisonMushroom}} Agree with the option entirely
#{{User|Mariomario64}} Per all. (Ignore my comment below)


====Option 3====
: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)


====Do not delete vote====
::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)


====Comments====
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)
If anybody has any suggestions for options 4 and 5, I'd be glad to add them in any time in the next three days. {{User|Marioguy1}}


:I respect what you're proposing here, but what I think you would need to do is to to set procedures in stone depending on the length of the block, and then go from there, if you know what I mean. So, for instance:
: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)


*24 hour block = Vote is not removed.
::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)
*24 hour block - 1 week block = Vote is not removed ''unless'' block expires after proposal ends.
*1 week block and higher = Vote is removed.
*Infinite block = Vote is always removed under any circumstances (unless for some reason the user's block expires while the proposal is still active, but again, this would have to be in accordance with the "24 hour block - 1 week block" policy).


This isn't a perfect procedure by any means, but food for thought at any rate, right? {{User|Phoenix}} 18:28, 27 April 2011 (EDT)
===Make Dark Mode available to everyone===
::But if we have a TPP which just begun and then a voter is blocked for one week, one week later the TPP will only be half-done and his vote will have been removed. That seems like a big waste of time; my way, his vote won't be removed unless his block is obviously going to exceed the ending of the proposal. {{User|Marioguy1}}
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.


:::"...one week later the TPP will only be half-done and his vote will have been removed." Well, yes, but I said that in the case of a block lasting for 1 week, the vote is not removed unless the block expires ''after'' the proposal ends. Since the block, in this case at least, will expire within the time limit of the proposal (TPP), then it should be fine, because by the time the proposal ends, the user will be unblocked, and will regain their credability as a legitimate voter... {{User|Phoenix}} 18:51, 27 April 2011 (EDT)
'''Proposer''': {{User|Pizza Master}}<br>
 
'''Deadline''': February 27, 2025, 23:59 GMT
We should also take other circumstances into consideration, such as the reason for the user's block. For example, if the user was banned for sockpuppeting or vandalism, his/her vote will probably be removed, but if the user was banned for editing a page multiple times, his/her vote probably won't be removed. {{User|ThirdMarioBro}}
 
:Well, okay, but if we do that, then are we going to take those factors into consideration in conjunction with the length of the block, or independent of the block length...? {{User|Phoenix}} 19:02, 27 April 2011 (EDT)
:@Phoenix: So what you're saying is that a user who's block is over one week long yet still expires during the voting period would have to re-add their vote? Wouldn't that just be redundant?
 
:@ThirdMarioBro: Not really, a block is a block, if  user is blocked for three weeks for sockpuppeting then their vote is invalid; they have no ability to change the vote or remove it. The same goes for a block of the same length but for editing multiple times (which is not a blockable offense). {{User|Marioguy1}}
 
I really believe that the first option should be chosen because I'm the kind of person who expects people to follow the rules or else they'll have to face the consequences, since staff unofficially and officially warn users of their actions on not to do them, they get the consequence of not following directions. {{User|Zero777}}
:Actually Zero, you have a point there...I just might change my vote to that...if a user did something wrong, anything worthy of a block, why should we care about making things convenient for them? {{User|Marioguy1}}
 
I have a suggestion; instead of doing anything above, we could wait until the ''end'' of the proposal. Then, we could check each user to see whether they are blocked and remove blocked users' votes then. {{User|Mariomario64}}
 
What about blocked user's proposals? Will they be deleted or kept? {{user|SWFlash}}
:Deleted. Rule 10 states that the proposer must take action as soon as their proposal passes: they can't do that if they're blocked. They also can't participate in the discussions and address users' concerns during the proposal, which is not good. - {{User|Walkazo}}
::What about 24-hour ban? {{user|SWFlash}}
 
What happens if a user made an FA nomination that didn't get edited for nearly a month, and got blocked? This would unnecessarily "bump" the nomination. I think you should add a rule. Something like, "Within x days in an FA nomination, if users get blocked, their vote will remain until somebody bumps the nomination." {{User|LeftyGreenMario}}
 
'''@LGM''' We could have a notice placed on the user's talk page upon his/her return with something along the lines of "''Due to your recent blocking, you have lost the privilege to vote on the '''insert name''' proposal. Thank you for your consideration''," couldn't we? {{User|Mario4Ever}}
 
'''@AI21436''': Blocks are never given for unintentional actions that harm the wiki. Generally, people get reminders and are only blocked if the action continues deliberately. {{User|Mario4Ever}}
:@Mario4Ever: 24-hour bans are given out whenever a user is being a blockhead and won't listen but isn't necessarily hurting anybody. {{User|Marioguy1}}
::Are users who act as blockheads doing so unintentionally? {{User|Mario4Ever}}
:::Why should users who can't follow the rules be allowed to help us make them? {{User|Xzelion}}
::::@Xzelion: That's very good logic, and I honestly do not oppose it, options 1 and 2 both look appetizing to me, but I am obliged by my contract to play the devil and annoy the hell out of that logic. So imagine this scenario: a new user who does not know the first thing about sentence formation. Does not capitalize words, does not use proper punctuation/spelling/spacing/etc. - this user is told to stop making spelling mistakes and to double-check his work. But he is really bad at English so he continues messing up. Eventually he is given a day-long block for ignoring warnings and refusing to listen to admins. Would this user's vote be removed? Because he couldn't speak proper English, his votes are now invalid? I agree that in this scenario a block might seem a bit unfair; but think of other scenarios, like a user who continuously adds information that he believes is true, but it isn't and he is blocked for that. You, and Mario4Ever, are looking at one side of things; the malicious/intentional crimes that are committed where the user ''wants'' to do bad. But there's the other side too, where they can't help but do something bad. Is a user's inadequacy at something really an accurate measurement of their worth? So if a user can't spell properly, do we remove their rights for it? These questions are not rhetorical; they are for everybody to answer in their own opinion. Like I said, I'm playing the devil, how you see my performance is based on you. I am not stating my opinion anywhere in this post. {{User|Marioguy1}}
:In those situations, the harm to the wiki is unintentional on the user's part, and in my opinion, actions done unintentionally should get reminders, not get blocked. If someone is bad at English, it's not a big deal in this case for someone proficient in the language to fix whatever mistakes there may be as a result of this inadequacy. One's inadequacy is not a measure of one's worth. Rather, a user's worth should be determined by his or her intent. If there is any doubt as to what the user's intent may be in a given situation, it should be brought up on his/her talk page before giving out reminders, warnings, etc. {{User|Mario4Ever}}
::I think that's pretty accurate... I don't think people usually get blocked for grammar mistakes, but I have seen a bunch of reminders and warnings because of minor things like that. If someone is blocked, it probably means they sockpuppeted or vandalised or behaved poorly in language... That being said, however, I have not been around terribly long, and it's possible that someone has been blocked for those types of things. {{User|Bop1996}}
:::So what you guys are saying is that we should continue just reminding and warning them, wasting our time correcting their errors when they could just as easily re-read their work to make sure it's right? There are tons of ways that one could use their time and effort to fix spelling/grammar problems but the user in question is choosing to make us use our time and effort to do it. And all we are going to do about it is use even more time and effort to give them countless reminders? There eventually has to be a block. But their intents weren't bad. But they still got blocked. {{User|Marioguy1}}
::::No, I don't think there should be a continuous cycle of reminders and warnings, but you said yourself (or rather, the devil's advocate did, since you're not giving your opinion), that blocking someone for ignoring warnings given because of his/her inadequacy in English seemed a bit unfair. We have no way of knowing if this inadequacy is due to the user's age or if the user is a relatively new speaker of English and therefore does not have a grasp of basic grammatical structure. Either way, blocking the user isn't going to rectify the problem; a user can't improve his or her proficiency in English if he or she doesn't know how. As imposing age limits would be an impractical way of doing things, perhaps something could be added to the registration process (like a sentence to type or something) to avoid having a problem like this altogether. {{User|Mario4Ever}}
 
'''@ThirdMarioBro:''' Your vote is invalid, what the heck are you trying to say? You don't get blocked from having a bad reasoning on your vote! {{User|Zero777}}
: I believe this user is saying that the user getting blocked probably doesn't have a good reason in the vote anyway; I think that is a bad assumption. People like KS3 have mostly good intentions, for instance, and he is (still?) blocked.{{User|LeftyGreenMario}}
 
::Again, my question was, sorry, the person who responded to me, you didn't understand, that we have to bump a nomination for an FA to delete the blocked user's vote. If the FA is very old, is deleting a blocked user's vote considered necessary?{{User|LeftyGreenMario}}
:::If you're referring to me, I wasn't addressing FAs in my reply. I was addressing your vote (''There is really no point to remove a user's vote if his or her blocktime expires before his or her proposal's deadline. If the user gets unblocked, he or she will just vote again''). Anyway, concerning FAs, I think that if an article is featured or unfeatured in part because of a blocked user's vote, I think that vote should be removed because the featuring/unfeaturing of the article is then unfair. Why should a blocked user's vote have equal merit (or any at all) to that of a non-blocked user in the period of time that a block is in effect? {{User|Mario4Ever}}
 
===Allow users to revert edits made on archives===
I've being noticing that users edit on archives sometimes. I propose that we can revert edits made by them.
 
Now you guys might be like "Don't change the rule", "Archives are supposed to be a history of the past" or "Let sysops do it instead". But what if a vandal vandalizes a talk page archive? You can ask sysops to do it and block the vandal, but what if none of them are online? And what will we do to a vandalized talk archive? Besides, many autoconfirmed users can be trusted to be given the ability. You can be trust [[User:DK and Diddy Kong vs Bowser and Bowser Jr.|me]], [[User:Superfiremario|He]] can be trusted, [[User:Yoshiwaker|he]] can be trusted, etc. You can counter that with "Just protect every archive", but again, that requires sysops. Besides, I've seen [[User:UltraMario3000|this guy]] and [[User:Porplemontage|Steve]] do it as well in [http://www.mariowiki.com/index.php?title=User_talk%3ALindsay151%2FArchive_3&action=historysubmit&diff=1002862&oldid=1002861 this archive] and [http://www.mariowiki.com/index.php?title=User_talk:Supremo78/Archive_1&diff=prev&oldid=929711 this one].
 
'''Proposer''': {{User|DK and Diddy Kong vs Bowser and Bowser Jr.}}<br>
'''Deadline''': May 6, 2011 23:59 GMT.
 
====Let everybody revert edits on archives====
#{{User|DK and Diddy Kong vs Bowser and Bowser Jr.}} Per proposal.
#{{User|Pokémon Trainer Mario}} Per the guy who copied my sig.
#{{User|Superfiremario}} Per proposal.
 
====Only revert vandalizing====
#{{User|Luigi is OSAM}} Because there's really no need to revert edits other then vandalism
#{{user|Tom The Atum}} Yeah, and added on spam, if that doesn't count as vandalism.
 
====Protect every talk page archive====
#{{user|SWFlash}} Because protect every talk page archive. We won't need any edits to be made on archives anyway, so why do we need them unprotected?
#{{User|Zero777}} Even if there was a mistake on it, it's an archive and archives are records and history to learn from them, we can't learn from archive/history if they've been altered to be perfect. Also, your logic on that has a few holes in it, Edo has a sleeping disorder and is online on unusual times for any user to be on, so there will always be a sysop online, and you made it sound like all the sysops are on and offline at the same time. Also, that point you made with Steve, he is the creator of the wiki!
#{{User|Nicke8}} Per all.
 
====Make no changes====
#{{User|Mario4Ever}} Everyone can already go to history and undo any unneeded edit. I don't think this proposal is necessary. Besides, when people revert edits on archives, they're making sure that the conversations therein remain as they were at their conclusions, as per the rules.
#{{User|LeftyGreenMario}} I can handle vandalism in my archives myself. I don't think Sysops need even more work to protect talk page archives of users.
#{{User|Goomba's Shoe15}} Per LGM
 
====Comments====
@Mario4ever I didn't know that. I made it because I got [[User talk:DK and Diddy Kong vs Bowser and Bowser Jr./Archive 3#Warning|a warning]] for reverting edits made on archives, so I thought you couldn't do so. I will still keep this proposal up to tell [[User:DKPetey99|these]] [[User:Lindsay151|two]] that you CAN revert edits. {{User|DK and Diddy Kong vs Bowser and Bowser Jr.}}
:I must mention that this ability only extends as far as the main archive. No user except the user who archived it can edit a particular user's talk page unless he or she is a sysop. Honestly, if a talk page archive other than yours is edited, you can let the user know on his/her current talk page, and he or she can fix it. {{User|Mario4Ever}}
 
I'm pretty sure you are allowed to undo an edit on an archive, as long as the edit you are undoing is an edit that was not there when the archive was first created. {{User|Fawfulfury65}}
 
So can I remove the warning? It's sounds like it's invalid. {{User|DK and Diddy Kong vs Bowser and Bowser Jr.}}
:There is no stone-set policy in editing archives. There's just a general "don't do it"; which is enforced on a case-by-case basis. If you are reverting vandalism in archives, chances are any warnings will be declared invalid. If you're fixing spelling however... {{User|Marioguy1}}
::Why is it imperative that you fix archives? Just contact an admin to do it, and if you're concerned about unnecessary warnings or reminders, don't worry. We're working on that. {{User|Xzelion}}
 
:::"You can ask sysops to do it and block the vandal, but what if none of them are online?" Really? I highly doubt that ''every'' sysop will be offline for such a huge period of time that the edits cannot be reverted. Also, I'm sure it would not be so serious that it couldn't wait until a sysop was online to be reverted. {{User|Phoenix}} 01:22, 30 April 2011 (EDT)
Really Zero? Really? You're all gung ho about giving users the chance to do what they want in every other proposal; but in this one we're forcing them to protect their talk pages? Nice. {{User|Marioguy1}}
 
===Talk Page Proposal===
I have noticed that talk page messages are basically the only edits in the Recent Changes. I now have a rule that will restrict the amount of talk edits you may have. Like user, if you have over 30% of your edits on talk pages, with the exception of users with under 250 edits total, your talk page will be protected and you will be warned by an administrator to not leave messages on other user's talk pages. First offense will result in a one hour block. Next offense one day. Third offense one week. Any further shall be decided by administration. This is so there will be more main edits. I myself have lots of talk edits, and I am trying to edit the mainspace more. '''Update:With the forums, even if you don't have an e-mail like me, this rule still applies. If you are a talker, and you don't have e-mail, well too bad and sorry.'''
 
'''Proposer:''' {{User|Tom The Atum}}<br>
'''Deadline:''' May 7, 2011 (23:59 GMT)


====Support====
====Support====
#{{User|Marioguy1}} - Like I said in the comment section, if a user has only 3,000 edits and already has over 1,000 on user talk pages then we have a problem. I have 9,000 edits and just barely over 1,000 on user talk pages. RAP (the user with the most contributions on the wiki) has 1009 edits on user talks. So I find it a really big problem when a user with only 3,000 contributions has over 1,000 on user talk pages while a user with 27,000 contributions only has 1,009.
#{{User|Pizza Master}} per.
#{{User|Goomba's Shoe15}} - A user should have to be productive when some one has over 1000 edits and 6% are main space despite countless User Space warnings something has to be there to back up the warning
#{{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|Mario4Ever}} Per Marioguy1.
#{{User|Camwoodstock}} Wait, theme changes are unavailable to users not logged in? Just, at all? It's not just dark mode, it's ''any'' theme, since it's all on Preferences. This feels like something that, if it's possible, it shouldn't even be a proposal, it should just be added outright without vote. This is a very obvious quality-of-life change for users that don't happen to be logged in.
#{{User|Mushroom Head}}Why do we still need to create an account just to not torture your eyes when we use this wiki at night? It literally has zero effect to the users who are always logged in anyways.


====Oppose====
====Oppose====
#{{User|Zero777}} Again, it is taking away a user's freedom. We need to communicate and collaborate with each other to make the wiki better, we're not going anywhere if we have to contribute to the wiki alone.
#{{User|Superfiremario}} Per Zero.


====Comments====
====Comments====
I totally understand what you're saying, but I really don't think a set guideline is necessary. Whenever we want to check up on users who edit their user page too much, we just look at [http://www.mariowiki.com/index.php?namespace=2&title=Special%3ARecentChanges this page]. Our current user page protection length is 2 weeks after being warned, though this may be subject extended length depending how severe the offense is (so don't create 50 user sub-pages).--{{User|Knife}} 18:42, 30 April 2011 (EDT)
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)


So would this proposal actually make User space warnings mean something
: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)
{{User|Goomba's Shoe15}}


Goomba:it will hopefully get some users to make more main edits. {{User|Tom The Atum}}
==Miscellaneous==
 
''None at the moment.''
What talk pages are you talking about? Are you talking about Mainspace or User's? {{User|Zero777}}
 
 
Zero: user talk. {{User|Tom The Atum}}
:I believe he's talking about the massive amount of edits going on with user talk pages (people asking to be friends, those "shops", one user just started some sort of club where he gives out items every week). Those kinds of edits are all on talk pages and they can pile up. And frankly, when a user has only 3,000 edits and they already have over 1,000 on user talk pages (that's around 30%) then we really have a problem. {{User|Marioguy1}}
::So I suggest better to make a policy on archiving user talks after a limit is reached. {{User|Zero777}}
::@Zero: This is not removing people's freedom to express themselves; it's removing their freedom to treat this website like it's facebook. They can still make edits on talk pages, just they can't clog up the entire wiki with those messages. I'd also suggest the forum to those users who can't bear to not talk to eachother. And archiving user talk pages won't help.
 
::Also, @Knife: Protecting user talk pages is never a good idea. {{User|Marioguy1}}
 
@Superfiremario no way would you oppose what with having 6% main space out of 1000 edits despite like 6 warnings that's ridiculous dude so no way would you oppose a proposal that would make you actually do mainspace edits
{{User|Goomba's Shoe15}}
 
@Goomba:Yeah, he needs to be warned more. I have included a warning when I told him my Mario Kart code, and he just responded with an okay, without a saying[I will try to make more main edits]. {{User|Tom The Atum}}

Latest revision as of 07:17, February 14, 2025

Image used as a banner for the Proposals page
Current time:
Friday, February 14th, 12:17 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.
  11. Mushroom Head (talk)

Oppose

Comments on proposal proposal

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

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

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

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

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

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

Removals

None at the moment.

Changes

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

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

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

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

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

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

Merge civilizations, leave Hooroglyphs alone

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

Merge Hooroglyphs to Hoohoo civilization, leave civilizations alone

Merge none (do nothing)

Comments (Indus River Valley civilization joke here)

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

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

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

Support

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

Oppose

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

Comments

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

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

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

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

Split the image quality category

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

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

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

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

Split both

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

Only split screenshots

Only split assets

Leave image quality alone

Comments on image quality proposal

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

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

    Scan of 3D render, colors are washed out.

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

    Muddy scan of 2D illustration, and background cropped.

  • Photoshop upscaled 2D promo art.

    Photoshop upscaled 2D promo art.

  • Too small image of merchandise.

    Too small image of merchandise.

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

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

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

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

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

Support

  1. Kaptain Skurvy (talk) Per proposal.

Oppose

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

Comments

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Option 4: Do nothing

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

Comments

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

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

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

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

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

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

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

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

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

Make Dark Mode available to everyone

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

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

Support

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

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