MarioWiki:Proposals

Writing guidelines
None at the moment.

New features
None at the moment.

Removals
None at the moment.

Discount resized enemies from Mario Kart Tour as "big" variants of the base enemy
The wiki currently regards upscaled enemies from Mario Kart Tour as distinct, "Big" derivatives of the template enemy, e.g. the large Piranha Plants from SNES Choco Island 2T, SNES Ghost House 1R etc. are taken to be "Big Piranha Plants". Admittedly, I was the one who made this distinction back when I set up the "course elements" table on the game's article, listing large-sized Piranha Plants separately from normal-sized counterparts; later on, an article for Big Sidestepper, an upscaled Sidestepper that only appears in Mario Kart Tour, was created and a corresponding entry was added to the aforementioned table.

One issue with the above is that, regardless of their size, Piranha Plants all share a "Piranha Plant" label on the in-game action display. The other enemies to appear with upscaled models, namely large Goombas and large Sidesteppers, are not labelled at all since they only appear in bonus challenges, where player actions are typically not displayed (except for Combo Attack, which to my recollection has yet to feature any instances of the latter two). Another issue stems from the fact that these enemies may not have been rescaled at a consistent size: for instance, RMX Choco Island 1R/T features an exceptionally humongous Piranha Plant (youtube.com) that visibly tops other already large-sized Piranha Plants appearing in other courses (youtube.com). If there isn't one specific "L" size these enemies comply with, is it warranted to have the larger enemies lumped together as the "Big" variant considering larger-but-still-intermediary-sized enemies, such as Hefty Goombas from New Super Mario Bros. Wii, are considered separate from their maximum-sized counterparts despite having a few shared names? In addition to everything said here, an enemy always behaves the same regardless of its model's size, as opposed to, say, Super Mario Maker big variants which, while not specifically labelled in-game as "big", may feature distinctive quirks from their normal counterparts.

In light of these points, I propose the following two courses of action as options:
 * 1) remove any listings of these rescaled enemies as distinct counterparts for Mario Kart Tour (i.e. remove their entries from the "Course elements" table, the MKT template, and the Mario Kart Tour enemies category), and restrict any mention of them appearing in different sizes to the base enemy's article (i.e. purge such information from the "Big [enemy]" articles);
 * 2) remove any listings of these rescaled enemies as distinct counterparts for Mario Kart Tour (i.e. remove their entries from the "Course elements" table, the MKT template, and the Mario Kart Tour enemies category), but retain/allow mentions of them appearing in different sizes on the "Big [enemy]" articles.

In either scenario, the Big Sidestepper article gets deleted, since Big Sidesteppers have yet to actually appear in a game where they are acknowledged as such or behave differently.

Proposer: Deadline: June 9, 2022, 23:59 GMT

Option 2

 * 1) I prefer this option myself. Despite the game's stance, a large enemy should have a passing mention where size is of interest.

Decide how to cover Mario Kart Tour bonus challenges on course articles
The layout of each bonus challenge in Mario Kart Tour (e.g. Ring Race) depends on the course in which it is set. It tracks, therefore, that these challenges should be covered in detail on their relevant course articles in addition to their parent article. If you wish to see how a course article would look with coverage of its bonus challenges, scroll down to the "Mario Kart Tour" section in the "History" section here.

However, bonus challenges have been observed to appear multiple times across the game's tours, sometimes with changed objectives, which prompts wiki users to regularly update their list entries. Simply copying and pasting these entries onto another article would make it more difficult for users to be aware of which needs to be updated where. On the other hand, adding a way to transclude entire entries (allow information entered on a page to be automatically transferred to another) would spaghettify the original code and potentially deter users from updating it with new information. For instance, this is how the code for an average bonus challenge entry currently looks:


 * MKT Tour1 YoshiCupChallenge.png
 * New York Minute
 * MKT Icon Yoshi.png Yoshi
 * MKT Icon PipeFrameLimeGreen.png Pipe Frame
 * MKT Icon SuperGliderLimeGreen.png Super Glider
 * 5
 * 8
 * 12
 * New York Tour
 * 12
 * New York Tour

(source: Do Jump Boosts article)

and this is how it would look with a transclusion mechanism in place:

A bit ugly, innit? On average, this would only save a small number of bytes on the target article--less than 100, really. Picture, now, an entire table with the same code plastered repeatedly. I believe the wiki should account for editor friendliness too, especially when the returns of optimisation are disappointing.

I am not sure how to proceed here. I am unwilling to go ahead with either option unless I have a clear-cut vision of each one's net advantages. I will thus be resorting to the community's choice.

Proposer: Deadline: June 9, 2022, 23:59 GMT