FANDOM


This page contains editing rules and guidelines as well as a how-to guide for new users.

General GuidelinesEdit

Adhere to the formatEdit

  • In short, this means to use the same style as found on other pages for layouts, how information is organized, etc.
    • The easiest way to do this is simply to edit an existing page and copy what you see there.
    • Make sure to utilize proper grammar and spelling.
    • Names used here for units, characters and such may differ from those used elsewhere, even the official ones in some cases.
  • Do not change the format used on any pages without consulting an admin. For example, do not begin using a new layout for tables unless you have been approved to do so.
  • If there's no precedent for a type of page in place, you should consult an admin before creating it. It would be a shame if your work were to go to waste because it needed to be changed; facilitating beforehand minimizes the risk of this happening.
  • Avoid using phrasing in articles that will/may become false over time. For example:
    • "X is the latest G Generation game."
    • "X has the most units in any G Generation."

Irrelevant contentEdit

  • Any type of information that's not currently added to pages is probably considered irrelevant information. Some examples include:
    • Unit biographies/summaries: This is not a Gundam encyclopedia, it's a wiki for the G Generation series. As such, only information that actually pertains to the G Generation games belongs here. Users can read about Gundam lore elsewhere.
      • Translated biographies from the games themselves are the exception, but as this is a massive project that will require an immense amount of time and commitment it's not recommended that anybody focus on it for now.
    • Selling prices of units: these can be derived just by looking at the buy cost.
  • Don't plaster unnecessary notes and explanations all over a page. These are fairly rudimentary games and users really don't need every little thing spelled out for them when they can just put two and two together most of the time.
    • An example of a good, warranted note would be if a bug in the game or similar caused the actual information, such as a unit's required amount of EXP to level up or the power of one of its weapons, differed from what is actually listed.
    • An example of a bad, unnecessary note would be explaining that the Zaku II is called "Zaku II F Type" when the developers choose to include the Zaku II J Type in the game. This is something obvious that readers can figure out themselves just by looking at the unit's appearances table or by playing the games.

Do not guess at information or add information that you can't confirmEdit

  • If you're not sure about what you're adding, either confirm it personally, ask somebody else to, or don't add it at all. We'll live without it.
    • An example of this is adding information from other wikis rather than directly from the games themselves. This is hugely frowned upon; to put it simply, there is incorrect information on them--yes, even the Japanese ones--and if you were to add that information to here, there is a possibility that it would slip by undetected and never be corrected.
  • Similarly, when handling Japanese text, if you don't understand it then just leave it to somebody who can. Just because you can copy and paste Japanese text or use a machine translator does not qualify you to work with Japanese text and translations.

Guidelines for Editing Unit PagesEdit

Page TitleEdit

  • This should be named identically to the unit's name on the unit list pages.
  • It should not contain any sort of categorization elements such as a 'MS:' or 'Unit:' prefix; this is what categories are for.
  • The name used for content here is, most of the time, identical to what it's referred to as in the latest G Generation game, as names for some units tend to change from game to game.
  • There are rare instances where the name may need to be changed because of two identically-named things, character restrictions in page titles, or otherwise.

InfoboxEdit

This is the box in the upper-right corner of a page containing the unit's image.

  • If an image has been uploaded for the unit, this is the first thing that you should add to a page.
  • If there is no image of the unit available, do not create an infobox. It is not set up to handle units with missing images.

To create an infobox, type in the following:

{{Infobox
 | eng-name    = 
 | designation = 
 | profile1    = 
 | tile1       = 
}}

Parameters:

  • eng-name: This is the unit's English name and should be identical to the one name the unit is known by everywhere else on the wiki. The Gundam's, for example, would be "Gundam".
  • designation: The unit's model number, such as "RX-78-2". These can generally be found within the game's gallery. If the unit doesn't have a model number, or if the designation is not an actual model number, leave it blank.
    • Model numbers found within the actual G Generation games are given priority over model numbers used extrinsically to the series.
      • For example, because the Guncannon is referred to as "RX-77" in G Generation World, then as of G Generation World, the model number "RX-77" is given priority over its alternate model number "RX-77-2".
    • Do not list more than one model number except for units legitimately listed that way within the games.
  • profile1: This is the name of the unit's profile image. For most units, just type the same name as in 'eng-name', being sure to remove all spaces, followed by "_Profile.png".
  • tile1: This is the small icon of the unit which appears in the upper-left corner of the unit's image in the infobox. For all intents and purposes, you can just type the same thing as in 'profile1', except ending instead in "_Tile.png".

An example of a completed infobox for the unit 'Gundam' would look like this:

{{Infobox
 | eng-name    = Gundam
 | designation = RX-78-2
 | profile1    = Gundam_Profile.png
 | tile1       = Gundam_Tile.png
}}

Infoboxes for Multi-Form UnitsEdit

If a unit has a transformation or otherwise some type of alternate form, the infobox is set up to account for that.

  • What constitutes a multi-form unit?
    • Transformations, different "modes" (God Gundam's Hyper Mode, Unicorn Gundam's NT-D Mode, etc.) and such qualify as an alternate form.
    • Hardpoint System forms (Aile Strike, etc.) and commander type/custom units do NOT qualify as alternate forms and are separate units that get their own pages.

An infobox for a multi-form unit may look like this:

{{Infobox
 | eng-name    = 
 | designation = 
 | name1       = 
 | profile1    = 
 | tile1       = 
 | name2       = 
 | profile2    = 
 | tile2       = 
}}

Parameters:

  • The 'eng-name', 'designation', 'profile1', and 'tile1' parameters function identically as before.
  • name1: This is the text that will appear in the first tab above the unit's profile image. It's the name of its 'base' form, which, most of the time, will be found in the game's gallery in parenthesis after the unit's name. For most units, this will just be "MS".
  • name2: This is the name of the unit's second form; its transformation, in most cases. As before, this can be found in the gallery. The Zeta Gundam's, for example, would be "Wave Rider".
  • profile2: This works the same way as 'profile1' and will appear when you click the tab for the second form. Just type in the image of the other form's name in the same format as the name of the first form.
  • tile2: Similarly, this is the icon for the second form.

An example of a completed infobox for a multi-form unit such as the unit 'Methuss' would look like this:

{{Infobox
 | eng-name    = Methuss
 | designation = MSA-005
 | name1       = MS
 | profile1    = Methuss_Profile.png
 | tile1       = Methuss_Tile.png
 | name2       = MA
 | profile2    = MethussMA_Profile.png
 | tile2       = MethussMA_Tile.png
}}

If the unit has more than two forms, just add more parameters (name3, profile3, etc.) as necessary.

InformationEdit

The information section is similar to the infobox but provides some slightly different information. To use the information template, type this:

{{Information
 | model    = 
 | eng-name = 
 | jpn-name = 
 | series   = 
}}

Parameters:

  • model: The unit's model number, such as "RX-78-2". These can generally be found within the game's gallery. If the unit doesn't have a model number, or if the designation is not an actual model number, use "Unknown".
    • Unlike in the infobox, it's ok to list more than one model number here; just list the "main" model number first.
  • eng-name: The unit's name in English. This should be identical to the page title.
  • jpn-name: What the unit is known as in Japanese.
    • There are times when a Japanese name can be written in more than one way, and it's ok to list more than one in that case.
  • series: The series from which the unit originates or is generally associated with.
    • You can add a 'series2' parameter for units which are generally associated with more than one series, but don't go overboard with it. This is for rare instances, not listing every single appearance a unit has made.

An example of a completed information table for the unit 'Gundam' would look like this:

{{Information
 | model    = RX-78-2
 | eng-name = Gundam
 | jpn-name = ガンダム
 | series   = Mobile Suit Gundam
}}

AppearancesEdit

This table lists all of a unit's appearances within the G Generation series as well as what it was known as in Japanese and an English translation of that name.

  • Do not fill in a unit's game appearance until you add the stats from that game. This helps confirm that the correct name is being used and also makes it easier to keep track of which information still needs to be added to the wiki.

To use the appearances template, type this:

{{Appearances
 | G = 
 | G-e = 
 | 0 = 
 | 0-e = 
 | GB = 
 | GB-e = 
 | F = 
 | F-e = 
 | If = 
 | If-e = 
 | GB2 = 
 | GB2-e = 
 | MG = 
 | MG-e = 
 | NEO = 
 | NEO-e = 
 | Advance = 
 | Advance-e = 
 | SEED = 
 | SEED-e = 
 | DS = 
 | DS-e = 
 | Portable = 
 | Portable-e = 
 | CrossDrive = 
 | CrossDrive-e = 
 | Spirits = 
 | Spirits-e = 
 | Wars = 
 | Wars-e = 
 | World = 
 | World-e = 
 | 3D = 
 | 3D-e = 
 | Overworld = 
 | Overworld-e = 
 | Notes = 
}}

Parameters:

  • As you can see, there is a parameter for each game in the series that the unit potentially appeared in. For the first, write the unit's original Japanese name from that game. For the second, write an English translation of that Japanese name.
    • As always, do not attempt to translate text if you don't know what you're doing, and do not use a machine translations.
    • Please delete unused parameters rather than leaving them empty. It helps reduce page clutter and length. If you're only adding an entry for G Generation World, for example, then only use the 'World' and 'World-e' parameters and delete the rest.
  • Notes: This parameter is for listing any necessary notes. Use it sparingly.

An example of a completed appearances table for the unit 'Gundam', if only entries for a handful of games have been completed, would look like this:

{{Appearances
 | SEED = ガンダム
 | SEED-e = Gundam
 | Spirits = ガンダム
 | Spirits-e = Gundam
 | World = ガンダム
 | World-e = Gundam
 | Overworld = ガンダム
 | Overworld-e = Gundam
}}

Unit StatsEdit

This section lists a unit's primary stats.

  • Which stat template should you use? Templates are made for the first game to which they apply, and subsequent games that share the same format will continue to use that template.

A list of games and matching templates will be added here when they're ready, but the short answer for now is, you're probably playing one of the recent games, so just use UnitStatsSpirits (found below).

'''Stats:'''
{{UnitStatsSpirits
 | cost = 
 | exp  = 
 | size = 
 | hp   = 
 | en   = 
 | atk  = 
 | def  = 
 | mob  = 
 | mov  = 
 | space      = 
 | air        = 
 | ground     = 
 | water      = 
 | underwater = 
}}

Parameters:

  • cost: How much a unit costs; check the shop to find out. Use '-' for units where this is not applicable, such as leader units.
  • exp: How much EXP a unit requires to level up at level 1.
  • The rest of the parameters are self-explanatory, however take into account that listed values should not take into account boosts from abilities and such. If, for example, a unit's mobility is being boosted from 20 to 25 by an ability--let's just say "Magnet Coating"--then the value you should list is 20, not 25.

An example of a completed stats template for the unit 'Gundam' in G Generation World would look like this:

'''Stats:'''
{{UnitStatsSpirits
 | cost = 19100
 | exp = 430
 | size = M
 | hp = 12000
 | en = 100
 | atk = 22
 | def = 22
 | mob = 21
 | mov = 6
 | space = B
 | air = -
 | ground = B
 | water = -
 | underwater = B
}}

Unit Stats for Multi-Form UnitsEdit

When you need to input stats for a unit with multiple forms, use this template:

{{UnitStatsSpirits
 | unit = 
 | cost = 
 | exp  = 
 | size = 
 | hp   = 
 | en   = 
 | atk  = 
 | def  =
 | mob  = 
 | mov  = 
 | space      = 
 | air        = 
 | ground     = 
 | water      = 
 | underwater = 
 | unit2 = 
 | hp2   = 
 | en2   = 
 | atk2  = 
 | def2  = 
 | mob2  = 
 | mov2  = 
 | space2      = 
 | air2        = 
 | ground2     = 
 | water2      = 
 | underwater2 = 
}}

Parameters:

  • The parameters are mostly identical to a normal unit, though there are a second set for the stats of the unit's other form.
  • unit: Similarly to the infobox, we must distinguish between a unit's two forms. This parameter is for the name of the base unit. As an example, for the unit 'ReZEL', it would be "ReZEL".
  • unit2: This is the name of the unit's alternate form. For the unit 'ReZEL', this would be "ReZEL (MA)".

An example of a completed stats template for a multi-form unit such as the unit 'ReZEL' would look like this:

{{UnitStatsSpirits
 | unit       = ReZEL
 | cost       = 27300
 | exp        = 475
 | size       = L
 | hp         = 13600
 | en         = 112
 | atk        = 27
 | def        = 24
 | mob        = 25
 | mov        = 6
 | space      = B
 | air        = -
 | ground     = B
 | water      = -
 | underwater = C
 | unit2       = ReZEL (MA)
 | hp2         = 13600
 | en2         = 112
 | atk2        = 27
 | def2        = 24
 | mob2        = 27
 | mov2        = 8
 | space2      = A
 | air2        = B
 | ground2     = -
 | water2      = -
 | underwater2 = -
}}

Unit AttacksEdit

This section lists a unit's weapons and the related stats. First, type this:

'''Attacks:'''
{{WeaponsWars/Header}}

Then, add this right under it:

{{WeaponsWars
 | name     = 
 | power    = 
 | en       = 
 | mp       = 
 | range    = 
 | type     = 
 | accuracy = 
 | critical = 
}}

Add one of the above for each weapon that a unit has. In other words, if the unit has four weapons, paste that four times. Finally, finish by adding this:

{{TableClose}}

Parameters:

  • name: This is a translated name of the weapon.
  • power: The weapon power.
  • en: EN consumption of the weapon.
  • mp: MP consumption, if any, of the weapon.
  • range: The weapon's range.
  • type: A translation of the weapon's type. Be sure to use the same translation as found elsewhere for weapons of the same type. (A consolidated list will be added later, but for now just check pages of units with the same types of weapons to see what was used.)
  • accuracy: The weapon's accuracy.
  • critical: And finally, the weapon's critical rate.

As said above, you need one 'WeaponsWars' template for each weapon a unit has. A completed attack table for the unit 'Jegan D Type' in G Generation World would look like this:

'''Attacks:'''
{{WeaponsWars/Header}}
{{WeaponsWars
 | name     = Beam Saber
 | power    = 3700
 | en       = 12
 | mp       = 0
 | accuracy = 100
 | critical = 5
 | range    = 1~1
 | type     = Beam Melee
}}
{{WeaponsWars
 | name     = Vulcan Pod
 | power    = 1000
 | en       = 6
 | mp       = 0
 | accuracy = 105
 | critical = 25
 | range    = 1~2
 | type     = Rapid-Fire
}}
{{WeaponsWars
 | name     = Beam Rifle
 | power    = 2700
 | en       = 12
 | mp       = 0
 | accuracy = 85
 | critical = 10
 | range    = 2~4
 | type     = Beam Shooting
}}
{{WeaponsWars
 | name     = Hand Grenade
 | power    = 3000
 | en       = 18
 | mp       = 0
 | accuracy = 70
 | critical = 9
 | range    = 2~4
 | type     = Shooting
}}
{{TableClose}}

Unit Attacks for Multi-Form UnitsEdit

Units with multiple forms require that you distinguish between which belong to which form. Attack tables for multi-form units are similar to normal units. First, type this:

{{WeaponsWars/Header
 | unit = 
}}

Parameters:

  • unit: This is the unit's name. This should be identical to the 'unit' parameter that you used in the stat template. Only use this if the unit has multiple forms.

Next, as with normal units, add this for each weapon the unit has, but only for those of the first form.

{{WeaponsWars
 | name     = 
 | power    = 
 | en       = 
 | mp       = 
 | accuracy = 
 | critical = 
 | range    = 
 | type     = 
}}

Then, you'll add this:

{{WeaponsWars/Header
 | unit2 = 
}}

Parameters:

  • unit2: Just like before, add the name of the unit's second form.

Then, as always, add one of these for each weapon that the unit's second form has:

{{WeaponsWars
 | name     = 
 | power    = 
 | en       = 
 | mp       = 
 | accuracy = 
 | critical = 
 | range    = 
 | type     = 
}}

And finally, add this:

{{TableClose}}

A completed attack table for a unit with multiple forms, such as the unit 'Delta Plus', would look like this:

'''Attacks:'''
{{WeaponsWars/Header
 | unit = Delta Plus
}}
{{WeaponsWars
 | name     = Beam Saber
 | power    = 3900
 | en       = 14
 | mp       = 0
 | accuracy = 100
 | critical = 5
 | range    = 1~1
 | type     = Beam Melee
}}
{{WeaponsWars
 | name     = 60mm Vulcan Guns
 | power    = 1000
 | en       = 6
 | mp       = 0
 | accuracy = 105
 | critical = 25
 | range    = 1~2
 | type     = Rapid-Fire
}}
{{WeaponsWars
 | name     = Beam Rifle
 | power    = 2900
 | en       = 14
 | mp       = 0
 | accuracy = 85
 | critical = 10
 | range    = 2~4
 | type     = Beam Shooting
}}
{{WeaponsWars/Header
 | unit2 = Delta Plus (MA)
}}
{{WeaponsWars
 | name     = Beam Rifle
 | power    = 2900
 | en       = 14
 | mp       = 0
 | accuracy = 85
 | critical = 10
 | range    = 2~4
 | type     = Beam Shooting
}}
{{TableClose}}

Unit AbilitiesEdit

This template lists a unit's abilities. If the unit has any abilities, type this:

'''Abilities:'''
{{UnitAbilitiesWorld|Ability1|Ability2|Ability3}}

Unlike the other templates, you do not need to declare "x = y". All you need to do is replace "Ability1", "Ability2", and so on with the translated name of the unit ability.

  • Make sure that you use the same translation for ability names that is used elsewhere. A consolidated list of abilities will be found on the option parts page, but for now just look at the pages of other units with the same ability as an example and see what was used there.

If the unit has no abilities, simply type this:

'''Abilities:'''
{{UnitAbilitiesWorld}}

A completed ability template for the unit 'Gundam' would look like this:

'''Abilities:'''
{{UnitAbilitiesWorld|Shield Defense Possible|Support Defense Possible}}

Unit Abilities for Multi-Form UnitsEdit

If a unit has multiple forms, chances are that some of its abilities are exclusive to only one of its forms. In this case, this is what you would use:

'''Abilities:'''
{{UnitAbilitiesWorld|Ability1|Ability2|Ability3
 | Comment1 = 
 | Comment2 = 
 | Comment3 = 
}}

Use the CommentX parameters to denote an ability which is not possessed by one or more forms. The easiest way of explaining this one is by example, so let's look at the unit 'Delta Plus' to illustrate:

'''Abilities:'''
{{UnitAbilitiesWorld|Shield Defense Possible|Transformation Possible|Support Defense Possible
 | Comment1 = (MS mode only)
 | Comment3 = (MS mode only)
}}

The Delta Plus has three abilities: Shield Defense Possible, Transformation Possible, and Support Defense Possible. However, when transforming to MA mode, it loses access to its Shield Defense Possible and Support Defense Possible abilities. Because those are abilities one and three, Comment1 and Comment3 are used to denote that those abilities can only be used in MS mode.

Unit DevelopmentEdit

The development template works similarly to the ability template. As with the stats templates, different games use different development templates and a list will be added later, but chances are you're playing a recent game and this is the template you will use:

'''Development:'''
{{DevelopmentPortable|DevelopLevelA|DevelopUnitA|DevelopLevelB|DevelopUnitB|DevelopLevelC|DevelopUnitC|DevelopLevelD|DevelopUnitD}}

As with the ability template, you do not need to declare "x = y", you only need to replace "DevelopUnitX" with the unit that the developing unit develops into, and the preceding "DevelopLevelX" with the level at which the unit develops into it. So, a completed development template of the unit 'Gundam' would look like this:

'''Development:'''
{{DevelopmentPortable|2|Gundam Ground Type|3|G-3 Gundam|4|Gundam GP01|4|Full Armor Gundam}}

Unit CombinationEdit

This is a list of all of the units that the unit can combine with and the result of the combination. Type this:

'''Combination:'''
{{Combination
 | Result1       = 
 | Combination1  = 
}}

Parameters:

  • Result1: The name of the unit that the first combination makes.
  • Combination1: The name of the unit that the unit combines with to make the result.
  • Simply add more parameters as needed.

When making this list, the order you should list it in is alphabetical order by result, and then alphabetical order by combination within that. So, as an example, if our unit has the following (hypothetical) combinations:

  • Gundam + Zaku II = Gelgoog
  • Gundam + Zaku Cannon = Gundam Unit 6
  • Gundam + Guncannon = Gundam Unit 6
  • Gundam + Hyaku Shiki = Delta Gundam

Then this is the order in which you must list them, because first you sort by the alphabetical order of the results, and then if there are any identical results you sort by the alphabetical order of the combination:

  1. Gundam + Hyaku Shiki = Delta Gundam
  2. Gundam + Zaku II = Gelgoog
  3. Gundam + Guncannon = Gundam Unit 6
  4. Gundam + Zaku Cannon = Gundam Unit 6

And how that looks when you actually fill out the template would be like this:

'''Combination:'''
 | Result1      = Delta Gundam
 | Combination1 = Hyaku Shiki
 | Result2      = Gelgoog
 | Combination2 = Zaku II
 | Result3      = Gundam Unit 6
 | Combination3 = Guncannon
 | Result4      = Gundam Unit 6
 | Combination4 = Zaku Cannon
}}

Unit AcquisitionEdit

Unit acquisition is easily the most convoluted thing to fill out here, but it can't be helped. If you aren't comfortable with it or don't feel like doing it until later, just write this:

'''Acquiring:'''
*Unknown

Otherwise, here is what you'll type:

'''Acquiring:'''
{{Acquiring
 | DevelopUnit1      =
 | DevelopCondition1 =
 | Combination1First1  = 
 | Combination1Second1 =
 | Capture1 = 
 | Other1 =
}}

Parameters:

  • DevelopUnit1: This is the unit which develops into the unit that you're filling out the acquiring template for.
    • Like with other templates, you can keep adding more parameters as needed, so 'DevelopUnit2', 'DevelopUnit3', etc.
  • DevelopCondition1: This is the condition by which the unit is acquired.
    • What you type here will depend on which G Generation it is, but chances are it's a recent one, and in that case what you'll be listing is the level which the unit from 'DevelopUnit1' develops into this unit.
      • The order that you should list these is (1) by lowest to highest level, and then (2) by alphabetical order within that.
  • Combination1First1: A unit that combines with some other unit to make this unit.
  • Combination1Second1: The other unit that combines with the unit from 'Combination1First1' to make this unit.
    • You can make more than one of these if there are multiple units for the same combination. So, for example, if Units C, D, and E can all combine with Unit B to make Unit A, then 'Combination1First1' would be Unit B, 'Combination1Second1' would be Unit C, 'Combination1Second2' would be Unit D, and 'Combination1Second3' would be Unit E.
      • As always, list these alphabetically.
  • Capture1: List stages (and be sure to link to them) that the unit can captured on, if any.
    • Do not use Capture2, 3, and so on to list multiple stages. They are for separating stages by category, not listing individual stages.
      • This is more applicable to some games than others. It's difficult to explain, so just ask if you need to fill it out.
  • Other1: For miscellaneous methods of acquisition. Codes, data imports, and so on.

Unit "See Also" SectionEdit

This section is for linking to external sites on which a user may read more about a unit. As GundamOfficial is now defunct, the only sites to be linked to are Gundam Wikia and MAHQ. Do not link to other sites. If you're editing a page which still has a GundamOfficial link then go ahead and remove it.

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.