MarioWiki:Proposals

Current time: Friday, November 22nd, 02:47 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 one or two weeks. Any user can support or oppose, but must have a strong reason for doing so (not, e.g., "I like this idea!"). All proposals must be approved by a majority of voters, including proposals with more than two options. For past proposals, see the proposal archive and the talk page proposal archive.

A proposal section works like a discussion page: comments are brought up and replied to using indents (colons, such as : or ::::) and all edits are signed using the code {{User|User name}}.

How to

Rules

1. If users have an idea about improving the wiki or managing its community, but feel that they need community approval before acting upon that idea, they may make a proposal about it. They must have a strong argument supporting their idea and be willing to discuss it in detail with the other users, who will then vote about whether or not they think the idea should be used. Proposals should include links to all relevant pages and writing guidelines. Proposals must include a link to the draft page. Any pages that would be largely affected by the proposal should be marked with {{proposal notice}}.
2. Only autoconfirmed users may create or vote on proposals and talk page proposals. While only autoconfirmed users can comment on proposals, anyone is free to comment on talk page proposals.
3. Proposals end at the end of the day (23:59) two weeks after voting starts (all times GMT).
   • For example, if a proposal is added at any time on Monday, August 1, 2011, the voting starts immediately and the deadline is two weeks later on Monday, August 15, at 23:59 GMT.
4. 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 accepted (including "per" votes), but tangential comments, heavy sarcasm, and other misleading or irrelevant quips are just as invalid as providing no reason at all.
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 "(banned)" is added next to their name in the "Proposer:" line of the proposal, which runs until its deadline as normal. If the proposal passes, it falls to the supporters of the idea to enact any changes in a timely manner.
8. A proposal 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.
   • Use {{proposal check|early=yes}} to automate this calculation; see the template page for usage instructions and examples.
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 can only be re-proposed after four weeks (at the earliest).
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. If the wiki staff deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to remove it at any time.
16. 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.
17. 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.
18. Proposals cannot be made about promotions and demotions. Staff changes are discussed internally and handled by the bureaucrats.
19. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
20. Proposals must have a status quo option (e.g. Oppose, Do nothing) unless the status quo itself violates policy.

Basic proposal and support/oppose format

This is an example of what your proposal must look like, if you want it to be acknowledged. If you are inexperienced or unsure how to set up this format, simply copy the following and paste it into the fitting section. Then replace the [subject] - variables with information to customize your proposal, so it says what you wish. If you insert the information, be sure to replace the whole variable including the squared brackets, so "[insert info here]" becomes "This is the inserted information", not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but what each voting section is supporting must be clearly defined. Such options should also be kept to a minimum, and if something comes up in the comments, the proposal can be amended as necessary.

---

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

'''Proposer''': {{User|[enter your username here]}}<br>
'''Deadline''': [insert a deadline here, 14 days after the proposal was created, at 23:59 GMT, in the format: "November 22, 2024, 23:59 GMT"]

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

====Oppose====

====Comments====

---

Users will now be able to vote on your proposal, until the set deadline is reached. Remember, you are a user as well, so you can vote on your own proposal just like the others.

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

Talk page proposals

Proposals concerning a single page or a limited group of pages are held on the most relevant talk page regarding the matter. Proposals dealing with a large amount of splits, merges, or deletions across the wiki should still be held on this page.

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

Rules

1. All active talk page proposals must be listed below in chronological order (new proposals go at the bottom) using {{TPP discuss}}. Include a brief description of the proposal while also mentioning any pages affected by it, a link to the talk page housing the discussion, and the deadline. If the proposal involves a page that is not yet made, use {{fake link}} to communicate its title in the description. Linking to pages not directly involved in the talk page proposal is not recommended, as it clutters the list with unnecessary links. Place {{TPP}} under the section's header, and once the proposal is over, replace the template with {{settled TPP}}.
2. All rules for talk page proposals are the same as for proposals (see the "How to" section above), with the exceptions made by the additional rules below:
3. The talk page proposal must pertain to the subject page of the talk page it is posted on.
4. When a talk page proposal passes, it should be removed from this list and included in the list under the "Unimplemented proposals" section until the proposed changes have been enacted.

List of ongoing talk page proposals

• Decide whether to create articles for Ashita ni Nattara and Banana Tengoku and/or include them on List of Donkey Kong Country (television series) songs (discuss) Deadline: November 23, 2024, 23:59 GMT
• Determine how to handle the Tattle Log images from Paper Mario: The Thousand-Year Door (Nintendo Switch) (discuss) Deadline: November 30, 2024, 23:59 GMT
• Merge False Character and the Fighting Polygon/Wireframe/Alloy/Mii Teams to List of Super Smash Bros. series bosses (discuss) Deadline: December 2, 2024, 23:59 GMT

Unimplemented proposals

Proposals

Break alphabetical order in enemy lists to list enemy variants below their base form, EvieMaybe (ended May 21, 2024)

Standardize sectioning for Super Mario series game articles, Nintendo101 (ended July 3, 2024)

^ NOTE: Not yet integrated for the Super Mario Maker titles, Super Mario Run, and Super Mario Bros. Wonder.

Create new sections for gallery pages to cover "unused/pre-release/prototype/etc." graphics separate from the ones that appear in the finalized games, Doc von Schmeltwick (ended September 2, 2024)

Add film and television ratings to Template:Ratings, TheUndescribableGhost (ended October 1, 2024)

Use the classic and classic-link templates when discussing classic courses in Mario Kart Tour, YoYo (ended October 2, 2024)

Split articles for the alternate-named reskins from All Night Nippon: Super Mario Bros., Doc von Schmeltwick (ended October 3, 2024)

Clarify coverage of the Super Smash Bros. series, Doc von Schmeltwick (ended October 17, 2024)

Remove all subpage and redirect links from all navigational templates, JanMisali (ended October 31, 2024)

Prioritize MESEN/NEStopia palette for NES sprites and screenshots, Doc von Schmeltwick (ended November 3, 2024)

Stop considering reused voice clips as references (usually), Waluigi Time (ended November 8, 2024)

Allow English names from closed captions, Koopa con Carne (ended November 12, 2024)

^ NOTE: A number of names coming from closed captions are listed here.

Talk page proposals

Split all the clothing, Doc von Schmeltwick (ended September 12, 2021)

Split machine parts, Robo-Rabbit, and flag from Super Duel Mode, Doc von Schmeltwick (ended September 30, 2022)

Make bestiary list pages for the Minion Quest and Bowser Jr.'s Journey modes, Doc von Schmeltwick (ended January 11, 2024)

Allow separate articles for Diddy Kong Pilot (2003)'s subjects, Doc von Schmeltwick (ended August 3, 2024)

Split Banana Peel from Banana, Doc von Schmeltwick (ended September 18, 2024)

Merge Spiked Thwomp with Thwomp, Blinker (ended November 2, 2024)

Create articles for specified special buildings in Super Mario Run, Salmancer (ended November 15, 2024)

Expand and rename List of characters by game to List of characters by first appearance, Hewer (ended November 20, 2024)

Writing guidelines

Do not surround song titles with quotes

This is a change to this section of our Manual of Style. Currently, our policy is to surround song titles with quotation marks whenever they appear. However. We are a Mario wiki, and the Mario series overwhelmingly does not do this.

The comparison arises to italics, but I feel there's quite a difference between that (an effect applied to text) and the inclusion of punctuation marks, which are text in and of themselves. Not to mention, unlike italics, which would require special programming to implement, quote marks are supported by anything that supports English text, meaning it's not a question of technical limitations — every game that names its songs is perfectly capable of listing them inside quotation marks, and yet they make the choice not to.

As such, surrounding song titles in quotes is questionable as adherence to an unofficial naming scheme over the original one. Not to mention the effects this can have on lists of song titles — their inclusion on Template:DDRMM fluffs up the width of the song section by the width of several song titles.

I'd also like to take the opportunity to mention how inconsistently these quote marks are applied across the wiki already — many entries in Category:Music do not use them in their article, none of the lists of songs from the shows or of WarioWare DIY records use them, Starring Wario! and only Starring Wario has had its article title changed to have the quotes. I take this to mean the rule is not serving the wiki as it stands.

The one exception to everything I've mentioned thus far is Paper Mario: The Origami King's music discs: "Deep, Deep Vibes", "Heartbeat Skipper", "M-A-X Power!", and "Thrills at Night". These are the only time the names of songs are formatted this way (possibly due to the items being CDs of the songs and not the songs themselves). Therefore, these will be the only exception if this proposal passes, and will keep their quote marks.

To circle back around to my original point: I think the nail in the coffin for displaying music this way is Nintendo Music. This application, specifically meant to play music, does not surround their names with quote marks. And yet this article surrounds them in quotes anyway, stringently adhering to our unofficial way of formatting these over the way Nintendo Music actually formats them. It's almost lying, frankly.

So, our options:

• Option 1: Exclude quote marks from song titles in all cases. Our manual of style will remove the mention of song titles from the section of italicizing titles. Just for clarity, this excludes Origami King's CDs.
• Option 2: Keep quote marks when song titles are used in a sentence, but exclude them from standalone appearances of the title. Such standalone appearances would include article titles, navboxes, infoboxes, track listings, and table entries. Just for clarity, this option, too, excludes Origami King's CDs.
• Option 3: Do nothing. I guess this option includes Origami King's CDs.

Proposer:: Ahemtoday (talk)
Deadline: November 24, 2024, 23:59 GMT

Option 1

1. Ahemtoday (talk) My primary choice. I've firmly laid out my reasons why here.
2. Jdtendo (talk) I prefer to think of each music as a work in its own right rather than a part of some "greater whole". Jump Up, Super Star! is more than just a piece of Super Mario Odyssey's OST. Therefore, song titles should be italicized like any other work and not be in quotation marks as if they were merely chapters.
3. Hewer (talk) Per proposal, and there's precedent for following Nintendo's official formatting in spite of usual conventions. The inconsistencies described in the proposal ought to be fixed regardless of the outcome, though.
4. Biggestman (talk) While I to a degree understand the entire thing with the songs simply being a part of a greater thing, that isn't really fair when I would make an argument some of these songs are a larger part of the series' history than those "greater" things. For example music from Yoshi's Story is still used relatively often to this very day, but Yoshi's Story as a whole is just kinda there. Per all, too.

Option 2

1. Ahemtoday (talk) I will settle for this — part of my ire toward the quotemarks is that I find them highly unsuitable for these particular usages.
2. Nintendo101 (talk) Secondary option, per my comment below in Option 3.

Option 3

1. Nintendo101 (talk) The purpose of the quotation marks is to quickly convey to the reader that a "named subject" is part of a greater whole (that is italicized), and/or what type of subject it is in the context of where it is discussed in an article. For music, that whole is typically an album or CD (or in this case, a video game), but it is not exclusively used for musical pieces. For example, "Chicken Man" is the fourteenth chapter in The Color of Water. "The Green Glow" is the seventh episode in season one of Resident Alien. One of the benefits of doing this is that music, chapters, episodes, etc. sometimes share the same exact name as the whole they are a part of, or something related in the whole (like the name of a character or place), and discrete formatting mitigates confusion for readers. This is readily valuable for many pieces in the Super Mario franchise, because most of them are given utilitarian names. Wouldn't it be valuable for readers to just recognize that "Gusty Garden Galaxy" (with quotation marks) is a musical piece and Gusty Garden Galaxy is a level? Because that is what the quotation marks are for. I think it is a good and helpful tool, one that is used almost everywhere else when discussing music, and more would be lost than gained if we did away with it.
2. EvieMaybe (talk) per N101. quotation marks are a writing convention! most mario games also don't have italic titles, but we italicize them anyways because it's a formal writing convention that makes sense
3. Waluigi Time (talk) Strong oppose, per all. This is a well-recognized writing convention, the fact that Nintendo doesn't typically follow it within their products is irrelevant.
4. Camwoodstock (talk) Per all, especially Nintendo101. These quotes are here for a reason, no matter how remote it may seem.
5. Ray Trace (talk) Quoting songs is from the manual of style itself, it's the same reason we italicize game titles. I would go even further and quote song titles as a display title like I did in "Starring Wario!"
6. ThePowerPlayer (talk) Per all.
7. Axii (talk) Per all.
8. Doc von Schmeltwick (talk) - "Because game writing" is what leads to wikis encouraging jokey sarcastic writing, which I'm pretty sure is not the direction we want to go.

Comments

If this passes, how would it affect coverage of non-Mario music? Our only options are either to have two standards, or ignore established convention based on what Nintendo does for media they had no hand in actually producing. Neither seems ideal to me. -- Too Bad! Waluigi Time! 20:24, November 10, 2024 (EST)

We'd treat non-Mario music the same as Mario music. Established convention doesn't mean much when we're always saying on this page that we're not other wikis and we don't necessarily need to do things the way other wikis do them. Ahemtoday (talk) 08:01, November 11, 2024 (EST)

I don't think anyone is advocating to hold onto a convention just for the sake of it. Rather, that we should hold onto the convention because it is useful and the proposal doesn't provide persuasive reasons to abandon that usage, or at least it does not for me. - Nintendo101 (talk) 08:44, November 11, 2024 (EST)

In addition, I wouldn't use applications such as Nintendo Music as proof that we shouldn't abide by formatting either. Neither music metadata nor files themselves quote song names, neither does Spotify nor Amazon Music. Yet Wikipedia still does because that's how it's standardized in writing articles. In addition, you pointed out how "Starring Wario!" is the outlier as your point, I've only just started working on those articles mate. Ray Trace^(T|C) 21:01, November 10, 2024 (EST)

Even Wikipedia doesn't use the quotes in article titles though. Hewer (talk · contributions · edit count) 02:17, November 11, 2024 (EST)

I would support an option that called for just removing the quotation marks in the header for articles (as done here, which should be compared to here). This is not uncommon in written books on music. But there currently is no voting option to do just that. - Nintendo101 (talk) 08:44, November 11, 2024 (EST)

@Ray Trace I'm aware it's in the manual of style. That's why the proposal is about changing the manual of style. Ahemtoday (talk) 08:01, November 11, 2024 (EST)

I'm not talking about the wiki's manual style. I'm talking about general guidelines especially MLA Ray Trace^(T|C) 15:41, November 11, 2024 (EST)

If it's not our manual of style, then there's no reason for us to care about it because we don't use it. Ahemtoday (talk) 18:04, November 11, 2024 (EST)

Our manual of style is based on this manual of style. Ray Trace^(T|C) 18:11, November 11, 2024 (EST)

If it's only based on it, then it isn't it. The manual of style is ours, so this quote mark convention has to survive on its own merits, not just by virtue of being in someone else's manual of style. Ahemtoday (talk) 18:22, November 11, 2024 (EST)

Not using general formatting standard guidelines solely because "we shouldn't just because we're not them" is not a good argument. Ray Trace^(T|C) 18:24, November 11, 2024 (EST)

Well, then — Nintendo doesn't do this either, so there's no reason for this wiki to pretend like they do. That's been my argument this whole time. Ahemtoday (talk) 18:35, November 11, 2024 (EST)

The main difference is that they're a video game, and they're inherently informal in their presentation. They're not trying to write things and bios formally, they're trying to present writing to players, so formatting like italicizing game titles is optional, because that's what it's set out to do. On the other hand, we're an encyclopedia, our writing formatting is far more similar to Wikipedia which observes these things and MLA writing guidelines, and how to format sourcing, and it's something we should emulate over a video game's script. Ray Trace^(T|C) 18:47, November 11, 2024 (EST)

@Ahemtoday I don't think that is the strong argument you think it is, because almost no piece of media where it has become conventional to include quotation marks include them themselves. They are not on the back of most albums, books, or title cards for television shows. But they are all still presented with quotes arounf them in reference material like Wikipedia and physical books. What makes the Nintendo music we cover here so different that warrants unique treatment? - Nintendo101 (talk) 18:53, November 11, 2024 (EST)

Nintendo doesn't always italicize game titles either, this site does. To be honest, though, I'm not sure how consistently this wiki observes MLA. There's some superficial basis in it (mostly coming off of Wikipedia's style guide, which is sprinkled with some MLA), what with the titles of whole works being written in italics and those of constituent parts of a work being surrounded by quotes, yet the manner in which citations are formatted, arguably a priority of any academic style guide, seems rather peculiar to Wikipedia's house style. Take any citation formatted using the {{cite}} template on this wiki and compare it to how MLA proposes it is done (owl.purdue.edu). There's also been at least one attempt at explicitly adopting a standard purveyed by MLA that got shot down. Not to digress too much, I just wanted to point out that MLA is not currently as pervasive here as it's made out to be and can't be appealed to solely because of a few instances that (happen to) observe it. -- KOOPA CON CARNE 19:20, November 11, 2024 (EST), edited 19:24, November 11, 2024 (EST)

I am personally forgiving on how we structure citations in that template, because many academic journals don't adopt the MLA structure either. Everyone does something a little different from one another. The information included in a citation is more important than how it is organized, and things like ISBN are pretty helpful for an online reference like Super Mario Wiki.

But I also don't believe in supporting conventions just for the sake of them being conventions. I'd rather support them if they are beneficial. What are your thoughts on what I said in my vote above? - Nintendo101 (talk) 19:33, November 11, 2024 (EST)

I cannot argue with your vote. If a writing standard promoted by outside guides can harmonize with the needs of Mario Wiki, there's no reason not to adopt it. Quotation marks serve their purpose well in this case. so if it ain't broke, don't fix it. -- KOOPA CON CARNE 20:10, November 11, 2024 (EST)

Cool! I was just curious. I value your perspective. - Nintendo101 (talk) 20:14, November 11, 2024 (EST)

I'm realizing I haven't given my full thoughts on @Nintendo101's vote yet. I agree that there are benefits to formatting song titles in this way (particularly in sentences, which is why I have the option to keep the quote marks exclusively in sentences) — but this formatting scheme misrepresents how the actual works in question are referred to by official media. I had to ask a friend who had Nintendo Music to find out whether or not the app displayed song titles in quotes, because I couldn't trust this wiki to tell me — and, like I said, Nintendo Music doesn't. Yet this article writes the song names as if it does, because apparently this convention is more important than this kind of information. I know this is a minor piece of information, but this formatting convention causes me to be unable to trust the wiki about it. No benefit can counterbalance that. Ahemtoday (talk) 20:13, November 11, 2024 (EST)

I am sorry that you felt mislead, but are you sure it is not because you were unfamiliar with this being a convention for music pieces in the first place? - Nintendo101 (talk) 21:12, November 12, 2024 (EST)

I was well familiar with the convention and how this wiki used it at the time, which is why I knew to ask a friend instead of taking the wiki's word for it. I take such a hardline stance against it not because this untrustworthiness has personally wronged me, but because untrustworthiness is a failure of the wiki on principle. Ahemtoday (talk) 00:02, November 13, 2024 (EST)

I am sorry, I was not referring to Super Mario Wiki in isolation. I was referring to the convention at large. In books and articles on music, regardless of topic, individual pieces are placed within quotation marks. I know I myself first learned one is supposed to put quotation marks around music titles while I was taking English class in middle school. So while I am sympathetic that this bothered you, I do not agree it is misleading. Maybe the issue lies with folks who do not have a lot of experience reading or writing about music. - Nintendo101 (talk) 13:05, November 13, 2024 (EST)

Whether or not readers are familiar with the convention doesn't change the fact that the convention is not reflective of what is being talked about. The only reason wiki readers know "Thrills at Night" and its ilk are actually surrounded in quotes officially is because we haven't been thorough in applying this convention. If we did, then the distinction would vanish completely, because the wiki currently considers adhering to this guideline more important than this kind of information. You can't pin that on readers being unfamiliar. Ahemtoday (talk) 22:17, November 13, 2024 (EST)

I have contacted the director of the Purdue OWL at Purdue University to ask them how one should cite music tracks that already has quotation marks rendered in their name. However, to be honest, I am still not really sure what the issue here is. How are the quotation marks any different from italicization of video games and albums? The name Paper Mario: The Origami King is not displayed anywhere in Nintendo's official material italicized, but we do it for the same reasons one puts quotation marks around music tracks - because it is a useful MLA convention. For music, it is unclear to me on what is being miscommunicated or lost when they are accurately displayed between quotation marks, especially since articles for "Thrills at Night" and other tracks are accompanied with screenshots that show how they are rendered in-game. Is this not sufficient? - Nintendo101 (talk) 14:22, November 14, 2024 (EST)

It is not sufficient. To begin with, not every use of song titles is accompanied by images showing that the music titles are formatted without quotes — the majority of articles in Category:Sound tests do not have such images. (Not to mention that to use these images to establish the formatting of every song title in a given game would require a comically excessive amount of images.) Furthermore, even if they did, this information would be entirely invisible to users of screen readers, raising accessibility concerns. This information can't be conveyed by images alone. Ahemtoday (talk) 15:14, November 14, 2024 (EST)

Couldn't it just be clarified in the article itself that a piece of music is displayed with quotations mark around it? It is not a very common thing to do. - Nintendo101 (talk) 16:22, November 14, 2024 (EST)

Writing in an explicit note clarifying that this time the article is actually reflective of how the music is referred to officially is a much more convoluted way of going about this compared to just referring to them in the official way to begin with. Ahemtoday (talk) 16:50, November 14, 2024 (EST)

Biggestman: The formatting of quotes in songs aren't discussed from a cultural relevancy angle, they're in context of being part of an album. It's the same reason short poetry gets quotes, but novels get italicized, we'd quote "The Raven" but still italicize The Day My Butt Went Psycho. Ray Trace^(T|C) 21:40, November 15, 2024 (EST)

Add identifiers to near-identical titles

Current MarioWiki writing guidelines state that articles with shared titles recieve an identifier to disambiguate between them (see: Mark (Mario Tennis series) and Mark (NES Open Tournament Golf)). However, this currently relies on the articles sharing an identical, character-by-character name. This means Color coin (Super Mario Run) and Colored coin (Wario Land 3) do not recieve identifiers, despite sharing functionally identical titles. Other sets of articles with the same dilemma include Secret Course 1 (Super Mario Land 2: 6 Golden Coins) and Secret Course 01 (Super Mario Run), Spyguy (Mario vs. Donkey Kong 2: March of the Minis) and Spy Guy (Paper Mario), and Rollin' Down the River (Yoshi's Woolly World) and Rolling Down the River (The Super Mario Bros. Super Show!).

This proposal aims to amend MarioWiki:Naming to consider near-identical titles like these as "shared titles", and thus qualify for recieving an identifier according to the established criteria. This is already applied in some articles, but this proposal aims to formalize it as part of the naming rules.

Note that this proposal only covers names that are semantically identical, and only differ in formatting or minor word choices. Buzzar and Buzzer have extremely similar names, but they aren't semantically identical. Balloon Boo and Boo Balloon are extremely similar as well, but the word order sets them apart.

Edit: Per Hewer's question and my comment below, I'd like to point out MarioWiki already does this sometimes. Pairs of near-identical names with identifiers include Family Basic (microgame) and Family BASIC (as ruled by a proposal), Hot Air Balloon (Donkey Kong franchise) and Hot-air balloon, Finish line (object) and Finish Line (microgame), and Avalanche (obstacle) and both Avalanche! (Dance Dance Revolution: Mario Mix) and Avalanche! (Mario Party 4). If this proposal doesn't pass, all of these would get their identifiers removed.

Proposer: EvieMaybe (talk)
Deadline: November 26, 2024, 23:59 GMT

Support

1. EvieMaybe (talk) per.
2. Super Mario RPG (talk) Per proposal.

Oppose

1. Altendo (talk) I don't see a need for this. If the names are similar, tophats containing the other pages can be placed on the pages with similar names. Identifiers are used to identify subjects with identical names, not similar names.
2. Hewer (talk) Per Altendo, this is what Template:Distinguish is for. We have to use identifiers for identical titles because the wiki can't have multiple pages with the same title, but that limitation doesn't exist if the titles are just similar. This would make the titles longer than they need to be, and I could also see this leading to disagreements about what's similar enough to count, if the examples are anything to go by. Easier to stick to the objectivity of only giving identical names identifiers. The proposal also doesn't specify what the "some articles" are where this has already been done, but I'm assuming they should be changed.
3. Ray Trace (talk) Per Hewer.
4. Dine2017 (talk) Per Hewer & I'd like to see the use of identifier kept to a minimum because it simplifies typing (URL, wikicode, etc.)
5. SeanWheeler (talk) Per Hewer. No need to extend the title just because of a couple letter difference. The identifiers are there for identical titles because it's impossible for wikipages to have the same name.
6. ThePowerPlayer (talk) Per Hewer. Making this change would only cause more confusion, not less.

Comments

I'm not sure why this is a problem in the first place, can you please elaborate? -- Too Bad! Waluigi Time! 12:13, November 11, 2024 (EST)

i just find it a bit unreasonable to expect people to remember the difference between two names that are identical in all but formatting, or essentially irrelevant word choice differences (in the case of Color coin and Colored coin, which have also been). this is especially true while editing; i had to verify whether Secret Course 1 was the SML2 one or the SMR one when writing the Secret exit article. without resorting to a literal, robotic interpretation of the rules, all of the articles i mentioned have functionally "the same name" as their pair, and there is precedent for adding identifiers to article names like these. Family Basic (microgame) recieved a differentiatior because a mere capitalization difference from Family BASIC was deemed unreasonable. folks in the MarioWiki Discord server agreed with me when i asked if i should rename Hot Air Balloon (Donkey Kong franchise) (previously just "Hot Air Balloon", with no hyphen and Air capitalized) to differentiate it from Hot-air balloon. Avalanche (obstacle) has an identifier to separate it from Avalanche! (Dance Dance Revolution: Mario Mix) and Avalanche! (Mario Party 4), even though both of them have exclamation marks. Finish line (object) and Finish Line (microgame) get identifiers, even though they're capitalized differently. this is something we already do, the aim here is just to formalize it. EvieMaybe (talk) 14:51, November 11, 2024 (EST)

This proposal passing wouldn't mean you no longer have to check whether it's Secret Course 1 or 01, it'd just mean you now have to type an unnecessary identifier and pipe link it as well. I'd say it's different for finish line and Family BASIC where the only difference between titles is casing, as the search function on the wiki is case insensitive (and also, that proposal made Family Basic a redirect to Family BASIC, so an identifier is still needed to distinguish from that). But in the other cases, we don't need the identifier. Hewer (talk · contributions · edit count) 15:49, November 11, 2024 (EST)

New features

Create a category for "catch-all articles"

By "catch-all article" (tentative term; please suggest names) I mean those that describe elements that are not related, but share an article because they boil down to the same generic, often real world object. Many of them fit what the guidelines call a "generic subject". Examples of this kind of article are:

• Hook, which includes the object from Donkey Kong Country 2: Diddy's Kong Quest and the hooks on poles from Super Mario Sunshine;
• Lift, which includes the yellow lifts seen in Super Mario games, elevators from Donkey Kong Country, Moving Platforms from Mario vs. Donkey Kong 2: March of the Minis, among others, all just basic platforms;
• Bubble, which includes the underwater bubble from Super Mario 64, the player-carrying bubble from New Super Mario Bros. Wii, the Bubble trap from Diddy Kong Racing, among others;
• Banana, which includes the bananas from the Mario Kart series, the bananas from the Donkey Kong Country games, the bananas from Yoshi's Story, among others;
• Heart, which includes the heart item from Super Mario Odyssey, the one from Donkey Kong Country Returns, the one from Dr. Mario World, among others.

They may also boil down to a similar fictional basic concept, which are their own distinct thing, despite all of them taking a similar form:

• ! Block, which includes the red blocks from the Yoshi's Island games games, the block-spawning yellow blocks from Super Mario Maker 2, the ! Block switches from the Wario Land games;
• Poison Mushroom, which includes the mushrooms from Super Mario Bros.: The Lost Levels, the Poison Shroom item from the early Paper Mario games, among others;
• ? Panel, which includes the panels from Super Mario Kart, the ones from Paper Mario: Color Splash, and others.

Compare subjects to which this category would not apply, like ? Block or P-Switch, where every reappearance of the subject is really a deliberate revisitation of a specific concept that already existed.

This category would be applied to articles on concrete subjects only (most of which, if not all, would be objects).

Proposer: Bro Hammer (talk)
Deadline: November 24, 2024, 23:59 GMT

Support

1. Bro Hammer (talk) My proposal.

Oppose

1. Hewer (talk) I don't see how such a category would be useful, and I don't like that it's pretty subjective and is based on a trait shared by the articles rather than the objects themselves. Even if there was value in distinguishing these pages, I don't think a category like this is the way to do it.
2. ThePowerPlayer (talk) Is History of Mario a catch-all article because it covers both a fictional character and Bob Hoskins? We would have to have that sort of debate for too many articles to count. This is too subjective and doesn't really accomplish anything.
3. Super Mario RPG (talk) Unnecessary, and the word "generic" alone is unclear whether it goes by the definition of real-life or Super Mario.
4. Arend (talk) Honestly, the inclusion of fictional items like Poison Mushroom, ! Block and ? Panel would make it more confusing for me what a "catch-all article" is supposed to be; if it's supposed to be about generic subjects, then their inclusion would definitely muddy the concept quite a bit. Not to mention that the term "catch-all article" isn't clear enough as it is.

Comments

My gut reaction is that I disagree that the Poison Mushroom and Lift articles encompass generic subjects. They are supported as discrete in the paratext for these games. But even if narrowed to articles I agree are generic, it is not inherently clear to me what the benefit of having a "catch-all category" would be. My general view is that there are quite a few subjects that we consider to be generic which really are not. - Nintendo101 (talk) 15:45, November 10, 2024 (EST)

What would be some subjects you don't consider generic? My case for the Lift is that it's an article that encompasses almost all types of flat, moving platforms (a basic platforming game object), many even with their own distinct names; I believe you could even argue for some of the versions to get their own articles. And yeah, I agree that there's no huge benefit to having this category, as it would be there mostly for the sake of acknowledgement that "this article does not describe the history of a single idea, but it's instead an aggregation of the histories of various ideas that fit under this umbrella". Bro Hammer (Talk • Cont) 16:25, November 10, 2024 (EST)

Create articles for Glohm enemies or merge them with their normal counterparts

I'm currently contributing to Mario & Luigi: Brothership content, and I'm currently creating articles for enemies in the game. It has been brought to my attention that Glohm enemies are basically stronger versions of preexisting enemies, although they have unique characteristics.

This proposal aims to determine whether or not Glohm enemies get their own articles. So, there are two choices for when Glohm enemy coverage eventually occurs:

1. Glohm enemies get their own articles. They get their own dedicated pages.

2. Glohm enemy coverage is limited to the articles for their normal counterparts. This means all Glohm related information for them is explained for the normal versions of the enemies.

Let's see what happens!

Proposer: Sparks (talk)
Deadline: December 5, 2024, 23:59 GMT

Create new articles for Glohm enemies

1. Sparks (talk) My preferred choice. Sure it could get repetitive and redundant, but it's worth it to document the abilities of these Glohm enemies.
2. Technetium (talk) Might end up changing my vote later, but I'll go for this for now. Once we get stat tables / infoboxes for Brothership enemies I feel it'll make more sense too.
3. Camwoodstock (talk) We give articles to other stronger RPG enemy and boss variants, so why should Brothership be any different?
4. Tails777 (talk) They are stronger variants with different stats to their originals, no different from every example Camwoodstock gave. Per proposal.
5. DryBonesBandit (talk) Per all.
6. Zootalo (talk) The Shiny Paper versions of enemies from Paper Jam have their own articles as well; this is no different. Per all.
7. Nightwicked Bowser (talk) Probably best for overall consistancy with a game like this one.

Comments

@Zootalo The Paper Jam shiny enemies are not split, but the Sticker Star ones are.

Removals

None at the moment.

Changes

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

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

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

The case for moving Daisy's article

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

The case for moving Peach's article

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

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

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

Move both princesses

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

#Pseudo (talk) First choice, per proposal. The princess titles for both characters can definitely be seen as their full names, but it seems to occupy a similar space to "King Bowser" in most games.
#EvieMaybe (talk) per Altendo, specifically

Only move Daisy

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

Keep both princesses the same

1. SeanWheeler (talk) Stop shortening names! Seriously, I knew this was next after the Koopaling proposal.
2. Mario (talk) I don't think any these moves are great (especially the one where "Shadow the Hedgehog" was shortened, I dislike that one). They greatly hinder searches on the wiki (in Peach's case, it's going to conflict with the fruit), and more people online are going to search "Princess Peach" and "Princess Daisy" to find the character. What these moves are going to do, like with those older name moves (which I am not on board with) is going to have searches rely on redirects. I'm not sure how much SEO and search engine discoverability is going to be impacted (Porple confirmed with me on Discord that it will certainly hinder discoverability on search engines but it's not catastrophic, just something to keep in mind) but I think there is a great reason we chose Chuckster over Pianta Thrower. These are distinct, recognizable names. Don't fix what isn't broken, and the current method of piping and using redirects for the shortened, overlapping names seemed to serve us well enough.
3. Waluigi Time (talk) Per Mario. I don't think focusing in so heavily on the exact places or times the full names vs. the shortened names are used is beneficial if those names are still in frequent use. Some of these make sense (E. Gadd is rarely called Elvin, the Koopalings' full names seem to be mostly phased out these days), but the Sonic proposal was a misstep IMO. Princess Peach is still very commonly used, the average person knows her by that name, I don't see a need to change it. I feel less strongly about Daisy, admittedly.
4. UltraMario (talk) Per all.
5. Pseudo (talk) Upon further thought and seeing Mario and Waluigi Time's votes, I'm inclined to think that moving pages like this is probably not such a wise idea, especially as it hurts searchability. I've removed my original vote for merging both and now consider this my primary one, though I think that moving Daisy would still be alright with me.
6. FanOfYoshi (talk) Yeah, no; per all. We'd need a counterproposal... That Sonic proposal already was a pretty bad enough decision as-is and this... this is no different.
7. MeritC (talk) Per all; first of all, in terms of a fan managed encyclopedia like this, it's still the best route to keep the "Princess Peach" and "Princess Daisy" article titles for this Wiki, even though certain and recent games like the sports, kart racing, and Mario Party games just address the two as "Peach" and "Daisy" in their names. Plus, in terms of linking their names to the respective articles, we're already making sure that "Peach" links to the "Princess Peach" article and "Daisy" links to the "Princess Daisy" article anyway.
8. Arend (talk) Secondary choice, the current names are fine too.
9. Dwhitney (talk) Per all. Also, Daisy is referred to as Princess Daisy in Mario Tennis Aces.
10. Lakituthequick (talk) Per all, in particular Mario and WT. As for the SEO point, while that certainly does matter (even outside of "corporate" contexts), in this case it's just clearer to denote the princesses with their titles. SEO happens to be a happy by-product of that.
11. SmokedChili (talk) Per all. Since these proposals are made with following the rules in mind, then the obvious alternative is to change the rules. The naming guidelines have nothing about full names and titles, that should be changed so that conditions pertaining to them to allow use of extending their titles based on official material over (identifiers). Let's use Princess Peach as an example. "Princess Peach" was first seen in Yoshi's Safari then later in Mario 64 and here and there ever since. Thus "Princess" is part of Peach and should be kept as "Princess Peach" to distinquish from Peach the fruit. Same with Roy Koopa and Roy from Mario Golf, the latter doesn't really need an identifier if the former is moved back to his full name. On the other hand, I've been also thinking such a policy would have to be restrictive: "Princess Peach Toadstool" wouldn't be legit because it wasn't seen in Yoshi's Safari first, "King Bowser" wouldn't be either for similar reasons, "Boo Diddly" wouldn't count because it's only seen in Mario 3 and its remakes, and Mollusque-Lanceur's full name won't because it comes from a secondary source and its length may be an issue. There's probably a lot more that needs to be figured out, those are just examples that came to my mind.
12. MCD (talk) Per all.
13. Killer Moth (talk) Per all.
14. Sdman213 (talk) Per all.
15. LadySophie17 (talk) Per all. And don't move my username to just Sophie.
16. DesaMatt (talk) Per all, but not strongly.
17. Shoey (talk) Per all
18. PnnyCrygr (talk) Per all. Removing the princess prefix could confuse them for the actual fruit and the actual flower, respectively. We have also an article about the LM ghost knows as Daisy. The "Peach Blossom" move involves Peach summoning literal Peaches, to give an example. Better to keep them "Princess Peach" and "Princess Daisy".
19. Ray Trace (talk) I really want to move Sonic back to Sonic the Hedgehog and Shadow the Hedgehog.

#EvieMaybe (talk) per Waluigi Time

Princess Comments, Peach

@SeanWheeler: Why is shortening names a bad thing? If the shortened name is the more current title of a character or game, shouldn't the article be moved to the more current title? The length of the titles of the characters is not the main issue here; it's how current those titles are. Mari0fan100 (talk) 20:41, November 9, 2024 (EST)

@Mario: Given "Peach" and "Daisy" are very commonly used names, and also shorter (thus easier to type), I can't imagine it being that bad for searches. The shortened names are also "distinct, recognizable names", and the ones Nintendo is fine to use for the characters (as well as what I usually hear fans call them), so why shouldn't we follow suit (especially given all the other renaming proposals, some of which, e.g. Bobbery and TEC, had literally no opposition)?
@Waluigi Time: I would argue Princess Daisy isn't really "still in frequent use". Hewer (talk · contributions · edit count) 06:13, November 10, 2024 (EST)

I think if I wanted to look up the Mario character named "Daisy" in Google, I would use "Princess Daisy" to try to get more results that aren't daisies. Mario's popular, but not the center of all reality. (Though a company selling BB guns somehow beats out the plant.) Google suggests I may also want to use "Daisy mario". Bobbery is unique enough to be the main topic of that name. TEC has technology companies beat out the character unless "TEC-XX" is used.

Super Mario Wiki appears to be far enough ahead in results that if Google recognizes the search is for a character this site is first up, even in cases like Bobbery, TEC, and Ludwig. But I'm no search engineer, so I don't know if changing the article names can impact this.Salmancer (talk) 06:29, November 10, 2024 (EST)

I was more referring to searches on the wiki itself. Google searches shouldn't really be what determines page names in my opinion, or we'd have a good case to move Pauline to "Mayor Pauline" (or to add "mario" in brackets to a ton of article titles). Either way, I feel like having to search "daisy mario" instead of "princess daisy" (as I imagine many people already do) isn't that big a deal. Hewer (talk · contributions · edit count) 06:44, November 10, 2024 (EST)

As I alluded to, my reasoning mostly concerns Peach, but I don't really want to put my official support behind a Daisy move either, which is why I chose that option. IMO, external searchability absolutely should be something taken into consideration when it's relevant, but not the deciding factor. At the end of the day, a wiki is here for its readers, so let's not make it needlessly harder on them to find things if we can help it. -- Too Bad! Waluigi Time! 12:56, November 10, 2024 (EST)

I'd think using the name the character most commonly goes by would make it more intuitive to find. Hewer (talk · contributions · edit count) 13:15, November 10, 2024 (EST)

I'm not convinced that switching to a shorter name has any negative influence on external searchability regardless of if that should be a priority or not. We're still on the front page of Google results for "Shadow the Hedgehog wiki", and the only results that come up before our "Shadow (character)" article are from Wikipedia and dedicated Sonic wikis. jan Misali (talk · contributions) 13:51, November 10, 2024 (EST)

I don't understand why the topic of SEO is still part of the debate. It's a misplaced priority. This site is a community-run educational resource, not a corporate product that you're incentivized to optimize every little aspect of in the name of clicks. Look at Fandom--outwardly, it provides the former, but it's also an ad-ridden hellhole artificially planted on the front page of Google results with no regard to the quality or accuracy of the content herein. I'm questioning whether it's worth compromising accuracy so the wiki could compete with such actors. Not to say this site would exist without traffic and participation at all, every project needs funding and other manners of support, but, like
guys,
This is the biggest resource on the Internet for the most popular video game franchise on the planet.
Do you really believe losing 0.005% of total searches because Glup Shitto got renamed to the less popular but more accurate "Shart Faqeer" is such a big deal in the grand scheme of things? -- KOOPA CON CARNE 14:33, November 10, 2024 (EST), edited 10:55, November 11, 2024 (EST)

I think "corporate product" is a bit of a misread. Rather, there is little value in maintaining an encyclopedia that people cannot find. I do not know if it impacts this particular case (i.e. when I last searched "wendy mario" or "wendy o. koopa" on Google, our article still shows up near or at the top, regardless of name), but I do not think it is invalid to keep in mind.

I think it is worth keeping in mind that the Super Mario Wiki has different goals than a character-selection screen or a level-selection screen, which typically prefer simple truncated names. New Super Mario Bros. U refers to a boss as "Larry" in one context and as "Larry Koopa" in another. An encyclopedic reference that encompasses many series and subjects may similarly best support its information by adopting fuller names with discretion. - Nintendo101 (talk) 15:22, November 10, 2024 (EST)

The character select screen name shortening argument has already been addressed: names like "Light-blue Shy Guy (Explorer)" are longer than "Princess Daisy", yet the former is used while the latter is not. Clearly Nintendo just has a preference for the shorter name, so we should too. Hewer (talk · contributions · edit count) 17:59, November 10, 2024 (EST)

This is not consistent though. On the character-selection screen in Super Mario Bros. Wonder, you can select "Light-Blue Yoshi." The standees for this character's name is truncated as "L. Blue Yoshi." The Star Fox protagonist goes by "Fox" on the character-selection screen for the Super Smash Bros. titles, but goes by "Fox McCloud" on the costume list for Super Mario Maker. Our pink princess character goes by "Princess Peach" on the box for her standalone game, and simply as "Peach" in the game itself. Is it invalid to suggest whether a character goes by a truncated or full name is really context dependent, and less about the phasing out of monikers or surnames for certain characters? If the former, is Super Mario Wiki inherently not the platform where full names would be helpful? And if it is not, why? - Nintendo101 (talk) 19:07, November 10, 2024 (EST)

The length of a character's name can undoubtedly be subject to technical limitations in a game. I personally just don't think this is necessarily the case with Daisy's name as of today, and my view is that the wiki should be observing what the most current official consensus on those names is. The standees in Wonder are a highly particular instance of name rendering even within the game; the character selection screen otherwise uses "Light-Blue Yoshi" and "Daisy" simultaneously, and I'd hazard a guess that players are more likely to make better note of those than how they are rendered in the standee menu. -- KOOPA CON CARNE 19:41, November 10, 2024 (EST), edited 19:50, November 10, 2024 (EST)

As people have related in this discussion, Mario Wiki tends to be pushed forward in Google results for a Mario character. It is decidedly not an encyclopedia people cannot find. Porplemontage can probably conjure some projections, he has the data for this sort of thing after all, but I'm confident given the wiki's size and popularity that Mario Wiki will remain in the top search results for "peach mario" and "daisy mario" whether the characters retain or lose their mantle titles. -- KOOPA CON CARNE 19:04, November 10, 2024 (EST), edited 19:12, November 10, 2024 (EST)

@JanMisali Same with googling "shadow sonic wiki". Even just "shadow wiki" still brings up his Mario Wiki article on the second page on my end, which is pretty impressing considering the breadth of coverage either of the words "shadow" and "wiki" have on the Internet. -- KOOPA CON CARNE 14:48, November 10, 2024 (EST)

@MeritC: "We'd have to change links" is never a good argument. If this passes, a bot will take care of fixing all the links. That's how we were able to rename the "Super Mario (franchise)" page, probably one of the most linked to pages on the entire wiki, with no issue. Hewer (talk · contributions · edit count) 17:59, November 10, 2024 (EST)

@Dwhitney Where in Mario Tennis Aces is the name "Princess Daisy" used? I can't find any evidence of her being called anything but "Daisy" in that game. jan Misali (talk · contributions) 10:27, November 11, 2024 (EST)

It's right there in the beginning of the story mode. This video, around the 5:15 time mark. rend (talk) (edits) 11:19, November 11, 2024 (EST)

Ah, missed that. Thanks! But regardless, it's definitely not her primary name in that game. jan Misali (talk · contributions) 12:25, November 11, 2024 (EST)

It should also be noted that the Super Mario Land manual consistently refers to Daisy as "Princess Daisy" in the story section and gameplay section; the character section is the only place in the manual where she's referred to as just "Daisy" (plus mistakenly calling her "Daisy Princess" as well). The manual of Mario Kart: Double Dash refers to her as "Princess Daisy" once, too. I get that these aren't exactly "in-game" materials, but that should put "Princess Daisy" on the same level as the Koopalings' full names.
Do Super Smash Bros. games count too, btw? Palutena has referred to her as "Princess Daisy". rend (talk) (edits) 11:43, November 11, 2024 (EST)

I mentioned Smash Bros. in my previous proposal about this. She's called Daisy everywhere else in that game, including elsewhere in that same Palutena's Guidance conversation. But yes, I agree that "Princess Daisy" is a name used on the same level as the full names of the Koopalings, and I think we should use it the same way we use the Koopalings' full names (ie. not in the article title). jan Misali (talk · contributions) 12:25, November 11, 2024 (EST)

@SmokedChili: There is no universe where peach the fruit that made minor appearances in five games could get naming priority on this wiki over Peach the major character with hundreds of appearances. That's why Peach already redirects to the character, and Peach (fruit) already has an identifier - shortening the name wouldn't change that. The same goes for Roy - the Mario Tennis character always had an identifier for years before Roy Koopa's name was shortened, because the former is significantly less prominent and less likely to be what people searching "Roy" are looking for. (Also, Mollusque-Lanceur's full name recently appeared in Nintendo Music, which I don't think is a "secondary source", and length wouldn't be an issue.) Hewer (talk · contributions · edit count) 12:35, November 11, 2024 (EST)

Why would the fruit need an identifier if Peach being in the "Princess Peach" page frees up the "Peach" page? And why use conveniences this wiki made up over what's found in official material? Wiki-made identifiers should thus be used as sparingly as possible. And my argument for Mollusque-Lanceur is that by using naming priority, since his short name comes from the in-game music player while his full name comes from the Prima guide, the latter shouldn't be qualified for use as a page title even if it comes up later. SmokedChili (talk) 13:13, November 14, 2024 (EST)

The reason "Peach (fruit)" needs an identifier is that a user who goes to www.mariowiki.com and types "Peach" into the search bar is more likely to be looking for information about one of the main characters of the Super Mario franchise than the fruit. It's the same reason Mario 1 (level) needs an identifier. Even if the thing it's disambiguating itself from isn't the name the wiki actually uses for that subject, one subject is simply so much more notable than the other that we choose to disambiguate other articles from even its unofficial names. This is a strictly positive thing for the user experience of anyone using this wiki, and I strongly disagree with the implication that we should stop considering "which subject is a user who searches for this term on this wiki more likely to be looking for?" to be a priority. jan Misali (talk · contributions) 14:25, November 14, 2024 (EST)

The difference is that Mario 1 (level) references SMB (and even then adding an identifier sounds like an overreaction) while Peach got her name from the fruit. Your assumption also ignores the possibility that readers may know about peach fruits and/or call Peach "Princess Peach" in their heads regardless of how formal the source is, so the search result argument wouldn't be as reliable because how many actually search for "Peach" over "Princess Peach" when they want the character? SmokedChili (talk) 04:55, November 17, 2024 (EST)

I think you're missing the point of identifiers and redirects a bit. Plenty of people would search "Peach" instead of "Princess Peach" (after all, it's shorter so easier to type), and I can't imagine the positives could outweigh the negatives of making it not redirect to the obviously more likely intended result. It would just harm the wiki's usability. Hewer (talk · contributions · edit count) 06:11, November 17, 2024 (EST)

@SmokedChili Peach is not called "Princess Peach" at any point in Super Mario 64. She is called "Princess Toadstool", "Peach", "the Princess", and "Princess Toadstool, Peach". jan Misali (talk · contributions) 12:48, November 11, 2024 (EST)

For clarity, this is not true. According to our own article Toad says "Hold on to your hat! If you lose it, you’ll be easily injured. If you lose it, look for the course where you lost it. Speaking of lost, Princess Peach is still stuck in the walls somewhere. Please help, Mario! Oh, you know there are secret worlds in the walls as well as in the paintings, right?" And in Super Mario 64 DS, the narrator also refers to her as "Princess Peach." People should do with that what they will. "Peach" is still more commonly used in the game, but it is not in isolation from "Princess Peach." - Nintendo101 (talk)

That article contains a mix of quotes from both Super Mario 64 and Super Mario 64 DS. The corresponding Ukikipedia article, which has a direct textdump of the raw text files from the Nintendo 64 game, has the original dialogue and does not contain the name "Princess Peach". jan Misali (talk · contributions) 14:40, November 14, 2024 (EST)

We should most certainly revise our naming conventions, since it's warranting proposals for every character to be moved to just their first names. And now that we have the Sonic restaurant, the hedgehog should definitely get his full name back. And with Shadow and Big, their full names would be better page titles than identifiers. And after opposing the proposal to add identifiers to similarly named pages, I might advocate for Peach (fruit) to get it's identifier removed just for the princess to keep her title. That page already has the {{About}} template linking to the princess anyway. SeanWheeler (talk) 23:52, November 13, 2024 (EST)

Are you suggesting that someone who types "Peach" into the search bar on mariowiki.com and presses enter is more likely to be looking for the fruit than the character? jan Misali (talk · contributions) 00:29, November 14, 2024 (EST)

Sonic Drive-In also changes nothing, it's called Sonic Drive-In and not just Sonic. Hewer (talk · contributions · edit count) 02:53, November 14, 2024 (EST)

Alright, whose responsible this? Still, it's not like "Princess Peach" completely disappeared after being seen in Yoshi's Safari first. SmokedChili (talk) 13:16, November 14, 2024 (EST)

@LadySophie17 To be clear, the purpose of this proposal is not simply a preference for shorter names. I wrote the proposal to move our article about The Old Psychic Lady with the Evil Eye Who Reads Fortunes and Knows Everything Before It Happens to her full title for the same reason I think it makes sense for our article about Daisy to be moved to "Daisy". We should prioritize the most common current primary name of a subject regardless of if that's a shorter name than their most formal full name or a longer name than what most fans would rather call them. jan Misali (talk · contributions) 14:07, November 14, 2024 (EST)

I'm aware. My comment was a just a cheeky remark at the fact that simply "Sophie" is the most common current primary name of the subject that is me. — Lady Sophie ^(T|C) 14:19, November 14, 2024 (EST)

Joke's on you, I'm writing a proposal for your name as we speak. -- KOOPA CON CARNE 14:23, November 14, 2024 (EST)

@PnnyCrygr We don't have an article about Daisy from Luigi's Mansion 2. That character is covered in a subsection of a longer article. Lower on this very page there is currently a proposal that has literally no opposition that's suggesting that it's unnecessary to use the title to disambiguate between a subject that has an article and a subject that only has a subsection of an article. jan Misali (talk · contributions) 08:51, November 16, 2024 (EST)

Thanks for the heads-up. Now I remember.  ^P_nn^yC_ryg^r  09:07, November 16, 2024 (EST)

Where did the "Drive-In" part of the name come from? The logo only has the word "Sonic" and every commercial I've seen simply called it Sonic. At least with Sonic the Hedgehog, his full name has been the title of many games and media, and he was called such quite frequently in his franchise. Sonic Drive-In is just advertised as Sonic. I only saw that full name as a wiki page title. If a crossover character has the same common name as a restuarant, who gets the short name? SeanWheeler (talk) 20:47, November 17, 2024 (EST)

The character? This is a problem this wiki has already solved. jan Misali (talk · contributions) 21:39, November 17, 2024 (EST)

How had the wiki already solved that problem? By the fact that Sonic the Hedgehog was already moved to Sonic by the time the Sonic Drive-In got an article? Considering the Sonic Drive-In article is about Sonic's promotion of Mario & Luigi: Paper Jam in 2016, it was created eight years late. SeanWheeler (talk) 16:38, November 18, 2024 (EST)

The way the wiki solved the problem is that "Sonic" is the article about the character (and in fact already redirected to the article about the character before it was moved) and "Sonic Drive-In" is the article about the restaurant. Unless you're suggesting that we should change this (and I legitimately cannot think of a single good reason why we would), there isn't really anything else to say about the matter. That just factually is the solution that is currently in place to the problem being asked about. jan Misali (talk · contributions) 17:29, November 18, 2024 (EST)

Why do you bring up the Sonic Drive-In page being "eight years late" like it's relevant? Sonic the character was relevant to the Mario franchise years before Sonic the restaurant anyway. The idea that the character can't be called just "Sonic" despite generally being called that in his several Mario appearances but the restaurant that has an article because of one promotion in 2016 must be called just "Sonic" sounds biased to me. Hewer (talk · contributions · edit count) 20:04, November 18, 2024 (EST)

Well, with the proposal to rename the princesses by their shorter more common referred names failing, it would be good to rethink some of the earlier renaming proposals. Especially the one about the crossover characters being moved, because I feel like a lot of these characters would lose their identity without their full names here, a few of them like Shadow got the unnecessary "(character)" identifier, because Shadow is a Super Mario RPG enemy, and there are still other users wanting to overturn that proposal. And if Zelda were to get her article back, I would want it to be consistent with Peach and Daisy. I do want to overturn that proposal that put the Smash characters on list pages, because I am not a fan of having articles stacked together as a list like we did with the Banjo and Conker series pages long ago, the sections for Mario characters and characters who made more Mario appearances linking to their own pages making those pages even less about the franchise we're about, and because of the amiibo having them appear in Super Mario Maker and other games. SeanWheeler (talk) 23:37, November 19, 2024 (EST)

And yet proposals like this, that, and the other passed with no opposition. Not sure how the Smash list pages are relevant, but the point of them is to cover the fighters not relevant enough to Mario for their own pages, so naturally they'll be some of the less Mario-relevant pages. If your problem is them not being relevant to Mario, I don't see how splitting all the characters back out will help. At this point I feel like outright deletion is probably the more likely eventual fate of those list pages, to be honest. Hewer (talk · contributions · edit count) 03:54, November 20, 2024 (EST)

Those list pages for the fighters aren't just covering Smash, but other appearances they had with Mario such as Super Mario Maker. Pit has so many Mario appearances that I'm wondering why he's on the Brawl list instead of getting his own article. The fighters who didn't appear with Mario outside of Smash would definitely be deleted, unless the majority votes to keep all of them. But I'm voting to split the ones with Mario cameos and delete the rest. SeanWheeler (talk) 20:16, November 20, 2024 (EST)

Those cameos are not notable enough to warrant their own articles, though. You're suggesting that being in Smash doesn't automatically make a character relevant to Mario, but also that being in Smash is what makes a character whose other appearances are a few cameos worthy of an article. Hewer (talk · contributions · edit count) 02:44, November 21, 2024 (EST)

Split off the Mario Kart Tour template(s)

Mario Kart Tour has quite the reputation on this wiki in terms of pages, at one time nearly forming the top ten of the largest pages here in terms of bit size. However, what was glossed over was the size of Tour's template, being large enough to hold several templates within itself, and making the page, should the user click on it, almost double in length, more so with the other templates open. Using DS DK Pass as an example, a page for a race course that doesn't have a lot of information on it making for a relatively quick read, is now nearly half taken up by the monstrously large Mario Kart Tour template.

A total of four sub templates exist within the Mario Kart Tour template: Characters (and their skins), Vehicle Parts, Courses, and Other (miscellaneous). For example, if the Courses template were split off and applied to DS DK Pass' page, it would make for a much more palatable experience for those looking for courses found in Tour, rather than making the reader scroll for a centuries and looking for it amongst a sea of numerous skins and kart parts.

Proposer: MightyMario (talk)
Deadline: November 24, 2024, 23:59 GMT

Support

1. MightyMario (talk) I heartily endorse this proposal.
2. Tails777 (talk) I kinda agree with this. I feel this would be a bit more organized too, so people don't have to scroll through loads of characters, karts and other things just to find the tracks section. I have found myself on numerous occasions jumping from track articles and with Tour's template, it was rather irritating searching through massive sections of characters and tours just to find tracks. I support this idea.
3. Waluigi Time (talk) We've split navigation templates for much less, this makes sense for the sheer amount of content in the game.
4. ThePowerPlayer (talk) A navigation template that buries content in an area larger than an entire computer screen defeats the purpose.
5. Super Mario RPG (talk) Agreed with all.
6. EvieMaybe (talk) per all
7. Dark Jonathan (talk) I didn't know Tour templates gave so many problems, but hey, that's a good proposal.
8. BMfan08 (talk) I was just thinking about this the other day when I was changing tense on tour articles. It's definitely a lot to take in, and it's also overlooked because people don't put into a template quite as much as they do a page. I agree with this idea.
9. SeanWheeler (talk) Per all.
10. PnnyCrygr (talk) This will make page-by-page navigation of MKT articles more efficient or convenient. Supporting.
11. Mario (talk) The size of this nav template would make Wario proud, but I'm sure this complaint has already been forwarded to a lot of aspects of Mario Kart Tour content on this wiki.

Comments

I think alternatively, they could be given different collapsible sections, like we do with the galleries template. But I agree it is overwhelmingly enormous. Doc von Schmeltwick (talk) 12:58, November 10, 2024 (EST)

We're talking about the navigation template at the bottom of these pages, right? Because that's the only Tour-related template on the DS DK Pass article (subpages notwithstanding) and it's indeed quite huge. If we do split it off into several subtemplates, I suppose it'd be comparable to various levels from specific platformer titles having a navbox template for themselves instead of sharing a primary nabvox template with the rest of that game's content (e.g. Super Bell Hill featuring {{SM3DW levels}} instead of {{SM3DW}}); or the existence of various navigation templates for the various microgames or minigames in specific WarioWare or Mario Party title. So while it's atypical for us to split Mario Kart-specific nav templates, it's not unheard of for us to split off nav templates in the first place. rend (talk) (edits) 17:04, November 10, 2024 (EST)

Allow certain proposals to close after one week

Alright, hear me out.

Recently, a proposal has passed, making all proposals last for 2 weeks instead of 1. Though I was opposed to this change, I can definitely now see the benefit of giving proposals more discussion time. However, not all proposals need that extra week. Some proposals leave zero room for discussion, because everyone already agrees with the proposer. So the proposal just sits for another week and the outcome obviously isn't going to change. I propose to introduce a rule that would close proposals with high participation and unanimous consensus after one week, like it was before that. Let me explain:

1. If a proposal has 10+ votes with no opposition or 12+ votes with 1 oppose vote by the end of the first week, it passes.
2. Same applies to proposals with unanimous opposition, 12+ oppose votes with only 1 support vote (that being of proposer, or 10 if the proposer didn't vote) closes a proposal at the end of the first week.
3. If this condition isn't met, a proposal runs for two weeks as expected, even if it gets 10 votes after one week. In short, the proposal only has one opportunity to get closed early: at the end of the first week.
   Proposals with more than two options also abide by this rule, though they're very unlikely to ever close early. Though it can happen! If the proposal has multiple options, it probably needs more discussion time anyway, so I decided not to touch those at the moment.
4. If the proposal has an ongoing discussion in the comments section or the proposal may for any other reason benefit from running for two weeks to generate more discussion (e.g. writing guidelines, wiki policy changes, etc.), both the proposer and the admin team have the right to add the "Do not close early" tag below the deadline (they then need to state their reasoning for doing so in the comments). This will ensure proposals with unanimous support that need that extra week of time can still get it.
5. When closing the proposal early, the deadline needs to be crossed out and "Closed early on ..." needs to be added instead:

Deadline: November 27, 2024, 23:59 GMT Closed early on November 20, 2024, 23:59 GMT

This rule will not apply to talk page proposals

I believe this change to be a good compromise between giving proposals more discussion time and eliminating proposals that can do without it.

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

Support

1. Axii (talk) This can be a good compromise
2. Nintendo101 (talk) Per proposal.
3. Altendo (talk) Why drag on proposals that already have anonymous support? Per proposal.
4. Camwoodstock (talk) This makes sense to us! We are a little on-the-fence about the exact thresholds, but this is definitely a pretty elegant system to help unanimous proposals pass sooner, and given it has only one method to proc, it leaves it pretty shenanigan-proof.
5. ThePowerPlayer (talk) Sounds good!
6. EvieMaybe (talk) per!
7. Killer Moth (talk) Sounds like a good idea. Per proposal.
8. OmegaRuby (talk) An idea I and others brought up in the initial proposal that made proposals two weeks long. Yes!

Comments

Would this also apply to talk page proposals? Never mind, I can't read. I do think this could apply to TPPs though. What's your reasoning for it not? Technetium (talk) 14:09, November 13, 2024 (EST)

Talk page proposals just aren't as visible to the community as mainspace proposals are, so I believe they should still last for two weeks regardless. They also do not clutter the proposals page. I may consider adding it as a third option. Axii (talk) 14:13, November 13, 2024 (EST)

Axil, I think it's a better idea to replace a direct URL ([https://www.mariowiki.com/MarioWiki:Proposals/Archive/70#Revise_how_long_proposals_take:_.22IT.27S_ABOUT_.28how_much.29_TIME_.28they_take.29.22 proposal]) to a direct wikilink ([[MarioWiki:Proposals/Archive/70#Revise how long proposals take: "IT'S ABOUT (how much) TIME (they take)"|proposal]]) so that it removes bytes on the archive page and doesn't always open a new window when clicked. Just my recommendation, though.

Also, what happens with proposals that somehow retain the aspect ratio of at least 12 to 1 (like 25 support votes to 2 oppose votes)? I feel like the case for closing proposals after one week with oppose votes should be changed to a ratio of at least 12 to 1, not at least 12 support votes and only 1 oppose vote. Altendo 15:07, November 13, 2024 (EST)

I think clause 2 needs to explicitly account for proposals where the proposer does not vote in support of their own proposal. It's not the least common thing in the world, after all — and if we miss it, we could have people retracting their solitary vote to buy more time, which would not be an intended feature of this. Ahemtoday (talk) 02:59, November 14, 2024 (EST)

This proposal only considers two-option proposals. We could adapt rules 1 and 2 to take into account any proposal, regardless of the number of voting options: "A proposal must meet these criteria to be closed early: the first place option must have at least 10 votes and at least 92% approval, and the second place option must have at most one vote". This is equivalent to rules 1 and 2 for two-option proposals (though I don't quite understand what would happen in rule 2 if the only support vote is from a user who is not the proposer), and it would work well with {{proposal check}}. Jdtendo^(T|C) 08:00, November 21, 2024 (EST)

It is too late to modify the proposal now, though I like your idea. Axii (talk) 08:36, November 21, 2024 (EST)

Since there is support for an early close rule, I'm going to add one, but I'm canceling this proposal since I want it to be a little different than what's proposed. 1) It should be applicable to all proposals regardless of the number of options. 2) Let's go with a margin of 8 or more votes with at least 80% approval. It's a little more lenient, but given that up until recently many big proposals ended after a week with much closer margins, I don't think we should shy away from closing heavy-consensus proposals after a week. This will further help to reduce clutter and process our proposals more efficiently where it is reasonable to do so. 3) Let's leave the "Do not close early" stuff up to wiki staff only. Allowing proposers to use it when their proposal is failing but there is no real hope would enable them to drag things out and defeat the whole point of having this rule. This is all about retaining the benefits of both two-week and one-week proposals simultaneously: Heavy-consensus proposals simply become one-week proposals, and for that not to happen should be a somewhat rare staff decision. 4) Even though I was unsure about making all proposals two weeks, one thing that I do like about the change is that there are fewer arbitrary differences between proposals and TPPs. In that spirit, this rule should apply to TPPs as well. If it's a good rule, then I think it's a good rule for both. I'm not concerned about TPP visibility because the required vote margin handles that: If a TPP falls under the radar, then it will fail to get the number of votes needed in a week. But if it is able to get the required votes, then it must have been visible enough to do so. 5) The #5 part about noting the early close in the archive sounds good. 6) I also need to reduce the proposal editing timeframe of six days since now that it's possible for a proposal to conclude after seven days, there needs to be a larger window than one day between the editing cutoff and a proposal's potential closure to ensure that people have enough time to be made aware of any edits and adjust their vote if needed. Let's try four days. 7) We will monitor and make further adjustments if needed. Thank you --Steve (talk) 16:28, November 21, 2024 (EST)

What to do with Steve and Ike

With a margin of 10 votes, at least 80% approval is required to close one week early. 100% approve the first place option. CLOSE EARLY

Despite that now the Smash Bros. characters don't get their own articles but instead grouped into lists by game, the actual Mario characters that have the same name as Smash fighters (being Steve from NES Open Tournament Golf and Ike from The Super Mario Bros. Super Show!) don't have their identifiers removed. This has been brought up before, however no actions have been taken. I think there is some good points to these identifiers being removed.

• Roy, Alex and Zombie don't have identifiers despite also sharing names with Smash Bros. characters.
• If a casual user wanted to find information on Steve from Minecraft, they'd go to the Minecraft Wiki. If they wanted more detailed information for Steve in Smash, they'd go to the Smash Bros. Wiki, not here.
• This could easily be distinguished with the "about" template.

With these points, I really don't see any reason for these identifiers. They're pointless if anything. This is a Mario wiki. Mario elements should take priority over things we don't fully cover anymore.

Proposer: Starluxe (talk)
Deadline: November 28, 2024, 23:59 GMT Closed early on November 21, 2024, 23:59 GMT

Support

1. Starluxe (talk) Per proposal!
2. EvieMaybe (talk) i feel some ways about the level of coverage we give Smash stuff. per proposal
3. Nintendo101 (talk) Per proposal.
4. Ahemtoday (talk) Very straightforward update to these article names given the merging.
5. UltraMario (talk) Per all.
6. Camwoodstock (talk) Makes sense to us. Per proposal.
7. ThePowerPlayer (talk) Per proposal.
8. Jdtendo (talk) Per proposal.
9. Killer Moth (talk) Per all.
10. BMfan08 (talk) Per all.

Tag images of bind-posing models for reuploading

It's been two years since the previous proposal had passed. Now let's talk about tagging images of bind-posing models for reuploading. Take this image for example. As you can see, this image is a bind-posing model. Once this proposal passes, we'll be able to tag every bind-posing model with this:

{{image-quality|Bind-posing model; should be replaced with a rendered game model}}

That way, if a bind-posing model is reuploaded as a rendered game model that serves as a replacement, we'll be able to reuse it as an infobox image.

Proposer: GuntherBayBeee (talk)
Deadline: November 29, 2024, 23:59 GMT

Support

1. GuntherBayBeee (talk) Per proposal

#ThePowerPlayer (talk) Like I said in the other proposal, T-poses are generally not how characters are supposed to look. If this is any indication, the wiki should favor game accuracy in images.

Oppose

1. Nintendo101 (talk) I think it is great when users replace images of bind-posed (or "t-posed") models with organically rendered ones. It is a practice I personally encourage and welcome. However, I do think there can be educational and illustrative purposes to bind-posed models, and I think a blanket rule would put unnecessary pressure on the users of this site to render models when a bind-posed one can be more than serviceable, and may even discourage the cataloging of 3D assets in the future if a user cannot render them. Rendering models is a very time-consuming process, and I think it is healthier to just allow users to replace the bind-posed images we have if they can. Not require them to. Perfection is the enemy of the good.
2. EvieMaybe (talk) this seems better handled on a case-by-case basis rather than a full sweep
3. Waluigi Time (talk) Per all.
4. Hewer (talk) Per all, a hard rule isn't necessary here.
5. ThePowerPlayer (talk) Per all.
6. Camwoodstock (talk) Per all, especially Nintendo101. Given there are scenarios where bind-posed/T-posed models are actually more illustrative than properly rigged alternatives, we should probably handle these on a case-by-case basis.
7. Mario (talk) Tag them if they're bad quality, not because they're t-posed.

Comments

Wording should be changed to "bind pose" since not all characters are T-posed, especially non-bipeds (like Yoshi from Super Smash Bros. Melee or Brawl, Wiggler, Buzzy Beetles, Piranha Plants, and more) and A-pose exists as a default pose too. In addition, models technically aren't "t-posing", they're modeled this way before animations and a rig are applied to them, the wording makes them look like they're animating when they're not. Ray Trace^(T|C) 20:36, November 15, 2024 (EST)

Does this proposal advocate replacing these ripped models with ones that are posed from a screenshot or posed in a 3d program with ripped animation files? Not all models are ripped with animations, so it's a bit of a task to undertake if you really want models with animations AND a rig (let's not get started in lighting, which is a separate skillset that's demanded from renderers; not many people get the lighting very good, no offense!); a chunk of models tend to not have a rig, much less an animation. Additionally, some t-posed models are great to use when comparing models or viewing models as they are. File:MLNPC.png is an example where it's easy to compare the proportions of Mario, PC Luigi, and NPC Luigi. Sure, you can probably put them all in a orthographic lineup in the same keyframe of a shared animation, but due to the arms, legs, spine, and head all straightened out, it's better to illustrate in T-pose imo. It's me, Mario! (Talk / Stalk) 21:00, November 15, 2024 (EST)

Miscellaneous

None at the moment.