MarioWiki:Proposals

Proposals that have not been implemented

 * Split Spoing, Sprangler and Klamber from Scuttle Bug - (November 3, 2012)
 * Create boss level articles for Donkey Kong Country and Land series - (January 3, 2015)
 * Create a template for the PM:TTYD badge drop rates - (August 17, 2016)
 * Create a Mini article - (August 20, 2016)
 * Split all remaining courts and boards from their parent articles - (September 25, 2016)
 * Clean up species categories to only include non-hostile species - (August 8, 2017)
 * Clean up Category:Artifacts - (August 22, 2017)
 * Trim down Category:Fire Creatures and Category:Ice Creatures - (September 7, 2017)
 * Create an article on Arcade Archives - (September 23, 2017)
 * Split all Starbeans Cafe items from the Starbeans Cafe article - (September 30, 2017)
 * Merge Mouser (The Super Mario Bros. Super Show!) with Mouser - (November 15, 2017)
 * Create separate articles for online Flash games - (November 25, 2017)
 * Reorganize the board table in Mario Party: Island Tour - (December 15, 2017)
 * Expand the Behemoth King article - (December 23, 2017)
 * Include Every Derivative Togepuku in Spiny Cheep Cheep - (December 25, 2017)
 * Split Porcupinefish from Spiny Cheep Cheep - (December 25, 2017)
 * Create articles on the Remix 10 secret courses in Super Mario Run - (December 26, 2017)

Writing guidelines
None at the moment.

New features
None at the moment.

Removals
None at the moment.

Do not require main templates to be placed on pages alongside auxiliary templates
MarioWiki:Navigation templates § Game-specific templates: These auxiliary game-specific templates only need to go on the articles of subjects that concern them (e.g. the NSMB2 level articles) and the game page itself, however the main template has to go on the subject pages along with the auxiliary template.

My problem is with the bolded sentence (emphasis mine). What's the point of placing a navigation template on an article if the article itself isn't in the template? It's not as if the opposite is true, where, for example, needs to be placed on every non-item page. What's the point of even splitting subjects into separate templates if we're just going to throw them all together anyways? It's extraneous and self-defeating.

Proposer: Deadline: December 29, 2017, 23:59 GMT

Support

 * 1) Per proposal.
 * 2) - The Super Mario Bros.: The Lost Levels level articles all have the  template, despite the levels themselves not showing on it. Conversely, the Super Mario Sunshine missions do not have the main  template, creating an inconsistency. Considering I worked on both of those, I suppose that would be poor planning on my part, but regardless, per proposal.
 * 3) Per proposal.
 * 4) Per proposal.

Comments
"What's the point of placing a navigation template on an article if the article itself isn't in the template?" The missing article could always be added to the template if it's relevant. 16:20, 24 December 2017 (EST)
 * That's not relevant for this case, as the link should have been there in the first place. Here, however, the links are being specifically placed in another nav template. 19:53, 24 December 2017 (EST)

Add anchor links to Power Moon lists
Recently, I've had a small talk with on the removal of anchor links from the Power Moon lists for each kingdom in Super Mario Odyssey. Some lists actually had anchor templates, but Legomariofanatic removed them because someone suggested that anyone looking for a specific Power Moon can use the CTRL+F function to find it in a list. Here's my discussion with Legomariofanatic.

Thing is, I think it's less probable that a user will look up "List of Power Moons in whatever Kingdom" and then do some search on that page to find the location of a Power Moon, than they will simply search that name of the Power Moon. In the game, Talkatoo tells you the names of uncollected Power Moons, so there's how someone could learn their names. The Hint Toad locates them directly on the map, although in some cases the locations may not be exact--that's where the Internet comes to help.

Because this might spur a quarrel, seeing as how someone saw anchor links as useless, I think a proposal is necessary to settle it. Should we use anchor links or not?

Proposer: Deadline: December 31, 2017, 08:53 GMT

Support

 * 1) per proposal
 * 2) - I think the anchor template was created for this sort of thing, so sure, per proposal.
 * 3) Per proposal.
 * 4) Clearly a no-brainer, per all.
 * 5) Per Mario jc's comments
 * 6) Give me one reason not to.
 * 7) Per my comment below.

Comments
I honestly think this is a no-brainer. Like other pages with a list of searchable names like the Things from Sticker Star and Color Splash, obviously it'd be faster and more convenient for people to be taken directly to the specific Power Moon they're looking for (this applies to both searching and linking to Power Moons on other pages). They shouldn't have to use CTRL+F to find the name themselves in this situation. It's better to have the anchor links than to not have them at all. 00:29, 25 December 2017 (EST)
 * There are many lists that use anchor links, like the treasure lists from different Wario games. So yeah, the proposal is apparently a no-brainer. But I thought someone could step forward and argue why those links wouldn't be needed. We need to be cautious! -- 06:55, 25 December 2017 (EST)

The format of the statistics in the main pages of Mario Kart 7, Mario Kart 8 and Mario Kart 8 Deluxe
While the statistics shown in the menus of Mario Kart games have been notoriously inaccurate and sometimes even outright wrong, since Mario Kart 7 the vehicle customization screen finally shows statistics in a way that at least is directly correlated with the underlying in-game statistics: internally the games use points that are summed to determine the final values of the statistics, with each character or part contributing their own points to each statistics, and in the vehicle customization screen every time there is an increase of 1 point in a statistics, the corresponding value shown by the bar increases by 0.25. This direct correspondence between the length of the bar and the underlying sum of points in each statistics led to the main pages of Mario Kart 7, Mario Kart 8 and Mario Kart 8 Deluxe exclusively reporting the statistics in the format used by the games' vehicle customization screens. It must be noted that said format is actually used by the games to display the final statistics of a certain combination of character, vehicle, tires and glider, while in the main pages it is being used to display the statistics of the individual elements (characters and vehicle parts). This mismatch first of all leads to different criteria used for the characters (the final statistics obtained when using said characters with standard parts) and the parts (how the tatistics of each part compare with respect to standard parts), furthermore when discussing a redesign of the tables of statistics thanks to an automated script with, other aspects emerged: Therefore, since the current format has both advantages and disadvantages and the games actually use an alternative format, the points, which is still simple and thus could be used in the main pages I propose to review and decide which format to use for the statistics shown in the main pages of Mario Kart 7, Mario Kart 8 and Mario Kart 8 Deluxe, between those two: In short, those are what I think are the main advantages of each format:
 * the differences between various parts and how much characters and parts contribute to the final stats are potentially more difficult to evaluate, since fractional number that, in the case of the parts, can be both negative and positive are being used to display the stats in place of integers
 * standard parts can have values which are not average in some statistics, leading to the numbers being skewed as a result, this being the case of Standard Tires in Mario Kart 8 which have maximum water speed
 * comparison between games can be more difficult, as the statistics of the standard parts are different in each game - as an example, the Standard Kart has different stats in each game, but the current format doesn't show this
 * more importantly, the current format can be misleading when trying to make considerations in the individual parts' pages, such as the ones on the Standard Kart that didn't reflect the actual statistics of the kart nor the actual contribution of the characters to the final statistics in Mario Kart 7.
 * 1) values actually used by the game (called points)
 * 2) values shown in the vehicle customization screen (what I'll call bar values)

MAIN ADVANTAGES OF POINTS
 * They are the values actually used by the game and, as such, they are not misleading
 * They allow for an easy comparison between characters and parts and between games using the points system, while allowing to easily see how much a character or part contributes to the final stats

MAIN ADVANTAGES OF BAR VALUES
 * They are the ones shown in the vehicle customization screen and, as such, they are the ones most readers are familiar with and the ones mainly used by the competitive Mario Kart community as well
 * They tend to be useful for statistics which are tiered on the integer part of bar values, in particular acceleration in Mario Kart 8 and weight in Mario Kart 8 and Mario Kart 8 Deluxe

As a final note, a revision of the pages of the individual parts will have to be done regardless of the outcome of this proposal, to add the actual statistics of the parts and to see if there are other considerations which need to be corrected in light of the actual statistics of each part.

Proposer: Deadline: January 2, 2018, 23:59 GMT

Use points

 * 1) - While bars are more familiar to players, points show the statistics more accurately, which I think is what should be used.
 * 2) the idea that most readers are already familiar with bar values is not really correct. most readers are familiar with the in-game system of bar values, which they might assume is identical with the wiki's system. but that is not a correct assumption, and cannot be. the in-game system is used to rate a combination of a character and three vehicle parts, while the wiki's system is used to rate each character or part individually. the mapping between the two is based on some fairly arbitrary decisions that readers can easily gloss over without understanding their implications for interpretation of the reported values. the upshot is that although the bar value format feels familiar to readers, because it resembles the in-game system, this feeling is inaccurate and misleads readers into believing that they understand the system when they actually do not. we have already seen the result of this: the claim linked above that the standard kart "doesn't offer any stat changes due to the main stats relying more on the weight class of the character and is shared for all characters" is completely wrong, and this is a direct result of an editor attempting to reason about the bar values system while having misunderstood it. this is a weakness that the point system lacks: because it does not falsely seem to be immediately familiar, users are less likely to incorrectly assume that they understand it when they do not, and more likely to read adjacent explanations of how to properly interpret the data as it is presented regardless of which system the page uses, it will need to include some such text to explain the system to uninformed readers, and readers who opt to ignore this text are likely to come to inaccurate conclusions regarding part statistics. since readers must read and understand this text to correctly use either system, it makes sense to use whichever of the two systems is most helpful to those who do understand it. this is clearly the point system, which allows users to easily understand how each individual part affects the overall stats of a build, cross reference the stats of a part with the translation tables here, and compare parts between mario kart 8 and mario kart 8 deluxe to see how their stats have changed. none of these tasks can easily be done with the bar values system. meanwhile, the main presumed advantage of the bar values system is that it's likely to feel familiar to readers. but as i've shown, this feeling does not mean that most readers actually understand it, and may actually be harmful to their ability to learn to use it
 * 3) Accuracy should take priority over familiarity. Readers would be better off with a foreign yet accurate display of information than a familiar yet flawed display, and it would be better to take the time to learn how to read it than simply go with what they already know, especially if the latter is inaccurate. Using the bar system would defeat the purpose of us being a wiki -- a reputable source of information -- due to said system having inaccurate data. Per 2257.
 * 4) Point values are better because they accurately measure the statistics of a certain part. It's also advisable that the maximum value should be present as well, so that the bar charts are truly obsolete. Per 2257.
 * 5) - Per 2257.
 * 6) Per 2257.
 * 7) Per 2257.

Use bar values

 * 1) You know, if readers are familiar with the bar values, and if the competitive Mario Kart community uses them, then I'm going with bar values. Anyway, that is some of the most detailed in-depth stuff I've read yet on this wiki. I'm gonna have to take a look at it again to make things a little clearer for me.
 * 2) Per Lcross.  The games use bars, and bars are easier for players to understand, so we use bars.

Comments
Why not both, like how we have for the Mario Kart Wii vehicles like Standard Kart M (but done better)? 17:55, 26 December 2017 (EST)
 * Dingo-DONGO. I like that idea. The problem is, how are we going to implement thatt? 18:07, 26 December 2017 (EST)
 * I personally tried that, and I was asked to just report one set of stats. We can of course include two sets of tables, but that would be additional vertical scrolling. In short, unless you can come up with a new layout that manages to do that more clearly, this simply isn't going to happen again.--Mister Wu (talk) 18:33, 26 December 2017 (EST)
 * If only one set of stats is what's been asked, then we may as well just use one for now. 19:30, 26 December 2017 (EST)