MarioWiki:Proposals

Current time: Sunday, December 22nd, 01:15 GMT

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

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

How to

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

Rules

1. Only autoconfirmed users may create or vote on proposals. Anyone is free to comment on proposals (provided that the page's protection level allows them to edit).
2. Proposals conclude at the end of the day (23:59) two weeks after voting starts (all times GMT).
   • For example, if a proposal is added at any time on Monday, August 1, 2011, the voting starts immediately and the deadline is two weeks later on Monday, August 15, at 23:59 GMT.
3. Users may vote for more than one option, but they may not vote for every option available.
4. Every vote should have a strong, sensible reason accompanying it. Agreeing with a previously mentioned reason given by another user is accepted (including "per" votes), but tangential comments, heavy sarcasm, and other misleading or irrelevant quips are just as invalid as providing no reason at all.
5. Users who feel that certain votes were cast in bad faith or which truly have no merit can address the votes in the comments section. Users can ask a voter to clarify their position, point out mistakes or flaws in their arguments, or call for the outright removal of the vote if it lacks sufficient reasoning. Users may not remove or alter the content of anyone else's votes. Voters can remove or rewrite their own vote(s) at any time, but the final decision to remove another user's vote lies solely with the 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.
6. If a user makes a vote and is subsequently blocked for any amount of time, their vote is removed. However, if the block ends before the proposal ends, then the user in question holds the right to re-cast their vote. If a proposer is blocked, their vote is removed and "(blocked)" is added next to their name in the "Proposer:" line of the proposal, which runs until its deadline as normal. If the proposal passes, it falls to the supporters of the idea to enact any changes in a timely manner.
7. Proposals cannot contradict an already ongoing proposal or overturn the decision of a previous proposal that concluded less than four weeks (28 days) ago.
8. If one week before a proposal's initial deadline, the first place option is ahead of the second place option by eight or more votes and the first place option has at least 80% approval, then the proposal concludes early. Wiki staff may tag a proposal with "Do not close early" at any time to prevent an early close, if needed.
   • Tag the proposal with {{early notice}} if it is on track for an early close. Use {{proposal check|early=yes}} to perform the check.
9. 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.
10. If a proposal reaches its deadline and there is a tie for first place, then the proposal is extended for another week.
11. 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.
12. Proposals can be extended a maximum of three times. If a consensus has not been reached by the fourth deadline, then the proposal fails and cannot be re-proposed until at least four weeks after the last deadline.
13. 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.
14. After a proposal passes, it is added to the appropriate list of "unimplemented proposals" below and is removed once it has been sufficiently implemented.
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 cancel 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 formatting

Below is an example of what your proposal must look like. If you are unsure how to set up this format, simply copy the following and paste it into the fitting section. When updating the bracketed variables with actual information, be sure to replace the whole variable including the square brackets, so "[insert info here]" becomes "This is the inserted information" and not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but the objective(s) of each voting option must be clearly defined. Such options should also be kept to a minimum, and if something comes up in the comments, the proposal can be amended as necessary.

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

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

====[option title (e.g. Support, Option 1)]: [brief summary of option]====
#{{User|{{subst:REVISIONUSER}}}} [make a statement indicating that you support your proposal]

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

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

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

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

Talk page proposals

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

All active talk page proposals must be listed below in chronological order (new proposals go at the bottom) using {{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.

List of ongoing talk page proposals

• Move Shadow (character) to Shadow (Sonic the Hedgehog) (discuss) Deadline: December 23, 2024, 23:59 GMT
• Move "Rare Ltd." to "Rareware" or "Rare" (discuss) Deadline: December 25, 2024, 23:59 GMT
• Make changes to List of Smash Taunt characters (discuss) Deadline: December 27, 2024, 23:59 GMT
• Tighten Category:Deceased characters (discuss) Deadline: December 27, 2024, 23:59 GMT
• Merge Cascading Stone, vanishing platform, and moon platform with Falling Platform (discuss) Deadline: December 28, 2024, 23:59 GMT
• Add to-do tasks on the Main Page (discuss) Deadline: January 1, 2025, 23:59 GMT
• Rename the NES Template (discuss) Deadline: January 4, 2025, 23:59 GMT
• Merge the list of show hosts in All Night Nippon: Super Mario Bros. (discuss) Deadline: January 4, 2025, 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)

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

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

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

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

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

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

Split off the Mario Kart Tour template(s), MightyMario (ended November 24, 2024)

Split major RPG appearances of recurring locations, EvieMaybe (ended December 16, 2024)

Talk page proposals

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

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

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

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

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

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

Determine how to handle the Tattle Log images from Paper Mario: The Thousand-Year Door (Nintendo Switch), Technetium (ended November 30, 2024)

Merge False Character and Fighting Polygon/Wireframe/Alloy/Mii Teams into List of Super Smash Bros. series bosses, Doc von Schmeltwick (ended December 2, 2024)

Writing guidelines

Determine a minimum number of glitches in a game to warrant a separate list article

I've noticed some strange discrepancies regarding how glitches are handled when a game has only 3 or 4 of them documented here. Wario Land 4 has a separate article for its 3 glitches (List of Wario Land 4 glitches), but every other game with 3 glitches simply has those glitches merged with the game's page. Specifically, Mario vs. Donkey Kong, Super Mario Strikers, Paper Mario: The Thousand-Year Door (Nintendo Switch), and, most glaringly, Wario Land 3 have sections for glitches rather than separate lists.

More complicated is figuring out how to deal with games with 4 glitches. Of the 6 games with 4 documented glitches:

• 4 of them have glitches merged into the main article: Super Mario World: Super Mario Advance 2, Donkey Kong Country: Tropical Freeze, Donkey Kong Land, Mario + Rabbids Kingdom Battle
• 2 of them have separate "List of glitches" articles: Mario vs. Donkey Kong: Mini-Land Mayhem!, Super Mario Advance

I put forward this proposal to determine a minimum number of glitches for the creation of "List of glitches" articles. That way, there is consistency between games with the same number of documented glitches. Additionally, if new glitches are documented later that brings the total number over this minimum, a new page can easily be created without the need for a proposal, as the editor can cite this proposal.

Option 1

The minimum number of glitches should be 3. "List of glitches" pages would be created for Mario vs. Donkey Kong, Paper Mario: The Thousand-Year Door (Nintendo Switch), and Wario Land 3 to match that of Wario Land 4.

Option 2

The minimum number of glitches should be 4. List of Wario Land 4 glitches would be deleted and its glitches merged into the main game's article. "List of glitches" pages would be created for Super Mario World: Super Mario Advance 2, Donkey Kong Country: Tropical Freeze, Donkey Kong Land, and Mario + Rabbids Kingdom Battle.

Option 3

The minimum number of glitches should be 5. List of Wario Land 4 glitches, List of Mario vs. Donkey Kong: Mini-Land Mayhem! glitches, and List of Super Mario Advance glitches would be deleted, with the glitches merged into each game's main article.

Do nothing

There should be no concrete minimum, and whether glitches should be split or not should be discussed on a game-by-game basis.

I could continue with 6, 7, etc., but I feel once this point is reached there is enough to warrant separate "List of glitches" articles, especially since game articles are typically long and images are usually needed to showcase glitches, taking up more space.

Proposer: Technetium (talk)
Deadline: August 29, 2024, 23:59 GMT

Option 2

1. Technetium (talk) Second choice.

Option 3

1. Technetium (talk) First choice. I am a bit torn between Options 2 and 3, but I prefer this one as I feel 4 glitches can easily fit on a game's page, as seen with the examples above.
2. Hewer (talk) I don't particularly mind what the minimum number of glitches is, but I agree that there should be a minimum in order to have some more consistency, and a smaller minimum may cause unnecessary splits of small glitch lists, so I'll go for this option.
3. DryBonesBandit (talk) Per all.

Comments

From what I can tell, articles on this wiki are usually split based on size, not the number of headings. It's why List of Fortune Street quotes is split into Dragon Quest characters (A-J / K-Z) and Super Mario characters (A-M / N-Z) and why the number of headings in these articles is inconsistent. I think it'd be weird to split lists of glitches based strictly on the number of sections rather than the amount of text since that could lead to very short articles that only list a few very minor glitches that can be described in just a few sentences. Dive Rocket Launcher 22:50, August 15, 2024 (EDT)

Yeah, I'm aware of that. It just feels different here because glitch descriptions tend to be around the same length. If you look at the examples I discussed in the proposal, you'll find there really isn't a noticeable size difference between the pages that have their glitches merged vs separate. Truth be told, I was originally going to just make a talk page proposal to merge List of Wario Land 4 glitches, but the discrepancies with the pages with 4 glitches led to me coming up with this. I'd be happy to hear anyone else's ideas on how to make things more consistent, because the way things are currently is frankly bugging me. --Technetium (talk) 23:02, August 15, 2024 (EDT)

New features

Add the Thanks extension

The Thanks extension is a way to personally thank a contributor without sending them a message directly. It's a kind gesture to show that you appreciate certain edits from someone, such as if they add more content to an article you made or fix grammatical errors. This saves the effort of having to manually message your appreciation if you wanted to give a quick Thanks to the user, though this proposal in no way seeks to replace that; it provides another option for thanking a user.

However, a requirement to installing Thanks is the Echo extension, which is used by Wikipedia, MediaWiki, and many other major wikis. The Echo extension had embedded features of its own, and it could get annoying for some if it gives a message for every 100, 200, 500, or so milestone edits that someone makes (even though it is possible that some may want to keep track of their milestones). Point is, if the Thanks extension is allowed, be wary of changes that the Echo extension would bring. The echo notification also replaces the new message box with a new messages notification at the top right of the screen. Perhaps it is possible to disable some of the default features of Echo, but the point is that this proposal is mainly about allowing Thanks.

On a sidenote, if this passes, the courtesy policy will be updated to prohibit spamming the use of it for consecutive edits made by a user or someone who personally does not wish to have their edits thanked.

Proposer: Super Mario RPG (talk)
Deadline: August 23, 2024, 23:59 GMT

Support

1. Super Mario RPG (talk) As proposer.
2. Pseudo (talk) Per proposal.
3. Mario shroom (talk) As a Wikipedia editor, I support.
4. Ray Trace (talk) Greenlit by Steve, and I massively support this.
5. Sparks (talk) Yes! The element of kindness (AKA Fluttershy) in Mario Wiki form. I support! Per all.
6. Nintendo101 (talk) Wonderful idea.
7. YoYo (talk) sure, there's no harm in this

Comments

I've always wanted this for years now, but I feel this sort of thing requires at least confirming with Steve first. Mario^-HOHO! (Talk / Stalk) 20:27, August 16, 2024 (EDT)

@Mario Maybe someone could ask him. Super Mario RPG (talk) 20:39, August 16, 2024 (EDT)

@Mario I asked on his talk page, and the proposal is allowed. Super Mario RPG (talk) 00:09, August 17, 2024 (EDT)

Removals

None at the moment.

Changes

Shorten disambiguation identifiers "(Super) Nintendo Entertainment System" to "(S)NES"

The console names "Nintendo Entertainment System" and "Super Nintendo Entertainment System" are way too long and clunky, so much so that the abbreviations "NES" and "SNES" are commonly used in the body of articles throughout the wiki, even though we usually don't use abbreviations. And yet, we still use the full console names in the disambiguation identifiers of article names:

• Mario is Missing! (Nintendo Entertainment System)
• Mario is Missing! (Super Nintendo Entertainment System)
• Wario's Woods (Nintendo Entertainment System)
• Wario's Woods (Super Nintendo Entertainment System)

The identifiers are so long that they take up more than half of the article name and are less immediately legible than their respective abbreviations. This is particularly jarring on the Mario is Missing! disambiguation page because the abbreviations are used on the page (e.g., "Mario is Missing!, the NES game") but it links to articles with names containing the full console names ("Mario is Missing! (Nintendo Entertainment System)").

That's why I propose to shorten "Nintendo Entertainment System" and "Super Nintendo Entertainment System" to "NES" and "SNES" respectively in disambiguation identifiers of article names:

• Mario is Missing! (NES)
• Mario is Missing! (SNES)
• Wario's Woods (NES)
• Wario's Woods (SNES)

Please note that there is already an article which uses an abbreviated identifier: "Building World (Mario's Early Years! Fun with Letters for SNES)", although if we decide to keep the full identifiers, maybe we should rename it to "Building World (Mario's Early Years! Fun with Letters for Super Nintendo Entertainment System)" for consistency?

Proposer: Jdtendo (talk)
Deadline: August 20, 2024, 23:59 GMT

Support (SNES)

1. Jdtendo (talk) Per proposal.
2. Super Mario RPG (talk) Per proposal and similarly passed earlier proposal on shortening identifiers of the second and third Donkey Kong Country games.
3. Technetium (talk) Per all.
4. Mario shroom (talk) too long, agree.
5. SeanWheeler (talk) Let's simplify the names.

#Pseudo (talk) Per all.

Oppose (Super Nintendo Entertainment System)

1. Hewer (talk) I don't see much of a problem with long names, and I'd rather go without the inconsistency created by these being the only shortened console names. And yes, I suppose we should move the Building World page too, like how "Beach Volleyball (Mario & Sonic at the London 2012 Olympic Games for 3DS)" got moved to "Beach Volleyball (Mario & Sonic at the London 2012 Olympic Games for Nintendo 3DS)".
2. Camwoodstock (talk) Per Hewer. While these shortened versions do make for fine redirects (and honestly, I kinda hope these do get made for other games in the form of redirects, but that's neither here nor there), we probably shouldn't be enforcing these as being the default name unless it's a part of a global move to abbreviate the console names for the articles of every game--not just one random edutainment game.
3. JanMisali (talk) Per all.
4. Pseudo (talk) Per Hewer and Camwoodstock.
5. Sdman213 (talk) Per all.

Comments (Mario's Early Years! Fun with Letters for SNES)

now there's a bit of a grey area here, what about consoles like Nintendo 64, Nintendo Switch and so on? It'd feel somewhat weird to abbreviate one but not the others, there'd be an inconsistency. - YoYo (Talk) 09:33, August 13, 2024 (EDT)

The thing with those is that the "Nintendo" part is needed or else it could just be confused as a random number (64) or word (switch). They also just aren't as long. Technetium (talk) 09:57, August 13, 2024 (EDT)

Besides, as I said in the proposal, the abbreviations "NES" and "SNES" are commonly used in the body of articles, but other console names are not abbreviated as frequently. For example, here is an extract of the LodgeNet article: "for the SNES, Nintendo 64, and Nintendo GameCube"; note how only the Super Nintendo Entertainment System's name is abbreviated whereas the other console names are written in full. Jdtendo^(T|C) 10:09, August 13, 2024 (EDT)

I think the shortening of N64, GCN, GBA, etc. could use another propasal. SeanWheeler (talk) 21:30, August 13, 2024 (EDT)

@Hewer Okay, The Old Psychic Lady with the Evil Eye Who Reads Fortunes and Knows Everything Before It Happens' name is ridiculous. I want to propose a shortening of the title, but I don't know enough about the character. But that just shows why page names shouldn't be too long. SeanWheeler (talk) 20:27, August 14, 2024 (EDT)

...Not to burst your bubble, but we actually had a proposal to move it to its current name last month. Prior to that, the article was merely titled "The Old Psychic Lady", which from what I can tell was actually never actually used like that in the episode. She introduced herself by the full title of "The Old Psychic Lady with the Evil Eye Who Reads Fortunes and Knows Everything Before It Happens" (whether it used capital letters or not is unknown), and the Marios simply refer her to as the "crazy lady" or "that psycho lady" since they can't properly remember such a long name. Since "The Old Psychic Lady" never was used as one of the official names, and the wiki refers to her by her full name anyway, it was proposed to move the article to the lady's full title (I mean, at least "NES" and "SNES" are officially used abbreviations by Nintendo themselves and their full names were not created for comedic purposes). rend (talk) (edits) 20:50, August 14, 2024 (EDT)

Arguments about the name being "ridiculous" or "too long" were used in the proposal linked to by Arend, and much like with those arguments, you haven't substantiated the claim very well. Why is a long page name "ridiculous" when it's just accurately referring to the subject? Why should we sacrifice accuracy in favour of a shorter page name? What about long page names is in any way disadvantageous? Hewer (talk · contributions · edit count) 05:37, August 15, 2024 (EDT)

Tbh, I'd merge the two Building Worlds together if it were up to me, they're still both represented by the same icon in the map screen and differences can easily be mentioned in the article, it'd also be consistent with the rest of the Mario's Early Years Worlds. Ray Trace^(T|C) 20:09, August 15, 2024 (EDT)

Allow more "History of" articles under two more conditions

This may be a small thing, but unlike the quotes, profiles, and even galleries, there is more restriction on which articles get to be split off into a History page. Please take note that proposal is not about amending the minimum number of bytes needed (150K) to split the History section of an article into its own page. It's about allowing more "History of" pages. The 150K guidelines already does not apply to splitting galleries, profiles, and quotes from the base article.

Should this proposal pass, more History pages would be allowed under the condition of the article either having a General information section with at least two subsections or the condition if there is a single section with a wikitable. This way, if a split were to occur, there's at least more information besides what is contained in the opening section. Luigi, Yoshi, Wario, Princess Peach, and other subjects with history pages all have something in common where their pages have well established General information sections, providing enough context about them, while the History page would serve as a comprehensive read on their individual appearances, which can be summarized on the main article. To me, it feels inconsistent that Wario and Bowser have their History pages split but not their respective partners, Waluigi and Bowser Jr., both of whom are recurring.

The reason I want to give exception if the section has a wikitable is because of the Barrel page, where the barrels section is tucked all the way at the bottom, below a long History section, so it cannot be seen immediately by readers, many of whom may not see the section otherwise.

If the article has been featured in the past (e.g. Chain Chomp), a different proposal would be required before splitting it, or some other democratic matter decided upon by the community (e.g. adding a talk template and overhauling the page in accordance to community input on the talk page).

Proposer: Super Mario RPG (talk)
Deadline: August 23, 2024, 23:59 GMT

Support

1. Super Mario RPG (talk) As proposer.

Oppose

1. Hewer (talk) These seem like very random metrics compared to the logical one of article size, especially since they're based on other sections of the article rather than the actual history section that's being split. History sections are split so that articles stay at reasonable sizes with reasonable loading times, not to aid presentation of the rest of the article. (Honestly I'd rather do less splitting of history sections since it scatters information a bit, but I understand it's a practicality issue to have such huge pages worsening loading times.) If someone who wants information on the subject doesn't look at the whole of the subject's article, that's not our problem - the information on a merged page is still conveyed well, and the "issue" of having to do some scrolling to find certain sections is solved by the contents list at the top of the article that lists the sections.
2. Nightwicked Bowser (talk) I'd honestly rather merge a lot of the split history pages back.
3. Nintendo101 (talk) per Nightwicked Bowser.
4. SeanWheeler (talk) These split history pages are longer than Waluigi's entire page. Waluigi doesn't need to split when his page isn't long enough.
5. TheUndescribableGhost (talk) Firstly, Bowser Jr. does have his own history page and secondly, I still think those pages are pretty easy to scroll through and find the information you want. This is actually the first time I learned that the article size has risen from 100kb, to 150kb, but regardless, that length makes much sense, because the articles could go on like novels at that point and the reasons for splitting articles is to make the pages load less. I'm all for more articles having their history pages split, but this is not the correct way to do it.

Comments

I'm a bit confused, what exactly is this proposal trying to change? Hewer (talk · contributions · edit count) 14:49, August 16, 2024 (EDT)

I'll give an example of what's allowed if this proposal passes. For the first condition, Waluigi article has at least two sections under General information. With that, the ==History== section of Waluigi's article can be split into History of Waluigi. For the second condition, the Barrel page would split into History of barrels so that the "Types of barrels" (which qualifies as a subsection of "General information") is more accessible to the reader for its comprehensive wikitable. Super Mario RPG (talk) 14:56, August 16, 2024 (EDT)

Require citations for names in other languages

Recently, the issue of confirming names in other languages has been discussed on the wiki's Discord server. Put simply, there is a high likelihood that many of these names are fake or otherwise inaccurate, and as an English wiki, the majority of the userbase is unable to independently verify the accuracy of these names. As such, I believe it should be made mandatory for every name listed in the names in other languages sections to have a citation attached to it. Yes, this will be very, VERY difficult to do considering the sheer number of pages that will need to be gone through, but I think it is better to address this problem now rather than later. More and more games and media will release the longer we wait, only adding more to the workload.

Proposer: Technetium (talk)
Deadline: August 25, 2024, 23:59 GMT

Support

1. Technetium (talk) As proposer.
2. Nintendo101 (talk) Per proposal. Misinformation is easy to get into a record and hard to remove. Best we avoid creating Brazilian aardvarks.
3. Sparks (talk) Per all.
4. Super Mario RPG (talk) Strongly agree.

Oppose

1. Jdtendo (talk) Per my comments below.

Comments

Goomther's Italian name is Goombolone. Source: that's his name in the Italian version of the game. Chef Soulfflé's Dutch name is Kok Eauvain. Source: that's his name in the Dutch version of the game. Destiny Del Vecchio's European French name is Allison Ledestin. Source: that's her name in the European French version of the movie. In the above cases where the name is found in only one piece of media, the source would be completely redundant because it's evident that the source is the localized version of the game or movie where the character appears; that's for the same reason that we don't require citations for English names in those situations. I feel that the scope of this proposal is way too broad and should be focused on subjects for which the source is not evident. Jdtendo^(T|C) 12:52, August 18, 2024 (EDT)

Some of the Dr. Mario World pages were taken from the datamine (examples: ice fan, Muddy Coin), because when the game's service was shut down, there really is no way to verify the different languages. And thus, I felt that the datamine has accurate information because it came directly from the game. How would those be sourced? (Also unrelated to this proposal, but I would like to add is that the translation sections for those terms are incomplete.) Winstein (talk) 12:57, August 18, 2024 (EDT)

Miscellaneous

None at the moment.