Glitch: Difference between revisions
m
→Controversy: Grammar fix.
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").) |
m (→Controversy: Grammar fix.) |
||
| (9 intermediate revisions by 2 users not shown) | |||
Line 43:
{{Anchor|Naturalness}}
== Natural glitches and non-natural glitches ==
Some glitches are considered "non-natural glitches" because they can only be performed from an already [[#As an adjective|glitched]] game state. In order to reach such a glitched game state, another glitch would need to be performed first, which would be known as the "parent glitch" of the other glitch. Conversely, glitches that do not require a parent glitch are called "
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
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 88:
Furthermore, it is generally understood that intended mechanics leading to unintended exploits does not count as glitches. Many speedrun strategies are likely not how the developers envisioned the game to be played, such as intentionally going to low HP to shorten sound effects (i.e. [[red bar manipulation]]), or using X Accuracy and X Speed with one-hit KO moves to sweep opposing teams, but they are logically consistent with the intended mechanics of the game, so most people would not consider them glitches. On the other end of the spectrum, something like the [[trainer escape glitch]] also stems from the "intended mechanics" of engaging trainers, but clearly leads to glitchy results. The big ambiguity is where "game mechanics" end and where "gameplay strategies" begin.
Two examples right in the middle of the spectrum
==As a verb==
The verb "to glitch" is usually used either intransitively meaning "to be affected by a glitch" ("my Pokémon glitched out"), or transitively meaning "to perform a glitch with an effect on something" ("I glitched my party").
Empirical glitching refers to the practise of exploiting glitches through observation (as the word empirical is a reference to [[wikipedia:empiricism|empiricism]] and refers to knowledge from the senses). Hard analytical glitching can be understood as the practise of analysing the game at the assembly or source code level. Empirical glitching alone (as well as broad generalisation) can lead to false conclusions when researching glitches (such as the case with sensitive glitches, [[arbitrary code execution]], [[List of revision differences in the core Pokémon games|revision]] or version specific glitches), so it is valuable to practise both.
==As an adjective==
Line 98 ⟶ 100:
There are two other adjective forms of "glitch", "'''glitched'''" and "'''glitchy'''", but their meanings are subtly different.
* "Glitched" describes a game state or an in-game object affected by a glitch. The difference is that while a glitch object (like the '''glitch''' Pokémon [[GlitchDex/RB:000|'M (00)]]) is something that fundamentally should not exist, a '''glitched''' object (like a '''glitched''' Kangaskhan created through evolving said 'M (00)) is just somewhat different from its normal counterpart (a normal Kangaskhan).
* "Glitchy" is sometimes used interchangeably with "glitched", but it puts more focus on the superficial weirdness of said object. "I knew my Pokémon was glitched, but I
==See also==
| |||