Fallout Wiki
Register
Fallout Wiki
Tag: sourceedit
(39 intermediate revisions by 18 users not shown)
Line 1: Line 1:
 
{{Games|Wiki}}
 
{{Games|Wiki}}
{{project|active}}
+
{{project|ongoing}}
 
{{Bug Verification Project}}
 
{{Bug Verification Project}}
   
The '''Bug Verification Project''' is a [[Project:Projects|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 see the bugs and others don't and if someone sees a bug, we need to at least get it verified in a certain amount of time say 2-3 weeks before it should be deleted out of 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 someone already knows the trigger; 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. This will cut down on the raw amount of bugs,verify them and clean some of these quest articles.
+
The '''Bug Verification Project''' is a [[Project:Projects|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).
   
 
==Scope==
 
==Scope==
Line 12: Line 12:
 
* New bugs should be flagged with <nowiki>{{Verify|~~~~~}}</nowiki> 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 (two weeks?), the tag changes to say "Verification overdue" in red.
 
* New bugs should be flagged with <nowiki>{{Verify|~~~~~}}</nowiki> 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 (two weeks?), the tag changes to say "Verification overdue" in red.
 
* Locate the Trigger of the Bug
 
* Locate the Trigger of the Bug
* If trigger is found edit article with said bug and if the bug has not already been labled with the <nowiki>{{platforms|Xbox|ps3|pc}}</nowiki> template for Fallout 3, New Vegas and Future games then it should be attached, as well as placing <nowiki> {{Verify|verified}} </nowiki>. You should also include a detailed description of the trigger to warn users how to avoid or fix the bug.
+
* If trigger is found edit article with said bug and if the bug has not already been labeled with the <nowiki>{{platforms|Xbox360|ps3|pc}}</nowiki> template for Fallout 3, New Vegas and Future games then it should be attached, as well as placing <nowiki> {{Verify|verified}} </nowiki>. 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 <nowiki>{{Platforms}}</nowiki> tag.
 
**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 <nowiki>{{Platforms}}</nowiki> tag.
 
*** Example: {{Platforms|PC}} The Tesla cannon does not destroy vertibirds in one shot.
 
*** Example: {{Platforms|PC}} The Tesla cannon does not destroy vertibirds in one shot.
Line 54: Line 54:
 
{{userlink|RAHMtheBOOYAKA}}
 
{{userlink|RAHMtheBOOYAKA}}
 
{{userlink|Buddha392}}
 
{{userlink|Buddha392}}
  +
{{userlink|TheForecaster}}
  +
{{userlink|Doctor Mobius}}
  +
{{userlink|WrightEveryTime}}
  +
{{userlink|noxwyll}}
  +
{{userlink|Cookie613}}
  +
{{userlink|Richie9999}}
  +
{{userlink|SgtGutsy}}
  +
{{userlink|Markd790}}
  +
{{userlink|TheGunslingerReturns...}}
  +
{{userlink|AkinalM}}
  +
{{userlink|Peace'n Hugs}}
  +
{{userlink|Gaberdude}}
   
 
== Platform Verification assignments ==
 
== Platform Verification assignments ==
Line 61: Line 73:
 
{{Platforms|Pc}} {{userlink|-bleep196-}}
 
{{Platforms|Pc}} {{userlink|-bleep196-}}
 
{{userlink|Korney San}}
 
{{userlink|Korney San}}
  +
{{userlink|TheForecaster}}
  +
{{userlink|WrightEveryTime}}
  +
{{userlink|Tocinoman}}
   
 
=== Xbox 360 ===
 
=== Xbox 360 ===
 
{{platforms|Xbox360}}
 
{{platforms|Xbox360}}
  +
{{userlink|Doctor Mobius}}
  +
{{userlink|Markd790}}
  +
{{userlink|AkinalM}}
   
 
=== Playstation 3 ===
 
=== Playstation 3 ===
 
{{platforms|Ps3}} {{userlink|Stars and Stripes Forever}} {{userlink|RAHMtheBOOYAKA}}
 
{{platforms|Ps3}} {{userlink|Stars and Stripes Forever}} {{userlink|RAHMtheBOOYAKA}}
{{userlink|Sgnt Wolfgang First Recon}}
+
{{userlink|Sgnt. Wolfgang First Recon}}
  +
{{userlink|Tribal Wisdom}}
 
  +
{{userlink|Tocinoman}}
==Progress==
 
   
 
==Progress charts==
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 <nowiki> {{Yes}} </nowiki>, <nowiki> {{No}} </nowiki>, or N/A depending on the condition of the article.
+
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 <nowiki> {{Yes}} </nowiki>, <nowiki> {{No}} </nowiki>, or N/A depending on the condition of the article.
   
  +
* [[Fallout_Wiki:Bug Verification Project/Bug chart 1/characters|Bug chart 1/Characters]]
The charts for this project can be found [[User:-bleep196-/sandbox2_Bug_Charts|Here]] and [[User:-bleep196-/Sandbox3_Bug_Charts|Here]] due to the sheer volume of the charts.
 
  +
* [[Fallout_Wiki:Bug Verification Project/Bug chart 2/Locations|Bug chart 2/Locations]]
  +
* [[Fallout_Wiki:Bug_Verification_Project/Bug_chart_3/Quests|Bug chart 3/Quests]]
  +
* [[Fallout_Wiki:Bug_Verification_Project/Bug_chart_4/Items|Bug chart 4/Items]]
  +
* [[Fallout_Wiki:Bug_Verification_Project/Bug_chart_5/Creatures_and_Robots|Bug chart 5/Creatures and Robots]]
  +
* [[Fallout_Wiki:Bug_Verification_Project/Bug_chart_6/_Factions_Radio_Stations_and_Vehicles|Bug chart 6/Factions, Radio Stations, and Vehicles]]
  +
* [[Fallout_Wiki:Bug_Verification_Project/Bug_chart_7/Perks_and_Traits|Bug chart 7/Perks and Traits]]

Revision as of 04:28, 10 April 2015

 
Gametitle-Wiki
Gametitle-Wiki

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).

Scope

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

Guidelines

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 (two weeks?), 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|Xbox360|ps3|pc}} 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: PCPC 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 Pages

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 Pages

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.

Participants

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


Platform Verification assignments

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

PC

PCPC

Xbox 360

Xbox 360Xbox 360

Playstation 3

Playstation 3Playstation 3Playstation 3

Progress charts

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.