Fallout Wiki

READ MORE

Fallout Wiki
Advertisement
Fallout Wiki
This page contains Nukapedia's editing guideline. It describes in which style articles on the Fallout wiki should be written and how the various formatting options should be applied. For more help, please visit the Vault Academy or Nukapedia Survival Guide.
Policyintro.png
  • Guidelines describe desired etiquette and common practice in the creation, editing and organization of articles on this wiki.
  • Any registered editor is free to edit this page to improve its readability as long as the essence of the article remains unchanged.
  • If you would like to suggest content changes or propose a new policy or guideline, please use the wiki discussion forum.
  • See the policies and guidelines page for an overview of this wiki's policies and guidelines.

General

  • The Fallout wiki uses American English and follows the Wikipedia Manual of Style. Where there is a conflict between the manual of style and Nukapedia formatting policies, local guidelines supersede those of Wikipedia.
  • Content should be written in an encyclopedic tone. Descriptions should be clear and precise, and speculations or uncertain facts are not allowed.
  • Do not be overly specific when writing.
  • Editors should use full sentences.
  • Colloquialisms, slang, and other informal styles are not acceptable.
  • Game-specific words should mirror in-game spelling, even in cases when it is incorrect. Capitalization considerations are listed in the section below.
  • Content should be written in the present tense except when relating to events that took place before the first chronological Fallout title, which can be referred to in the past tense.
  • Articles should not be created based on out of game mentions only, such as those from design documents or game guides. Content must have direct mention or appearance in game to warrant an independent article.
  • Wikipedia links not allowed outside of the behind the scenes section of gameplay articles. This does not apply to meta articles, such as voice actors.
  • Fallout Wiki has a custom CSS class for tables called by the "va-table" variable. It should be used for all visible tables in articles.
  • Do not overlink. A page should be linked from a given article only once, on its first occurrence. Links may be repeated if the first link is far up the page or if the manner the word is used in makes it necessary, such as in lists.

Correct instead of remove

Per Edit summary clarity vote - 10/07/2021

Fix problems if possible, but preserve appropriate content and information. As long as the underlying information, if not the manner in which it has been added, is solid, it should be retained and corrected rather than being outright removed. Consider rewriting the edit to improve the quality or cleaning up formatting to meet Nukapedia standards. If the error cannot be corrected when found, rather than lose valuable information, flag the section for correction, so that it can be attended to and neither the information nor the incorrect formatting go unaddressed.

Instead of removing content from an article:

  • Rephrasing or correcting grammar to improve.
  • Fixing errors formatting or style.
  • Merging or moving the content to a more relevant existing article, should it not already be represented, or splitting the content to an entirely new article.
  • Doing a quick search for sources and add the citation.
  • Requesting a citation by adding the {{citation needed}} tag.
  • Adding appropriate cleanup tags where necessary, if unable to correct the error when it is discovered.
  • Correcting any accompanying inaccuracies, while keeping the rest of the content intact.

If unsure about the content of the information, it may also be necessary to make mention of the any concerns or rationales behind tags in the edit summary or article talk page, so that it is clear what specifically needs to be sourced or what other issues should be addressed in order to improve the page. Vandalism should be removed at face value.

Format

  • Bold the article name the first time it appears in the article itself. Any alternative names should also be bolded at their first occurrence.
  • Italics should be used for the titles of books and games.
  • Do not use all caps.
  • Do not use quotation marks, italics, or bold for emphasis.

Article names

  • For characters, titles and ranks should not be included in the article title unless any part of their name is not known. For example, if a character is referred to as "Paladin Rahmani" in-game, the article should be named "Rahmani". Full names are preferred, if possible, so "Leila Rahmani" would be more appropriate than "Rahmani". However, "Paladin Rahmani" should be a redirect to "Leila Rahmani".
  • If the article is for a subject that primarily uses an acronym in-game, the acronym (without intermittent periods) should be used for the primary URL. For example, as it is primarily referred to as "V.A.T.S." in-game, the article should be named "VATS". Both "Vault-Tec Assisted Targeting System" and "V.A.T.S." should redirect to "VATS"
  • Single subject articles should be singular ("Mutant", not "Mutants")
  • Category names should be plural ("Category:Fallout 3 items")
  • Overview articles should be named "<full game name> <subject in plural>" ("Fallout 2 organizations")

Merging and splitting

  • Every article should be "strong" enough to stand on its own. This means the subject provides enough content to write an article of decent length about it. Information should be presented in a way that allows readers to easily find what they are looking for.
  • This means that when creating a new article, it should always be considered whether its subject is too weak to carry an own article and whether it would be more convenient for readers if it were merged with another article. If the answer to these questions are positive, the content should be added to an existing article, or merged if already created. If the subject of an article is broad enough to supply enough content for multiple individual articles or if it would be more convenient for readers, it should be split.
  • It is the responsibility of the editor to correct all links impacted by a merge or split. Utilize the "What Really Links Here" gadget available in the preferences menu.
  • Do not delete empty redirects, as they serve to prevent the creation of duplicate articles.

Overviews

  • If an article subject appears in multiple games, there should be a single article about the subject which serves as an overview.
  • The overview list will contain each game's variant in order of release. Specific gameplay information should be placed in separate articles and not listed on the overview.
  • If several characters, items, perks, etc. can be expressed as a list without any information being lost, then they should be presented as a list instead.

Perspective

Contributions should only use third-person point of view as followed. Elements that are quoted, such as bug notes, quotes, developer commentary, and transcripts, are exempt and use original spelling and perspective.

Term Description Example
Player When referring to game mechanics, customization, or the character system. "The player can have 18 of 19 available mutations simultaneously."
Player character or
protagonist name
When referring to the protagonist, in storyline events, or while describing actions in quests or dialogue selections. "The player character is left for dead in a shallow grave." or
"The Courier is left for dead in a shallow grave."

Disambiguation

  • If a given term can refer to multiple articles (if it is "ambiguous"), the articles should be moved to non-ambiguous (or "disambiguated") titles. A disambiguation page, a page which links to all possible articles this term may refer to, should then be placed at the ambiguous title.
  • In absence of other possibilities to disambiguate the titles (like a surname for a common first name), a term in brackets should be appended to the end.
  • If a term is disambiguated by game and an article refers to multiple games, a disambiguation page should be created with the term without parenthesis.
  • The minimum number of articles required to create a disambiguation page is two (2).
Examples
    • Priority 1: Type of subject ("Example (character)" or "Example (item)")
    • Priority 2: Title of the game in which the subject appears ("Example (Fallout 2)")
    • Priority 3: Location ("Example (Shady Sands)")
    • Priority 4: Any differentiating characteristic between the subjects

Capitalization

Article page names and links should not be overcapitalized, regardless of whether they relate to in-game subjects or not. If it's not clear whether a name is a proper name or a common one, naming should be discussed and decided on a case-by-case basis.

Examples
  • Incorrect: Fallout 2 is part of the Fallout Series of games.
    Incorrect: The Fallout World exists in an alternate timeline.
    Correct: Fallout 2 is part of the Fallout series of games.
    Correct: The Fallout world exists in an alternate timeline.
  • Proper names, such as Pancor Jackhammer, Ranger Sequoia, or Stealth Boy should be capitalized. But common words or descriptive names, like combat shotgun, hunting revolver, or stimpak should not. This also includes names where part of the names constitutes a proper name, like Gannon family Tesla armor.
    Incorrect: A Stimpak is a type of hand-held medication used for healing the body.
    Incorrect: The Gannon Family Tesla Armor is a piece of armor in Fallout: New Vegas.
    Correct: The RobCo Stealth Boy 3001 is a personal stealth device worn on one's wrist.
    Correct: The Gannon family Tesla armor is a piece of armor in Fallout: New Vegas.
  • Generic character names should not be capitalized, unless it can be misinterpreted and its meaning unclear, like Gunner (a member of a specific mercenary faction) and gunner (might be a gunman or something else).
    Incorrect: A Raider killed a Super Mutant with an Assault Rifle.
    Incorrect: A team of gunners was spotted near that area.
    Correct: A raider killed a super mutant with an assault rifle.
    Correct: A team of Gunners was spotted near that area.
  • Species names should not be capitalized. In the same way as cat or dog would not be capitalized, deathclaw and ghoul are also not capitalized.
    Incorrect: The Deathclaws were originally created before the Great War.
    Incorrect: As with normal Ghouls, Feral Ghouls are extremely resistant to radiation.
    Correct: The deathclaws were originally created before the Great War.
    Correct: As with normal ghouls, feral ghouls are extremely resistant to radiation.
  • Names of statistics, perks, traits, skills etc. (e.g. Charisma, Medicine, Fast Shot) should be capitalized when referring specifically to game mechanics. The same words, however, should not be capitalized in other uses.
    Incorrect: Joe is an Intelligent or Charismatic character.
    Correct: The Lone Wanderer will need high Intelligence or Charisma to convince Joe.

Categorization

  • All content pages should belong to at least one category which is not a maintenance category. Maintenance categories are all subcategories of Category:Attention required. Disambiguation pages and redirects are not considered articles in the sense of this rule.
  • A content page should be placed in all the categories to which it belongs.
  • A content page should be placed in only the most specific category (or categories) out of a given branch of the category tree.
  • An article should always be categorized by characteristics of the topic, not characteristics of the article. A character article that contains descriptions of bugs, for example, does not belong in Category:Bugs.
  • An article should never be left with a non-existent (red link) category on it. Either the category should be created by clicking on the red link, or else the link should be removed or changed to a category that does exist.
  • User pages should not be placed in content categories. They may be placed in certain categories that explicitly allow doing so, otherwise, they should remain uncategorized.
Examples
Is category A (more) specific version than category B? If that is the case, the page should only be in category A. For example:
A weapon that appears in Fallout 2 should be in Category:Fallout 2 weapons but not in Category:Weapons (because "Fallout 2 weapons" is a specific version of "Weapons".
A weapon which appears in Operation: Anchorage should not be in Category:Weapons or Category:Fallout 3 weapons, but only in Category:Operation: Anchorage weapons because the latter is the most specific category.
A weapon which appears in both Fallout and Fallout 2 should be in both Category:Fallout weapons and Category:Fallout 2 weapons because "Fallout weapons" is not a more specific version of "Fallout 2 weapons").

See also

Advertisement