MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
Line 31: Line 31:
#{{User|Camwoodstock}} This makes the most sense to us. While the Rhythm Game articles are a tad overkill (it'd be like making a <s>Spleef</s> "Tumble" article because of Minecraft's coverage on the wiki), given ''Rhythm Heaven Fever'' is retroactively the debut of [[Cicada]], it seems only fair to at least give that game an article as a guest appearance. After all, if ''[[Art Style: PiCTOBiTS]]'' <small>(our beloved)</small> can have an article as a token guest appearance because you can use Mario items, why can't Rhythm Heaven Fever when it has the debut of a ''WarioWare'' character?
#{{User|Camwoodstock}} This makes the most sense to us. While the Rhythm Game articles are a tad overkill (it'd be like making a <s>Spleef</s> "Tumble" article because of Minecraft's coverage on the wiki), given ''Rhythm Heaven Fever'' is retroactively the debut of [[Cicada]], it seems only fair to at least give that game an article as a guest appearance. After all, if ''[[Art Style: PiCTOBiTS]]'' <small>(our beloved)</small> can have an article as a token guest appearance because you can use Mario items, why can't Rhythm Heaven Fever when it has the debut of a ''WarioWare'' character?
#{{User|JanMisali}} Second choice, per Hewer and Camwoodstock.
#{{User|JanMisali}} Second choice, per Hewer and Camwoodstock.
#{{User|FanOfYoshi}}


====Only create articles for the eight Rhythm Games in ''Megamix'' that have ''WarioWare'' versions====
====Only create articles for the eight Rhythm Games in ''Megamix'' that have ''WarioWare'' versions====

Revision as of 12:25, April 23, 2024

Image used as a banner for the Proposals page

Current time:
Friday, May 3rd, 19:17 GMT

Proposals can be new features (such as an extension), the removal of previously-added features that have tired out, or new policies that must be approved via consensus before any action is taken.
  • "Vote" periods last for one week.
  • Any user can support or oppose, but must have a strong reason for doing so (not, e.g., "I like this idea!").
  • All proposals must be approved by a majority of voters, including proposals with more than two options.
  • For past proposals, see the proposal archive and the talk page proposal archive.

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

How to

Rules

  1. If users have an idea about improving the wiki or managing its community, but feel that they need community approval before acting upon that idea, they may make a proposal about it. They must have a strong argument supporting their idea and be willing to discuss it in detail with the other users, who will then vote about whether or not they think the idea should be used. Proposals should include links to all relevant pages and writing guidelines. Proposals must include a link to the draft page. Any pages that would be largely affected by the proposal should be marked with {{proposal notice}}.
  2. Only registered, autoconfirmed users can create, comment in, or vote on proposals and talk page proposals. Users may vote for more than one option on proposals with more than two choices.
  3. Proposals end at the end of the day (23:59) one week after voting starts, except for writing guidelines and talk page proposals, which run for two weeks (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 one week later on Monday, August 8, at 23:59 GMT.
  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 at any time, but the final decision to remove another user's vote lies solely with the administrators.
    • 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 "(banned)" is added next to their name in the "Proposer:" line of the proposal, which runs until its deadline as normal. If the proposal passes, it falls to the supporters of the idea to enact any changes in a timely manner.
  7. No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old.
  8. 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.
  9. All proposals that end up in a tie will be extended for another week. Proposals with more than two options must also be extended another week if any single option does not have a majority support: i.e. more than half of the total number of voters must appear in a single voting option, rather than one option simply having more votes than the other options.
  10. If a proposal with only two voting options has more than ten votes, it can only pass or fail by a margin of three votes, otherwise the deadline will be extended for another week as if no majority was reached at all.
  11. Proposals can only be extended up to three times. If a consensus has not been reached by the fourth deadline, the proposal fails and can only be re-proposed after four weeks, at the earliest.
  12. 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.
  13. If the administrators deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to remove it at any time.
  14. Proposals can only be rewritten or deleted by their proposer within the first three days of their creation (six days for talk page proposals). However, proposers can request that their proposal be deleted by an administrator at any time, provided they have a valid reason for it. Please note that canceled proposals must also be archived.
  15. 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.
  16. Proposals cannot be made about promotions and demotions. Users can only be promoted and demoted by the will of the administration.
  17. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
  18. Proposals must have a status quo option (e.g. Oppose, Do nothing) unless the status quo itself violates policy.

Basic proposal and support/oppose format

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


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

'''Proposer''': {{User|[enter your username here]}}<br>
'''Deadline''': [insert a deadline here, 7 days after the proposal was created (14 for writing guidelines and talk page proposals), at 23:59 GMT, in the format: "May 3, 2024, 23:59 GMT"]

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

====Oppose====

====Comments====


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

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

Talk page proposals

All proposals dealing with a single article or a specific group of articles are held on the talk page of one of the articles in question. Proposals dealing with massive amounts of splits, merges or deletions across the wiki should still be held on this page.

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

Rules

  1. All active talk page proposals must be listed below in chronological order (new proposals go at the bottom) using {{TPPDiscuss}}. Include a brief description of the proposal while also mentioning any pages affected by it, a link to the talk page housing the discussion, and the deadline. If the proposal involves a page that is not yet made, use {{fake link}} to communicate its title in the description. Linking to pages not directly involved in the talk page proposal is not recommended, as it clutters the list with unnecessary links. Place {{TPP}} under the section's header, and once the proposal is over, replace the template with {{SettledTPP}}.
  2. All rules for talk page proposals are the same as mainspace proposals (see the "How to" section above), with the exceptions made by Rules 3 and 4 as follows:
  3. Voting in talk page proposals will be open for two weeks, not one (all times GMT).
    • For example, if a proposal is added at any time on Monday, August 1, 2011, it ends two weeks later on Monday, August 15, 2011, at 23:59 GMT.
  4. The talk page proposal must pertain to the article it is posted on.
  5. When a talk page proposal passes, it should be removed from this list and included in the list under the "Unimplemented proposals" section until the proposed changes have been enacted.

List of ongoing talk page proposals

Unimplemented proposals

Proposals

Merge the Wrecking Crew and VS. Wrecking Crew phases into list articles, Axis (ended February 24, 2022)
Do not consider usage of classic recurring themes as references to the game of origin, Swallow (ended March 9, 2022)
Split Mario Kart Tour character variants into list articles, Tails777 (ended May 4, 2022)
Enforce WCAG Level AA standards to mainspace and template content, PanchamBro (ended May 29, 2022)
Change how RPG enemy infoboxes classify role, Doc von Schmeltwick (ended September 18, 2022)
Trim away detailed special move information for all non-Mario fighters, Koopa con Carne (ended January 30, 2023)
Classify the Just Dance series as a guest appearance, Spectrogram (ended April 27, 2023)
Establish a standard for long course listings in articles for characters/enemies/items/etc., Koopa con Carne (ended June 8, 2023)
Consider filenames as sources and create redirects, Axis (ended August 24, 2023)
Add tabbers to race/battle course articles, GuntherBB (ended November 18, 2023)
Remove elemental creatures categories from various Super Mario RPG enemies, Swallow (ended January 11, 2024)
Standardize the formatting of foreign and explanatory words and phrases in "Names in other languages" tables, Annalisa10 (ended February 7, 2024)
Trim or remove various Smash franchise-specific subcategories, Camwoodstock (ended February 25, 2024)
Merge Super Mario Bros. (film) subjects with their game counterparts, JanMisali (ended April 18, 2024)
Create an article for Rhythm Heaven Fever, JanMisali (ended April 29, 2024)
Remove profiles and certain other content related to the Super Mario Bros. Encyclopedia from the wiki, Koopa con Carne (ended April 30, 2024)

Talk page proposals

Split all the clothing, Doc von Schmeltwick (ended September 12, 2021)
Split the various reissues of Mario Bros., Doc von Schmeltwick (ended April 22, 2022)
Split machine parts, Robo-Rabbit, and flag from Super Duel Mode, Doc von Schmeltwick (ended September 30, 2022)
Expand source priority exception to include regional English differences, LinkTheLefty (ended January 14, 2023)
Add product IDs in game infoboxes, Windy (ended March 18, 2023)
Remove the list of Super Smash Bros. series objects, Axis (ended May 10, 2023)
Merge Start Dash with Rocket Start, Koopa con Carne (ended August 17, 2023)
Use italics for the full title of the Mario Kart 8 Deluxe – Booster Course Pass, Hewer (ended September 15, 2023)
Split Special Shot into separate articles by game, Technetium (ended September 30, 2023)
Convert the lists of episode appearances for television series characters into categories, Camwoodstock (ended November 22, 2023)
Decide which series certain Yoshi games are related to, GuntherBB (ended December 14, 2023)
Change the Super Mario 64 DS level section to include more specific character requirements, Altendo (ended December 20, 2023)
Replace "List of Game Over screens" and "'Game Over' as death" sections with a "History" section, DrippingYellow (ended December 20, 2023)
Split the Jungle Buddies from Animal Friends, DrippingYellow (ended December 22, 2023)
Make major changes to the MarioWiki:Links page, PnnyCrygr (ended January 10, 2024)
Make bestiary list pages for the Minion Quest and Bowser Jr.'s Journey modes, Doc von Schmeltwick (ended January 11, 2024)
Merge the "Johnson" running gag into one page, Doc von Schmeltwick (ended January 11, 2024)
Merge the ghost Bats and Mice from Luigi's Mansion to their respective organic counterparts from the later games, Doc von Schmeltwick (ended January 20, 2024)
Split Strobomb from Robomb, Doc von Schmeltwick (ended January 20, 2024)
Split the NES and SNES releases of Wario's Woods, SONIC123CDMANIA+&K(B&ATSA) (ended March 27, 2024)
Merge Mii Brawler, Mii Swordfighter, and Mii Gunner to Mii, TheUndescribableGhost (ended March 28, 2024)
Merge Masterpieces to the Super Smash Bros. Brawl and Super Smash Bros. for Wii U articles, Camwoodstock (ended March 31, 2024)
Split Mario's Time Machine (Nintendo Entertainment System), or the Super Nintendo Entertainment version along with both console versions of Mario is Missing!, LinkTheLefty (ended April 11, 2024)
Rename Beanstalk to Vine, DrippingYellow (ended April 11, 2024)
Split Hell from List of implied locations, Hewer (ended April 27, 2024)

Writing guidelines

None at the moment.

New features

Expand Rhythm Heaven series coverage

The WarioWare and Rhythm Heaven series cross over with each other very frequently for various reasons. As such, this wiki currently has some limited coverage of Rhythm Heaven games. I believe that this coverage should be slightly expanded. While our fellow NIWA member Rhythm Heaven Wiki is doing a great job documenting these things and linking to it when relevant works, it would still be nice for the Super Mario Wiki to have all the WarioWare-related Rhythm Heaven content covered within its scope.

The new articles I suggest should be created are:

To be clear, these articles would only cover these subjects to the extent that they are relevant to the WarioWare series, much like how the Rhythm Heaven Megamix article is written. This is not a proposal to annex the Rhythm Heaven Wiki's coverage into our own.

Proposer: JanMisali (talk)
Deadline: April 29, 2024, 23:59 GMT

Create articles for Rhythm Heaven Fever and all Rhythm Games that feature playable WarioWare characters

  1. JanMisali (talk) Per my proposal.

Only create an article for Rhythm Heaven Fever

  1. Hewer (talk) While we do have articles for the Mario minigames in Nintendo Land, these ones are, from what I can tell, less substantial and reskins of un-Mario-related minigames, so I feel like giving articles to every one is a bit overkill and covering them like we currently do on the Rhythm Heaven Megamix page is neater and gives more purpose to those pages. Having a Rhythm Heaven Fever article but covering the main thing connecting it to Mario on a separate page would be like if we split the Super Mario Mash-up from the Minecraft page. That said, giving Rhythm Heaven Fever guest appearance status seems reasonable.
  2. Super Mario RPG (talk) Secondary choice
  3. Camwoodstock (talk) This makes the most sense to us. While the Rhythm Game articles are a tad overkill (it'd be like making a Spleef "Tumble" article because of Minecraft's coverage on the wiki), given Rhythm Heaven Fever is retroactively the debut of Cicada, it seems only fair to at least give that game an article as a guest appearance. After all, if Art Style: PiCTOBiTS (our beloved) can have an article as a token guest appearance because you can use Mario items, why can't Rhythm Heaven Fever when it has the debut of a WarioWare character?
  4. JanMisali (talk) Second choice, per Hewer and Camwoodstock.
  5. FanOfYoshi (talk)

Only create articles for the eight Rhythm Games in Megamix that have WarioWare versions

Do nothing

  1. Super Mario RPG (talk) First of all, we have Rhythm Heaven Wiki, which you even mentioned in your proposal. We can still practically find ways to cover all of the Super Mario content in Rhythm Heaven without going overboard, otherwise we may find ourselves with a successor to the Super Smash Bros. coverage issue. Also, when you said in your proposal that you thought it would be "nice," that's vague and based on personal opinion, since one could swap out Rhythm Heaven for anything (Bayonetta, Shin Megami Tensei, Terraria, etc.) Wiki scope should be about practicality, not whether someone thinks something is "nice."

Comments

@Super Mario RPG: Obviously "nice" was being used to mean "preferable given the described circumstances", not sure what gave you an impression otherwise. One could not swap out Rhythm Heaven for any other franchise as Bayonetta, Shin Megami Tensei, and Terraria have not had frequent crossovers with the WarioWare series. Hewer (talk · contributions · edit count) 16:18, April 22, 2024 (EDT)

@Hewer, To be fair, there is precedent for giving Mario reskins of otherwise unrelated minigames dedicated articles, namely the Game & Watch Gallery series. I understand your point though, it might be overkill to have full coverage of all these minigames when they're already handled on the Rhythm Heaven Wiki. jan Misali (talk · contributions) 17:00, April 22, 2024 (EDT)

Removals

Remove profiles and certain other content related to the Super Mario Bros. Encyclopedia from the wiki

The wiki currently houses a sizeable number of transcriptions of information from the 2015 Super Mario Bros. Encyclopedia, mainly the Japanese edition, in the form of character and enemy profiles. I stated my concern here that this practice may infringe Dark Horse/Nintendo's copyright over the product: to my knowledge, the book's entire selling point is to inform you on the stuff you find in Mario games through bitesized blurbs. In incorporating these blurbs within its knowledge base, the Mario Wiki, a free resource, is not just impairing the very purpose of the book, but, given that it's still in print, may negatively impact its sales. In fact, that second point is the reason this proposal concerns this book only and not similar publications like Perfect Edition of the Great Mario Character Encyclopedia, which has long been out of print and has been superseded by the SMB Encyclopedia, making it highly unlikely that some big wig will send Porple a DMCA strike over something like Fire (100m)'s profile. When it comes to the 2015 Encyclopedia, though, that has a reasonable likelihood of happening and it's best the wiki enforces good faith.

On a similar basis, one user who engaged with the topic in the above talk page has also questioned the wiki's need to feature scans of the book's mistakes in its very article. Given the small size of each blurb, the scans are essentially taking away substantial chunks of information in a way that cannot be conceived as demonstrative or transformative under US Fair Use law.

What this proposal aims to do is the following:

  • remove encyclopedia bios listed on various articles, regardless of their source's language. Here's an example. Here's another.
  • delete the scans in the "List of English translation errors and typos not from the Super Mario Wiki" section of the encyclopedia's article, as well as any other scans of the book's contents, unless said content has been displayed by Nintendo or one of their official distributors for the purpose of promoting the book. To exemplify: This, this, and this image should be deleted if the proposal passes. This and this one should also be deleted, since the content depicted in these images hasn't been used by Shogakukan, Amazon, or some other official distributor to portray the Japanese edition on their online storefronts. On the other hand, the artwork shown in the article's gallery, such as this one, shouldn't be removed unless they depict textual information that infringes copyright.

A few notes:

  • Paraphrases of the encyclopedia's information will be allowed under the proposal, so the book's article may continue to describe its mistakes until further notice.
  • Small quotes of the book will also be permitted (e.g.: "This text is translated from the Japanese instruction booklet.") if they do not violate this proposal's requirements, albeit it's entirely up to editors to decide how small a quote should be and whether it fits US Fair Use.
  • Subject names unique to the encyclopedia are not concerned by this proposal.

Proposer: Koopa con Carne (talk)
Deadline: April 30, 2024, 23:59 GMT

Support

  1. Koopa con Carne (talk) Per proposal.
  2. Doc von Schmeltwick (talk) - Book's only 9 years old, this is worrisome.

Oppose

  1. Axis (talk) I genuinely don't see how use of limited material from the book on pages relevant to the subject in question is by any means problematic.
  2. Hewer (talk) Per Axis.

Comments

@Axis Put it another way: how legal would it be if you cut down a copyrighted movie in 30 second clips and uploaded all of them to your youtube channel? That's exactly what the wiki does, except with a book. -- KOOPA CON CARNE 12:03, April 23, 2024 (EDT)

Changes

Overhaul titles of generic-named level/course/stage pages

With the recent release of the Nintendo Switch remake of Mario vs. Donkey Kong, we have already seen the introduction of two new worlds - Merry Mini-Land and Slippery Summit, as well as their plus variants. However, while I was documenting levels for the remake, I have noticed an issue - since these worlds also change the numbering for Spooky House, Mystic Forest, and Twilight City's level pages, this causes several concerns for me in regards to naming level articles with generic-named stage numberings in games where worlds are named:

  • Right now, the level numberings for the various levels in Mario vs. Donkey Kong are correspondent to the GBA version. If I attempt to move those pages to match the Switch numbering (for example: "Level 4-1 (Mario vs. Donkey Kong)" (Spooky House 4-1) to "Level 5-1 (Mario vs. Donkey Kong)" (Spooky House 5-1, Switch version)), this can cause several issues with us cleaning up all the links to other level pages, and is especially the case for links to various Mystic Forest (5-x > 7-x) and Spooky House (4-x > 5-x) pages.
  • Related to above, the new Merry Mini-Land and Slippery Summit pages have a slightly conjectural variation of the game's title. Take a look at this for example: "Level 4-1 (Mario vs. Donkey Kong for Nintendo Switch)", aka the first stage of Merry Mini-Land.
    • As a reminder: nowhere in any circumstance has the remake been titled "Mario vs. Donkey Kong for Nintendo Switch", it is simply titled "Mario vs. Donkey Kong". It could be seen as confusing especially as there are some reissues of games that are officially titled the same way too (like Super Mario Maker for Nintendo 3DS).
    • I attempted to get around this by initially naming the title of the article as "Level 4-1 (Mario vs. Donkey Kong (Nintendo Switch))", but it caused issues with rendering the title on top of the page.

What I wanted to propose is to overhaul the titles of generic-named level/course/stage pages. Level articles that fall under this description are:

Given that there are a lot of generic-named level articles that fall under this jurisdiction, this is a very large-scale proposal, and may affect most, if not all "x-x" level articles. This will require help from the wiki's higher staff, especially an administrator who can handle several article renames and moves at large. Due to this, please note that the effects of the proposal may not be always guaranteed to be immediate even if it is already passed, but I hope to get this done with everyone as soon as possible.

After brainstorming for a while, these are the possible formats we're going to aim for when making level pages, see below.

Option 1: "(World/Game Name) - (Level Code)"

This is the new page naming format for levels which is based on the naming format used for WiKirby (note for reference: levels in the Kirby series are called "stages", while worlds are called "levels".) Examples of articles on WiKirby that follow this format are Cookie Country - Stage 1 (Level 1-1 or Stage 1 of Cookie Country in Kirby's Return to Dream Land), and Kirby Tilt 'n' Tumble - Lvl 7-2 in Kirby Tilt 'n' Tumble.

This makes it easier to update a level's numbering designation should any circumstances of adding new worlds in-between happen again (like how Merry Mini-Land and Slippery Summit were handled in the Switch version of Mario vs. Donkey Kong). It can also make it easier to identify levels from each other easily without having to look up the name of the world first. This will also ensure moving articles if new worlds are added in remakes are made easier as well. Additionally, this will prevent game name confusion from occurring, specifically my issue with the Merry Mini-Land stages using the identifier "Mario vs. Donkey Kong for Nintendo Switch".

With this format, this is how it will work:

  • For levels that use generic numbering (1-x) and are from a named world, they will be named "(World Name) - X-X". For example, in the Switch version of Mario vs. Donkey Kong, we can call Level 5-DK and Level 8-2 as "Spooky House - Level 5-DK" and "Twilight City - Level 8-2".
    • As a side note - if two worlds from different games happen to share names, the newer game's level page can have the newer game's title in parenthesis. For example, hypothetically speaking, we get two worlds named "MarioWiki Land" in two games. It can go like this "MarioWiki Land - Level 2-2" for Game A, and "MarioWiki Land - Level 2-2 (Game B)" for Game B. To my knowledge, something like this has not occurred in any official games and upcoming content.
    • Depending on how the game may call the level code, it can be formatted differently. For example, in Hotel Mario, levels are named as "Stage #", and Super Mario Wiki refers to their level articles with the title ("Stage # (Hotel Name)"). It can be changed to be something like "Lemmy's High-ate Regency Hotel - Stage 1".
  • For levels that use generic numbering and are in unnamed worlds (eg. Super Mario Bros.), they will be named "(Game Name) - X-X". For example, take World 1-1 in Super Mario Bros.. This can be named as "Super Mario Bros. - World 1-1" instead. The "world" designator can be renamed to "Level/Area/Stage/Course" depending on how the game calls it.
    • Some of you might be concerned with it conflicting with a certain job name in Super Mario Maker 2 - "Super Mario Bros. W1-1?". It shouldn't conflict at all - the format of the title is seemingly close but in the end it's fairly different.
  • Redirects can be made based on the original names of the articles. For example, if "Level 6-3 (Mario vs. Donkey Kong)" is moved to "Twilight City - Level 8-3", the former can be turned into a redirect that leads to the latter new title of the article itself, to make it easier to search for wiki readers who are more used to the old format. Another example is if "World 1-2 (Super Mario Bros. 3)" is moved to "Grass Land - World 1-2", where typing in "World 1-2 (Super Mario Bros. 3)" still leads to the article with the new name.
  • Levels with names are already kept as is. If some level names from two or more games conflict due to them being the same, the name of the game should be placed in parenthesis for the associated articles, while the level of the game that is released first chronologically will keep its name as is (no game title in parenthesis after it.)
  • If a case of level codes being updated occurs due to addition of new worlds (eg. Merry Mini-Land and Slippery Summit), the reissue's new level numbering should take priority over the old one.

Option 2: "(World Name) - (Level Code)" and "(Level Code) (Game Name)"

This is a variation of the first option which incorporates itself with the old level article naming system to make it more flexible to some situations especially for tackling commonly-searched terms like "World 1-1". This is how it will go:

  • Levels that use generic numbering and are from a named world will be named "(World Name) - Level X-X". Ex. Level 4-mm (Mario vs. Donkey Kong for Nintendo Switch) becomes "Merry Mini-Land - Level 4-mm".
    • If two worlds from different games happen to share names, the newer game's level page can have the newer game's title in parenthesis. For example, hypothetically speaking, we get two worlds named "MarioWiki Land" in two games. It can go like this "MarioWiki Land - Level 2-2" for Game A, and "MarioWiki Land - Level 2-2 (Game B)" for Game B. To my knowledge, something like this has not occurred in any official games and upcoming content.
    • Depending on how the game may call the level code, it can be formatted differently, whether it would be "Stage X-X", "Area X-X", or even simply "X-X".
    • For redirects, the original names of the articles may serve as redirects, however this may be handled differently depending on certain circumstances (shifting of world number for various worlds in the Mario vs. Donkey Kong remake, for example).
  • Levels that use generic numbering and are from worlds with no names will follow this format: "World X-X ('Game Name')". Examples of such are World 1-1 (Super Mario Bros.) and World 18-1. The game name is used to differentiate the level from other games featuring a level with the same name, as per usual.
  • Levels with names are already kept as is.
  • If a case of level codes being updated occurs due to addition of new worlds (eg. Merry Mini-Land and Slippery Summit), the reissue's new level numbering should take priority over the old one.

I believe that identifying generically-named levels with numbered coding from each other should be made easier, especially if we need to look up information quickly for a friend struggling to find a level or its information. Right now, the current method of using game titles in parentheses makes it hard for such information to be easily looked up, and it has become more of an issue when we tried to fix up the level number coding and the articles for the new levels when documenting the Switch remake of Mario vs. Donkey Kong. I hope this proposal serves to change this for the foreseeable future.

Proposer: EleCyon (talk)
Deadline: April 29, 2024, 23:59 GMT

Option 1

  1. Super Mario RPG (talk) Secondary choice.

Option 2

  1. EleCyon (talk) - First choice, per proposal.
  2. Super Mario RPG (talk) - This could help solve some level naming discrepancies.

Keep as is

  1. Hewer (talk) I don't really get why the problem of a few worlds in Mario vs. Donkey Kong getting their numbers changed warrants a massive change to how we name levels that forgoes our usual naming and identifier rules for no apparent reason. There was never a level called "Super Mario Bros. - World 1-1", it's just known as "World 1-1". I'd compare this to the case of Mario Kart tracks: for example, we have Wii Rainbow Road, but Rainbow Road (Mario Kart: Double Dash!!). We could rename the latter "GCN Rainbow Road" to be more neat and consistent, but it's never been officially called that, so we don't. I'd rather use that same logic and stick to official naming instead of enforcing our own version. And I don't see why only newer games should get identifiers for their titles - I feel like having both get identifiers, similar to the current system where identifier-less World 1-1 is a disambiguation, makes more sense.
  2. Jdtendo (talk) Per Hewer, changing our entire level naming system just for disambiguating some MVDK worlds is overkill. However, I could see the merits of using the world name as an identifier specifically for disambiguating worlds 4 and more of MVDK (e.g., Level 4-1 (Merry Mini-Land)) and only in that specific case.
  3. Camwoodstock (talk) Per Hewer. The MvDK (Switch) situation is overwhelmingly the exception, rather than the norm, so accounting for it on the levels for every single game that doesn't have this problem (so... basically every other Mario video game that has level articles) is extremely overkill.
  4. JanMisali (talk) Per all. The proposal as written would be a lot of work for very little benefit, but implementing this for exclusively the relevant Mario vs. Donkey Kong stages would make those titles both less cluttered and more descriptive.
  5. LinkTheLefty (talk) per plexing
  6. FanOfYoshi (talk) Per all.
  7. YoYo (talk) per all.

Comments

Personally, I fail to see how this makes it any easier. With longer titles especially, the search dropdown's just gonna get cut off and you'll have a bunch of identical copies of the game title without being able to tell which is which (unless the functionality of it has been updated without me realizing). Also, I disagree with prioritizing remake over original with this. I'm not voting right now because I consider myself too tired to do so reliably, but those are my thoughts right now. Doc von Schmeltwick (talk) 01:58, April 22, 2024 (EDT)

I'll point out that "(Mario vs. Donkey Kong for Nintendo Switch)" as an identifier is supported by MarioWiki:Naming: "If two different games share the same title but appear on different consoles and the identifier needs to distinguish between them, the game name and console are used in this format: ({game name} for {console}). For example, Beach Volleyball (Mario & Sonic at the London 2012 Olympic Games for Wii)." And you can tell the difference from something where it's part of the actual title like Super Mario Maker for Nintendo 3DS thanks to the placement of the italics. Hewer (talk · contributions · edit count) 02:18, April 22, 2024 (EDT)

Given the problem is exclusively present in the MvDK levels, I feel like it makes more sense to simply use a format like Spooky House-5 and Merry Mini-Land-mm for specifically that game and its remake, and leave the other courses and levels alone. This seems at least like an acceptable choice, given that the New Super Mario Bros. U and New Super Luigi U courses Stone-Eye Zone and Spike's Tumbling Desert are both being alternatively referred to as Layer-Cake Desert-1 in their respective articles; meaning that, if these NSMBU and NSLU courses hadn't gotten exclusive names, the wiki would've most likely went for the Layer-Cake Desert-1 format. ArendLogoTransparent.pngrend (talk) (edits) 11:19, April 22, 2024 (EDT)

Jdtendo does make a good point, however. Using the world's name in parenthesis for the Mario vs. Donkey Kong worlds might be a better idea to go than mass renaming all the worlds to match what we're going for in the proposal. I might consider this should the proposal not pass at all, especially as I'm about to start documenting Slippery Summit levels soon. --EleCyon (talk) 21:58, April 22, 2024 (EDT)

Miscellaneous

None at the moment.