Bug Verification Project
This article is within the scope of the Bug Verification Project. This project is dedicated to increasing the validity of game bugs. For participation, please check the project page.
Icon info
This is the home page of a Nukapedia project. A project is a collaboration of editors improving articles and other content related to a particular subject. For more information, see Fallout Wiki:Projects.
This project's scope encompasses a subject that does not have a definitive end. Editors are encouraged to contribute as available tasks and time permits.

The Bug Verification Project is a project which aims to organize and regulate the fashion in which bugs are reported and verified. We've all seen our fair share of bugs in each game, but some people see the bugs while others don't. If someone sees and reports a bug, it must be verified in a certain amount of time (say 4 weeks) before it should be deleted from the article. With the way it's done now, some unconfirmed and (quite frankly, ridiculous) bugs are currently sitting on pages without verification (or if they have been verified, do not list the triggers). Bugs should only be added if the trigger is already known since there's no real difference between the Xbox, the PS3, or the PC when it comes to bugs, with the exception of more nasty Havok engine glitches (see Lucky shades) on the PS3. Abiding by such rules will cut down on the raw amount of bugs people encounter while also verifying them (and this will, in turn, clean up quest articles).


All Game Articles (Items, Characters, Quests, Places, Creatures, Robots and computers, etc...)


A set group of contributors will be chosen to go on to a base game with add-ons without Mods to do the following Tasks when a bug is presented.

  • New bugs should be flagged with {{Verify|~~~~~}} at the end of the bug description - this adds a note that it needs verification, and adds a hidden date to the template. When a certain amount of time passes from the date in the template (see docs for the current number), the tag changes to say "Verification overdue" in red.
  • Locate the Trigger of the Bug
  • If trigger is found edit article with said bug and if the bug has not already been labeled with the {{platforms|pc,ps3,xbox360}} template for Fallout 3, New Vegas and Future games then it should be attached, as well as placing {{Verify|verified}} . You should also include a detailed description of the trigger to warn users how to avoid or fix the bug.
    • Not all bugs exist on all platforms; for those that don't exist on every platform, only add the system on which it appears to the {{Platforms}} tag.
      • Example: PCIcon pc The Tesla cannon does not destroy vertibirds in one shot.
      • If you find a bug that lacks the platform tag, place {{pn}} at the end of the bugs description. (This should only apply to games that exist on more than one console, so Fallout, Fallout 2 and Fallout Tactics: Brotherhood of Steel bugs should not have the template placed by them).
      • Bugs that mention console commands as a fix are obviously from the PC even if unmarked, so do not place the platforms needed tag next to them. Instead insert the PC platform tag.
  • If no trigger for said bug can be found within 4 weeks the bug should be removed, DO NOT remove bugs that don't have "Verification overdue" by them.
  • Note that we are also actively seeking out triggers to bugs that may not have been noticed/identified.

Main Game Bug PagesEdit

The main game bug pages should look like Fallout: New Vegas bugs and should exclude the following:

  • Location Specific bugs
  • NPC specific bugs
  • Quest Specific bugs
  • Item specific bugs

Add-on-Specific Bug PagesEdit

Add-on-specific bug pages should resemble Point Lookout bugs and should only include bugs that appear as a result of the DLC, it should not reiterate bugs that appear in the main game. Bugs on these pages should be sorted according to platform.

For more guidelines on what to do about bugs, please see Fallout Wiki:Bug policy.

For articles with bugs that currently need verification please see Category:Verify.


To participate, simply add your name below using {{userlink|your user name}}. Place every participant on a new line, while keeping the alphabetical order.

Platform Verification assignments Edit

The following sections list users who are dedicated to confirming bugs on specific platforms.

PC Edit

PlayStation 3 Edit

PlayStation 4 Edit

Xbox 360 Edit

Xbox One Edit

Progress chartsEdit

Chart format should have the following: Specificity (Quests/Items/Characters/Locations/Factions/Perks/Traits/ Creatures/Robots) articles, Bugs present, Verified, Platform, and Complete across the top. The first column should have the specific type of bug in it, Whether it's Quests, Items, Characters, or Locations. The second column should contain the individual article titles under the specificity. The 3rd - 6th columns should have either {{Yes}} , {{No}} , or N/A depending on the condition of the article.