MUGEN Database
Register
Advertisement

This page's purpose is to show you the basics of creating a stage article; the rest is up to you.

The first part is the name of the article. You have to name the article EXACTLY how the stage itself is named (besides the capital letter at the beginning of a title); this includes bad spelling/grammar unfortunately..."What if the stage hasn't got a name?" Well that's a pretty bad stage then :P

Now onto the article itself.


Infobox

Similar to source character articles, the very first thing that should be on a stage article is the infobox, though the type of infobox used is the one that's exclusively for stage articles, as denoted by the template being named {{Infobox stage}}; the logic behind the stage infobox template is the same as the logic for character templates, the difference lying solely in the parameters that are required for it.

{{Infobox stage
|Name=
|Image=
|Caption=
|Creator=
|Downloadlink=
|Animated=
|Music=
|Super Jump=
|Resolution=}}

General parameter explanations

The following section gives a general explanation as to what the functions are for each infobox parameter, however, it only explains the correct parameter formatting for stage articles where only one version of a stage exists, for the parameter formatting regarding stage articles where more than one version of the stage exists, see the section after this one titled 'Multi-version parameter formatting'.

Name -- The name that will display at the top of the infobox; while this is usually the same as the article's title, some stages have names that differ from the source media name either out of the creator's preference for naming their work or because the stage's name is in a language other than English.
Caption -- A short snippet of text that describes what is happening in the image; the default caption text is '(Character A) fighting (Character B) on (Name of stage)', where Character A is player 1 and Character B is player 2.
Creator -- The name of the stage's creator, remember to link to the creator's article if it exists on the Database. It is important to note that the creator's name should be written exactly how the creator normally writes it, with proper capitalisation and letter/word spacing being taken into account.
Downloadlink -- The external link to the where the stage can be downloaded from, remember that linking to the download location on a creator's website takes priority over a link to any file hosting site that the stage can be downloaded from. As with character version articles, the text for the link that shows up in the infobox should be the name of the website that the stage is hosted on.
|Downloadlink=[https://example.com/ Example Domain]
Avoid using direct download links, if a direct download link is unavoidable (which should very rarely be the case), use a tooltip next to the download link to indicate this.
|Downloadlink=[https://example.com/example.rar Example Domain]{{tt|*|Direct download}}
If the stage's background music comes as a separate download, it needs to be listed as a separate link in the infobox; only list download links to background music provided by the stage's creator, if a stage's only known background music are links to music downloads not provided by the stage's creator, disregard them completely and use 'No' for the Music parameter. Make sure that not only is the second link placed onto the next line so that it looks tidy in the editor, but a break tag (<br>) is also placed next to the first download link so that the second download link is shown below it in the infobox.
|Downloadlink=[https://example.com/ Example Domain]<br>
[https://example.net/ Background music]
Animated -- Either 'Yes' or 'No', depending on whether the stage has features that animate or not.
Music -- Either 'Yes' or 'No', depending on whether the stage comes bundled with music or the stage's creator has a separate download for it. If the parameter is 'Yes', a Background music section needs to be added to the article. As explained above, ignore any music that was not provided by the stage's creator.
Super Jump -- Either 'Yes' or 'No', depending on whether the stage's camera pans upwards enough so that most of a character is still visible after performing a Super Jump or not.
Resolution -- Either 'High' or 'Low', depending on the resolution of the stage.

End result

The following is an example of how a finished infobox appears in the editor and on a article respectively, this one being Rave On's infobox:

{{Infobox stage
|Name=Rave On
|Image=File:Rave_on.PNG
|Caption=Weiss and Heart Aino staring each other down on Rave On
|Creator=[[EXShadow]]
|Downloadlink=[http://www.mediafire.com/download/sv9ahhw22oevv6r/XX%27RAVE%27XX.rar#39;RAVE'XX.rar MediaFire]
|Animated=Yes
|Music=Yes
|Super Jump=Yes
|Resolution=High}}
Rave On
Rave on
Weiss and Heart Aino staring each other down on Rave On

Creator

EXShadow

Download

MediaFire


Multi-version parameter formatting

The following section gives a general explanation as to the formatting of parameters for infoboxes where the article has more than one version of that particular stage, the parameter's functions are identical to those used in single-version stage articles, all of which are listed in the previous section: 'General parameter explanations'.

Name -- Exactly the same as the article name, regardless of what any of the individual stages are named as.
Creator -- Identical to what is required for the single-version infobox, with the only difference being the addition of other creator names. Names should be in order of when the creator created their version of the stage from oldest to newest, with all names being on the same line and having break tags separating them; If the amount of creators for a stage exceeds 3, write 'Various' instead of any creator names.
|Creator=[[Creator 1]]<br>[[Creator 2]]<br>[[Creator 3]]
Downloadlink -- Practically identical to what is required for the single-version infobox, although there are some minor differences concerning how things are named as well as what order the links are listed; instead of the download link's infobox text being the name for the website that the stage is hosted on, it is instead the stage creator's name followed by 'version', this is to prevent confusion over which link belongs to which stage. Download links have a particular ordering to them, as links are listed from the oldest version of the stage to the newest version, similar to how creator names are ordered in the 'creator' parameter; stages with background music that is downloaded separately from the stage are listed right under their respective stage.
When it comes to stages that have been created more than once by the same creator, the infobox text for those links should be formatted as 'Creator's nth version', with 'nth' being replaced by first/second/third etc. depending on the ordering of when the creator released a particular version of that stage. Minor updates to any particular stage version by the stage's creator do not count as an additional version, however, if the updates are as such that the updated stage is significantly different from the original, treat the stage as a new version; stages made by the same creator are not grouped together in the infobox, they still follow the rules of links being listed from oldest to newest, for example:
|Download=[(Downloadlink) Creator 1's first version]<br>
[(Downloadlink) Creator 2's first version]<br>
[(Downloadlink) Creator 1's second version]<br>
[(Downloadlink) Creator 3's version]<br>
[(Downloadlink) Creator 2's second version]<br>
[(Downloadlink) Creator 2's third version]<br>
[(Downloadlink) Creator 1's third version]
Stage edits by different creators are handled similarly to separate background music downloads in the infobox, but are handled differently in regards to download link ordering; it should also be noted that instead of using 'version' to denote an edit, 'edit' should be used and the link text should be formatted as 'Creator's edit' or 'Creators first/second/third edit' if a creator has edited the stage more than once. A stage edit is listed under the link of the stage that it is an edit of and otherwise ignores the traditional listing of stages from oldest to newest, however, multiple edits of the same stage are listed in order of oldest to newest within themselves. If a stage has a separate link for background music, any links for stage edits are listed under this instead of the original stage, similarly, if any of the edits have a separate link for background music, that link is listed directly under the edit that the music belongs to.
|Download=[(Downloadlink) Creator's version]<br>
[(Downloadlink) Background music]<br>
[(Downloadlink) Creator 2's edit]<br>
[(Downloadlink) Background music]<br>
[(Downloadlink) Creator 3's edit]<br>
[(Downloadlink) Background music]<br>
[(Downloadlink) Creator 4's first edit]<br>
[(Downloadlink) Creator 4's second edit]<br>
Animated/Music/Super Jump -- Functions differently depending on whether individual versions of a stage have differing attributes, if all versions of a stage have animated elements, for instance, then this parameter is treated the same as it would be for single version stage articles; if some versions have animated elements while others do not, then both the 'Yes' and 'No' functions have to be placed into the infobox with a tooltip next to each that states which versions correspond to which function. When listing creators in the tooltip, it is only necessary to list the creators name and separating each name with a comma, list the creator names in order of when their stage was created (oldest to newest).
|Animated=Yes{{tt|*|Creator1, Creator3, Creator4}}<br>
No{{tt|*|Creator2, Creator5}}
In the event that two stages by the same creator have different attributes, list the creator's name as usual, but state which version has that particular attribute in brackets.
|Animated=Yes{{tt|*|Creator1 (first version), Creator2 (second version)}}<br>
No{{tt|*|Creator1 (second version), Creator2 (first version)}}
Resolution -- Fundamentally the same as the Animated, Music and Super Jump parameters, but with 'High' and 'Low' instead of 'Yes' and 'No', depending on the resolution of the stages.

Background music

Applies to both single and multi-section stage articles.

For any stage version that comes with background music either bundled with the stage or as a separate downloadable file (and thus has the Music parameter in the infobox filled in as 'Yes'), a section is required for said version that includes the stage's music for people to listen to, similar to a 'try before you buy' setup that informs a user if the music is of good quality/to their tastes, or whether they need to head off to a certain video sharing website to find a higher quality version of that music/a different music that they prefer to have on that stage.

Section header

A level 3 header is used for the background music section, with the word 'background' starting with an uppercase 'B' and 'music' starting with a lowercase 'm', like so:

===<u>'''Background music'''</u>===

Music description

Next up is the piece of text that explains what the name of the music is and which media it originates from; for the sake of standardisation, all of these texts should start with:

The music used is

The music itself

It's clear as crystal that the most important part of the background music section is the actual music itself, however, the correct music to use is the one that either comes bundled with the stage or the one that is part of a separate download, regardless of the music's quality. This process would have been as simple as simply uploading the raw music file to the Database, were it not for the fact that the Database (and Wikia as a whole) only accepts audio files in Ogg Vorbis format (.ogg); fortunately, there is a way around this for files in different formats that won't cost any money, simply download and install Audacity -- an open source program that can cleanly convert files to Ogg Vorbis format (as well as loads of other audio related stuff) and follow these instructions:

  1. Open the raw file in Audacity.
  2. File -> Export... -> change 'Save as type' to 'Ogg Vorbis Files'.
  3. Name the file something relevant, typically in the fashion of (creatorname/creatorinitials)(stagename).ogg.
  4. Upload the Ogg Vorbis version of the file to the Database.

Inserting the music into an article is a relatively simple process, it goes directly under the music description and is done in the same way that an image is inserted into an article, with the file extension obviously being .ogg instead of the extensions used for an image file:

[[File:Audio_filename.ogg]]

An example of a finished product will look like this:

===<u>'''Background music'''</u>===
The music used is the battle theme for Gateway Colosseum from ''Pokémon Battle Revolution''.
[[File:Gateway_Colosseum.ogg]]

Which would translate onto an article as:

Background music

The music used is the battle theme for Gateway Colosseum from Pokémon Battle Revolution.

Videos

Videos are dealt with in the much the same way they are dealt with on character articles, however, seeing as one stage article may end up containing multiple versions of a particular stage [insert policy regarding how we manage videos on stage articles with more than 1 version here].

Although a videos section is a requirement on all stage articles, it is sometimes impossible to actually list at least one video owing to the possibility of a video not existing that contains that particular stage; when this is the case, put the {{Needvid}} template under the section header and remove the gallery tags, this will remind editors that should a video containing this stage be created in the future, it will need documenting in the article.

The finished section will look something akin to:

Videos

Categories

The categories used for stage articles are somewhat different from the ones used for character articles, as the categories combine what would be elements of the ones used on both the source character and character version articles; fortunately, there are less categories required for stage articles than there are for character articles, which makes this task a little bit easier.

The first category that needs listing in the article is the all-important stages master category: Category:Stages, this category is what the Database looks for when a random stage is searched for using the navigation toolbar at the top of the page, as well as what bots look for when making important edits to all stage articles at the same time.

The next categories to list on the article are the genre/company/series categories, these are near identical the the character versions of said categories with the exception of the final word of the category being 'Stages' as opposed to 'Characters'.

The final category that can be listed in the article is the one that states whether the stage is only compatible with a certain M.U.G.E.N version, these categories are mutually exclusive, so only one of these categories is allowed on any particular article. The categories and their specific requirements are as follows:

Category:1.0+ Stages -- Used on articles where all versions of the stage are only compatible with versions of M.U.G.E.N starting with M.U.G.E.N 1.0 and are thus not compatible with older versions of M.U.G.E.N. All stages in this category should work perfectly fine with newer versions of M.U.G.E.N.
Category:1.1 Stages -- Used on articles where all versions of the stage are only compatible with versions of M.U.G.E.N starting with M.U.G.E.N 1.1 and are thus not compatible with M.U.G.E.N 1.0 or other older versions of M.U.G.E.N.

Because of the above, these categories can be ignored if either there are two versions of the stage with conflicting compatibility requirements, or if at least one of the stage versions doesn't have any specific requirements for M.U.G.E.N compatibility, though if any stages do have a specific M.U.G.E.N compatibility, it should be mentioned under that version's respective stage description.

Advertisement