About: Fallout Wiki:Bug Verification Project   Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

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

AttributesValues
rdfs:label
  • Fallout Wiki:Bug Verification Project
rdfs:comment
  • 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
dbkwik:fallout/pro...iPageUsesTemplate
abstract
  • 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).
Alternative Linked Data Views: ODE     Raw Data in: CXML | CSV | RDF ( N-Triples N3/Turtle JSON XML ) | OData ( Atom JSON ) | Microdata ( JSON HTML) | JSON-LD    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software