Help:Contents/Bug Rules & Guidelines
This is a sub-page of Help:Contents.
|This article is a work in progress.
...Well, all the articles here are, in a way. But this one moreso, and the article may contain incomplete information and editor's notes.
Bug pages are meant to document all the bugs found in a game. A bug is an unexpected fault or failure in the game, sometimes resulting in a crash. Check out the Content to Expand section for ideas on what needs to be covered.
- Games With Bug Pages: These games have existing bug pages for you to add to.
- Bug Content to Expand: This page features a list of information, categorized by game, that has yet to be added to a bug page. Some games listed here don't have bugpages yet.
What information can I add?
Except for the rules about what to add and what to avoid that are specific to Bug pages, TCRF's regular rules and guidelines also apply. Don't forget to read them, too!
Add This Stuff
Glitches in the game.
- Example: Any event or occurrence in a game that is or is highly likely to be caused due to an error in programming.
Artwork errors in the game.
- Example: Any time some sprites have incorrect proportions, coloring errors, or consistency problems.
Sound errors in the game.
- Example: Any time a sound has popping, hiccuping, splicing, or has an outtake attached to it.
Don't Add This Stuff
- If a bug requires another bug to be triggered to "unlock" it, it shouldn't be documented here, as crazy as the results may be. Many popular bugs that rely on an already glitched character or game state to be performed are considered nested bugs (such as Final Fantasy VI's numerous Sketch glitches).
- Example: Landing on an enemy in a specific way causes your character to enter a glitched state (bug); using this glitched state to clip through a wall and enter an invalid area causes the game to freeze (not a bug).
Bugs that cannot be triggered on original, properly-working hardware.
- Example: A lot of NES games freak out if you press Left + Right at the same time. Since a real, properly-functioning NES controller typically doesn't allow this, many programmers simply didn't bother checking for it.
- Exception: If such a bug is fixed in a revision or localization of a game, it can be documented under a Regional Differences or Revisional Differences section of the main article.
Bugs caused by inaccurate emulation.
- Whenever possible, bugs must be confirmed to occur on the original hardware.
- Example: Kirby Super Star will occasionally crash and/or glitch out in interesting ways in ZSNES due to inaccurate SA-1 emulation.
- Official emulated re-releases of a game and the bugs specific to those releases also fall under this rule.
- Example: The Game Boy (Color) emulator used for 3DS Virtual Console releases ignores illegal opcodes and allows the game to continue to run (unlike the real hardware, which will hang when it encounters an illegal opcode), allowing for code that would have never run on a real system to run within the emulator, leading to new bugs.
Bug articles for games that don't have a mainspace article yet.
- Creepypastas or any general fictional glitches are not allowed.
Common errors within games.
- This include stuff like date overflows (particularly for 32-bit machines).
- This should be on the mainspace pages, under the category of unused code.
- TCRF is not a place to advertise your own content. This includes videos and sites not directly related to the material covered here.
Please read the general rules and guidelines about uploading images.
To learn about uploading videos, and formatting videos on a page, see the Video rules and guidelines.
Who owns the information?
Please see the Ownership of Information page.