MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
 
Line 1: Line 1:
{{/Header}}
{{/Header}}
==Writing guidelines==
==Writing guidelines==
===Encourage concise, consistent and minimalistic layouts and design for tables===
===Lower Category Item Requirement from 4 to 3===
Tables in game articles are a total playground. Overall, they often are as inconsistent and showy as they can be, and are often laid out in such a way that it makes them worse to read. Some are more extreme than others, like driver and track tables in [[Mario Kart (series)|''Mario Kart'']] articles, such as [https://www.mariowiki.com/index.php?title=Mario_Kart_64&oldid=4402277#Courses this] and [https://www.mariowiki.com/index.php?title=Mario_Kart_7&oldid=4401364#Drivers this]. Those ostentatious charts look like they belong in a promotional website rather than in an encyclopedia, and do not prioritize ease of reading and data relevancy. Some are not all that exaggerated, but still look over the top, overstyled and are more spacious than they need to be. Maybe people think it is more fun to design them like that, but they look unprofessional.
This was spurred by the introduction of the to-do bar. Thanks, to-do bar! Anyways, if you look at [[Special:WantedCategories]], at the moment, it's all entries with 3 or fewer items each; this makes sense, given we have a policy that suggests [[MarioWiki:Categories#Size and scope|categories are kept to only 4 or more items]]. However, for a good portion of the 3-itemers, these are all fairly featured images from sources like various short flash advergames, or more niche subjects like the [[MediaBrowser]] which came in a series of, well, 3 web browsers. In comparison to the 1-or-2 entry, well, entries, these have a bit more substance to them, basically waiting for a fourth image to be taken at some point; and while in some cases, that image can come up, in others... Well, what are the odds a fourth MediaBrowser is releasing when they went bust back in 2001, y'know?
 
That being said, these are the points I judged good ones to encourage when it comes to creating tables:
 
'''1. Uniformly use plain wikitable style for regular tables.''' Pages often use several styles for tables for no reason (the [https://www.mariowiki.com/index.php?title=Paper_Mario:_Sticker_Star&oldid=4399708 article for ''Paper Mario: Sticker Star''] uses four styles throughout, [https://www.mariowiki.com/index.php?title=Paper_Mario:_Sticker_Star&oldid=4399708#Status_effects here], [https://www.mariowiki.com/index.php?title=Paper_Mario:_Sticker_Star&oldid=4399708#Characters here], [https://www.mariowiki.com/index.php?title=Paper_Mario:_Sticker_Star&oldid=4399708#Locations here] and [https://www.mariowiki.com/index.php?title=Paper_Mario:_Sticker_Star&oldid=4399708#Super_Flags here]). The wikitable style is pretty standard, so it makes sense to use it consistently.


'''2. Prefer to lay out table data in simple rows or columns.''' If the table data fits well in a "one entry per row or column" format, do it, rather than attempting to use more elaborate, arbitrary layouts. Some examples of such arbitrary layouts are [https://www.mariowiki.com/Mario_Kart_7#Vehicle_parts this table], which is laid out like it is a grid of infoboxes, and [https://www.mariowiki.com/index.php?title=Super_Mario_RPG:_Legend_of_the_Seven_Stars&oldid=4379392#Objects this set of tables]. If you judge it wouldn't work to make a table fit that minimal layout, try making it the closest possible to it.
While we don't feel strongly about what happens to the 1 or 2 entry categories, we do think there is ''just enough'' to these 3-entry categories to warrant a closer look our current policies are not providing. Should we lower the cutoff to 3? Or is 4 the magical number for categories?


'''3. Avoid using images of text in lieu of actual text.''' This is often done for the name of the subject, and it is purely for decoration purposes. Cases include Mario's name and stat names [https://www.mariowiki.com/index.php?title=Paper_Mario:_Sticker_Star&oldid=4399708#Mario.27s_stats here] and board names [https://www.mariowiki.com/index.php?title=Mario_Party_2&oldid=4403544#Boards here] (notice that the images in those examples are not there for mere visual reference, as they replace links; the editor likely wanted to add some flavor to the table). It makes the text less straightforward to read, in some cases duplicates it, because normal text is used alongside the image. Another common occurence is using images of stars or other icons to represent scales (such as "X out of 5 stars" scales), when you could use standard star characters (★ and ☆) instead. That does not mean to ''never'' use images instead of text, only consider whether it is worth it or not. For example, [https://www.mariowiki.com/index.php?title=Mario_Kart_8&oldid=4403601#Drivers.27_and_vehicle_parts.27_statistics_2 this] is a ''good'' use of images replacing text because writing the names for each driver and part as text would make it harder for the reader to quickly find the desired info.
'''Proposer''': {{User|Camwoodstock}}<br>
'''Deadline''': February 5, 2025, 23:59 GMT


'''4. Avoid using more images than necessary to illustrate the subject.''' This is also often used for decoration and visual effect. As an example, playable character tables in sports games articles (such as [https://www.mariowiki.com/index.php?title=Mario_Superstar_Baseball&oldid=4392117#Characters this] and [https://www.mariowiki.com/index.php?title=Super_Mario_Kart&oldid=4392250#Drivers this]), where the playable characters' table entries often include both an illustration of the character ''and'' that character's in-game icon (which is just the character's head graphic), which is redundant (if I already have an illustration as visual reference for the character, an icon showing the same thing is unnecessary, and vice versa). This is a specific example but that happens with other kinds of tables, like [https://www.mariowiki.com/index.php?title=Mario_Kart_64&oldid=4402277#Courses the ''Mario Kart 64'' track table] featuring both an image of the track ''and'' the track's thumbnail. Consider whether adding extra images actually make sense or if it's just filler.
====Lower to 3 (triple trouble!)====
#{{User|Camwoodstock}} Per ourselves, of course. We don't see any particular harm in this when, as of submitting this proposal, this would only create, what, 10 categories?
#{{User|Pseudo}} Makes sense to me, especially because, if an individual is uploading images to the wiki for a source that currently has no images, there's a solid chance that that person will upload three images. {{wp|Rule of three (writing)|It's a popular number}}!
#{{User|Nintendo101}} Three is a magic number.


'''5. Avoid decoration in general, such as coloring text and cell backgrounds.''' Take the colored table [https://www.mariowiki.com/index.php?title=Super_Mario_3D_World&oldid=4405481#Characters here] for example. As I said before, it is more about the visuals than the info, and it looks like some sort of promotional material. Instead, save coloring text and table cells for cases where it aids in reading data in some way.
====Keep at 4 (forced to four!)====
#{{User|Waluigi Time}} Per Porple in the comments, image categories don't have this restriction so the proposal seems moot otherwise. I don't see a benefit to reducing this limit across the board, and I'm very hesitant to support without a clearer picture of the implications. (The assertion in the comments that this wouldn't have immediate impact was based on the list on Special:WantedCategories - there weren't any categories there besides image ones because that would require mainspace articles to have redlinked categories that would go against policy if you made them. Obviously, that wouldn't fly.)
#{{User|Sparks}} Per Porplemontage and Waluigi Time.
#{{User|Ahemtoday}} Per Waluigi Time.
#{{User|Super Mario RPG}} Honestly, five would be a better restriction so that it's a well rounded number.
#{{User|Jdtendo}} Per Waluigi Time.
#{{User|TheFlameChomp}} Per Waluigi Time.
#{{User|Mushroom Head}} Per all.


Notice I've been proposing for these guidelines to be encouraged rather than enforced because some of them depend largely on the judgement of the editor.
====Comments (wait, letters in numbers?)====
 
The intent of that restriction is that, for example, if there aren't four articles for [[:Category:Super Paper Mario characters]] then the couple characters would just go in [[:Category:Super Paper Mario]] rather than create the subcategory. Image categories are different since moving up the tree in the same way would be undesirable (there would be a bunch of random images at the bottom of [[:Category:Game images]] rather than those categories being redlinked). We can create image categories with as few as one entry; I updated [[MarioWiki:Categories]]. If you still want to change the number needed for articles, up to you. --{{User:Porplemontage/sig}} 22:38, January 21, 2025 (EST)
'''Proposer''': {{User|Bro Hammer}}<br>
:Oh! We didn't know that, good to know! We'd like to proceed with the proposal, even if we don't think it'd have any immediate impact under these rules--all the 3-item categories have to do with images at the moment. {{User:Camwoodstock/sig}} 22:41, January 21, 2025 (EST)
'''Deadline''': November 6, 2024, 23:59 GMT
 
====Support====
#{{User|Bro Hammer}} Per my proposal.
#{{User|Waluigi Time}} The only thing this proposal is missing is encouraging tables to be horizontally aligned in accordance with web design standards, but otherwise, pretty spot on. I think a little visual flair with coloration is okay, but since this is more of a guideline to be encouraged, I'm fine voting for this as-is.
#{{User|Nintendo101}} I will say, I have used colors for some of the tables I have crafted for the mainline series articles I have worked on, but it is always with illustrative intent. When all the tables in an article look indistinguishable from one another, it can sometimes be easy to lose one's place or not easily understand how some bits of information relate to others. But otherwise, I thinks these are great guidelines and they have my support.
#{{User|Camwoodstock}} Per all, especially Nintendo101; color has a time and a place, but stuff like the SM3DW character chart just kinda feels like a meld. That's not to say we should be replacing everything with the dull greys, of course, but we should probably dial it back at least a ''little'' bit. No real objections to the other parts, we should probably standardize as best we can.
#{{User|Ninelevendo}} I just don’t like what’s been done to the Mario Golf: Toadstool Tour character table so whatever it takes to fix that.
#{{User|Koopa con Carne}} per all
#{{User|Lakituthequick}} Per proposal and per WT – I have indeed commented a few times on tables and how they should be used for tabular data (more notably [[Talk:Mario_Kart_Wii#Decide_how_to_present_courses|for ''Mario Kart Wii'']]), and this proposal will start enforcing tables to do that.
#{{User|Cadrega86}} Wholeheartedly agree with all your points. These tables are over-designed and often include superfluous information (e.g. the track table in the Mario Kart 64 page, why don't we also add staff ghost times and future appearances while we're at it?)
#{{User|Shy Guy on Wheels}} Per all.
#{{User|SolemnStormcloud}} Per all.
#{{User|EvieMaybe}} per Camwoodstock and Waluigi Time
#{{User|TheFlameChomp}} Per all.
#{{User|MCD}} Per all.
#{{User|Sparks}} Per all.
#{{User|Fun With Despair}} Per all. Information should remain accessible and easy to reference, and tables utilizing images instead of easily transcribed or copied text are the opposite of that.
#{{User|PnnyCrygr}} Per all; MarioWiki is not a fansite, it's a wiki! A wiki's tables should therefore be formal and not unconventionally designed.
#{{User|ThePowerPlayer}} Per all. Table design on this wiki has bothered me for a while, and these guidelines are a great solution.
#{{User|Mario}} Current tables are too cluttered with information and are quite hostile to editing. This is a case of less is more imo.
 
====Oppose====
#{{User|Tails777}} I can agree that there should be a bit more consistency and organization on when and where to use certain elements for a table, but I also believe in making tables both informative and entertaining to look at. I see nothing wrong with using board logos to represent names for some of the earlier ''Mario Party'' boards that had them or using colored backgrounds on tables (something I've already supported). And while I can agree that some of the ''Mario Kart'' related tables are a bit all over the place, I believe we could take certain similar cases (tracks, boards, statistics, etc) and maybe make guidelines for each based on the topic. I get that this isn't outright enforcing the outage of these elements, but I don't really think we should actively enforce minimalist designs for tables, rather deciding what to do on a more case-by-case basis.
#[[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) - As the person who made many of the more "showy" ones, I'm kinda societally obligated to oppose this as a matter of course. <small>I can't let my MS in CS with a few classes on advanced web design/web app programming and an undergraduate Minor in Art go to waste</small> and I find it more engaging and explanatory as to the different aspects of whatever entity is being described to have both an in-game graphic and either an artwork or a screenshot. Stat bars and star-bubble fill-in charts with color-coding are also a lot more immediately understandable than numbers alone. To quote Bowser, [https://youtube.com/clip/UgkxjfSn6biDqu-61p6UwftFsKbsS2_1O8vX?si=0CqbG4WO7I7GE8V3 "Haven't you heard? A picture's worth a thousand words."] (People also generally seem to approve of my tables for the ''[[Golf]]'' games...) Anyways, I'm not gonna make this a big to-do, since I still can be beautiful on [[User:Doc von Schmeltwick/Projects/Fun with tables|my own page]], but I still think it looks and functions better than a schedule-looking list with inconsistent image resizings and row heights.
#{{User|OmegaRuby}} Per all. Some consistency between tables in articles would be nice, but I feel the rules this proposal would put in place are a bit too much. I mean, we did recently pass a proposal ''allowing'' [https://www.mariowiki.com/MarioWiki:Proposals/Archive/68#Allow_colorful_tables_again colorful tables] again.
#{{User|DesaMatt}} Per all. While consistency is good, there's a point where it becomes unnecessary and repetitive, and in my view this is that point. Also, I disagree with the idea that MarioWiki isn't a fan site. It will always be a fan site as long as it's not officially affiliated with Nintendo and is operated by fans.
#{{User|Scrooge200}} I actually really like the trend of giving games uniquely stylized tables, it helps give them a bit more personality. All the information is there and you can still read it effectively. I think I worked on some of the modern ''Paper Mario'' tables, and nobody seemed to have a problem with them until now.
#{{User|Hewer}} Per all.
 
====Comments====
{{@|Tails777}} Using images as a substitute for text is very poor for accessibility and searchability with ctrl+f, though. --{{User:Waluigi Time/sig}} 22:08, October 23, 2024 (EDT)
:True and perhaps I can agree to not substituting text with images. But I still stand by what will be my main point: tables can be presentable and professional without being a bore to look at. I still see nothing wrong with colored tables at the very least. {{User:Tails777/sig}}
 
With regards to colours and visuals as is most often used as a counterpoint: I believe those are strictly speaking less important than being informative and clear, but I do love myself tables that look good as well. I can see a future proposal to establish some generic reusable table styles and colours for specific purposes. To take one back a while, Walkazo did [[MarioWiki:Proposals/Archive/30#Navigation_Templates|just that for navigation templates]], which, [[MarioWiki:Proposals/Archive/36#The_Template_Shuffle|with updates]], resulted in [[MarioWiki:Navigation_templates#Coloration|this chart]] to be created, still in use today. ''The 'Shroom'' for instance also features [[The_%27Shroom:Issue_211/Pipe_Plaza#The_.27Shroom_Report|its own table styles]] which are pleasant to look at, and which use colours [[The_%27Shroom:Issue_211/Strategy_Wing#An_Octet_Gazette|that match the page's theme]]. {{User:Lakituthequick/sig}} 08:41, 24 October 2024 (UTC)
:I'm staunchly against using the fugly ass gray and grayer tables across all articles and I'm definitely perring LTQ's suggestion for themes. I like the red header in the Super Mario World article and the green header in the Yoshi's Island article, it's deliberately done to match the nav templates the articles use and I'd be in full support of making tables be consistent with that. {{User:Ray Trace/sig}} 15:51, October 24, 2024 (EDT)
 
There are a ton of tables on here that use STRONG, EXTREME colours in attempt to look flashy but just end up being really hard to read, and I think above all else those need to go. Colour should be used very sparingly. I came across this recently looking at the MK8 Color Scheme tables for [[Standard Kart]] and [[Standard Bike]]. When you see things like '''{{color|lightcoral|Pink}}''', '''{{text outline|{{color|#E0E0E0|White}}}}''', '''{{color|#E6CC00|Medium yellow}}''', '''{{color|gold|Yellow}}''', '''{{color|lawngreen|Chartreuse}}''', '''{{color|#F2DFA6|Light-gold}}''', '''{{text outline|{{color|#F2DFA6|light-gold}}}}''' and especially '''{{color|#FF6633|In}}{{color|lawngreen|k}}{{color|deeppink|l}}{{color|blue|in}}{{color|#990099|g}}{{color|#00E6CC|s}}''', it's murder on the eyes... [[User:Shadow2|Shadow2]] ([[User talk:Shadow2|talk]]) 04:45, October 24, 2024 (EDT)
:Hmm, would it be acceptable if we kinda did {{iw|inkipedia|Template:Ink|what Inkipedia does with ink colors}}, and have a colored square show before the color terms? {{User:Arend/sig}} 12:31, October 24, 2024 (EDT)
:e.g. <span style="width: 1rem; height: 1rem; display: inline-block; vertical-align: middle; border-radius: 0.4rem; background-color:lightcoral">&nbsp;</span> Pink, <span style="width: 1rem; height: 1rem; display: inline-block; vertical-align: middle; border-radius: 0.4rem; border: 1px solid #000000; background-color:#E0E0E0">&nbsp;</span> White, <span style="width: 1rem; height: 1rem; display: inline-block; vertical-align: middle; border-radius: 0.4rem; background-color:#E6CC00">&nbsp;</span> Medium yellow, <span style="width: 1rem; height: 1rem; display: inline-block; vertical-align: middle; border-radius: 0.4rem; background-color:gold">&nbsp;</span> Yellow, <span style="width: 1rem; height: 1rem; display: inline-block; vertical-align: middle; border-radius: 0.4rem; background-color:lawngreen">&nbsp;</span> Chartreuse, <span style="width: 1rem; height: 1rem; display: inline-block; vertical-align: middle; border-radius: 0.4rem; background-color:#F2DFA6">&nbsp;</span> Light-gold. {{User:Arend/sig}} 14:55, October 24, 2024 (EDT)
 
{{@|OmegaRuby}} the guidelines stipulate to "save coloring text and table cells for cases where it aids in reading data in some way." The colors used on those tables provide quick distinction between ''New Super Mario Bros. U'' and ''New Super Luigi U'', so I don't think they would be impacted by this proposal. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 11:32, October 24, 2024 (EDT)
:I hold my opposition on the idea of any tables not being colorful at all, regardless if it assists reading data or distinguishes things - like I said, while I believe there should be consistency in tables in wiki articles I do not believe more bland, grayscale tables should be pushed when adding a dash of color or an image representing a subject doesn't exactly harm readability if implemented correctly. I do know that the proposal pushes for encouragement towards this sort of standard, but I feel as if even the simple suggestion will sway many editors into setting this as a standard. <small>I am also personally a fan of the pretty tables Doc has made, but looking at them from a readability standpoint I do know for sure they're a little ''too'' flashy and would hurt specifically the mobile wiki experience.</small>--{{User:OmegaRuby/sig}} 08:28, October 25, 2024 (EDT)
 
{{@|Doc von Schmeltwick}} I question why exactly you keep bringing up the fact that you have a degree in web design and art in each of these table proposals as though it serves an argumentative point. I do not feel as though it tends to add much to the conversation, nor do I feel that anyone cares. Obviously it is good to have a level of professional training in a subject, however it comes across less as a point in your favor, and more as something you choose to flex whenever anyone disagrees with you on the matter of these tables, which hurts your arguments if anything. Personally as someone who uses a wiki, I would prefer information be conveyed in a simple manner across all the devices I use, and I would prefer that information be accessible and easy to reference in text form - which images hinder. I don't really care if someone with a degree says otherwise, because I know what I prefer - and many members seem to prefer the same thing with regards to simplified tables. Just bringing up your degree as an argument and excuse to ignore feedback does not make people impressed, just annoyed and like they're being talked down to when art is a completely subjective field to begin with. --[[User:Fun With Despair|Fun With Despair]] ([[User talk:Fun With Despair|talk]]) 15:05, October 24, 2024 (EDT)
:I say that because it illustrates why I'm this weird combination of artsy and HTML-based in what I do, not to act high-and-mighty. As well as my massive inferiority complex coupled by my inability to get a job due to the current job market, I need to have ''something'' going for me or I'm worthless - and I need to do ''something'' with that training or it was all a waste of time, and I don't want to have wasted 7 years of my life. I don't think it's important or authoritative by any means - that's the reason it's shrunk. Also I like pictures. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 15:08, October 24, 2024 (EDT)
::Doc, I say this with earnest respect for the struggle to find a job and an understanding that there are difficult times in our lives during which we may lean more heavily on external sources of validation, such as our accomplishments and creations, as founts of our self-worth. I also say this recognizing that, to some degree, there may be a bit of tongue-in-cheek exaggeration in your previous response. While I think it is commendable you have the self-awareness to recognize that some of your pointing to your degree again and again in these discussions arises from your struggles to land a job in an oversaturated market and the effect that has on your own perception of the effort you put into acquiring your degree, it would be prudent to further reflect on ''why'' it serves neither yourself nor the wiki to let those struggles color your decisions and discussions regarding wiki policy, and thus why it might rub others the wrong way to have the point repeated.
 
::There is nothing wrong with taking pride in the work you have done for the wiki. As I understand, you have done a great deal. It doesn't serve you, however, to rely upon that work - especially any single element of it - to seek validation of your major decisions in life through that work. The nature of a wiki is collaboration and change. If not in the near future, if not through the decisions in this proposal, at some point the tables you have contributed to will change, whether it be because the collective aesthetic sensibilities of the userbase have changed, or because of a technical update necessitating it, or because someone sees an opportunity to add further information, or for any number of reasons. Staking the value of your degree to tables bound to change is building an edifice of sand by the ocean and expecting it to stand for years.  Don't tie the value of your degree to transient projects; find the intrinsic value of your degree, such as the knowledge you gained in pursuing it, and use that to bolster your perception of it and yourself.
 
::Further, while perhaps useful as additional context to other wiki editors explaining why your degree is so often referenced, this response also indicates this is not something which is actionable to other wiki editors. A self-described "inferiority complex" is a personal matter which only you can address, and the general wiki editor is not equipped to help you in this respect. If this is the driving factor behind your position, you may need to reevaluate whether it is truly germane to the best interests of the wiki.
 
::So as not to stray too far off-topic, ultimately, I want to acknowledge that this is not necessarily your only reason for opposing this proposal and plainer tables, and it does not in any way invalidate or impact your other points. It is only a word of advice. You have shown the self-awareness to acknowledge what drives you to mention your degree; extend that thinking and see why, then, that is not relevant and should not be relevant to decisions and discussions on wiki policy. [[User:Hooded Pitohui|Hooded Pitohui]] ([[User talk:Hooded Pitohui|talk]]) 16:33, October 24, 2024 (EDT)
:::Thanks. Again, I used small text to display it as not-too-relevant in the grand scheme of things but part of my basis. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 16:36, October 24, 2024 (EDT)
 
As I said on the MarioWiki Discord, "i do believe practicality of a table should prevail over the aesthetics of a table. that way, the table can be easier to comprehend. the tables as of right now look more like they belong to a fansite [...] stop all these gaudy, garish tables". {{User:PnnyCrygr/sig}} 21:50, October 24, 2024 (EDT)
:To be fair, this is a fansite. {{User:Hewer/sig}} 04:20, October 25, 2024 (EDT)
 
{| class="mw-collapsible mw-collapsed" style="width: 40%; float: right; text-align: center;"
|- style="background: whitesmoke;"
!Example
|-
|
{| class="wikitable"
!colspan=2 |Entry
!Name
!Value A
!Value B
|-
|style="width: 3px; background: #380000" |
!First entry
|First name
|1A
|1B
|-
|style="width: 3px; background: #9A0607" |
!Second entry
|Second name
|2A
|2B
|-
|style="background: #FEC724" |
!Third entry
|Third name
|3A
|3B
|-
|style="background: #ACBBC3" |
!Fourth entry
|Fourth name
|4A
|4B
|}
 
{| class="wikitable"
|-style="background: #380000; color: #fff;"
!Entry
!Description
!Another value
|-
!A
|This is the description A for the first entry.
|1A
|-
!B
|This is the description B for the first entry.
|1B
|-
!C
|This is the description C for the first entry.
|1C
|}
 
{| class="wikitable"
|-style="background: #9A0607; color: #fff;"
!Entry
!Description
!Another value
|-
!A
|This is the description A for the second entry.
|2A
|-
!B
|This is the description B for the second entry.
|2B
|-
!C
|This is the description C for the second entry.
|2C
|}
 
{| class="wikitable"
|-style="background: #FEC724; color: #000;"
!Entry
!Description
!Another value
|-
!A
|This is the description A for the third entry.
|3A
|-
!B
|This is the description B for the third entry.
|3B
|-
!C
|This is the description C for the third entry.
|3C
|}
 
{| class="wikitable"
|-style="background: #ACBBC3; color: #000;"
!Entry
!Description
!Another value
|-
!A
|This is the description A for the fourth entry.
|4A
|-
!B
|This is the description B for the fourth entry.
|4B
|-
!C
|This is the description C for the fourth entry.
|4C
|}
|}
In my opinion, Wikipedia has an elegant way of dealing with color in tables: they rarely use it for the visuals, but when they do, it just makes sense to have it. Take for example how they present seasons of TV shows in the example. Also, maybe people think that articles would become "too boring" or "too gray" if tables were ''completely'' standardized with no decoration at all and whatnot, but that happens because articles overuse tables in my opinion. But that's a different topic. {{User:Bro Hammer/sig}} 11:53, October 26, 2024 (EDT)
:These examples are indeed in line with the idea of generic themes I mentioned above. Of course, these examples are still on the tamer side and other styles can be added on top, but it does already look less dull while still maintaining clarity. {{User:Lakituthequick/sig}} 15:08, 28 October 2024 (UTC)
 
{{@|Waluigi Time}} Thank you for the suggestion. I wanted to read about horizontally aligned tables being a standard, but I couldn't find anything about it. Do you have a link you can share? {{User:Bro Hammer/sig}} 11:53, October 26, 2024 (EDT)
:Unfortunately I don't have a link on hand and wasn't able to find it myself - my knowledge on this admittedly comes from talking to people who are much more well-versed than me - but I've asked Lakituthequick to look into it. For what it's worth, the documentation I've looked at doesn't explicitly say anything about it, but all examples provided are horizontal. In the meantime, a few points in favor of horizontal alignment (in other words, one subject per row instead of per column):
:*It preserves the natural left-to-right reading flow used by the rest of our content. I think screen readers also do this, so a vertical alignment ends up being especially confusing for anyone using one, which isn't good for accessibility.
:*Only horizontal tables can be sorted, since that function works off of the headings.
:*The code is much easier to understand and edit since all the information on one subject is kept together neatly. (e.g. Horizontally, you get Mario grouped with all of his stats in a game. Vertically, you're just left with a bunch of character names, and their stats are scattered in multiple chunks further down the page.) Incidentally, this criticism is what created that "grid of infoboxes" layout you mentioned to preserve the column alignment.
:So if I was mistaken on this being an explicit standard, it still seems like best practice, at least. --{{User:Waluigi Time/sig}} 14:22, October 26, 2024 (EDT)
::Can confirm this; additionally, web standards are just written in such a way that tables have headers and footers at the top and bottom, respectively (it is worth noting that wikicode doesn't support separating [https://developer.mozilla.org/en-US/docs/Web/HTML/Element/thead header], [https://developer.mozilla.org/en-US/docs/Web/HTML/Element/tbody body], and [https://developer.mozilla.org/en-US/docs/Web/HTML/Element/tfoot footer] elements in a table – heck, the parser actively rejects those elements when used directly). In print, this is not so much of an issue. ''Technically'' it is probably possible to rotate a table by 90° while maintaining the said pros, but this likely involves throwing a bunch of CSS (hacks) at it that require work to look good in each instance and may not be worth it in most cases. {{User:Lakituthequick/sig}} 15:08, 28 October 2024 (UTC)
{{br}}


==New features==
==New features==
Line 209: Line 34:


==Changes==
==Changes==
===Remove all subpage and redirect links from all navigational templates===
===Allow users to remove friendship requests from their talk page===
Navigational templates are one of this wiki's best features. They're a really convenient way to get around the wiki. However, one common pitfall of the templates is bloat, in particular in the form of links to subjects that do not have dedicated articles. I have previously made [[MarioWiki:Proposals/Archive/66#Trim Super Smash_Bros. navigational templates|a proposal about this subject]] specifically in the context of the ''Super Smash Bros.'' series, but the problem extends to navigational templates across the entire wiki.
This proposal is not about banning friendship requests. Rather, it's about allowing users to remove friendship requests on their talk page. The reason for this is that some people are here to collaborate on a giant community project on the ''Super Mario'' franchise. Sure, it's possible to ignore it, but some may want to remove it outright, like what [https://www.mariowiki.com/index.php?title=User_talk:Arceus88&diff=4568152&oldid=1983365 happened here]. I've seen a few talk pages that notify that they will ignore friendship requests, [[User talk:Ray Trace|like here]], and this proposal will allow users to remove any friend requests as they see fit.


In principle, navigational templates should be '''directories of articles on the wiki'''. What advantage does it give the reader for [[Template:WWMI]] to have a whole section dedicated to eighteen separate links to subsections of [[Form Stones]] on ''top'' of a link to the main article itself? Why does [[Template:Humans]] link to all seven individual members of [[List of show hosts in All Night Nippon: Super Mario Bros.|List of show hosts in ''All Night Nippon: Super Mario Bros.'']] individually? Does the already crowded [[Template:Super Mario games]] really need to use precious space on a link to [[List of unreleased media#Tesla Mario Kart game|a two-sentence section]] about a theoretical game that Elon Musk claims to have failed to have pitched to Nintendo?
If this proposal passes, '''only''' the user will be allowed to remove friendship requests from their talk pages, including the user in the first link should they want to remove it again.


I propose that, across the board, '''all subpage and redirect links on all navigational templates should be either removed or replaced'''. (''Red links'' are relatively fine, as long as the things they don't link to theoretically ''should'' be articles that just haven't been made yet. Edge cases like "[[Unnamed Worlds A-C Human]]" should be decided case-by-case in [[Template talk:Humans#Unnamed Worlds A-C Human|the relevant talk pages]].)
This proposal falls directly in line with [[MarioWiki:Courtesy]], which states: "Talking and making friends is fine, but sometimes a user simply wants to edit, and they should be left to it."


'''Proposer''': {{User|JanMisali}}<br>
'''Proposer''': {{User|Super Mario RPG}}<br>
'''Deadline''': October 31, 2024, 23:59 GMT
'''Deadline''': <s>January 29, 2025, 23:59 GMT</s> Extended to February 5, 2025, 23:59 GMT


====Remove the extra links from navigational templates====
====Support====
#{{User|JanMisali}} As proposer.
#{{User|Super Mario RPG}} Per.
#{{User|Hewer}} To be honest, the main reason I'm supporting this is because I hate how cluttered [[Template:Super Mario games]] is with useless links, and this would help solve that problem. We don't need to list every single game to ever have been pitched there.
#{{User|Shadow2}} Excuse me?? We actually prohibit this here? Wtf?? That is one of the most ridiculous things I've ever heard. Literally ''any other platform that has ever existed'' gives you the ability to deny or remove friend requests... They don't just sit there forever. What if your talk page just gets swamped with friend requests from random people you don't know, taking up space and getting in the way? I also don't think it's fair, or very kind, to say "just ignore them". It'll just sit there as a reminder of a less-than-ideal relationship between two users that doesn't need to be put up on display. Honestly I didn't even know we did "Friends" on this site...maybe the better solution is to just get rid of that entirely. This is a wiki, not social media.
#{{User|Camwoodstock}} This makes sense to us. It's much easier to just list a page link once and only once.
#{{User|RetroNintendo2008}} Per Shadow2's comment.
#{{User|OmegaRuby}} Per all.
#{{User|Waluigi Time}} IMO, the spirit of the no removing comments rule is to avoid disrupting wiki business by removing comments that are relevant to editing, records of discipline, and the like. I don't think that removing friend requests and potentially other forms of off-topic chatter is harmful if the owner of the talk page doesn't want them.
#{{User|EvieMaybe}} per all
#{{User|EvieMaybe}} per WT
#{{User|ThePowerPlayer}} When I think about it, it's an extreme stretch to e.g. list [[Mario Chase]] on the [[Template:Super Mario games|list of ''Super Mario'' games]] just because it was a reworked demo, or to give real estate to ''[[List of unreleased media#Mario's Castle|Mario's Castle]]'', a concept so nebulous that it is covered by a list article in a grand total of two sentences. I feel more ambivalent about entries that are clearly their own games, such as ''[[Mario Party 4#Arcade|Dokidoki Mario Chance!]]'' or ''[[Reflex Rally#Browser game|Reflex Rally]]'', but those could be split on a case-by-case basis if necessary.
#{{User|Camwoodstock}} If someone doesn't want something ultimately unrelated to the wiki on their talk page, they shouldn't be forced to keep it. Simple-as. It would be one thing if it was "remove ''any'' conversation", as that could be particularly disruptive, but for friend requests, it's so banal that we can't see the harm in allowing people to prune those if they deem it fit.
#{{User|SeanWheeler}} If we're not allowed to link redirects, how could our templates have redirect links?
#{{User|Nintendo101}} <s>Per proposal and Waluigi Time.</s> No, I do think this is principally fine. Though I do not support the broader scope envisioned by Shadow2.
#{{User|Jdtendo}} No need to clutter navboxes with useless links.
#{{User|LinkTheLefty}} Agreed with N101.
#{{User|Paper Plumm}} While the concerns presented by the opposing side are valid, I think we should allow people to have the ability to control this sort of thing, this will have no consequence to you if you enjoy having friend requests however for those who are against this they are able to gain a net positive in relieving themselves of needless clutter. As per the broader ideas presented, that definitely needs its own vote, however again I am of the mind that the option should be made available but not forced upon all.
#{{User|Killer Moth}} Per proposal, Waluigi Time, Camwoodstock, and Paper Plumm.
#{{User|Daisy4Days}} Per proposal. I just don’t see why one should have to keep that; it’s completely unrelated to editing the wiki.
#{{User|Ahemtoday}} Per Shadow2.


====Do nothing====
====Oppose====
#{{User|Ray Trace}} This hasn't been a problem as if lately and doesn't really fix anything. Just ignore the comments unless it's warning/block-worthy behavior like harassment or vandalism.
#{{User|Hewer}} I don't really see the point of this. A user can ignore friend requests, or any messages for that matter, without having to delete them.
#{{User|Sparks}} Friend '''requests''' are not any kind of vandalism or flaming. However, if they falsely claim to be their friend and steal their userbox then it would be an issue.
#{{User|Jdtendo}} I don't see why we would allow the removal of friend requests specifically and no other kind of non-insulting comments.
#{{User|Technetium}} No one even does friend requests nowadays.
#{{User|Mario}} Iffy on this. The case was a fringe one due to a user removing a very old friend request comment done by a user that I recall had sent out friend requests very liberally. I don't think it should be exactly precedent setting, especially due to potential for misuse (removing friend requests may be seen as an act of hostility, maybe impolite even if unintentional; ignoring it also has the problem but not as severe). Additionally, friend requests are not as common as they used to be, and due to this I just rather users exercise discretion rather than establish policy I don't think is wholly necessary. My preference is leaving up to individual to set boundaries for friend requests; a lot of users already request no friend requests, no swear words, or no inane comments on their talk pages and this is where they reserve that right to remove it or censor it. Maybe instead we can have removing friend requests be within rules, but it ''must'' be declared first in the talk page, either through a comment ("sorry, I don't accept friend requests") or as a talk page rule.
#{{User|Tails777}} I can see the logic behind allowing people to remove such requests from their talk pages, but at the same time, yeah, it's not really as common anymore. I just feel like politely declining is as friendly as it can get and flat out deleting them could just lead to other negative interactions.
#{{User|Mushroom Head}} It’s honestly rude to just delete them. If they were not nice, I guess it would make sense, but I can’t get over it when others delete your message.
#{{User|Shy Guy on Wheels}} A friend request ain't gonna hurt you. If you have a problem with it, you can always just reject it.
#{{User|Arend}} On top of what everyone else has already said, I think leaving them there is more useful for archival purposes.
#{{User|MCD}} This seems like something that would spark more pointless arguments and bad blood than it would prevent, honestly. Nothing wrong with saying 'no' if you ''really'' don't want to be friends with them, or just ignoring it. Also, the example that sparked this isn't anything to do with courtesy - the message in question was from 9 years ago and was not removed because the user was uncomfortable with it, but they seem to be basically starting their whole account from scratch and that was the one message on the page. In that context, I think removing the message was fine, but anything like that should decided on a case-by-case basis if there's nothing wiki-related or worth archiving otherwise.
#{{User|Sdman213}} Per all.
#{{User|Green Star}} Friend requests may not be especially helpful when it comes to building an encyclopedia, but allowing users to remove rather than simply ignore them isn't exactly helpful for building a friendly and welcoming community.
<s>{{User|Nintendo101}} It is not our place to remove talkpage comments — regardless of comment — unless it is harassment or vandalization, to which stuff like this is neither. I really think this energy and desire to helping out is best spent trying to elaborate on our thinner articles, of which there are many.</s>


====Comments====
====Comments====
Wait, that ANN thing is a page? I was unaware. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 18:51, October 17, 2024 (EDT)
{{@|Nintendo101}} Ignoring friendship requests and removing them are basically the same thing. It's not required to foster a collaborative community environment, whether a user wants to accept a friendship request or not. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 09:52, January 15, 2025 (EST)
:A page that's linked to on nearly 900 (!!) other pages! But since those links are hidden in a big bloated alphabetical list of characters (only most of which have actual articles), it's not nearly as visible of an article as it otherwise would be. {{User:JanMisali/sig}} 19:09, October 17, 2024 (EDT)
:I think it is fine for users to ignore friend requests and even remove them if they so choose. I do not think it is the place of another user — without being asked — to remove them, especially on older user talk pages. [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 10:03, January 15, 2025 (EST)
::When I made that proposal not too long ago on that game, my idea was a page for each since they're all based on real people and look different despite having the same role (like the people in Mario is Missing and the NES Mario's Time Machine). [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 19:13, October 17, 2024 (EDT)
::{{@|Nintendo101}} The proposal is for only the user whom the talk page belongs to removing friend requests being allowed to remove friend requests, '''not''' others removing it from their talk page for them. I tried to make it clear with bold emphasis. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 10:04, January 15, 2025 (EST)
:::That sounds perfectly reasonable. If/when those dedicated articles ''are'' created, then including links to them in Template:Humans would make sense. As it stands now, of course, linking to one list article several times is just messy and unhelpful. {{User:JanMisali/sig}} 19:20, October 17, 2024 (EDT)
:::Do we really need a proposal for this, though? And besides, I don't think friend requests are much of a thing here anymore. [[User:Technetium|Technetium]] ([[User talk:Technetium|talk]]) 10:24, January 15, 2025 (EST)
::::I would've thought not, though a user got reverted for removing a friend request from own talk page (see proposal text). [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 10:26, January 15, 2025 (EST)
:::::My bad, I thought you had removed it to begin with. Apologies for the misunderstanding. [[User:Technetium|Technetium]] ([[User talk:Technetium|talk]]) 10:50, January 15, 2025 (EST)
Adding on, there's a BIG difference between "Removing a warning or disciplinary action", "Hiding or censoring past discussions"...and "Getting rid of a little friend request". Sure it's important to retain important information and discussions on a talk page, but if it's not relevant to anything or important then the user shouldn't be forced to keep it forever. Perhaps a more meaningful proposal would be, "Allow users to remove unimportant information from their talk page". I've looked at the talk pages for some users on this wiki, and some of them are filled with...a '''lot'''. Like, a ton of roleplay stuff, joking and childish behaviour, gigantic images that take up a ton of space. Is it really vitally necessary to retain this "information"? Can't we be allowed to clean up our talk pages or remove stuff that just doesn't matter? Stuff that doesn't actually relate in any way to editing on the wiki or user behaviour? Compare to Wikipedia, a place that is generally considered to be much more serious, strict and restrictive than here...and you ''are'' allowed to remove stuff from your talk page on Wikipedia. In fact, ''you're even allowed to remove disciplinary warnings''. So why is it so much more locked-down here? [[User:Shadow2|Shadow2]] ([[User talk:Shadow2|talk]]) 08:55, January 16, 2025 (EST)
:I've been trying to convey this very thing. I'm not against people befriending on the wiki, or even WikiLove to help motivate others. But there's a big difference between removing friend requests to removing formal warnings, reminders, and block notices from one's talk page. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 09:24, January 16, 2025 (EST)
::"''I've looked at the talk pages for some users on this wiki, and some of them are filled with...a lot. [...] Is it really vitally necessary to retain this 'information'?''"
::It absolutely is for those users on the talk pages. {{User:Mario/sig}} 20:12, January 16, 2025 (EST)
:::...Right...And it's their choice to keep it. But as I understand it, the rules of this website prevents those users from ''removing'' it if they should so choose. [[User:Shadow2|Shadow2]] ([[User talk:Shadow2|talk]]) 20:44, January 16, 2025 (EST)
::::I just don't see the issue. Those talk pages you cited are typically content exchanged between two users who know each other well enough. It doesn't happen with two strangers. If you don't want the content in the rare case some random person decides to post an image you don't like, then reply to it to indicate such, and it shouldn't be posted again. If they do it again, it's a courtesy violation and it's actionable, just ask sysops to remove it. It's not really violating the spirit of the "no removing comments" rule. Our current rules are already equipped to deal with this, I don't think it's a great idea to remove this content in most cases without at least prior notice, which I think this proposal will allow. {{User:Mario/sig}} 20:59, January 16, 2025 (EST)
:::::That's the problem right there, you've perfectly outlined it. "some random person decides to post an image you don't like, then reply to it to indicate such, and it shouldn't be posted again". But the image is ''still there'', even though I don't want it to be there. Why does the image I don't like have to remain permanently affixed to my talk page, taking up space and not doing anything to further the building of this wiki? Rather, I should be allowed to say "I don't like this image, I am going to remove it now." [[User:Shadow2|Shadow2]] ([[User talk:Shadow2|talk]]) 22:49, January 16, 2025 (EST)


Speaking of that "Unnamed Worlds A-C Human", has anyone attempted a thorough search through the history of ''All Night Nippon'' to identify the guy? As I said on the relevant talk, I ''assume'' it's also a radio host, since all the other Toad replacements are hosts as well, but I can't say with certainty (might as well be a higher-up at Fuji TV) {{User:Arend/sig}} 18:13, October 25, 2024 (EDT)
I want to make something clear: under [[MarioWiki:Userspace#What can I have on my user talk page?|the current policy for user talk pages]], "you cannot remove conversations or comments, unless they are acts of vandalism or trolling". Comments that you can remove are the exception, not the norm. If this proposal passes, should we change the end of the sentence to "unless they are acts of vandalism, trolling, or friend requests"? {{User:Jdtendo/sig}} 13:13, January 16, 2025 (EST)
:No. This is about letting users to decide whether to remove friend requests from their talk page if they do not want that solicitation. "you cannot remove conversations or comments, unless they are acts of vandalism or trolling" would be more along the lines of, "You are not allowed to remove any comments irrelevant to wiki-related matters, such as warnings or reminders. The most leeway for removing comments from talk pages comes from vandalism, trolling, or harassment. Users are allowed to remove friend requests from their own talk page as well." [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 15:43, January 16, 2025 (EST)
::{{@|Super Mario RPG}} receiving a friend request does not mean you have to engage with it or accept, does it? So I am not really sure it constitutes as solicitation. Is the idea of leaving a friend request there at all the source of discomfort, even if they can ignore it? Or is it the principal that a user should have some say as to what is on their own talk page as their user page? I worry allowing users to remove their comments from their talk pages (especially from the perspective of what Shadow2 is suggesting) would open a can of worms, enabling more disputes between users. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 21:13, January 16, 2025 (EST)
:::It's the principal of a user deciding whether they want it on their talk page or not. It would be silly if disputes occur over someone removing friendship requests. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 21:20, January 16, 2025 (EST)


===Prioritize MESEN/NEStopia palette for NES sprites and screenshots===
:No, we should change it to "acts of vandalism, trolling, or unimportant matters unrelated to editing on the wiki." [[User:Shadow2|Shadow2]] ([[User talk:Shadow2|talk]]) 18:28, January 16, 2025 (EST)
I want to preface this by saying this proposed change will NOT be a one-person job to go back and change all instances of uploaded images. This will be more a general guideline going forward, and a thing anyone who wants to help can do without feeling like it might be unnecessary or unwanted. If this succeeds, the only immediate change needed to be considered "put into effect" is an edit to the image policy, though there will probably be a lot of quality tags for blatantly off colors.
::I believe users should have ''some'' fun here and there. The wiki isn't just a super serious website! Plus, it gives us all good laughs and memories to look back on. {{User:Sparks/sig}} 20:32, January 16, 2025 (EST)
::{{@|Shadow2}} What are some specific examples? [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 20:35, January 16, 2025 (EST)
:::Examples of what? [[User:Shadow2|Shadow2]] ([[User talk:Shadow2|talk]]) 20:44, January 16, 2025 (EST)
::::Of what other "unimportant matters" you'd like for users to be allowed to remove from their own talk page. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 20:47, January 16, 2025 (EST)
:::::Unfortunately it might be in bad faith to say "Look at this other user's page, this is considered unimportant and if it were on MY page, I would want it deleted." But like, when I first started on Wikipedia a friend of mine left a message on my talk page that said "Sup noob". I eventually fell out of favour with this friend and didn't really want to have anything to do with him anymore, so I removed it. It wasn't an important message, it didn't relate to any activity on the wiki, it was just a silly, pointless message. I liked it at first so I kept it, then I decided I didn't want it there anymore so I removed it. There's a lot of other very silly, jokey text I've seen on talk pages that I'm sure most users are happy to keep, but if they ''don't'' want to keep it then they should have the option of removing it. [[User:Shadow2|Shadow2]] ([[User talk:Shadow2|talk]]) 23:00, January 16, 2025 (EST)


For context of this, the NES and the Japanese FamiCom/Disk System do not have a "native" hard-coded palette. As such, different machines display different colors. However, a ''majority'' of contemporary televisions in the NTSC region (which includes both Japan and America, so where the FamiCom and the NES were initially respectively developed - sorry PAL pals) would display them with a particular muted palette. Many early computer-based emulators instead displayed an extremely bright palette with colors that tended to clash with each other, which is still present on many old images on the site. Even a few today are like that, such as FCEUX, which while great for ripping tiles, has a very odd color display.
{{@|Technetium}} That's true, no one does, but me and some others still would prefer a precedent to be set. This proposal began because someone blanked a friend request from own talk page recently, so this may occur every once in a while. The reason that one was allowed to be removed (by {{@|Mario}}) is because it was a single comment from long ago that had no constructive merit when applied to this year and wasn't that important to keep when the user decided to remove it. This proposal would allow it in all cases. Removing such messages from one's own talk page is the equivalent of declining friend requests on social platforms. It stops the message from lingering and saves having to do a talk page disclaimer that friend requests will be ignored, since some people may choose to accept certain friend requests but not others. This opens room for choices. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 16:21, January 16, 2025 (EST)


MESEN and NEStopia are NES emulators that display that more "accurate" (for lack of better term) color. It is widely recommended by sources such as The Spriters Resource and The Cutting Room Floor as a good way to ensure color consistency. Even Nintendo themselves seems to prefer its colors, as official emulators like the Nintendo Switch Online use that type of palette. I think we should start prioritizing it going forward as a general rule so there's more consistency to the uploads color and quality.
{{@|Mario}} So if this proposal fails, would there be some clarification in rules behind the justification of such content being removed?  [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 20:35, January 16, 2025 (EST)
:[[File:Toadlose.gif]] Maybe? I don't know. This proposal was kind of unexpected for me to be honest. {{User:Mario/sig}} 20:38, January 16, 2025 (EST)
::I do believe that the intentions of this proposal are good, but the scope is too narrow. It should be about granting users the freedom to remove unimportant fluff (Friend requests included) from their talk page if they so choose. Discussions about editing and building the wiki, as well as disciplinary discussions and warnings, do ''not'' fall under "unimportant fluff". [[User:Shadow2|Shadow2]] ([[User talk:Shadow2|talk]]) 20:47, January 16, 2025 (EST)
:::{{@|Shadow2}} have you considered that the users who receive images and jokes on their talk pages like having them there? The users who send jokes and images to certain receivers view them as good friends - these are friendly acts of comradery, and they are harmless within the communal craft of wiki editing. Are you familiar with anyone who would actually like to have the ability to remove "fluffy" comments from their talk pages? - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 21:18, January 16, 2025 (EST)
:::Some narrow-scope proposals have set precedents. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 21:20, January 16, 2025 (EST)
::::(edit conflict) I would also add that they help build a wiki by fostering trust and friendship (which is magic) and helping morale around here, but I do think Shadow2 is arguing that if they receive such content, they should see fit to remove it. However, the hypothetical being construed here involves a stranger sending the content (which probably has happened like years ago) and I dispute that the scenario isn't supported in practice, so I don't think it's a strong basis for the argument. In the rare cases that do happen (such as, well, exchanges years ago), they're resolved by a simple reply and the content doesn't really get removed or altered unless it's particularly disruptive, which has happened. If it's applicable, I do think a rule change to at least allow users to set those particular boundaries in their talk pages can help but I don't see how that's strictly disallowed in the first place like the proposal is implying. {{User:Mario/sig}} 21:38, January 16, 2025 (EST)
::::"have you considered that the users who receive images and jokes on their talk pages like having them there?" Yes? Obviously? What does that have to do with what I'm saying. Why does everybody keep turning this whole proposal into "GET RID OF EVERYTHING!!" when it's not at all like that. If the users want the images and jokes on their talk page, they can keep them. If they ''don't'' want them, then there's nothing they can do because the rules prohibit removal needlessly. [[User:Shadow2|Shadow2]] ([[User talk:Shadow2|talk]]) 22:49, January 16, 2025 (EST)
:::::I think you misunderstand my point - why should we support a rule that does not actually solve any problems had by anyone in the community? - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 23:03, January 16, 2025 (EST)
::::::That's an unfair assumption. It would be a problem for me if someone left something on my page, and there's probably plenty of others who would like to remove something. Conversely, what is there to gain from forcing users to keep non-important information on their talk page? [[User:Shadow2|Shadow2]] ([[User talk:Shadow2|talk]]) 02:11, January 17, 2025 (EST)
:::::::I would appreciate it if you elaborated on what about my inquiry was an unfair assumption. I am generally not someone who supports the implementation of rules without cause. If there were examples of users receiving unsolicited "fluff" on the site that do not like it, or if you yourself were the receiver of such material, that would be one thing. But I do not believe either thing has happened. So what would be the point in supporting a rule like that? What are the potential consequences of rolling something like that? Facilitating edit wars on user talkpages? Making participants in a communal craft feel unwelcomed? Making users hesitant to express acts of friendship with another? The history of an article-impacting idea being lost because it emerged between two users on one of their talkpages? In my experience the users who have received light messages and images from others have established a bond elsewhere, such as on Mario Boards or the Super Mario Wiki Discord. I am not familiar of this being done between acquaintances or strangers, or people who dislike it regardless. If you had proof of that or any comparable harm, I would be more receptive to your perspective. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 12:13, January 17, 2025 (EST)
::::::::Feels like I'm just shouting at a wall here, and all of my concerns are being rebuffed as "not a big deal", so I guess I'll just give up. But going forward, having learned that once someone puts something on my talk page it's stuck there for eternity, no matter what it is, makes me incredibly uncomfortable. [[User:Shadow2|Shadow2]] ([[User talk:Shadow2|talk]]) 18:48, January 17, 2025 (EST)
This proposal says: ‘You may get your edit reverted for being nice, but because swearing is not being nice, you can swear the şħįț out’ {{User:Mushroom Head/sig}} 07:55, January 17, 2025 (EST)


For an example of what I am talking about, see the upload history for {{File link|SMB Goomba Sprite.gif}}. A lot of the fixes have already been historically done; I myself worked a lot on the ''Famicom Grand Prix'' and ''Golf'' series images. Most of what's left are random images in larger platforming games as well as assorted more obscure games (looking at you, ''Wario's Woods''), as well as newer uploads from people using older sources without realizing or caring about this issue (which is the main thing this proposal hopes to address).
===Merge the Tortes===
Three birds with one stone with this one! This proposal concerns the following articles:
* [[Apprentice (Torte)]]
* [[Chef Torte]]
* [[Torte]]


(As a side note, I spent yesterday evening collecting the NEStopia colors for ''Super Mario Bros. 2'' by playing through the whole game and applying them to the pre-existing level maps (which were ripped originally in one of those odd bright emulators), so assistance with applying them to the innumerable screenshots, sprites, and animations for the game would be greatly appreciated.)
The argument is fairly simple; the Chef and Apprentice Tortes are just a duo never seen separate from one another, like the [[Jellyfish Sisters]], or [[Cork and Cask]]--and given they are the ''only'' Tortes we see in the game, it seems only fair to merge that article as well. This is only particularly unique in the amount of articles there are; 3 of them, for this one concept? The Torte article focuses mostly on their in-battle role, while the Chef Torte and Apprentice articles try to explain their duo role in two distinct articles.


'''Proposer''': {{User|Doc von Schmeltwick}}<br>
In addition, if we merge Apprentice (Torte), either to Torte or to Chef Torte, we should probably move [[Apprentice (Snifit)]] over to [[Apprentice]], and give it the <nowiki>{{about}}</nowiki> template.
'''Deadline''': November 3, 2024, 23:59 GMT


====Supportopia====
'''Proposer''': {{User|Camwoodstock}}<br>
#{{user|Doc von Schmeltwick}} - De vunderbar vald of color. Co''RR''ECT color.
'''Deadline''': February 3, 2025, 23:59 GMT
#{{User|Nintendo101}} I think utilizing a unified palette is a smart idea. It would look nice, unified, and would mitigate potential confusion as to how colors differ between subjects.
#{{User|Camwoodstock}} The weirdly vibrant colors are a rare FCEUX L, as far as we're concerned, and it'd be nice to have some guidelines in place to encourage consistency.
#{{User|SolemnStormcloud}} Though my ''Mega Man''-brained self prefers the FCEUX palette in the context of that series due to MisterMike's sprite rips as well as it being the basis of  ''Mega Man 9'' and ''10''{{'}}s palette, this isn't a ''Mega Man'' wiki, so per all.
#{{User|ThePowerPlayer}} It's better to use the most accurate colors to the original output, to match the accuracy of the resolution of game screenshots.
#{{User|LinkTheLefty}} TCRF standards FTW.
#{{User|Killer Moth}} Per all.
#{{User|EvieMaybe}} it's worth noting that CRTs and LCDs display color differently, so a direct rip of what the nes displays to an LCD might not be properly accurate. however, if both TSR and TCRF recommend it, then i have to defer to their opinion
#{{user|wildgoosespeeder}} I have had Mesen [[User:Wildgoosespeeder/sandbox#NES/Famicom/Famicom Disk System/SNES/Satellaview|as a mention]] for years. It has the highest accuracy I have ever seen in an NES emulator. However I have always treated it as a fallback option to FCEUX. Reason being TASVideos.org availability. There is a section on TCRF about [[tcrf:Help:Contents/Taking Screenshots#NES|applying the correct color pallete when using FCEUX]].
#{{User|Mario}} I suppose there's no way to have all monitors display the exact colors uniformly, might worth documenting the colors.


====Opposeux====
====Merge all 3 to Torte (It's burnt...)====
 
#{{User|Camwoodstock}} Primary option. It's probably the simplest option overall, if you ask us, and it fits with how we handle the various duos of ''Superstar Saga''.
====Commesents====
#{{User|LinkTheLefty}} Unusually, these guys don't even have unique battle labels.
[https://tcrf.net/Help:Contents/Taking_Screenshots#NES Here's] the source on The Cutting Room Floor's preference for the MESEN/NEStopia palette, in case anyone needs it. Sorry if it's unnecessary, but I think the claim of the other websites' stances could've had links provided. [[User:SolemnStormcloud|SolemnStormcloud]] ([[User talk:SolemnStormcloud|talk]]) 15:47, October 20, 2024 (EDT)
#{{User|Sparks}} Merge!
:Thank you, now I can actually use FCEUX without needing to back-and-forth between emulators. Maybe I can get back into ''U.S. Course''{{'}}s prize card again... [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 16:01, October 20, 2024 (EDT)
#{{User|Blinker}} Per proposal. (By the way, I'm also rethinking my position on the Iron Cleft situation...)
 
#{{User|Ahemtoday}} Per proposal.
{{@|SolemnStormcloud}} - Not to gossip but FR MisterMike'd be the best NES sprite ripper ever if not for exclusively using FCEUX palette. His ''Zelda'' 1 rips were... eyebrow-raising, to say the least, which is part of what inspired me to prioritize the NEStopia palette. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 15:58, October 20, 2024 (EDT)
<s>{{User|Nintendo101}} Per proposal.</s>
 
====Merge Chef Torte & Apprentice, keep them split from Torte (It's just a little crispy.)====
{{@|EvieMaybe}} - Note the "closest to contemporary NTSC display" thing, so that'd be close-to-CRT. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 00:16, October 22, 2024 (EDT)
#{{User|Camwoodstock}} Secondary option; if we really must keep Torte split from the duo we see in-game, that's fine, but we can't see any particular reason to keep the duo split up.
:makes sense! i figured that by "contemporary" you meant an LCD or an OLED, thanks for clarifying [[User:EvieMaybe|EvieMaybe]] ([[User talk:EvieMaybe|talk]]) 11:12, October 22, 2024 (EDT)
#[[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) - Also if I recall correctly, that inconsistent-in-English accent difference is not present in Japanese, where their speech patterns are mostly the same. I'm not sure about merging them to the species since they at least ''have'' unique names from the species, unlike say, Birdo.
 
#{{User|Waluigi Time}} Per Doc in the comments. This would also be consistent with [[Talk:Iron_Cleft#Merge_with_The_Iron_Adonis_Twins|last year's proposal for Iron Clefts/the Iron Adonis Twins]].
===Stop considering reused voice clips as references (usually)===
#{{User|DryBonesBandit}} Per all. If all three'd be merged, I'd rather the title be "Chef Torte and Apprentice" anyway, because iirc they're the only Tortes in the game.
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.
#{{User|Paper Plumm}} Per all.
 
#{{User|Nintendo101}} I think this makes more sense, from the comments below.
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|Technetium}} Per all.
#{{User|Jdtendo}} Per all.
#{{User|SolemnStormcloud}} Per Waluigi Time.
#{{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.
 
====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====
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)
 
 
===Encourage game-related "icon"-type images to have consistent file dimensions with each other when applicable to their origins===
 
[[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>
 
;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>
 
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.
 
'''{{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.


'''{{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.
====Do nothing (It's gourmet!)====


'''{{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.  
====Comments (It's... Alive???)====
This can easily be ''four'' birds with one stone, since "Apprentice (Snifit)" can become the default article (the identifier's a little dated anyway) and the paltry disambig can be turned into an <nowiki>{{about}}</nowiki>. [[User:LinkTheLefty|LinkTheLefty]] ([[User talk:LinkTheLefty|talk]]) 22:08, January 19, 2025 (EST)
:Good observation, actually! Went and added this. {{User:Camwoodstock/sig}} 22:15, January 19, 2025 (EST)


'''Proposer''': {{User|Doc von Schmeltwick}}<br>
@Doc: On that note, because of [[MarioWiki:once and only once|once and only once]], that info is awkwardly divided across two out of three articles at present, even though it pertains to all three. [[User:LinkTheLefty|LinkTheLefty]] ([[User talk:LinkTheLefty|talk]]) 08:25, January 22, 2025 (EST)
'''Deadline''': November 11, 2024, 23:59 GMT
:I see the "species" article as being mostly about how they battle, as well as the best place to note the various unused setups containing differing amounts of them, while a singular character duo article would cover their role in the story and general characterization. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 09:15, January 22, 2025 (EST)


====Support - consistent icons (change the few remaining icon images and make it a general rule for the future)====
By the way, wouldn't option 1 go against [[MarioWiki:Minor NPCs]]? --{{User:Waluigi Time/sig}} 10:27, January 27, 2025 (EST)
#{{user|Doc von Schmeltwick}} - ''Icon'' haz dead, never-funny-in-the-first-place memes about fast food sandwiches?
:Not any more than [[Cork and Cask]] does, I'd say. The main difference here is that the game already has a good name that can apply to both. Speaking of which, {{@|Camwoodstock}}, would the resulting article be treated as a character or species article? The former would make more sense, in my view, but just to make sure. [[User:Blinker|Blinker]] ([[User talk:Blinker|talk]]) 10:57, January 27, 2025 (EST)
#{{user|Super Mario RPG}} - Accurate to how the graphic or texture is stored in game.
::We were imagining the former, akin to the many duos of Superstar Saga, yes. {{User:Camwoodstock/sig}} 11:51, January 27, 2025 (EST)
#{{User|Hewer}} Per fast food sandwiches
:::Come to think about it, it's also a little odd how Booster's main trio of [[Snifster]]s are covered on what is otherwise treated as a species article. That's a somewhat similar situation, isn't it? [[User:Blinker|Blinker]] ([[User talk:Blinker|talk]]) 10:29, January 28, 2025 (EST)
#{{User|Ahemtoday}} Per proposal.
::::Well they don't really have names, they have numbers. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 12:51, February 2, 2025 (EST)
#{{User|blueberrymuffin}} Per proposal.


====Oppose - who needs consistency? (do nothing)====
===Merge the Ancient Beanbean Civilizations to List of implied species (and Hooroglyphs info to that)===
#{{User|Waluigi Time}} Rawsize exists.
Another multiple-way merge! This is about the following articles:
#{{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.
*[[List of implied species]]
#{{user|Lakituthequick}} Per WT.
*[[Hoohoo civilization]]
#{{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.
*[[Soybean civilization]]
#{{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.
*[[Hooroglyphs]]
#{{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.


====Comments====
Simply put, these are all ancient civilizations that we don't encounter in-game, since. Well. They're long-gone ancient civilizations that are only ever mentioned alongside occasional things that originate from them, most notably the statue [[Hoohooros]], but also [[Hooroglyphs]] and [[Beanstone]]s. While we can understand keeping Hoohooros and Beanstones split--the former is a full boss encounter, the latter is a key item involved in a sidequest--we're less sure about Hooroglyphs in particular. Merges for the civilizations have been called for since around late 2023, and we think the Hooroglyphs should be merged as their split mostly comes from the decision to make a page for them back in ''March 2007'', actually predating the Hoohoo civilization article. We've provided an option for keeping Hooroglyphs split, though we imagine it'd be better to merge this with the Hoohoo civilization information.
{{@|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)
'''Proposer''': {{User|Camwoodstock}}<br>
: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)
'''Deadline''': February 13, 2025, 23:59 GMT
::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)


{{@|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)
====Merge all (merge Hoohoo/Soybean Civilizations to List, merge Hooroglyphs to the Hoohoo Civilization section)====
#{{User|Camwoodstock}} Per ourselves; these civilizations don't have as much plot relevance nor lore behind them as something like, say, [[Squirpina XIV]] or the [[Flora Kingdom royalty]], at most serving as the origin for [[Hoohooros]].


{{@|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)
====Merge civilizations, leave Hooroglyphs alone====
: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)
#{{User|LinkTheLefty}} The glyphs are actually seen, though.
::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)
#{{User|Jdtendo}} Per LinkTheLefty.
:::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)
====Merge Hooroglyphs to Hoohoo civilization, leave civilizations alone====
: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)
====Merge none (do nothing)====
: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)


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)
====Comments (Indus River Valley civilization joke here)====
: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)


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

Latest revision as of 03:47, February 3, 2025

Image used as a banner for the Proposals page

Current time:
Monday, February 3rd, 12:05 GMT

Proposals can be new features, the removal of previously-added features that have tired out, or new policies that must be approved via consensus before any action is taken.
  • Voting periods last for two weeks, but can close early or be extended (see below).
  • Any autoconfirmed user can support or oppose, but must have a strong reason for doing so.
  • All proposals must be approved by a majority of voters, including proposals with more than two options.
  • For past proposals, see the proposal archive and the talk page proposal archive.

If you would like to get feedback on an idea before formally proposing it here, you may do so on the proposals talk. For talk page proposals, you can discuss the changes on the talk page itself before creating the TPP there.

How to

If someone has an idea about improving the wiki or managing its community, but feel that they need community approval before acting upon that idea, they may make a proposal about it. They must have a strong argument supporting their idea and be willing to discuss it in detail with other users, who will then vote on whether or not they think the idea should be implemented. Proposals should include links to all relevant pages and writing guidelines. Proposals must include a link to the draft page. Any pages that would be largely affected by the proposal should be marked with {{proposal notice}}.

Rules

  1. Only autoconfirmed users may create or vote on proposals. Proposals can be created by one user or co-authored by two users.
  2. Anyone is free to comment on proposals (provided that the page's protection level allows them to edit).
  3. Proposals conclude at the end of the day (23:59) two weeks after voting starts (all times GMT).
    • For example, if a proposal is added at any time on Monday, August 1, 2011, the voting starts immediately and the deadline is two weeks later on Monday, August 15, at 23:59 GMT.
  4. Users may vote for more than one option, but they may not vote for every option available.
  5. Every vote should have a strong, sensible reason accompanying it. Agreeing with a previously mentioned reason given by another user is acceptable (including "per" votes), but tangential comments, heavy sarcasm, and other misleading or irrelevant quips are just as invalid as providing no reason at all.
  6. Users who feel that certain votes were cast in bad faith or which truly have no merit can address the votes in the comments section. Users can ask a voter to clarify their position, point out mistakes or flaws in their arguments, or call for the outright removal of the vote if it lacks sufficient reasoning. Users may not remove or alter the content of anyone else's votes. Voters can remove or rewrite their own vote(s) at any time, but the final decision to remove another user's vote lies solely with the wiki staff.
    • Users can also use the comments section to bring up any concerns or mistakes in regards to the proposal itself. In such cases, it's important the proposer addresses any concerns raised as soon as possible. Even if the supporting side might be winning by a wide margin, that should be no reason for such questions to be left unanswered. They may point out any missing details that might have been overlooked by the proposer, so it's a good idea as the proposer to check them frequently to achieve the most accurate outcome possible.
  7. If a user makes a vote and is subsequently blocked for any amount of time, their vote is removed. However, if the block ends before the proposal ends, then the user in question holds the right to re-cast their vote. If a proposer is blocked, their vote is removed and "(blocked)" is added next to their name in the "Proposer:" line of the proposal, which runs until its deadline as normal. If the proposal passes, it falls to the supporters of the idea to enact any changes in a timely manner.
  8. Proposals cannot contradict an already ongoing proposal or overturn the decision of a previous proposal that concluded less than four weeks (28 days) ago.
  9. If one week before a proposal's initial deadline, the first place option is ahead of the second place option by eight or more votes and the first place option has at least 80% approval, then the proposal concludes early. Wiki staff may tag a proposal with "Do not close early" at any time to prevent an early close, if needed.
    • Tag the proposal with {{early notice}} if it is on track for an early close. Use {{proposal check|early=yes}} to perform the check.
  10. Any proposal where none of the options have at least four votes will be extended for another week. If after three extensions, no options have at least four votes, the proposal will be listed as "NO QUORUM." The original proposer then has the option to relist said proposal to generate more discussion.
  11. If a proposal reaches its deadline and there is a tie for first place, then the proposal is extended for another week.
  12. If a proposal reaches its deadline and the first place option is ahead of the second place option by three or more votes, then the first place option must have over 50% approval to win. If the margin is only one or two votes, then the first place option must have at least 60% approval to win. If the required approval threshold is not met, then the proposal is extended for another week.
    • Use {{proposal check}} to automate this calculation; see the template page for usage instructions and examples.
  13. Proposals can be extended a maximum of three times. If a consensus has not been reached by the fourth deadline, then the proposal fails and cannot be re-proposed until at least four weeks after the last deadline.
  14. All proposals are archived. The original proposer must take action accordingly if the outcome of the proposal dictates it. If it requires the help of an administrator, the proposer can ask for that help.
  15. After a proposal passes, it is added to the appropriate list of "unimplemented proposals" below and is removed once it has been sufficiently implemented.
  16. If the wiki staff deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to cancel it at any time.
  17. Proposals can only be rewritten or canceled by their proposer within the first four days of their creation. However, proposers can request that their proposal be canceled by a staff member at any time, provided they have a valid reason for it. Please note that canceled proposals must also be archived.
  18. Unless there is major disagreement about whether certain content should be included, there should not be proposals about creating, expanding, rewriting, or otherwise fixing up pages. To organize efforts about improving articles on neglected or completely missing subjects, try setting up a collaboration thread on the forums.
  19. Proposals cannot be made about promotions and demotions. Staff changes are discussed internally and handled by the bureaucrats.
  20. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
  21. Proposals must have a status quo option (e.g. Oppose, Do nothing) unless the status quo itself violates policy.

Basic proposal formatting

Copy and paste the formatting below to get started; your username and the proposal deadline will automatically be substituted when you save the page. Update the bracketed variables with actual information, and be sure to replace the whole variable including the square brackets, so "[insert info here]" becomes "This is the inserted information" and not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but the objective(s) of each voting option must be clearly defined. Such options should also be kept to a minimum, and if something comes up in the comments, the proposal can be amended as necessary.

===[insert a title for your proposal here]===
[describe what issue this proposal is about and what changes you think should be made to improve how the wiki handles that issue]

'''Proposer''': {{User|{{subst:REVISIONUSER}}}}<br>
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT

====[option title (e.g. Support, Option 1)]: [brief summary of option]====
#{{User|{{subst:REVISIONUSER}}}} Per proposal.

====[option title (e.g. Oppose, Option 2)]: [brief summary of option]====

====Comments ([brief proposal title])====

Autoconfirmed users will now be able to vote on your proposal. Remember that you can vote on your own proposal just like the others.

To vote for an option, just insert #{{User|[your username here]}} at the bottom of the section of your choice. Just don't forget to add a valid reason for your vote behind that tag if you are voting on another user's proposal. If you are voting on your own proposal, you can simply say "Per proposal."

Talk page proposals

Proposals concerning a single page or a limited group of pages are held on the most relevant talk page regarding the matter. All of the above proposal rules also apply to talk page proposals. Place {{TPP}} under the section's heading, and once the proposal is over, replace the template with {{settled TPP}}. Proposals dealing with a large amount of splits, merges, or deletions across the wiki should still be held on this page.

All active talk page proposals must be listed below in chronological order (new proposals go at the bottom) using {{ongoing TPP}}. Include a brief description of the proposal while also mentioning any pages affected by it, a link to the talk page housing the discussion, and the deadline. If the proposal involves a page that is not yet made, use {{fake link}} to communicate its title in the description. Linking to pages not directly involved in the talk page proposal is not recommended, as it clutters the list with unnecessary links.

List of ongoing talk page proposals

Unimplemented proposals

Proposals

Break alphabetical order in enemy lists to list enemy variants below their base form, EvieMaybe (ended May 21, 2024)
Standardize sectioning for Super Mario series game articles, Nintendo101 (ended July 3, 2024)
^ NOTE: Not yet integrated for the Super Mario Maker titles and Super Mario Run.
Create new sections for gallery pages to cover "unused/pre-release/prototype/etc." graphics separate from the ones that appear in the finalized games, Doc von Schmeltwick (ended September 2, 2024)
Add film and television ratings to Template:Ratings, TheUndescribableGhost (ended October 1, 2024)
Use the classic and classic link templates when discussing classic courses in Mario Kart Tour, YoYo (ended October 2, 2024)
Clarify coverage of the Super Smash Bros. series, Doc von Schmeltwick (ended October 17, 2024)
Remove all subpage and redirect links from all navigational templates, JanMisali (ended October 31, 2024)
Prioritize MESEN/NEStopia palette for NES sprites and screenshots, Doc von Schmeltwick (ended November 3, 2024)
Stop considering reused voice clips as references (usually), Waluigi Time (ended November 8, 2024)
Allow English names from closed captions, Koopa con Carne (ended November 12, 2024)
^ NOTE: A number of names coming from closed captions are listed here.
Split off the Mario Kart Tour template(s), MightyMario (ended November 24, 2024)
Split major RPG appearances of recurring locations, EvieMaybe (ended December 16, 2024)
Stop integrating templates under the names of planets and areas in the Super Mario Galaxy games, Nintendo101 (ended December 25, 2024)
Split image categories into separate ones for assets, screenshots, and artwork, Scrooge200 (ended January 5, 2025)
Organize "List of implied" articles, EvieMaybe (ended January 12, 2025)
Split Mario & Luigi badges and remaining accessories, Camwoodstock (ended February 1, 2025)

Talk page proposals

Split all the clothing, Doc von Schmeltwick (ended September 12, 2021)
Split machine parts, Robo-Rabbit, and flag from Super Duel Mode, Doc von Schmeltwick (ended September 30, 2022)
Make bestiary list pages for the Minion Quest and Bowser Jr.'s Journey modes, Doc von Schmeltwick (ended January 11, 2024)
Allow separate articles for Diddy Kong Pilot (2003)'s subjects, Doc von Schmeltwick (ended August 3, 2024)
Create articles for specified special buildings in Super Mario Run, Salmancer (ended November 15, 2024)
Expand and rename List of characters by game to List of characters by first appearance, Hewer (ended November 20, 2024)
Merge False Character and Fighting Polygon/Wireframe/Alloy/Mii Teams into List of Super Smash Bros. series bosses, Doc von Schmeltwick (ended December 2, 2024)
Make changes to List of Smash Taunt characters, Hewer (ended December 27, 2024)
Merge Wiggler Family to Dimble Wood, Camwoodstock (ended January 11, 2025)
Split the Ink Bomb, Camwoodstock (ended January 12, 2025)
Create a catch-all Poltergust article, Blinker (ended January 21, 2025)
Merge the two Clawing for More articles, Salmancer (ended January 27, 2025)
Merge Dangan Mario to Invincible Mario, PrincessPeachFan (ended January 30, 2025)
Merge Hurricane (move) into Gale Force, EvieMaybe (ended January 30, 2025)
Give the Cluck-A-Pop Prizes articles, Camwoodstock (ended January 31, 2025)

Writing guidelines

Lower Category Item Requirement from 4 to 3

This was spurred by the introduction of the to-do bar. Thanks, to-do bar! Anyways, if you look at Special:WantedCategories, at the moment, it's all entries with 3 or fewer items each; this makes sense, given we have a policy that suggests categories are kept to only 4 or more items. However, for a good portion of the 3-itemers, these are all fairly featured images from sources like various short flash advergames, or more niche subjects like the MediaBrowser which came in a series of, well, 3 web browsers. In comparison to the 1-or-2 entry, well, entries, these have a bit more substance to them, basically waiting for a fourth image to be taken at some point; and while in some cases, that image can come up, in others... Well, what are the odds a fourth MediaBrowser is releasing when they went bust back in 2001, y'know?

While we don't feel strongly about what happens to the 1 or 2 entry categories, we do think there is just enough to these 3-entry categories to warrant a closer look our current policies are not providing. Should we lower the cutoff to 3? Or is 4 the magical number for categories?

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

Lower to 3 (triple trouble!)

  1. Camwoodstock (talk) Per ourselves, of course. We don't see any particular harm in this when, as of submitting this proposal, this would only create, what, 10 categories?
  2. Pseudo (talk) Makes sense to me, especially because, if an individual is uploading images to the wiki for a source that currently has no images, there's a solid chance that that person will upload three images. It's a popular number!
  3. Nintendo101 (talk) Three is a magic number.

Keep at 4 (forced to four!)

  1. Waluigi Time (talk) Per Porple in the comments, image categories don't have this restriction so the proposal seems moot otherwise. I don't see a benefit to reducing this limit across the board, and I'm very hesitant to support without a clearer picture of the implications. (The assertion in the comments that this wouldn't have immediate impact was based on the list on Special:WantedCategories - there weren't any categories there besides image ones because that would require mainspace articles to have redlinked categories that would go against policy if you made them. Obviously, that wouldn't fly.)
  2. Sparks (talk) Per Porplemontage and Waluigi Time.
  3. Ahemtoday (talk) Per Waluigi Time.
  4. Super Mario RPG (talk) Honestly, five would be a better restriction so that it's a well rounded number.
  5. Jdtendo (talk) Per Waluigi Time.
  6. TheFlameChomp (talk) Per Waluigi Time.
  7. Mushroom Head (talk) Per all.

Comments (wait, letters in numbers?)

The intent of that restriction is that, for example, if there aren't four articles for Category:Super Paper Mario characters then the couple characters would just go in Category:Super Paper Mario rather than create the subcategory. Image categories are different since moving up the tree in the same way would be undesirable (there would be a bunch of random images at the bottom of Category:Game images rather than those categories being redlinked). We can create image categories with as few as one entry; I updated MarioWiki:Categories. If you still want to change the number needed for articles, up to you. --Steve (talk) Get Firefox 22:38, January 21, 2025 (EST)

Oh! We didn't know that, good to know! We'd like to proceed with the proposal, even if we don't think it'd have any immediate impact under these rules--all the 3-item categories have to do with images at the moment. Camwoodstock-sigicon.png~Camwoodstock (talk) 22:41, January 21, 2025 (EST)

New features

None at the moment.

Removals

None at the moment.

Changes

Allow users to remove friendship requests from their talk page

This proposal is not about banning friendship requests. Rather, it's about allowing users to remove friendship requests on their talk page. The reason for this is that some people are here to collaborate on a giant community project on the Super Mario franchise. Sure, it's possible to ignore it, but some may want to remove it outright, like what happened here. I've seen a few talk pages that notify that they will ignore friendship requests, like here, and this proposal will allow users to remove any friend requests as they see fit.

If this proposal passes, only the user will be allowed to remove friendship requests from their talk pages, including the user in the first link should they want to remove it again.

This proposal falls directly in line with MarioWiki:Courtesy, which states: "Talking and making friends is fine, but sometimes a user simply wants to edit, and they should be left to it."

Proposer: Super Mario RPG (talk)
Deadline: January 29, 2025, 23:59 GMT Extended to February 5, 2025, 23:59 GMT

Support

  1. Super Mario RPG (talk) Per.
  2. Shadow2 (talk) Excuse me?? We actually prohibit this here? Wtf?? That is one of the most ridiculous things I've ever heard. Literally any other platform that has ever existed gives you the ability to deny or remove friend requests... They don't just sit there forever. What if your talk page just gets swamped with friend requests from random people you don't know, taking up space and getting in the way? I also don't think it's fair, or very kind, to say "just ignore them". It'll just sit there as a reminder of a less-than-ideal relationship between two users that doesn't need to be put up on display. Honestly I didn't even know we did "Friends" on this site...maybe the better solution is to just get rid of that entirely. This is a wiki, not social media.
  3. RetroNintendo2008 (talk) Per Shadow2's comment.
  4. Waluigi Time (talk) IMO, the spirit of the no removing comments rule is to avoid disrupting wiki business by removing comments that are relevant to editing, records of discipline, and the like. I don't think that removing friend requests and potentially other forms of off-topic chatter is harmful if the owner of the talk page doesn't want them.
  5. EvieMaybe (talk) per WT
  6. Camwoodstock (talk) If someone doesn't want something ultimately unrelated to the wiki on their talk page, they shouldn't be forced to keep it. Simple-as. It would be one thing if it was "remove any conversation", as that could be particularly disruptive, but for friend requests, it's so banal that we can't see the harm in allowing people to prune those if they deem it fit.
  7. Nintendo101 (talk) Per proposal and Waluigi Time. No, I do think this is principally fine. Though I do not support the broader scope envisioned by Shadow2.
  8. LinkTheLefty (talk) Agreed with N101.
  9. Paper Plumm (talk) While the concerns presented by the opposing side are valid, I think we should allow people to have the ability to control this sort of thing, this will have no consequence to you if you enjoy having friend requests however for those who are against this they are able to gain a net positive in relieving themselves of needless clutter. As per the broader ideas presented, that definitely needs its own vote, however again I am of the mind that the option should be made available but not forced upon all.
  10. Killer Moth (talk) Per proposal, Waluigi Time, Camwoodstock, and Paper Plumm.
  11. Daisy4Days (talk) Per proposal. I just don’t see why one should have to keep that; it’s completely unrelated to editing the wiki.
  12. Ahemtoday (talk) Per Shadow2.

Oppose

  1. Ray Trace (talk) This hasn't been a problem as if lately and doesn't really fix anything. Just ignore the comments unless it's warning/block-worthy behavior like harassment or vandalism.
  2. Hewer (talk) I don't really see the point of this. A user can ignore friend requests, or any messages for that matter, without having to delete them.
  3. Sparks (talk) Friend requests are not any kind of vandalism or flaming. However, if they falsely claim to be their friend and steal their userbox then it would be an issue.
  4. Jdtendo (talk) I don't see why we would allow the removal of friend requests specifically and no other kind of non-insulting comments.
  5. Technetium (talk) No one even does friend requests nowadays.
  6. Mario (talk) Iffy on this. The case was a fringe one due to a user removing a very old friend request comment done by a user that I recall had sent out friend requests very liberally. I don't think it should be exactly precedent setting, especially due to potential for misuse (removing friend requests may be seen as an act of hostility, maybe impolite even if unintentional; ignoring it also has the problem but not as severe). Additionally, friend requests are not as common as they used to be, and due to this I just rather users exercise discretion rather than establish policy I don't think is wholly necessary. My preference is leaving up to individual to set boundaries for friend requests; a lot of users already request no friend requests, no swear words, or no inane comments on their talk pages and this is where they reserve that right to remove it or censor it. Maybe instead we can have removing friend requests be within rules, but it must be declared first in the talk page, either through a comment ("sorry, I don't accept friend requests") or as a talk page rule.
  7. Tails777 (talk) I can see the logic behind allowing people to remove such requests from their talk pages, but at the same time, yeah, it's not really as common anymore. I just feel like politely declining is as friendly as it can get and flat out deleting them could just lead to other negative interactions.
  8. Mushroom Head (talk) It’s honestly rude to just delete them. If they were not nice, I guess it would make sense, but I can’t get over it when others delete your message.
  9. Shy Guy on Wheels (talk) A friend request ain't gonna hurt you. If you have a problem with it, you can always just reject it.
  10. Arend (talk) On top of what everyone else has already said, I think leaving them there is more useful for archival purposes.
  11. MCD (talk) This seems like something that would spark more pointless arguments and bad blood than it would prevent, honestly. Nothing wrong with saying 'no' if you really don't want to be friends with them, or just ignoring it. Also, the example that sparked this isn't anything to do with courtesy - the message in question was from 9 years ago and was not removed because the user was uncomfortable with it, but they seem to be basically starting their whole account from scratch and that was the one message on the page. In that context, I think removing the message was fine, but anything like that should decided on a case-by-case basis if there's nothing wiki-related or worth archiving otherwise.
  12. Sdman213 (talk) Per all.
  13. Green Star (talk) Friend requests may not be especially helpful when it comes to building an encyclopedia, but allowing users to remove rather than simply ignore them isn't exactly helpful for building a friendly and welcoming community.

Nintendo101 (talk) It is not our place to remove talkpage comments — regardless of comment — unless it is harassment or vandalization, to which stuff like this is neither. I really think this energy and desire to helping out is best spent trying to elaborate on our thinner articles, of which there are many.

Comments

@Nintendo101 Ignoring friendship requests and removing them are basically the same thing. It's not required to foster a collaborative community environment, whether a user wants to accept a friendship request or not. Super Mario RPG (talk) 09:52, January 15, 2025 (EST)

I think it is fine for users to ignore friend requests and even remove them if they so choose. I do not think it is the place of another user — without being asked — to remove them, especially on older user talk pages. — Nintendo101 (talk) 10:03, January 15, 2025 (EST)
@Nintendo101 The proposal is for only the user whom the talk page belongs to removing friend requests being allowed to remove friend requests, not others removing it from their talk page for them. I tried to make it clear with bold emphasis. Super Mario RPG (talk) 10:04, January 15, 2025 (EST)
Do we really need a proposal for this, though? And besides, I don't think friend requests are much of a thing here anymore. Technetium (talk) 10:24, January 15, 2025 (EST)
I would've thought not, though a user got reverted for removing a friend request from own talk page (see proposal text). Super Mario RPG (talk) 10:26, January 15, 2025 (EST)
My bad, I thought you had removed it to begin with. Apologies for the misunderstanding. Technetium (talk) 10:50, January 15, 2025 (EST)

Adding on, there's a BIG difference between "Removing a warning or disciplinary action", "Hiding or censoring past discussions"...and "Getting rid of a little friend request". Sure it's important to retain important information and discussions on a talk page, but if it's not relevant to anything or important then the user shouldn't be forced to keep it forever. Perhaps a more meaningful proposal would be, "Allow users to remove unimportant information from their talk page". I've looked at the talk pages for some users on this wiki, and some of them are filled with...a lot. Like, a ton of roleplay stuff, joking and childish behaviour, gigantic images that take up a ton of space. Is it really vitally necessary to retain this "information"? Can't we be allowed to clean up our talk pages or remove stuff that just doesn't matter? Stuff that doesn't actually relate in any way to editing on the wiki or user behaviour? Compare to Wikipedia, a place that is generally considered to be much more serious, strict and restrictive than here...and you are allowed to remove stuff from your talk page on Wikipedia. In fact, you're even allowed to remove disciplinary warnings. So why is it so much more locked-down here? Shadow2 (talk) 08:55, January 16, 2025 (EST)

I've been trying to convey this very thing. I'm not against people befriending on the wiki, or even WikiLove to help motivate others. But there's a big difference between removing friend requests to removing formal warnings, reminders, and block notices from one's talk page. Super Mario RPG (talk) 09:24, January 16, 2025 (EST)
"I've looked at the talk pages for some users on this wiki, and some of them are filled with...a lot. [...] Is it really vitally necessary to retain this 'information'?"
It absolutely is for those users on the talk pages. Mario It's me, Mario! (Talk / Stalk) 20:12, January 16, 2025 (EST)
...Right...And it's their choice to keep it. But as I understand it, the rules of this website prevents those users from removing it if they should so choose. Shadow2 (talk) 20:44, January 16, 2025 (EST)
I just don't see the issue. Those talk pages you cited are typically content exchanged between two users who know each other well enough. It doesn't happen with two strangers. If you don't want the content in the rare case some random person decides to post an image you don't like, then reply to it to indicate such, and it shouldn't be posted again. If they do it again, it's a courtesy violation and it's actionable, just ask sysops to remove it. It's not really violating the spirit of the "no removing comments" rule. Our current rules are already equipped to deal with this, I don't think it's a great idea to remove this content in most cases without at least prior notice, which I think this proposal will allow. Mario It's me, Mario! (Talk / Stalk) 20:59, January 16, 2025 (EST)
That's the problem right there, you've perfectly outlined it. "some random person decides to post an image you don't like, then reply to it to indicate such, and it shouldn't be posted again". But the image is still there, even though I don't want it to be there. Why does the image I don't like have to remain permanently affixed to my talk page, taking up space and not doing anything to further the building of this wiki? Rather, I should be allowed to say "I don't like this image, I am going to remove it now." Shadow2 (talk) 22:49, January 16, 2025 (EST)

I want to make something clear: under the current policy for user talk pages, "you cannot remove conversations or comments, unless they are acts of vandalism or trolling". Comments that you can remove are the exception, not the norm. If this proposal passes, should we change the end of the sentence to "unless they are acts of vandalism, trolling, or friend requests"? Jdtendo(T|C) 13:13, January 16, 2025 (EST)

No. This is about letting users to decide whether to remove friend requests from their talk page if they do not want that solicitation. "you cannot remove conversations or comments, unless they are acts of vandalism or trolling" would be more along the lines of, "You are not allowed to remove any comments irrelevant to wiki-related matters, such as warnings or reminders. The most leeway for removing comments from talk pages comes from vandalism, trolling, or harassment. Users are allowed to remove friend requests from their own talk page as well." Super Mario RPG (talk) 15:43, January 16, 2025 (EST)
@Super Mario RPG receiving a friend request does not mean you have to engage with it or accept, does it? So I am not really sure it constitutes as solicitation. Is the idea of leaving a friend request there at all the source of discomfort, even if they can ignore it? Or is it the principal that a user should have some say as to what is on their own talk page as their user page? I worry allowing users to remove their comments from their talk pages (especially from the perspective of what Shadow2 is suggesting) would open a can of worms, enabling more disputes between users. - Nintendo101 (talk) 21:13, January 16, 2025 (EST)
It's the principal of a user deciding whether they want it on their talk page or not. It would be silly if disputes occur over someone removing friendship requests. Super Mario RPG (talk) 21:20, January 16, 2025 (EST)
No, we should change it to "acts of vandalism, trolling, or unimportant matters unrelated to editing on the wiki." Shadow2 (talk) 18:28, January 16, 2025 (EST)
I believe users should have some fun here and there. The wiki isn't just a super serious website! Plus, it gives us all good laughs and memories to look back on. link:User:Sparks Sparks (talk) link:User:Sparks 20:32, January 16, 2025 (EST)
@Shadow2 What are some specific examples? Super Mario RPG (talk) 20:35, January 16, 2025 (EST)
Examples of what? Shadow2 (talk) 20:44, January 16, 2025 (EST)
Of what other "unimportant matters" you'd like for users to be allowed to remove from their own talk page. Super Mario RPG (talk) 20:47, January 16, 2025 (EST)
Unfortunately it might be in bad faith to say "Look at this other user's page, this is considered unimportant and if it were on MY page, I would want it deleted." But like, when I first started on Wikipedia a friend of mine left a message on my talk page that said "Sup noob". I eventually fell out of favour with this friend and didn't really want to have anything to do with him anymore, so I removed it. It wasn't an important message, it didn't relate to any activity on the wiki, it was just a silly, pointless message. I liked it at first so I kept it, then I decided I didn't want it there anymore so I removed it. There's a lot of other very silly, jokey text I've seen on talk pages that I'm sure most users are happy to keep, but if they don't want to keep it then they should have the option of removing it. Shadow2 (talk) 23:00, January 16, 2025 (EST)

@Technetium That's true, no one does, but me and some others still would prefer a precedent to be set. This proposal began because someone blanked a friend request from own talk page recently, so this may occur every once in a while. The reason that one was allowed to be removed (by @Mario) is because it was a single comment from long ago that had no constructive merit when applied to this year and wasn't that important to keep when the user decided to remove it. This proposal would allow it in all cases. Removing such messages from one's own talk page is the equivalent of declining friend requests on social platforms. It stops the message from lingering and saves having to do a talk page disclaimer that friend requests will be ignored, since some people may choose to accept certain friend requests but not others. This opens room for choices. Super Mario RPG (talk) 16:21, January 16, 2025 (EST)

@Mario So if this proposal fails, would there be some clarification in rules behind the justification of such content being removed? Super Mario RPG (talk) 20:35, January 16, 2025 (EST)

Toadlose.gif Maybe? I don't know. This proposal was kind of unexpected for me to be honest. Mario It's me, Mario! (Talk / Stalk) 20:38, January 16, 2025 (EST)
I do believe that the intentions of this proposal are good, but the scope is too narrow. It should be about granting users the freedom to remove unimportant fluff (Friend requests included) from their talk page if they so choose. Discussions about editing and building the wiki, as well as disciplinary discussions and warnings, do not fall under "unimportant fluff". Shadow2 (talk) 20:47, January 16, 2025 (EST)
@Shadow2 have you considered that the users who receive images and jokes on their talk pages like having them there? The users who send jokes and images to certain receivers view them as good friends - these are friendly acts of comradery, and they are harmless within the communal craft of wiki editing. Are you familiar with anyone who would actually like to have the ability to remove "fluffy" comments from their talk pages? - Nintendo101 (talk) 21:18, January 16, 2025 (EST)
Some narrow-scope proposals have set precedents. Super Mario RPG (talk) 21:20, January 16, 2025 (EST)
(edit conflict) I would also add that they help build a wiki by fostering trust and friendship (which is magic) and helping morale around here, but I do think Shadow2 is arguing that if they receive such content, they should see fit to remove it. However, the hypothetical being construed here involves a stranger sending the content (which probably has happened like years ago) and I dispute that the scenario isn't supported in practice, so I don't think it's a strong basis for the argument. In the rare cases that do happen (such as, well, exchanges years ago), they're resolved by a simple reply and the content doesn't really get removed or altered unless it's particularly disruptive, which has happened. If it's applicable, I do think a rule change to at least allow users to set those particular boundaries in their talk pages can help but I don't see how that's strictly disallowed in the first place like the proposal is implying. Mario It's me, Mario! (Talk / Stalk) 21:38, January 16, 2025 (EST)
"have you considered that the users who receive images and jokes on their talk pages like having them there?" Yes? Obviously? What does that have to do with what I'm saying. Why does everybody keep turning this whole proposal into "GET RID OF EVERYTHING!!" when it's not at all like that. If the users want the images and jokes on their talk page, they can keep them. If they don't want them, then there's nothing they can do because the rules prohibit removal needlessly. Shadow2 (talk) 22:49, January 16, 2025 (EST)
I think you misunderstand my point - why should we support a rule that does not actually solve any problems had by anyone in the community? - Nintendo101 (talk) 23:03, January 16, 2025 (EST)
That's an unfair assumption. It would be a problem for me if someone left something on my page, and there's probably plenty of others who would like to remove something. Conversely, what is there to gain from forcing users to keep non-important information on their talk page? Shadow2 (talk) 02:11, January 17, 2025 (EST)
I would appreciate it if you elaborated on what about my inquiry was an unfair assumption. I am generally not someone who supports the implementation of rules without cause. If there were examples of users receiving unsolicited "fluff" on the site that do not like it, or if you yourself were the receiver of such material, that would be one thing. But I do not believe either thing has happened. So what would be the point in supporting a rule like that? What are the potential consequences of rolling something like that? Facilitating edit wars on user talkpages? Making participants in a communal craft feel unwelcomed? Making users hesitant to express acts of friendship with another? The history of an article-impacting idea being lost because it emerged between two users on one of their talkpages? In my experience the users who have received light messages and images from others have established a bond elsewhere, such as on Mario Boards or the Super Mario Wiki Discord. I am not familiar of this being done between acquaintances or strangers, or people who dislike it regardless. If you had proof of that or any comparable harm, I would be more receptive to your perspective. - Nintendo101 (talk) 12:13, January 17, 2025 (EST)
Feels like I'm just shouting at a wall here, and all of my concerns are being rebuffed as "not a big deal", so I guess I'll just give up. But going forward, having learned that once someone puts something on my talk page it's stuck there for eternity, no matter what it is, makes me incredibly uncomfortable. Shadow2 (talk) 18:48, January 17, 2025 (EST)

This proposal says: ‘You may get your edit reverted for being nice, but because swearing is not being nice, you can swear the şħįț out’ MHA Super Mushroom:) at 07:55, January 17, 2025 (EST)

Merge the Tortes

Three birds with one stone with this one! This proposal concerns the following articles:

The argument is fairly simple; the Chef and Apprentice Tortes are just a duo never seen separate from one another, like the Jellyfish Sisters, or Cork and Cask--and given they are the only Tortes we see in the game, it seems only fair to merge that article as well. This is only particularly unique in the amount of articles there are; 3 of them, for this one concept? The Torte article focuses mostly on their in-battle role, while the Chef Torte and Apprentice articles try to explain their duo role in two distinct articles.

In addition, if we merge Apprentice (Torte), either to Torte or to Chef Torte, we should probably move Apprentice (Snifit) over to Apprentice, and give it the {{about}} template.

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

Merge all 3 to Torte (It's burnt...)

  1. Camwoodstock (talk) Primary option. It's probably the simplest option overall, if you ask us, and it fits with how we handle the various duos of Superstar Saga.
  2. LinkTheLefty (talk) Unusually, these guys don't even have unique battle labels.
  3. Sparks (talk) Merge!
  4. Blinker (talk) Per proposal. (By the way, I'm also rethinking my position on the Iron Cleft situation...)
  5. Ahemtoday (talk) Per proposal.

Nintendo101 (talk) Per proposal.

Merge Chef Torte & Apprentice, keep them split from Torte (It's just a little crispy.)

  1. Camwoodstock (talk) Secondary option; if we really must keep Torte split from the duo we see in-game, that's fine, but we can't see any particular reason to keep the duo split up.
  2. Doc von Schmeltwick (talk) - Also if I recall correctly, that inconsistent-in-English accent difference is not present in Japanese, where their speech patterns are mostly the same. I'm not sure about merging them to the species since they at least have unique names from the species, unlike say, Birdo.
  3. Waluigi Time (talk) Per Doc in the comments. This would also be consistent with last year's proposal for Iron Clefts/the Iron Adonis Twins.
  4. DryBonesBandit (talk) Per all. If all three'd be merged, I'd rather the title be "Chef Torte and Apprentice" anyway, because iirc they're the only Tortes in the game.
  5. Paper Plumm (talk) Per all.
  6. Nintendo101 (talk) I think this makes more sense, from the comments below.
  7. Technetium (talk) Per all.
  8. SolemnStormcloud (talk) Per Waluigi Time.

Do nothing (It's gourmet!)

Comments (It's... Alive???)

This can easily be four birds with one stone, since "Apprentice (Snifit)" can become the default article (the identifier's a little dated anyway) and the paltry disambig can be turned into an {{about}}. LinkTheLefty (talk) 22:08, January 19, 2025 (EST)

Good observation, actually! Went and added this. Camwoodstock-sigicon.png~Camwoodstock (talk) 22:15, January 19, 2025 (EST)

@Doc: On that note, because of once and only once, that info is awkwardly divided across two out of three articles at present, even though it pertains to all three. LinkTheLefty (talk) 08:25, January 22, 2025 (EST)

I see the "species" article as being mostly about how they battle, as well as the best place to note the various unused setups containing differing amounts of them, while a singular character duo article would cover their role in the story and general characterization. Doc von Schmeltwick (talk) 09:15, January 22, 2025 (EST)

By the way, wouldn't option 1 go against MarioWiki:Minor NPCs? --Waluigi's head icon in Mario Kart 8 Deluxe. Too Bad! Waluigi Time! 10:27, January 27, 2025 (EST)

Not any more than Cork and Cask does, I'd say. The main difference here is that the game already has a good name that can apply to both. Speaking of which, @Camwoodstock, would the resulting article be treated as a character or species article? The former would make more sense, in my view, but just to make sure. Blinker (talk) 10:57, January 27, 2025 (EST)
We were imagining the former, akin to the many duos of Superstar Saga, yes. Camwoodstock-sigicon.png~Camwoodstock (talk) 11:51, January 27, 2025 (EST)
Come to think about it, it's also a little odd how Booster's main trio of Snifsters are covered on what is otherwise treated as a species article. That's a somewhat similar situation, isn't it? Blinker (talk) 10:29, January 28, 2025 (EST)
Well they don't really have names, they have numbers. Doc von Schmeltwick (talk) 12:51, February 2, 2025 (EST)

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

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

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

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

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

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

Merge civilizations, leave Hooroglyphs alone

  1. LinkTheLefty (talk) The glyphs are actually seen, though.
  2. Jdtendo (talk) Per LinkTheLefty.

Merge Hooroglyphs to Hoohoo civilization, leave civilizations alone

Merge none (do nothing)

Comments (Indus River Valley civilization joke here)

Miscellaneous

None at the moment.