MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
No edit summary
 
(999 intermediate revisions by more than 100 users not shown)
Line 1: Line 1:
<table style="background:#fefffe;color:black;-moz-border-radius:8px;border:2px solid black;padding:4px" width=100%><tr><td>
{{/Header}}
<div class="proposal">
<center>http://img33.picoodle.com/img/img33/9/9/17/f_propcopym_9045f2d.png</center>
<br clear="all">
{| align="center" style="width: 85%; background-color: #f1f1de; border: 2px solid #996; padding: 5px; color:black"
|'''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>. '''Signing with the signature code <nowiki>~~~(~)</nowiki> is not allowed''' due to technical issues.


<h2 style="color:black">How To</h2>
==Writing guidelines==
#Actions that users feel are appropriate to have community approval first can be added by anyone, but they must have a strong argument.
===Consider Super Smash Bros. series titles for recurring themes low-priority===
#Users then vote and discuss on the issue during that week. The "deadline" for the proposal is one week from posting at:
Something I noticed late yesterday was that the page for "Flower Fields BGM" from Super Mario World 2: Yoshi's Island (Or just Yoshi's Island from now on for simplicity) is still titled [[Yoshi's Island (theme)]], even after Nintendo Music dropped, and then I realised that some other song titles (Most notably [[Obstacle Course]], also from Yoshi's Island) just don't make a lot of sense. Then I feel it's important to note that even though this is a Mario Wiki (What?!?!?!? Huh!?!?!?) we should also take a look at the Super Smash Bros. titles for themes from other series, with the biggest example I can think of being "Meta Knight's Revenge" from Kirby Super Star, which is actually an incorrectly titled medley of the songs "Boarding the Halberd" and "Havoc Aboard the Halberd". It's also good to look at songs Super Smash Bros. is using a different title for than us, like how it uses the Japanese titles of the Donkey Kong Country OST instead of the correct ones. Between all these facts it should be obvious the track titles in Super Smash Bros. are not something the localisation team puts a whole lot of thought or effort into (Though the original Japanese dev team also mess these up sometimes).
##Monday to Thursday: 17:00 (5pm)
Going back to the original point that gave me this realisation, "Yoshi's Island" is a very nondescript track title for a random stage theme which most people would look for by searching for something like "Flower Stage" or possibly even "Ground theme" (Even though that would lead to another song but still), this is especially considering the title screen theme from the game is ALSO called Yoshi's Island, and that's not even considering the Yoshi's Island world map theme from Super Mario World, which I don't know if it even has an official title (Yet, it is coming to Nintendo Music eventually) but I would bet that's ALSO YOSHI'S ISLAND.
##Friday and Saturday: 20:00 (8pm)
So I am suggesting to just make Smash Bros. a VERY low-priority source for this specific small aspect of the Wiki to avoid confusion and potentially future misinformation if things go too far.
##Sunday: 15:00 (3pm)
#Every vote should have a reason accompanying it.
#At any time a vote may be rejected if at least '''three''' active users believe the vote truly has no merit or was cast in bad faith. However, there must be strong reasons supporting the invalidation.
#"<nowiki>#&nbsp;</nowiki>" should be added under the last vote of each support/oppose section to show another blank line.
#At the deadline, the validity of each vote and the discussion is reviewed by the community.
#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.
#All proposals are archived. The original proposer must '''''take action''''' accordingly if the outcome of the proposal dictates it. If it requires the help of a sysop, the proposer can ask for that help.


The times are in EDT, and are set so that the user is more likely to be online at those times (after school, weekend nights).
'''Proposer''': {{User|biggestman}}<br>
'''Deadline''': November 18, 2024, 23:59 GMT


So for example, if a proposal is added on Saturday night at 11:59 PM EDT, the deadline is the next Saturday night at 8:00 PM. If it is indeed a minute later, the deadline is a day plus 15 hours (Sunday), as opposed to a day minus 4 hours.  
====Support====
#{{User|biggestman}} Did you know there's a theme titled "Per this proposal" in Super Wiki Bros. Ultimate but the original title is simply "Per Proposal"? INSANE! (Per proposal)
#{{user|Doc von Schmeltwick}} - the theme names given in ''Smash'' (particularly ''Brawl'' and previous) are more just general descriptions of the contexts they play in rather than actual names. Hence why [[DK Island Swing]] became "Jungle Level."
#{{User|Jdtendo}} Per all.
#{{User|Super Mario RPG}} Per Doc and proposal.
#{{User|LadySophie17}} Per proposal. To me this feels like making a non-Mario game determine the name of a Mario-article.


Also,
====Oppose====
<br><span style="font-family:sans-serif;font-size:30px;line-height:30px;font-weight:900;">NO PROPOSALS ABOUT HAVING BANJO AND CONKER ARTICLES</span> -The Management.
#{{User|Hewer}} The names are from an official source whether we like them or not. Not only that, they come from within the games themselves, putting them at the top of the naming priority list. Tracks that have gone by different names more recently can use those, but those inconsistencies shouldn't invalidate the whole source. We also accept "inconsistent" names from Smash for other subjects, e.g. [[Propeller Piranha]], so it would be odd to single out music. (Also, I'd argue "Meta Knight's Revenge" isn't incorrect, but is the name of the medley rather than of either individual song. On the topic of Kirby music, I'm pretty sure "A Battle of Friends and Bonds 2" from Kirby Star Allies was first called that in Smash before the name appeared in other sources, which would suggest Smash's names aren't all bad.)
#{{User|Nintendo101}} The names used in the Super Smash Bros. series are from first-party games, are specific localizations of ''Super Mario'' specific material, and are localized by Nintendo of America. In my view, that is all that matters for citations, especially given most of these music tracks have not been officially localized into English through other channels. I similarly would not support a proposal to discredit the names for music tracks used in games like ''Mario & Sonic''. However, I do think this proposal is in the ballpark of a reality, which is that melodies that sometimes incorporate multiple compositions (like "Meta Knight's Revenge") and specific arrangements sometimes are given unique names. (This is not unique to the Smash Bros. series — a cursory view of the [https://vgmdb.net/ Video Game Music Database] or of officially published sheet music reveals Nintendo is often inconsistent with these names in the West.) In some installments, what is given a unique name for a particular arrangement (like "Princess Peach's Castle" from ''Melee'' and labeled as such in ''Super Smash Bros. for Wii U'') is attributed to just one piece in a subsequent game (in ''Ultimate'', this piece is named "Ground Theme" despite interlacing the "Underground BGM" in the piece as well, so while more simplistic for the Music List it is not wholly accurate, and I do not think "Ground BGM" should be called "Princess Peach's Castle" in any context other than this ''Melee'' piece). So I think it is worth scrutinizing how we name pieces that are "misattributed." However, I do not support a blanket downground of first-party Nintendo games just because we do not like some of the names.
#{{User|Salmancer}} If I recall from Miiverse correctly, the reason many songs are not given official public names is that naming songs does require spending very valuable developmental bandwidth, something that not all projects have to spare. (Sometimes, certain major songs have names because of how important they are, while other songs don't.) Given this, I am okay with Smash Bros. essentially forcing names for songs out early because it's interface requires named songs. Names don't have to be good to be official. My line is "we all agree this uniquely identifies this subject and is official".
#{{User|Waluigi Time}} See my comment below.
#{{User|Tails777}} Per Waluigi Time
#{{User|Killer Moth}} Per all.
#{{User|Koopa con Carne}} per Nintendo101 & Waluigi Time. Some scrutiny is warranted, but let's not entirely discredit Smash Bros--a series of games published and sometimes developed in first-party capacity--as a source of information.
#{{User|Axii}} Per all.
#{{User|ThePowerPlayer}} These are still the most recent official names. Let's not unnecessarily overcomplicate things.
 
====Comments====
I'm not sure if this is a necessary proposal, or what it's going to accomplish in practice that isn't already handled with current organization and policy. As far as I'm aware, the ''Yoshi's Island'' examples here are just the result of no editor taking the initiative to move those pages to the new titles yet. The Nintendo Music names are the most recent and I think also fall under tier 1 of source priority, technically, so the pages should have those names, end of story. We don't need a proposal to do that.
 
Additionally, "Yoshi's Island" and "Obstacle Course" do ''not'' refer to the original themes from ''Yoshi's Island'' - they're the names of specific arrangements of those themes from the ''Smash'' games. Maybe it's not cemented into policy, but our current approach for theme articles is to use a title referring to the original theme when available. Take "[[Inside the Castle Walls]]", for instance. There's been several different names given to arrangements of this track over the years, including "Peach's Castle", "A Bit of Peace and Quiet", and most recently in the remake of ''Thousand-Year Door'', "A Letter from Princess Peach", but we haven't and most likely aren't going to move the page to any of those. (And that doesn't mean any of those games got it wrong for not calling it "Inside the Castle Walls". It's perfectly valid to give a different name to a new arrangement.)
 
Basically, I don't think this would be beneficial and could potentially cause headaches down the road. I can't think of any actual examples where we're stuck with a "worse" name from ''Smash'' based on everything else I've said here, especially with Nintendo Music being a new and growing resource for track titles in the context of the original games. --{{User:Waluigi Time/sig}} 14:17, November 4, 2024 (EST)
:Indeed, [[Ground BGM (Super Mario Bros.)|Ground BGM]] already got moved to its Nintendo Music name, despite being called "Ground Theme" in Smash (among other sources). Nintendo Music should already take priority over Smash just for being more recent. {{User:Hewer/sig}} 14:29, November 4, 2024 (EST)
 
:{{@|biggestman}} I recommend skimming through our [[MarioWiki:Naming|naming policies]] for some clarity. The only reason why "[[Yoshi's Island (theme)]]" has not been moved to "Flower Fields BGM" is because no editor took the initiative yet, and another one had already turned "[[Flower Fields BGM]]" into a redirect page. That must be deleted by an admin first before the page can be moved, but that is the only reason. ''Super Smash Bros.'' and Nintendo Music are at the same tier of coverage, and because Nintendo Music is the most recent use of the piece, it should be moved. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 15:50, November 4, 2024 (EST)
 
@LadySophie17: What do you make of [[Propeller Piranha]], [[Fire Nipper Plant]], [[Nipper Dandelion]], etc., which are named based on what Viridi [[List of Palutena's Guidance conversations#Piranha Plant|calls them]] in Smash? And more generally, why does Smash not being strictly a Mario game matter? It's still an official game from Nintendo that uses the Mario IP, and the Mario content in it is fully covered even if it's exclusive to Smash (e.g. Mario stages and special moves all get articles). {{User:Hewer/sig}} 17:29, November 4, 2024 (EST)
:There's also the fact that Nintendo Music, which this proposal aims to prioritise, is not a Mario game either. It has a collection of music from various different franchises that just so happens to include Mario, much like Smash. {{User:Hewer/sig}} 08:10, November 5, 2024 (EST)


__TOC__
A lot of you have made good points, but one I don't understand or like is the one that those are the names of specifically the Super Smash Bros. versions, which is just painfully inconsistent. With very little exception remixes in Super Smash Bros. almost always use the original title in one of two ways, either using the name completely normally or by titling it (SONG NAME 1 HERE)/(SONG NAME 2 HERE) for remixes that are a relatively even split between two songs. Outside of this the only examples of "Well it COULD be the name of specifically the Smash version!!!" from every series represented are "Yoshi's Island", "Obstacle Course" and "Meta Knight's Revenge". Out of these Yoshi's Island and Obstacle Course theoretically COULD be original titles, but Meta Knight's Revenge is (probably) just meant to be named after Revenge of Meta Knight from Kirby Super Star, which is where both of the songs represented debuted, but was mistranslated. However I can't prove anything because none of these 3 Smash Bros. series remixes Japanese titles are anywhere online as far as I can tell so there's nothing to compare any of them to. There might also be examples from something like Fire Emblem or something idk I play primarily funny platformers. The point though is that if they were to name some remixes after the originals while making original titles for some it would just be so inconsistent I simply can't see a world where that's the intent. {{User:Biggestman/sig}} 13:19, November 5, 2024 (EST)
:I believe the Japanese name of the track was the same as the Japanese name of "Revenge of Meta Knight", but I maintain that translating it as "Meta Knight's Revenge" is not necessarily a mistake, the translators might have just thought that name was better suited for the theme specifically, especially since medleys in the Kirby series are often given different titles to the included themes ("Revenge of Meta Knight" is still not the title of either of the individual tracks included). For example, a different medley of the same two themes in Kirby's Dream Buffet is titled "Revenge of Steel Wings". Even if "Meta Knight's Revenge" is an error, though, that's one error in over a thousand track names, and one not even from the Mario franchise. One or two errors aren't enough to invalidate an entire source, especially one of this size. As for the Yoshi's Island tracks, as has already been pointed out, they should be changed anyway because Nintendo Music is the more recent source ([[Flower Field BGM]] already has been changed since this proposal was made). {{User:Hewer/sig}} 13:49, November 5, 2024 (EST)
::FWIW, that point isn't meant to be an argument against this specific change anyway, it's "we already shouldn't be prioritizing those names for article titles regardless of the outcome of this proposal, and here's why". --{{User:Waluigi Time/sig}} 18:13, November 5, 2024 (EST)
Ok so now that it's been a few days I have very quickly realised that I very much said a bad reason this change should be implemented. I just realised that all of these titles have already been moved but I have since realised a somewhat more understandable reason for it. If a new Smash game came out and reused these titles then according to our rules they would need to be moved back to those titles again, wouldn't they? Would it make sense to move Flower Fields BGM back to the less descriptive title just because a game reused a (debatably) worse title? Overall though I don't care too much about the result, even when I started this proposal, my impatience just got to me too early. {{User:Biggestman/sig}} 11:09, November 7, 2024 (EST)
:Yes, that's how recent name policy works. We should choose what name to use based on what the most recent official source says, not what we subjectively prefer. I personally feel like "Flower Field BGM" isn't much less generic than "Yoshi's Island". {{User:Hewer/sig}} 11:38, November 7, 2024 (EST)
::Not a simple yes/no answer, actually. If they're just arrangements again, then no, we wouldn't move the pages. If they added the original tracks from the SNES version and used those names, then they would probably be moved. (However, you might still be able to make a decent argument for keeping the Nintendo Music names on a recency basis considering it's a live service?) --{{User:Waluigi Time/sig}} 11:48, November 7, 2024 (EST)


<center><span style="font-size:200%">CURRENTLY: '''{{LOCALTIME}}, {{LOCALDAY}} {{LOCALMONTHNAME}} {{LOCALYEAR}} (EDT)'''</span></center>
I've actually been mulling over a proposal like this, but for names in general, not just themes. We generally don't consider out-of-franchise content as a source of a recent name if the original ''Super Mario'' franchise supersedes it; for example, Podoboo, which is still in use over Lava Bubble in ''The Legend of Zelda'' franchise. I don't see why the same thing can't be said for ''Super Smash Bros.'', especially now with its reduced coverage. For that matter, possibly breaking it down to a per-''series'' basis (like how "Gold Goomba" was the most recent name in the ''Super Mario'' series despite being "Golden Goomba" in the most recent ''Mario Party'')? It might not be a bad idea to establish a new rule over this. [[User:LinkTheLefty|LinkTheLefty]] ([[User talk:LinkTheLefty|talk]]) 08:24, November 8, 2024 (EST)


==New Features==
===Decide how to prioritize PAL English names===
===NWFC Chat add to sidebar===
As with [[MarioWiki:Proposals/Archive/69#Decide how to handle the "latest portrayal" section in infoboxes|my previous proposal]], this one aims at getting a consistent method of how PAL names are used alongside NTSC names. One thing that I noticed is that the priority of some of these names are inconsistent, like [{{fullurl:Mini Bowser|redirect=no}} Mini Bowser], which redirects to [[Koopa Kid]] rather than link to [[Mini Bowser (toy)|the name actually used in NTSC countries]]. Other pages, like [[Bowser Party]], are disambiguations between the ''[[Mario Party 10]]'' game mode and the ''[[Mario Party 7]]'' [[Bowser Time|event]] that is only known as "Bowser Party" in PAL regions.
It's a pain to type "/j mwikionline" all the time when you enter chat. Why not have a seperate thing on the sidebar that says "Wifi Chat" or something which is a direct link to "/j mwikionline"? We could get some more users who dont know the room by name into the room and we can get  more wifi competitors! i mean is it just me or are the same users in that room every time we go check? i mean i only go in when someone tells me to go in and i bet alot of people do that too.i feel it should be publicized to our community .Wonder how many users new this room existed before i made this Proposal. Just my point.


i mean image average guests coming in and wants to Brawl, Race, or what not? We could get a whole new breed of online social mobility!
[https://upload.wikimedia.org/wikipedia/commons/0/0d/PAL-NTSC-SECAM.svg This map] shows which countries use these different systems. The terms go beyond just color conversion; in terms of English, the PAL system is used in countries like the United Kingdom (and correct me if I'm wrong, but I also think Australia and New Zealand too), while the NTSC system is used in North America, specifically in the United States and Canada. [[MarioWiki:Naming]] says that the North American name takes priority, which means that Mini Bowser would link to the toy and Bowser Party would redirect to the section in ''Mario Party 10'', potentially among other pages, although tophats linking to pages with alternate PAL names will remain.


Any Goers?
Therefore, I am proposing four options:
*NTSC>PAL, in which when linking pages, the page with the name in NTSC English or all-English takes priority over other pages sharing the same PAL name, even if it isn't as significant. If another page with the same name in PAL English exists, it can be linked to in the tophat.
*NTSC=PAL, in which pages that share the same name in both NTSC and PAL English appear in a disambiguation page regardless of whether the name is used in NTSC English multiple times or not. This is already done with [[Bowser Party]].
*NTSC<PAL, in which pages that share the same name in PAL English have the highest priority name linked to it, even if it doesn't have that name in NTSC English but the other pages does, in which case it will redirect to the higher-priority PAL name and the lower-priority NTSC (or all-English) page will be linked to in the tophat in the Redirect template. This has been done with [[Mini Bowser]].
*Do nothing - do I even have to explain this?


'''Proposer:''' -- {{user|WarioLoaf}} 23:43, 10 May 2008 (EDT)<br>
'''Proposer''': {{User|Altendo}}<br>
'''Deadline:''' May 17, 2008, 20:00
'''Deadline''': November 18, 2024, 23:59 GMT


====YAY====
====NTSC>PAL====
#{{User|WarioLoaf}} - I'm the one who proposed it , if i said NAY i'd be the wiki idiot wouldn't i be?
#{{User|Altendo}} I think that abiding by SMW:NAMING is the best option. Yes, Koopa Kid is more notable than Mini Bowser toys, but if this is an American English wiki, might as well make pages link to the one that actually are named like that in NTSC.
#{{User|Knife}} 12:02, 11 May 2008 (EDT) - Maybe not on the sidebar, but I do consider it the most important sub-chat of #mariowiki. Of course, its not as important as the main channel, but there should be a link to it in the intro message of the chat saying "please do not organize online matches here, do so in #mwikionline", or something like that.
#{{User|Master Crash}} - I for one didn't even know this place existed! Makes me wonder what else i didn't know :o


====NAY====
====NTSC=PAL====
#{{User|Wayoshi}} &ndash; no no no. #mwikionline is a sub-chatroom of #mariowiki, not equally separate from it. It's easy enough to tell users what to do to get there from #mariowiki.
#{{User|Ahemtoday}} I think this is the best solution — completely deprioritizing the PAL names doesn't quite seem right to me.
#{{User|Purple Yoshi}} - Per Wayo. It would be really annoying for people who didn't want to go on the chat. If you want more people there, ask them to come.
#Per Purple Yoshi. For people like me who don't go on the chat, that would jus be extremely annoying. {{User|Toadette 4evur}}
#{{User|Stooben Rooben}} Per all. It just seems like it would be kind of annoying.
#{{User|Super-Yoshi}} - Come on , dont be THAT lazy. It takes like 2 seconds.
#{{User|Pokemon DP}} - Yeah... Uh, WarioLoaf, you must be REALLY lazy to make a Proposal asking to make something that takes, like, 2 seconds easier for you. XD Per all.


====NTSC<PAL====


====Do nothing====


====Comments====
====Comments====
I have redirected [[Mario Wiki Chat]] to the chat room so you can just type that into the search bar, easier and simpler (if i wasnt aloud to do this just let me know...:/)<br>~~{{user|theused}}
can i ask for some more examples? i'm having a bit of trouble fully grasping what you mean [[User:EvieMaybe|EvieMaybe]] ([[User talk:EvieMaybe|talk]]) 20:11, November 4, 2024 (EST)
:The Mini Bowser situation, for instance:


===Badges===
:*NTSC>PAL: Mini Bowser would link to the [[Mini Bowser (toy)|page actually named "Mini Bowser"]] instead of [[Koopa Kid]] (who is known as Mini Bowser in PAL English)
I was looking at "Unused Badges" and I found alot of "Unknowns" and what not. So I was asking, if that info is not filled in, why is it part of the page? I also looked at the little green badge with a sun in the middle of it, and someone wrote down " It's possible to make the sun in Flower Fields shine more with this badge" or something along the lines of it. But there are no sources for that line. So if we dont have any information or any sources and other stuff like that, why not make a seperate new section for it? It would go well and when we find the information we an merge it in the Unused Badge's page again, so it will look more neater and proffesional. I propose that we should make a new page for these unknown badges, and when information is found, put them in the unused badges again. EDIT: I am trying to say that the "Unused Badges" page is too informal, it needs some fixing up to do. So for now, why dont we put the Incomplete page template or either make a new page for the badges that have no info on them. Now anyone see what Im sayin?
:*NTSC=PAL: Mini Bowser would be a disambiguation page between Koopa Kid and the Mini Bowser toy
Anyone with me?
:*NTSC<PAL: Mini Bowser would continue to redirect to Koopa Kid.
:*Do nothing: Nothing changes.


'''Proposer:''' {{User|Super-Yoshi}}<br>
:Hope this makes more sense. [[User:Altendo|Al]][[User talk:Altendo|ten]][[Special:Contributions/Altendo|do]] 21:07, November 4, 2024 (EST)
'''Deadline:''' May 19, 2008, 17:00
::So in the first option, "Mini Bowser (toy)" would lose its identifier? {{User:Hewer/sig}} 06:19, November 5, 2024 (EST)
:::Basically. The tophat will say, "This article is about the toy. For the characters known as "Mini Bowsers" in Europe, as Koopa Kid." I prefer abiding by SMW:NAMING by prioritizing NTSC names over PAL names. Basically, the current Mini Bowser (toy) page will be moved to Mini Bowser, which will no longer redirect to Koopa Kid. For people who have only owned NTSC copies, this is more straightforward, as many would be unaware that Koopa Kid is known as Mini Bowser without having a PAL copy. As for Bowser Party, if Option 1 passes, it will redirect to the section in ''Mario Party 10'', with a tophat leading to Bowser Time. If Option 2 passes, Mini Bowser would become a disambiguation page between Koopa Kid and Mini Bowser (toy). If Option 3 passes, Bowser Party would redirect to Bowser Time and would have a tophat leading to the ''Mario Party 10'' section. If Option 4 passes, well... nothing changes, making everything remain inconsistent.


====Make New Page====
:::So, to answer your question, yes, the identifier will be removed. The only other page with the exact same name minus the identifier is simply the redirect to Koopa Kid, who is only known as "Mini Bowser" in European English, and SMW:NAMING prioritizes American English names. [[User:Altendo|Al]][[User talk:Altendo|ten]][[Special:Contributions/Altendo|do]] 07:15, November 5, 2024 (EST)
#{{User|Super-Yoshi}} I am the proposer, so I say yes
::::Now that I think about it, couldn't the identifier for the Mini Bowser toy be removed anyway? There's no actual article named Mini Bowser. For that matter, I thought it was discouraged to use the terms NTSC and PAL now in regards to English, especially now that region-locking is mostly a thing of the past. [[User:LinkTheLefty|LinkTheLefty]] ([[User talk:LinkTheLefty|talk]]) 08:24, November 8, 2024 (EST)
 
==New features==
''None at the moment.''


====Don't Make New Page====
==Removals==
#{{User|Stumpers}} This proposal could use examples and specific references. It is far to general and confusing to me right know. Page and section were used interchangably above, for example. Please clarify and repost.
''None at the moment.''
#{{User|Stooben Rooben}} Per Stumpers. This proposal is too vague for my liking.
 
#{{User|Cobold}} - Any unused sprites should be at the [[Beta Elements]] page. Unless we're planning to split that, I don't see a need for an Unused Badges page.
==Changes==
#{{user|InfectedShroom}} Per Stoobs. Plus, why would we need a new page? We already have a seperate section for them. :S
===Stop considering reused voice clips as references (usually)===
More often than not, if you look at a game's list of references to other games, you'll find something about how so-and-so character reuses voice clips from so-and-so game. This has been bugging me for a while because these just aren't references. Nintendo has been reusing voice clips for multiple decades now, so this isn't anything new. When a new ''Mario Kart'' game comes out and some of the drivers reuse some wahoos or hurt sounds or whatever else from an old ''Mario Party'' game, it's not because the developers wanted to give a nod to that ''Mario Party'' game, it's because they had those clips on hand and could easily repurpose them instead of dragging the voice actor back into the recording booth. I propose removing reused voice clips from the references to other games/references in later games lists, with one exception that I'll get to shortly.
 
For a particularly egregious example, here's all the "references" of this type currently listed on ''Super Mario Party''. Notice how vague these entries are and how many of them don't even specify which characters have clips reused.
*''[[Super Mario Strikers]]'': Some of Hammer Bro's voice clips are reused from this game.
*''[[Mario Party 8]]'': Hammer Bro's artwork, as well as some voice clips, are reused from this game.
*''[[Mario Kart Wii]]'': Some voice clips are reused.
*''[[Mario Super Sluggers]]'': [...] Some voice clips are reused.
*''[[New Super Mario Bros. Wii]]'', ''[[New Super Mario Bros. 2]]'', and ''[[New Super Mario Bros. U]]'': [...] Some voice clips are reused.
*''[[Super Mario Galaxy 2]]'': Some of [[Yoshi]]'s voice clips are reused from this game.
*''[[Mario Kart 7]]'': Flutter's voice clips are recycled from [[Wiggler]]'s voice clips in this game.
*''[[Mario Party 9]]'': [...] Some voice clips are reused.
*''[[Mario Party: Island Tour]]'': [...] Some of Bowser Jr.'s voice clips are reused from this game.
*''[[Super Mario 3D World]]'': [...] Some voice clips are reused.
*''[[Mario Kart 8]]'': Some voice clips are reused from this game.
*''[[Mario Tennis: Ultra Smash]]'': Some of Mario's voice clips are reused from this game.
*''[[Super Mario Odyssey]]'': [...] Some of [[Mario]] and [[Luigi]]'s voice clips are recycled.
 
The exception to this would be if a voice clip, within the context it appears in the game, is clearly a reference to another work. I'm not sure of any actual examples off the top of my head, but hypothetically, if Luigi reused some of the "MARIO!" voice clips from ''Luigi's Mansion'' in [[Luigi and the Haunted Mansion]] from ''Super Mario Galaxy'', that would probably be considered a reference. In this case, the entry should explain exactly what clip(s) are being used and what it is about the situation that makes it a reference. That leads me into what should probably be a good rule of thumb for this exception: if you can't explain why it's a reference beyond just being in that game, then it's probably not a reference.
 
'''Proposer''': {{User|Waluigi Time}}<br>
'''Deadline''': November 8, 2024, 23:59 GMT
 
====Support====
#{{User|Waluigi Time}} Waluigi Time's support vote is reused from this proposal.
#{{User|Nightwicked Bowser}} These voice clips are most likely used without their game of origin in mind.
#{{User|Super Mario RPG}} Per both.
#{{User|Sparks}} Per all.
#{{User|LadySophie17}} ''[[Donkey Kong (game)|Donkey Kong]]'': Mario's mustache is reused from this game.
#{{User|TheFlameChomp}} Per all.
#{{User|Nintendo101}} Repurposing an asset — voice clip or otherwise — is rarely a reference in isolation.
#{{user|Doc von Schmeltwick}} - I ''swear'' this has already been proposed and passed....
#{{User|Arend}} I think this is more worth to be its own trivia subsection ("Reused assets"?) than treating it as a specific "reference" and lumping it among the more legit ones.
#{{User|Shadow2}} Per all.
#{{User|Camwoodstock}} Per all. Reuse of assets isn't really a "reference" in the usual sense, as there's plenty of non-callback reasons to do so. We don't think the re-used Charles Martinet lines in the ''TTYD'' remake were done out of wanting to do a cameo from Charles, they probably just didn't feel like bringing Kevin back into the recording booth when they already had a cohesive library of voicelines from the original game. ;P
#{{User|EvieMaybe}} per all
#{{User|DesaMatt}} per all.
#{{User|PnnyCrygr}} Per all as This "reusal of voices" statement is getting done to death over and over again. And a reuse of assets is not an allusion/reference to something.
#{{User|ThePowerPlayer}} ThePowerPlayer's "Per all" vote is reused.
#{{User|Cadrega86}}, the same also goes for generic artwork (so unless it's specifically stylized or features stuff specific to a single game/subseries). These are not references but just "lazy" asset re-usage.
#{{User|Technetium}} Per all.
#{{User|Jdtendo}} Per all.
#{{User|Ray Trace}} Grunts, screams, and whoohoos aren't uttered with a specific game in mind and our articles shouldn't reflect that.
#{{User|Scrooge200}} This has been bugging me for a while. This is just asset reuse to save budget and because there's very few specific lines that need to be newly recorded.
#{{User|Mario}} Just because it was first heard in a game doesn't mean it was recorded for this game. It might be a stock sound that went unused and eventually found its way into a future game. Additionally there are clips that are better known in other games than the one it originated in. "That's-a so nice!" Is commonly heard when Mario clears a level in New Super Mario Bros., but this quote is first heard in Mario Kart Double Dash, barely audible in the Awards Ceremony. Unless the clip itself is made specifically for a game (Mario vs. Donkey Kong!!! Finding its way in a Mario Kart game as a store speaker or something) it's best not to list as a reference. That being said, there should be ways to list if voices have been reused.
#{{User|Tails777}} This is on par with referencing ''Super Mario Galaxy'' every time Rosalina appears. Pretty sure we had a proposal at some point opting to exclude these types of recurring things from the references section and this is just following in suit. Per proposal.
#{{User|DryBonesBandit}} Reusing a "per all" vote from previous proposals.
#{{User|BlueBirdBlues}} Reusing assets are, in most cases, not references. That being said, I do feel like we should document these reused assets ''somewhere'', perhaps on a separate [[List of reused assets]] article? Creating a new subsection in each article for these reused assets would work too, I suppose.
#{{User|SeanWheeler}} Don't want to bloat the references section of each game's page.
#{{User|ExoRosalina}} Reused are unlikely as references, especially voice clips.
#{{User|Okapii}} Per all; voice lines in the Mario franchise have been reused so many times that what game they originated in feels almost meaningless, and making a note for every time any character reuses a specific line just feels like pointless bloat for the reference section.
 
====Oppose====
#{{User|Hewer}} I think a game reusing assets like voice clips from a previous one is still worth noting, and the reference sections are a handy place to do it. I don't see why we must restrict the section to only when "the developers wanted to give a nod".
#{{User|Pseudo}} Per Hewer. I do get that it's not an intentional reference per se, but this is still information worth documenting on the wiki (if a different place to note this information would be proposed, I'm all ears).


====Comments====
====Comments====
It seems to me like you want to remove the parts of the article that are incomplete.  that defeats the point of the Wiki, which is for people to both consume information and add what isn't there. You'd be hiding the incomplete information from users who might be able to make it complete. {{User|Stumpers}} 23:33, 13 May 2008 (EDT)
I do know Luigi's "Gotcha!" was made for ''Luigi's Mansion'' as a thing he says when he catches ghosts, then became a standard voice clip for him in 64DS and NSMB, despite no longer making as much sense there. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 11:46, October 27, 2024 (EDT)


===Create Smash Bros costumes page===
I would also like a place for people to note when new voice clips get recorded. I think the Protrayals section of character articles makes a fair amount of sense. Or maybe in Development sections of games? [[User:Salmancer|Salmancer]] ([[User talk:Salmancer|talk]]) 21:07, October 30, 2024 (EDT)
I was just thinking about how we could have a page where users could look at the costumes and see descriptions of their appearance. How this could be done, you ask? A contributer(s) with an SD card could take small resolution pics of each costume and fit them into one image. Since each character has a unique set of costumes, with some even resembling other characters, I thought this would be a good idea. The table would look something like this:


'''Mario'''


(insert pic of all costumes)
===Encourage game-related "icon"-type images to have consistent file dimensions with each other when applicable to their origins===


Costume 1: Mario's basic outfit.
[[MarioWiki:Proposals/Archive/70#Prioritize sprite/tile uploads that have their original file parameters (or clean divisions of them)|My last proposal]] related to this subject had too many holes in it due to being too wide to make an actual rule on the subject. Indeed, not all sprites really need the blank space, not all "icons" are sprites at all. To recap:
;this looks good:
<gallery heights=64 widths=64>
MKDD_Mario.png
MKDD_Luigi.png
ToadIcon-MKDD.png
PeachIcon-MKDD.png
MKDD_Yoshi.png
MKDD_DK.png
BowserMKDD.png
MKDD_Wario.png
</gallery>


Costume 2: Fire Mario.
;this does not:
<gallery heights=72 widths=72>
MarioMPT.png
Luigi MPT.png
Shy Guy MPT.png
Peach MPT.png
Yoshi MPT.png
DK MPT.png
Bowser MPT.png
WarioMPT.png
</gallery>


Costume 3: Mario's normal outfit with red and blue switched.
Notice how half of the MPT ones (second row) are awkwardly, inconsistently stretched in various gross ways that makes some of the pixels be rectangles, and none are at a proper size relative to each other - this is an obsessive-compulsive spriter's worst nightmare. Meanwhile, the MKDD ones (first row) look crisp, clean, and are at a nice size relative to each other. Why is this? Because since they are icons, they are programmed to occupy the same type of space in select screens and player standings in-game. They're ''supposed'' to be at around the same size, which is accomplished through the small amount of empty space some have in the upper right corners - which the origin images have in the game's files. We should reflect this for the simple reason that we're only going to be putting these in galleries and table cells with each other ''anyway'', so it makes the most sense to have them take up the same amount of space here as well. They should either be at their raw parameters, or if they are cropped, cropped to the exact same size as all the others for that type in that game so as to not screw up formatting and table cell sizes (and we shouldn't be increasing the size of sprites that are at this size by default anyway). This goes for selection icons, rank icons, map icons, that sort of thing. Cropping them down needlessly leads to the grossness that the second gallery there displays.


Costume 4: Wario's color scheme.
This is already something of an unofficial rule on here; a majority of the games with this sort of icon have them uploaded at a consistent size already for the same pragmatic reasons I just listed. I'm just trying to make this more clear-cut. It's like how "don't optimize images with color-changing metadata" is a rule - most people can't tell the difference, but it minorly affects the accuracy and presentation, so that's why that rule is in place. This is also for the "accuracy and presentation" reasoning. Also, I fail to see what the difference is between this and preferring screenshots be uploaded at native res rather than boosted resolution.


Costume 5: Brown hat, overalls and gray sleeves.
'''{{color|purple|THIS DOES NOT COVER THE RARE INSTANCES GAME ICONS ACTUALLY ''DO'' HAVE DIFFERENT SIZES AS STORED IN-GAME.}}''' Instances of that are quite rare, especially for character icons that swap locations, but they can happen. Since they aren't the same size to begin with, there's nothing to match up with. It also does not apply to ones that are extrapolated from a singular group image containing all of them.


Costume 6: Green hat, sleeves and tan overalls.
'''{{color|purple|PLEASE NOTE THAT MOST IMAGES OF THIS TYPE ON THE WIKI ALREADY FOLLOW THIS RULE.}}''' Attempting to do the opposite, therefore, will take more effort for less reward.


'''{{color|purple|ADDITIONALLY, I WANT TO CLARIFY THAT THIS IS NOT SPECIFICALLY STATING THEY NEED TO KEEP THEIR NATIVE DIMENSIONS.}}''' Rather, it is saying that if you ''do'' decide to crop them, you should crop them to consistent parameters, ie, the width of the widest one and the height of the tallest one. Having to resize images on an individual basis is tedious and can lead to extra HTML bloating the page that would be a non-issue if they were uploaded at the same size to begin with.


So, opinions?
'''{{color|purple|EDIT:}}'''
Here's a better illustration of why I think this is necessary:<br>
https://www.marioboards.com/attachments/49667.png
<br>Notice how with them cropped to content, their vertical (and horizontal if they were stacked, thanks to Klap Trap's muzzle and Diddy's hat) positions are all over the place. To someone with OCD, that's maddening. Not unlike [https://www.xkcd.com/1015/ bad kerning]. This is what this proposal hopes to avoid. And no, that's not something a "rawsize" thing can do, that's gallery-only - and this inconsistent positioning would be an even bigger issue with the images in a gallery, since those ''don't'' have positioners available. And while technically, HTML ''can'' fix the positioning on the table (but again, not in a gallery), that would require a bunch of finagling span classes that would bloat the page's byte count unnecessarily - not to mention take potentially hours of trial and error depending on the image amount - when the obvious solution is to give the images the consistent parameters they were deliberately made to have - and yes, that's deliberate in more than just "limited by sprite parameters," because they used them to position them accurately in the character/level select, as I am doing with this table.


'''Proposer:''' {{User|huntercrunch}}<br>
'''Proposer''': {{User|Doc von Schmeltwick}}<br>
'''Deadline:''' May 19, 2008, 10:00
'''Deadline''': November 11, 2024, 23:59 GMT


====Make New Page====
====Support - consistent icons (change the few remaining icon images and make it a general rule for the future)====
#{{User|huntercrunch}} My reasons are given above
#{{user|Doc von Schmeltwick}} - ''Icon'' haz dead, never-funny-in-the-first-place memes about fast food sandwiches?
#{{User|MegaMario9910}} I have to agree with his comment. Besides, we have a lot of Brawl stuff in the characters articles, so let's lessen some out. I also think this is a good idea.
#{{user|Super Mario RPG}} - Accurate to how the graphic or texture is stored in game.
#{{User|Hewer}} Per fast food sandwiches
#{{User|Ahemtoday}} Per proposal.
#{{User|blueberrymuffin}} Per proposal.


====Don't Make New Page====
====Oppose - who needs consistency? (do nothing)====
#{{User|Ninjayoshi}}- Per stumpers with his idea on no individual articles, but sections on each character.
#{{User|Waluigi Time}} Rawsize exists.
#{{User|HyperToad}} Per Ninjayoshi
#{{User|Koopa con Carne}} There's no sense in ''deliberately'' translating the functional limitations of a game onto a wiki. The site's educational purpose dictates that official material shown on a wiki be inherently recontextualized, and showing that material at a different scale than originally intended is in line with that idea. Even taking into account the niche interests of a sprite enthusiast (which TBH is fair, the wiki is a gateway to Mario material for anybody), the sprites in and of themselves are accurate to how they were extracted when you view them on their dedicated file pages; it's only their appearance on mainspace pages that is subject to alterations, and what to what degree that is beneficial is better scrutinized on a case-by-case basis than through a global proposal. TLDR If the sprites are too uncomfortably big just resize them, or use rawsize like Waluigi Time says.
#{{User|Glitchman}} This is a bad idea, we already have too much info on the SSB games as it is, a new page for each costume would result to hundreds of pages and, added to the pre-existing SSB pages, thousands.
#{{user|Lakituthequick}} Per WT.
#{{User|Stooben Rooben}} Per Stumpers and Glitchman.
#{{User|UltraMario}} Per all. This can easily be taken care of by either a gallery or a table's settings, I am very sure of that. We don't need to be unnecessarily tampering with perfectly cropped files. I am not 100% sure of the technical site of the wiki but I am very sure that there are better ways to go about fixing sizing of things in tables not being adequate without just having to overhaul image uploads entirely, rather than just playing around with a table.
#{{User|Cobold}} - Per Stumpers' comment below and per Glitchman.
#{{User|Fun With Despair}} Seems like a huge amount of work for what is... honestly imperceptible to 99.9% of users such as in your example. Busywork for the sake of busywork.
#{{User:Stumpers/sig}} See my comment.
#{{User|Shy Guy on Wheels}} Per all. I see no real benefit from this.
#{{user|Sdman213}} Per all.
#{{User|Camwoodstock}} Per all, especially Waluigi Time. We already have tools capable of representing these icons more accurately to their in-game versions as necessary without requiring deadzones or other such things to be baked into the image itself. In fact, baking it into the image itself can cause issues when attempting to use the same image on different pages not fitted for them; such as how the image on the infobox for [[Blooper (Paper Mario: The Thousand-Year Door)]] is markedly smaller because it retains the blank space for the sake of [[Paper Mario: The Thousand-Year Door (Nintendo Switch) bestiary|the bestiary article]]. While we should strive for accuracy, we shouldn't let it get in the way of making the information actually accessible and readable; besides, if someone wanted the raw, original images, including any blank space around them, they would likely check The Spriter's Resource, not us.
#{{User|Ray Trace}} Per Koopa Con Carne. Zero readers care if an asset is cropped to content to dimensions in the power of 8 or if they have the ripped dimensions, especially if all said images are there to illustrate a gallery and especially if there is copious amounts of empty space just to pad the image to appropriate dimensions for a game engine. We aren't a game engine (modern game engines are perfectly capable of having textures in resolutions not in powers of 8 by the way), official websites such as the Mario Kart 8 Deluxe's official website [[:File:MK8DX Baby Luigi Icon.png|crop to content]] because image editors know that it doesn't need to be in those dimensions (let's not get into how these assets are actually made, they're scaled down in the first place 100% for game engine reasons) icons should be cropped to editor's discretion without bludgeoning editors over the head about it, we should prioritize optimization and readability over faithfulness to asset dimensions. I can see cases where consistent sizes can work out, namely the character icons as listed in this proposal, but the general rule ''should'' be crop to content, but leave some in exceptions in regards to formatting tables, not the other way around.
#{{User|TheFlameChomp}} Per all.
#{{User|ThePowerPlayer}} Per all.
#{{User|Shoey}} Per all.
#{{User|Jdtendo}} Per all.
#{{User|Cadrega86}} Per all, especially Koopa con Carne and Ray Trace.
#{{User|Axii}} Per all.
#{{User|SeanWheeler}} Some really small icons like the Super Smash Bros. series stock icons would look really bad if they were resized to be consistent with Mario Kart ranking icons.
#{{User|Mario}} The additional caveats in the proposal trying to address this issue is nice I guess but it makes the proposal much less clear in what it's trying to accomplish and it comes off as this user trying to bludgeon over their approach to these images in opposition with several other people's while tacking on qualifications and caveats after the fact. It doesn't help that the terminology of the proposal is imprecise (what is a "game-related 'icon'-type image"?? Does the proposal apply to whatever is a "game related 'non-icon' type image"?)  Per all.
#{{User|Killer Moth}} Per all. I don't see the point in doing this.
#{{User|Nintendo101}} I will reiterate what I said below: if folks want to maintain unified dimensions around certain assets, like the ones in the ''Diddy Kong Pilot'' example, that is completely fine and okay to do. I agree it looks nice. However, folks should have the freedom to choose whether they want to do that or not with the tables and templates they have developed. To experiment. I agree with the opposition that cropping to the visual content of an asset is not inherently destructive, while recognizing there are real examples on this wiki where assets benefit from having unified dimensions outside of galleries. But those were choices made because they are visually appealing and convey information - not out of a unique reverence for how computer engines spatially store assets, and while I know this proposal is not explicitly advocating for that, it derives from similar arguments made in the previous one, and I wanted to touch upon that here. We adjust assets all the time for the sake of illustrative intent. We assemble disembodied sprites. Adjust/add colors to reflect in-game appearances (especially when they are not actually coded as such for older consoles). We pose models. We approximate lighting conditions. We crop out screenshot details for a focused view. We narrow displays to omit details that the player typically has [[:File:MagmawNSMBU.png#File history|no way of seeing]]. From my experience, none of these choices have been considered controversial, and they should not be. They are not dissimilar from {{wp|taxidermy}}, {{wp|Conservation and restoration of paintings|art restoration}}, and similar curatorial techniques that are exercised in museums worldwide. To me, cropping to visual content - the pixels that people can actually see - is no different from these methods and not an inherent problem. If folks want to keep unified dimensions around the assets they are working with or see use outside of galleries, that is fine and good. This is the opinion of some other folks in the opposition, like fellow ripper Ray Trace, as evident [[:File:WarioMASATOG.png#File history|here]]. However, if folks do not want to do that, or use tables built on the expectation that assets they are using are cropped to content, or they are cropping the content around assets that are only found in galleries, I think they should have that freedom too.
#{{User|MCD}} Per all.
#{{User|FanOfYoshi}} No. No, both look good in their own right. Per all.
#{{User|SmokedChili}} Per all.


====Comments====
====Comments====
Wouldn't this be better on the Smash Bros. section in each character article? {{User|Stumpers}} 00:34, 13 May 2008 (EDT)
{{@|Waluigi Time}} - Rawsize doesn't help for tabular data. Only for galleries. Only way to get it there would be to separately size each cell, and even that doesn't keep them in the correct position within the cell. Wouldn't it be more pragmatic to just have the images at the correct size rather than having to mess with the HTML each time? And we do indeed use these for tabular data, like ghost times, tennis rivals, that sort of thing. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 16:43, October 28, 2024 (EDT)
:And would that not be easily solved by displaying the image at its native resolution (or at least consistent resolutions for all of them) and centering it? --{{User:Waluigi Time/sig}} 16:51, October 28, 2024 (EDT)
::No, it absolutely wouldn't. Because not all the icons are themselves centered, such as the MKDD ones above. They all come out of the lower-left corner. And that's not getting into how some games have a variant with an actual shaped background alongside clear-background ones, like ''[https://www.spriters-resource.com/wii/mariostrikerscharged/sheet/195218/ Strikers Charged]'' for example. It'd make the most sense to match those up relative to where the square bounds are for their respective size, IMO. Also, when they need shrunk for smaller tables, it's easier to do that when they have the same x-y parameters anyway so you don't have to check every. Last. One. And do the math each time. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 16:52, October 28, 2024 (EDT)
::{{@|Waluigi Time}} - Rawsize also doesn't work for sizing images down. Only sizing them as-is or sizing them up. So it's still not a perfect solution for all occasions anyway. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 02:48, October 29, 2024 (EDT)
:All of these things can be fixed using <code>text-align: center</code>, <code>vertical-align: middle</code>, and the inherent ability of tables to size columns and rows based on their contents. {{User:Lakituthequick/sig}} 20:55, 28 October 2024 (UTC)
::I already said that's not true, because not all of them are centered in their origin. If you want DK's image's left border touching the left border and his right border touching the right border, and the same to go for Luigi, that will absolutely not work unless they are uploaded at their intended size. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 16:58, October 28, 2024 (EDT)
 
{{@|Koopa con Carne}} - I thought you didn't want math to be forced onto the site. In order to resize them consistently if they aren't uploaded at the intended consistent size, you have to go through ''every single one'' and check their sizes individually, ''then'' apply whatever size change also individually in order to be consistent. Keeping them as they are intentionally incorporated into the game is much cleaner on both counts. If mediawiki had a "50%" in addition to the pixel resizing, that wouldn't be an issue, but they don't. And applying a same-pixel-size on sprites with different base sizes is just dirty. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 17:04, October 28, 2024 (EDT)
:You're misconstruing my point about math on the wiki. I never suggested curbing the use of math in the back end by editors (even then, I don't recall ever actually mathing my way through editing a page other than establishing sizes of things like images and charts). It was strictly in reference to the math that is displayed, for one reason or another, to readers, specifically how serviceable it is for articles to show readers more complex formulas versus simple tallies of elements in a level. I've long digressed though, lol.<br>The issues you bring up are solvable on a case-by-case basis. I like consistency and tidiness, too, however, those ought to have a healthy marriage with the wiki's primary interest to educate. [[Mario_Kart_Tour_race_points_system#Object interactions|Here]], you'll notice I purposefully enlarged the icon for the Giant Banana item relative to the regular banana peel, because it used to look about the same size, which was odd. I understand where you're coming from and I support giving a sense of scale to sprites of a certain type in a row if it would otherwise look too messy or unnatural, but I don't believe that has to be enforced among all these sprites indiscriminately. {{User:Koopa con Carne/Sig}} 18:23, October 28, 2024 (EDT), edited 19:03, October 28, 2024 (EDT)
::Well this proposal isn't about "all sprites," it is specifically about icons within a particular family, ie, all MKDD character select icons are one family, all MKDD item icons are another family, all MKW select icons are yet another family, etc. etc. etc. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 18:30, October 28, 2024 (EDT)
:::I understand. That's what I meant when I said "sprites of a certain type in a row". That's a tad wordy, so I guess "sprite family" can indeed be used for the purposes of this proposal instead. {{User:Koopa con Carne/Sig}} 18:59, October 28, 2024 (EDT)
::::OK so.... what is the negative you are seeing to this? It seems like you agree with what the proposal actually aims to do, so I'm not really understanding your opposition. It's like how "don't optimize images with color-changing metadata" is a rule - most people can't tell the difference, but it affects the accuracy and presentation, so that's why that rule is in place. This is also for the "accuracy and presentation" reasoning. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 19:07, October 28, 2024 (EDT)
:::::What I agree with, is that assets extracted from the game shouldn't be tampered with before they are uploaded on the wiki. The native size and optimizations should still inherently be part of the asset. What I disagree with, is that such a principle should extend to their presentation on mainspace articles. An image gallery is not a sprite sheet, it's '''demonstrative'''. If you think a gallery of assets can benefit from a few fine adjustments to accommodate scale and aesthetic sensibility, by all means do it. I agree the Shy Guy icon you show in the proposal looks too large and should be scaled down a little, as I did with the giant banana I mentioned previously. Enforcing the standard you propose across a demonstrative gallery is shifting the priority on technical accuracy. {{User:Koopa con Carne/Sig}} 12:19, October 29, 2024 (EDT)
::::::The actual argument of this proposal is different from the last one. This isn't specifically aiming for native dimensions, though that would still be the "easy way" imo. This allows for cropping as long as the cropping is to a consistent size for said related assets. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 12:40, October 29, 2024 (EDT)
 
{{@|UltraMario}} - You... ''do'' realize that ''cropping'' the files is where the "tampering" comes into play, right? If they're displayed as they are in the game, they are ''un''tampered with. Cropping them down is, by definition, tampering with them. I think you need to reword that. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 17:07, October 28, 2024 (EDT)
 
{{@|Fun With Despair}} - Except most of them are ''already'' like this - this is just making an unofficial rule we've used for years an official one for practicality. In this case, doing the ''opposite'' would be busywork. And making them consistent is busywork I am willing to ''do''. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 17:35, October 28, 2024 (EDT)
:Besides, being a lot of work hasn't stopped [[MarioWiki:Proposals/Archive/68#Require citations for names in other languages|proposals that take even more work to implement]] from passing. It's a flimsy reason to oppose a change. {{User:Hewer/sig}} 18:02, October 28, 2024 (EDT)
::Not opposing because it's a lot of work, opposing because it's a lot of work in service of something that is unnoticed and not cared about by the vast majority of users. The citation proposal is a bad example because that is actually something important to the accuracy of information on the wiki. This doesn't do much of anything at all besides force small edits to many old images.--[[User:Fun With Despair|Fun With Despair]] ([[User talk:Fun With Despair|talk]]) 18:33, October 28, 2024 (EDT)
:::That could be said about proposals in general. If it doesn't matter to you, wouldn't it make more sense to not vote at all? If I see a proposal on a subject I don't care about, I just don't vote. After all, if it matters to ''someone'', it matters in general and shouldn't just be opposed because of what amounts to "I don't care about this." [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 18:36, October 28, 2024 (EDT)
:::I'd argue a majority (or at least significant number) of readers likely don't care either way about citations for names in other languages. But that doesn't mean people who do care about the change don't exist, or that it's inherently a bad change. I think "eh who cares" is also a flimsy reason to oppose a change. {{User:Hewer/sig}} 18:38, October 28, 2024 (EDT)
 
Wait, so if this is already often the way things are, will the oppose option change that? That would mean this proposal lacks a "do nothing" option. {{User:Hewer/sig}} 18:07, October 28, 2024 (EDT)
:Oppose is a "do nothing." I'm not going to include an option for what I would consider a ''negative'' change. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 18:28, October 28, 2024 (EDT)
::Wasn't suggesting you should, just got confused since you were making comments about "doing the opposite". {{User:Hewer/sig}} 18:31, October 28, 2024 (EDT)
:::That was mainly directed at the "too much work" argument. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 18:32, October 28, 2024 (EDT)
 
{{@|Camwoodstock}} - Things like the TTYDr bestiary images are not covered by this proposal, only small icon sprites that are intended to be square anyway. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 19:46, October 28, 2024 (EDT)
:For the record, we know that wasn't exactly what the proposal was targetting, we mostly mentioned it as it's a pretty striking example of how including these transparent margins in the images themselves can backfire (besides, it's one of the most recent examples of such a thing happening.) We hope that makes sense, anyway. {{User:Camwoodstock/sig}} 19:48, October 28, 2024 (EDT)
::I still don't see why it's preferable to be forced to use the HTML to make them somewhat close-ish to accurate when simply letting it have the one or two columns of blank pixels that it's supposed to have on one side of it would look better for practical reasons anyway. It's a lot simpler and doesn't hurt anything to do. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 19:52, October 28, 2024 (EDT)
:::Because sometimes, you ''don't'' want them to be entirely accurate; while an original-resolution image might be wanted for, say, a gallery or a table, in an article, template, or especially in an infobox, you probably don't want the original size and would want something a lot more readily scalable, without transparent margins baked into the image that you need to futz with. At best, it would be too small to add a proper caption to; at worst, you basically gut the clarity of the image itself. For example, while not an "icon" in the sense of the original proposal, the articles for various objects from [[Super Mario Land]] upscale the images outside of their original context. Infoboxes on articles such as the [[Lift Block]] would be rendered borderline incomprehensible if the images were not enlarged like this. And the grown image size is accomplished not via baking it into the files themselves, but via using fairly basic wikiscript or HTML; that way, on the main article, they can still appear in their original format. This general philosophy applies to icons as well, which is why we bring it up.<br>Again, if someone was looking for the raw, unedited sprites, they would likely head to The Spriter's Resource and not us; our goal here is to make these images accurate, of course, but we need to make them both usable in articles and also keep them standardized between one another; baking transparent margins into the images themselves, even if technically accurate to the source material, does run counter to that latter goal. {{User:Camwoodstock/sig}} 21:09, October 28, 2024 (EDT)
::::There are plenty of instances where we'd have to edit ripped textures anyway because they're ripped rotated or flipped. Cropping to content is similar to those nondestructive edits and I still fail to see how it's such a big issue, we don't need to preserve transparent pixels just because image editors deliberately padded out assets just for the game engine to decipher properly. Otherwise we should upload sprites without any color data and their palette data as separate entities. {{User:Ray Trace/sig}} 21:15, October 28, 2024 (EDT)
:::::It's destructive to me. ._. Also, saying "zero" readers is obviously wrong if there's people supporting this. "Who cares" is never a good argument. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 22:10, October 28, 2024 (EDT)
::::{{@|Camwoodstock}} - Boosting them by a consistent size factor (like 50%, 200%, 300%, etc) is perfectly fine - Lift Block, for example, is sized up by 1000%. And it's a lot easier to do that when they have consistent base dimensions so you don't have to look the specific dimensions to resize them by for each image separately. Having all the 32px images display at 64px is a lot simpler than having to look through each to see which needs to be at 64, which needs to be at 62, which needs to be at 58, and so on. That's pointless, tedious, and can be prevented completely by doing what this proposal aims for. And again, non-consistent size factors, like "just make them all display at 50px!" are really messy - see the ''Mario Power Tennis'' example above, and how Shy Guy's icon is ultra pixelated while Bowser's is fairly crisp. It's grossly inconsistent, and on a table, it can't just be rawsized with a percentage (and rawsize in galleries only works for making them ''bigger'', not ''smaller''). [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 00:45, October 29, 2024 (EDT)
::I was the one who uploaded these bestiary images, and I had a few reasons. The main one is that some images like Smorg are cut off by the borders and would look strange when cropped. Also, since each of the Tattle Log images display against a border and background that I was also able to rip, I was hoping we'd be able to fit the enemy images over the background and border so it'd be more accurate to how it appears in-game. {{User:Scrooge200/sig}} 20:30, October 29, 2024 (EDT)
 
By the way, a striking example of ripped assets that are extremely counterpoint to this proposal are the [[Mario_Party:_Island_Tour#Spaces|Mario Party: Island Tour]] space icons. Every single one of those icons are cropped from a single texture that compiles all of them, absolutely requiring you to crop images and then crop to content because none of the options suggested that would "encourage" them cover those instances. Hence why I think it's extremely pertinent to encourage crop to content except for formatting purposes in regards to tables. In addition, icons ripped may also come with engine gamma-fixes or even be outright flipped or rotated all which require correction in display for browsing purposes. {{User:Ray Trace/sig}} 21:10, October 28, 2024 (EDT)
:Hence "when applicable to their origins". As that one is done differently, it is not applicable. {{file link|MK8DX-BCP audience TVV.png|This texture}} was stored in a similar manner with all eight of its frames in a single image (evenly spaced), while there's also {{file link|MKAGP audience.png|this group texture image}} that has someone sideways. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 22:06, October 28, 2024 (EDT)
 
Some important things to note:<br>
'''1.''' The proposal only applies to icons that have a natural similarity, such as characters, items, board spaces, badges, etc. It does not apply to textures, screenshots, logos or scanners.<br>
'''2.''' In fact, the wiki and the TSR do not have the same purpose. The wiki is not a graphics museum, nor does the TSR have informational content. But this has nothing to do with what the proposal suggests is the organizational factor.<br>
'''3.''' "Who cares?" Yes, the readers and Super Mario enthusiasts who visit the site every day may not care. But the proposal is not for them. After all, are they the ones who vote here? The proposal is for the editors, for those who submit images and create galleries. Approving this would only be a way to better organize what is already common practice.<br>
'''4.''' This prevents things like {{file link|M&S2014 Mii Costume 55.png|it}}.<br>
[[User:blueberrymuffin|blueberrymuffin]] ([[User talk:blueberrymuffin|talk]]) 17:44, October 29, 2024 (-03 UTC)
:What constitutes as an "icon" is entirely arbitrary in terms of graphics, there is technically no difference between graphics HUD of a character's disembodied head in a map and images used as flair in menus, or images of items in say Mario Party 4, or little images in the group photo in ''Mario Superstar Baseball''. As for the "who cares" statement, that's specifically why I voted to oppose: '''I''' don't care about what this proposal wants to implement, I think it's way too draconian for the purposes of this wiki, and I am having my voice heard, and there is a discernible amount of people who share that sentiment. ''Editors use this wiki too''. I also don't see the issue with the cropped Mii suits, MediaWiki has the tools to format those images should they be formatted. {{User:Ray Trace/sig}} 23:18, October 29, 2024 (EDT)
::"MediaWiki has the tools," does it? Please tell me how, using the <nowiki>[[File:xxxxxxx.png]]</nowiki> type of image, you can implement a resizing of, say, "50%" rather than individually going in and checking the pixel dimensions and dividing it by two yourself. As far as I am aware, you cannot, and when there's 70 or so images all with different dimensions, that's adding a needless amount of tedious work when the obvious solution is to give them the same dimensions in the first place so it only needs done for ''one'' value. And obviously, what makes an icon is determined by whether it is ''used'' as an icon. That doesn't even need said, so I don't know where you were going with that. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 00:29, October 30, 2024 (EDT)
 
I do not know if this has been mentioned or demonstrated yet, but '''this is what the ''Mario Kart: Toadstool Tour'' icons look in a gallery when rawsize is integrated''':
<gallery class=rawsize>
MarioMPT.png
Luigi MPT.png
Shy Guy MPT.png
Peach MPT.png
Yoshi MPT.png
DK MPT.png
Bowser MPT.png
WarioMPT.png
</gallery>


Agreed. {{User|Pokemon DP}}
and this is what they look like when it is added to '''the gallery as laid out in this proposal, with heights and widths set to 72'''.
<gallery class=rawsize heights=72 widths=72>
MarioMPT.png
Luigi MPT.png
Shy Guy MPT.png
Peach MPT.png
Yoshi MPT.png
DK MPT.png
Bowser MPT.png
WarioMPT.png
</gallery>
I do not know if this is apparent in all displays, but Donkey Kong and Bowser are smaller than they should be in the second row. This is happening because the dimensions set for the gallery (72) are smaller than the dimensions of the sprites for DK and Bowser. '''When the heights and widths are changed to 79 (the pxl height of the biggest sprite), it looks like this''':
<gallery class=rawsize heights=79 widths=79>
MarioMPT.png
Luigi MPT.png
Shy Guy MPT.png
Peach MPT.png
Yoshi MPT.png
DK MPT.png
Bowser MPT.png
WarioMPT.png
</gallery>
I do not know if has been alluded to elsewhere in the discussion or changes anything, but I just wanted to point this out. In galleries, you can use rawsize to accurately display assets to scale as long as their are no dimensions set for the gallery, or the dimensions set are larger than the largest sprite. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 20:04, October 29, 2024 (EDT)
:But you can't ''shrink'' them or use that outside of galleries, so it is not a solution to the primary issue of "it screws up table cell widths and heights," and "you'd need to go in and resize each individually on a table since mediawiki doesn't have a percent-based standard image-resizer, only a pixel-based one, and that's an unnecessarily large amount of work and added HTML for adding proper-sized bounding boxes separately, needlessly bloating the page's byte count when the easy, practical, and obvious solution is to just upload them with the intentional shared dimensions in the first place." [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 00:26, October 30, 2024 (EDT)
::I honestly feel these are valid points. I found instances where it is easier to us certain assets in tables when they are all squared in dimension, and I personally have not heard persuasive reasons why easy integration into templates or tables should always take a backseat to their presence in galleries since we are primarily a resource to be read. Not just browsed. However, this is again a case where I feel allowing users to exercise discretion would be better than a rule. For example, I agree that squaring the ''Double Dash!!'' icons is nice, but I don't know how that really benefits the display for the ''Mario & Sonic'' Mii costumes.
::For clarity, I would not support a proposal that insists we must always crop to content. I understand assets are not always restricted to galleries, and tables and templates are often setup with reliable size parameters. It is generally easier to edit an asset once rather than adjust all the tables it appears to ensure it is displayed in a preferred way, and while cropping to content is nice, I do not personally think it really "ruins" the display in a gallery if one or two assets are out of alignment with their neighbors or look smaller in preview. I at least do not think it is so unsightly that cropping to content should be prioritized over their utility outside of galleries. Users should have the ability to exercise discretion. It remains an important part of making this a communal space. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 02:28, October 30, 2024 (EDT)
:::Keep in mind the proposal is not specifically about keeping the original dimensions, it's more about consistency - cropping can occur as long as that too is consistent. And if an icon is completely unique and not part of any "family" with other ones, then it doesn't matter. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 02:36, October 30, 2024 (EDT)


I'm not suggesting a page for each costume, that's just silly. I'm proposing a SINGLE PAGE. Just to clarify. {{User|huntercrunch}}
{{@|Doc von Schmeltwick}} I think you're missing the point the opposition here or in the previous proposal is trying to make. As far as I'm aware, no one's saying "never do this". It's already done on the wiki, and it's good when the circumstances call for it. I don't think the ''Diddy Kong Pilot'' example you posted is that bad but it's definitely better at the consistent dimensions, and I don't see anyone here clamoring to crop down the ''Double Dash'' icons either. What I take issue with, and I assume many of my fellow voters feel the same, is this proposal's goal to essentially enforce that across the wiki whether it's helpful and wanted for design purposes or not. The ''Mario Power Tennis'' icons you used as an example aren't currently used anywhere on the wiki where inconsistent dimensions actually matter. I assume the [[Mario_%26_Sonic_at_the_Sochi_2014_Olympic_Winter_Games#Costumes|''Mario & Sonic'' Mii costumes]] would also get caught up in this since they're technically icons, but in my opinion, consistent sizing is unnecessary and the images look worse with the extra space needed to accommodate the largest costumes. At the very least you can't say it looks objectively worse that they're not all centered in this case. You've mentioned having OCD several times in these types of discussions, so I recognize and sympathize that some of these inconsistencies can be frustrating for you, but your personal preferences and irritations aren't always going to reflect the majority of the userbase.


==Removals==
Also, the reason rawsize keeps getting brought up is because ''you'' were the one who started this proposal with a comparison of images in galleries and made it seem like a key point of your proposal. I'm not sure why you did that, and it feels misrepresentative of the situation at best since [[MarioWiki:Proposals/Archive/68#Expand_use_of_.22rawsize.22_gallery_class|you were the one who proposed its wider usage a few months ago]] and should've known it was an easy solution to the specific problem you were presenting. --{{User:Waluigi Time/sig}} 14:59, October 30, 2024 (EDT)
''None at the moment.''
:I know I proposed that addition. I mainly used a gallery as an example here because it was convenient to bang out quickly, not at an illustration that it is the only issue brought on by this. In regards to making it a rule though, please recall I am not stating here it "has" to be the native dimensions specifically. Also, we have other image upload rules that some people and/or wikis might consider "draconian" but have been around long enough here that they make perfect sense to us (don't upload non-animated .gif's, don't convert .jpg's to .png's and especially don't give them transparency, don't optimize images with metadata, and the above proposed one with currently unanimous support regarding NES palettes), so I really don't see how this ends up any different. I specifically noted in the proposal and its very title that if it straight-up doesn't work in whatever context, that it doesn't need done for it, so I don't see how it ends up as a problem anyway. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 15:58, October 30, 2024 (EDT)
:: This unfortunately contributes to the same problem I had with the previous proposal. Your reply here makes it sound like there would be no substantive or practical difference between how folks generally handle assets already, making it unclear what would actually change if the proposal were to pass. What would change? — [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 16:42, October 30, 2024 (EDT)
:::Because when I tried to enforce "how folks generally handle assets already" it was treated as me going notably out-of-line. There's always gonna be ''someone'' who uploads a .jpg -> .png image because they don't know any better or don't realize it (I'm guilty of the latter from before I knew to check with the "save image as" function), and that needs to be corrected - it is how we "generally do things," but we do it because that is a thing that needs discouraged, hence there being a rule. I see this as no different from that. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 18:52, October 30, 2024 (EDT)
::::This proposal is just going to result in a patchwork of interpretation of how to approach these assets. It's a sign of a very flawed proposal. Doesn't help that your entire bedrock of reasoning that led to this kind of proposal (that we should be encouraged to maintain the original dimensions of a ripped sprite), which I have deemed utter nonsense and I stand by it being utter nonsense, continues to be maintained. This leaves me with a not very confident impression you have any clue how these assets are created, stored, and used in a video game, that you understand ''why'' an asset is padded and has dimensions of 128x256 or something and ''why'' this doesn't mean a wiki should be necessarily maintaining these dimensions. {{User:Mario/sig}} 00:33, October 31, 2024 (EDT)
:::::I have explained time and time and time and time and time and time again that ''this'' proposal ''does NOT'' require the original dimensions. Just ''shared'' dimensions. I figured putting it at the top in '''{{color|purple|ALL-CAPS BOLDED BRIGHT PURPLE}}''' would be enough to get people to actually read and realize this, but apparently not. Please acknowledge this and stop treating it as though that is my argument here when it is ''not''. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 01:02, October 31, 2024 (EDT)
::::::Let me clarify: when I mentioned the bedrock of reasoning, I meant to contextualize the situation that led up to the proposal. It's to support my criticism of your proposal, which was made in response to the earlier one that was canceled from mounting opposition, that this follow up proposal is poorly made. Due to the timing of things, it comes off as an attempt to simultaneously continue your practices of insisting that image dimensions are important information to maintain (they are not) but with flawed solutions designed around this flawed principle. To me, this is a confusing proposal that will lead to conflicting approaches to how an asset will be handled, and the examples used don't do a great job clarifying points (this example shouldn't even be a table imo). {{User:Mario/sig}} 02:04, October 31, 2024 (EDT)
:::::::They absolutely are, but regardless of that, if it ''wasn't'' a table and were instead a gallery, the OCD-triggering vertical position issue would be even worse. (Seriously, I'd get less feeling of disgust from an animated loop of Wario puking up an endless stream of black dioxic squid ink onto Penny than I get from this - hell, that wouldn't even be half of it. This is trypophobia-level shit here.) In regards to that edit you made to your vote, obviously non-icons are completely unrelated to this. I worded this as specifically as I could to avoid it being abused. This is for icons and icons alone, and by "game-related," I mean such as "MKDD-related" or "MPT-related" to determine which group gets which parameters. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 02:21, October 31, 2024 (EDT)


==Splits & Merges==
::::I think there was some misunderstanding amongst parties after the previous proposal was cancelled. I at least do not think anyone intentionally meant any harm. The impression I have is that a lack of familiarity with certain tools lead to some bad-faith interpretations of why folks did the things that they did. But regardless, I think a gentler, less heavy-handed approach to these types of things would be better going forward. I do not think this needs to be strict policy, or something staff and other users need to enforce. But generally, as a courtesy, if one wants to adjust assets that are being used in particular fashions outside of galleries, it does not hurt to reach out and ask if it would be okay to adjust their dimensions. And if a user cropped material, one should not invoke rules that do not exist as actual policy, or bring up some "innate" sprite-ripping principals that do not exist. (I understand the point of this specific proposal is to make certain rules concrete, but I am referring to some of the interactions I saw between users before this current proposal was raised.) Rather, there is no harm in explaining why it is helpful to keep certain assets at particular dimensions for tables and templates. I know some folks have mentions CSS coding, but no one has bothered explaining what that would look like, and generally, adjusting the empty space around an asset is the most user-friendly and intuitive path to take. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 01:28, October 31, 2024 (EDT)
===Merge Super Mushroom to Mushroom===
I think we should merge the [[Super Mushroom]] article to the [[Mushroom]] article. Why? They're almost THE SAME! I mean, look at the beginning phrase of the Super Mushroom article. It says: "A Super Mushroom is a red Mushroom that allows whoever eats it to grow to an enormous size". The normal Mushroom is also red and also will you grow. However, the Mushroom have some other effects in other series. But, notice the images on the Super Mushroom article. You'll see an artwork of ''[[Mario Kart Super Circuit]]''. But in other Mario Kart games, it's called Mushroom. Also, the [[Golden Mushroom]] was sometimes called Super Mushroom. In SSB series, they are called Super Mushrooms, but they are still the same.


I also readed on the Super Mushroom article that a Super Mushroom appeared in ''[[Super Mario 64 DS]]'' that will let you grow. But on the Mushroom article, there stands information that has the same meaning. And there was only ONE red-capped Mushroom in that game! So both articles has information about the same item.
@SeanWheeler: I believe the proposal is just for the icons within a particular "set" to be consistent with each other, not icons of different sets. {{User:Hewer/sig}} 08:46, October 31, 2024 (EDT)


So, now I told enough information from why we should merge the Super Mushroom Article to the Mushroom Article. When we have merged, we can maybe (I say "Maybe") make a Disambiguestion page with the name "Super Mushroom" (I told that the Golden Mushroom also sometimes was called Super Mushroom).
{{@|Killer Moth}} - See the ''Diddy Kong Pilot'' table above and the alignment issues it had before I enacted this principle on it, and how it's much more eye-pleasing afterward? ''That'' is the point. Without it, they tend to look gross - like that table did before. If you can't see why that's an issue, then I envy you, but it really looks bad - the version with the alignment lines is how ''my'' eyes see it even when they aren't there. And I have still yet to see any actual downside to this other than people trying to cram them into signatures, which is... not what the wiki is about and that absolutely should ''not'' take priority in presentation. Same reason we don't add fake armbands to Bowser's SMB1 sprite since that's transparency. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 12:50, October 31, 2024 (EDT)
:Again, the dominant perspective of the opposition is '''not''' "no, this is a bad idea. No one is allowed to set up assets to make them aligned as they appear in the ''Diddy Kong Pilot'' table." Personally, I think the ''Diddy Kong Pilot'' example you provided is aesthetically pleasing when the sprites are all aligned, and folks should have the freedom to do that. It is for similar reasons that I integrated organized 100x100px sizing for all images in the mainline game tables and try to ensure columns are the same width across all tables in an article. Rather, the oppositional perspective is, "no, we do not want to police this or make this a type of rule. People should have the freedom to experiment with what types of dimensions they want for the assets used in their tables, and we do not agree that cropping to visual content is inherently destructive of an asset." - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 13:11, October 31, 2024 (EDT)
::I feel doing this is an absolute good, and if someone has the freedom to crop, I have the freedom to restore. Two-way street and all that. Also, LGM's argument from what I can tell is exactly that (which coupled by the general belligerent/caustic directing of profanity towards it) fueled most of this. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 13:57, October 31, 2024 (EDT)
:::I respect that you view a policy revision like the one advocated for in this proposal is an "absolute good," but I do not think you have made a compelling persuasive argument as to why, or at least not one to me. And I understand your concerns over a "two way streak," but we do have [[MarioWiki:Courtesy|courtesy policies]] on this wiki. Many of them seem relevant, but the one I would like to highlight is that '''users should not participate in other users' editing projects without asking them first'''. Galleries are more of a shared neutral space, but if one wants to crop to content or retain space around ones that are integrated into tables in a spatially-dependent way, it would be courteous for one to reach out to the uploader of those assets first or at least touch base with them. The ''Mario Power Tennis'' ones, for example, have only been integrated in [[Mario Power Tennis#Participants|one table]] at the time of this comment and cropping them does not seem to have impacted the layout or scaling in any perceivable way to me. There was no demonstrable harm.
:::I do not think LGM is advocating that arranging tables like the one in the ''Diddy Kong Pilot'' example should not be allowed, or at least that is not my reading of her comments. I believe her perspective is not dissimilar from mine. I would personally appreciate it if you reviewed what I wrote in my vote above. I think it would be clarifying.
:::I could be wrong, but I believe the curtness comes from statements you had included in the previous proposal that, from her experience as someone who also rips assets and someone who participates on this wiki very regularly, she knew were objectively false, but you were presenting them as hard facts and even invoking them to talk down to another user. This is understandably not appreciated conduct, and it is not uncommon from you. She can speak more to that if she wants to. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 16:13, October 31, 2024 (EDT)
::::The statements I made then were accurate too, our perspectives are just completely incompatible. And considering in the cases of those Mii costume images, here, the original uploader (who is supporting this proposal) explicitly wants to keep them they way they were uploaded in, which is what I reverted them to, and LGM is reverting them from. The specific thing she has said that I take issue with is her claim that the space is absolutely worthless and should be removed from everywhere it feasibly can be, which naturally I perceive to be extremely misguided. As for the ''Mario Power Tennis'' table, it only looks as good as it does thanks to my own ingenuity of hiding a cell divider bar to make two cells look like one cell - that table is ''the'' one that has given me trouble in that regard. Presumably if they are changed to a tabular form, those icons will remain useful if we start covering rivals for it like we do for the 64 game, but by then it'd be easier if they did share parameters. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 16:39, October 31, 2024 (EDT)
:::::Maintaining space needs to be done for a good reason, and having it simply because it was ripped that way ''is not a good reason''. It is okay to find an example where extra space is needed but that table provided is a heavily flawed example due to being an inappropriate use of a table and the suggestion below that does fix the issue to begin with (and probably there is a code for horizontal alignment too). As for Mario Power Tennis table, if you're referring to this one[https://www.mariowiki.com/index.php?title=Mario_Power_Tennis&oldid=4392103#Participants] that's another fundamentally flawed table which was one of the many other tables that prompted criticism by multiple users and would not be my example to try to illustrate a proposal. The ''one'' example I think may work is [[:File:MK8 Mario Icon.png]] due to its use in multiple pages and being in an array with similar scaled images, which were all put in a 128x128 box. Not sure if cropping to content is going to lead to unexpected results but for the record, I don't see the point of cropping to content for these Mario Kart 8 things either, since they're already reasonably occupying the space (unlike those Mario Kart Double Dash map icons which were heavily padded); it's a case of don't fix what isn't broken. The proposal doesn't really advocate any of this. It's, what I can glean, a way to maintain aspect ratio while cropping tightly as possible without losing information, but dressed up in bad examples and imprecise wording (like the proposal does not even define what a "game-related 'icon-type' image" is, so). {{User:Mario/sig}} 20:56, November 2, 2024 (EDT)
::::::I was more referring to how the N64 Mario Tennis had a separate "partners/rivals" table before I incorporated that information into the main character table, and it used the face icons. I was saying if MPT did something similar, which it probably should if there is indeed a hard-coded system like that in the game. I don't really think I need to define the icon thing; but if you insist, I mean "icon" as in "a small image representing a subject," with "game related" simply meaning as a per-game basis (ie, MK64 icons have no bearing on MKDD icons). (Also, off-topic, but how else would the ''Diddy Kong Pilot'' example be handled if not as a table? There's other information below it that's been cropped out.) [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 21:52, November 2, 2024 (EDT)


Sooo...
The ''Diddy Kong'' example, too, can be easily fixed with aforementioned styling, in this case by using <code>vertical-align: bottom</code>. That is to say however that those sprites are of a size where it makes sense for all of them to just retain their original size, I would not crop those either. There are cases like the Mii suits from the other day where it does make sense to crop them. {{User:Lakituthequick/sig}} 17:14, 31 October 2024 (UTC)
:Not all of them have flat bottoms in other games, of course, while that also doesn't fix the left-right issue. But yes, I digress. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 13:57, October 31, 2024 (EDT)


Do you also think that the Super Mushroom article should be merged to the Mushroom article? Or do you think of NOT?
Another thing I want to ask the opposition: if {{file link|058-SMMMontyMole.png|this}} is to not be cropped, why should any of the other things? [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 19:24, November 6, 2024 (EST)


'''Proposer:''' {{User|Arend}}<br>
===Allow unregistered users to comment under talk page proposals===
'''Deadline:''' May 23, 2008, 20:00
One thing I never understood about rule 2 is why unregistered users are not allowed to comment under proposals. The rule states: "Only registered, autoconfirmed users can create, comment in, or vote on proposals and talk page proposals." While it makes sense on this page, it is semi-protected after all, talk page proposals are a different story. Why should IPs be prevented from commenting under talk page proposals? Most IPs are readers of this wiki and they should be allowed to express their opinion on wiki matters too. I've seen several examples of IPs making good points on talk pages, I imagine most of them are regular visitors who are more interested in reading rather than editing, and allowing them to leave a comment under a TPP would only be beneficial.


==== Merge the Super Mushroom Article! ====
If this proposal passes, unregistered and not-autoconfirmed users would be permitted to comment under talk page proposals. They still wouldn't be allowed to vote or create proposals, only comment.
#{{User|Arend}} What do you think? I'm the proposer!


==== Don't Merge it! ====
'''Proposer''': {{User|Axii}}<br>
#{{User:Stumpers/sig}} I'm opposing because "Super Mushroom" and "Mushroom" are two distinct items in many (all?) Mario RPGs.  You bring up a very good point which made question my oppose: the two articles do need clean-up.  How to go about doing that for an item that is the same in the platformers but different in the RPGs is a tough question.
'''Deadline''': November 14, 2024, 23:59 GMT
#While I do think some things should be moved from one page to the other, I think that they are things that should have independant articles. Also per Stumpers. -[[user:Canama|Canama]]
# [[Ninjayoshi]]: Per all.


==== Comments ====
====Support (unregistered users proposal)====
#{{User|Axii}} Per proposal.
#{{User|Hewer}} Wait, this was a rule?
#{{User|Pseudo}} This rule doesn't really seem like it accomplishes anything.
#{{User|Blinker}} Per proposal.
#{{User|FanOfYoshi}} Why wasn't this already applicable?
#{{User|EvieMaybe}} it makes sense if it's just for comments
#{{User|Drago}} The rule was only [[Special:Diff/1858371|changed]] because of this page's semi-protection and not, as far as I can tell, because of any misuse of comment sections by unregistered users. Per all.
#{{User|ThePowerPlayer}} This is a reasonable change.
#{{User|Dine2017}} Per proposal.
#{{User|Ray Trace}} Anons use the wiki too and should be able to voice their concerns in the comments section, there's no reason to bar them the ability to comment.
#{{User|Mario}} We'll see if the Bunch of Numbers behave.
#{{User|Nintendo101}} Per proposal.
#{{User|Killer Moth}} Per proposal.


==Changes==
====Oppose (unregistered users proposal)====
===Limit Images from the Same Game===
#{{User|SeanWheeler}} Unregistered users just have numbers for their names, so that looks awkward with the way the votes are counted. It's easy to use your IP to sockpuppet, so I wouldn't want anyone doing that for the votes. And even for just the comments, I wouldn't want anyone to sockpuppet in an argument for manipulation tactics. Nor do I want to see poor grammer or vandalism. Anyone who wants to participate in voting discussions should sign up. This page was semiprotected for a reason. [[User:SeanWheeler|SeanWheeler]] ([[User talk:SeanWheeler|talk]]) 00:19, November 1, 2024 (EDT)
Currently there is no limit for images (screenshots or artwork) ''from the same game'' to appear in galleries at the bottom of articles. In a previous [[MarioWiki:Proposals/Archive 7#Repeated Images|proposal]], {{User|Grandy02}} pointed out the example of [[Princess Peach]], an article which has twelve different artwork images from ''Super Princess Peach'' in the [[Princess Peach#Official Artwork|gallery]]. In my opinion, this fails to serve the purpose of galleries, that is to show the development of a character (more precisely, his or her appearance), because there's too much importance attached to just one game. Therefore I propose to limit the number of images from one and the same game in galleries to '''three'''. This only applies to articles about characters (or species, whatever), not articles about games (those may have more than three images of course).


'''Proposer:''' {{User|Time Q}} <small>(originally brought up by {{User|Grandy02}})</small><br>
====Comments (unregistered users proposal)====
'''Deadline:''' May 23, 2008, 20:00
"While it makes sense on this page, it is semi-protected after all"<br>If the protection history displayed above this page's edit box is any indication, it was the other way around. There was already a rule against anonymous voting on this page by the time it was semi-protected. In that case, it might be useful to look into the reasons this rule was made in the first place and, if there's any disagreement, extend this proposal to this page too. As to where these reasons are stated, I don't know. My assumption is that the rule exists because anons are more prone to shit up the place than registered and autoconfirmed users. {{User:Koopa con Carne/Sig}} 16:15, October 31, 2024 (EDT)
:I couldn't find a reason why IPs were disallowed to comment. My only assumption is that when this page was protected the rule was modified to mention that IPs couldn't comment, but talk page proposals weren't considered. I'll look into it more and potentially add a third option to allow IPs to comment here as well. [[User:Axii|Axii]] ([[User talk:Axii|talk]]) 16:20, October 31, 2024 (EDT)


====Limit of Three Images====
{{@|SeanWheeler}} - This isn't about voting, it's about commenting. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 01:04, November 1, 2024 (EDT)
#{{User|Time Q}}: Per myself.
:For real, do you even read before voting on proposals? It's a small paragraph that makes it very clear that it's only about commenting under talk page proposals, not even on this page. [[User:Axii|Axii]] ([[User talk:Axii|talk]]) 01:07, November 1, 2024 (EDT)
#Per Time Q, including the exception for game articles. --[[User:Pikax|Pikax]] 12:54, 16 May 2008 (EDT)
#[[User: WikiGuest|WikiGuest]] - Per Time Q.
#{{User|Grandy02}}: 3 images already show the character's appearance in the respective game distinctly enough, I'd also accept 4 images, but that's really sufficient enough then. But we should try to use the images taken off the gallery in the fitting articles, so that they won't be deleted.
#{{user|Wayoshi}} &ndash; I was concerned when I read the title of this proposal, but the details told me exactly what the issue is and I agree just in those circumstances, image galleries can be overbearing in main character articles.
#{{User|MegaMario9910}} Per Time Q.


====No Such Limit====
===Decide whether to cover the E3 2014 ''Robot Chicken''-produced sketches===
#[[User:ForeverDaisy09|ForeverDaisy09]] a limit of three doesn't seem to be enough for certain characters such as Mario and Peach.
For {{wp|E3 2014}}, Nintendo's press conference was a video presentation similar to today's Nintendo Directs, featuring [https://www.youtube.com/watch?v=4FgzkZC0reE clips of stop-motion sketches] by the producers of ''{{wp|Robot Chicken}}''. I feel that these qualify to receive coverage on this wiki, since their appearance in a video published by Nintendo means that they are officially authorized, and they prominently feature ''Mario'' franchise characters. However, I have never seen the sketches discussed in any wiki article, nor are they listed on [[MarioWiki:Coverage]], so I thought it would be appropriate to confirm their validity for coverage with a proposal.
#{{User|Cobold}} - Why don't we use reason for a limit? I don't think we need set-in-stone rules which might get in our way. Characters may have different appearances in the same game (such as Peach in Mario Kart Wii).
#{{User|Bob-omb buddy}}.Some pages need to have lots of screenshots,showing different features of the game.
#{{User|Stooben Rooben}} - I have to agree with Cobold. We should all be able to judge what looks right.
#{{User|Stumpers}} Per Cobold.  It seems to me that the ''SPP'' example is the only one really under question. The problem could be more easily solved on the talk page for the article.
#Per Stumps. {{User|Toadette 4evur}}
#Per Stumpers. -[[user:Canama|Canama]]
# [[Ninjayoshi]]: Per all, but the Princess Peach pics from Super Princess Peach are outrageous.


====Comments====
The following articles would be affected by this proposal if it passes (since the E3 2014 video is not a game, film, etc., coverage is best suited to an "Other appearances" section):
Hmm... I think it should be upped to four, as the articles of certain obscure games ([[Mario Bros. Special]], [[Punch Ball Mario Bros.]], etc) could use the images to include more information. But I'm all for limiting the number of images. ;) {{user|InfectedShroom}}
*[[History of Mario]]
:Okay... other opinions? I might change it to four, but only if there are some more users who agree with it. {{user|Time Q}}
*[[History of Bowser]]
::<s>I agree that the Princess Peach article shouldn't have 26 SPP artworks... But I don't think that the limit should apply to games article. I stay neutral.</s> D'oh, didn't read the proposal correctly. {{User|Blitzwing}}
*[[History of Princess Peach]]
:::Huh? What do InfectedShroom and Blitzwing want to say? I thought this is about the galleries for character articles, not about screenshot galleries for articles about single games. {{User|Grandy02}}
*[[History of Wario]]
::::Grandy02, indeed ;) I didn't read InfectedShroom's comment very well either, otherwise I would have noticed that he's talking about game articles. So yeah, this proposal only talks about '''character''' articles. {{user|Time Q}}
*[[Reggie Fils-Aimé]]
*[[Fire Flower]]
*[[Bullet Bill]]
*[[List of implied entertainment]] (In the last sketch, Mario mentions the fictional game ''Mario Ballet'').


Oh, also, since I have a feeling this will go through, I think we should still keep all of the artworks (regardless of amount) on the game pages. [[User:ForeverDaisy09|ForeverDaisy09]]
Regardless of which option ends up winning, a note should be added to MarioWiki:Coverage to explain how these sketches are classified. Also, I'm clarifying that this proposal does not involve any sketches from ''Robot Chicken'' itself, since those are clearly parodies that have no approval from Nintendo.
:I absolutely agree with that. {{User|Time Q}}


Cobold and Bob-omb buddy: You're right, but then again, a limit would avoid putting too much focus on just one game in the gallery. If there is much different artwork of Peach in ''Mario Kart Wii'', what's the point in cluttering the gallery up and deflecting from the other games? As ForeverDaisy09 said, the artwork could be placed in the game article. Three images, in my opinion, totally suffice to show the appearance of a character in a game. {{User|Time Q}}
'''Proposer''': {{User|ThePowerPlayer}}<br>
'''Deadline''': November 16, 2024, 23:59 GMT


Yeah, sorry for the somehow confusing title of the proposal. If you can think of a better name, let me know. :P {{User|Time Q}}
====Support====
#{{User|ThePowerPlayer}} Per proposal.
#{{User|Hewer}} This feels logical enough that I'm not sure it needs a proposal or even an explicit note on the coverage policy, but per proposal just in case.
#{{User|EvieMaybe}} per proposal
#{{User|Tails777}} Some of them were Mario related so I don't see any reason not to mention them. Per proposal.
#{{User|Ray Trace}} Per proposal.
#{{User|Camwoodstock}} At first, we were a bit confused as to why ''only'' E3 2014 was getting this treatment, but it turns out that no, actually, we do mention a few things from E3 presentations and Nintendo Directs in these articles, we just never internalized that information. If we cover [[History of Wario#Other appearances|that Wario animatronic puppet from E3 1996]], and we cover [[History of Bowser#Other appearances|Bowser in Bayonetta 2]], we don't see why we shouldn't cover this specific E3's trailers just because it was by a different producer.
#{{User|Nintendo101}} Don't see why not.
#{{User|Killer Moth}} Per proposal.


ForeverDaisy09, three images '''from each game''' is sufficient for any character, be they as uncommon as Princess Shroob or as famous as Mario himself. --[[User:Pikax|Pikax]] 17:35, 16 May 2008 (EDT)
====Oppose====
:That's a good example of why this is worrying me, actually. Princess Shroob only appeared in one game, so all of the information about her personality (which is established largely though visual action) might be limited to 3/4 images.  I do agree that the massive galleries do detract from articles like Princess Peach, but I really feel that a different solution is needed.  How about this: the current galleries are moved to a page, such as Image Gallery (Princess Peach), and the main Princess Peach article could feature enough images to show her visual developement over the years, something like what you are proposing. {{User:Stumpers/sig}} 17:55, 16 May 2008 (EDT)
#{{User|SeanWheeler}} Robot Chicken is an adult parody show. To cover Robot Chicken in Mario's history is like taking the Family Guy cutaway gags as canon. The Robot Chicken sketches including the E3 specials are covered in [[List of references in animated television]].


==Miscellaneous==
====Comments====
===Trouble Center===
Uh, SeanWheeler? You may want to see [[MarioWiki:Canonicity]]. There is no canon in Super Mario. And being an "adult" show shouldn't prevent text from being referenced in normal articles given the wiki does not censor anything. (The last point on [[MarioWiki:Courtesy]], and the set of arguing over [[Bob Hoskins]]'s page quote.) I guess one could discount the sketches on account of them as parodies, but given the "no canon" bit that seems hard to justify. [[User:Salmancer|Salmancer]] ([[User talk:Salmancer|talk]]) 21:01, November 3, 2024 (EST)
:It's been a hot minute, but aren't the 2014 E3 sketches not even a part of Robot Chicken, anyways? Just produced by the same team behind them. It would be like prohibiting mention of [[Ubisoft]] because they developed those South Park games. And even if the sketches for E3 2014 were particularly "adult", [[List of unofficial media acknowledged by Nintendo#Super Hornio Brothers|overwhelmingly adult content hasn't stopped us before]]. {{User:Camwoodstock/sig}} 09:43, November 4, 2024 (EST)
{{@|ThePowerPlayer}} Looking at these sketches, why not create an article covering them? It would be inconsistent not to cover them separately as well, not just as sections of other articles. [[User:Axii|Axii]] ([[User talk:Axii|talk]]) 13:26, November 4, 2024 (EST)
:The proposal is to cover them in "Other appearances" sections, which are [[MarioWiki:Proposals/Archive/57#Define the scope of "Other appearances" sections|supposed to cover things without articles]]. Also, to my knowledge, they don't exactly have an official title that we could use. {{User:Hewer/sig}} 13:32, November 4, 2024 (EST)
::This is exactly why I brought it up. It would be weird not to have a page on them when all other content does. Lack of an official title never stopped us either :) <br>[[User:Axii|Axii]] ([[User talk:Axii|talk]]) 03:42, November 5, 2024 (EST)
:::My point is that not "all other content" has a page, and that's what "Other appearances" sections are for. I don't think these short, nameless skits from an E3 presentation that are more about Nintendo in general than specifically Mario are really in need of an article when this proposal passing would mean their entire relevance to Mario would already be covered on the wiki. They aren't even the only skits with Mario characters from an E3 presentation, E3 2019 has an appearance from Bowser. {{User:Hewer/sig}} 06:34, November 5, 2024 (EST)
::::Exactly. Making an article would just lead to a lot of unnecessary descriptions of content that has nothing to do with the ''Super Mario'' franchise. {{User:ThePowerPlayer/sig}} 19:44, November 5, 2024 (EST)


On this wiki, there have been many '''Not Taken''' spots in the trouble center. Sometimes, this spot can go for a long time, basically never getting it done. I propose we should make automatic match-ups for troubles. (Meaning, a  user posts up a trouble, and one random user gets to do that trouble.) But of course, the user does not have to do it. If he/she refuses another user gets it. If this was done, much more troubles would get completed.What do you think?
===Require citations for dates===
Recently, a proposal decided that not sourcing a foreign name puts the article into a meta category of "unsourced foreign names". But I'd say a similar idea should be implemented to dates for things such as media releases, company foundations, and game, company and system defunction. Because, for example, there's been many times where I've seen an exact release date pinpointed and I think "where did they get that date from?", and after a bit of research, I can't find any reliable source with said exact release date. Dates being sorted like this would be nice.


'''Proposer:''' {{User|Goldguy}}<br>
'''Proposer''': {{User|Starluxe}}<br>'''Deadline''': November 16, 2024, 23:59 GMT
'''Deadline:''' May 16, 2008, 20:00


====Agree====
====Support====
#Reason stated above.{{User|Goldguy}}
#{{User|Starluxe}} Per my proposal
#{{User|ThePowerPlayer}} Per proposal.
#{{User|Super Mario RPG}} I agree.
#{{User|Camwoodstock}} Wait, how is this ''not'' already policy??? Per proposal.
#{{User|Shy Guy on Wheels}} I personally find that a lot of release dates for games on the internet come from hearsay, and copying what other sites say without actually double checking that info, so this would be great for guaranteeing accuracy.
#{{User|Technetium}} Per proposal.


====Oppose====
====Oppose====
#{{User|Lakitu bros}}The User could be inactive.So the trouble could take a very long time to/never get completed.
#{{User|Stumpers}} Something inherent to any Wiki is that a user cannot be forced to do anything.  So, the chance that the user decided would be one who had it in there ability to fill the trouble and was also willing is very low, even when you cycle through multiple users.  You'll need to get a technical mastermind to confirm this, but I believe the only way we could do this would be through a committee of users doing this by hand.
#{{User|Pokemon DP}} You can't force Users to do something. It's cruel! I actually think the Trouble Center should be removed...
#{{User|Stooben Rooben}} Per all. The trouble center is redundant. 99% of the time, users just ask other users (or Sysops) for help on their talk pages.
#{{User|Time Q}}: Per Stumpers and DP, forcing users to do things is bad. Besides, I also agree that the Trouble Center should get removed.
#{{User|InfectedShroom}} Oh. Now I understand what this proposal is about. :P Per Stoobs. And yeah, the trouble center is no longer used. X_X
#{{User|Glitchman}} I don't think the Trouble Center should be removed, it is useful, but per Stumpers and Lakitu Bros.
#{{User|Cobold}} - The wiki is and stays voluntary work. Nobody is forced to do anything.


====Comments====
====Comments====
Hey, Goldguy: You might want to support your own proposal. ;) {{User|Stooben Rooben}} 18:45, 9 May 2008 (EDT)
What source you think is acceptable for release dates? I personally use GameFAQs. {{User:Ray Trace/sig}} 20:05, November 2, 2024 (EDT)
:GameFAQs isn't officially related to Nintendo, right? If so, then no. It needs to be an official source. Because if anything, GameFAQs' release dates could be taken from another unofficial source, making that an unacceptable source. {{User:Starluxe/sig}} 13:00, November 6, 2024 (EDT)
::But that is a major problem of mine regarding old games, especially those that came out before the internet. Game sites such as GameFAQs and Wikipedia have it down all the time, especially those as old as GFAQs, but I don't think Nintendo themselves keep track of it too much barring recent titles or titles they are currently selling, with rare cases of them citing release dates in games themselves (like Super Smash Bros. Brawl's chronicles). For example, Wikipedia does cite Mario Kart: Double Dash's release date in a financial statement by Nintendo but other games such as the original Thousand Year Door's release dates remain unsourced. I'll need an answer to what sources you plan on using to cite the release data. {{User:Ray Trace/sig}} 18:28, November 7, 2024 (EST)
:::This has come up [[Talk:Donkey Kong (game)#Arcade release dates|a]] [[Talk:VS. Super Mario Bros.|few]] [[Talk:Donkey Kong Country 2: Diddy's Kong Quest#NA release date|times]], but the state of proper video game release date archival is dreadful. I would argue it was around the time of digital storefronts that they were catalogued more seriously. I really want to support this proposal, but first, I think it's really important to decide what type of sources are usable. Sites like GameFAQs and MobyGames? They're actually user-contributed, in theory, I guess. You can contribute there. The problem is that I don't know anything about their curation. Unlike a wiki, you can't look back. Someone can contribute something else that overrides your contribution, and you won't know why (probably something to the effect of "another online source"). So, I wouldn't take sites like them, despite search results doing a good job of making sure they're one of the first things you see. Wikipedia has taken to citing the copyright office, but as far as I know, details like that are not always the same thing as an actual release/airing date. My suggestion is that this needs a whole source priority of its own, preferably contemporary sources like magazines and press releases. [[User:LinkTheLefty|LinkTheLefty]] ([[User talk:LinkTheLefty|talk]]) 08:24, November 8, 2024 (EST)


Honestly, I agree with DP. This mess has been around long enough. I've had two proposals about this already. I still think they way we did it before the Trouble Center was better.
Seeing how this could also apply to other things like defunction dates, I've added so to my explanation. {{User:Starluxe/sig}} 12:16, November 7, 2024 (EDT)


For those who don't remember those days, we just created a challenges page for each user and other users randomly added sets of challenges for the user to complete. We got a lot more done then than we do now. -- {{User|Ghost Jam}} 02:11, 10 May 2008 (EDT)
===Move "Princess Peach" and "Princess Daisy" to "Peach" and "Daisy"===
Earlier this year, I made [[Talk:Princess Daisy#Move to "Daisy"|a proposal]] suggesting that the article "Princess Daisy" should be moved to "Daisy". That proposal was rejected, with one of the main reasons being that people were concerned about the inconsistency this would cause with Princess Peach. Since then, [[MarioWiki:Proposals/Archive/60#Remove "Koopa" and other name particles from Koopaling article titles|another similar proposal]] has passed that suggested moving the Koopaling articles to just their first names. So, I would like to suggest once again that I think "Princess Daisy" should be moved to "Daisy", except that this time I'm also including the option to move "Princess Peach" to "Peach".


Yeah. The old way is normally the right way. {{User|Pokemon DP}}
This proposal is ''not'' suggesting that we stop using these titles for these characters ''completely''. We should continue to do as we have done: use whatever name is used in a specific work when talking about a character's appearance in that work. I am only suggesting that the articles themselves be moved to "Peach" and "Daisy", which I believe to be their ''primary'' names.


NO!That's not what I meant.Any user can refuse until one user takes it.{{User|Goldguy}}
====The case for moving Daisy's article====
:But do you think any user is really gonna want to do that? Everyone will refuse. Having users get to choose things is the way to go. I don't think I'll vote, though, because I don't really know anything about the trouble center. {{User|CrystalYoshi}} 18:26, 11 May 2008 (EDT)
You can read my full argument for Daisy in my previous proposal about this subject, so I'll be brief here. My key point is that '''Daisy has never been called Princess Daisy in any game as her primary English name'''. It's certainly not an ''un''official title by any means, but she is and always has been called "Daisy", with no honorific, considerably more often and more prominently than her full title.


=== Mario Kart Wii Karts and Bikes ===
====The case for moving Peach's article====
Mario Kart Wii Karts and Bikes have different names in the North American and the PAL versions of the game. Currently, the pages are called like e.g. [[Sugarscoot (Bon Bon)]], the first being the NA name and the second the PAL one. I am under the impression that we never used both names in one article name, and it also isn't needed. I think it is enough to simply state the PAL name in the article itself, and leave the NA name in the article title.
The case for Peach is much weaker than the case for Daisy. Unlike Daisy, Peach is actually called by her full title in-game as her primary English name sometimes. In fact, as was pointed out in the comments of the previous proposal, Nintendo has [https://play.nintendo.com/activities/puzzles/jigsaw-puzzle-princess-peach-daisy-rosalina/ on occasion] used the names "Princess Peach" (with the honorific) and "Daisy" (without) together.


'''Proposer:''' {{User|Cobold}}<br>
Nonetheless, her highness is called "Peach" in-game considerably more often than "Princess Peach". (To be clear, my point is not that she's ''never'' called "Princess Peach", just that "Peach" appears to be her ''primary'' in-game name, which is what the [[MarioWiki:Naming|naming policy]] recommends.) I believe the strongest example here is ''[[Mario Kart Tour]]'', which uses "Peach" despite having no shortage of playable drivers with excessively unweildy names.
'''Deadline:''' May 18th, 15:00


==== Use North American name in the article title only ====
'''Proposer''': {{User|janMisali}}<br>
#{{User|Cobold}} - The article names should not be cluttered up, the added note is unnecessary when using redirects.
'''Deadline''': November 21, 2024, 23:59 GMT
#{{User|InfectedShroom}} Per Cobold. The North American Name is what we use for everything else, so we should not create confusion.
#{{User|Stooben Rooben}} Per Cobold. I was going to move those articles to just their NA name, but I didn't know if some new rule had been passed where there had to be ''2'' names.
#{{User|Time Q}}: Per Cobold, plus with the PAL name in brackets, it looks as if it was used to distinguish the article from another one with the same name, such as [[Mario Tennis (N64)]] and [[Mario Tennis (GBC)]]...
#{{User|Princess Grapes Butterfly}} Per all. This sound like a great ideas so wikiers can know American names.
#{{User|Glitchman}} Per all, as long as the European names redirect to the page.
#{{User|Stumpers}} For consistency's sake.  Plus, if you did that to all the articles, you'd end up with a Wiki full of links to redirect pages rather than articles themselves.
#{{User|EnPeached}} - Per all, expecially Glitchman.
#{{User|Master Crash}} - Per All
#I support as long as the European names are mentioned somewhere in the articles. If these are going to be removed from the articles, I will change my vote to an oppose. --[[User:Pikax|Pikax]] 12:56, 16 May 2008 (EDT)
#[[User: Booster|Booster]] - Per All.
#Per All. -[[user:Canama|Canama]]


====Move both princesses====
#{{User|JanMisali}} First choice, as proposer.
#{{User|Pseudo}} First choice, per proposal. The princess titles for both characters can definitely be seen as their full names, but it seems to occupy a similar space to "King Bowser" in most games.
#{{User|Tails777}} Primary choice. Even if Peach uses her title more often, MANY games usually relegate to just calling the princesses by their names without their titles. And since Bowser is also referred to as just "Bowser" over "King Bowser" (a titled name used about as often as Princess Peach), I feel all three can just use their names without titles.
#{{User|Ahemtoday}} Only choice, per proposal. I was part of the opposition to the previous proposal, but this one fixes the issue I had with it. And anyway, in basically any game where Peach is playable, the thing written under her on the character select is just "Peach", same as Daisy, so this feels like the natural solution.
#{{User|Super Mario RPG}} "Princess" is just a title of Peach's name, and most appearances refer to her as simply Peach. The name for "Daisy" is very seldomly preceded by "Princess". Compare to Dr. Mario, where the "Dr." is an inherent part of his name, rather than a full title.
#{{User|Altendo}} If we can remove names from Sonic characters, the Koopalings, and even named identifiers like [[Sir Grodus|Sir]] and [[Admiral Bobbery|Admiral]], there is no reason to not do this. Per all.
#{{User|EvieMaybe}} per Altendo, specifically
#{{User|Camwoodstock}} Per proposal, and the original proposal that spurred this one.
#{{User|LinkTheLefty}} Things are headed in this direction, let's rip the bandage off.
#{{User|Arend}} I'm more comfortable with removing the "Princess" title from both articles rather than just Daisy's. Yes, Peach is often called "Princess Peach", but I find it comparable to Koopa minions referring to Bowser as "Lord Bowser" or "King Bowser" (or, in the case of game titles such as ''Super Princess Peach'' or ''Princess Peach Showtime'', it's comparable to the ''Super Mario'' games, which bear this title even if there's no Super Mushrooms to turn Mario into Super Mario).
#{{User|SolemnStormcloud}} Per all.


==== Keep as currently ====
====Only move Peach====


==== Comments ====
====Only move Daisy====
I would like to add that having PAL names in the article name only is against the [[MarioWiki:Importance Policy|Importance Policy]] as it is currently. - {{User|Cobold}} 12:08, 11 May 2008 (EDT)
#{{User|JanMisali}} Second choice, as proposer.
#{{User|Pseudo}} Second choice, since Daisy has stronger reason to be moved.
#{{User|Tails777}} Secondary choice. Daisy is referred to as "Princess Daisy" far less than Peach is referred to as "Princess Peach", with some modern games still using Peach's title. Daisy is almost always just referred to as "Daisy".
#{{User|Koopa con Carne}} per the case being made for Daisy. Games and other media as recent as ''Princess Peach Showtime'' and the Mario Movie alternate between naming Peach with and without the honorific, so MarioWiki:Naming cannot enforce one over the other based on recency, frequency, or source priority. None of this can be said about Daisy, however. Some have argued that "Daisy" is chosen for functional purposes within games, i.e. is an attempt to keep the character's name short in areas where you can allocate a piece of text only so much memory--and I'd understand the argument, if it weren't for cases like "Light-blue Shy Guy (Explorer)", "Yellow Shy Guy (Explorer)", and "Purple Koopa (Freerunning)" which push that memory limit much further than "Princess Daisy" ever could. I also question why the naming scheme of either character has to remain consistent with the other just for the sake of it; if their patently similar appearance and roles is the sole thrust behind this point of view, what's stopping [[Rosalina]] from being moved to "Princess Rosalina", then? That's an official title, too. Better lock in and make the facts readily apparent on the fan encyclopedia.
#{{User|Hewer}} Per Koopa con Carne. I see the argument for moving Peach as well, but feel more strongly that Daisy should be moved since she's rarely called "Princess Daisy".
#{{User|Super Mario RPG}} Secondary choice.
#{{User|Camwoodstock}} Secondary choice. We need to do ''something'' about Daisy, at least.
#{{User|ThePowerPlayer}} Per Koopa con Carne.


Princess Grapes Butterfly: Er, are you sure you know what the proposal is about? You're voting ''against'' keeping both NA and PAL names in the article title. {{User|Time Q}} 18:48, 11 May 2008 (EDT)
====Keep both princesses the same====


...Lol, I already moved all the pages back, Cobold. XP {{User|Pokemon DP}}
====Princess Comments, Peach====
:That's the easy way. But it is always helpful to have a proposal backing yourself up. :P - {{User|Cobold}} 11:46, 14 May 2008 (EDT)


Someone changed them back to [[Sugarscoot (Bon Bon)]]. We REALLY need to enforce what we have decided. There's really a HUGE fight between NTSC and PAL people. What can we do to make sure everything doesn't keep on changing? It seems like NTSC won, but everything's still changing. Any ideas? {{User|EnPeached}} 15:32, 14 May 2008 (EDT)
==Miscellaneous==
:We wait until the deadline is over. - {{User|Cobold}} 15:33, 14 May 2008 (EDT)
===Either remove non-English names from cartoon dubs that weren't overseen by Nintendo or affiliated companies, or allow English names from closed captions===
"What does one have to do with the other?" You'll see!


===American Spellings===
Back in 2021, there was a [[MarioWiki:Proposals/Archive/56#"Closed caption of the Mario cartoons"|proposal]] to allow closed captions used on ''Mario'' cartoons uploaded or streamed officially online to be used as sources on the wiki. It encountered massive opposition, with one comment left by a user in a previous discussion acting as the cornerstone of the opposition's rationale. The link intended to lead to that comment, seen under that proposal, doesn't do its job any more, so I'm copy-pasting it here for your convenience.
This proposal wasn't inspired by the above one or anything, but kind of coincedential, lol. Anyway, I've noticed for a long time now about the inconsistent American and English spellings for certain words in articles. Some examples would include Colour, Favourite, Centre, and some others; although it may not seem important(and it probably isn't all that much). I'm not saying one is better than the other, I'm just saying we should stay consistent.
<blockquote><span class="quote" style="font-family:Times New Roman;font-size:11pt;font-style:italic">“re closed caption: The relation between WildBrain and video streaming platforms like Netflix is the same one Nintendo has with retaillers like Gamespot: meaning the owner of the property sells the product to the retailler/streaming website, and they may supply other material (like artwork, press releases, etc) to help the client market the product. However, that doesn't mean everything the client does with the product is now official; for instance, Gamespot has in the past created fake placeholder boxarts for Mario games using edited official artwork. Gamestop may be an authorized (or "official") retailler of Mario products but it doesn't make those placeholder boxarts by association as they were made entirely by Gamespot without inputs from the creators of the source material.


'''Proposer:''' {{User|Garlic Man}}<br>
“In that respect, closed captions fall in the same category as placeholder retailler-made boxarts. Closed captions are made by people with no relation to the source material or access to behind-the-scenes material like script, and who are just writing down what they hear by ear. They are not an acceptable source for spellings.”</span>
'''Deadline:''' May 19th, 15:00


====American Spellings====
~ '''{{user|Glowsquid}}, 2021'''
#{{User|Garlic Man}} - This wiki was made in America, and is based primarily on Americans. I think we should stay consistent.(As said in the proposal itself)
</blockquote>
#{{User|MegaMario9910}} Per GM


====Oppose (use either)====
This is valid. In all this talking about what is official and what is not, I suppose it feels right to draw a concrete line somewhere. Someone who acquires the rights to use Nintendo's or one of their partners' IP to use it for a given purpose is technically an authorized party, but they're no authority themselves over the content within. Makes sense.
#{{User|Storm Yoshi}}Its whoever spells it first. Not to an Americans Enjoyment >_>
#{{User|Blitzwing}} - Using exclusively American spelling simply because a lot of our contributers are American is complete BS. Nowhere does the rules says that the wiki is American, and that's being disrespectful to editors that comes from other part of the word.
#{{User|Cobold}} - There is no need to create any consistency in spellings that are so minor as to whether there is a u in favourite or not. Per Blitzwing.
#{{User|Stooben Rooben}} - Per the comments below, but especially per Blitzwing.
#{{User|EnPeached}} - There words are somewhat universal. People on both sides understand what they mean. Unless there's paticular confusion, nothing needs to be changed.
#Per all. {{User|Toadette 4evur}}
#{{User|Stumpers}} - Beggars can't be choosers as they say.  If a UK speller wants to contribute, let him/her use his/her favorite spellings.
#{{User|Hemu}} american spellings and brittish spellings are pretty much the same except for like 1 or 2 letters people will understand if brittish spellings are used I mean I use both
#Per Stumpers and EnPeached. --[[User:Pikax|Pikax]] 12:58, 16 May 2008 (EDT)
#{{User|Arend}} Per all! Per All! PER ALL!


====Comments====
...Meaning the multilanguage names invoked in the proposal's title stick out all the more like a sore thumb. A good chunk of them, at least. Why would the wiki treat a studio or company that dubs and distributes syndicated Mario cartoons to a given demographic as particularly authoritative over the content? Ultimately, it's the same situation as the one described in the quote, the apparent clincher being that it's in a different language, and I apologize, but I don't see how it is consistent to prohibit third-party English subtitles but allow foreign dubs by people that are just as far-removed from the parent company. I propose a compromise.
I'm not sure I completely understand; is this just moving articles to their NA name? Or, is it fixing the British spelling to be American? I've been doing the latter since I came here, and if that's what the proposal's about, I don't see its point. It's kind of hard to tell English citizens to spell like Americans; they grow up spelling how they do. {{User|Stooben Rooben}} Sorry if that sounds blunt.
 
Of course, not all foreign dubs would be off limits as sources should the second option of this proposal win. If one can provide sufficient proof that a given dub was supervised by one or more employees representing a company with authority over the original product, i.e. that the company left their mark on the endeavor, sourcing it is absolutely fine. As it stands, though, I can already point to the Romanian dubs of the Mario DIC cartoons as ineligible for sourcing given my failing to find any evidence DIC Entertainment ever put its signature on them. (This is coming from someone who contributed a significant amount of names from these dubs. Sometimes you gotta kill your darlings.)
 
"'''So if option 1 wins, 'Ahehehaue' is considered official again?'''"
 
No. That doesn't come from a closed caption, and I consider WildBrain's issue of circular sourcing to be a whole other can of worms best left out of this week's topic.
 
(added 17:42, October 30, 2024 (EDT)) "'''Does the proposal extend to the live-action segments of the ''Super Show''?'''"
 
Yes, they're within the same package.
 
'''Proposer''': {{User|Koopa con Carne}}<br>
'''Deadline''': November 12, 2024, 23:59 GMT
 
====Allow the sourcing of English closed captions from officially uploaded and streamed ''Mario'' animated works====
#{{User|Hewer}} Perhaps I just have a more liberal understanding of "official" (as an Ahehehauhe defender), but after proposals like [[MarioWiki:Proposals/Archive/57#Allow/prohibit fan work by former Nintendo staff|this]], [[MarioWiki:Proposals/Archive/67#Allow quotes of characters being voiced by their official actors in unofficial media|this]], and [[Talk:Fangamer#Delete this article|this]], I feel like all these should be close enough to official to be worth documenting. And aren't games like [[Hotel Mario]] a bit of a similar case, where the "official" involvement didn't go much further than licensing them?
#{{User|Ahemtoday}} I think the difference between closed captions and placeholder retailer box art is that the closed captions are a(n optional) part of the media as it can be officially experienced. As such, I think it counts as "official" regardless of who did it.
#{{User|SeanWheeler}} Well, we would need some kind of source for names of characters that never appeared in English localizations.
#{{User|Pseudo}} These names would be familiar to some viewers of the material, if nothing else, and it seems a bit odd to consider them completely unofficial even if they weren't overseen by the original creators.
#{{User|EvieMaybe}} a license is a license
#{{User|UltraMario}} Per all. I still believe that these should still count as official enough, as they are the providers of the content and it's like a license of a license.
 
====Remove names that originate from non-English dubs of ''Mario'' animated works that were not overseen by Nintendo or an affiliated company====
#{{User|Nintendo101}} Per proposal. I found the argument persuasive.
 
====Do nothing====
 
====Comments (closed captions vs. foreign dubs proposal)====
Waltuh... I'm not voting right now, Waltuh... {{User:Koopa con Carne/Sig}} 14:01, October 30, 2024 (EDT)


Slightly confusing. I use a spell check, so I don't know what it would pick up differently, but I don't think we really need a proposal for this. {{User|ForeverDaisy09}}
{{@|Koopa con Carne}} By "not overseen by Nintendo/DiC", do you mean they gave the go-ahead but didn't have any direct involvement in production, or the dubs were produced by a third party with no permission whatsoever? I'd consider being more charitable for the former, but if it's completely unauthorized then that's basically equivalent to a bootleg or fan translation and probably shouldn't be covered. --{{User:Waluigi Time/sig}} 17:07, October 30, 2024 (EDT)
:I have to agree with FD09 here. {{User|Stooben Rooben}} 11:46, 13 May 2008 (EDT)
:First one. The proposal only touches on the scenario where a company that airs a dubbed ''Mario'' cartoon has a license to do so from the work's owner. Anything outside of such a licensing agreement is completely unofficial, like you pointed out. {{User:Koopa con Carne/Sig}} 17:42, October 30, 2024 (EDT), edited 17:44, October 30, 2024 (EDT)


The oppose should be to turn down the proposal and continue with the old way of dealing with the problem. As it stands, you're asking us to either go with the US or the UK spellings, you don't leave an option for leaving it as it is. {{User|Stumpers}} 23:35, 13 May 2008 (EDT)
Added stipulation that the proposal extends to live-action ''Super Show'' segments. {{User:Koopa con Carne/Sig}} 17:42, October 30, 2024 (EDT)
:That's why I haven't voted. :| {{User|Stooben Rooben}} 23:37, 13 May 2008 (EDT)
:What is "Ahehehauhe?" [[User:SeanWheeler|SeanWheeler]] ([[User talk:SeanWheeler|talk]]) 23:29, October 30, 2024 (EDT)
::I'll just add that, then. :P {{User|Stumpers}} 23:39, 13 May 2008 (EDT)
::It's a [https://youtu.be/OdLFZ5RAPTU clip] of a ''Super Show'' episode uploaded to YouTube by WildBrain, the current owners of most of DIC Entertainment's library (including their Mario shows). On the wiki, "Ahehehauhe" used to redirect to that episode's article because it was deemed an "official" alternate title given WildBrain's ownership status over the material, which many found outrageous since it barely passes as a "title" and is simply a transcription of the characters cackling in that clip. We don't even know if a human consciously named the clip that; it could've been a bot. {{User:Koopa con Carne/Sig}} 06:28, October 31, 2024 (EDT)
::Now, "Ahehehauhe" isn't linked to the WildBrain-related circular sourcing issues I mentioned in the proposal (they used names from the wiki in promotional texts, which Ahaha isn't one of). However, if the same policy used for the English Super Mario Encyclopedia is to be applied to WildBrain on the same grounds, then the only case where a name they used for a given subject should be employed by the wiki is (a) if the name didn't come from the wiki in the first place, and (b) there are no other known names for that subject. Even if we're to consider Ahahahue a unique and proper way to call an episode of a TV show, its use would still be untenable under the second point. {{User:Koopa con Carne/Sig}} 06:39, October 31, 2024 (EDT)
:::If the same ''Encyclopedia'' logic applied, shouldn't it still be a redirect at least? [[User:LinkTheLefty|LinkTheLefty]] ([[User talk:LinkTheLefty|talk]]) 08:24, November 8, 2024 (EST)

Latest revision as of 21:35, November 8, 2024

Image used as a banner for the Proposals page
Current time:
Saturday, November 9th, 08:45 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.
  • Any user can support or oppose, but must have a strong reason for doing so (not, e.g., "I like this idea!").
  • 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.

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 {{User|User name}}.

How to

Rules

  1. 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. 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}}.
  2. Only registered, autoconfirmed users can create, comment in, or vote on proposals and talk page proposals. Users may vote for more than one option, but they may not vote for every option available.
  3. Proposals end 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. Every vote should have a strong, sensible reason accompanying it. Agreeing with a previously mentioned reason given by another user is accepted (including "per" votes), but tangential comments, heavy sarcasm, and other misleading or irrelevant quips are just as invalid as providing no reason at all.
  5. 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 administrators.
    • 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.
  6. 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 "(banned)" 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.
  7. No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old.
  8. 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.
  9. If a proposal reaches its deadline and there is a tie for first place, then the proposal is extended for another week.
  10. 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 the {{proposal check}} tool to automate this calculation; see the template page for usage instructions and examples.
  11. 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 can only be re-proposed after four weeks (at the earliest).
  12. 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.
  13. If the administrators 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.
  14. Proposals can only be rewritten or canceled by their proposer within the first six days of their creation. However, proposers can request that their proposal be canceled by an administrator at any time, provided they have a valid reason for it. Please note that canceled proposals must also be archived.
  15. 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.
  16. Proposals cannot be made about promotions and demotions. Users can only be promoted and demoted by the will of the administration.
  17. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
  18. Proposals must have a status quo option (e.g. Oppose, Do nothing) unless the status quo itself violates policy.

Basic proposal and support/oppose format

This is an example of what your proposal must 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 replace the whole variable including the squared brackets, so "[insert info here]" becomes "This is the inserted information", not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but what each voting section is supporting 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|[enter your username here]}}<br>
'''Deadline''': [insert a deadline here, 14 days after the proposal was created, at 23:59 GMT, in the format: "November 9, 2024, 23:59 GMT"]

====Support====
#{{User|[enter your username here]}} [make a statement indicating that you support your proposal]

====Oppose====

====Comments====

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 "#{{User|[add 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 just say "Per my 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. Proposals dealing with a large amount of splits, merges, or deletions across the wiki should still be held on this page.

For a list of all settled talk page proposals, see MarioWiki:Proposals/TPP archive and Category:Settled talk page proposals.

Rules

  1. All active talk page proposals must be listed below in chronological order (new proposals go at the bottom) using {{TPP discuss}}. 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. Place {{TPP}} under the section's header, and once the proposal is over, replace the template with {{settled TPP}}.
  2. 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:
  3. The talk page proposal must pertain to the subject page of the talk page it is posted on.
  4. When a talk page proposal passes, it should be removed from this list and included in the list under the "Unimplemented proposals" section until the proposed changes have been enacted.

List of ongoing talk page proposals

  • Split sections between Tanooki Mario and Kitsune Luigi (discuss) Deadline: November 10, 2024, 23:59 GMT
  • Determine what to do with Jamboree Buddy (discuss) Deadline: November 12, 2024, 23:59 GMT
  • Split Cursed Mushroom from Poison Mushroom (discuss) Deadline: November 12, 2024, 23:59 GMT
  • Merge Orbs that share names with pre-existing Mario Party series items with those items (discuss) Deadline: November 14, 2024, 23:59 GMT
  • Create a number of articles for special buildings in Super Mario Run (discuss) Deadline: November 15, 2024, 23:59 GMT
  • Consider Deep Cheeps' appearance in the Super Mario Maker series a design cameo rather than a full appearance (without Blurps being affected) (discuss) Deadline: November 15, 2024, 23:59 GMT
  • Merge Mushroom, Dash Mushroom, and most of Super Mushroom (discuss) Deadline: November 18, 2024, 23:59 GMT
  • Expand and rename List of characters by game (discuss) Deadline: November 20, 2024, 23:59 GMT

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, Super Mario Run, and Super Mario Bros. Wonder.
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)
Split articles for the alternate-named reskins from All Night Nippon: Super Mario Bros., Doc von Schmeltwick (ended October 3, 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)

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)
Split Banana Peel from Banana, Doc von Schmeltwick (ended September 18, 2024)
Merge Spiked Thwomp with Thwomp, Blinker (ended November 2, 2024)

Writing guidelines

Consider Super Smash Bros. series titles for recurring themes low-priority

Something I noticed late yesterday was that the page for "Flower Fields BGM" from Super Mario World 2: Yoshi's Island (Or just Yoshi's Island from now on for simplicity) is still titled Yoshi's Island (theme), even after Nintendo Music dropped, and then I realised that some other song titles (Most notably Obstacle Course, also from Yoshi's Island) just don't make a lot of sense. Then I feel it's important to note that even though this is a Mario Wiki (What?!?!?!? Huh!?!?!?) we should also take a look at the Super Smash Bros. titles for themes from other series, with the biggest example I can think of being "Meta Knight's Revenge" from Kirby Super Star, which is actually an incorrectly titled medley of the songs "Boarding the Halberd" and "Havoc Aboard the Halberd". It's also good to look at songs Super Smash Bros. is using a different title for than us, like how it uses the Japanese titles of the Donkey Kong Country OST instead of the correct ones. Between all these facts it should be obvious the track titles in Super Smash Bros. are not something the localisation team puts a whole lot of thought or effort into (Though the original Japanese dev team also mess these up sometimes). Going back to the original point that gave me this realisation, "Yoshi's Island" is a very nondescript track title for a random stage theme which most people would look for by searching for something like "Flower Stage" or possibly even "Ground theme" (Even though that would lead to another song but still), this is especially considering the title screen theme from the game is ALSO called Yoshi's Island, and that's not even considering the Yoshi's Island world map theme from Super Mario World, which I don't know if it even has an official title (Yet, it is coming to Nintendo Music eventually) but I would bet that's ALSO YOSHI'S ISLAND. So I am suggesting to just make Smash Bros. a VERY low-priority source for this specific small aspect of the Wiki to avoid confusion and potentially future misinformation if things go too far.

Proposer: biggestman (talk)
Deadline: November 18, 2024, 23:59 GMT

Support

  1. biggestman (talk) Did you know there's a theme titled "Per this proposal" in Super Wiki Bros. Ultimate but the original title is simply "Per Proposal"? INSANE! (Per proposal)
  2. Doc von Schmeltwick (talk) - the theme names given in Smash (particularly Brawl and previous) are more just general descriptions of the contexts they play in rather than actual names. Hence why DK Island Swing became "Jungle Level."
  3. Jdtendo (talk) Per all.
  4. Super Mario RPG (talk) Per Doc and proposal.
  5. LadySophie17 (talk) Per proposal. To me this feels like making a non-Mario game determine the name of a Mario-article.

Oppose

  1. Hewer (talk) The names are from an official source whether we like them or not. Not only that, they come from within the games themselves, putting them at the top of the naming priority list. Tracks that have gone by different names more recently can use those, but those inconsistencies shouldn't invalidate the whole source. We also accept "inconsistent" names from Smash for other subjects, e.g. Propeller Piranha, so it would be odd to single out music. (Also, I'd argue "Meta Knight's Revenge" isn't incorrect, but is the name of the medley rather than of either individual song. On the topic of Kirby music, I'm pretty sure "A Battle of Friends and Bonds 2" from Kirby Star Allies was first called that in Smash before the name appeared in other sources, which would suggest Smash's names aren't all bad.)
  2. Nintendo101 (talk) The names used in the Super Smash Bros. series are from first-party games, are specific localizations of Super Mario specific material, and are localized by Nintendo of America. In my view, that is all that matters for citations, especially given most of these music tracks have not been officially localized into English through other channels. I similarly would not support a proposal to discredit the names for music tracks used in games like Mario & Sonic. However, I do think this proposal is in the ballpark of a reality, which is that melodies that sometimes incorporate multiple compositions (like "Meta Knight's Revenge") and specific arrangements sometimes are given unique names. (This is not unique to the Smash Bros. series — a cursory view of the Video Game Music Database or of officially published sheet music reveals Nintendo is often inconsistent with these names in the West.) In some installments, what is given a unique name for a particular arrangement (like "Princess Peach's Castle" from Melee and labeled as such in Super Smash Bros. for Wii U) is attributed to just one piece in a subsequent game (in Ultimate, this piece is named "Ground Theme" despite interlacing the "Underground BGM" in the piece as well, so while more simplistic for the Music List it is not wholly accurate, and I do not think "Ground BGM" should be called "Princess Peach's Castle" in any context other than this Melee piece). So I think it is worth scrutinizing how we name pieces that are "misattributed." However, I do not support a blanket downground of first-party Nintendo games just because we do not like some of the names.
  3. Salmancer (talk) If I recall from Miiverse correctly, the reason many songs are not given official public names is that naming songs does require spending very valuable developmental bandwidth, something that not all projects have to spare. (Sometimes, certain major songs have names because of how important they are, while other songs don't.) Given this, I am okay with Smash Bros. essentially forcing names for songs out early because it's interface requires named songs. Names don't have to be good to be official. My line is "we all agree this uniquely identifies this subject and is official".
  4. Waluigi Time (talk) See my comment below.
  5. Tails777 (talk) Per Waluigi Time
  6. Killer Moth (talk) Per all.
  7. Koopa con Carne (talk) per Nintendo101 & Waluigi Time. Some scrutiny is warranted, but let's not entirely discredit Smash Bros--a series of games published and sometimes developed in first-party capacity--as a source of information.
  8. Axii (talk) Per all.
  9. ThePowerPlayer (talk) These are still the most recent official names. Let's not unnecessarily overcomplicate things.

Comments

I'm not sure if this is a necessary proposal, or what it's going to accomplish in practice that isn't already handled with current organization and policy. As far as I'm aware, the Yoshi's Island examples here are just the result of no editor taking the initiative to move those pages to the new titles yet. The Nintendo Music names are the most recent and I think also fall under tier 1 of source priority, technically, so the pages should have those names, end of story. We don't need a proposal to do that.

Additionally, "Yoshi's Island" and "Obstacle Course" do not refer to the original themes from Yoshi's Island - they're the names of specific arrangements of those themes from the Smash games. Maybe it's not cemented into policy, but our current approach for theme articles is to use a title referring to the original theme when available. Take "Inside the Castle Walls", for instance. There's been several different names given to arrangements of this track over the years, including "Peach's Castle", "A Bit of Peace and Quiet", and most recently in the remake of Thousand-Year Door, "A Letter from Princess Peach", but we haven't and most likely aren't going to move the page to any of those. (And that doesn't mean any of those games got it wrong for not calling it "Inside the Castle Walls". It's perfectly valid to give a different name to a new arrangement.)

Basically, I don't think this would be beneficial and could potentially cause headaches down the road. I can't think of any actual examples where we're stuck with a "worse" name from Smash based on everything else I've said here, especially with Nintendo Music being a new and growing resource for track titles in the context of the original games. --Waluigi's head icon in Mario Kart 8 Deluxe. Too Bad! Waluigi Time! 14:17, November 4, 2024 (EST)

Indeed, Ground BGM already got moved to its Nintendo Music name, despite being called "Ground Theme" in Smash (among other sources). Nintendo Music should already take priority over Smash just for being more recent. Hewer (talk · contributions · edit count) 14:29, November 4, 2024 (EST)
@biggestman I recommend skimming through our naming policies for some clarity. The only reason why "Yoshi's Island (theme)" has not been moved to "Flower Fields BGM" is because no editor took the initiative yet, and another one had already turned "Flower Fields BGM" into a redirect page. That must be deleted by an admin first before the page can be moved, but that is the only reason. Super Smash Bros. and Nintendo Music are at the same tier of coverage, and because Nintendo Music is the most recent use of the piece, it should be moved. - Nintendo101 (talk) 15:50, November 4, 2024 (EST)

@LadySophie17: What do you make of Propeller Piranha, Fire Nipper Plant, Nipper Dandelion, etc., which are named based on what Viridi calls them in Smash? And more generally, why does Smash not being strictly a Mario game matter? It's still an official game from Nintendo that uses the Mario IP, and the Mario content in it is fully covered even if it's exclusive to Smash (e.g. Mario stages and special moves all get articles). Hewer (talk · contributions · edit count) 17:29, November 4, 2024 (EST)

There's also the fact that Nintendo Music, which this proposal aims to prioritise, is not a Mario game either. It has a collection of music from various different franchises that just so happens to include Mario, much like Smash. Hewer (talk · contributions · edit count) 08:10, November 5, 2024 (EST)

A lot of you have made good points, but one I don't understand or like is the one that those are the names of specifically the Super Smash Bros. versions, which is just painfully inconsistent. With very little exception remixes in Super Smash Bros. almost always use the original title in one of two ways, either using the name completely normally or by titling it (SONG NAME 1 HERE)/(SONG NAME 2 HERE) for remixes that are a relatively even split between two songs. Outside of this the only examples of "Well it COULD be the name of specifically the Smash version!!!" from every series represented are "Yoshi's Island", "Obstacle Course" and "Meta Knight's Revenge". Out of these Yoshi's Island and Obstacle Course theoretically COULD be original titles, but Meta Knight's Revenge is (probably) just meant to be named after Revenge of Meta Knight from Kirby Super Star, which is where both of the songs represented debuted, but was mistranslated. However I can't prove anything because none of these 3 Smash Bros. series remixes Japanese titles are anywhere online as far as I can tell so there's nothing to compare any of them to. There might also be examples from something like Fire Emblem or something idk I play primarily funny platformers. The point though is that if they were to name some remixes after the originals while making original titles for some it would just be so inconsistent I simply can't see a world where that's the intent. BiggestManMario dead in the arcade version of Donkey Kong 13:19, November 5, 2024 (EST)

I believe the Japanese name of the track was the same as the Japanese name of "Revenge of Meta Knight", but I maintain that translating it as "Meta Knight's Revenge" is not necessarily a mistake, the translators might have just thought that name was better suited for the theme specifically, especially since medleys in the Kirby series are often given different titles to the included themes ("Revenge of Meta Knight" is still not the title of either of the individual tracks included). For example, a different medley of the same two themes in Kirby's Dream Buffet is titled "Revenge of Steel Wings". Even if "Meta Knight's Revenge" is an error, though, that's one error in over a thousand track names, and one not even from the Mario franchise. One or two errors aren't enough to invalidate an entire source, especially one of this size. As for the Yoshi's Island tracks, as has already been pointed out, they should be changed anyway because Nintendo Music is the more recent source (Flower Field BGM already has been changed since this proposal was made). Hewer (talk · contributions · edit count) 13:49, November 5, 2024 (EST)
FWIW, that point isn't meant to be an argument against this specific change anyway, it's "we already shouldn't be prioritizing those names for article titles regardless of the outcome of this proposal, and here's why". --Waluigi's head icon in Mario Kart 8 Deluxe. Too Bad! Waluigi Time! 18:13, November 5, 2024 (EST)

Ok so now that it's been a few days I have very quickly realised that I very much said a bad reason this change should be implemented. I just realised that all of these titles have already been moved but I have since realised a somewhat more understandable reason for it. If a new Smash game came out and reused these titles then according to our rules they would need to be moved back to those titles again, wouldn't they? Would it make sense to move Flower Fields BGM back to the less descriptive title just because a game reused a (debatably) worse title? Overall though I don't care too much about the result, even when I started this proposal, my impatience just got to me too early. BiggestManMario dead in the arcade version of Donkey Kong 11:09, November 7, 2024 (EST)

Yes, that's how recent name policy works. We should choose what name to use based on what the most recent official source says, not what we subjectively prefer. I personally feel like "Flower Field BGM" isn't much less generic than "Yoshi's Island". Hewer (talk · contributions · edit count) 11:38, November 7, 2024 (EST)
Not a simple yes/no answer, actually. If they're just arrangements again, then no, we wouldn't move the pages. If they added the original tracks from the SNES version and used those names, then they would probably be moved. (However, you might still be able to make a decent argument for keeping the Nintendo Music names on a recency basis considering it's a live service?) --Waluigi's head icon in Mario Kart 8 Deluxe. Too Bad! Waluigi Time! 11:48, November 7, 2024 (EST)

I've actually been mulling over a proposal like this, but for names in general, not just themes. We generally don't consider out-of-franchise content as a source of a recent name if the original Super Mario franchise supersedes it; for example, Podoboo, which is still in use over Lava Bubble in The Legend of Zelda franchise. I don't see why the same thing can't be said for Super Smash Bros., especially now with its reduced coverage. For that matter, possibly breaking it down to a per-series basis (like how "Gold Goomba" was the most recent name in the Super Mario series despite being "Golden Goomba" in the most recent Mario Party)? It might not be a bad idea to establish a new rule over this. LinkTheLefty (talk) 08:24, November 8, 2024 (EST)

Decide how to prioritize PAL English names

As with my previous proposal, this one aims at getting a consistent method of how PAL names are used alongside NTSC names. One thing that I noticed is that the priority of some of these names are inconsistent, like Mini Bowser, which redirects to Koopa Kid rather than link to the name actually used in NTSC countries. Other pages, like Bowser Party, are disambiguations between the Mario Party 10 game mode and the Mario Party 7 event that is only known as "Bowser Party" in PAL regions.

This map shows which countries use these different systems. The terms go beyond just color conversion; in terms of English, the PAL system is used in countries like the United Kingdom (and correct me if I'm wrong, but I also think Australia and New Zealand too), while the NTSC system is used in North America, specifically in the United States and Canada. MarioWiki:Naming says that the North American name takes priority, which means that Mini Bowser would link to the toy and Bowser Party would redirect to the section in Mario Party 10, potentially among other pages, although tophats linking to pages with alternate PAL names will remain.

Therefore, I am proposing four options:

  • NTSC>PAL, in which when linking pages, the page with the name in NTSC English or all-English takes priority over other pages sharing the same PAL name, even if it isn't as significant. If another page with the same name in PAL English exists, it can be linked to in the tophat.
  • NTSC=PAL, in which pages that share the same name in both NTSC and PAL English appear in a disambiguation page regardless of whether the name is used in NTSC English multiple times or not. This is already done with Bowser Party.
  • NTSC<PAL, in which pages that share the same name in PAL English have the highest priority name linked to it, even if it doesn't have that name in NTSC English but the other pages does, in which case it will redirect to the higher-priority PAL name and the lower-priority NTSC (or all-English) page will be linked to in the tophat in the Redirect template. This has been done with Mini Bowser.
  • Do nothing - do I even have to explain this?

Proposer: Altendo (talk)
Deadline: November 18, 2024, 23:59 GMT

NTSC>PAL

  1. Altendo (talk) I think that abiding by SMW:NAMING is the best option. Yes, Koopa Kid is more notable than Mini Bowser toys, but if this is an American English wiki, might as well make pages link to the one that actually are named like that in NTSC.

NTSC=PAL

  1. Ahemtoday (talk) I think this is the best solution — completely deprioritizing the PAL names doesn't quite seem right to me.

NTSC<PAL

Do nothing

Comments

can i ask for some more examples? i'm having a bit of trouble fully grasping what you mean EvieMaybe (talk) 20:11, November 4, 2024 (EST)

The Mini Bowser situation, for instance:
  • NTSC>PAL: Mini Bowser would link to the page actually named "Mini Bowser" instead of Koopa Kid (who is known as Mini Bowser in PAL English)
  • NTSC=PAL: Mini Bowser would be a disambiguation page between Koopa Kid and the Mini Bowser toy
  • NTSC<PAL: Mini Bowser would continue to redirect to Koopa Kid.
  • Do nothing: Nothing changes.
Hope this makes more sense. Altendo 21:07, November 4, 2024 (EST)
So in the first option, "Mini Bowser (toy)" would lose its identifier? Hewer (talk · contributions · edit count) 06:19, November 5, 2024 (EST)
Basically. The tophat will say, "This article is about the toy. For the characters known as "Mini Bowsers" in Europe, as Koopa Kid." I prefer abiding by SMW:NAMING by prioritizing NTSC names over PAL names. Basically, the current Mini Bowser (toy) page will be moved to Mini Bowser, which will no longer redirect to Koopa Kid. For people who have only owned NTSC copies, this is more straightforward, as many would be unaware that Koopa Kid is known as Mini Bowser without having a PAL copy. As for Bowser Party, if Option 1 passes, it will redirect to the section in Mario Party 10, with a tophat leading to Bowser Time. If Option 2 passes, Mini Bowser would become a disambiguation page between Koopa Kid and Mini Bowser (toy). If Option 3 passes, Bowser Party would redirect to Bowser Time and would have a tophat leading to the Mario Party 10 section. If Option 4 passes, well... nothing changes, making everything remain inconsistent.
So, to answer your question, yes, the identifier will be removed. The only other page with the exact same name minus the identifier is simply the redirect to Koopa Kid, who is only known as "Mini Bowser" in European English, and SMW:NAMING prioritizes American English names. Altendo 07:15, November 5, 2024 (EST)
Now that I think about it, couldn't the identifier for the Mini Bowser toy be removed anyway? There's no actual article named Mini Bowser. For that matter, I thought it was discouraged to use the terms NTSC and PAL now in regards to English, especially now that region-locking is mostly a thing of the past. LinkTheLefty (talk) 08:24, November 8, 2024 (EST)

New features

None at the moment.

Removals

None at the moment.

Changes

Stop considering reused voice clips as references (usually)

More often than not, if you look at a game's list of references to other games, you'll find something about how so-and-so character reuses voice clips from so-and-so game. This has been bugging me for a while because these just aren't references. Nintendo has been reusing voice clips for multiple decades now, so this isn't anything new. When a new Mario Kart game comes out and some of the drivers reuse some wahoos or hurt sounds or whatever else from an old Mario Party game, it's not because the developers wanted to give a nod to that Mario Party game, it's because they had those clips on hand and could easily repurpose them instead of dragging the voice actor back into the recording booth. I propose removing reused voice clips from the references to other games/references in later games lists, with one exception that I'll get to shortly.

For a particularly egregious example, here's all the "references" of this type currently listed on Super Mario Party. Notice how vague these entries are and how many of them don't even specify which characters have clips reused.

The exception to this would be if a voice clip, within the context it appears in the game, is clearly a reference to another work. I'm not sure of any actual examples off the top of my head, but hypothetically, if Luigi reused some of the "MARIO!" voice clips from Luigi's Mansion in Luigi and the Haunted Mansion from Super Mario Galaxy, that would probably be considered a reference. In this case, the entry should explain exactly what clip(s) are being used and what it is about the situation that makes it a reference. That leads me into what should probably be a good rule of thumb for this exception: if you can't explain why it's a reference beyond just being in that game, then it's probably not a reference.

Proposer: Waluigi Time (talk)
Deadline: November 8, 2024, 23:59 GMT

Support

  1. Waluigi Time (talk) Waluigi Time's support vote is reused from this proposal.
  2. Nightwicked Bowser (talk) These voice clips are most likely used without their game of origin in mind.
  3. Super Mario RPG (talk) Per both.
  4. Sparks (talk) Per all.
  5. LadySophie17 (talk) Donkey Kong: Mario's mustache is reused from this game.
  6. TheFlameChomp (talk) Per all.
  7. Nintendo101 (talk) Repurposing an asset — voice clip or otherwise — is rarely a reference in isolation.
  8. Doc von Schmeltwick (talk) - I swear this has already been proposed and passed....
  9. Arend (talk) I think this is more worth to be its own trivia subsection ("Reused assets"?) than treating it as a specific "reference" and lumping it among the more legit ones.
  10. Shadow2 (talk) Per all.
  11. Camwoodstock (talk) Per all. Reuse of assets isn't really a "reference" in the usual sense, as there's plenty of non-callback reasons to do so. We don't think the re-used Charles Martinet lines in the TTYD remake were done out of wanting to do a cameo from Charles, they probably just didn't feel like bringing Kevin back into the recording booth when they already had a cohesive library of voicelines from the original game. ;P
  12. EvieMaybe (talk) per all
  13. DesaMatt (talk) per all.
  14. PnnyCrygr (talk) Per all as This "reusal of voices" statement is getting done to death over and over again. And a reuse of assets is not an allusion/reference to something.
  15. ThePowerPlayer (talk) ThePowerPlayer's "Per all" vote is reused.
  16. Cadrega86 (talk), the same also goes for generic artwork (so unless it's specifically stylized or features stuff specific to a single game/subseries). These are not references but just "lazy" asset re-usage.
  17. Technetium (talk) Per all.
  18. Jdtendo (talk) Per all.
  19. Ray Trace (talk) Grunts, screams, and whoohoos aren't uttered with a specific game in mind and our articles shouldn't reflect that.
  20. Scrooge200 (talk) This has been bugging me for a while. This is just asset reuse to save budget and because there's very few specific lines that need to be newly recorded.
  21. Mario (talk) Just because it was first heard in a game doesn't mean it was recorded for this game. It might be a stock sound that went unused and eventually found its way into a future game. Additionally there are clips that are better known in other games than the one it originated in. "That's-a so nice!" Is commonly heard when Mario clears a level in New Super Mario Bros., but this quote is first heard in Mario Kart Double Dash, barely audible in the Awards Ceremony. Unless the clip itself is made specifically for a game (Mario vs. Donkey Kong!!! Finding its way in a Mario Kart game as a store speaker or something) it's best not to list as a reference. That being said, there should be ways to list if voices have been reused.
  22. Tails777 (talk) This is on par with referencing Super Mario Galaxy every time Rosalina appears. Pretty sure we had a proposal at some point opting to exclude these types of recurring things from the references section and this is just following in suit. Per proposal.
  23. DryBonesBandit (talk) Reusing a "per all" vote from previous proposals.
  24. BlueBirdBlues (talk) Reusing assets are, in most cases, not references. That being said, I do feel like we should document these reused assets somewhere, perhaps on a separate List of reused assets article? Creating a new subsection in each article for these reused assets would work too, I suppose.
  25. SeanWheeler (talk) Don't want to bloat the references section of each game's page.
  26. ExoRosalina (talk) Reused are unlikely as references, especially voice clips.
  27. Okapii (talk) Per all; voice lines in the Mario franchise have been reused so many times that what game they originated in feels almost meaningless, and making a note for every time any character reuses a specific line just feels like pointless bloat for the reference section.

Oppose

  1. Hewer (talk) I think a game reusing assets like voice clips from a previous one is still worth noting, and the reference sections are a handy place to do it. I don't see why we must restrict the section to only when "the developers wanted to give a nod".
  2. Pseudo (talk) Per Hewer. I do get that it's not an intentional reference per se, but this is still information worth documenting on the wiki (if a different place to note this information would be proposed, I'm all ears).

Comments

I do know Luigi's "Gotcha!" was made for Luigi's Mansion as a thing he says when he catches ghosts, then became a standard voice clip for him in 64DS and NSMB, despite no longer making as much sense there. Doc von Schmeltwick (talk) 11:46, October 27, 2024 (EDT)

I would also like a place for people to note when new voice clips get recorded. I think the Protrayals section of character articles makes a fair amount of sense. Or maybe in Development sections of games? Salmancer (talk) 21:07, October 30, 2024 (EDT)


Encourage game-related "icon"-type images to have consistent file dimensions with each other when applicable to their origins

My last proposal related to this subject had too many holes in it due to being too wide to make an actual rule on the subject. Indeed, not all sprites really need the blank space, not all "icons" are sprites at all. To recap:

this looks good
  • MKDD Mario.png
  • MKDD Luigi.png
  • ToadIcon-MKDD.png
  • PeachIcon-MKDD.png
  • MKDD Yoshi.png
  • MKDD DK.png
  • BowserMKDD.png
  • MKDD Wario.png
this does not
  • MarioMPT.png
  • Luigi MPT.png
  • Shy Guy MPT.png
  • Peach MPT.png
  • Yoshi MPT.png
  • DK MPT.png
  • Bowser MPT.png
  • WarioMPT.png

Notice how half of the MPT ones (second row) are awkwardly, inconsistently stretched in various gross ways that makes some of the pixels be rectangles, and none are at a proper size relative to each other - this is an obsessive-compulsive spriter's worst nightmare. Meanwhile, the MKDD ones (first row) look crisp, clean, and are at a nice size relative to each other. Why is this? Because since they are icons, they are programmed to occupy the same type of space in select screens and player standings in-game. They're supposed to be at around the same size, which is accomplished through the small amount of empty space some have in the upper right corners - which the origin images have in the game's files. We should reflect this for the simple reason that we're only going to be putting these in galleries and table cells with each other anyway, so it makes the most sense to have them take up the same amount of space here as well. They should either be at their raw parameters, or if they are cropped, cropped to the exact same size as all the others for that type in that game so as to not screw up formatting and table cell sizes (and we shouldn't be increasing the size of sprites that are at this size by default anyway). This goes for selection icons, rank icons, map icons, that sort of thing. Cropping them down needlessly leads to the grossness that the second gallery there displays.

This is already something of an unofficial rule on here; a majority of the games with this sort of icon have them uploaded at a consistent size already for the same pragmatic reasons I just listed. I'm just trying to make this more clear-cut. It's like how "don't optimize images with color-changing metadata" is a rule - most people can't tell the difference, but it minorly affects the accuracy and presentation, so that's why that rule is in place. This is also for the "accuracy and presentation" reasoning. Also, I fail to see what the difference is between this and preferring screenshots be uploaded at native res rather than boosted resolution.

THIS DOES NOT COVER THE RARE INSTANCES GAME ICONS ACTUALLY DO HAVE DIFFERENT SIZES AS STORED IN-GAME. Instances of that are quite rare, especially for character icons that swap locations, but they can happen. Since they aren't the same size to begin with, there's nothing to match up with. It also does not apply to ones that are extrapolated from a singular group image containing all of them.

PLEASE NOTE THAT MOST IMAGES OF THIS TYPE ON THE WIKI ALREADY FOLLOW THIS RULE. Attempting to do the opposite, therefore, will take more effort for less reward.

ADDITIONALLY, I WANT TO CLARIFY THAT THIS IS NOT SPECIFICALLY STATING THEY NEED TO KEEP THEIR NATIVE DIMENSIONS. Rather, it is saying that if you do decide to crop them, you should crop them to consistent parameters, ie, the width of the widest one and the height of the tallest one. Having to resize images on an individual basis is tedious and can lead to extra HTML bloating the page that would be a non-issue if they were uploaded at the same size to begin with.

EDIT: Here's a better illustration of why I think this is necessary:
49667.png
Notice how with them cropped to content, their vertical (and horizontal if they were stacked, thanks to Klap Trap's muzzle and Diddy's hat) positions are all over the place. To someone with OCD, that's maddening. Not unlike bad kerning. This is what this proposal hopes to avoid. And no, that's not something a "rawsize" thing can do, that's gallery-only - and this inconsistent positioning would be an even bigger issue with the images in a gallery, since those don't have positioners available. And while technically, HTML can fix the positioning on the table (but again, not in a gallery), that would require a bunch of finagling span classes that would bloat the page's byte count unnecessarily - not to mention take potentially hours of trial and error depending on the image amount - when the obvious solution is to give the images the consistent parameters they were deliberately made to have - and yes, that's deliberate in more than just "limited by sprite parameters," because they used them to position them accurately in the character/level select, as I am doing with this table.

Proposer: Doc von Schmeltwick (talk)
Deadline: November 11, 2024, 23:59 GMT

Support - consistent icons (change the few remaining icon images and make it a general rule for the future)

  1. Doc von Schmeltwick (talk) - Icon haz dead, never-funny-in-the-first-place memes about fast food sandwiches?
  2. Super Mario RPG (talk) - Accurate to how the graphic or texture is stored in game.
  3. Hewer (talk) Per fast food sandwiches
  4. Ahemtoday (talk) Per proposal.
  5. blueberrymuffin (talk) Per proposal.

Oppose - who needs consistency? (do nothing)

  1. Waluigi Time (talk) Rawsize exists.
  2. Koopa con Carne (talk) There's no sense in deliberately translating the functional limitations of a game onto a wiki. The site's educational purpose dictates that official material shown on a wiki be inherently recontextualized, and showing that material at a different scale than originally intended is in line with that idea. Even taking into account the niche interests of a sprite enthusiast (which TBH is fair, the wiki is a gateway to Mario material for anybody), the sprites in and of themselves are accurate to how they were extracted when you view them on their dedicated file pages; it's only their appearance on mainspace pages that is subject to alterations, and what to what degree that is beneficial is better scrutinized on a case-by-case basis than through a global proposal. TLDR If the sprites are too uncomfortably big just resize them, or use rawsize like Waluigi Time says.
  3. Lakituthequick (talk) Per WT.
  4. UltraMario (talk) Per all. This can easily be taken care of by either a gallery or a table's settings, I am very sure of that. We don't need to be unnecessarily tampering with perfectly cropped files. I am not 100% sure of the technical site of the wiki but I am very sure that there are better ways to go about fixing sizing of things in tables not being adequate without just having to overhaul image uploads entirely, rather than just playing around with a table.
  5. Fun With Despair (talk) Seems like a huge amount of work for what is... honestly imperceptible to 99.9% of users such as in your example. Busywork for the sake of busywork.
  6. Shy Guy on Wheels (talk) Per all. I see no real benefit from this.
  7. Sdman213 (talk) Per all.
  8. Camwoodstock (talk) Per all, especially Waluigi Time. We already have tools capable of representing these icons more accurately to their in-game versions as necessary without requiring deadzones or other such things to be baked into the image itself. In fact, baking it into the image itself can cause issues when attempting to use the same image on different pages not fitted for them; such as how the image on the infobox for Blooper (Paper Mario: The Thousand-Year Door) is markedly smaller because it retains the blank space for the sake of the bestiary article. While we should strive for accuracy, we shouldn't let it get in the way of making the information actually accessible and readable; besides, if someone wanted the raw, original images, including any blank space around them, they would likely check The Spriter's Resource, not us.
  9. Ray Trace (talk) Per Koopa Con Carne. Zero readers care if an asset is cropped to content to dimensions in the power of 8 or if they have the ripped dimensions, especially if all said images are there to illustrate a gallery and especially if there is copious amounts of empty space just to pad the image to appropriate dimensions for a game engine. We aren't a game engine (modern game engines are perfectly capable of having textures in resolutions not in powers of 8 by the way), official websites such as the Mario Kart 8 Deluxe's official website crop to content because image editors know that it doesn't need to be in those dimensions (let's not get into how these assets are actually made, they're scaled down in the first place 100% for game engine reasons) icons should be cropped to editor's discretion without bludgeoning editors over the head about it, we should prioritize optimization and readability over faithfulness to asset dimensions. I can see cases where consistent sizes can work out, namely the character icons as listed in this proposal, but the general rule should be crop to content, but leave some in exceptions in regards to formatting tables, not the other way around.
  10. TheFlameChomp (talk) Per all.
  11. ThePowerPlayer (talk) Per all.
  12. Shoey (talk) Per all.
  13. Jdtendo (talk) Per all.
  14. Cadrega86 (talk) Per all, especially Koopa con Carne and Ray Trace.
  15. Axii (talk) Per all.
  16. SeanWheeler (talk) Some really small icons like the Super Smash Bros. series stock icons would look really bad if they were resized to be consistent with Mario Kart ranking icons.
  17. Mario (talk) The additional caveats in the proposal trying to address this issue is nice I guess but it makes the proposal much less clear in what it's trying to accomplish and it comes off as this user trying to bludgeon over their approach to these images in opposition with several other people's while tacking on qualifications and caveats after the fact. It doesn't help that the terminology of the proposal is imprecise (what is a "game-related 'icon'-type image"?? Does the proposal apply to whatever is a "game related 'non-icon' type image"?) Per all.
  18. Killer Moth (talk) Per all. I don't see the point in doing this.
  19. Nintendo101 (talk) I will reiterate what I said below: if folks want to maintain unified dimensions around certain assets, like the ones in the Diddy Kong Pilot example, that is completely fine and okay to do. I agree it looks nice. However, folks should have the freedom to choose whether they want to do that or not with the tables and templates they have developed. To experiment. I agree with the opposition that cropping to the visual content of an asset is not inherently destructive, while recognizing there are real examples on this wiki where assets benefit from having unified dimensions outside of galleries. But those were choices made because they are visually appealing and convey information - not out of a unique reverence for how computer engines spatially store assets, and while I know this proposal is not explicitly advocating for that, it derives from similar arguments made in the previous one, and I wanted to touch upon that here. We adjust assets all the time for the sake of illustrative intent. We assemble disembodied sprites. Adjust/add colors to reflect in-game appearances (especially when they are not actually coded as such for older consoles). We pose models. We approximate lighting conditions. We crop out screenshot details for a focused view. We narrow displays to omit details that the player typically has no way of seeing. From my experience, none of these choices have been considered controversial, and they should not be. They are not dissimilar from taxidermy, art restoration, and similar curatorial techniques that are exercised in museums worldwide. To me, cropping to visual content - the pixels that people can actually see - is no different from these methods and not an inherent problem. If folks want to keep unified dimensions around the assets they are working with or see use outside of galleries, that is fine and good. This is the opinion of some other folks in the opposition, like fellow ripper Ray Trace, as evident here. However, if folks do not want to do that, or use tables built on the expectation that assets they are using are cropped to content, or they are cropping the content around assets that are only found in galleries, I think they should have that freedom too.
  20. MCD (talk) Per all.
  21. FanOfYoshi (talk) No. No, both look good in their own right. Per all.
  22. SmokedChili (talk) Per all.

Comments

@Waluigi Time - Rawsize doesn't help for tabular data. Only for galleries. Only way to get it there would be to separately size each cell, and even that doesn't keep them in the correct position within the cell. Wouldn't it be more pragmatic to just have the images at the correct size rather than having to mess with the HTML each time? And we do indeed use these for tabular data, like ghost times, tennis rivals, that sort of thing. Doc von Schmeltwick (talk) 16:43, October 28, 2024 (EDT)

And would that not be easily solved by displaying the image at its native resolution (or at least consistent resolutions for all of them) and centering it? --Waluigi's head icon in Mario Kart 8 Deluxe. Too Bad! Waluigi Time! 16:51, October 28, 2024 (EDT)
No, it absolutely wouldn't. Because not all the icons are themselves centered, such as the MKDD ones above. They all come out of the lower-left corner. And that's not getting into how some games have a variant with an actual shaped background alongside clear-background ones, like Strikers Charged for example. It'd make the most sense to match those up relative to where the square bounds are for their respective size, IMO. Also, when they need shrunk for smaller tables, it's easier to do that when they have the same x-y parameters anyway so you don't have to check every. Last. One. And do the math each time. Doc von Schmeltwick (talk) 16:52, October 28, 2024 (EDT)
@Waluigi Time - Rawsize also doesn't work for sizing images down. Only sizing them as-is or sizing them up. So it's still not a perfect solution for all occasions anyway. Doc von Schmeltwick (talk) 02:48, October 29, 2024 (EDT)
All of these things can be fixed using text-align: center, vertical-align: middle, and the inherent ability of tables to size columns and rows based on their contents. Lakituthequick.png Lakituthequick 20:55, 28 October 2024 (UTC)
I already said that's not true, because not all of them are centered in their origin. If you want DK's image's left border touching the left border and his right border touching the right border, and the same to go for Luigi, that will absolutely not work unless they are uploaded at their intended size. Doc von Schmeltwick (talk) 16:58, October 28, 2024 (EDT)

@Koopa con Carne - I thought you didn't want math to be forced onto the site. In order to resize them consistently if they aren't uploaded at the intended consistent size, you have to go through every single one and check their sizes individually, then apply whatever size change also individually in order to be consistent. Keeping them as they are intentionally incorporated into the game is much cleaner on both counts. If mediawiki had a "50%" in addition to the pixel resizing, that wouldn't be an issue, but they don't. And applying a same-pixel-size on sprites with different base sizes is just dirty. Doc von Schmeltwick (talk) 17:04, October 28, 2024 (EDT)

You're misconstruing my point about math on the wiki. I never suggested curbing the use of math in the back end by editors (even then, I don't recall ever actually mathing my way through editing a page other than establishing sizes of things like images and charts). It was strictly in reference to the math that is displayed, for one reason or another, to readers, specifically how serviceable it is for articles to show readers more complex formulas versus simple tallies of elements in a level. I've long digressed though, lol.
The issues you bring up are solvable on a case-by-case basis. I like consistency and tidiness, too, however, those ought to have a healthy marriage with the wiki's primary interest to educate. Here, you'll notice I purposefully enlarged the icon for the Giant Banana item relative to the regular banana peel, because it used to look about the same size, which was odd. I understand where you're coming from and I support giving a sense of scale to sprites of a certain type in a row if it would otherwise look too messy or unnatural, but I don't believe that has to be enforced among all these sprites indiscriminately. -- KOOPA CON CARNE 18:23, October 28, 2024 (EDT), edited 19:03, October 28, 2024 (EDT)
Well this proposal isn't about "all sprites," it is specifically about icons within a particular family, ie, all MKDD character select icons are one family, all MKDD item icons are another family, all MKW select icons are yet another family, etc. etc. etc. Doc von Schmeltwick (talk) 18:30, October 28, 2024 (EDT)
I understand. That's what I meant when I said "sprites of a certain type in a row". That's a tad wordy, so I guess "sprite family" can indeed be used for the purposes of this proposal instead. -- KOOPA CON CARNE 18:59, October 28, 2024 (EDT)
OK so.... what is the negative you are seeing to this? It seems like you agree with what the proposal actually aims to do, so I'm not really understanding your opposition. It's like how "don't optimize images with color-changing metadata" is a rule - most people can't tell the difference, but it affects the accuracy and presentation, so that's why that rule is in place. This is also for the "accuracy and presentation" reasoning. Doc von Schmeltwick (talk) 19:07, October 28, 2024 (EDT)
What I agree with, is that assets extracted from the game shouldn't be tampered with before they are uploaded on the wiki. The native size and optimizations should still inherently be part of the asset. What I disagree with, is that such a principle should extend to their presentation on mainspace articles. An image gallery is not a sprite sheet, it's demonstrative. If you think a gallery of assets can benefit from a few fine adjustments to accommodate scale and aesthetic sensibility, by all means do it. I agree the Shy Guy icon you show in the proposal looks too large and should be scaled down a little, as I did with the giant banana I mentioned previously. Enforcing the standard you propose across a demonstrative gallery is shifting the priority on technical accuracy. -- KOOPA CON CARNE 12:19, October 29, 2024 (EDT)
The actual argument of this proposal is different from the last one. This isn't specifically aiming for native dimensions, though that would still be the "easy way" imo. This allows for cropping as long as the cropping is to a consistent size for said related assets. Doc von Schmeltwick (talk) 12:40, October 29, 2024 (EDT)

@UltraMario - You... do realize that cropping the files is where the "tampering" comes into play, right? If they're displayed as they are in the game, they are untampered with. Cropping them down is, by definition, tampering with them. I think you need to reword that. Doc von Schmeltwick (talk) 17:07, October 28, 2024 (EDT)

@Fun With Despair - Except most of them are already like this - this is just making an unofficial rule we've used for years an official one for practicality. In this case, doing the opposite would be busywork. And making them consistent is busywork I am willing to do. Doc von Schmeltwick (talk) 17:35, October 28, 2024 (EDT)

Besides, being a lot of work hasn't stopped proposals that take even more work to implement from passing. It's a flimsy reason to oppose a change. Hewer (talk · contributions · edit count) 18:02, October 28, 2024 (EDT)
Not opposing because it's a lot of work, opposing because it's a lot of work in service of something that is unnoticed and not cared about by the vast majority of users. The citation proposal is a bad example because that is actually something important to the accuracy of information on the wiki. This doesn't do much of anything at all besides force small edits to many old images.--Fun With Despair (talk) 18:33, October 28, 2024 (EDT)
That could be said about proposals in general. If it doesn't matter to you, wouldn't it make more sense to not vote at all? If I see a proposal on a subject I don't care about, I just don't vote. After all, if it matters to someone, it matters in general and shouldn't just be opposed because of what amounts to "I don't care about this." Doc von Schmeltwick (talk) 18:36, October 28, 2024 (EDT)
I'd argue a majority (or at least significant number) of readers likely don't care either way about citations for names in other languages. But that doesn't mean people who do care about the change don't exist, or that it's inherently a bad change. I think "eh who cares" is also a flimsy reason to oppose a change. Hewer (talk · contributions · edit count) 18:38, October 28, 2024 (EDT)

Wait, so if this is already often the way things are, will the oppose option change that? That would mean this proposal lacks a "do nothing" option. Hewer (talk · contributions · edit count) 18:07, October 28, 2024 (EDT)

Oppose is a "do nothing." I'm not going to include an option for what I would consider a negative change. Doc von Schmeltwick (talk) 18:28, October 28, 2024 (EDT)
Wasn't suggesting you should, just got confused since you were making comments about "doing the opposite". Hewer (talk · contributions · edit count) 18:31, October 28, 2024 (EDT)
That was mainly directed at the "too much work" argument. Doc von Schmeltwick (talk) 18:32, October 28, 2024 (EDT)

@Camwoodstock - Things like the TTYDr bestiary images are not covered by this proposal, only small icon sprites that are intended to be square anyway. Doc von Schmeltwick (talk) 19:46, October 28, 2024 (EDT)

For the record, we know that wasn't exactly what the proposal was targetting, we mostly mentioned it as it's a pretty striking example of how including these transparent margins in the images themselves can backfire (besides, it's one of the most recent examples of such a thing happening.) We hope that makes sense, anyway. ~Camwoodstock (talk) 19:48, October 28, 2024 (EDT)
I still don't see why it's preferable to be forced to use the HTML to make them somewhat close-ish to accurate when simply letting it have the one or two columns of blank pixels that it's supposed to have on one side of it would look better for practical reasons anyway. It's a lot simpler and doesn't hurt anything to do. Doc von Schmeltwick (talk) 19:52, October 28, 2024 (EDT)
Because sometimes, you don't want them to be entirely accurate; while an original-resolution image might be wanted for, say, a gallery or a table, in an article, template, or especially in an infobox, you probably don't want the original size and would want something a lot more readily scalable, without transparent margins baked into the image that you need to futz with. At best, it would be too small to add a proper caption to; at worst, you basically gut the clarity of the image itself. For example, while not an "icon" in the sense of the original proposal, the articles for various objects from Super Mario Land upscale the images outside of their original context. Infoboxes on articles such as the Lift Block would be rendered borderline incomprehensible if the images were not enlarged like this. And the grown image size is accomplished not via baking it into the files themselves, but via using fairly basic wikiscript or HTML; that way, on the main article, they can still appear in their original format. This general philosophy applies to icons as well, which is why we bring it up.
Again, if someone was looking for the raw, unedited sprites, they would likely head to The Spriter's Resource and not us; our goal here is to make these images accurate, of course, but we need to make them both usable in articles and also keep them standardized between one another; baking transparent margins into the images themselves, even if technically accurate to the source material, does run counter to that latter goal. ~Camwoodstock (talk) 21:09, October 28, 2024 (EDT)
There are plenty of instances where we'd have to edit ripped textures anyway because they're ripped rotated or flipped. Cropping to content is similar to those nondestructive edits and I still fail to see how it's such a big issue, we don't need to preserve transparent pixels just because image editors deliberately padded out assets just for the game engine to decipher properly. Otherwise we should upload sprites without any color data and their palette data as separate entities. BabyLuigiFire.pngRay Trace(T|C) 21:15, October 28, 2024 (EDT)
It's destructive to me. ._. Also, saying "zero" readers is obviously wrong if there's people supporting this. "Who cares" is never a good argument. Doc von Schmeltwick (talk) 22:10, October 28, 2024 (EDT)
@Camwoodstock - Boosting them by a consistent size factor (like 50%, 200%, 300%, etc) is perfectly fine - Lift Block, for example, is sized up by 1000%. And it's a lot easier to do that when they have consistent base dimensions so you don't have to look the specific dimensions to resize them by for each image separately. Having all the 32px images display at 64px is a lot simpler than having to look through each to see which needs to be at 64, which needs to be at 62, which needs to be at 58, and so on. That's pointless, tedious, and can be prevented completely by doing what this proposal aims for. And again, non-consistent size factors, like "just make them all display at 50px!" are really messy - see the Mario Power Tennis example above, and how Shy Guy's icon is ultra pixelated while Bowser's is fairly crisp. It's grossly inconsistent, and on a table, it can't just be rawsized with a percentage (and rawsize in galleries only works for making them bigger, not smaller). Doc von Schmeltwick (talk) 00:45, October 29, 2024 (EDT)
I was the one who uploaded these bestiary images, and I had a few reasons. The main one is that some images like Smorg are cut off by the borders and would look strange when cropped. Also, since each of the Tattle Log images display against a border and background that I was also able to rip, I was hoping we'd be able to fit the enemy images over the background and border so it'd be more accurate to how it appears in-game. Scrooge200 (talk) PMCS Mustard Cafe Sign.png 20:30, October 29, 2024 (EDT)

By the way, a striking example of ripped assets that are extremely counterpoint to this proposal are the Mario Party: Island Tour space icons. Every single one of those icons are cropped from a single texture that compiles all of them, absolutely requiring you to crop images and then crop to content because none of the options suggested that would "encourage" them cover those instances. Hence why I think it's extremely pertinent to encourage crop to content except for formatting purposes in regards to tables. In addition, icons ripped may also come with engine gamma-fixes or even be outright flipped or rotated all which require correction in display for browsing purposes. BabyLuigiFire.pngRay Trace(T|C) 21:10, October 28, 2024 (EDT)

Hence "when applicable to their origins". As that one is done differently, it is not applicable. This textureMedia:MK8DX-BCP audience TVV.png was stored in a similar manner with all eight of its frames in a single image (evenly spaced), while there's also this group texture imageMedia:MKAGP audience.png that has someone sideways. Doc von Schmeltwick (talk) 22:06, October 28, 2024 (EDT)

Some important things to note:
1. The proposal only applies to icons that have a natural similarity, such as characters, items, board spaces, badges, etc. It does not apply to textures, screenshots, logos or scanners.
2. In fact, the wiki and the TSR do not have the same purpose. The wiki is not a graphics museum, nor does the TSR have informational content. But this has nothing to do with what the proposal suggests is the organizational factor.
3. "Who cares?" Yes, the readers and Super Mario enthusiasts who visit the site every day may not care. But the proposal is not for them. After all, are they the ones who vote here? The proposal is for the editors, for those who submit images and create galleries. Approving this would only be a way to better organize what is already common practice.
4. This prevents things like itMedia:M&S2014 Mii Costume 55.png.
blueberrymuffin (talk) 17:44, October 29, 2024 (-03 UTC)

What constitutes as an "icon" is entirely arbitrary in terms of graphics, there is technically no difference between graphics HUD of a character's disembodied head in a map and images used as flair in menus, or images of items in say Mario Party 4, or little images in the group photo in Mario Superstar Baseball. As for the "who cares" statement, that's specifically why I voted to oppose: I don't care about what this proposal wants to implement, I think it's way too draconian for the purposes of this wiki, and I am having my voice heard, and there is a discernible amount of people who share that sentiment. Editors use this wiki too. I also don't see the issue with the cropped Mii suits, MediaWiki has the tools to format those images should they be formatted. BabyLuigiFire.pngRay Trace(T|C) 23:18, October 29, 2024 (EDT)
"MediaWiki has the tools," does it? Please tell me how, using the [[File:xxxxxxx.png]] type of image, you can implement a resizing of, say, "50%" rather than individually going in and checking the pixel dimensions and dividing it by two yourself. As far as I am aware, you cannot, and when there's 70 or so images all with different dimensions, that's adding a needless amount of tedious work when the obvious solution is to give them the same dimensions in the first place so it only needs done for one value. And obviously, what makes an icon is determined by whether it is used as an icon. That doesn't even need said, so I don't know where you were going with that. Doc von Schmeltwick (talk) 00:29, October 30, 2024 (EDT)

I do not know if this has been mentioned or demonstrated yet, but this is what the Mario Kart: Toadstool Tour icons look in a gallery when rawsize is integrated:

  • MarioMPT.png
  • Luigi MPT.png
  • Shy Guy MPT.png
  • Peach MPT.png
  • Yoshi MPT.png
  • DK MPT.png
  • Bowser MPT.png
  • WarioMPT.png

and this is what they look like when it is added to the gallery as laid out in this proposal, with heights and widths set to 72.

  • MarioMPT.png
  • Luigi MPT.png
  • Shy Guy MPT.png
  • Peach MPT.png
  • Yoshi MPT.png
  • DK MPT.png
  • Bowser MPT.png
  • WarioMPT.png

I do not know if this is apparent in all displays, but Donkey Kong and Bowser are smaller than they should be in the second row. This is happening because the dimensions set for the gallery (72) are smaller than the dimensions of the sprites for DK and Bowser. When the heights and widths are changed to 79 (the pxl height of the biggest sprite), it looks like this:

  • MarioMPT.png
  • Luigi MPT.png
  • Shy Guy MPT.png
  • Peach MPT.png
  • Yoshi MPT.png
  • DK MPT.png
  • Bowser MPT.png
  • WarioMPT.png

I do not know if has been alluded to elsewhere in the discussion or changes anything, but I just wanted to point this out. In galleries, you can use rawsize to accurately display assets to scale as long as their are no dimensions set for the gallery, or the dimensions set are larger than the largest sprite. - Nintendo101 (talk) 20:04, October 29, 2024 (EDT)

But you can't shrink them or use that outside of galleries, so it is not a solution to the primary issue of "it screws up table cell widths and heights," and "you'd need to go in and resize each individually on a table since mediawiki doesn't have a percent-based standard image-resizer, only a pixel-based one, and that's an unnecessarily large amount of work and added HTML for adding proper-sized bounding boxes separately, needlessly bloating the page's byte count when the easy, practical, and obvious solution is to just upload them with the intentional shared dimensions in the first place." Doc von Schmeltwick (talk) 00:26, October 30, 2024 (EDT)
I honestly feel these are valid points. I found instances where it is easier to us certain assets in tables when they are all squared in dimension, and I personally have not heard persuasive reasons why easy integration into templates or tables should always take a backseat to their presence in galleries since we are primarily a resource to be read. Not just browsed. However, this is again a case where I feel allowing users to exercise discretion would be better than a rule. For example, I agree that squaring the Double Dash!! icons is nice, but I don't know how that really benefits the display for the Mario & Sonic Mii costumes.
For clarity, I would not support a proposal that insists we must always crop to content. I understand assets are not always restricted to galleries, and tables and templates are often setup with reliable size parameters. It is generally easier to edit an asset once rather than adjust all the tables it appears to ensure it is displayed in a preferred way, and while cropping to content is nice, I do not personally think it really "ruins" the display in a gallery if one or two assets are out of alignment with their neighbors or look smaller in preview. I at least do not think it is so unsightly that cropping to content should be prioritized over their utility outside of galleries. Users should have the ability to exercise discretion. It remains an important part of making this a communal space. - Nintendo101 (talk) 02:28, October 30, 2024 (EDT)
Keep in mind the proposal is not specifically about keeping the original dimensions, it's more about consistency - cropping can occur as long as that too is consistent. And if an icon is completely unique and not part of any "family" with other ones, then it doesn't matter. Doc von Schmeltwick (talk) 02:36, October 30, 2024 (EDT)

@Doc von Schmeltwick I think you're missing the point the opposition here or in the previous proposal is trying to make. As far as I'm aware, no one's saying "never do this". It's already done on the wiki, and it's good when the circumstances call for it. I don't think the Diddy Kong Pilot example you posted is that bad but it's definitely better at the consistent dimensions, and I don't see anyone here clamoring to crop down the Double Dash icons either. What I take issue with, and I assume many of my fellow voters feel the same, is this proposal's goal to essentially enforce that across the wiki whether it's helpful and wanted for design purposes or not. The Mario Power Tennis icons you used as an example aren't currently used anywhere on the wiki where inconsistent dimensions actually matter. I assume the Mario & Sonic Mii costumes would also get caught up in this since they're technically icons, but in my opinion, consistent sizing is unnecessary and the images look worse with the extra space needed to accommodate the largest costumes. At the very least you can't say it looks objectively worse that they're not all centered in this case. You've mentioned having OCD several times in these types of discussions, so I recognize and sympathize that some of these inconsistencies can be frustrating for you, but your personal preferences and irritations aren't always going to reflect the majority of the userbase.

Also, the reason rawsize keeps getting brought up is because you were the one who started this proposal with a comparison of images in galleries and made it seem like a key point of your proposal. I'm not sure why you did that, and it feels misrepresentative of the situation at best since you were the one who proposed its wider usage a few months ago and should've known it was an easy solution to the specific problem you were presenting. --Waluigi's head icon in Mario Kart 8 Deluxe. Too Bad! Waluigi Time! 14:59, October 30, 2024 (EDT)

I know I proposed that addition. I mainly used a gallery as an example here because it was convenient to bang out quickly, not at an illustration that it is the only issue brought on by this. In regards to making it a rule though, please recall I am not stating here it "has" to be the native dimensions specifically. Also, we have other image upload rules that some people and/or wikis might consider "draconian" but have been around long enough here that they make perfect sense to us (don't upload non-animated .gif's, don't convert .jpg's to .png's and especially don't give them transparency, don't optimize images with metadata, and the above proposed one with currently unanimous support regarding NES palettes), so I really don't see how this ends up any different. I specifically noted in the proposal and its very title that if it straight-up doesn't work in whatever context, that it doesn't need done for it, so I don't see how it ends up as a problem anyway. Doc von Schmeltwick (talk) 15:58, October 30, 2024 (EDT)
This unfortunately contributes to the same problem I had with the previous proposal. Your reply here makes it sound like there would be no substantive or practical difference between how folks generally handle assets already, making it unclear what would actually change if the proposal were to pass. What would change? — Nintendo101 (talk) 16:42, October 30, 2024 (EDT)
Because when I tried to enforce "how folks generally handle assets already" it was treated as me going notably out-of-line. There's always gonna be someone who uploads a .jpg -> .png image because they don't know any better or don't realize it (I'm guilty of the latter from before I knew to check with the "save image as" function), and that needs to be corrected - it is how we "generally do things," but we do it because that is a thing that needs discouraged, hence there being a rule. I see this as no different from that. Doc von Schmeltwick (talk) 18:52, October 30, 2024 (EDT)
This proposal is just going to result in a patchwork of interpretation of how to approach these assets. It's a sign of a very flawed proposal. Doesn't help that your entire bedrock of reasoning that led to this kind of proposal (that we should be encouraged to maintain the original dimensions of a ripped sprite), which I have deemed utter nonsense and I stand by it being utter nonsense, continues to be maintained. This leaves me with a not very confident impression you have any clue how these assets are created, stored, and used in a video game, that you understand why an asset is padded and has dimensions of 128x256 or something and why this doesn't mean a wiki should be necessarily maintaining these dimensions. Icon showing how many lives Mario has left. From Super Mario 64 DS. It's me, Mario! (Talk / Stalk) 00:33, October 31, 2024 (EDT)
I have explained time and time and time and time and time and time again that this proposal does NOT require the original dimensions. Just shared dimensions. I figured putting it at the top in ALL-CAPS BOLDED BRIGHT PURPLE would be enough to get people to actually read and realize this, but apparently not. Please acknowledge this and stop treating it as though that is my argument here when it is not. Doc von Schmeltwick (talk) 01:02, October 31, 2024 (EDT)
Let me clarify: when I mentioned the bedrock of reasoning, I meant to contextualize the situation that led up to the proposal. It's to support my criticism of your proposal, which was made in response to the earlier one that was canceled from mounting opposition, that this follow up proposal is poorly made. Due to the timing of things, it comes off as an attempt to simultaneously continue your practices of insisting that image dimensions are important information to maintain (they are not) but with flawed solutions designed around this flawed principle. To me, this is a confusing proposal that will lead to conflicting approaches to how an asset will be handled, and the examples used don't do a great job clarifying points (this example shouldn't even be a table imo). Icon showing how many lives Mario has left. From Super Mario 64 DS. It's me, Mario! (Talk / Stalk) 02:04, October 31, 2024 (EDT)
They absolutely are, but regardless of that, if it wasn't a table and were instead a gallery, the OCD-triggering vertical position issue would be even worse. (Seriously, I'd get less feeling of disgust from an animated loop of Wario puking up an endless stream of black dioxic squid ink onto Penny than I get from this - hell, that wouldn't even be half of it. This is trypophobia-level shit here.) In regards to that edit you made to your vote, obviously non-icons are completely unrelated to this. I worded this as specifically as I could to avoid it being abused. This is for icons and icons alone, and by "game-related," I mean such as "MKDD-related" or "MPT-related" to determine which group gets which parameters. Doc von Schmeltwick (talk) 02:21, October 31, 2024 (EDT)
I think there was some misunderstanding amongst parties after the previous proposal was cancelled. I at least do not think anyone intentionally meant any harm. The impression I have is that a lack of familiarity with certain tools lead to some bad-faith interpretations of why folks did the things that they did. But regardless, I think a gentler, less heavy-handed approach to these types of things would be better going forward. I do not think this needs to be strict policy, or something staff and other users need to enforce. But generally, as a courtesy, if one wants to adjust assets that are being used in particular fashions outside of galleries, it does not hurt to reach out and ask if it would be okay to adjust their dimensions. And if a user cropped material, one should not invoke rules that do not exist as actual policy, or bring up some "innate" sprite-ripping principals that do not exist. (I understand the point of this specific proposal is to make certain rules concrete, but I am referring to some of the interactions I saw between users before this current proposal was raised.) Rather, there is no harm in explaining why it is helpful to keep certain assets at particular dimensions for tables and templates. I know some folks have mentions CSS coding, but no one has bothered explaining what that would look like, and generally, adjusting the empty space around an asset is the most user-friendly and intuitive path to take. - Nintendo101 (talk) 01:28, October 31, 2024 (EDT)

@SeanWheeler: I believe the proposal is just for the icons within a particular "set" to be consistent with each other, not icons of different sets. Hewer (talk · contributions · edit count) 08:46, October 31, 2024 (EDT)

@Killer Moth - See the Diddy Kong Pilot table above and the alignment issues it had before I enacted this principle on it, and how it's much more eye-pleasing afterward? That is the point. Without it, they tend to look gross - like that table did before. If you can't see why that's an issue, then I envy you, but it really looks bad - the version with the alignment lines is how my eyes see it even when they aren't there. And I have still yet to see any actual downside to this other than people trying to cram them into signatures, which is... not what the wiki is about and that absolutely should not take priority in presentation. Same reason we don't add fake armbands to Bowser's SMB1 sprite since that's transparency. Doc von Schmeltwick (talk) 12:50, October 31, 2024 (EDT)

Again, the dominant perspective of the opposition is not "no, this is a bad idea. No one is allowed to set up assets to make them aligned as they appear in the Diddy Kong Pilot table." Personally, I think the Diddy Kong Pilot example you provided is aesthetically pleasing when the sprites are all aligned, and folks should have the freedom to do that. It is for similar reasons that I integrated organized 100x100px sizing for all images in the mainline game tables and try to ensure columns are the same width across all tables in an article. Rather, the oppositional perspective is, "no, we do not want to police this or make this a type of rule. People should have the freedom to experiment with what types of dimensions they want for the assets used in their tables, and we do not agree that cropping to visual content is inherently destructive of an asset." - Nintendo101 (talk) 13:11, October 31, 2024 (EDT)
I feel doing this is an absolute good, and if someone has the freedom to crop, I have the freedom to restore. Two-way street and all that. Also, LGM's argument from what I can tell is exactly that (which coupled by the general belligerent/caustic directing of profanity towards it) fueled most of this. Doc von Schmeltwick (talk) 13:57, October 31, 2024 (EDT)
I respect that you view a policy revision like the one advocated for in this proposal is an "absolute good," but I do not think you have made a compelling persuasive argument as to why, or at least not one to me. And I understand your concerns over a "two way streak," but we do have courtesy policies on this wiki. Many of them seem relevant, but the one I would like to highlight is that users should not participate in other users' editing projects without asking them first. Galleries are more of a shared neutral space, but if one wants to crop to content or retain space around ones that are integrated into tables in a spatially-dependent way, it would be courteous for one to reach out to the uploader of those assets first or at least touch base with them. The Mario Power Tennis ones, for example, have only been integrated in one table at the time of this comment and cropping them does not seem to have impacted the layout or scaling in any perceivable way to me. There was no demonstrable harm.
I do not think LGM is advocating that arranging tables like the one in the Diddy Kong Pilot example should not be allowed, or at least that is not my reading of her comments. I believe her perspective is not dissimilar from mine. I would personally appreciate it if you reviewed what I wrote in my vote above. I think it would be clarifying.
I could be wrong, but I believe the curtness comes from statements you had included in the previous proposal that, from her experience as someone who also rips assets and someone who participates on this wiki very regularly, she knew were objectively false, but you were presenting them as hard facts and even invoking them to talk down to another user. This is understandably not appreciated conduct, and it is not uncommon from you. She can speak more to that if she wants to. - Nintendo101 (talk) 16:13, October 31, 2024 (EDT)
The statements I made then were accurate too, our perspectives are just completely incompatible. And considering in the cases of those Mii costume images, here, the original uploader (who is supporting this proposal) explicitly wants to keep them they way they were uploaded in, which is what I reverted them to, and LGM is reverting them from. The specific thing she has said that I take issue with is her claim that the space is absolutely worthless and should be removed from everywhere it feasibly can be, which naturally I perceive to be extremely misguided. As for the Mario Power Tennis table, it only looks as good as it does thanks to my own ingenuity of hiding a cell divider bar to make two cells look like one cell - that table is the one that has given me trouble in that regard. Presumably if they are changed to a tabular form, those icons will remain useful if we start covering rivals for it like we do for the 64 game, but by then it'd be easier if they did share parameters. Doc von Schmeltwick (talk) 16:39, October 31, 2024 (EDT)
Maintaining space needs to be done for a good reason, and having it simply because it was ripped that way is not a good reason. It is okay to find an example where extra space is needed but that table provided is a heavily flawed example due to being an inappropriate use of a table and the suggestion below that does fix the issue to begin with (and probably there is a code for horizontal alignment too). As for Mario Power Tennis table, if you're referring to this one[1] that's another fundamentally flawed table which was one of the many other tables that prompted criticism by multiple users and would not be my example to try to illustrate a proposal. The one example I think may work is File:MK8 Mario Icon.png due to its use in multiple pages and being in an array with similar scaled images, which were all put in a 128x128 box. Not sure if cropping to content is going to lead to unexpected results but for the record, I don't see the point of cropping to content for these Mario Kart 8 things either, since they're already reasonably occupying the space (unlike those Mario Kart Double Dash map icons which were heavily padded); it's a case of don't fix what isn't broken. The proposal doesn't really advocate any of this. It's, what I can glean, a way to maintain aspect ratio while cropping tightly as possible without losing information, but dressed up in bad examples and imprecise wording (like the proposal does not even define what a "game-related 'icon-type' image" is, so). Icon showing how many lives Mario has left. From Super Mario 64 DS. It's me, Mario! (Talk / Stalk) 20:56, November 2, 2024 (EDT)
I was more referring to how the N64 Mario Tennis had a separate "partners/rivals" table before I incorporated that information into the main character table, and it used the face icons. I was saying if MPT did something similar, which it probably should if there is indeed a hard-coded system like that in the game. I don't really think I need to define the icon thing; but if you insist, I mean "icon" as in "a small image representing a subject," with "game related" simply meaning as a per-game basis (ie, MK64 icons have no bearing on MKDD icons). (Also, off-topic, but how else would the Diddy Kong Pilot example be handled if not as a table? There's other information below it that's been cropped out.) Doc von Schmeltwick (talk) 21:52, November 2, 2024 (EDT)

The Diddy Kong example, too, can be easily fixed with aforementioned styling, in this case by using vertical-align: bottom. That is to say however that those sprites are of a size where it makes sense for all of them to just retain their original size, I would not crop those either. There are cases like the Mii suits from the other day where it does make sense to crop them. Lakituthequick.png Lakituthequick 17:14, 31 October 2024 (UTC)

Not all of them have flat bottoms in other games, of course, while that also doesn't fix the left-right issue. But yes, I digress. Doc von Schmeltwick (talk) 13:57, October 31, 2024 (EDT)

Another thing I want to ask the opposition: if thisMedia:058-SMMMontyMole.png is to not be cropped, why should any of the other things? Doc von Schmeltwick (talk) 19:24, November 6, 2024 (EST)

Allow unregistered users to comment under talk page proposals

One thing I never understood about rule 2 is why unregistered users are not allowed to comment under proposals. The rule states: "Only registered, autoconfirmed users can create, comment in, or vote on proposals and talk page proposals." While it makes sense on this page, it is semi-protected after all, talk page proposals are a different story. Why should IPs be prevented from commenting under talk page proposals? Most IPs are readers of this wiki and they should be allowed to express their opinion on wiki matters too. I've seen several examples of IPs making good points on talk pages, I imagine most of them are regular visitors who are more interested in reading rather than editing, and allowing them to leave a comment under a TPP would only be beneficial.

If this proposal passes, unregistered and not-autoconfirmed users would be permitted to comment under talk page proposals. They still wouldn't be allowed to vote or create proposals, only comment.

Proposer: Axii (talk)
Deadline: November 14, 2024, 23:59 GMT

Support (unregistered users proposal)

  1. Axii (talk) Per proposal.
  2. Hewer (talk) Wait, this was a rule?
  3. Pseudo (talk) This rule doesn't really seem like it accomplishes anything.
  4. Blinker (talk) Per proposal.
  5. FanOfYoshi (talk) Why wasn't this already applicable?
  6. EvieMaybe (talk) it makes sense if it's just for comments
  7. Drago (talk) The rule was only changed because of this page's semi-protection and not, as far as I can tell, because of any misuse of comment sections by unregistered users. Per all.
  8. ThePowerPlayer (talk) This is a reasonable change.
  9. Dine2017 (talk) Per proposal.
  10. Ray Trace (talk) Anons use the wiki too and should be able to voice their concerns in the comments section, there's no reason to bar them the ability to comment.
  11. Mario (talk) We'll see if the Bunch of Numbers behave.
  12. Nintendo101 (talk) Per proposal.
  13. Killer Moth (talk) Per proposal.

Oppose (unregistered users proposal)

  1. SeanWheeler (talk) Unregistered users just have numbers for their names, so that looks awkward with the way the votes are counted. It's easy to use your IP to sockpuppet, so I wouldn't want anyone doing that for the votes. And even for just the comments, I wouldn't want anyone to sockpuppet in an argument for manipulation tactics. Nor do I want to see poor grammer or vandalism. Anyone who wants to participate in voting discussions should sign up. This page was semiprotected for a reason. SeanWheeler (talk) 00:19, November 1, 2024 (EDT)

Comments (unregistered users proposal)

"While it makes sense on this page, it is semi-protected after all"
If the protection history displayed above this page's edit box is any indication, it was the other way around. There was already a rule against anonymous voting on this page by the time it was semi-protected. In that case, it might be useful to look into the reasons this rule was made in the first place and, if there's any disagreement, extend this proposal to this page too. As to where these reasons are stated, I don't know. My assumption is that the rule exists because anons are more prone to shit up the place than registered and autoconfirmed users. -- KOOPA CON CARNE 16:15, October 31, 2024 (EDT)

I couldn't find a reason why IPs were disallowed to comment. My only assumption is that when this page was protected the rule was modified to mention that IPs couldn't comment, but talk page proposals weren't considered. I'll look into it more and potentially add a third option to allow IPs to comment here as well. Axii (talk) 16:20, October 31, 2024 (EDT)

@SeanWheeler - This isn't about voting, it's about commenting. Doc von Schmeltwick (talk) 01:04, November 1, 2024 (EDT)

For real, do you even read before voting on proposals? It's a small paragraph that makes it very clear that it's only about commenting under talk page proposals, not even on this page. Axii (talk) 01:07, November 1, 2024 (EDT)

Decide whether to cover the E3 2014 Robot Chicken-produced sketches

For E3 2014, Nintendo's press conference was a video presentation similar to today's Nintendo Directs, featuring clips of stop-motion sketches by the producers of Robot Chicken. I feel that these qualify to receive coverage on this wiki, since their appearance in a video published by Nintendo means that they are officially authorized, and they prominently feature Mario franchise characters. However, I have never seen the sketches discussed in any wiki article, nor are they listed on MarioWiki:Coverage, so I thought it would be appropriate to confirm their validity for coverage with a proposal.

The following articles would be affected by this proposal if it passes (since the E3 2014 video is not a game, film, etc., coverage is best suited to an "Other appearances" section):

Regardless of which option ends up winning, a note should be added to MarioWiki:Coverage to explain how these sketches are classified. Also, I'm clarifying that this proposal does not involve any sketches from Robot Chicken itself, since those are clearly parodies that have no approval from Nintendo.

Proposer: ThePowerPlayer (talk)
Deadline: November 16, 2024, 23:59 GMT

Support

  1. ThePowerPlayer (talk) Per proposal.
  2. Hewer (talk) This feels logical enough that I'm not sure it needs a proposal or even an explicit note on the coverage policy, but per proposal just in case.
  3. EvieMaybe (talk) per proposal
  4. Tails777 (talk) Some of them were Mario related so I don't see any reason not to mention them. Per proposal.
  5. Ray Trace (talk) Per proposal.
  6. Camwoodstock (talk) At first, we were a bit confused as to why only E3 2014 was getting this treatment, but it turns out that no, actually, we do mention a few things from E3 presentations and Nintendo Directs in these articles, we just never internalized that information. If we cover that Wario animatronic puppet from E3 1996, and we cover Bowser in Bayonetta 2, we don't see why we shouldn't cover this specific E3's trailers just because it was by a different producer.
  7. Nintendo101 (talk) Don't see why not.
  8. Killer Moth (talk) Per proposal.

Oppose

  1. SeanWheeler (talk) Robot Chicken is an adult parody show. To cover Robot Chicken in Mario's history is like taking the Family Guy cutaway gags as canon. The Robot Chicken sketches including the E3 specials are covered in List of references in animated television.

Comments

Uh, SeanWheeler? You may want to see MarioWiki:Canonicity. There is no canon in Super Mario. And being an "adult" show shouldn't prevent text from being referenced in normal articles given the wiki does not censor anything. (The last point on MarioWiki:Courtesy, and the set of arguing over Bob Hoskins's page quote.) I guess one could discount the sketches on account of them as parodies, but given the "no canon" bit that seems hard to justify. Salmancer (talk) 21:01, November 3, 2024 (EST)

It's been a hot minute, but aren't the 2014 E3 sketches not even a part of Robot Chicken, anyways? Just produced by the same team behind them. It would be like prohibiting mention of Ubisoft because they developed those South Park games. And even if the sketches for E3 2014 were particularly "adult", overwhelmingly adult content hasn't stopped us before. ~Camwoodstock (talk) 09:43, November 4, 2024 (EST)

@ThePowerPlayer Looking at these sketches, why not create an article covering them? It would be inconsistent not to cover them separately as well, not just as sections of other articles. Axii (talk) 13:26, November 4, 2024 (EST)

The proposal is to cover them in "Other appearances" sections, which are supposed to cover things without articles. Also, to my knowledge, they don't exactly have an official title that we could use. Hewer (talk · contributions · edit count) 13:32, November 4, 2024 (EST)
This is exactly why I brought it up. It would be weird not to have a page on them when all other content does. Lack of an official title never stopped us either :)
Axii (talk) 03:42, November 5, 2024 (EST)
My point is that not "all other content" has a page, and that's what "Other appearances" sections are for. I don't think these short, nameless skits from an E3 presentation that are more about Nintendo in general than specifically Mario are really in need of an article when this proposal passing would mean their entire relevance to Mario would already be covered on the wiki. They aren't even the only skits with Mario characters from an E3 presentation, E3 2019 has an appearance from Bowser. Hewer (talk · contributions · edit count) 06:34, November 5, 2024 (EST)
Exactly. Making an article would just lead to a lot of unnecessary descriptions of content that has nothing to do with the Super Mario franchise. ThePowerPlayer Slug.png ThePowerPlayer 19:44, November 5, 2024 (EST)

Require citations for dates

Recently, a proposal decided that not sourcing a foreign name puts the article into a meta category of "unsourced foreign names". But I'd say a similar idea should be implemented to dates for things such as media releases, company foundations, and game, company and system defunction. Because, for example, there's been many times where I've seen an exact release date pinpointed and I think "where did they get that date from?", and after a bit of research, I can't find any reliable source with said exact release date. Dates being sorted like this would be nice.

Proposer: Starluxe (talk)
Deadline: November 16, 2024, 23:59 GMT

Support

  1. Starluxe (talk) Per my proposal
  2. ThePowerPlayer (talk) Per proposal.
  3. Super Mario RPG (talk) I agree.
  4. Camwoodstock (talk) Wait, how is this not already policy??? Per proposal.
  5. Shy Guy on Wheels (talk) I personally find that a lot of release dates for games on the internet come from hearsay, and copying what other sites say without actually double checking that info, so this would be great for guaranteeing accuracy.
  6. Technetium (talk) Per proposal.

Oppose

Comments

What source you think is acceptable for release dates? I personally use GameFAQs. BabyLuigiFire.pngRay Trace(T|C) 20:05, November 2, 2024 (EDT)

GameFAQs isn't officially related to Nintendo, right? If so, then no. It needs to be an official source. Because if anything, GameFAQs' release dates could be taken from another unofficial source, making that an unacceptable source. Starluxe Shy Guy in Super Mario Maker. 13:00, November 6, 2024 (EDT)
But that is a major problem of mine regarding old games, especially those that came out before the internet. Game sites such as GameFAQs and Wikipedia have it down all the time, especially those as old as GFAQs, but I don't think Nintendo themselves keep track of it too much barring recent titles or titles they are currently selling, with rare cases of them citing release dates in games themselves (like Super Smash Bros. Brawl's chronicles). For example, Wikipedia does cite Mario Kart: Double Dash's release date in a financial statement by Nintendo but other games such as the original Thousand Year Door's release dates remain unsourced. I'll need an answer to what sources you plan on using to cite the release data. BabyLuigiFire.pngRay Trace(T|C) 18:28, November 7, 2024 (EST)
This has come up a few times, but the state of proper video game release date archival is dreadful. I would argue it was around the time of digital storefronts that they were catalogued more seriously. I really want to support this proposal, but first, I think it's really important to decide what type of sources are usable. Sites like GameFAQs and MobyGames? They're actually user-contributed, in theory, I guess. You can contribute there. The problem is that I don't know anything about their curation. Unlike a wiki, you can't look back. Someone can contribute something else that overrides your contribution, and you won't know why (probably something to the effect of "another online source"). So, I wouldn't take sites like them, despite search results doing a good job of making sure they're one of the first things you see. Wikipedia has taken to citing the copyright office, but as far as I know, details like that are not always the same thing as an actual release/airing date. My suggestion is that this needs a whole source priority of its own, preferably contemporary sources like magazines and press releases. LinkTheLefty (talk) 08:24, November 8, 2024 (EST)

Seeing how this could also apply to other things like defunction dates, I've added so to my explanation. Starluxe Shy Guy in Super Mario Maker. 12:16, November 7, 2024 (EDT)

Move "Princess Peach" and "Princess Daisy" to "Peach" and "Daisy"

Earlier this year, I made a proposal suggesting that the article "Princess Daisy" should be moved to "Daisy". That proposal was rejected, with one of the main reasons being that people were concerned about the inconsistency this would cause with Princess Peach. Since then, another similar proposal has passed that suggested moving the Koopaling articles to just their first names. So, I would like to suggest once again that I think "Princess Daisy" should be moved to "Daisy", except that this time I'm also including the option to move "Princess Peach" to "Peach".

This proposal is not suggesting that we stop using these titles for these characters completely. We should continue to do as we have done: use whatever name is used in a specific work when talking about a character's appearance in that work. I am only suggesting that the articles themselves be moved to "Peach" and "Daisy", which I believe to be their primary names.

The case for moving Daisy's article

You can read my full argument for Daisy in my previous proposal about this subject, so I'll be brief here. My key point is that Daisy has never been called Princess Daisy in any game as her primary English name. It's certainly not an unofficial title by any means, but she is and always has been called "Daisy", with no honorific, considerably more often and more prominently than her full title.

The case for moving Peach's article

The case for Peach is much weaker than the case for Daisy. Unlike Daisy, Peach is actually called by her full title in-game as her primary English name sometimes. In fact, as was pointed out in the comments of the previous proposal, Nintendo has on occasion used the names "Princess Peach" (with the honorific) and "Daisy" (without) together.

Nonetheless, her highness is called "Peach" in-game considerably more often than "Princess Peach". (To be clear, my point is not that she's never called "Princess Peach", just that "Peach" appears to be her primary in-game name, which is what the naming policy recommends.) I believe the strongest example here is Mario Kart Tour, which uses "Peach" despite having no shortage of playable drivers with excessively unweildy names.

Proposer: janMisali (talk)
Deadline: November 21, 2024, 23:59 GMT

Move both princesses

  1. JanMisali (talk) First choice, as proposer.
  2. Pseudo (talk) First choice, per proposal. The princess titles for both characters can definitely be seen as their full names, but it seems to occupy a similar space to "King Bowser" in most games.
  3. Tails777 (talk) Primary choice. Even if Peach uses her title more often, MANY games usually relegate to just calling the princesses by their names without their titles. And since Bowser is also referred to as just "Bowser" over "King Bowser" (a titled name used about as often as Princess Peach), I feel all three can just use their names without titles.
  4. Ahemtoday (talk) Only choice, per proposal. I was part of the opposition to the previous proposal, but this one fixes the issue I had with it. And anyway, in basically any game where Peach is playable, the thing written under her on the character select is just "Peach", same as Daisy, so this feels like the natural solution.
  5. Super Mario RPG (talk) "Princess" is just a title of Peach's name, and most appearances refer to her as simply Peach. The name for "Daisy" is very seldomly preceded by "Princess". Compare to Dr. Mario, where the "Dr." is an inherent part of his name, rather than a full title.
  6. Altendo (talk) If we can remove names from Sonic characters, the Koopalings, and even named identifiers like Sir and Admiral, there is no reason to not do this. Per all.
  7. EvieMaybe (talk) per Altendo, specifically
  8. Camwoodstock (talk) Per proposal, and the original proposal that spurred this one.
  9. LinkTheLefty (talk) Things are headed in this direction, let's rip the bandage off.
  10. Arend (talk) I'm more comfortable with removing the "Princess" title from both articles rather than just Daisy's. Yes, Peach is often called "Princess Peach", but I find it comparable to Koopa minions referring to Bowser as "Lord Bowser" or "King Bowser" (or, in the case of game titles such as Super Princess Peach or Princess Peach Showtime, it's comparable to the Super Mario games, which bear this title even if there's no Super Mushrooms to turn Mario into Super Mario).
  11. SolemnStormcloud (talk) Per all.

Only move Peach

Only move Daisy

  1. JanMisali (talk) Second choice, as proposer.
  2. Pseudo (talk) Second choice, since Daisy has stronger reason to be moved.
  3. Tails777 (talk) Secondary choice. Daisy is referred to as "Princess Daisy" far less than Peach is referred to as "Princess Peach", with some modern games still using Peach's title. Daisy is almost always just referred to as "Daisy".
  4. Koopa con Carne (talk) per the case being made for Daisy. Games and other media as recent as Princess Peach Showtime and the Mario Movie alternate between naming Peach with and without the honorific, so MarioWiki:Naming cannot enforce one over the other based on recency, frequency, or source priority. None of this can be said about Daisy, however. Some have argued that "Daisy" is chosen for functional purposes within games, i.e. is an attempt to keep the character's name short in areas where you can allocate a piece of text only so much memory--and I'd understand the argument, if it weren't for cases like "Light-blue Shy Guy (Explorer)", "Yellow Shy Guy (Explorer)", and "Purple Koopa (Freerunning)" which push that memory limit much further than "Princess Daisy" ever could. I also question why the naming scheme of either character has to remain consistent with the other just for the sake of it; if their patently similar appearance and roles is the sole thrust behind this point of view, what's stopping Rosalina from being moved to "Princess Rosalina", then? That's an official title, too. Better lock in and make the facts readily apparent on the fan encyclopedia.
  5. Hewer (talk) Per Koopa con Carne. I see the argument for moving Peach as well, but feel more strongly that Daisy should be moved since she's rarely called "Princess Daisy".
  6. Super Mario RPG (talk) Secondary choice.
  7. Camwoodstock (talk) Secondary choice. We need to do something about Daisy, at least.
  8. ThePowerPlayer (talk) Per Koopa con Carne.

Keep both princesses the same

Princess Comments, Peach

Miscellaneous

Either remove non-English names from cartoon dubs that weren't overseen by Nintendo or affiliated companies, or allow English names from closed captions

"What does one have to do with the other?" You'll see!

Back in 2021, there was a proposal to allow closed captions used on Mario cartoons uploaded or streamed officially online to be used as sources on the wiki. It encountered massive opposition, with one comment left by a user in a previous discussion acting as the cornerstone of the opposition's rationale. The link intended to lead to that comment, seen under that proposal, doesn't do its job any more, so I'm copy-pasting it here for your convenience.

“re closed caption: The relation between WildBrain and video streaming platforms like Netflix is the same one Nintendo has with retaillers like Gamespot: meaning the owner of the property sells the product to the retailler/streaming website, and they may supply other material (like artwork, press releases, etc) to help the client market the product. However, that doesn't mean everything the client does with the product is now official; for instance, Gamespot has in the past created fake placeholder boxarts for Mario games using edited official artwork. Gamestop may be an authorized (or "official") retailler of Mario products but it doesn't make those placeholder boxarts by association as they were made entirely by Gamespot without inputs from the creators of the source material.

“In that respect, closed captions fall in the same category as placeholder retailler-made boxarts. Closed captions are made by people with no relation to the source material or access to behind-the-scenes material like script, and who are just writing down what they hear by ear. They are not an acceptable source for spellings.”

~ Glowsquid (talk), 2021

This is valid. In all this talking about what is official and what is not, I suppose it feels right to draw a concrete line somewhere. Someone who acquires the rights to use Nintendo's or one of their partners' IP to use it for a given purpose is technically an authorized party, but they're no authority themselves over the content within. Makes sense.

...Meaning the multilanguage names invoked in the proposal's title stick out all the more like a sore thumb. A good chunk of them, at least. Why would the wiki treat a studio or company that dubs and distributes syndicated Mario cartoons to a given demographic as particularly authoritative over the content? Ultimately, it's the same situation as the one described in the quote, the apparent clincher being that it's in a different language, and I apologize, but I don't see how it is consistent to prohibit third-party English subtitles but allow foreign dubs by people that are just as far-removed from the parent company. I propose a compromise.

Of course, not all foreign dubs would be off limits as sources should the second option of this proposal win. If one can provide sufficient proof that a given dub was supervised by one or more employees representing a company with authority over the original product, i.e. that the company left their mark on the endeavor, sourcing it is absolutely fine. As it stands, though, I can already point to the Romanian dubs of the Mario DIC cartoons as ineligible for sourcing given my failing to find any evidence DIC Entertainment ever put its signature on them. (This is coming from someone who contributed a significant amount of names from these dubs. Sometimes you gotta kill your darlings.)

"So if option 1 wins, 'Ahehehaue' is considered official again?"

No. That doesn't come from a closed caption, and I consider WildBrain's issue of circular sourcing to be a whole other can of worms best left out of this week's topic.

(added 17:42, October 30, 2024 (EDT)) "Does the proposal extend to the live-action segments of the Super Show?"

Yes, they're within the same package.

Proposer: Koopa con Carne (talk)
Deadline: November 12, 2024, 23:59 GMT

Allow the sourcing of English closed captions from officially uploaded and streamed Mario animated works

  1. Hewer (talk) Perhaps I just have a more liberal understanding of "official" (as an Ahehehauhe defender), but after proposals like this, this, and this, I feel like all these should be close enough to official to be worth documenting. And aren't games like Hotel Mario a bit of a similar case, where the "official" involvement didn't go much further than licensing them?
  2. Ahemtoday (talk) I think the difference between closed captions and placeholder retailer box art is that the closed captions are a(n optional) part of the media as it can be officially experienced. As such, I think it counts as "official" regardless of who did it.
  3. SeanWheeler (talk) Well, we would need some kind of source for names of characters that never appeared in English localizations.
  4. Pseudo (talk) These names would be familiar to some viewers of the material, if nothing else, and it seems a bit odd to consider them completely unofficial even if they weren't overseen by the original creators.
  5. EvieMaybe (talk) a license is a license
  6. UltraMario (talk) Per all. I still believe that these should still count as official enough, as they are the providers of the content and it's like a license of a license.

Remove names that originate from non-English dubs of Mario animated works that were not overseen by Nintendo or an affiliated company

  1. Nintendo101 (talk) Per proposal. I found the argument persuasive.

Do nothing

Comments (closed captions vs. foreign dubs proposal)

Waltuh... I'm not voting right now, Waltuh... -- KOOPA CON CARNE 14:01, October 30, 2024 (EDT)

@Koopa con Carne By "not overseen by Nintendo/DiC", do you mean they gave the go-ahead but didn't have any direct involvement in production, or the dubs were produced by a third party with no permission whatsoever? I'd consider being more charitable for the former, but if it's completely unauthorized then that's basically equivalent to a bootleg or fan translation and probably shouldn't be covered. --Waluigi's head icon in Mario Kart 8 Deluxe. Too Bad! Waluigi Time! 17:07, October 30, 2024 (EDT)

First one. The proposal only touches on the scenario where a company that airs a dubbed Mario cartoon has a license to do so from the work's owner. Anything outside of such a licensing agreement is completely unofficial, like you pointed out. -- KOOPA CON CARNE 17:42, October 30, 2024 (EDT), edited 17:44, October 30, 2024 (EDT)

Added stipulation that the proposal extends to live-action Super Show segments. -- KOOPA CON CARNE 17:42, October 30, 2024 (EDT)

What is "Ahehehauhe?" SeanWheeler (talk) 23:29, October 30, 2024 (EDT)
It's a clip of a Super Show episode uploaded to YouTube by WildBrain, the current owners of most of DIC Entertainment's library (including their Mario shows). On the wiki, "Ahehehauhe" used to redirect to that episode's article because it was deemed an "official" alternate title given WildBrain's ownership status over the material, which many found outrageous since it barely passes as a "title" and is simply a transcription of the characters cackling in that clip. We don't even know if a human consciously named the clip that; it could've been a bot. -- KOOPA CON CARNE 06:28, October 31, 2024 (EDT)
Now, "Ahehehauhe" isn't linked to the WildBrain-related circular sourcing issues I mentioned in the proposal (they used names from the wiki in promotional texts, which Ahaha isn't one of). However, if the same policy used for the English Super Mario Encyclopedia is to be applied to WildBrain on the same grounds, then the only case where a name they used for a given subject should be employed by the wiki is (a) if the name didn't come from the wiki in the first place, and (b) there are no other known names for that subject. Even if we're to consider Ahahahue a unique and proper way to call an episode of a TV show, its use would still be untenable under the second point. -- KOOPA CON CARNE 06:39, October 31, 2024 (EDT)
If the same Encyclopedia logic applied, shouldn't it still be a redirect at least? LinkTheLefty (talk) 08:24, November 8, 2024 (EST)
Retrieved from "https://www.mariowiki.com/index.php?title=MarioWiki:Proposals&oldid=4426373"