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===
''None at the moment.''
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.


That being said, these are the points I judged good ones to encourage when it comes to creating tables:
==New features==
===Establish a format for poll proposals on the archive lists===
Something that's slipped through the cracks when we invented poll proposals was what we do when we add them to [[MarioWiki:Proposals/Archive|these]] [[MarioWiki:Proposals/TPP_archive|pages]]. We can't simply have one link to the poll proposal — the entire purpose of the format is that different parts of it can pass and fail independently of one another. What color do we put a proposal where one thing fails and another thing succeeds in?


'''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.
I have several pitches for you.


'''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.
<big>'''''OPTION ZERO'''''</big><br>
Do nothing. I'm putting this at the front because I want to leave room for any good-sounding solutions beyond the four I'm about to suggest. <s>It's here on the proposal at all because I'm pretty sure I'm legally obligated to put it here, but I'll be honest — I'm not entirely sure what this winning would... mean. Our hand will eventually be forced when our first poll proposal fully resolves, so a format will be established one way or the other.</s>


'''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.
''EDIT: It has been helpfully pointed out that there is a [https://www.mariowiki.com/index.php?title=MarioWiki:Proposals/Header&diff=prev&oldid=4772367 current policy] — they are red if they all issues fail, gray if at least one passes and is unimplemented, and green if at least one passes and all issues are implemented. A "one issue changes the color" kind of rule. It's definitely not insensible, but I feel that we could be conveying more information. Still, even if  this if the "fail option", we have a policy now, so I got what I wanted even if this one wins.''


'''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.
<big>'''''OPTION ONE'''''</big><br>
The different issues of a poll proposal share a number corresponding to when the first issue closes. They're listed separately, and distinguished from each other via letters. As an example, the three parts of [[Talk:Yoshi_(species)#Properly_define_Brown_Yoshi|the Brown Yoshi proposal]] would slot in at #83A, #83B, and #83C. (That would shove some other proposals down; we could also just append them to the end of the list like normal and brush off the inconsistency if y'all prefer.)


'''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.
The Brown Yoshi proposal is also a handy demonstration of an edge case we have to contend with — if this proposal passed ''right now'', we would list #83A as red and #83B as gray, but what would happen with #83C, which is still ongoing? This is the aspect on which Options One and Two differ. In Option One, issues are not added to the archive page until they close. The page would only contain #83A and #83B if the proposal passed right now, with #83C being added later


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.
I would like to note that the Brown Yoshi proposal is a remarkably well-behaved example. If the issues were ordered differently, we may at one point have #83A and #83C on the list with no #83B until later.


'''Proposer''': {{User|Bro Hammer}}<br>
<big>'''''OPTION TWO'''''</big><br>
'''Deadline''': November 6, 2024, 23:59 GMT
Option Two is identical to Option One except in how it handles open issues on partially closed poll proposals. In this option, they ''are'' added to the list alongside the other issues, and marked with a new color — let's say black.


====Support====
This prevents the awkward gaps we would be susceptible to in Option One, but it ''is'' introducing a whole color for a temporary edge case.
#{{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====
<big>'''''OPTION THREE'''''</big><br>
#{{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.
Option Three is simpler. We create a new color in the archive for poll proposals — I guess let's say black again. Poll proposals get added to the archive when all issues on them are closed.
#[[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====
This saves space (the other options will have to give fourteen entries to [[Talk:List_of_references_on_the_Internet#Determine_what_memes_should_be_on_the_Internet_references_page|this proposal]], but it means the entry on the list doesn't reflect anything about any individual issue's status, such as whether it's been implemented or not.
{{@|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)
''EDIT: Camwoodstock's pitch below of using three colors (and, implicitly, adding the poll proposal to the archive when it has any closed issues) doesn't entirely eliminate that negative, but it does seem much more useful than just having the one color.''
: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)
<big>'''''OPTION FOUR'''''</big><br>
: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)
Option Four is simpler still. Each issue is treated as if it were an entirely separate proposal. Each gets numbered and appended to the list when it closes regardless of what anything else in the poll proposal is up to.
: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)
The negative of this way of doing it is that the issues of a poll proposal may end up strewn about the list in a way that doesn't really reflect that they're a related thing.
: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)
'''Proposer''': {{User|Ahemtoday}}<br>
: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)
'''Deadline''': March 18, 2025, 23:59 GMT
::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.
====Option Zero====
#{{User|Jdtendo}} Per Porple "Steve" Montage in the comments.
#{{User|Waluigi Time}} Per Porple.
#{{User|EvieMaybe}} perple montage
#{{User|Camwoodstock}} Per Porple in the comments, though admittedly this is more of a secondary option to our more robust version of Option Three we pitched. Status quo isn't the ''worst'' thing in the world, and we do acknowledge our more robust solution of "dark colors" may be a bit harder to convey as we've been slowly rolling out... Well, a dark mode for the ''whole wiki''. (If it was down to us, the poll proposals would use lighter colors in dark mode, before you ask; of course, if that option somehow wins, we'd be down to help fine-tune it.)
#{{User|Arend}} Per Porple.
#{{User|Nintendo101}} Per porplemontage.
#{{User|Salmancer}} Oh, huh. I suppose this is a solved problem then.  


::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.
====Option One====
#{{User|Ahemtoday}} It's either this or Option Two for me — it's important to me that the issues end up next to each other on the archive ''and'' that the status of each one is visible on the page.
#{{User|Salmancer}} There's no rule saying a poll proposal has to be for small things, since part of the premise was reducing the need for large numbers of combination options. There could be poll proposals that have wide scopes, and as such I think we're going to have to stomach the poll proposals with 10+ proposals in them to make it easier to track policy without thumbing through old proposal pages. Also an archive is for the past, not the present.


::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)
====Option Two====
:::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)
#{{User|Ahemtoday}} See my note about Option One.
#{{User|Camwoodstock}} Secondary option, but we do think darker shades of the colors (a-la our pitch for Option Three) would be nice. Helps distinguish at a glance what was a poll proposal.


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)
====Option Three====
:To be fair, this is a fansite. {{User:Hewer/sig}} 04:20, October 25, 2024 (EDT)
#{{User|Camwoodstock}} We would like to pitch a more sophisticated variant of this; 3 new colors. One for a poll that has concluded, one for one that's partially ongoing, and one for a poll that has been partially overturned by a future proposal. Maybe dark green, dark gray/maybe a de-saturated dark green a-la the Shroom Spotlight template, and a dark yellow? The darker colors, of course, to contrast with the non-poll proposals. (On dark mode, we'd probably make these lighter, rather than darker, provided we actually even add dark mode compatibility to the proposal archive colors.)
#{{User|Rykitu}} Per all.
#{{User|Ahemtoday}} I definitely see the appeal in having poll proposals under a singular listing, but I think they'd be better served by having one or multiple new colors rather than using the standard red and green.


{| class="mw-collapsible mw-collapsed" style="width: 40%; float: right; text-align: center;"
<s>#{{User|Jdtendo}} Listing every single poll would probably take a lot of space whereas the whole purpose of a poll proposal is bringing together many similar polls that would be too cumbersome to handle separately. I would prefer having a single proposal listed as "Determine what memes should be on the Internet references page" that users can click on to check the detailed results rather than cluttering the list with a dozen links.</s>
|- 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"
====Option Four====
|-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"
====Comments====
|-style="background: #9A0607; color: #fff;"
{{@|Camwoodstock}} — I definitely think your pitch for Option Three is better than the version I was suggesting. I'm not really sure about the pitch for Option Two, though — the letters already distinguish them, and I feel like they'd seem more like separate states rather than a "modifier" on some of the existing ones. Not to mention, wouldn't we need a darker version of every single color just in case? That's a lot of changes to make, and we'd end up running into problems with dark blue, teal, and dark teal; or "dark white", gray, and dark gray. [[User:Ahemtoday|Ahemtoday]] ([[User talk:Ahemtoday|talk]]) 03:20, March 4, 2025 (EST)
!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"
I don't quite understand option one and two, as the above rules for poll proposals state "A poll proposal closes after all of its options have been settled, and no action is taken until then. If all options fail, then nothing will be done." --[[User:PopitTart|PopitTart]] ([[User talk:PopitTart|talk]]) 07:09, March 4, 2025 (EST)
|-style="background: #FEC724; color: #000;"
:Could you explain the contradiction in greater detail? I don't see what you mean. [[User:Ahemtoday|Ahemtoday]] ([[User talk:Ahemtoday|talk]]) 12:01, March 4, 2025 (EST)
!Entry
::The options say "The page would only contain #83A and #83B if the proposal passed right now, with #83C being added later" and "...how it handles open issues on partially closed poll proposals" there shouldn't be any instances of archiving partially closed poll proposals, they only close all at once when every entry has been resolved.--[[User:PopitTart|PopitTart]] ([[User talk:PopitTart|talk]]) 20:07, March 4, 2025 (EST)
!Description
:::So is your position that we should use the lettering scheme from Options One and Two, but only add poll proposals to the archive page when all of their issues are closed? I don't think I agree, but I can add that as Option Five if that's what you want to vote for. [[User:Ahemtoday|Ahemtoday]] ([[User talk:Ahemtoday|talk]]) 22:48, March 4, 2025 (EST)
!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"
I feel like [https://www.mariowiki.com/index.php?title=MarioWiki:Proposals/Header&diff=prev&oldid=4772367 this] is fine. Either it's red (no change from the status quo so nothing needs to be done), gray (''some'' change was established and there is work to do), or green (some change was established and it's all done). There are other proposals where people list [https://www.mariowiki.com/MarioWiki:Proposals/Archive/70#Clarify_coverage_of_the_Super_Smash_Bros._series several things] to be done, it's not that different, it's just that now we have the ability to vote on each individual thing. But in either case you just click the link to read exactly what was approved. --{{User:Porplemontage/sig}} 10:56, March 7, 2025 (EST)
|-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==
''None at the moment.''


==Removals==
==Removals==
Line 209: Line 81:


==Changes==
==Changes==
===Remove all subpage and redirect links from all navigational templates===
===Introducing the crossover article===
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.
The passing of this proposal would accomplish seven things:
#'''See the publication of the drafted ''Zelda'' article''' discussed in this proposal, titled "{{Fake link|crossovers with ''The Legend of Zelda''}}." (The draft can be viewed [[User:Nintendo101/community garden|here]].)
#'''Funnel redirects and disambiguation pages pertaining to ''Zelda'' on the wiki to the published ''Zelda'' article''' (i.e., searches for The Legend of Zelda, Octoroks, etc. Fully covered crossover subjects like [[Link]] would keep their articles, and this would not preclude a crossover subject from receiving an article of their own in the future if warranted, such as the inclusion of Princess Zelda in a future ''Mario Tennis'' or something like that).
#'''Move details pertaining to ''Zelda'' from list articles on the site to this one''' (i.e. all information pertaining to Sheik on the [[List of fighters debuting in Super Smash Bros. Melee|list of fighters debuting in ''Super Smash Bros. Melee'']] article would be cleared, and searching for "Sheik" on the site would bring you to this article. ''Zelda'' info on the [[list of references in Nintendo video games]] article would similarly be cleared. Visitors to that article would be directed towards the published ''Zelda'' one when they reach that section of the list article).
#'''Establish a navbox for crossover articles''' (either a wholly dedicated one, an incorporation into "Template:Culture," or a retooling of "Template:Crossover characters").
#'''Establish the precedent where this can be done for other IPs with which the ''Super Mario'' franchise has crossed-over.'''
#'''Establish a 'Crossover article" section to the [[MarioWiki:Manual of Style]]''' that explains the framework for crossover articles described below. This is to be the standard structure for how other articles are to be structured.
#'''Note that this framework exists on the the [[MarioWiki:Coverage#Crossovers|crossover section of our coverage policy]]''', and provide a link directing readers to it.


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?
The ''Super Mario'' franchise is very much the IP tentpole for Nintendo Co., Ltd. and at least one of the ones for the Japanese video game industry as a whole. Consequently, ''Super Mario'' as a franchise and brand has crossed-over with many other franchises, brands, and series over its nearly fifty years of existence - not only sister series developed by Nintendo EAD and R&D, and their successor EPD (i.e. ''Duck Hunt'', ''Punch-Out!!'', ''Exictebike'', ''Metroid'', ''F-ZERO'', ''Animal Crossing'', ''Pikmin'', ''Splatoon'', etc.) and those of their external creative partners (i.e. Ape Inc.'s ''EarthBound'', HAL Laboratory's ''Kirby'', Game Freak's ''Pokémon'', etc.), but also fellow ones from other studios like Square Enix, Sega, Bandai Namco, Koei Tecmo, Chunsoft, Ubisoft, Konami, and Hudson Soft. This is not groundbreaking news: Most folks interested in gaming history already know this, especially the curators of the Super Mario Wiki. However, I do not feel like we handle this information particularly well on the site.


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]].)
A lot of coverage of ''Super Mario'' references, homages, allusions, and cameos are nestled within various list articles, inexplicitly at the end of [[Super Mario Bros.#Notes|dedicated game articles]], or in ''Super Smash Bros.'' articles with which there seemed to have been effort to bury on the site and [[List of fighters debuting in Super Smash Bros.#Captain Falcon|are not wholly about ''Super Smash Bros.'' anyways]]. This coverage, exasperated by recent efforts to reduce coverage on the ''Super Smash Bros.'' series: (1.) obfuscates the fact that ''Super Mario'' has made references and ''is'' referenced in many other franchises outside of ''Smash Bros.'' contexts, often in very meaningful ways that are interesting and fun to read about; (2.) mitigates how ''Mario'' has been an influence behind some of these other franchises; and (3.) makes finding some bits of information just very difficult. If I, as a visitor of the site, wanted to understand scenarios where ''Splatoon'' and ''Mario'' have crossed-over, I would not have an easy way to find that all in one place, and I think that is a shame.


'''Proposer''': {{User|JanMisali}}<br>
[[File:LA Wart.gif|right|200px|frog man!]]
'''Deadline''': October 31, 2024, 23:59 GMT
[[File:SM3DW WS-1 2nd Green Star.jpg|right|200px|green lad!]]
To better cover and consolidate crossover info on the site, I have been drafting what I would like to call a "<u>crossover article</u>" using [[User:Nintendo101/community garden|''The Legend of Zelda'' franchise as an example]] (with contributions from Salmancer, DryBonesBandit, Memelord2020, RHG1951, LeftyGreenMario, and LadySophie17, and feedback from Super Mario RPG, Doc von Schmeltwick, and Koopa con Carne). This is a long article, and it is not wholly completed yet, but I think it is serviceable example of what I would like us to do going forward. Crossover articles take inspiration from the {{iw|smashwiki|Mario (universe)|universe articles}} from our affiliate Smash Wiki and, as apparent in the ''Zelda'' draft, consist of the following sections:
*'''Overview''' : A brief description of what the crossover franchise/series is for those not well versed in the subject and would like to know a little more about it without visiting another site, and how this relates to ''Mario''. It is the create a foundation so the reader is not confused by descriptions or terminology in the other areas of the article. For ''Zelda'', this section may be a bit lengthier than it would be for others because ''Mario'' had a lot of direct influence on ''Zelda'' as a series.
*'''Recurring crossover subjects''': for subjects like characters, enemies, bosses, or items that make substantial appearances in or alongside ''Mario''-related media, such as subjects that used to have their own articles on the site. Each subject would be briefly explained so readers understand who they are when mentioned in other parts of the article, have explicit conceptual or design connections with ''Mario'' highlighted, and summarize areas where they specifically crossover with ''Mario''.
*'''History in the ''Super Mario'' franchise''': a history section for where the crossover subject is referenced in the ''Super Mario'' franchise itself.
*'''History in the subject series/franchise''': a history section for the inverse, where ''Super Mario'' is referenced in the franchise subject of the article. In this case, it is ''Zelda''.
*'''Shared history''' (if applicable): a history section for mutual space where both subjects appear, such as the ''Super Smash Bros.'' series, ''Tetris'' series, ''NES Remix'' series, or other media.


====Remove the extra links from navigational templates====
''Zelda'' is uniquely related to ''Mario'' and nearly as old, but crossover articles can be written for smaller franchises/series as well. The only requirement for a series/franchise to receive an article of its own is for it to directly crossover with ''Super Mario'' within an officially licensed capacity. Articles of this nature should not be written for series/franchise that simply make homages to ''Super Mario'' or have elements inspired by it, such as ''Celeste'', ''Gears of War'', or ''Astro Bot''.
#{{User|JanMisali}} As proposer.
#{{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|Camwoodstock}} This makes sense to us. It's much easier to just list a page link once and only once.
#{{User|OmegaRuby}} Per all.
#{{User|EvieMaybe}} per all
#{{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|SeanWheeler}} If we're not allowed to link redirects, how could our templates have redirect links?
#{{User|Jdtendo}} No need to clutter navboxes with useless links.


====Do nothing====
I offer three options:
#'''Support: I like the idea of crossover articles and want to see them implemented as described.'''
#'''Support: I like the idea of crossover articles, but list articles for the ''Super Smash Bros.'' series should be left alone.'''
#'''Oppose: I do not like the idea of the crossover article and do not want to see them implemented.'''


====Comments====
I know this was a long one, folks. Sorry about that, but the ideas behind this idea are multifaceted. Please let me know if you need additional clarity on anything or if you have any recommended amendments. (Also, if you would like, I welcome you to contribute to the drafted ''Zelda'' article! It is in my "<u>community</u> garden" sandbox for a reason.)
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)
: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)
::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)
:::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)


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)
'''Proposer''': {{User|Nintendo101}}<br>
'''Deadline''': March 17, 2025, 23:59 GMT


===Prioritize MESEN/NEStopia palette for NES sprites and screenshots===
====Support: let's implement crossover articles!====
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.
#{{User|Nintendo101}} [[File:Link pose SMM.png]]
#{{User|Super Mario RPG}} Per proposer.
#{{User|Koopa con Carne}} Per proposal with absolutely no second thought. Aside from the obvious value such articles would bring, this practice may incidentally just be the silver bullet for the community's differences on how to cover Smash Bros. content. Nintendo101, even with your inspiration from SmashWiki, I'd say you still managed to think out of the box here.
#{{User|Waluigi Time}} Per all.
#{{User|EvieMaybe}} been waiting a long time for this one. per proposal!
#{{User|LadySophie17}} Secondary choice, I suppose. Better than no article.
#{{User|Camwoodstock}} Secondary option; we'd rather these articles exist, even if the Smash coverage is confusing, than these articles not exist at all.
#{{User|PopitTart}} It has always felt absurd to me that [[Captain Olimar]]'s presence on the wiki is entirely an entry in [[List of fighters debuting in Super Smash Bros. Brawl]], despite being directly based on Mario himself and having appearances in ''Luigi's Mansion'', ''WarioWare: D.I.Y.'', ''Super Mario Maker'', ''Yoshi's Woolly World'', ''Mario Kart 8'', and ''WarioWare Move It!''
#{{User|Jdtendo}} Crossover articles are a great idea, and if it can also declutter ''Smash Bros.'' list articles, it's even better.
#{{User|Arend}} As long as the content from the list pages are preserved in SOME way or another, I am perfectly fine with this. I think this is a great idea, and the well-detailed draft really sold me on this.
#{{User|Nelsonic}} Makes perfect sense.
#{{User|Kaptain Skurvy}} Sounds good to me.
#{{User|Shy Guy on Wheels}} Per all. death to the smash bros lists
#{{User|Mario}} Those list pages are a spaghetti of sadness, mama mia. I love the idea of these crossover pages, wonderful idea (similar to those decade splits for the gallery pages), and they're going to be a massive step up from that mess we currently have. I don't want to keep those lists at all. Their tolerated existence makes our wiki look bad, although absolutely delicious, if you ask me.
#{{User|OmegaRuby}} The list pages are an abhorrent sight and I'd much rather have Smash information contained in these respective crossover articles - if that proves too large for the size of the existing article, then the next logical step would be a subpage for Smash Bros. information, would it not? Per all.
#{{User|Pseudo}} I love how you've put this together, Nintendo101 and other contributors! This seems like a very valuable addition to the wiki.
#{{User|SolemnStormcloud}} Per all.
#{{User|Mushzoom}} Per proposal.
#{{User|TheFlameChomp}} Per all.


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.
====Support: let's implement crossover articles, but leave ''Smash Bros.'' lists alone====
 
#{{User|LadySophie17}} Per proposal. I believe the articles would be better focused on the relationship between their respective series and Mario. Detailing all their character's Smash histories (which could get quite lengthy with something like Pokémon) would be better left in the List articles they currently are in.
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.
#{{User|Sparks}} Per Sophie.
 
#[[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) - Per Soph
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).
#{{User|Camwoodstock}} Primary option; per Sophie, we worry about the length of some Smash sections, and we feel the organization is fine enough as it is right now for Smash-related subjects.
#{{User|Tails777}} Per Sophie. I fully agree with making crossover articles to cover the relations another franchise has with Mario, but Smash in of itself is also a crossover and covering the details of these characters in a place that relates to Smash feels better.
#{{User|Arend}} Second option. I'm personally not a huge fan of loss of content, and this option allows this to be fully preserved by leaving it be. While I have been assured that the history sections will be preserved in a form better suited for the article and other details such as Classic Mode routes and stickers/trophies/spirits might be reimplemented, I'm still keeping this as a secondary option to be safe.
#{{User|Okapii}} Per Sophie.
#{{User|Nelsonic}} Second opinion.
#{{User|LinkTheLefty}} This proposal is pretty close to how I imagined covering ''Zelda'' subjects had ''[[MarioWiki:Proposals/Archive/58#Determine The Legend of Zelda: Link's Awakening and its reissues as a guest appearance and create an article covering all three versions and/or its Mario-related subjects|Link's Awakening]]'' failed!
#{{User|Killer Moth}} Per all.
#{{User|Salmancer}} Hmm, so I'm going to do this because technically each of a character's special moves gets a sentence to itself on their article/Smash list entry and those just aren't going to fit in a crossover article
#{{User|Pseudo}} Secondary choice.
#{{User|Weegie baby}} Yes.


(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.)
====Oppose: let's not implement crossover articles====


'''Proposer''': {{User|Doc von Schmeltwick}}<br>
====Crossover comments====
'''Deadline''': November 3, 2024, 23:59 GMT
I also happened to start a [[User:PopitTart/Sandbox#Pikmin (franchise)|draft for a Pikmin series article]] the other day, inspired by Nintendo101's Zelda draft. It's in a much... '''much''' rougher state, but I hope it gives an idea what these crossover articles can provide.--[[User:PopitTart|PopitTart]] ([[User talk:PopitTart|talk]]) 19:31, March 3, 2025 (EST)


====Supportopia====
{{@|Koopa con Carne}} thank you for the kind words! - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 20:30, March 3, 2025 (EST)
#{{user|Doc von Schmeltwick}} - De vunderbar vald of color. Co''RR''ECT color.
:[[File:LinkCN.jpg|50px]] {{User:Koopa con Carne/Sig}} 11:32, March 4, 2025 (EST)
#{{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====
Question: One of the proposed points is to "''Move'' details pertaining to Zelda from list articles on the site to this one", but the i.e. states that "all information pertaining to Sheik on the list of fighters debuting in Super Smash Bros. Melee article would be ''cleared''". Characters on these fighter lists have extensive history sections; will these be moved to the crossover pages as well, or will these be nixed altogether?<br>Also, what about franchises which currently only have a connection with Mario through ''Smash Bros.'', such as ARMS? Will these get a crossover article as well or not? {{User:Arend/sig}} 12:10, March 4, 2025 (EST)
:I don't know. Perhaps we'll cross that bridge when we get there. Ultimately, very few of the franchises within ''Smash Bros.'' have only crossed-over with ''Mario'' within ''Smash Bros.'', and that was at the front of my mind for this proposal. ''ARMS'' is one of the few exceptions. I should probably make some sort of list to parse what other series and franchises are within that boat. But what would you want to see, {{@|Arend}}? - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 15:52, March 4, 2025 (EST)
::I don't know... I'd understand not giving those an article given how they only crossover in ''Smash'', but it would be strange to do with ''ARMS'' considering it's probably the only franchise with such a distinction that is directly from Nintendo. I can see us making an exception and allowing a crossover article for ''ARMS'' regardless, considering how most of the ''ARMS'' development team is basically ''Mario Kart 8'' alumni anyway, but that same excuse probably wouldn't work with ''Kingdom Hearts''. Then again, maybe so few franchises would be left that we might as well make crossover pages for those anyway.<br>Anyway {{@|Nintendo101}}, you didn't answer my first question regarding the fighters' history sections on the fighter lists, so I ask again: would they be moved to the crossover pages as well, or be deleted altogether and not being covered at all? Knowing precisely what's going to happen to those (as the proposal hasn't really elaborated well on what will happen to those) is pivotal for me to pick which option to choose for, you see. That's kind of why I haven't voted yet. {{User:Arend/sig}} 20:07, March 4, 2025 (EST)
:::I personally envisioned the history sections for each fighter being disseminated within history sections as described in this proposal (one section for ''Mario'', one section for the other franchise, and one section for mutual space where both franchises crossover together). Individual characters would not have the full history sections as present in those list articles, but the individual info would largely be preserved. (I did not think it was important to reiterate granular ''Smash Bros.'' info about Stickers, Trophies, Classic Mode routes, etc. because that seemed more about ''Zelda'' in ''Smash Bros.'' and less about ''Zelda'' with ''Mario'' in ''Smash Bros.'', but Hewer had reservations on that info being discarded, so maybe that can be reincorporated. But everything else, especially info outside of ''Smash Bros.'', would be retained.) For example, in my ''Zelda'' draft, [[User:Nintendo101/community garden#Ganon|Ganon]] is described under the "recurring crossover subject" section, and Ganondorf is mentioned in the relevant sections below where he shows up, like ''Super Mario Maker'', ''Mario Artist: Paint Studio'', ''Yoshi's Woolly World'', and the ''Super Smash Bros.'' series. That info is just being presented alongside other relevant ''Zelda'' info in those games and others, and I suspect that is the type of info someone searching for "Ganondorf" on the Super Mario Wiki would be interested in. How does that sound? What do you think of the draft? - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 21:16, March 4, 2025 (EST)
::::I suppose that works. So long as the content on the original pages is preserved (one way or another), I'm perfectly fine with this. Also, I think the draft looks amazing so far. There are a couple things missing of course (it is a draft, after all), but what is there is very well-detailed. {{User:Arend/sig}} 06:16, March 5, 2025 (EST)
So is the ultimate plan for these to effectively be a replacement for the Smash list pages? I imagine the lists would start looking a bit barren if things on them get moved to crossover franchise articles. {{User:Hewer/sig}} 16:07, March 4, 2025 (EST)
:I am admittedly not a fan of the fighter list articles on the wiki and I think the information on them would be better served in articles more directly focused on the ''Super Mario'' franchise, both for readers and editors. However, I respect the will of those who would rather we keep those articles around. I am not sure if you looked at my ''Zelda'' draft, but it does omit more granular information specific to the ''Super Smash Bros.'' series, like stickers, trophies, Classic Mode routes, special moves, or NIOLs for individual characters. I would rather this article emphasize how ''Zelda'' engages with ''Mario'' in other contexts. If folks would rather Super Mario Wiki continue to hold onto the more granular ''Smash Bros.'' info on the fighter list articles, they could be retained for those purposes, I imagine. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 16:47, March 4, 2025 (EST)
::Well, there are two voting options for people who want both. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 16:52, March 4, 2025 (EST)
::I find Classic Mode routes in particular a bit odd to remove since they often involve Mario characters/stages/etc. (and I guess a similar argument could possibly be made for stickers), but I understand for the stuff with no particular Mario relevance.<br>Another thing I just thought of: we already have [[Pushmo (series)]] and [[Just Dance (series)]] as guest appearances, and [[Talk:List of references in Nintendo video games#Split Animal Crossing|this proposal]] passed to make a page for the Animal Crossing series (technically the proposal was just to make a page on the game, but every single voter agreed to do a series page instead). Would this proposal affect these pages? {{User:Hewer/sig}} 18:44, March 4, 2025 (EST)
:::I had touched base with some of the users involved in those proposals. I do personally think it would make sense for all of these articles to have similar structure to one another - I think that uniformity would make them easier for readers to jump between them and find what they are looking for. However, maybe {{@|Kaptain Skurvy}}, {{@|Nelsonic}}, and {{@|Mushzoom}} can provide their two cents. Would you want the ''Pushmo'', ''Just Dance'', and ''Animal Crossing'' articles be grandfathered into this proposal? It would just provide some structural guidelines and inform how redirects and disambiguation pages relevant to these series would be handled on the wiki. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 20:01, March 4, 2025 (EST)
::::Yeah, it would make sense to apply this to those articles for consistency (and Pushmo technically crosses over in Smash as well, as a spirit). So a list of franchises to split could look something like:<br>Major non-Smash crossovers ("major" meaning "would take more than a couple of sentences to fully explain"): The Legend of Zelda, Animal Crossing, Splatoon, Sonic the Hedgehog, F-Zero, Dragon Quest, Final Fantasy, Pikmin, Punch-Out!!, {{iw|rhythmheaven|WarioWare (series)|Rhythm Heaven}}, Kirby, Metroid, Excitebike, Pushmo, Just Dance, EarthBound, Kid Icarus, Mega Man, Pac-Man, Banjo-Kazooie, maybe Star Fox, maybe Duck Hunt, maybe [[Balloon Fighter|Balloon Fight]], maybe [[Bubbles (Clu Clu Land)|Clu Clu Land]], maybe Fire Emblem, maybe Street Fighter, maybe Ice Climber, maybe Bayonetta?, not sure if "Game & Watch" really counts as a franchise, Minecraft technically counts but would [[Minecraft|probably be redundant to split]]<br>Minor non-Smash crossovers and/or appearances only as amiibo costumes: Pokémon, Wii Fit, Xenoblade Chronicles<br>Minor non-Smash crossovers: Metal Gear, Castlevania, Tekken<br>No non-Smash crossovers: Persona, Fatal Fury, ARMS, Kingdom Hearts<br>I probably missed something. I'm assuming that franchises whose only crossover is non-fighter representation in Smash (like a stage or Assist Trophy or something) don't count. {{User:Hewer/sig}} 05:29, March 5, 2025 (EST)
::::Forgot about [[Starfy|The Legendary Starfy]], that would qualify. There's also [[I Choose You!]] from Mario Maker, which might barely push Pokémon up to "major". {{User:Hewer/sig}} 07:13, March 5, 2025 (EST)
::::{{@|Nintendo101}} I'm fine with that. [[User:Mushzoom|Mushzoom]] ([[User talk:Mushzoom|talk]]) 02:30, March 16, 2025 (EDT)
:{{@|Nintendo101}} Yes. This makes perfect sense, and the grandfathering approach would allow these series to get more mainstream attention, which is never a bad thing. New series with a significant amount of ''Super Mario'' content would also likely be considered for a crossover article as opposed to being relegated to the [[list of references in Nintendo video games]] or the [[list of references in third-party video games]]. Being placed on said lists works for games with small amounts of ''Super Mario'' content (i.e. ''{{wp|Drill Dozer}}'' or ''{{wp|Borderlands 2}}''), but doesn't for games with larger amounts of ''Super Mario'' content (i.e. [[Punch-Out!! (Wii)|''Punch-Out!!'']] or ''[[Mobile Golf]]'').  [[User:Nelsonic|Nelsonic]] ([[User talk:Nelsonic|talk]]) 11:31, March 5, 2025 (EST)


====Commesents====
This is probably a separate proposal, but should the ''Link's Awakening'' article be outright merged with the new crossover one? [[User:LinkTheLefty|LinkTheLefty]] ([[User talk:LinkTheLefty|talk]]) 07:14, March 6, 2025 (EST)
[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)
:Not an invalid idea, but I agree that is better the focus of a future proposal. This one does not address non-list articles. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 20:35, March 7, 2025 (EST)
: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)


{{@|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)
===Add headings for first topics of talk pages that lack one===
{{early notice|March 17, 2025}}
When users create a talk page, they don't always create a heading for their first topic. As a consequence, talk pages sometimes start with a discussion, then there's the table of contents (TOC) and then the remaining topics. For instance, this is the case for [[Gallery talk:Donkey Kong Card Game (trading cards)]].
It is ugly and inelegant, and it's even worse on mobile because this initial topic takes up a lot of vertical space and never gets collapsed; it is quite a pain having to scroll down an entire discussion just to access the TOC that lists the other topics.


{{@|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)
To solve this problem, I propose to add a heading at the top of the first topic of a talk page if it does not have one.
: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)
That way, the TOC will be at the top of the page (as it should be) and the first topic will be listed along with the other topics instead of being separated from them.


===Stop considering reused voice clips as references (usually)===
The title of the new headings could be "(First topic)", enclosed in parentheses to indicate that this was not a heading from the original poster; the heading title is open for discussion.
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.
If this proposal passes, [https://www.mariowiki.com/index.php?title=Gallery_talk:Donkey_Kong_Card_Game_(trading_cards)&oldid=4730155 the aforementioned page] would look [https://www.mariowiki.com/index.php?title=User:Jdtendo/Bacassab&oldid=4776920 like this].


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.
'''Proposer''': {{User|Jdtendo}}<br>
*''[[Super Mario Strikers]]'': Some of Hammer Bro's voice clips are reused from this game.
'''Deadline''': March 24, 2025, 23:59 GMT
*''[[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.
====Support: add a heading to first topic if it lacks one====
 
#{{User|Jdtendo}} Per proposal
'''Proposer''': {{User|Waluigi Time}}<br>
#{{User|Technetium}} Good idea
'''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|Sparks}} Per all.
#{{User|LadySophie17}} ''[[Donkey Kong (game)|Donkey Kong]]'': Mario's mustache is reused from this game.
#{{User|Pseudo}} Seems useful for navigation!
#{{User|TheFlameChomp}} Per all.
#{{User|Camwoodstock}} Works for us, and would make it marginally easier to tell when a talk page should be split. Per proposal.
#{{User|Nintendo101}} Repurposing an asset — voice clip or otherwise — is rarely a reference in isolation.
#{{User|EvieMaybe}} per all! very good idea
#{{user|Doc von Schmeltwick}} - I ''swear'' this has already been proposed and passed....
#{{User|LadySophie17}} per all. That has always bothered me.
#{{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|Ahemtoday}} Very good to establish consistency.
#{{User|Shadow2}} Per all.
#{{User|Nelsonic}} 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|Rykitu}} Per all. Finally consistency.
#{{User|EvieMaybe}} per all
#{{User|Killer Moth}} Per all.
#{{User|DesaMatt}} per all.
#{{User|Weegie baby}} The fact there are no headings on the first topics of talk pages annoys me so much 😤
#{{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}} Consistency is good.
#{{User|ThePowerPlayer}} ThePowerPlayer's "Per all" vote is reused.
#{{User|Cadrega86}}, the same also goes for generic artwork (so unless it's specifically stylized or features stuff specific to a single game/subseries). These are not references but just "lazy" asset re-usage.
#{{User|Technetium}} Per all.
#{{User|Jdtendo}} Per all.
#{{User|Ray Trace}} Grunts, screams, and whoohoos aren't uttered with a specific game in mind and our articles shouldn't reflect that.
#{{User|Scrooge200}} This has been bugging me for a while. This is just asset reuse to save budget and because there's very few specific lines that need to be newly recorded.
#{{User|Mario}} Just because it was first heard in a game doesn't mean it was recorded for this game. It might be a stock sound that went unused and eventually found its way into a future game. Additionally there are clips that are better known in other games than the one it originated in. "That's-a so nice!" Is commonly heard when Mario clears a level in New Super Mario Bros., but this quote is first heard in Mario Kart Double Dash, barely audible in the Awards Ceremony. Unless the clip itself is made specifically for a game (Mario vs. Donkey Kong!!! Finding its way in a Mario Kart game as a store speaker or something) it's best not to list as a reference. That being said, there should be ways to list if voices have been reused.
#{{User|Tails777}} This is on par with referencing ''Super Mario Galaxy'' every time Rosalina appears. Pretty sure we had a proposal at some point opting to exclude these types of recurring things from the references section and this is just following in suit. Per proposal.
 
====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)


====Oppose: don't add headings to topics====


===Encourage game-related "icon"-type images to have consistent file dimensions with each other when applicable to their origins===
====Comments (first topic heading)====


[[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:
===Give ''Taiko no Tatsujin'' an article===
;this looks good:
''Taiko no Tatsujin'' has had numerous crossovers with the ''Mario'' franchise throughout its history. This extends to not only the songs being playable, but actual ''Mario'' characters showing up and being animated in the accompanying videos in the earlier games.
<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:
*The DS version has "Super Mario Bros." as a track, [https://www.youtube.com/watch?v=870WLPGnnKs using imagery from the games].
<gallery heights=72 widths=72>
*The Wii version includes "New Super Mario Bros. Wii Medley." and "[https://www.youtube.com/watch?v=RkcrnhCfrtw Super Mario Bros.]" Notably, the videos include [https://www.youtube.com/watch?v=zO31iswKX84 actual characters and imagery from the game showing up]. The former has nearly every enemy from the original ''Super Mario Bros.''
MarioMPT.png
*''Taiko no Tatsujin Wii U Version!'' has "[[Fever]]" from ''[[Dr. Mario]]''. There are also Mario and Luigi costumes for Don-chan and Katsu-chan.
Luigi MPT.png
*''Nintendo Switch Version!'' has "[[Jump Up, Super Star!]]" from ''[[Super Mario Odyssey]]''.
Shy Guy MPT.png
*The 2020 version brings back "Super Mario Bros." and "Jump Up, Super Star!", also including a "Famicom Medley" track using "Fever" from ''Dr. Mario''. These tracks are present in many of the arcade versions. Playing "Super Mario Bros." will have mushrooms and [[Super Star]]s appear [https://www.youtube.com/watch?v=8jxXo0oHzZg when notes are hit].
Peach MPT.png
*''Blue Version'' has [[Cappy]] has an equippable hat.
Yoshi MPT.png
*''Rhythm Festival'' has a medley of music from ''Super Mario Bros.'', re-used from earlier games.
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.
''Mario'' has paid it back with the serial-numbers-filed-off ''[[Donkey Konga]]'' and [[Don-chan]] being a playable character in ''[[Mario Kart Arcade GP DX]]''. Since there's overlap between the franchises, and they've had a decent history together, I think ''Taiko'' is deserving of its own article to cover all this in one place.


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.
'''Proposer''': {{User|Scrooge200}}<br>
'''Deadline''': March 30, 2025, 23:59 GMT


'''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.
====Support (Bring Us One Degree of Separation Closer to Jimmy Neutron)====
#{{User|Scrooge200}} Per proposal.
#{{User|Camwoodstock}} Makes sense to us; with how many cross references there are both ways, it seems only fair.
#{{User|Hewer}} This should probably be cancelled given the crossover article proposal but I'll support just in case. I previously wasn't sure whether it would get a page under that proposal because the only crossover I knew about was Don-chan being in Mario Kart (and his tiny Smash representation in one of Pac-Man's taunts), but all of this other stuff seems very comparable to what got [[Just Dance (series)]] a page. Now we just need to figure out whether [[Mametchi|Tamagotchi]] gets one...
#{{User|Killer Moth}} Per proposal.


'''Proposer''': {{User|Doc von Schmeltwick}}<br>
====Oppose (No More Megalovania, Please)====
'''Deadline''': November 11, 2024, 23:59 GMT


====Support - consistent icons====
====Comments' Perfect Math Class====
#{{user|Doc von Schmeltwick}} - ''Icon'' haz dead, never-funny-in-the-first-place memes about fast food sandwiches?
{{@|Scrooge200}}, have you considered waiting until the proposal [[#Introducing the crossover article|immediately above]] is finished? You would not need to raise proposal for ''Taiko no Tatsujin'' at all if it were to be pass. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 15:23, March 16, 2025 (EDT)
#{{user|Super Mario RPG}} - Accurate to how the graphic or texture is stored in game.
:Oh, I noticed that, but figured it was more for just ''Zelda''. I'm glad to see we're finally making it out of the Stone Age with our crossover coverage, though. {{User:Scrooge200/sig}} 15:27, March 16, 2025 (EDT)
 
::''Zelda'' is just the example I worked with. The proposal itself applies to all manner of crossover. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 15:30, March 16, 2025 (EDT)
====Oppose - who needs consistency?====
::{{@|Scrooge200}} By "stone age" I assume you mean it's one of the last steps to becoming a wiki centered completely on ''Super Mario''. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 15:38, March 16, 2025 (EDT)
#{{User|Waluigi Time}} Rawsize exists.
#{{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.
 
====Comments====
{{@|Waluigi Time}} - Rawsize doesn't help for tabular data. Only for galleries. Only way to get it there would be to separately size each cell, and even that doesn't keep them in the correct position within the cell. Wouldn't it be more pragmatic to just have the images at the correct size rather than having to mess with the HTML each time? And we do indeed use these for tabular data, like ghost times, tennis rivals, that sort of thing. [[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)


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

Latest revision as of 09:46, March 17, 2025

Image used as a banner for the Proposals page
Current time:
Monday, March 17th, 13:46 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."

Poll proposal formatting

As an alternative to the basic proposal format, users may choose to create a poll proposal when one larger issue can be broken down into multiple sub-issues that can be resolved independently of each other. In a poll proposal, each option is essentially its own mini-proposal with a deadline and Support/Oppose subheadings. The rules above apply to each option as if it were a its a two-option proposal: users may vote Support or Oppose on any number of options they wish, and individual options may close early or be extended separately from the rest. If an option fails to achieve quorum or reach a consensus after three extensions, then the status quo wins for that option by default. A poll proposal closes after all of its options have been settled, and no action is taken until then. If all options fail, then nothing will be done.

To create a poll proposal, copy and paste the formatting below to get started; your username and the option deadlines 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]". 

===[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}}}}

====[option title (e.g. Option 1)]: [brief summary of option]====
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT

;Support
#{{User|{{subst:REVISIONUSER}}}} Per proposal.

;Oppose

====[option title (e.g. Option 2)]: [brief summary of option]====
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT

;Support
#{{User|{{subst:REVISIONUSER}}}} Per proposal.

;Oppose

====[option title (e.g. Option 3)]: [brief summary of option]====
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT

;Support
#{{User|{{subst:REVISIONUSER}}}} Per proposal.

;Oppose

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

A poll proposal is archived after all of its options have settled, and it is listed as one single proposal in the archive. It is considered to have "passed" if one or more options were approved by voters (resulting in a change from the status quo), and it is considered to have "failed" if all options were rejected by voters and no change in the status quo was made.

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)
Use the classic and classic link templates when discussing classic courses in Mario Kart Tour, YoYo (ended October 2, 2024)
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)
Split Mario & Luigi badges and remaining accessories, Camwoodstock (ended February 1, 2025)
Merge Chef Torte and Apprentice (Torte), Camwoodstock (ended February 3, 2025)
Merge intro/outro sections, rename Gameplay section to "Overview" for Mario Party minigame articles, ToxBoxity64 (ended March 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)
Merge False Character and Fighting Polygon/Wireframe/Alloy/Mii Teams into List of Super Smash Bros. series bosses, Doc von Schmeltwick (ended December 2, 2024)
Merge Wiggler Family to Dimble Wood, Camwoodstock (ended January 11, 2025)
Create a catch-all Poltergust article, Blinker (ended January 21, 2025)
Give the Cluck-A-Pop Prizes articles, Camwoodstock (ended January 31, 2025)
Reverse the proposal to trim White Shy Guy, Waluigi Time (ended February 8, 2025)
Split Animal Crossing (game), Kaptain Skurvy (ended February 12, 2025)
Split the modes in the Battles page, Mario (ended February 15, 2025)
Count ongoing serialized comics for latest appearances, Rykitu (ended March 2, 2025)
Split Toad wearing headphones off from Jammin' Toad, PrincessPeachFan (ended March 7, 2025)
Split Super Mario Maker helmets from Buzzy Shell and Spiny Shell (red), PopitTart (ended March 12, 2025)

Writing guidelines

None at the moment.

New features

Establish a format for poll proposals on the archive lists

Something that's slipped through the cracks when we invented poll proposals was what we do when we add them to these pages. We can't simply have one link to the poll proposal — the entire purpose of the format is that different parts of it can pass and fail independently of one another. What color do we put a proposal where one thing fails and another thing succeeds in?

I have several pitches for you.

OPTION ZERO
Do nothing. I'm putting this at the front because I want to leave room for any good-sounding solutions beyond the four I'm about to suggest. It's here on the proposal at all because I'm pretty sure I'm legally obligated to put it here, but I'll be honest — I'm not entirely sure what this winning would... mean. Our hand will eventually be forced when our first poll proposal fully resolves, so a format will be established one way or the other.

EDIT: It has been helpfully pointed out that there is a current policy — they are red if they all issues fail, gray if at least one passes and is unimplemented, and green if at least one passes and all issues are implemented. A "one issue changes the color" kind of rule. It's definitely not insensible, but I feel that we could be conveying more information. Still, even if this if the "fail option", we have a policy now, so I got what I wanted even if this one wins.

OPTION ONE
The different issues of a poll proposal share a number corresponding to when the first issue closes. They're listed separately, and distinguished from each other via letters. As an example, the three parts of the Brown Yoshi proposal would slot in at #83A, #83B, and #83C. (That would shove some other proposals down; we could also just append them to the end of the list like normal and brush off the inconsistency if y'all prefer.)

The Brown Yoshi proposal is also a handy demonstration of an edge case we have to contend with — if this proposal passed right now, we would list #83A as red and #83B as gray, but what would happen with #83C, which is still ongoing? This is the aspect on which Options One and Two differ. In Option One, issues are not added to the archive page until they close. The page would only contain #83A and #83B if the proposal passed right now, with #83C being added later

I would like to note that the Brown Yoshi proposal is a remarkably well-behaved example. If the issues were ordered differently, we may at one point have #83A and #83C on the list with no #83B until later.

OPTION TWO
Option Two is identical to Option One except in how it handles open issues on partially closed poll proposals. In this option, they are added to the list alongside the other issues, and marked with a new color — let's say black.

This prevents the awkward gaps we would be susceptible to in Option One, but it is introducing a whole color for a temporary edge case.

OPTION THREE
Option Three is simpler. We create a new color in the archive for poll proposals — I guess let's say black again. Poll proposals get added to the archive when all issues on them are closed.

This saves space (the other options will have to give fourteen entries to this proposal, but it means the entry on the list doesn't reflect anything about any individual issue's status, such as whether it's been implemented or not.

EDIT: Camwoodstock's pitch below of using three colors (and, implicitly, adding the poll proposal to the archive when it has any closed issues) doesn't entirely eliminate that negative, but it does seem much more useful than just having the one color.

OPTION FOUR
Option Four is simpler still. Each issue is treated as if it were an entirely separate proposal. Each gets numbered and appended to the list when it closes regardless of what anything else in the poll proposal is up to.

The negative of this way of doing it is that the issues of a poll proposal may end up strewn about the list in a way that doesn't really reflect that they're a related thing.

Proposer: Ahemtoday (talk)
Deadline: March 18, 2025, 23:59 GMT

Option Zero

  1. Jdtendo (talk) Per Porple "Steve" Montage in the comments.
  2. Waluigi Time (talk) Per Porple.
  3. EvieMaybe (talk) perple montage
  4. Camwoodstock (talk) Per Porple in the comments, though admittedly this is more of a secondary option to our more robust version of Option Three we pitched. Status quo isn't the worst thing in the world, and we do acknowledge our more robust solution of "dark colors" may be a bit harder to convey as we've been slowly rolling out... Well, a dark mode for the whole wiki. (If it was down to us, the poll proposals would use lighter colors in dark mode, before you ask; of course, if that option somehow wins, we'd be down to help fine-tune it.)
  5. Arend (talk) Per Porple.
  6. Nintendo101 (talk) Per porplemontage.
  7. Salmancer (talk) Oh, huh. I suppose this is a solved problem then.

Option One

  1. Ahemtoday (talk) It's either this or Option Two for me — it's important to me that the issues end up next to each other on the archive and that the status of each one is visible on the page.
  2. Salmancer (talk) There's no rule saying a poll proposal has to be for small things, since part of the premise was reducing the need for large numbers of combination options. There could be poll proposals that have wide scopes, and as such I think we're going to have to stomach the poll proposals with 10+ proposals in them to make it easier to track policy without thumbing through old proposal pages. Also an archive is for the past, not the present.

Option Two

  1. Ahemtoday (talk) See my note about Option One.
  2. Camwoodstock (talk) Secondary option, but we do think darker shades of the colors (a-la our pitch for Option Three) would be nice. Helps distinguish at a glance what was a poll proposal.

Option Three

  1. Camwoodstock (talk) We would like to pitch a more sophisticated variant of this; 3 new colors. One for a poll that has concluded, one for one that's partially ongoing, and one for a poll that has been partially overturned by a future proposal. Maybe dark green, dark gray/maybe a de-saturated dark green a-la the Shroom Spotlight template, and a dark yellow? The darker colors, of course, to contrast with the non-poll proposals. (On dark mode, we'd probably make these lighter, rather than darker, provided we actually even add dark mode compatibility to the proposal archive colors.)
  2. Rykitu (talk) Per all.
  3. Ahemtoday (talk) I definitely see the appeal in having poll proposals under a singular listing, but I think they'd be better served by having one or multiple new colors rather than using the standard red and green.

#Jdtendo (talk) Listing every single poll would probably take a lot of space whereas the whole purpose of a poll proposal is bringing together many similar polls that would be too cumbersome to handle separately. I would prefer having a single proposal listed as "Determine what memes should be on the Internet references page" that users can click on to check the detailed results rather than cluttering the list with a dozen links.

Option Four

Comments

@Camwoodstock — I definitely think your pitch for Option Three is better than the version I was suggesting. I'm not really sure about the pitch for Option Two, though — the letters already distinguish them, and I feel like they'd seem more like separate states rather than a "modifier" on some of the existing ones. Not to mention, wouldn't we need a darker version of every single color just in case? That's a lot of changes to make, and we'd end up running into problems with dark blue, teal, and dark teal; or "dark white", gray, and dark gray. Ahemtoday (talk) 03:20, March 4, 2025 (EST)

I don't quite understand option one and two, as the above rules for poll proposals state "A poll proposal closes after all of its options have been settled, and no action is taken until then. If all options fail, then nothing will be done." --PopitTart (talk) 07:09, March 4, 2025 (EST)

Could you explain the contradiction in greater detail? I don't see what you mean. Ahemtoday (talk) 12:01, March 4, 2025 (EST)
The options say "The page would only contain #83A and #83B if the proposal passed right now, with #83C being added later" and "...how it handles open issues on partially closed poll proposals" there shouldn't be any instances of archiving partially closed poll proposals, they only close all at once when every entry has been resolved.--PopitTart (talk) 20:07, March 4, 2025 (EST)
So is your position that we should use the lettering scheme from Options One and Two, but only add poll proposals to the archive page when all of their issues are closed? I don't think I agree, but I can add that as Option Five if that's what you want to vote for. Ahemtoday (talk) 22:48, March 4, 2025 (EST)

I feel like this is fine. Either it's red (no change from the status quo so nothing needs to be done), gray (some change was established and there is work to do), or green (some change was established and it's all done). There are other proposals where people list several things to be done, it's not that different, it's just that now we have the ability to vote on each individual thing. But in either case you just click the link to read exactly what was approved. --Steve (talk) Get Firefox 10:56, March 7, 2025 (EST)

Removals

None at the moment.

Changes

Introducing the crossover article

The passing of this proposal would accomplish seven things:

  1. See the publication of the drafted Zelda article discussed in this proposal, titled "crossovers with The Legend of Zelda." (The draft can be viewed here.)
  2. Funnel redirects and disambiguation pages pertaining to Zelda on the wiki to the published Zelda article (i.e., searches for The Legend of Zelda, Octoroks, etc. Fully covered crossover subjects like Link would keep their articles, and this would not preclude a crossover subject from receiving an article of their own in the future if warranted, such as the inclusion of Princess Zelda in a future Mario Tennis or something like that).
  3. Move details pertaining to Zelda from list articles on the site to this one (i.e. all information pertaining to Sheik on the list of fighters debuting in Super Smash Bros. Melee article would be cleared, and searching for "Sheik" on the site would bring you to this article. Zelda info on the list of references in Nintendo video games article would similarly be cleared. Visitors to that article would be directed towards the published Zelda one when they reach that section of the list article).
  4. Establish a navbox for crossover articles (either a wholly dedicated one, an incorporation into "Template:Culture," or a retooling of "Template:Crossover characters").
  5. Establish the precedent where this can be done for other IPs with which the Super Mario franchise has crossed-over.
  6. Establish a 'Crossover article" section to the MarioWiki:Manual of Style that explains the framework for crossover articles described below. This is to be the standard structure for how other articles are to be structured.
  7. Note that this framework exists on the the crossover section of our coverage policy, and provide a link directing readers to it.

The Super Mario franchise is very much the IP tentpole for Nintendo Co., Ltd. and at least one of the ones for the Japanese video game industry as a whole. Consequently, Super Mario as a franchise and brand has crossed-over with many other franchises, brands, and series over its nearly fifty years of existence - not only sister series developed by Nintendo EAD and R&D, and their successor EPD (i.e. Duck Hunt, Punch-Out!!, Exictebike, Metroid, F-ZERO, Animal Crossing, Pikmin, Splatoon, etc.) and those of their external creative partners (i.e. Ape Inc.'s EarthBound, HAL Laboratory's Kirby, Game Freak's Pokémon, etc.), but also fellow ones from other studios like Square Enix, Sega, Bandai Namco, Koei Tecmo, Chunsoft, Ubisoft, Konami, and Hudson Soft. This is not groundbreaking news: Most folks interested in gaming history already know this, especially the curators of the Super Mario Wiki. However, I do not feel like we handle this information particularly well on the site.

A lot of coverage of Super Mario references, homages, allusions, and cameos are nestled within various list articles, inexplicitly at the end of dedicated game articles, or in Super Smash Bros. articles with which there seemed to have been effort to bury on the site and are not wholly about Super Smash Bros. anyways. This coverage, exasperated by recent efforts to reduce coverage on the Super Smash Bros. series: (1.) obfuscates the fact that Super Mario has made references and is referenced in many other franchises outside of Smash Bros. contexts, often in very meaningful ways that are interesting and fun to read about; (2.) mitigates how Mario has been an influence behind some of these other franchises; and (3.) makes finding some bits of information just very difficult. If I, as a visitor of the site, wanted to understand scenarios where Splatoon and Mario have crossed-over, I would not have an easy way to find that all in one place, and I think that is a shame.

frog man!
green lad!

To better cover and consolidate crossover info on the site, I have been drafting what I would like to call a "crossover article" using The Legend of Zelda franchise as an example (with contributions from Salmancer, DryBonesBandit, Memelord2020, RHG1951, LeftyGreenMario, and LadySophie17, and feedback from Super Mario RPG, Doc von Schmeltwick, and Koopa con Carne). This is a long article, and it is not wholly completed yet, but I think it is serviceable example of what I would like us to do going forward. Crossover articles take inspiration from the universe articles from our affiliate Smash Wiki and, as apparent in the Zelda draft, consist of the following sections:

  • Overview : A brief description of what the crossover franchise/series is for those not well versed in the subject and would like to know a little more about it without visiting another site, and how this relates to Mario. It is the create a foundation so the reader is not confused by descriptions or terminology in the other areas of the article. For Zelda, this section may be a bit lengthier than it would be for others because Mario had a lot of direct influence on Zelda as a series.
  • Recurring crossover subjects: for subjects like characters, enemies, bosses, or items that make substantial appearances in or alongside Mario-related media, such as subjects that used to have their own articles on the site. Each subject would be briefly explained so readers understand who they are when mentioned in other parts of the article, have explicit conceptual or design connections with Mario highlighted, and summarize areas where they specifically crossover with Mario.
  • History in the Super Mario franchise: a history section for where the crossover subject is referenced in the Super Mario franchise itself.
  • History in the subject series/franchise: a history section for the inverse, where Super Mario is referenced in the franchise subject of the article. In this case, it is Zelda.
  • Shared history (if applicable): a history section for mutual space where both subjects appear, such as the Super Smash Bros. series, Tetris series, NES Remix series, or other media.

Zelda is uniquely related to Mario and nearly as old, but crossover articles can be written for smaller franchises/series as well. The only requirement for a series/franchise to receive an article of its own is for it to directly crossover with Super Mario within an officially licensed capacity. Articles of this nature should not be written for series/franchise that simply make homages to Super Mario or have elements inspired by it, such as Celeste, Gears of War, or Astro Bot.

I offer three options:

  1. Support: I like the idea of crossover articles and want to see them implemented as described.
  2. Support: I like the idea of crossover articles, but list articles for the Super Smash Bros. series should be left alone.
  3. Oppose: I do not like the idea of the crossover article and do not want to see them implemented.

I know this was a long one, folks. Sorry about that, but the ideas behind this idea are multifaceted. Please let me know if you need additional clarity on anything or if you have any recommended amendments. (Also, if you would like, I welcome you to contribute to the drafted Zelda article! It is in my "community garden" sandbox for a reason.)

Proposer: Nintendo101 (talk)
Deadline: March 17, 2025, 23:59 GMT

Support: let's implement crossover articles!

  1. Nintendo101 (talk) Link costume pose in Super Mario Maker
  2. Super Mario RPG (talk) Per proposer.
  3. Koopa con Carne (talk) Per proposal with absolutely no second thought. Aside from the obvious value such articles would bring, this practice may incidentally just be the silver bullet for the community's differences on how to cover Smash Bros. content. Nintendo101, even with your inspiration from SmashWiki, I'd say you still managed to think out of the box here.
  4. Waluigi Time (talk) Per all.
  5. EvieMaybe (talk) been waiting a long time for this one. per proposal!
  6. LadySophie17 (talk) Secondary choice, I suppose. Better than no article.
  7. Camwoodstock (talk) Secondary option; we'd rather these articles exist, even if the Smash coverage is confusing, than these articles not exist at all.
  8. PopitTart (talk) It has always felt absurd to me that Captain Olimar's presence on the wiki is entirely an entry in List of fighters debuting in Super Smash Bros. Brawl, despite being directly based on Mario himself and having appearances in Luigi's Mansion, WarioWare: D.I.Y., Super Mario Maker, Yoshi's Woolly World, Mario Kart 8, and WarioWare Move It!
  9. Jdtendo (talk) Crossover articles are a great idea, and if it can also declutter Smash Bros. list articles, it's even better.
  10. Arend (talk) As long as the content from the list pages are preserved in SOME way or another, I am perfectly fine with this. I think this is a great idea, and the well-detailed draft really sold me on this.
  11. Nelsonic (talk) Makes perfect sense.
  12. Kaptain Skurvy (talk) Sounds good to me.
  13. Shy Guy on Wheels (talk) Per all. death to the smash bros lists
  14. Mario (talk) Those list pages are a spaghetti of sadness, mama mia. I love the idea of these crossover pages, wonderful idea (similar to those decade splits for the gallery pages), and they're going to be a massive step up from that mess we currently have. I don't want to keep those lists at all. Their tolerated existence makes our wiki look bad, although absolutely delicious, if you ask me.
  15. OmegaRuby (talk) The list pages are an abhorrent sight and I'd much rather have Smash information contained in these respective crossover articles - if that proves too large for the size of the existing article, then the next logical step would be a subpage for Smash Bros. information, would it not? Per all.
  16. Pseudo (talk) I love how you've put this together, Nintendo101 and other contributors! This seems like a very valuable addition to the wiki.
  17. SolemnStormcloud (talk) Per all.
  18. Mushzoom (talk) Per proposal.
  19. TheFlameChomp (talk) Per all.

Support: let's implement crossover articles, but leave Smash Bros. lists alone

  1. LadySophie17 (talk) Per proposal. I believe the articles would be better focused on the relationship between their respective series and Mario. Detailing all their character's Smash histories (which could get quite lengthy with something like Pokémon) would be better left in the List articles they currently are in.
  2. Sparks (talk) Per Sophie.
  3. Doc von Schmeltwick (talk) - Per Soph
  4. Camwoodstock (talk) Primary option; per Sophie, we worry about the length of some Smash sections, and we feel the organization is fine enough as it is right now for Smash-related subjects.
  5. Tails777 (talk) Per Sophie. I fully agree with making crossover articles to cover the relations another franchise has with Mario, but Smash in of itself is also a crossover and covering the details of these characters in a place that relates to Smash feels better.
  6. Arend (talk) Second option. I'm personally not a huge fan of loss of content, and this option allows this to be fully preserved by leaving it be. While I have been assured that the history sections will be preserved in a form better suited for the article and other details such as Classic Mode routes and stickers/trophies/spirits might be reimplemented, I'm still keeping this as a secondary option to be safe.
  7. Okapii (talk) Per Sophie.
  8. Nelsonic (talk) Second opinion.
  9. LinkTheLefty (talk) This proposal is pretty close to how I imagined covering Zelda subjects had Link's Awakening failed!
  10. Killer Moth (talk) Per all.
  11. Salmancer (talk) Hmm, so I'm going to do this because technically each of a character's special moves gets a sentence to itself on their article/Smash list entry and those just aren't going to fit in a crossover article
  12. Pseudo (talk) Secondary choice.
  13. Weegie baby (talk) Yes.

Oppose: let's not implement crossover articles

Crossover comments

I also happened to start a draft for a Pikmin series article the other day, inspired by Nintendo101's Zelda draft. It's in a much... much rougher state, but I hope it gives an idea what these crossover articles can provide.--PopitTart (talk) 19:31, March 3, 2025 (EST)

@Koopa con Carne thank you for the kind words! - Nintendo101 (talk) 20:30, March 3, 2025 (EST)

Link -- KOOPA CON CARNE 11:32, March 4, 2025 (EST)

Question: One of the proposed points is to "Move details pertaining to Zelda from list articles on the site to this one", but the i.e. states that "all information pertaining to Sheik on the list of fighters debuting in Super Smash Bros. Melee article would be cleared". Characters on these fighter lists have extensive history sections; will these be moved to the crossover pages as well, or will these be nixed altogether?
Also, what about franchises which currently only have a connection with Mario through Smash Bros., such as ARMS? Will these get a crossover article as well or not? ArendLogoTransparent.pngrend (talk) (edits) 12:10, March 4, 2025 (EST)

I don't know. Perhaps we'll cross that bridge when we get there. Ultimately, very few of the franchises within Smash Bros. have only crossed-over with Mario within Smash Bros., and that was at the front of my mind for this proposal. ARMS is one of the few exceptions. I should probably make some sort of list to parse what other series and franchises are within that boat. But what would you want to see, @Arend? - Nintendo101 (talk) 15:52, March 4, 2025 (EST)
I don't know... I'd understand not giving those an article given how they only crossover in Smash, but it would be strange to do with ARMS considering it's probably the only franchise with such a distinction that is directly from Nintendo. I can see us making an exception and allowing a crossover article for ARMS regardless, considering how most of the ARMS development team is basically Mario Kart 8 alumni anyway, but that same excuse probably wouldn't work with Kingdom Hearts. Then again, maybe so few franchises would be left that we might as well make crossover pages for those anyway.
Anyway @Nintendo101, you didn't answer my first question regarding the fighters' history sections on the fighter lists, so I ask again: would they be moved to the crossover pages as well, or be deleted altogether and not being covered at all? Knowing precisely what's going to happen to those (as the proposal hasn't really elaborated well on what will happen to those) is pivotal for me to pick which option to choose for, you see. That's kind of why I haven't voted yet. ArendLogoTransparent.pngrend (talk) (edits) 20:07, March 4, 2025 (EST)
I personally envisioned the history sections for each fighter being disseminated within history sections as described in this proposal (one section for Mario, one section for the other franchise, and one section for mutual space where both franchises crossover together). Individual characters would not have the full history sections as present in those list articles, but the individual info would largely be preserved. (I did not think it was important to reiterate granular Smash Bros. info about Stickers, Trophies, Classic Mode routes, etc. because that seemed more about Zelda in Smash Bros. and less about Zelda with Mario in Smash Bros., but Hewer had reservations on that info being discarded, so maybe that can be reincorporated. But everything else, especially info outside of Smash Bros., would be retained.) For example, in my Zelda draft, Ganon is described under the "recurring crossover subject" section, and Ganondorf is mentioned in the relevant sections below where he shows up, like Super Mario Maker, Mario Artist: Paint Studio, Yoshi's Woolly World, and the Super Smash Bros. series. That info is just being presented alongside other relevant Zelda info in those games and others, and I suspect that is the type of info someone searching for "Ganondorf" on the Super Mario Wiki would be interested in. How does that sound? What do you think of the draft? - Nintendo101 (talk) 21:16, March 4, 2025 (EST)
I suppose that works. So long as the content on the original pages is preserved (one way or another), I'm perfectly fine with this. Also, I think the draft looks amazing so far. There are a couple things missing of course (it is a draft, after all), but what is there is very well-detailed. ArendLogoTransparent.pngrend (talk) (edits) 06:16, March 5, 2025 (EST)

So is the ultimate plan for these to effectively be a replacement for the Smash list pages? I imagine the lists would start looking a bit barren if things on them get moved to crossover franchise articles. Hewer A Hamburger in Super Smash Bros. Brawl. (talk · contributions · edit count) 16:07, March 4, 2025 (EST)

I am admittedly not a fan of the fighter list articles on the wiki and I think the information on them would be better served in articles more directly focused on the Super Mario franchise, both for readers and editors. However, I respect the will of those who would rather we keep those articles around. I am not sure if you looked at my Zelda draft, but it does omit more granular information specific to the Super Smash Bros. series, like stickers, trophies, Classic Mode routes, special moves, or NIOLs for individual characters. I would rather this article emphasize how Zelda engages with Mario in other contexts. If folks would rather Super Mario Wiki continue to hold onto the more granular Smash Bros. info on the fighter list articles, they could be retained for those purposes, I imagine. - Nintendo101 (talk) 16:47, March 4, 2025 (EST)
Well, there are two voting options for people who want both. Super Mario RPG (talk) 16:52, March 4, 2025 (EST)
I find Classic Mode routes in particular a bit odd to remove since they often involve Mario characters/stages/etc. (and I guess a similar argument could possibly be made for stickers), but I understand for the stuff with no particular Mario relevance.
Another thing I just thought of: we already have Pushmo (series) and Just Dance (series) as guest appearances, and this proposal passed to make a page for the Animal Crossing series (technically the proposal was just to make a page on the game, but every single voter agreed to do a series page instead). Would this proposal affect these pages? Hewer A Hamburger in Super Smash Bros. Brawl. (talk · contributions · edit count) 18:44, March 4, 2025 (EST)
I had touched base with some of the users involved in those proposals. I do personally think it would make sense for all of these articles to have similar structure to one another - I think that uniformity would make them easier for readers to jump between them and find what they are looking for. However, maybe @Kaptain Skurvy, @Nelsonic, and @Mushzoom can provide their two cents. Would you want the Pushmo, Just Dance, and Animal Crossing articles be grandfathered into this proposal? It would just provide some structural guidelines and inform how redirects and disambiguation pages relevant to these series would be handled on the wiki. - Nintendo101 (talk) 20:01, March 4, 2025 (EST)
Yeah, it would make sense to apply this to those articles for consistency (and Pushmo technically crosses over in Smash as well, as a spirit). So a list of franchises to split could look something like:
Major non-Smash crossovers ("major" meaning "would take more than a couple of sentences to fully explain"): The Legend of Zelda, Animal Crossing, Splatoon, Sonic the Hedgehog, F-Zero, Dragon Quest, Final Fantasy, Pikmin, Punch-Out!!, Rhythm Heaven, Kirby, Metroid, Excitebike, Pushmo, Just Dance, EarthBound, Kid Icarus, Mega Man, Pac-Man, Banjo-Kazooie, maybe Star Fox, maybe Duck Hunt, maybe Balloon Fight, maybe Clu Clu Land, maybe Fire Emblem, maybe Street Fighter, maybe Ice Climber, maybe Bayonetta?, not sure if "Game & Watch" really counts as a franchise, Minecraft technically counts but would probably be redundant to split
Minor non-Smash crossovers and/or appearances only as amiibo costumes: Pokémon, Wii Fit, Xenoblade Chronicles
Minor non-Smash crossovers: Metal Gear, Castlevania, Tekken
No non-Smash crossovers: Persona, Fatal Fury, ARMS, Kingdom Hearts
I probably missed something. I'm assuming that franchises whose only crossover is non-fighter representation in Smash (like a stage or Assist Trophy or something) don't count. Hewer A Hamburger in Super Smash Bros. Brawl. (talk · contributions · edit count) 05:29, March 5, 2025 (EST)
Forgot about The Legendary Starfy, that would qualify. There's also I Choose You! from Mario Maker, which might barely push Pokémon up to "major". Hewer A Hamburger in Super Smash Bros. Brawl. (talk · contributions · edit count) 07:13, March 5, 2025 (EST)
@Nintendo101 I'm fine with that. Mushzoom (talk) 02:30, March 16, 2025 (EDT)
@Nintendo101 Yes. This makes perfect sense, and the grandfathering approach would allow these series to get more mainstream attention, which is never a bad thing. New series with a significant amount of Super Mario content would also likely be considered for a crossover article as opposed to being relegated to the list of references in Nintendo video games or the list of references in third-party video games. Being placed on said lists works for games with small amounts of Super Mario content (i.e. Drill Dozer or Borderlands 2), but doesn't for games with larger amounts of Super Mario content (i.e. Punch-Out!! or Mobile Golf). Nelsonic (talk) 11:31, March 5, 2025 (EST)

This is probably a separate proposal, but should the Link's Awakening article be outright merged with the new crossover one? LinkTheLefty (talk) 07:14, March 6, 2025 (EST)

Not an invalid idea, but I agree that is better the focus of a future proposal. This one does not address non-list articles. - Nintendo101 (talk) 20:35, March 7, 2025 (EST)

Add headings for first topics of talk pages that lack one

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

When users create a talk page, they don't always create a heading for their first topic. As a consequence, talk pages sometimes start with a discussion, then there's the table of contents (TOC) and then the remaining topics. For instance, this is the case for Gallery talk:Donkey Kong Card Game (trading cards). It is ugly and inelegant, and it's even worse on mobile because this initial topic takes up a lot of vertical space and never gets collapsed; it is quite a pain having to scroll down an entire discussion just to access the TOC that lists the other topics.

To solve this problem, I propose to add a heading at the top of the first topic of a talk page if it does not have one. That way, the TOC will be at the top of the page (as it should be) and the first topic will be listed along with the other topics instead of being separated from them.

The title of the new headings could be "(First topic)", enclosed in parentheses to indicate that this was not a heading from the original poster; the heading title is open for discussion. If this proposal passes, the aforementioned page would look like this.

Proposer: Jdtendo (talk)
Deadline: March 24, 2025, 23:59 GMT

Support: add a heading to first topic if it lacks one

  1. Jdtendo (talk) Per proposal
  2. Technetium (talk) Good idea
  3. Sparks (talk) Per all.
  4. Pseudo (talk) Seems useful for navigation!
  5. Camwoodstock (talk) Works for us, and would make it marginally easier to tell when a talk page should be split. Per proposal.
  6. EvieMaybe (talk) per all! very good idea
  7. LadySophie17 (talk) per all. That has always bothered me.
  8. Ahemtoday (talk) Very good to establish consistency.
  9. Nelsonic (talk) Per all.
  10. Rykitu (talk) Per all. Finally consistency.
  11. Killer Moth (talk) Per all.
  12. Weegie baby (talk) The fact there are no headings on the first topics of talk pages annoys me so much 😤
  13. ThePowerPlayer (talk) Consistency is good.

Oppose: don't add headings to topics

Comments (first topic heading)

Give Taiko no Tatsujin an article

Taiko no Tatsujin has had numerous crossovers with the Mario franchise throughout its history. This extends to not only the songs being playable, but actual Mario characters showing up and being animated in the accompanying videos in the earlier games.

  • The DS version has "Super Mario Bros." as a track, using imagery from the games.
  • The Wii version includes "New Super Mario Bros. Wii Medley." and "Super Mario Bros." Notably, the videos include actual characters and imagery from the game showing up. The former has nearly every enemy from the original Super Mario Bros.
  • Taiko no Tatsujin Wii U Version! has "Fever" from Dr. Mario. There are also Mario and Luigi costumes for Don-chan and Katsu-chan.
  • Nintendo Switch Version! has "Jump Up, Super Star!" from Super Mario Odyssey.
  • The 2020 version brings back "Super Mario Bros." and "Jump Up, Super Star!", also including a "Famicom Medley" track using "Fever" from Dr. Mario. These tracks are present in many of the arcade versions. Playing "Super Mario Bros." will have mushrooms and Super Stars appear when notes are hit.
  • Blue Version has Cappy has an equippable hat.
  • Rhythm Festival has a medley of music from Super Mario Bros., re-used from earlier games.

Mario has paid it back with the serial-numbers-filed-off Donkey Konga and Don-chan being a playable character in Mario Kart Arcade GP DX. Since there's overlap between the franchises, and they've had a decent history together, I think Taiko is deserving of its own article to cover all this in one place.

Proposer: Scrooge200 (talk)
Deadline: March 30, 2025, 23:59 GMT

Support (Bring Us One Degree of Separation Closer to Jimmy Neutron)

  1. Scrooge200 (talk) Per proposal.
  2. Camwoodstock (talk) Makes sense to us; with how many cross references there are both ways, it seems only fair.
  3. Hewer (talk) This should probably be cancelled given the crossover article proposal but I'll support just in case. I previously wasn't sure whether it would get a page under that proposal because the only crossover I knew about was Don-chan being in Mario Kart (and his tiny Smash representation in one of Pac-Man's taunts), but all of this other stuff seems very comparable to what got Just Dance (series) a page. Now we just need to figure out whether Tamagotchi gets one...
  4. Killer Moth (talk) Per proposal.

Oppose (No More Megalovania, Please)

Comments' Perfect Math Class

@Scrooge200, have you considered waiting until the proposal immediately above is finished? You would not need to raise proposal for Taiko no Tatsujin at all if it were to be pass. - Nintendo101 (talk) 15:23, March 16, 2025 (EDT)

Oh, I noticed that, but figured it was more for just Zelda. I'm glad to see we're finally making it out of the Stone Age with our crossover coverage, though. Scrooge200 (talk) PMCS Mustard Cafe Sign.png 15:27, March 16, 2025 (EDT)
Zelda is just the example I worked with. The proposal itself applies to all manner of crossover. - Nintendo101 (talk) 15:30, March 16, 2025 (EDT)
@Scrooge200 By "stone age" I assume you mean it's one of the last steps to becoming a wiki centered completely on Super Mario. Super Mario RPG (talk) 15:38, March 16, 2025 (EDT)

Miscellaneous

None at the moment.

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