MarioWiki:Proposals

Current time: Monday, November 4th, 07:53 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 4, 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

• Remove "(series)" identifier from titles that don't need it (discuss) Deadline: November 5, 2024, 23:59 GMT
• Split sections between Tanooki Mario and Kitsune Luigi (discuss) Deadline: November 10, 2024, 23:59 GMT
• 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

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)

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)

Create Secret exit article, EvieMaybe (ended October 15, 2024)

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

List of Talk Page Proposals

• Split the sections Attackathlon, Toad Quiz and Lakitu Info Centre into Template:Fakelink and Template:Fakelink (Discuss) Passed
• Split Spiny Fish from Spiny Cheep Cheep (Discuss) Deadline: May 2, 2016, 23:59 GMT

Writing Guidelines

None at the moment.

New features

None at the moment.

Removals

None at the moment.

Changes

Merge all YWW [X] Patch Articles with Their Non-Patch Articles

In Yoshi's Woolly World, some enemies, such as the Ruffin Tumble, have a patch form, that is simply a pixelated version of the original enemy; they're the exact same as the originals, except that they look different and that the patch forms are seen in blocks, and are released after the block is eaten. I don't think that one minor difference is enough to warrant separate articles for the original and the patch form. The only thing that might be a problem is their positions in the Scrapbook Theater, but I'm not sure that warrants separate articles either.

Proposer: Roy Koopa (talk)
Deadline: April 18, 2016, 23:59 GMT

Support

1. Roy Koopa (talk) My proposal.

Oppose

1. Superchao (talk) Looking at the Dream Team enemies, the R enemies all have separate changes, despite being only recolors with different stats. For consistency, the patch enemies should keep their own pages.
2. 3D Player 2010 (talk) per Superchao
3. LudwigVon (talk) - Per Superchao.
4. Bazooka Mario (talk) I don't necessarily agree with comparison Superchao is trying to make. We separate R enemies because they're treated as separate enemies, supported by stats and a recolor. We do sometimes merge mere aesthetic variants such as the Scarescraper ghosts. I do oppose because there are only four patch enemies in the game, so all we're getting are four harmless small articles on a minor aesthetic variant. You can also argue that the methods for encountering them is different compared to the standard enemy as another case to leave them split, but just the amount of articles alone tells me it's okay to leave them as standalone.
5. PowerKamek (talk) Per Superchao and Bazooka Mario.
6. Niiue (talk) Completely different enemies. Per all.
7. Ghost Jam (talk) Per Bazooka Mario.
8. AfternoonLight (talk) Per Bazooka Mario!

Comments

It may be an issue if all enemies have a patch form, but it seems to me that we have only Bullet Bill Patch, Monty Mole Patch, Nipper Spore Patch, and Ruffin' Tumble Patch that exist. Maybe it's not so bad that we leave it as it is? It's me, Mario! (Talk / Stalk) 19:14, 11 April 2016 (EDT)

Create a template for proposal outcomes

The current coding for the proposal outcome is repetitive and cumbersome to remember every single time we need to archive a proposal, which has resulted in inconsistent headers (we first used Times New Roman, then switched to Comic Sans, and we're allowed to do that because one, there's virtually no guideline on this, and two, the coding is a crap to remember). So, exactly why isn't the outcomes in a template again? Repetitive coding is essentially template fodder, and there's no reason why we need to remember and duplicate difficult to remember coding when we can simply remember a template and use switchers to depend on the outcomes of a proposal. ‎Megadardery (talk) has created various templates in his sandbox pages to demonstrate how we can use the template to make archiving proposals easier.

• A test on how the new template will look like.
• Draft page for the template

In the long term, I believe this will greatly benefit users who want to archive older proposals and will make remembering the exact coding less of a hassle.

Also, this will eliminate the egregious misplacement of the notorious and extremely unprofessional Comic Sans font, which will be replaced by Verdana. Comic Sans is not a web-safe font, and any browser who doesn't have it installed will fallback to Arial and therefore look incredibly inconsistent with different browsers, whereas, Verdana is a web-safe standard font that should be used for more professional headers, especially those that notify readers the outcomes of important wiki matters. If past "minor" problems such as the misuse of subspecies and beta elements can be addressed, I don't see why it's particularly difficult to address what is essentially a design problem, which is more important to others than others, like terminology. The little things matter too.

Update: Both options have been merged into one, increasing flexibility of the template.

Proposer: Baby Luigi (talk), with great help from Megadardery (talk)
Deadline: April 26, 2016, 23:59 GMT

Implement

1. Baby Luigi (talk)
2. Tucayo (talk) - Why shouldn't we make things easier whenever we can?
3. Mister Wu (talk) I agreed before, I'll agree now! A template is better to avoid errors and inconsistencies!
4. LudwigVon (talk) - Per proposal. Much better than what it is currently used.
5. Megadardery (talk) Per all, I always found it annoying to copy-paste old codes, this template is going to make it more consistent and easier to use.
6. Bazooka Mario (talk) It's worth standardizing the formatting for the proposal outcomes, especially since such text should go in a template since they're repetitive and are found in several pages, exactly what templates are for. While comic sans dominates proposal outcomes, we also have a few off Times New Roman-styled outcome text lying around, so we should fix that too. That means getting rid of the comic sans: the typeface clashes with everything else (especially since we're supposed to be a serious wiki) and, as a result, the casual, unsophisticated typeface appears ugly and sloppy, which goes against our idea that proposals should be serious matters. Years of careless handling with typefaces do not justify continued mishandling nor do years of editor oversight on what should've been a template in the first place. The only reason it is tedious to change them is the result of that error. Once the changes are done, everything will be much easier to manage, from the template itself to how proposals should be archived. I also think we don't really need to change to Verdana since the font (the colors, size, and bold, that is) does a good job at helping it stand out. Sure, it might seem all minor in the end, but the little stuff shouldn't be disregarded. We should regard every aspect of the wiki as if we care; the egregious use of comic sans gives off the vibe of carelessness. This is an easy, harmless fix. The biggest issue I find is that many of these outcomes are tucked under protected archives, but that in of itself shouldn't be a reason against this change.

Comments

Maybe we can take a step further and color-code proposal outcomes similar to color legend in the proposals archive? It's me, Mario! (Talk / Stalk) 18:47, 18 April 2016 (EDT)

i don't know, i think it's a bit complex to remember what passed and what didn't, and over time, we might have to remember to change it. I think sticking to a three color scheme would keep those simpler. You also have to keep in mind that this also applies to TPP, not simply mainspace proposals, so more stuff gets affected. Ray Trace^(T|C) 19:02, 18 April 2016 (EDT)

It is the simplest thing currently: green passed, red failed, gray has no impact.--

19:05, 18 April 2016 (EDT)

---A spontaneous idea is that we could technically allow both ways of using the template.--

19:09, 18 April 2016 (EDT)

I wouldn't be 100% opposed to this, but wouldn't it overcomplicate things? Ray Trace^(T|C) 19:10, 18 April 2016 (EDT)

I did it with a slight modification. If you feel that this creates an inconsistency you can revert it, it's your idea after all.--

19:13, 18 April 2016 (EDT)

I'm a stupid layperson, so it's pretty unclear to me what you changed. Ray Trace^(T|C) 19:15, 18 April 2016 (EDT)

"Comic Sans is not a web-safe font, and any browser who doesn't have it installed will fallback to Times New Roman"

It'll actually fallback to the default Arial typeface, so that's not a valid point. It's me, Mario! (Talk / Stalk) 20:41, 18 April 2016 (EDT)

whatever Ray Trace^(T|C) 21:33, 18 April 2016 (EDT)

@Mister Wu: tie is basically no-quorum, I created that because it is certainly easier to write than no-quorum, even if it is technically incorrect. The end result is the same. In reality, the template defaults to the no-quorum if you don't specify/specify something incorrectly.

@Baby Luigi: right now, if you specify a color (red,green,gray/grey) in the first parameter you can use the second format, otherwise you default to the first format. The usage didn't even get a slight change. And the template edit is just ~55 bytes. Fundamentally I removed the second version so this proposal can focus on the idea of implementing a template in the first place.--

05:13, 19 April 2016 (EDT)

Sounds good. I think I'll just remove option 2 and I'll reset the votes considering that options have been changed (but not the proposal itself). btw, which link to the coding itself is the updated one, so i can link it to my proposal? Ray Trace^(T|C) 10:57, 19 April 2016 (EDT)

Merging option 2 in makes me slightly tempted to oppose. As I said in my original vote, "More parameters might be slightly more complex to use, but make it much less likely that things will end as a mess of inconsistency all over again." I really think this is a serious misstep... - Reboot (talk) 11:07, 19 April 2016 (EDT)

@Baby Luigi: It's already been updated. The template draft stayed at User_talk:Megadardery/2 and the usage doc stayed at User_talk:Megadardery/1.

@Reboot: The usage didn't get the slightest modification, it was simply merged with the other version. You can use whichever you want. The parameters stayed as simple as they were. Check the usage page again.--

11:12, 19 April 2016 (EDT)

I think his concern is that the extra parameter is overcomplicating things. Like, he would like things to be kept consistent. Besides, uh, is there any use for the color parameter option? I think the simply "passed" or "failed" covers all bases when dealing with proposals. Ray Trace^(T|C) 11:15, 19 April 2016 (EDT)

exactly, it is just a different way to use the same template. I told you that you can revert it if you want, I don't mind which way the template is implemented, I only care that a template is implemented.--

11:23, 19 April 2016 (EDT)

Nothing to do what *I* would do, and everything to do with what "random percentage of userbase" would do. Basically, I think if there was only one set of fixed options, it would stop things devolving into a ****ing mess all over again. Having the open "option 2" variables available means things will go wrong.

IOW, I think having "option 2" available as well is a Bad Idea if the idea of this is consistency. It should be either/or, and since there's a finite number of outcomes, best to have them locked-in as in "option 1". - Reboot (talk) 17:57, 19 April 2016 (EDT)

Hm, I don't think option 2 is even necessary either, given how superior and cleaner the first one is. The outcomes in the first template are already color-coded and there seems to be no real reason to use different colors outside of red, gray, or green. My suggestion was just a passing thought, but even then, there shouldn't have to be a separate color parameter. It's me, Mario! (Talk / Stalk) 19:12, 19 April 2016 (EDT)

Reorganize species designations in Koopa (species) and Koopa Troopa

See one of Walkazo's essays for a start.

Note: Unless otherwise stated, all referrals here to "Koopa" are intended to mean the Koopa family that consists of turtle-like creatures; examples are Koopa Troopas, Hammer Bros., Lakitus, Shellcreepers, Buzzy Beetles, Spike). The Koopa Troopa species, often shortened in the games as "Koopa", will be referred as the full name; examples are Koopa Paratroopas, Dry Bones, Koopa Striker,

Throughout the wiki's history, there has been confusion surrounding the Koopas as a group of turtle-like creatures and the Koopa Troopa species, mainly how and where to categorize species in these groups. Since there isn't clearly defined taxonomy and "Koopa Troopa" is often shortened to "Koopa", there is always an unclear way of handling these two pages, and, as a result, they're a total mess (with the misuse of subspecies terminology aggravating the situation). The Koopa (species) article, for instance is wildly inconsistent and incomplete. The derived species list under the infobox includes several sorts of stuff including the basic parent species such as Hammer Bro. and Koopa Troopa (not all of them), but also sometimes derived species from them including Ice Bro. and Beach Koopa. By containing several Koopa Troopa derivatives, the article focuses on Koopa Troopas, which feeds into the confusion and leads users to think that this page is redundant with the Koopa Troopa article. The Koopa (species) is needed though, as Bowser, the Koopalings, and Bowser Jr. are not defined aside from being part of the Koopa family, and it would be convenient that other turtle-like Koopa species such as Lakitus, Hammer Bros., and Buzzy Beetles be placed under this article rather than get awkwardly lumped with Koopa Troopas.

The common question is, "What is the difference between a Koopa and a Koopa Troopa?" The logical answer would be that "Koopa" is an umbrella designation to turtle-like creatures in the Mario series. Koopa Troopas are the most common member under this Koopa family. The current state of these articles, however, fail to adequately answer this. While it's true that Koopa Troopas are often shortened to "Koopas" because they're the quintessential Koopa, the focus on Koopa (species) should not be Koopa Troopas. The article instead should cover all creatures that are deemed Koopas (including derivatives), logically or officially, and organize it by basic species. To avoid having it becoming a souped up category or list, the species and their variants will have a short description. Here is one example: There is a section on Lakitu showing a short paragraph on the basic enemy, and Lakitu's variants are listed as one-liner annotated bullet points (the header for this section should be "Lakitu variants" or "Other Lakitu species", though, not just "Lakitus", for the sake of being technical). Unfortunately, the late Walkazo had not brought up the issue of derived species from derived species such as Dull Bones nor is there a discussion on species derived from multiple sources such as Shady Paratroopa. I do, however, suggest that we nest these kinds of species as a double bullet point under their parent species, and creatures with multiple parents are listed twice, similar to how we organize List of species. Check this revision of my sandbox for an idea.

This proposal will not end speculation such as determining Sumo Bro. and Hammer Bro.'s relationship, but it will clear up the confusion between Koopas and Koopa Troopas which lead to illogical statements such as assuming Bowser or Lakitu are types of Koopa Troopa.

Some changes on categorizing Koopas and Koopa Troopas have already been set in place, but this proposal should set these changes rolling into a more organized and concrete form.

In short

• Koopa (species) will include all Koopa creatures. We organize by basic species, alphabetically, and in derived species, we use bullet points followed by a short description.
• Koopa Troopa will include only species that are or are a type of Koopa Troopa. This means we remove references to Hammer Bros., Magikoopas, Mechakoopas, and Spinies in the list. What is under the Koopa Troopa article infobox should be something like {{Koopa Troopas}} or the in the related species section in the Koopa Troopa gallery page.

Proposer: Bazooka Mario (talk)
Deadline: April 26, 2016; 23:59 GMT

Support

1. Bazooka Mario (talk) If this proposal passes, we can expect to clear up confusion that have plagued wiki editors for years, outlined in the Koopa (species) talk page and in Walkazo's essay page I mentioned earlier in this proposal. We can improve the quality greatly of the Koopa (species) article and somewhat of the Koopa Troopa article once this is completed.
2. Baby Luigi (talk) Per proposal
3. LudwigVon (talk) - Per proposal.
4. Gabumon (talk) - Clear definitions are always preferrable over ambiguity. Many pages on this wiki have the problem that they're trying to cover several widely different subjects where one would suffice. If this proposal helps to alleviate that problem, I am all for it.

Comments

Isn't this why we have the {{distinguish}} and {{distinguish2}} templates? --Wildgoosespeeder (talk) ^{(Stats - Contribs)} 21:57, 19 April 2016 (EDT)

I believe the issue is more complex than that, though I guess we could make good use of those templates in the meantime. It's me, Mario! (Talk / Stalk) 22:09, 19 April 2016 (EDT)

Done. --Wildgoosespeeder (talk) ^{(Stats - Contribs)} 23:32, 19 April 2016 (EDT)

I've seen the sandbox, and I'm wondering if it would make sense, in the case of multiple species, to cite the main species among the derived ones, with a "The family of the X species" title to the list (maybe it should be genus, but probably family is easier to understand and, most importantly, its taxonomic sense can be removed to avoid biological speculation). Also, what about an image for each family?--Mister Wu (talk) 22:00, 19 April 2016 (EDT)

Well, the paragraph of information already pertains to the main species in the sandbox (which is taken from late Walkazo's prototype), unless you mean derived species with their own derivatives including Paratroopas and Dry Bones. Oh, we can always put the image in each family, no hurry for that. It's me, Mario! (Talk / Stalk) 22:09, 19 April 2016 (EDT)

Just a matter of classification - you talk about the generic characteristic of the family and then you list the species - which means that also the species that gives the name to the family is in, just like the red fox (Vulpes Vulpes) is among the other foxes. In your example, you're giving the link to Hammer Bros. in another place, which might be confusing.--Mister Wu (talk) 22:16, 19 April 2016 (EDT)

Pardon? Je ne te comprends pas. I organize this by parent species, not necessarily by generic characteristic. Parent species are generally the most well-known of the family so it would make sense to have a paragraph on them and then have the minor derived species with a small description listed underneath. If that's what I'm getting from you. It's me, Mario! (Talk / Stalk) 22:52, 19 April 2016 (EDT)

Miscellaneous

None at the moment.