MarioWiki:Proposals

Current time: Monday, November 11th, 20:19 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. 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, but they may not vote for every option available.
3. Proposals end 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.
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(s) 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. If a proposal reaches its deadline and there is a tie for first place, then the proposal is extended for another week.
10. 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 the {{proposal check}} tool to automate this calculation; see the template page for usage instructions and examples.
11. 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 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 canceled by their proposer within the first six days of their creation. However, proposers can request that their proposal be canceled 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, 14 days after the proposal was created, at 23:59 GMT, in the format: "November 11, 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

Proposals concerning a single page or a limited group of pages are held on the most relevant talk page regarding the matter. Proposals dealing with a large amount 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 {{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. Place {{TPP}} under the section's header, and once the proposal is over, replace the template with {{settled TPP}}.
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. The talk page proposal must pertain to the subject page of the talk page it is posted on.
4. 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

• Determine what to do with Jamboree Buddy (discuss) Deadline: November 12, 2024, 23:59 GMT
• Split Cursed Mushroom from Poison Mushroom (discuss) Deadline: November 12, 2024, 23:59 GMT
• Merge Orbs that share names with pre-existing Mario Party series items with those items (discuss) Deadline: November 14, 2024, 23:59 GMT
• Create a number of articles for special buildings in Super Mario Run (discuss) Deadline: November 15, 2024, 23:59 GMT
• Consider Deep Cheeps' appearance in the Super Mario Maker series a design cameo rather than a full appearance (without Blurps being affected) (discuss) Deadline: November 15, 2024, 23:59 GMT
• Merge Mushroom, Dash Mushroom, and most of Super Mushroom (discuss) Deadline: November 18, 2024, 23:59 GMT
• Expand and rename List of characters by game (discuss) Deadline: November 20, 2024, 23:59 GMT
• Decide whether to create articles for Ashita ni Nattara and Banana Tengoku and/or include them on List of Donkey Kong Country (television series) songs (discuss) Deadline: November 23, 2024, 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)

Split articles for the alternate-named reskins from All Night Nippon: Super Mario Bros., Doc von Schmeltwick (ended October 3, 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)

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)

Split Banana Peel from Banana, Doc von Schmeltwick (ended September 18, 2024)

Merge Spiked Thwomp with Thwomp, Blinker (ended November 2, 2024)

Writing guidelines

Repeal the "derived names" having priority over official names in other languages

Recently, a (completely undiscussed) amendment was made to the naming system making it so quote-unquote "derived names" - as in, standard conjectural names made by cut-n-pasting descriptors from similar entities - have priority over official names from other languages (particularly the games' language of origin, which for this franchise is usually Japanese). While allowing said "derived names" as conjecture makes sense, it comes with several pitfalls, and my main concern is it is turning into a slippery slope. Much of it is discussed on the talk page for the so-called "Hefty Goombrat," which is a sterling example of why this was not a good idea. I have also been recently seeing cases of people moving to subjects based on objects sharing some adjective with a random obscure object in the same game, as demonstrated here. To be blunt, this was a short-sighted idea (and more than likely, simply a failed experiment) and needs cut back to a reasonable level before it gets out of hand. For the record, I am favor of letting it stay when the only indications in other languages or file names or what-have-you are generic terms rather than clear "names," for instance when the only confirmed name for Shoot was just "jugador de futbol," as well as rewording clunky generic descriptors like "vehicle with surfboard."

Proposer: Doc von Schmeltwick (talk)
Deadline: May 13, 2024, 23:59 GMT

Support

1. Doc von Schmeltwick (talk) - Per.
2. Hewer (talk) Per proposal, these names are conjectural and shouldn't be unduly given more weight than their fellow conjectural names.
3. Koopa con Carne (talk) Might just be me but I'd rather not have a policy that specifically states "if you don't like this official name, just completely ignore it and make up something wacky instead" because that's not what this site is even remotely about
4. Axis (talk) Per all.
5. JanMisali (talk) Per proposal. While some of these derived names are fine and it's sensible to have this as an option, it shouldn't take priority over an official name when one exists.
6. Camwoodstock (talk) ...Okay, yeah, KCC makes a good point we didn't think of, so, surprise! We're changing our vote! Conjectural names have their place, but we really shouldn't prioritize them over actual names if they exist.
7. LinkTheLefty (talk) I'm pretty sure this all started here, and...yeah, in practice, conjectural exceptions bloat the elegant naming policy. Plus, this is practically begging to have more "Fire Nipper Plant"-esque situations.
8. Blinker (talk) Per all.
9. Somethingone (talk) Per the arguments raised above.

Oppose

1. Archivist Toadette (talk) While I agree that some discussions may need to be made on what counts as derived conjecture and what doesn't, a flat-out repeal is not the way to go about this. Plus, some of these derived conjecture names are completely straightforward (such as "Fire Spike" or "Wonder Hoppycat"), as in we can reasonably assume that Nintendo of America or Nintendo of Europe would pick these names for the respective subject.
2. Waluigi Time (talk) The only problem with this policy is that it's being applied in cases and/or ways that it shouldn't be (I personally think Hefty Goombrat was a step too far). If it's kept to reasonable use like the examples Archivist Toadette gave, it's fine. No need to repeal the entire thing.
3. SolemnStormcloud (talk) Per opposition.
4. Hooded Pitohui (talk) Per Archivist Toadette, really. To me, it does seem greater caution and discussion on these derived names is warranted, but a case-by-case approach seems more useful here than a flat-out repeal. I'd be worried about throwing the baby out with the bathwater, here, tossing away something that's generally beneficial to readers in the process of correcting a few cases where this has been misapplied.
5. Tails777 (talk) Per all.
6. Shoey (talk) Per all.
7. DrippingYellow (talk) I seriously fail to see how this is a problem. If you have a Japanese noun that has had a direct, consistent translation across multiple pieces of English Mario media (i.e. gabon to Spike, kakibo to Goombrat, deka to "Big" enemies, admittedly kodeka for "Hefty" enemies is pushing it since we really only have Hefty Goombas as an official translation), then the way I see it this replacement of terms is no different than how we've been treating internal names. We already have a rule on not "partially translating" names, so I'd maybe expand on that to prohibit creating translations for words that don't have a consistent translation across games, but I wouldn't get rid of the derived name rule altogether. (i.e. Sensuikan Heihō does not become "Submarine Shy Guy" or even "Sensuikan Shy Guy")
8. MegaBowser64 (talk) Per all of yall (collectively)
9. TheFlameChomp (talk) Per all.
10. Sdman213 (talk) Per all.

#Camwoodstock (talk) Per all, especially Waluigi Time. We really ought to be handling poor names born from this policy on a case-by-case basis, rather than nixing the policy altogether and potentially causing more harm than good.

Comments

@Opposition I did say in the last sentence that this isn't removing it completely, just changing its position in the "acceptable naming" hierarchy. The reason I said "repeal" is an incarnation of it existed before for generic-borne titles and I am trying to go back to that as - unlike the current iteration - it isn't just begging to be misused. Doc von Schmeltwick (talk) 02:08, April 29, 2024 (EDT)

I guess the best way to put it is this: if an official name that is a name exists, period, there is no excuse whatsoever for there to be a "conjecture" template of any sort. That's not hypothesizing, that's ignoring, and to be frank is a grotesque perversion of the policies this site has had for decades that have not caused any harm whatsoever - meanwhile, these have plenty of potential for misleading people. Doc von Schmeltwick (talk) 02:08, April 29, 2024 (EDT)

Then what about the examples I brought up? ^(T|C) 07:30, April 29, 2024 (EDT)

What about them? They have official names, but the wiki opts to give them explicitly conjectural ones because apparently a couple of sysops thought so. -- KOOPA CON CARNE 07:33, April 29, 2024 (EDT)

I still find the idea that these names are "conjectural" to be kind of weird, if that's the big hang-up here. If we can already take some liberties with Japanese titles I don't see why we can't just look at something and say "oh, this is literally Goomba's Japanese name, let's just call it Goomba", especially when the name is partially English already. That's just doing some simple translation, not really making conjectural names? I'm speaking as someone with no background in translation, mind you, so take what I'm saying with a grain of salt. -- Too Bad! Waluigi Time! 12:19, April 29, 2024 (EDT)

Conjecture occurs when you're presuming something to be the case in the absence of hard facts. Archive Toadette states in his vote that "we can reasonably assume that Nintendo of America or Nintendo of Europe would pick these names for the respective subject". "Assume". That's the thrust of this policy: assumption. Which is pretty much synonymous with conjecture, and some editors are taking issue with prioritizing that over official names. Regarding the liberties on Japanese names, there's nothing conjectural about adapting something like Sunaipā to "Sniper", because it's literally the word's Japanese transliteration--the romanization reflects how the word sounds when converted to Japanese writing. Note how that policy states that instances of "Kuppa" should be adapted to "Koopa", and not "Bowser", even though that's his Japanese name. "Kuribo" wouldn't be adapted to "Goomba" in article titles because that's not a transliteration, that a compound of actual Japanese morphemes. The basis of the Japanese naming policy isn't the same as that of the conjectural naming policy. -- KOOPA CON CARNE 12:43, April 29, 2024 (EDT)

@Hooded Pitohui: Could you be more specific on what is or isn't acceptable? Because I'm kind of struggling to picture any time these conjectural names should have priority over an actual official name, or what would make that case different to others (note that they'd still take priority over filenames per the proposal). Hewer (talk · contributions · edit count) 13:01, April 29, 2024 (EDT)

I think it may be helpful to start with a disclaimer and an acknowledgement of where I'm coming from in casting a vote. I'm a very infrequent, casual editor on the wiki side of things, so when I do wade into these proposals on the intricacies of the wiki's policies on naming or classification or scope of coverage, I don't often have a large repository of examples to draw upon, and rarely am I able (or attempting to) make any kind of case or argument. Generally, I'm entering these discussions from the perspective of a reader/user of the wiki first, and casual contributor second, and generally my votes are going to be informed by that perspective, so I apologize if this seems a bit broad and dealing in hypotheticals. For me, I'd think anything that's a straight localization of a recurring, official enemy/item/what have you is acceptable, and more adjectival/descriptive parts of a name or a name of something that hasn't really had a localization established is not. To use the cited Hefty Goombrat example, "Hefty" probably shouldn't have been conjecturally localized, but a Goombrat is pretty clearly a Goombrat, so conjecturally localizing that part seems fine to me. If, I don't know, Nintendo introduces a Lakitu that throws fireballs down that become Firesnakes, and it's called "[something] Jugem" officially in Japanese material, again, I think we leave the descriptive part as-is because there's no clear precedent, but we know a "Jugem/Jugemu" is consistently localized as Lakitu, so we might as well localize that because an average reader will recognize "Lakitu" quickly. Meanwhile, if we just got, say, a generic cloud spitting fireballs with the same behavior, I'd say we'd be wise not to do a conjectural localization because there's not clear precedent for what that'd get localized as. Of course, even always following really clear, solid precedent, we might get it wrong occasionally, especially if Nintendo decides to rename a recurring enemy at some point, but it's a wiki, information is constantly getting updated, renamed, and reevaluated anyway. Hope that helps explain my reasoning a bit better! Hooded Pitohui (talk) 13:26, April 29, 2024 (EDT)

Slippiest of slippery slopes. Just use redirects if you expect casual readers to look up for a thing more intuitively than how it's been officially presented. There's no need to compromise encyclopedic integrity to cater to what readers expect to see. -- KOOPA CON CARNE 14:06, April 29, 2024 (EDT)

For the record, this isn't a talk page proposal, so I think the deadline for this proposal should be May 6. Unless there was a statement of "you can make the proposals two weeks long if you want" that I missed in the rules, which is entirely possible. DrippingYellow (talk) 19:21, May 1, 2024 (EDT)

Writing Guideline proposals also last two weeks, like TPPs. Tails777 Talk to me!

Oh, I didn't notice that in the rules. I guess that makes sense. DrippingYellow (talk) 11:30, May 2, 2024 (EDT)

New features

Create The Cutting Room Floor link template

"Pre-release and unused content" articles already link to The Cutting Room Floor very often, and since they are established as the to-go wiki for that kind of information, I propose we formalize the linking with a template just like the Wikipedia template.

This is how it could look:

If in a "List of pre-release and unused content" article:

If in a main game article:

Proposer: Bro Hammer (talk)
Deadline: May 7, 2024, 23:59 GMT

Support

1. Bro Hammer (talk): Per my proposal.
2. Super Mario RPG (talk): This is a good idea.
3. Pseudo (talk) Per proposal. This is a really high quality wiki.
4. SONIC123CDMANIA+&K(B&ATSA) (talk) As someone with a account there, per all.
5. Scrooge200 (talk) I don't edit there anymore, but it does help coverage.
6. Camwoodstock (talk) We're surprised this hasn't been added sooner, all things considered. Per proposal.
7. Arend (talk) Per all.
8. Doc von Schmeltwick (talk) - It'll also make it easier to source info and graphics from them, especially given many of out own P-R&UC pages are... lacking (especially since the giga-leak in regards to prototype information and graphics).
9. Archivist Toadette (talk) Sure, if it helps expand our coverage gaps.
10. FanOfRosalina2007 (talk) Yes, please! I think we've been in need of this for a while, and TCRF is a high-quality site. (I should know, because I have an account there... :)) Per all.
11. Superchao (talk) Per all, nothing wrong with another affiliation.
12. TheFlameChomp (talk) Per all.
13. Sdman213 (talk) Per all.
14. YoYo (talk) lets not put this on the cutting room floor since it's a good idea

Comments

Could you change the links on the template from external links to interwiki links, like this one? The Cutting Room Floor is on our interwiki list, after all, and that would look much better on the template than the external link thing. rend (talk) (edits) 05:01, May 1, 2024 (EDT)

Done! Bro Hammer (Talk • Cont) 08:19, May 1, 2024 (EDT)

Removals

None at the moment.

Changes

Non-standardize franchise sub-headings in History sections

This proposal aims to non-standardize -- not outright forbid or penalize -- the use of "franchise" subheadings under History. In other words, should this pass, if someone gets rid of franchise sub-headings in favor of series or standalone game sub-headings, someone is not allowed to revert it and must leave it as-is. Otherwise, users are allowed to add the sections at their discretion. Think of it like the Cite template, which is standardized but not required.

I never understood the need for the franchise subheadings (with three equals signs), since it just adds an unnecessary extra heading in the page text. It's like if we had a "Super Mario franchise" section and began listing various subsections under it. The points I'm making below may digress from the proposal, but could provide insight as to why I think it muddies the waters too much by giving individual franchise sections.

I feel that it shouldn't be this wiki's job to decide which game goes into what franchise. To give some examples, Nintendo has not taken the effort to, let's say, classify Yoshi's Safari as a Yoshi game on par with the Yoshi's Island series, and I haven't seen Wario's Woods being listed among the likes of Wario Land series, not to mention Wario is the main antagonist of Wario's Woods, despite his name in the title (though could similarly be said about DK arcade game). And Mario vs. Donkey Kong could either be a Super Mario game, since it stars Mario, or a Donkey Kong game, but I'm more inclined toward the former, since all the sequels (minus the Switch remake) do not retain any elements from the Game Boy version of Donkey Kong, and Donkey Kong is the consistent antagonist.

So with the examples listed, see how it kind of muddies the waters? And if future proposals or discoveries determine the games to not be part of the franchises, or the franchises themselves outright nil, then that would be numerous pages to clean up on, should the franchise sub-sections be applied to the wiki universally. Even if it may appear disjointed on some articles, the point is still that these are still Super Mario characters starring in their own games, not different than Captain Toad, Princess Peach, and Luigi's Mansion, all of which are explicitly Super Mario games but starring different characters.

In the Smash Bros. series, I am aware that Wario, Yoshi, and Donkey Kong have distinct symbols, but that could reflect their protagonist status, not their own series.

Edit: Another problem from using franchise sub-sections is that would mean game sub-sections could have five equal signs if branching off of a series subheading of a franchise sub-heading. An example of how that would look: ===Yoshi franchise=== ====Yoshi's Island series==== =====Yoshi's Island DS=====

Proposer: Super Mario RPG (talk)
Deadline: May 14, 2024, 23:59 GMT

Support

1. Super Mario RPG (talk) As proposer.

Oppose

1. Nintendo101 (talk) I cannot speak for anyone else, but I find it genuinely difficult to find topics when they are not grouped into franchise headers like this, especially for long articles, and it can be frustrating. I can understand not putting Wario Land and WarioWare titles together under a "Wario (franchise)" heading, but Yoshi's Woolly World is a Yoshi's Island game in everything but literal name, and it is unintuitive to not group it with those titles for recurring subjects. Same with Donkey Kong Jungle Beat and the other Donkey Kong platforms. Smash Bros. did not invent the idea of grouping these franchises together. Nothing is lost when these subfranchise headings are maintained - only gains for readers.

Comments

Except the Yoshi's Woolly World is not a Yoshi's Island game, since those have Baby Mario in it, but reuses concepts from said series. And the "Donkey Kong platforms" already have two series of their own: Donkey Kong Country series and Donkey Kong Land series, and then there's the unassociated games like Donkey Kong 64 (which i used to think was a DKC game) and DK Jungle Beat Super Mario RPG (talk) 19:19, May 7, 2024 (EDT)

Miscellaneous

None at the moment.