MarioWiki:Proposals

Current time: Monday, December 30th, 18:29 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 acceptable (including "per" votes), but tangential comments, heavy sarcasm, and other misleading or irrelevant quips are just as invalid as providing no reason at all.
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

• Merge Cascading Stone, vanishing platform, and moon platform with Falling Platform (discuss) Deadline: January 4, 2025, 23:59 GMT
• Rename the NES Template (discuss) Deadline: January 4, 2025, 23:59 GMT
• Split the theme songs from the list of Donkey Kong Country (television series) songs (discuss) Deadline: January 5, 2025, 23:59 GMT
• Rename Mario & Sonic (series) to Mario & Sonic at the Olympic Games (series) (discuss) Deadline: January 6, 2025, 23:59 GMT
• Rename Shadow to Shadow (enemy), and rename either Shadow (character) or Shadow (disambiguation) to Shadow (discuss) Deadline: January 6, 2025, 23:59 GMT
• Decide what to do with Category:Siblings and Category:Twins (discuss) Deadline: January 7, 2025, 23:59 GMT
• Merge Candy Block with Hard Block (discuss) Deadline: January 7, 2025, 23:59 GMT
• Merge ON/OFF Conveyor Belt with Conveyor Belt, or expand to cover all reversible conveyor belts (discuss) Deadline: January 8, 2025, 23:59 GMT
• What to do about Wiggler Family (discuss) Deadline: January 11, 2025, 23:59 GMT
• Repurpose Template:Stub (discuss) Deadline: January 12, 2025, 23:59 GMT
• Split the Ink Bomb (discuss) Deadline: January 12, 2025, 23:59 GMT
• Split the Giant Bowser battle Refreshroom (discuss) Deadline: January 12, 2025, 23:59 GMT
• Keep or Delete File:Spiny Shell PMTTYD.png (discuss) Deadline: January 12, 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)

Stop integrating templates under the names of planets and areas in the Super Mario Galaxy games, Nintendo101 (ended December 25, 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)

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

Make changes to List of Smash Taunt characters, Hewer (ended December 27, 2024)

Merge the list of show hosts in All Night Nippon: Super Mario Bros., Axii (ended December 28, 2024)

Writing guidelines

Change how "infinitely respawning" enemies are counted in level enemy tables

Currently, the wiki lists enemy counts for each level in tables located in that level's article. This is all well and good, but the problem arises when infinitely respawning ones (like piped ones) are included. As seen here, this is awkwardly written as

• "[number] (not including the infinite [enemy] spawning from [number] [method]),"

and why shouldn't it include them? That method of writing is ungainly, misleading, and bloats the table's width unnecessarily. Therefore, I propose the alternate writing of

• "[number] + (∞ x [number]),"

with the "x [number]" and parentheses being removed if there is only one case. So in the linked example, it would be "6 + ∞," which says the same thing without contradicting itself with a lengthy diatribe.
(Also I had to restrain myself from using * rather than x because that's how I'm used to writing multiplication in equations. Thanks, higher-level math classes defaulting to "X" as a variable! But the asterisk could be used too, anyway.)

Proposer: Doc von Schmeltwick (talk)
Deadline: September 30, 2024, 23:59 GMT

Support

1. Doc von Schmeltwick (talk) - Per
2. Altendo (talk) - This doesn't sound like a bad idea, although I do think there should be an asterisk like "*" instead which leads to a note saying "not including the infinite [enemy] spawning from [number] [method]", as enemies can spawn in different ways, and showing how they spawn could still be useful. If we just show "∞ x [number]", it wouldn't show how Goombas are spawned in (the linked page doesn't specify how they are spawned in otherwise). But I do like the idea of shortening the "count" section of tables.

#ThePowerPlayer (talk) Per Altendo. This formatting is much better, but I also think some note of where the infinite enemy spawner(s) originate from should be preserved.
#Super Mario RPG (talk) Per all.

Oppose

1. Hewer (talk) I don't see the benefit of changing this. The current wording is straightforward and succinct, I'd expect the reader to understand "6 (not including the infinite Goombas spawning from one Warp Pipe)" easily. Changing it to "6 + ∞" just makes it less clear for no reason, I'd definitely be confused if I saw that and didn't know this specific context. The fact that the other support votes have also brought up how doing this risks losing the specific information completely (and suggested a more long-winded solution that seems to contradict the proposal) compels me to oppose this more.
2. Waluigi Time (talk) Per Hewer.
3. FanOfYoshi (talk) Per all.
4. Axii (talk) Per Hewer
5. SolemnStormcloud (talk) Per all.
6. EvieMaybe (talk) we don't need to throw a mathematical equation at people
7. Sparks (talk) Per all.
8. ThePowerPlayer (talk) I realized that this only makes sense if you have it explained to you like in the proposal description, which defeats the purpose.
9. Arend (talk) I feel that "[number] (+ [number] infinite spawn points)" would be less awkward to write than what we currently do and more understandable fir most people than what is proposed here
10. Killer Moth (talk) Per all.
11. TheFlameChomp (talk) Per all.

Comments

@Hewer - "succinct" would generally imply "short, sweet, and to-the-point," of which the current method is the exact opposite. I'm fine with including an asterisk-note next to the infinity, but the current one is much too bloated, outright admits to stating false information, and since the tables are center-aligned with that horizontal-bloat, it makes it look incredibly awkward. Doc von Schmeltwick (talk) 12:41, September 17, 2024 (EDT)

I guess we just have totally opposing opinions on this one, because I don't personally find ten words of explanation to be "much too bloated", would rather "state false information" (not really what's happening because it's immediately clarified and the only way not to state any "false" info would be to just put "∞" which helps no one) than obscure the meaning of what we're trying to say, and I don't at all think the somewhat wider tables look "incredibly awkward". This is a case where I feel giving more explanation than "6 + ∞" is necessary for the sake of conveying clear information, so I'd rather prioritise that over having a thin table (which I still don't really see why that's so desirable). Hewer (talk · contributions · edit count) 03:19, September 18, 2024 (EDT)

If this proposal passes, I think that a dedicated template should be made; something like {{infinite respawn|5|3}} that would produce "5 + (∞ × 3)". Or at the very least, use an actual "×" symbol rather than "x". Jdtendo^(T|C) 12:08, September 19, 2024 (EDT)

I dislike the idea of hiding details in easily missable hover text and don't really see the benefit of using it. It just makes it more convoluted. Hewer (talk · contributions · edit count) 11:12, September 20, 2024 (EDT)

I'll refrain from voting because I have a visceral reaction to anything that resembles a math formula, and I want as little as possible for personal preference to seep into my vote. That's not to say I don't understand what's being proposed, in fact it makes perfect sense if you're aiming strictly for concision, but you'd need to take into account how accessibly that information is communicated--you'd need to establish that "infinity symbol" stands for infinite enemy spawning point, which is not immediately clear. At that point, you'd go for a relatively lengthy explanation nonetheless. Though, I agree that the phrasing in that page you linked doesn't sound inclusive. I think something like "5 individual, 3 infinite spawning points" works better if we're going down this path.
If the proposal passes, I'd like to see it implemented in the manner Jdtendo suggests above.
EDIT: I'm aware there's already plenty of math on this wiki that has potential to confound people, but in that case, not only is its succinctness a better way to explain how the game's scoring system works (as opposed to paragraphs-long descriptions), but it's taken straight out of the game as well. I'd say, use math formulas only when you're sure prose would be of less service to its intended audience: people looking up how many enemies are in a level aren't necessarily interested in complex gameplay dynamics. -- KOOPA CON CARNE 13:12, September 19, 2024 (EDT), edited 14:55, September 19, 2024 (EDT)

I'd personally prefer if this was notated with ω instead of ∞, something like "3ω+5", but that would probably be too confusing to anyone not already familiar with transfinite ordinal notation. jan Misali (talk · contributions) 10:01, September 21, 2024 (EDT)

This should be written "ω⋅3+5" because 3⋅ω = ω; multiplication on transfinite ordinal numbers is not commutative. Jdtendo^(T|C) 12:40, September 21, 2024 (EDT)

Maybe just have a table for finite enemies and a table for infinite enemies? There's horizontal space for both. Salmancer (talk) 11:33, September 21, 2024 (EDT)

That just needlessly splits information, which I again don't see the benefit of (and I still don't really see how there's a problem here that needs fixing anyway). Hewer (talk · contributions · edit count) 21:26, September 21, 2024 (EDT)

Figure out how to handle {{classic}} and {{classic-link}} templates when discussing Mario Kart Tour classic courses

This wiki has two templates used to format classic courses in the Mario Kart series: {{classic}} and {{classic-link}}. These templates convert text like "3DS Shy Guy Bazaar" into a format that closer resembles the one seen in games, with the prefix being written as such, a prefix, and not part of the courses name. So "3DS Shy Guy Bazaar" becomes "3DS Shy Guy Bazaar". However, there's an exception this wiki seems to have regarding this template: classic courses in Mario Kart Tour.

This is because the game does not structure the title of courses in such a way: instead it writes the prefix as large as the rest of the name, so it's written as "3DS Shy Guy Bazaar". However, I feel this creates a lot of inconsistency and confusion here on this wiki. For example, the page for a course like 3DS Rock Rock Mountain, a course featured as a classic in and out of Tour structures fellow course names both ways, with and without the template, simply because of the game the classic course appears in. To make things more confusing, when a Tour section on a course's page discusses classic courses outside of Tour, it uses the template, as seen in a few course pages. Additionally, page titles for courses that are only classics in Tour still use a smaller font for the page name, such as GBA Lakeside Park. Finally, some courses in Tour don't even adhere to this rule that has been enforced before, such as Wii Maple Treeway.

(I cannot find the edit log, however I was informed by a moderator here that it is a rule that is enforced a while back)

So this proposal is asking for one thing: an enforcement to be decided on.

The options are simple:

• Use the templates for all references to classic courses.
• Not use the template when referring to classic courses in Tour.

RMX courses will not be affected by this since the "RMX" is established to be part of the course's name.

Proposer: YoYo (talk)
Deadline: October 2, 2024, 23:59 GMT

Use the templates for all classic course links

1. YoYo (talk) per my proposal, I think that the template formats them in a way that distinguishes the prefix from course name, and I think consistency is important here.
2. Tails777 (talk) I really don't think we need to be that accurate with the way things are written. Just because Tour doesn't have the system prefixes in a slightly smaller font, doesn't mean we have to follow in suit. Heck, when I removed some images from infoboxes and put them in respective sections, I kept using the {{classic}} templates regardless of which game section they were in. Why would the size of the font be that big of a deal? I think using the template for all classic courses is just the way to go.
3. Ahemtoday (talk) I think being accurate to the text size parts of a name are written with is different from being accurate to the name itself — and I find the former kind of unnecessary.
4. Jdtendo (talk) Per all.

New features

None at the moment.

Removals

None at the moment.

Changes

Add film and television ratings to Template:Ratings

Regarding ratings on the games we cover on this wiki, it's usually done very well and even shows off obscure rating companies hardly anyone talks about. It's educational and shows how the world rates a Super Mario game. However, when it comes to television shows and movies, they do not get the same treatment. Television shows don't even have ratings in their infobox. And while the movies do, they not only list just the MPAA, which for people who live in the United Kingdom or other countries, is not representative of the majority of the world, it's just the text, "PG". Sure, most people know it means "Parental Guidance," but imagine if we included more ratings. It's not super easy to find ratings for films and television shows in general, other than IMDB and there are no sources for proof of these ratings. When it comes to the Canadian Home Video Rating System, I can hardly find what rating was applied to that particular movie/TV show and I remember not being lucky for searching any other ratings for other movies (personal experience, but I remember searching on one of these websites and the site was rather buggy or didn't have the film/show in question).

The better solution is to add film and television ratings to the rating template so we can provide a wide variety of ratings for movies and television shows. In this case, users from around the world can view how movies are rated in almost every country. As for what ratings we add, it's a bit tricky. Because there is a lot, I would need some help here. Regardless, I got some EFIGS ratings in question. If you have more ratings, please let me know and I'll add it to the proposal These are split up into film and television.

Film

• Motion Picture Association film rating system (MPAA)
• British Board of Film Classification (BBFC)
• Freiwillige Selbstkontrolle der Filmwirtschaft (FSK)
• Canadian Home Video Rating System (It can also apply to DVDs of TV shows as well.)

Television

• TV Parental Guidelines

My list so far is not comprehensive, but my idea is to add these ratings (and potentially others) to the template and make the infoboxes look much prettier and more visually educational. I have nothing else to say, so that's about it.

Proposer: TheUndescribableGhost (talk)
Deadline: October 1, 2024, 23:59 GMT

Support

1. TheUndescribableGhost (talk) Rated PR for per proposal.
2. Technetium (talk) Never noticed ratings were missing from TV and movie coverage until now. It feels obvious ratings should be included like they are with games. Per proposal.
3. FanOfRosalina2007 (talk) This is something I never noticed, but I completely agree. I'm happy that there are observant people in this world! Per proposal.
4. Arend (talk) Per all (fun fact: the Dutch rating system for movies and television, Kijkwijzer, is being utilized by NICAM, which happens to also rate games in Europe using PEGI. In fact, PEGI's ratings appear to be based on those of Kijkwijzer)
5. ThePowerPlayer (talk) Per all.
6. Nintendo101 (talk) Per proposal.
7. Sparks (talk) Per all.
8. Mari0fan100 (talk) Per all, especially since movies like The Super Mario Bros. Movie have classification ratings.
9. Killer Moth (talk) Per all.
10. BMfan08 (talk) Per all! (This comment is not yet rated.)
11. EvieMaybe (talk) i cannot fathom a reason someone would oppose this
12. Camwoodstock (talk) How did we miss this? Per proposal.
13. TheFlameChomp (talk) Per all.

Comments

Wait, couldn't this just be a talk page proposal on the template itself? It would affect many pages, yes, but this is specifically about editing a template… I'm honestly not so sure. Technetium (talk) 15:52, September 24, 2024 (EDT)

Split articles for certain official single-game enemy behavior splits

In the early days, before Nintendo was really sure how they wanted to classify enemies, there were some splits that didn't stick - namely, behaviors that were initially unique to a specific subtype, and then became normal alternatives to the base enemies. I'm specifically talking about:

• Sky Blooper - Blooper variant from Super Mario Bros.: The Lost Levels
• Upside-down Buzzy Beetle - Buzzy Beetle variant from Super Mario Bros. 3
• Upside-down Spiny - Spiny variant from Super Mario Bros. 3
• Scattering Blooper - Blooper Nanny variant from Super Mario Bros. 3
• Upside-down Piranha - Piranha Plant variant from Super Mario Land

I make this mainly because the Mario Portal splits each of these for these games specifically, across language borders, despite being a newer source (which is notably a lot more than Boss Bass/Big Bertha gets, so that merge remains correct), along with Upside-down Piranha making the Smash Bros. Piranha Plant list; other instances of similar things occurring that have not (yet) been corroborated by a source like Portal (such as Tobipuku from New Super Mario Bros.) will not be counted. Now, I want to clarify something important: this split only covers the appearances where the official word treats them as distinct enemies. Random upside-down Buzzy Beetles and Piranha Plants in New Super Mario Bros. Wii are not counted, as they are not distinguished from their base species in any way in that game. I see this as similar to Fire Nipper Plant, another SMB3 enemy whose fire-breathing characteristics were given to normal Nipper Plants in a few later games.

I have a demo for these pages in the various sections of this page, along with stuff for the below proposal.

EDIT 9/28: Adding an option for only splitting the two Bloopers.

Proposer: Doc von Schmeltwick (talk)
Deadline: October 3, 2024, 23:59 GMT

Scattering Support

1. Doc von Schmeltwick (talk) - Per
2. FanOfYoshi (talk) Per proposal.

Bloopers only, no upside-down!

1. Nintendo101 (talk) I see no problem with this. Unlike the other proposed splits, normal Bloopers have not inherited the defining airborne traits of Sky Bloopers outside of the Super Mario Maker games, which breaks a lot of conventions for the sake of fun creative gameplay. I do not think it is the same situation as Upside-down Piranha Plant or Spiny.
2. DryBonesBandit (talk) Agreed.
3. Hewer (talk) Blooper proposal

Upside-down Oppose

1. Arend (talk) Maybe a case could be made for Scattering Blooper, but Sky Blooper and Upside-down Piranha Plant also behave (nearly) identical to their regular counterparts. Not to mention that nearly all the regular versions of these enemies have retroactively gained attributes of these enemies too (Buzzy Beetles and Spinies can appear commonly walking on ceilings and dropping down in various games, Piranha Plants can pop out upside down from a ceiling pipe in various games, nearly all Bloopers encountered on land float above the ground; none of these are regarded as distinct variants in those later games), so it's a little weird to me if only those specific versions of enemies are regarded as separate entities but regular versions of these enemies adapting these attributes aren't; feels inconsistent and confusing for a reader.
2. Axii (talk) Per Arend. I feel like it would be an unnecessary split. Nintendo doesn't refer to these enemies separately in any newer games. Sky Blooper may have had a chance, but Super Mario Maker clearly shows that they are just regular Bloopers. I can see Scattering Blooper being split in the future though.
3. SolemnStormcloud (talk) Per opposition.
4. Killer Moth (talk) Per all.
5. EvieMaybe (talk) i can see the case for scattering blooper and MAYBE sky blooper, but i don't think i agree with the philosophy behind the proposal.
6. DrippingYellow (talk) The idea of splitting certain minor behavior differences in enemies, but only in certain games where they are given a specific adjective relating to the thing they do, honestly just sounds ridiculous. If you're going to split some of them, you might as well split all of them, lest you create a glaring inconsistency in the wiki's coverage of these enemy variants.
   Also keep in mind that these individual acknowledgements of upside-down enemies aren't consistent even between these similar-era games; Piranha Plants can be found upside-down as early as The Lost Levels and Super Mario Bros. 3, yet would be confusingly absent from your proposed "Upside-down Piranha Plant" article due to not being called "Upside-down Piranha Plants" (and also kind of throws a wrench into your theory that these were originally special variants before being merged into the main enemy). These upside-down enemies are only listed on Mario Portal when the game's respective manual also mentions them (with apparently a single exception in SMB3's Upside-down Spiny), suggesting less of a confirmation as species and more of an attempt to parallel existing material.
   The only potential exceptions I see here are the Bloopers, particularly the Sky Blooper with its actually distinct appearance. Though, if the red Koopa Troopa, an enemy that has had consistently has a different appearance and behavior from its green counterpart in all mainline games it has appeared in (the black-and-white SML2 with only the ledge-fearing green Koopa doesn't count due to there being no red Koopa to compare with), is too minor a difference to get an article, then how are these any different?
7. Shoey (talk) Per all.
8. Mario (talk) Some of these proposed splits are overkill.
9. Sparks (talk) Per all.

#Hewer (talk) Not opposed to all of these (I'd probably support splitting Sky Blooper), but while I do generally like following official classification of things, having an article for Buzzy Beetles that were upside down in SMB3 specifically and no other game just feels silly and confusing.
#DryBonesBandit (talk) Per all.

Sky Comments

I understand the rationale, but Mario Portal (and most game material) also recognizes things like green-shelled and red-shelled Koopas as distinct from one another and they also have different behaviors from one another. That'd probably be a bigger proposal than you'd be interested in executing, but how would you feel on those types of enemies being split? I at least like the idea of Sky Blooper getting its own article on the face of it. - Nintendo101 (talk) 22:27, September 25, 2024 (EDT)

Those shouldn't be by virtue of the functional distinctions being inconsistent, especially when you get into things like Shy Guys. Most of them use (identifiers) too rather than actual naming differences. Doc von Schmeltwick (talk) 23:09, September 25, 2024 (EDT)

Fair (especially for Shy Guys), though generally, I'm pretty sure red-shelled Koopas mechanically are always the ones that turn when they reach an edge, whereas green-shelled ones don't.

What if, for those enemies, there was a similar scenario as with Koopa Shells, where there is one main article, but also smaller ones for Green Shells and Red Shells for scenarios where the shells have mechanical differences? We could have a main Koopa Troopa article, and then a Koopa Troopa (Green) and Koopa Troopa (Red). - Nintendo101 (talk) 23:50, September 25, 2024 (EDT)

You're only looking in terms of 2D platformers, there. Doc von Schmeltwick (talk) 00:02, September 26, 2024 (EDT)

(I hope this is isn't too tangential - I appreciate your insight on this) I think the only 3D platformer with both Koopa Troopas is Super Mario Galaxy, and they still have mechanical differences from one another in those games.

For platformers and spin-offs where colors are only cosmetic, I think it would be fine for them to share a single Koopa Troopa article (again, similar setup to Koopa Shell). But I understand the resistance to that idea, because it could be messy and difficult to curate. - Nintendo101 (talk) 00:09, September 26, 2024 (EDT)

And there's the black-and-white Super Mario Land 2, where the art shows green, but the behavior's more like typical red ones. Then we get into Paratroopas, where originally green hopped or moved back-and-forth and red moved up-and-down, then games like Super Mario World have red ones moving horizontally or green ones moving vertically. And then there's Cheep Cheep - swimming Cheep Cheeps' colors in SMB1 were purely cosmetic, then SMB3 had lots of behavioral variation among red-colored ones and only one behavior for green-colored ones. I think keeping the "color" ones grouped unless a very notable difference is present (like the Paper Mario and Yoshi's Story versions of Black Shy Guy) is the best way to go in that regard. Doc von Schmeltwick (talk) 00:23, September 26, 2024 (EDT)

@Opposition I see this as a similar case to Gloomba only covering the blue underground Goombas when they are officially split, or Headbonk Goomba only covering headbonking Goombas when they are officially split. Same for the large-sized Chain Chomps and Wigglers sometimes being considered "big" versions and sometimes considered standard. Doc von Schmeltwick (talk) 22:09, September 26, 2024 (EDT)

I see those as a bit different since they have functional or other differences specific to those games, blue Goombas aren't normally stronger than the standard versions. As far as I can tell, the only way Upside-down Buzzy Beetle is more of a variant in SMB3 than it is any other game is in name. Hewer (talk · contributions · edit count) 02:52, September 27, 2024 (EDT)

The fact that Portal, which is recent, bothers to split them for those games specifically rather than ignore it in favor of following what later games do makes me think this is still valid. Especially since Upside-Down Piranhas were also differentiated in Viridi's Piranha Plant list in Smash Ultimate. Doc von Schmeltwick (talk) 13:09, September 27, 2024 (EDT)

Technically, do we know whether Viridi was referring to specifically upside-down Piranha Plants from Super Mario Land, rather than just upside-down ones in general? Not sure if it's different in Japanese, but their placement in the list is notably odd especially if it was meant to be referring to just Mario Land, as they are the last variant listed before the three Petey Piranhas, rather than the roughly release date order the list mostly uses. As for Mario Portal, Nintendo101's point about red and green Koopa Troopas compels me to ignore that. Hewer (talk · contributions · edit count) 15:12, September 27, 2024 (EDT)

They're the only ones that are named as such, so yes. Doc von Schmeltwick (talk) 20:36, September 27, 2024 (EDT)

Uhhh, I'd find sources other than Super Mario Land and the Mario Portal before I confidently make claims like that. Personally, I doubt that these games are the only instances in which the Japanese word for "upside-down" immediately precedes the name of an enemy that happens to be upside-down. DrippingYellow (talk) 01:46, September 28, 2024 (EDT)

Treating it as a label, there are none. Prose, perhaps, but not as a deliberate label. Doc von Schmeltwick (talk) 02:03, September 28, 2024 (EDT)

Again, sources???? The only evidence I could find vaguely supporting you (for the Piranha Plant in Lost Levels at least) is in a scan of the Japanese Super Mario All-Stars guide, which is after you claim they dropped the concept. DrippingYellow (talk) 11:47, September 28, 2024 (EDT)

What Portal is doing is enough, IMO. It shows their "current interpretation" is that they are different enough for a separate listing (without the parentheses, even) specifically in the respective games I listed, but not elsewhere. Doc von Schmeltwick (talk) 13:42, September 28, 2024 (EDT)

@DrippingYellow - Technically, only the Upside-Down Piranha Plants in SML have the point bonus, which is part of how the game defines its enemies. Also, that "paralleling existing material" also doesn't split color, so this doesn't seem inconsistent to me. Doc von Schmeltwick (talk) 20:36, September 27, 2024 (EDT)

...Are you seriously trying to argue that the point value of the enemy is the clincher here? As though enemies are supposed to stay exactly the same with no changes between games? Maybe the developers of SML thought you deserved more of a reward for landing a Superball shot on these upside-down enemies, but how does that specifically support them being considered a unique variant of Piranha Plant in only Super Mario Land? And sure, they called the red Koopa Troopas "Koopa Troopa (Red)" or whatever instead of "Red Koopa Troopa", but simply having a unique name is not the end-all be-all of whether something gets an article or not (Black Shy Guy (Yoshi's Story), the countless articles that we had to give a conjectural name, to name a few).
The problem is simply that versions of enemies that are visually idential and behaviorally similar to their normal counterpart usually don't get split, regardless of whether they have a unique name or not. And somehow, what you're proposing is even more bizarre than that; that these specific enemies in these specific games are Upside-down with a capital "U", and should be split, and the others, lowercase "u", with the exact same behavior, attributes, and appearance, should not. DrippingYellow (talk) 01:46, September 28, 2024 (EDT)

I see this as equivalent to Fire Nipper Plant, which only appeared once in SMB3, and later RPGs gave normal Nipper Plants identical fire breath abilities. And the point value is a notable difference in function. Doc von Schmeltwick (talk) 02:03, September 28, 2024 (EDT)

Even if these truly are separate listed enemies in only these specific games, this is more like the Grinder/Ukiki situation if anything; two completely different enemies from different series that were eventually merged, and we treat them as the same thing. No "Grinder" article that only covers the monkeys in the Yoshi's Island games and not Wooly World. This situation is even simpler than that debacle if you ask me, as we know exactly what to look for in terms of defining traits (that is, they are upside-down). See also: the Helper Monkey article, with all of the uniquely-named-in-Japan variants merged together for the sake of simplicity. DrippingYellow (talk) 11:47, September 28, 2024 (EDT)

The monkeys are mainly a snarl because YNI used both (O-saru-san in-game for a level name, Ucky in the guidebook), but in that case the "two separate enemies" weren't in a single game alongside each-other separately, so that situation is still different. There's also a reverse situation related to that, where Big Cheep Cheep lost its funny big mouth and its original design was eventually given to its derivative Cheep Chomp (in the same game that gave Grinder's design to Ukiki). Now, I do get where you're coming from, but I find this situation clean enough to enact this. Meanwhile, on the Triforce Wiki, I list both of the "Zora" designs together, while Nintendo back-and-forths on whether they're different, the same, or different-looking clans of the same species (which as of Echoes of Wisdom, is their current depiction) - I find that to be too much confusing mingling to bother attempting to split it. Doc von Schmeltwick (talk) 13:45, September 28, 2024 (EDT)

I will say, Nintendo is inconsistent with whether they list colored variants as separate subjects or lumped together, but in the modern era (the mid-2010s onward), they generally do if there are mechanical differences between them. For example, the Super Mario Bros. Encyclopedia and Mario Portal list red and green Koopa Troopas separately for every game where they both appear (as well as yellow and blue ones in Super Mario World), as well as the Kadokawa guidebook for Super Mario Bros. Wonder. They do not do this for enemies that appear in multiple colors but have no mechanical differences between them, like Biddybuds, Para-Biddybuds, or Lava Bubbles in Super Mario 3D World (of note, they do recognize blue and red Lava Bubbles separately in Super Mario Galaxy 2, where they do have mechanical and behavioral differences with each other. I should also note that I have seen Super Mario 3D Land Biddybud figures sold with color denotations in their listed names in Japan, but it makes sense to do that for physical merchandise).

I do not know the best approach for Super Mario Wiki. My gut feeling is that it would be best to stick to the systematics employed by the source material, and if that material is listing enemies separately by behavior or color or size, then it is not inherently unreasonable for them to get a dedicated article. What constitutes an "enemy" is not innate - it does not necessarily mean they are members of different species or anything like that (as apparent with Giant Goombas, which can split into Hefty Goombas, then normal Goombas, indicating all Goombas have the capacity to mature into Giant Goombas and would be members of the same exact species, but they are not the same enemy). But our source material is inconsistent and fluid, adjusting based on the specific functions of individual games, as is the case with Lava Bubbles in SMG2 and SM3DW. They have flipflopped with whether they recognize different colors as separate enemies or the same ones (such as here, in the bestiary for New Super Mario Bros. from 2006 that lumps Koopa Troopas together) but they are also inconsistent in contemporary sources. In the encyclopedia, Big Deep Cheep is listed as a distinct enemy in the first New Super Mario Bros. and New Super Mario Bros. 2 - it is lumped with the smaller one in New Super Mario Bros. Wii even though it has not undergone any behavioral changes, and this is in the same book. Dragoneels are lumped as one enemy in the New Super Mario Bros. U section, even though there are fast, extremely long red Dragoneels and stout, slow-moving blue Dragoneels, which seems as valid a distinction as green and red Koopa Troopas. In the Kadokawa Super Mario Bros. Wonder excerpt I linked to above, it recognizes Red Koopa Troopas and Red Koopa Paratroopas as separate enemies from the green ones, but it lists brown and purple Trompettes as one enemy, as well as yellow and blue Konks. This is despite the fact that the difference between the brown and purple Trombettes is that the latter turns around when it reaches the edge of a platform... just like red Koopa Troopas in the same game. - Nintendo101 (talk) 13:18, September 28, 2024 (EDT)

Split articles for the alternate-named reskins from All Night Nippon: Super Mario Bros.

All Night Nippon: Super Mario Bros. has various alternatively named graphic swaps of things from Super Mario Bros., most of which relate to the cast and iconography of the show it is based on. These include:

• OkaP and Pakkun OkaP replacing Goomba and Piranha Plant (split demoed here alongside stuff from the above proposal
• The Hiranya replacing the Star
• The various celebrities replacing the Toads (though admittedly the bonus one is unknown)

These are meant to be seen as different things from the originals, so the current system of lumping them in with them is awkward to say the least. The only real outlier here is the NBS logo replacing the axe, because from what I can tell Katsu Yoshida never named the eye.

Proposer: Doc von Schmeltwick (talk)
Deadline: October 3, 2024, 23:59 GMT

Sunplaza Support - all subjects

1. Doc von Schmeltwick (talk) - Per
2. Ahemtoday (talk) Consistent with how we handle, say, Deku Babas in Mario Kart 8.
3. Shoey (talk) I've always said the wiki needs more weirdo articles.
4. Koopa con Carne (talk) Per. Don't see why not. Deku Baba is a good parallel.
5. Mariuigi Khed (talk) Per.
6. FanOfYoshi (talk) Per all.
7. EvieMaybe (talk) i always thought we dont give ANNSMB enough coverage here. per all
8. DrippingYellow (talk) I'm tempted to say this seems like unnecessary splitting of information, but I guess the information would still also be present in the main article, wouldn't it? This seems fine.
9. ThePowerPlayer (talk) Per all.
10. Camwoodstock (talk) Makes sense, and perhaps this could finally crack the mystery of who that unknown celebrity is! Per all.
11. DryBonesBandit (talk) Per all, especially on Deku Baba and Keese.

Sunplaza Support - only enemies

1. Doc von Schmeltwick (talk) - Per

OkaP Oppose

1. LinkTheLefty (talk) I'd personally not want to split these enemies since doing so is practically a degree away from re-splitting Super Mario World's "Fall" graphic swaps (and the Advance 2 exclusives don't have their own names).

Remove "Koopa" and other name particles from Koopaling article titles - take 2

Since the last proposal, other proposals have cropped up which sought to trim excess appellatives and nicknames from the titles of various character articles. As a result of these proposals, which saw little to no contention, the following changes were made:

• Professor Elvin Gadd was moved to "Professor E. Gadd".
• Baby Donkey Kong was moved to "Baby DK".
• Crossover characters with formerly descriptive titles (e.g. Sonic the Hedgehog, Fox McCloud) were moved to the shortened forms of their names (e.g. "Sonic", "Fox").

As well, before the aforementioned proposal:

• Donkey Kong Country's Animal Friends were moved to their shorthand names.
• Conker the Squirrel was moved to "Conker".

Vigilant gamers and game lore extraordinaires will know why these changes were made: the short forms of these subjects' names have been much more prominent and recent in their relevant official works, and their display titles across the site did not reflect this predilection. The Koopalings, as well as Princess Daisy, are now the outliers in this specific regard--but while the sentiment against moving Daisy's name to its more common shortened form was the inconsistency that would arise with Princess Peach using her long title, I do not recall the Koopalings, as a group, having some special counterpart that would create a similar perceived inconsistency.

Yeah, Larry was called "Larry Koopa" in a specific line of dialogue within Smash Ultimate, in a decade-and-a-half old licensed player's guide, and probably some 2010's toy that I'm sure users will name here in the comments, but the fact is, his short name has been promoted front-and-center within all of the games he has appeared from Mario Kart 8 back in 2014 until today, many of which are namedropped in the previous proposal. Same with his 6 siblings.

Besides, MarioWiki:Naming states plainly:

• "the name of an article should correspond to the most commonly used English name of the subject"
• "the more commonly used modern name should be used as the title"

and I believe it's only sensible for the wiki to mirror the more recent developments of the franchise in how a subject is introduced to readers.

Affected pages include:

Larry Koopa (will be moved to "Larry") Roy Koopa ("Roy") Wendy O. Koopa ("Wendy") Lemmy Koopa ("Lemmy") Morton Koopa Jr. ("Morton") Ludwig von Koopa ("Ludwig") Iggy Koopa ("Iggy")

List of Larry Koopa profiles and statistics (will be moved to "List of Larry profiles and statistics") List of Roy Koopa profiles and statistics ("List of Roy profiles and statistics") List of Wendy O. Koopa profiles and statistics ("List of Wendy profiles and statistics") List of Lemmy Koopa profiles and statistics ("List of Lemmy profiles and statistics") List of Morton Koopa Jr. profiles and statistics ("List of Morton profiles and statistics") List of Ludwig von Koopa profiles and statistics ("List of Ludwig profiles and statistics") List of Iggy Koopa profiles and statistics ("List of Iggy profiles and statistics")

Note:

• This proposal targets only page titles. Even if it's a pass, articles can still acknowledge the full forms of these characters where appropriate, such as in Koopaling article openers.
• If this proposal passes, the templates in Category:Koopaling content templates become obsolete and are to be abolished.

Proposer: Koopa con Carne (talk)
Deadline: October 4, 2024, 23:59 GMT

Support

1. Koopa con Carne (talk) per proposal, and per the former proposal as well, which I encourage participants to peruse. (Though, this time, with no multi-option shenanigans.)
2. Axii (talk) Per con Carne (like the last time).
3. Nintendo101 (talk) This may be controversial, but I think this is fine and in-line with our policies. These characters have largely only been referred to by their first names since Mario & Luigi: Superstar Saga. This does not mean Ludwig's full name is not "Ludwig von Koopa" or that it does not see occasional use in marketing and in games - it just means the title of the article is just Ludwig. I personally do not think that is as systematically harmful or erroneous as previous proposals seemed to have suggested. Lots of reference material does this. For example, the name of the Mark Twain article on Wikipedia is not "Samuel L. Clemens" in any language.
4. LinkTheLefty (talk) Needless to say, there have been a few changes since the last time this was proposed.
5. Camwoodstock (talk) Per proposal. It seems only fair as we clamp down more and more on these elongated page titles.
6. Tails777 (talk) Supported once and I'll do it again. Per proposal.
7. Hewer (talk) Per all. I never really understood the main argument against this last time ("the full names still exist", as though that means they should automatically take priority over their more common short counterparts).
8. Technetium (talk) Per all.
9. DesaMatt (talk) Per all von Koopa.
10. EvieMaybe (talk) while i don't agree with the de-title-ification that's been going on, if we're going to do it we might as well be consistent with it.
11. ThePowerPlayer (talk) The fact that there exists an entire category of templates just to circumvent a standard that violates MarioWiki:Naming is concerning, to say the least.
12. Jdtendo (talk) Per all.
13. YoYo (talk) per all
14. BMfan08 (talk) Per all.

Comments

To clarify my position on Daisy, it was not because I thought the proposal was unreasonable. To me, an analogous situation would be drafting a proposal to only change the name of Iggy Koopa's article and none of other Koopalings. Maybe others don't see Peach and Daisy as related to each other as sibling characters like the Koopalings, but that's how I feel at least. I would receive a proposal that included both Peach and Daisy differently. - Nintendo101 (talk) 15:31, September 27, 2024 (EDT)

I reworded that point about the Daisy vs. Peach situation to sound less like a potshot. Sorry. -- KOOPA CON CARNE 15:34, September 27, 2024 (EDT)

I thought it was funny :) Just wanted to clarify my position. - Nintendo101 (talk) 15:37, September 27, 2024 (EDT)

I appreciate that you took it in good humor, but I've made a point that I'll try and be more careful with the way I word my statements. -- KOOPA CON CARNE 15:41, September 27, 2024 (EDT)

Overturn the proposal that resulted in the deletion of Category:User eo (category for speakers of Esperanto)

Myself, I don't care about this language, and needless to say, neither do most people on the planet, but I take issue with the proposal that had it removed in the first place for a few reasons.

• The proposal argues that this language "is not a real language", that "nobody really picked it up", and likens it to the fictional language of Klingon. Despite its status as a constructed language, it is, in fact, very much a real language intended and created to be functional. It has a(n admittedly small) number of speakers across the planet, some of whom may well be potential editors on this wiki for all we know. The comparison to Klingon, which was created with an artistic purpose, is misleading.
• The proposer was outed as an extremist (read up on the details at your own risk) who seemingly was planning to have other language-based user categories removed, as he followed up with another proposal targeting the Georgian user category. The wiki's policies outline that we shouldn't assume bad faith in users, but given the circumstances here, I hope you'll allow me the assumption that this user had ulterior motives in their little curatorial project, namely in altering the wiki ever so slightly according to their outlooks. Proposal failed and the user was banned for their concerning behavior, preventing further such proposals from being made.

Now, as you'd expect, the Esperanto user category certainly never saw much use--in fact, only one user employed it as of 2014 (archive.org) and even then only listed Esperanto as a second language (archive.org) (though, the very point of Esperanto was to be an auxillary language between people who don't speak the same native language). That user, who goes by Pakkun (talk), has since taken the category off their page, so you could argue that this proposal lacks a tangible purpose as "User eo" would be dead on arrival should it be recreated.

The point of this proposal, however, isn't to recreate this language immediately; it is to negate the proposal that currently prevents its creation if someone ever considers they'd derive some use from it. This community should be open to anyone regardless of their cultural background. The previous proposal is contrary to that.

Proposer: Koopa con Carne (talk)
Deadline: October 5, 2024, 23:59 GMT

Support

1. Koopa con Carne (talk) per proposal.
2. Ahemtoday (talk) Per proposal.
3. Camwoodstock (talk) Honestly, we would be down for more Conlangs to have user categories. We can't imagine the overlap of, say, Vötgil speakers to Mario Wiki users is very large, but like, in regards to a strictly English wiki, the Conlang categories in particular are just for-fun categories at the end of the day, and who the hey are we to expressly prohibit other people's fun? And even in the most generous reading of the events, it still feels like a bit of warped priorities when some categories have been in need of reforms for awhile now (sorry about the Thieves category thing, we're still thinking of that and honestly at this point we wouldn't mind someone else chipping in with that) and haven't gotten them, but we have an entire proposal dedicated to... Deleting a category for Esperanto speakers??? (And for the record, this was back when Category:Canines was called Dogs--something something, obligatory mention of Penkoon.)
4. Shadow2 (talk) We DID this? wtf??
5. Nintendo101 (talk) Per proposal.
6. DryBonesBandit (talk) Per proposal.
7. Hewer (talk) Per proposal.
8. Arend (talk) With the provided context, something about Trig Jegman's proposals rubs me the wrong way. If it's true that he was trying to gradually remove other languages, where would he stop? He stated that Esperanto and Gregorian are languages not supported by Nintendo (a weak argument IMO, as Nintendo =/= this wiki), and not widely spoken, so would he first try to get all small-spoken languages removed? Would he eventually try to get larger languages removed just because Nintendo doesn't support these languages? Would he eventually go even further and get even languages that are supported by Nintendo removed because they're not as widely spoken as other languages? Would he eventually make it so that English is the only language remaining? Would he then remove that category too because if that's the only language category for users, then what's the point of keeping it? Or worse, is this a ploy to recognize who is native to other languages and would he try to get non-English users banned so only English-speaking users have access to the wiki (and then remove the English category)? ...Uh...fearmongering aside, per all.
9. Waluigi Time (talk) No harm having it if people want to use it.
10. TheFlameChomp (talk) Per all.

Comments

The real question is if we can have a Klingon category (as a certain other editor who is no longer with us due to concerning behavior mentioned on that proposal). Doc von Schmeltwick (talk) 17:11, September 28, 2024 (EDT)

Up for debate whether user categories can have some basis in fiction. -- KOOPA CON CARNE 17:16, September 28, 2024 (EDT)

We think that Conlangs in general should just be allowed, just because it both feels really, really weird to try to police what Conlangs "count" as languages, and because the idea of focusing even more proposals on such a for-fun topic feels.... A little too much, when that effort is best used elsewhere. ;P ~Camwoodstock (talk) 18:14, September 28, 2024 (EDT)

We should be open for Inklingese and Smurf. rend (talk) (edits) 20:24, September 28, 2024 (EDT)

Miscellaneous

None at the moment.