Anonymous user
Glitch: Difference between revisions
m
Changed "normal consequence" to "logical consequence" because it sounds more right (I want to use "natural consequence" but that might be confused with the "natural" in "natural glitches").
(Added an analysis of common causes of glitches) |
m (Changed "normal consequence" to "logical consequence" because it sounds more right (I want to use "natural consequence" but that might be confused with the "natural" in "natural glitches").) |
||
Line 47:
Natural glitches are always notable because they indicate logic errors in the underlying game program, i.e., software bugs. On the other hand, non-natural glitches reflect a "[[wikipedia:Garbage in, garbage out|garbage in, garbage out]]" scenario that is not necessarily due to any underlying errors in that part of the program. For example, the [[double Blue glitch]] happens because the programmer assumed that the player must earn the Boulder Badge before earning the Earth Badge. This is a very reasonable assumption: The player [[Pewter Gym skip glitch|escaping from Pewter City]] without beating Brock is not supposed to happen, and if it does, then the programmer has [[Brock Through Walls|bigger things]] to worry about.
The concept of "non-natural glitches" is not always clear. It could be argued that, the behaviors under a glitched game state are all undefined, with none more "unintended" than the others. As such, it can be difficult to differentiate a non-natural glitches from "
Another difficulty in separating natural and non-natural glitches is that glitch procedures usually consist of many steps, and it can be hard to separate the "setup", the "actual glitch", and the "consequences". For example, performing what is known as the "[[dry underflow glitch]]" usually involves the following many steps:
Line 82:
== Controversy ==
It can be sometimes controversial whether a given game behavior should be regarded as a glitch. As mentioned above, many behaviors under a glitched game state can be viewed either as a non-natural glitch, or as a
By definition, a glitch produces results unintended by the developers, but it could be difficult to infer developer intentions. For example, the [[Focus Energy glitch]] is usually thought of a glitch that causes Focus Energy to lower the critical hit rate from normal. However, another theory is that the an error in the program causes the critical hit rate after Focus Energy to be ''swapped with'' the normal critical hit rate, which would mean that the "normal" critical hit rate is in fact glitched to be higher than intended. There is not enough evidence to tell which one the "intended" normal critical hit rate is.
|