User:Rusty/BugsRules

This page will act as a place to dump WIP rules and guidelines along with related ideas/thoughts for the Bugs: namespace. We need to keep a pretty tight grip on this category, otherwise it will quickly spiral out of control.

If you have any ideas, suggestions, or constructive criticism, feel free to type some words on the Talk page.

• The category should cover both program bugs and design oversights that cause gameplay issues (popular example: unobtainable Rings in Sonic games that prevent players from getting a perfect bonus). I'm not interested in restricting it to only program bugs just because the namespace is called "Bugs:".
  • Should this also include oversights that don't cause issues (or are even noticeable to players), such as enemies trapped in walls?
• No bugs caused by cheat codes or devices. The category should only include bugs that could affect someone playing an unmodified copy.
• No "cascading" bugs. We don't need to document the whole crazy series of events and other "bugs" you can trigger by putting a character in your party that isn't supposed to be there. The initial bug (getting said player in your party) would be acceptable, but the crash that occurs when talking to an NPC with him in your party would not (because the programmers obviously did not expect this situation to occur).
  • Similarly, glitched worlds that can be accessed as a result of going out of bounds or via other means don't need to be thoroughly documented (Metroid's "hidden worlds", for example).
• Should we document program bugs that have no effect on the game? I don't really want a bunch of pages with mostly uninteresting code snippets that ultimately don't do anything.