User:Walkazo/Essays

Here's where I shall rant about my views on the Mario series or the Super Mario Wiki itself and/or draft stuff to actually use on the wiki. Old stuff includes:


 * Courtesy
 * MarioWiki:Redirect (formerly)
 * Template:Wikipolicy
 * Categories
 * Proposal Archiving
 * Template:PArchive
 * Proposals/Archive
 * Proposals/Archive_Template
 * Version Differences

Navigation Templates

 * Templates to fix
 * white overall backgrounds; solid grey borders; footnotes darker than headers, lighter than banners
 * alternating bg stripes; darker bg stripes first; if only two lines, both bg stripes dark
 * headers centered and subheaders right, or both centered? simply right when no subheaders


 * ''( - unique colours: add to chart below G&W)
 * series items
 * (series)
 * - items
 * ''(, - unique colours: classify as species)
 * - golf series characters
 * DK templates - levels
 * ''{{{tem|NSMBW}} - "further info" is good way to include subpages/galleries/etc.)
 * - could be merged with YI and YIDS, but YTT has no template yet
 * - do something with it

Infoboxes
'''make log and tattle different - light/neutral? with (horizontally compressed) bestiary as the dark one/another-light-one on far right (so actually 6 columns)?

There are 11 variables to this template. Only 6 are needed for PM enemies, 8 for PM2 enemies.

Align takes care of the alignment of the table (default is right). If the enemy is in both games or all 3, use this template twice (and ) in one section, aligning them all to the center, making a nice comparison. Ignore and leave PM2 blank if it's a PM enemy. If it is a PM2 enemy, fill in yes. The extra fields log, items, and the bestiary end section will appear automatically so you can fill in those sections. Name is for the rare case when there is a small difference between the names in different games (i.e. Spiked Goomba and Spiky Goomba) or a quantifier is used in the page's title (i.e. something in brackets in addition to the enemy's name); the default is. Image is still optional.

......

This template is for information on enemies in Mario & Luigi: Superstar Saga. Here are the variables:

* The asterisk'd ones are ones that can be changed by Badges and Equipment from E. Gadd, as explained in the hover-over text.

Also, if no items can be dropped, put "none" in that variable.

There is no POW/Attack Power statistic for this game.

Lastly, if you want to know the exact HP, Power, Defense, and Speed stats, look here.

BS Super Mario USA
From my forum post here, from Feb. 21, 2012. (For admin eyes only.)

A translation of the ending dialogue is here, but it's not overly useful for plot stuff. The first episode's opening is on Nico Nico Douga (but I viewed it through page), and the entire fourth episode is on youtube: it's got the ending with narration and also the same opening as the first episode except for different closing enemy banter and one missing line from the Commander.

When I transcribed the text, I had only been studying Japanese for six months and listening comprehension was my weak point. Still is, but when I get a chance I'll give the videos a re-listen to try and figure out the stuff I missed before. Even in this crappy, unfinished transcription (italics and question marks are stuff I'm not sure about at all) and translation, however, some key plot points are quite clear.

Crappy transcription:

Narration: Yume no kuni Subcon. Kono kuni wa sono munokashi yasai ga daiki na Mamu to sono uchi ni otte kurushii me wa rarette imashita. Soko ni owarette ano wa onajimi Mario, Luigi, Kinopio, soshite Peach-hime. Kono yo-nin no daikatsuyaku no sei, Mamu wa sono uchi ni yasai yo ippai nitsu me komare, Subcon kara oidasareta no desu. Tokoro ga kurushii me rarette de Subcon wa hitotsu dake de wa arimasen deshita. Hito-bito no miru yume to onaji kase dake Subcon wa attano desu. Nigesata Mamu to sono uchi ni wa soto betsu na yume no naka ni moguri komi. Nandomo nandomo akuji o kurikashite tanō deshita. Commander: Ōsama, hoshi no chikara o tsukatte, Subcon o mamorimasho. King: Yoshi, Mario-kun-tachi onegai sho. Narration: Kōshite mata-mata ano yo-nin ga katsuyakusuru koto temota no desu. Shikashi, hoshi no chikara o tsukau, dōshite ano e wa Ōsama-dachi dake dewa imasen deshita. Ano Mamu to sono uchi ni mo chika wa kui o shio to takuramu de imasu. Sono de hajime ni donchuru de ga me wa no akashii ano o gondo Mario. Sō doko ga me kakushite mata yo desu.

Crappy translation:

Narrator: Dream land Subcon. In the land, in a chest, are important vegetables - the painful sprouts that can drive away Wart and his group. There at the end are the familiar Mario, Luigi, Toad and Princess Peach. because of the foursome's great efforts, Wart and his group were packed full of vegetables and expelled from Subcon. Only one place of the painful, capable sprouts of Subcon was not there. The people [thought] Subcon had only been a dream. Wart and his group escaped outside and dived into a separate dream. Many times they repeatedly [did] various crimes. Commander: King, let's use the power of the star and protect Subcon. King: All right, [get] Mario and friends, please. Narration: Thus, those four [were] made active again (which they were not intending to be). But the star power is used, [only???] why is the King's group missing? Wart and his group were also underground ??? plotting. First [find the ???] sprouts Mario. So, where have the sprouts been hidden again?

Basically, the narration confirms that Mario & Co. initially bested Wart with veggies and kicked him out of Subcon, but they thought it was a dream, but then Wart & Co., who had been hiding in another dream, come back and run amok, so the King summons Mario & Co. and they spring back into action again, only to find the King and his people gone (I'm not sure if he's kidnapped, however).

Table coding
Nested table, gradients, borders.

And to make it float...

(Also, note that the width of the background columns has to be of the overall template width - i.e. 17% gives you (approx.) half of 35%, whereas 50% just makes the column in question grow huge and the other one turn as skinny as the longest word will allow it.)

Sorting Table
"Title" = abc order; "Date" = default = release date order (reverse puts series at top); "Series" = abc order; right "#" = date-by-series order

Navbar
User:Walkazo/Nav - Usage:

Now, if only there's a way to automatically get it to appear in the templates, rather than manually transcribing it and entering the template name as the variable... There probably is, but haven't found it yet - wikipedia's impossible to track back to the source - it's all weird "modules"...

MediaWiki:Common.css

Will have to do the first one for the templates overall (much shorter than the current one: "!important" seems to override all other types of links' colours*), and the second one for all the light nav templates (just adding "!important" to the exiting lines*). Test it using "Inspect element" (right click on page) and using the "new" function in the "style editor" tab, and use " " to see the variety of link types magically change when you paste the css stuff; can use different colours for extra fun.

* It's apparently lazy coding? But it works well, and the black spp code overrules the general navtemplate white stuff since it's more specific, so it seems good?

Super Princess Peach

Kong family

 * Wiki stuff (all-in-one to avoid headches)
 * TMK's Kongtroversy and any official stats/bios on out wiki were used to make the chart.
 * Not showing non-game material that contradicts game stuff (see TMK)
 * The names in the cells show what articles are covering the games
 * The columns are trying to place the Kongs in relation to each other and to other games based on bios/in-game text, etc.; if a name spans multiple columns, it's been left ambiguous; if a column is split (i.e. DK III), it's because it could be either name representing that generation, usually due to ambiguity over which generation the older Kong was part of (which is also why there's a "DK IV/V" column - which it is depends on whether Cranky is generation II or III).
 * Green is using context to place Baby DK (non-canon, just for convenience).


 * Interpretation stuff (while I'm at it)
 * Line skips indicate years passing
 * Assume "cold-hearted northerners" of MK8 could mean something other than vikings and ignore it
 * All other DK Arcade appearances are DKJr-DK-I
 * The Konga placement is inspired by SiFi.
 * I forget where I first read the fan-theory about DK:JB being arcade-DK Jr. and DKC-DK being his kid
 * All other DK (i.e. Barrel Blast, etc.) and Mario (including MvDK) appearances are DKC-DK-III
 * SSB is non-headcanon

Image Check
Check to see if the transparency is good, or crappy:

MarioWiki:Image Maps
Image Maps are templates consisting of a single background image that links to different pages, depending on where the image is clicked. They are used for matching locations in a game with their locations on in-game maps and are a visual counterpart to traditional name-based navigation templates. They are useful for game, world, and overworld location (e.g. Beanbean Kingdom and Bowser's body) articles. Navigating between specific level and location (e.g. Beanbean Castle and Rump Command) articles, however, should be covered by regular navigation templates found on every page. This policy page outlines standards that must be followed when creating a Image Maps template.

Creation

 * The Image Maps must use a map sprite from the game (e.g. this), a screenshot (e.g. this), or an official map artwork (i.e this). If no official maps exist, no template can be made. Fan-made maps are not allowed.
 * Maps should be in one piece by default: separate world maps should not be pieced together to form a single overworld map (unless the complete map exists, but is never visible in a single frame in-game - but even then, it would be better to wait for the full map to be provided by Nintendo or ripped rather than piecing together screenshots). The only exception is combining maps of different levels of a building to create a single floorplan, such as.
 * If the names of the levels or locations in a map are visible in the image itself, an Image Map is unnecessary and should not be created.
 * Image Maps usually need 8 or more links in order to be worth making: simpler maps can just be explained in the articles' texts.
 * Image Maps must be large and clear enough to make it easy to tell locations apart and click on them. Otherwise, they are not helpful for understanding the maps or navigating to the areas pictured and should be avoided.
 * In general, 400px should be a good width/height (depending on the orientation), such as or, although simpler maps may be smaller (like ), and more complex maps may need to be larger (such as ).

Design

 * Locations that are widespread in the map should have multiple link sites to make it easier to identify them and/or locate said links.
 * The default link should be to the file page of the image being used (like how normal images included on articles link to their file page when clicked), rather than the overall location, as most Image Maps will be on the article already, or have it mentioned in the corresponding text in the page it is placed on.
 * Locations that are not pictured on a map should not be linked to (i.e. do not infer where they would be relative to the pictured areas; for example, in, Star Shrine is technically located on top of the Star Hill, but should not have a link since it is not shown). Only the text of the articles should mention and link to the areas that are not pictured.
 * Image Maps must always be captioned in order to inform readers that they are looking at an Image Map and not a simple image of a map. The standard message is: "Click an area to open the relevant article."
 * Image Maps that are only used in infoboxes must be classified as  and it must be aligned in the center, while maps that will not be used in infoboxes should be classified as a   and will usually be aligned to the right.
 * If an Image Map will be used in both infoboxes and as embedded images in text (such as an infobox on the location article and in the text in a game page), a variable must be declared. If it is set to, it will be classified as   and aligned in the center. If it is not set, it will be classified as a  , and should generally be aligned to the right.

Placement

 * Image Maps depicting the overworld of a game should be placed on the articles corresponding to the overall location pictured and can also be put on the game pages (f.e. can be placed on Dinosaur Land and Super Mario World), but should not be placed on the specific locations shown in the map (f.e.  should not be placed on Chocolate Island, Cheese Bridge or Donut Plains 1, etc.). If the map itself has an article due to being an object in-game, the Image Map can be placed there as well, such as  being placed on Beanbean Map.
 * Whether the Image Maps occur in the infoboxes or are placed elsewhere in the article depends on the structures of the article and what other images are available.
 * Image Maps depicting worlds in sidescrollers should always go in the infoboxes at the tops of the world pages (i.e. they should go in or a corresponding game-specific template), but should not go in the specific level articles. For example,  goes in World 1 (New Super Mario Bros.), but not in World 1-1 (New Super Mario Bros.), etc.
 * If a game does not have a single overall map, once all the specific worlds have Image Maps, they may all be stacked up and included in the game's article instead, but this is not absolutely necessary and is discouraged if it will look cluttered, such as due to a large amount of worlds or the design of the Image Maps (e.g. Image Maps such as are not suitable for stacking). Only using one or a subset of Image Maps on a game page looks incomplete and sloppy and should not be done either.
 * The image used in an Image Map and the template itself should not co-occur on a page: the Image Map should be used in place of the regular image. The plain images can instead be included in the game's gallery page.

Creating the Image Map

 * 1) First thing is specify the image, upload one if none exists.
 * 2) Specify the name of the template that will contain the Image Map, which should generally take the form of "Template:NAMEmap", where "NAME" is an acronym of the game's name. If there are multiple world maps in a game, the names should take the form of "Template:NAME-W#map", where "W#" is substituted with "W1", "W2", etc. (or the name of the world, if applicable). There is some flexibility, however: as long as the subject matter is clear from the title and there is consistency between different world maps in a game (and/or between games in a series), it should be fine.
 * 3) Start coding the template. If you cannot specify the coordinates, you could use online tools such as this. (But change the output to "Wiki imagemap")
 * 4) Once done, preview the template to make sure that it appears correctly, and that the links work (just make sure to open them in another tab by pressing CTRL or right-clicking, so as not to loose your progress).
 * 5) If everything works correctly, save the template, and start adding it to articles.

Basic coding

 * : The name of the image for the map (e.g. ). Note that is is included a second time at the bottom as the default link (as such, include it in link form this time, e.g.  ).
 * : The size of the map (e.g. ).
 * : The class of the image: it can be omitted entirely, or filled in with   or a variable,.
 * Omit the class (or use a class of ) for maps used only in infoboxes.
 * Use  or maps only used outside of infoboxes.
 * Use  for maps used in both infoboxes and body text.
 * : The alignment of the map: it can be omitted to let the map default to a right alignment, or filled in with  (or possibly , but this is not encouraged) or a variable:.
 * Omit the alignment (or use a  alignment) for maps only used outside of infoboxes.
 * Use  for maps used only in infoboxes.
 * Use  for maps used in both infoboxes and body text.
 * Specify all the  for each  . The number of lines depends on the number of links in the map.
 * Note: If desired, additional variables may be specified (e.g. replace [size] with to allow an image with a default size of 300px to be enlarged or shrunk on specific pages), and the alignment variable can be used on templates other than those used in both infoboxes and templates.

Basic usage

 * Substitute " " with the name of the template (not including the template prefix).
 * If the template is both included in infoboxes on some pages and embedded in the body text on others, it will have variables associated with it:
 * : The class of the map: type  when the Image Maps is being used in the body text of an article, and type   if it is being used in an infobox.
 * : The alignment of the map: type  (or occasionally  ) when the Image Maps is being used in the body text of an article, and type   if it is being used in an infobox.
 * Note that both variables can be omitted when the Image Map is embedded in the body text, as it being a right-aligned thumbnail should be the default variables.
 * If a template has additional variables encoded, such as for size, this can also be included using  (e.g.  ).
 * An example of an Image Map (Template:NSMBUmap) embedded in the body text of an article (including a size variable in addition to the regular two needed for maps that go in infoboxes and body text) is as follows:

Categories redux
There are a lot of pages on the Super Mario Wiki, and the most fundamental way of organizing them all is with categories. These appear as links in a box at the bottom of a page and can be created by typing, which should go at the bottom of a page, after all the text, tables and any navigation templates that are used on the article. Most pages have multiple categories, which are entered one after another, with line breaks between them to make it easy to tell them all apart.

Overview
While a game has one template that is put on every in-game subject's page, with the characters, items, places, enemies, etc. being separated into different sections within the template, different categories for each subject can be used for the different sets of pages. In other words, subject pages should get the most specific category possible, taking both the game and subject type into account. For example, a character in Super Paper Mario would get Cat:SPM Characters while a place would get Cat:SPM Places (and both pages would get the same navigation template).

All these game/subject-specific categories are grouped together in a category for the overall game (i.e. "Cat:SPM Characters" is part of Cat:SPM), which also houses any pages that don't fit into a more specific category, such as the game's gallery, staff, media, glitch, beta or quotes pages. Subjects with four or less entries should also go into the overall game category, rather than getting a specific subcategory, in order to streamline navigation. Which subjects do not qualify for categories differs from game to game - i.e. if one game only has four minigames, they would simply go in the game's category, whereas a different game with many minigames would have a minigames category, and other games may have no minigames at all. While most games should have subcategories for fundamental subjects like characters, enemies and items, obscure, data-deficient games (such as Japan-only releases like Super Mario Fushigi no Korokoro Party 2), and games with very small scopes or niche spin-offs (like Mario's Cement Factory or Pinball) may not even have game categories, much less subcategories, although the goal is always to improve coverage of such titles.

Game-specific categories are grouped into series-wide categories. For example, "Cat:SPM Characters" is part of Cat:Paper Mario Series Characters, and both that category and "Cat:SPM" are subcategories of Cat:PM Series. The series-wide categories are then grouped into the "big 4" series categories (Mario, Yoshi, Donkey Kong and Wario), such as "Cat:PM Series" being part of Cat:Mario Games. Note that standalone games skip the series step and can be grouped straight into the "big 4" categories (i.e. Cat:Wario World Bosses is a subcategory of Cat:Wario Bosses and Cat:Super Princess Peach is a subcategory of "Cat:Mario Games"). Pairs of games don't get series templates either, and instead use to link directly to the each others' corresponding category; for example, Cat:Mario is Missing! and Cat:Mario's Time Machine link to each other (and are both in "Cat:Mario Games"), while Cat:MiM Images and Cat:MTM Images also link to each other, etc. On the other hand, crossovers between "big 4" series should get both parent series categories (i.e. Mario vs. Donkey Kong pages and articles belong in both "Cat:Mario Games" and Cat:DK Games), while crossovers between one Mario series and a third-party series go in a fifth "crossover" category instead of a "big 4" category (i.e. Cat:SSB Series is filed under Cat:Crossover Games). Remake categories should only exist if there is remake-exclusive content, in which case, the categories should only be placed on that content, while subjects found in both only get the original game's categories, to avoid redundancy and clutter. For example, Rip Van Fish would go in Cat:SMW2:YI Enemies but not Cat:YI:SMA3 Enemies, whereas it would go in Cat:SMA4:SMB3 since it was only in the remake and not the original Super Mario Bros. 3 9and so, would not get the corresponding category). The remake categories should be subcategories if the original, and the text in the categories should also make reference to the corresponding remake/original categories.

Finally, the root of every category tree is a non-series-specific category such as Cat:Characters or Cat:Games, which are in turn placed within Category:Main. These broad subject categories, from the "Big 4" to Cat:Main, should not be used on actual articles, since we already have numerous pages dedicated to listing franchise-wide sets of articles (i.e. List of characters, etc.), and get more use out of nested categories. The exception to this rule are the game articles themselves, which should get every level of category (except Cat:Main): for example, the Super Paper Mario article gets "Cat:SPM", "Cat:PM Series", "Cat:Mario Games" and "Cat:Games". This is because of the centrality of the games to the franchise: while we do have various pages dedicated to listing them (i.e. List of games by date and List of games by console), it is still useful to have alphabetical lists at the overall, "big 4", and specific series levels via the categories. And, unlike subjects, game pages themselves do not accumulate large numbers of categories, so having the various levels does not create clutter as a similar setup would for the subject articles. Other categories trees that do lead to game pages are Cat:Games by date, Cat:Games by genre and Cat:Games by system (meaning SPM will also have Cat:2007 games, Cat:RPGs, and Cat:Wii Games).

All subjects can be organized in this hierarchical method. Many of them have roots that lead back to "Category:Main" like "Cat:Games", "Cat:Characters", Cat:Jobs or Cat:Diseases, although others may branch out of other tree roots, such as Cat:Buildings leading back to Cat:Places (which in turn is part of "Cat:Main"). Some subject-based trees, like "Cat:Characters", are fundamental and applicable to every game, while others will only be applicable to certain games or series. Some, like Cat:Minigames, occur enough in certain games and/or series to warrant some subcategories, while others, like "Cat:Diseases", don't have more than four entries for any game and thus, have no subcategories. Certain games will also have subcategories based on increasingly specific subjects rather than going by games/series, such as "Cat:Buildings" including Cat:Homes that itself includes Cat:Mansions. Just like game/series-based categorization, the articles themselves should only contain the most specific category applicable for specialized subject trees (i.e. Merlee's Mansion would include "Cat:Mansions", but not "Cat:Homes" or "Cat:Places"). These concepts also apply to category trees that do not pertain to games at all, but to other media, such as Cat:TV Shows or Cat:Publications, or to subjects about the development of the Mario franchise - namely, Cat:Real World.

At both the article and category levels, there is overlap between the various category trees, resulting in multiple categories being used for single subjects. This is a given when subjects appear in multiple games, but sometimes a subject will fall into multiple categories for a single game. For example, Goombas are part of both Cat:SMB Enemies and Cat:SMB Species (as well as Cat:SMB3 Enemies, Cat:SMB3 Species; Cat:NSMB Enemies, Cat:NSMB Species; etc.), which might seem redundant, however there are numerous cases where not all species in a game are also enemies (i.e. Toads), and sometimes enemies are individual characters rather than species, and so, the two must be categorized separately. Meanwhile, bosses and allies are usually characters, but occasionally species, and so must also be separate (and bosses must be separate from enemies, as the two perform different gameplay functions). The opposite is done for subject-based categories that do not follow game/series divisions, however, with single categories like Cat:Goombas being used for both species and characters, and so, being part of both "Cat:Characters" and Cat:Species, rather than making separate "Goomba Characters" and "Goomba Species" categories. Instead, the navigation template itself (found on every Goomba article) can be used to differentiate the two types of subject, while the single category is more supplemental than anything else. Similarly, subpages like List of Super Paper Mario quotes only get overall categories like Cat:Quotes, which in turn link straight to Cat:Lists (which is part of "Cat:Main") rather than subdividing it by series, which is left to the templates (i.e. ).

In the characters/species/enemies/allies/bosses complex, the trees should remain separate, however there are other cases where trees often link to each other at the category levels too, such as things like Cat:SPM Items being a subcategory of Cat:SPM Objects despite having its own separate Cat:Items tree, and thus, also being a subcategory of "Cat:SPM" (alongside "Cat:SPM Objects") and Cat:PM Series Items. There is also lots of category-level overlap between subject-based categories and the roots of game/series-based categories, such as things like Cat:Plumbers being part of both "Cat:Characters" and the separate "Cat:Jobs" root, or the aforementioned rooting of "Cat:Goombas" in both "Cat:Characters" and "Cat:Species".

Category Trees
Below is an example of some trees, followed by in-depth explanations about the three types, their levels and the examples. The Primary games tree is in blue, and is only a partial example. The secondary tree is red, and is represented by a single branch plus the other possible paths branching off at each level. Both use Super Paper Mario as their example. A tertiary game-based category using Minigames as its example is included, showing the variability about which levels are visited, even between different branches within one tree. This tree is complete except for some game-specific categories, which are merely alluded to using "..." and yellow, rather than green, connecting lines. Yellow is also used to connect all the trees to the one category they have in common (which will be explained in the following section), since the Lv. 2 Subjects are the true roots of the trees, rather than the Lv. 1 category. A non-game tertiary category is also included in purple, illustrating how the series and game-based levels are not applicable, and the steps that are used are solely based on how many levels of subcategories are needed for a given subject.

The below Minigames tree has examples of both skipped steps and shortened branches, and it also shows how, unlike Secondary subjects, Tertiary subjects are often not applicable to all games (although some, like Levels or Items, are fairly universal, and are Tertiary because intermediate series steps would be of limited value). Like the Secondary subject categories, Tertiary trees skip right down to the Game level for subseries-less titles, like Category:Super Mario RPG Minigames, but they can also skip the subseries level if only one game of a series is applicable, which is why cat:Minigames leads directly to Category:Super Paper Mario Minigames - the other two Paper Mario titles don't have Minigames that need categorization. Similarly, if multiple games in a series have entries, but only one or two games have enough for unique game-specific categories, those games get their categories while the rest go straight into the series category. The above example of this is Category:Super Mario 64 DS Minigames vs. the general Category:Super Mario Series Minigames, which would be used for the Super Mario Galaxy and New Super Mario Bros. minigames. If no games in a subseries have enough entries for specific categories, the branch simply cuts off there and that category is used for all the games. While this isn't found in the above example, it is shown in the Category Webs charts in the next section, which also has examples of step-skipping.



Category Webs
While Category Trees branch out from the most basic categories to the most specific categories, Category Webs are formed when following every specific category applicable to a game back through every level to the basic categories. Webs are basically single branches of many different trees that connect to each other at various levels. Below is an example of a complete category web for Super Paper Mario, as well as a partial web of the same game, to more clearly illustrate cross-categorization.



Koopa Taxonomy
There are many kinds of Koopa: some are like Koopa Troopas, some are like Bowser, some are like Lakitu, some are like Hammer Bros., and if I had my way, Buzzy Beetles and Clubbas would be Koopas too. Are these different species? Are Red Magikoopas and Yellow Magikoopas different species, or do they just wear different clothes? And what are sub-species? Koopatrols? KP Koopas? What's the relationship between Dark Koopas in Paper Mario and Paper Mario: The Thousand-Year Door and Dark Koopas in Super Paper Mario? What is Bowser? And what the heck is a Koopa anyway? Since Nintendo didn't give us any sort of Koopa taxonomy, evolutionary chart, fossil record or family tree, it's totally up to us to answer those questions.

This is not impossible: mother nature didn't share her blueprints either, and yet we still know that spiders and crabs are cousins, and that tapeworms and earthworms aren't. We can't tell if Koopas evolved from turtles or dinosaurs, but we can tell that Bowser is not a Koopa Troopa based on the fact that they look nothing alike, besides their shells and overall skin colour. It's just like how tapeworms and earthworms look nothing alike beyond the fact that they're long and limbless and don't make for pleasant dinner conversations. By analyzing the facts, we can make reasonable deductions, enabling us to organize these enemy pages logically with minimal speculation involved, if we do it right. For example, we can associate Fire Bros. and Boomerang Bros. in because they are nearly identical except for colouration and some physical capabilities (fire or boomerang), just as we can say Ruby-crowned Kinglets and Golden-crowned Kinglets are closely related based on the fact that their body makeup is virtually the same, but their facial feathers and songs are different. But unlike the cute little birdies, we can't speculate on how the Fire and Boomerang Bros. are related: we can't assign them genera or place them in phylogenetic trees, but I think we can say they're different species. True, Nintendo never said they are, but, I mean, one breathes fire and one doesn't: any biologist will tell you that's enough to separate them.

Unfortunately, the "species" vs. "sub-species" debate is where things get really sticky; if you bring race into it too, all the stickier. It's easier just to say they're different "types" of a larger "group" of Koopas which are "related" to one-another, but our nature is to stick "species" in there as well - since it sounds more professional, and more importantly, way more posh. We can justify "species" when there's no doubt to the biology (if it quacks like a duck, it's a duck; if it's pitch black and throws hammers, it's a Dark Hammer Bro.), but when you have really similar enemies, the arguments start to waver. For example, Dark Koopas in Paper Mario: The Thousand-Year Door and Paper Mario just look like Koopa Troopas of a different colour, but they also have unique skills and live in a specific habitat, so are they a sub-species, or a race, or what? In cases like these, to label them is to make an assumption out of uncertainty, which we have to avoid as much we can: no more of this "sub-species" nonsense - therein lies the face of speculation.

Now, the reason for this spiel (aside from my love of taxonomy) is the confusion over "Koopa" vs. "Koopa Troopa", and what to do with their respective articles. As I said before, to the best of my understanding, the "Koopa Troopa" is a specific species (with many similar species and races attached to it, though the actual relationships between the organisms are ambiguous), and "Koopa" is a general term for all the vaguely turtle/dragonish creatures (I'd call it an Order, but that would be speculation to the max). Therefore, I believe it is a very good thing to have separate Koopa and Koopa Troopa pages: one for the species, one for all the shelled enemies. Currently, Koopa is just a partial list of all the major species and some of the minor species, and that should be changed: it should be an annotated list of all the species. Note the "annotated" part: that's what will set the page apart from a mere category or a list in Koopa (disambiguation): it will give context to the Koopas, allowing us to present them in an organized and logical manner, and as long as we watch ourselves, it can be one that is virtually free of speculation. An example of what the Lakitu section could look like is at the end of this essay.

Of course, some level of speculation is unavoidable. Like tapeworms and earthworms, things like Sumo Bro. and Hammer 'Bro. may not be related at all, but if names are good enough reasons to cram everything else on the Wiki together (A Pirate Goomba is a Goomba? Who knew!), why not here too? No matter what we do, we will have to make some assumptions, but none wil be as large and misguided as saying "Koopa" = "Koopa Troopa" = all Koopas and merging the pages. Bowser is not a Koopa Troopa: any biologist could tell you that even if they never played a videogame in their life. Therefore, we can't write about Bowser's species in Koopa Troopa, and if we merge Koopa, we lose the only logical place to put it - we'd have to make a nameless stub about them, which would be against various Super Mario Wiki policies. For this specific reason, and for the organizational benefits I stated above, in the name of taxonomy and in the spirit of organization, I say we leave the pages separate.

Lakitu
Lakitus are bespectacled Koopas who ride clouds through the skies, and which can occasionally be found snorkeling in water and hiding in walls or pipes. Unlike most Koopa species, they do not have snouts or beaks, but flat faces; their shells are also unique in their circular patterning. To attack, Lakitus typically throw unlimited numbers of Spiny Eggs at their opponents, and some will also dangle 1-Up Mushrooms from fishing poles to lure their targets closer.


 * Lakitus
 * Aqua Lakitu - A race of Lakitu that lives underwater with the aid of scuba gear, coming to the surface to breathe and throw Spiny Eggs.
 * Calm Lakitu - Lakitus that inhabit Vibe Island, where they are associated with the Calm Vibe, incarnating the power by sleeping most of the time.
 * Dark Lakitu - Lakitus that are darker in colour with red shells and that throw Sky-Blue Spinies.
 * Fishin' Lakitu - Lakitus that use Fishing Rods baited with a 1-Up Mushroom to lure enemies near their clouds. Once the bait is taken the rod is withdrawn and Spinies are thrown. The Fishing Rod can also be used to hook enemies, support various objects, or to simply fish.
 * Lakipea - The Beanish Lakitus. Lakipea have a leaf-like appendage growing from their head, inhabit vine-covered clouds, and throw the Beanish variation of Spiny, Sharpea.
 * Lakitufo - Red-shelled Lakitus bioengineered by the Shroobs to possess strange extraterrestrial features, including antennae in place of hair. They ride UFOs instead of clouds and beam down Spiny Shroopas in lieu of Spinies. They can also jump off their UFOs and assault their enemies themselves with a screw attack.
 * Pipe Lakitu - Lakitus that hide in Warp Pipes to ambush enemies (still attacking with Spiny Eggs).
 * Roketon - A species of Lakitu that flies in airplanes through the skies of Sarasaland. Instead of throwing Spinies, Roketons fire large amounts of Giras from their aircraft to attack their enemies.
 * Thunder Lakitu - This species of Lakitu has a red shell (like Dark Lakitus) and tanned skin. Instead of throwing Spinies it shoots fire generated by a device in its cloud that harnesses the energy from the sun.
 * Wall Lakitu - Lakitus that hide behind hills and other objects in order to throw Spiny Eggs in surprise-attacks.

Timeline
Every Mario game, show, movie and publication in chronological order (right), and in chronological order sub-divided by series (left). Things without specific dates go before everything else released in that month/year. Non-game titles are bold. Issues in serialized publications and the set-of-three anime are marked with dashes on the right column; usually not included in left column. Remakes and notable ports are in brackets, although most ports/re-releases aren't listed. All that is to help with organization/comprehension. Non-English names often have translations (just for fun), and I also have the NA names in parentheses for the things we use the PAL titles for (because my memory is bad).

For the left column, games (or books, special comic issues (most not included), TV series, movies, etc.) in a series are numbered in most cases. Ports/remakes are in brackets and bulleted under the game they are a remake/port of; compilations are also bracketed, but are numbered like original game (All-Stars within the Super Mario series; Nintendo Puzzle Collection is on its own, as it includes games from multiple series). Similarly, the Super Mario Advance series of games is broken apart, with each game being filed under the original it is porting. In some cases, sequels are merely bulleted under the original (without brackets), rather than a new series being made for the two games. All other important notes are more case-specific, and are included as references (listed at the bottom); the entries with references are denoted with goldenrod text.