#{{User|Hewer}} 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.
#{{User|Hewer}} 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.
#{{User|Jdtendo}} 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 (Mario vs. Donkey Kong for Nintendo Switch)|Level 4-1 (Merry Mini-Land)]]) and only in that specific case.
====Comments====
====Comments====
Revision as of 04:38, April 22, 2024
Current time:
Friday, May 3rd, 15:39 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.
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
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}}.
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.
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.
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.
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.
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.
No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old.
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.
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.
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.
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.
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.
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.
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.
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.
Proposals cannot be made about promotions and demotions. Users can only be promoted and demoted by the will of the administration.
No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
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".
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.
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}}.
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:
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.
The talk page proposal must pertain to the article it is posted on.
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
Delete all Super Smash Bros. challenges pages (discuss) Deadline:April 19, 2024, 23:59 GMTApril 26, 2024, 23:59 GMT May 3, 2024, 23:59 GMT
Consider Beanies and Octoombas to be related to Goombas rather than direct variants of them (for consistency with Galoomba et al.) (discuss) Deadline: May 10, 2024, 23:59 GMT
Split "Baby Fat" from Baby Yoshi (discuss) Deadline: May 10, 2024, 23:59 GMT
In Template:Species infobox, expand "Relatives" guidelines to include variant-type relationships with significant differences between species (discuss) Deadline: May 12, 2024, 23:59 GMT
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.
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:
Levels with generic numbering identifiers in worlds that are not named in any circumstance (including in-game and supplementary material like Nintendo Power). Example is World 1-1 in Super Mario Bros..
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.
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.
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:
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
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.
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.
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)
