Anonymous user
Glitch: Difference between revisions
Rewrote the page completely
old->Bbbbbbbbba (I really just want to change this section that was really cringey, but I guess I am not completely clear on this topic, either. I will return to this page later.) |
(Rewrote the page completely) |
||
Line 3:
{{wikipedia2|Glitch#Video_game_glitches}}
In the context of video gaming, a '''glitch''' is largely synonymous with what would be called a '''bug''' in the context of software in general — an error in the programming of the game that causes it to produce results unintended by the developers of the game. Such unintended results may range from simple graphical weirdness, [[freeze|game freezes]], or sequence breaking, to (specifically in Pokémon games) strange [[glitch Pokémon|Pokémon]], [[glitch move|moves]], or [[glitch item|items]] that should never appear in normal gameplay. Trying to play the game "normally" with such Pokémon, moves, or items may lead to even more unexpected results.
The use of the word "glitch" is standard in the video gaming community. While the word "bug" always carries a negative connotation, many video game players see glitches in a more positive light, as extra contents in the game, and/or tools that could be exploited to achieve something otherwise difficult or impossible, such as speedrun records. Still, some glitches do have (usually) harmful effects like erasing the player's [[save file]], although most glitches are harmless, especially if the player has enough understanding of the glitch in order to avoid the harmful effects.
In addition, the word "glitch" is generally used more broadly and loosely than "bug" would be used. For example, [[#Naturalness|non-natural glitches]] usually do not reflect bugs that need to be fixed (instead, once their parent glitches are fixed, they cease to exist). In a sense, "glitch" reflects weirdness from the player's perspective, whereas "bug" reflects incorrectness from the programmer's perspective.
==As a verb==▼
{{Anchor|Naturalness}}
==As an adjective==▼
When used as an adjective, "glitch" indicates some in-game object that can only be acquired/triggered using a glitch. Examples include [[glitch Pokémon]], [[glitch move]]s, [[glitch item]]s, [[glitch encounter system]]s, etc. Sometimes a glitch object (especially a glitch Pokémon) would be simply referred to as a "glitch"; however, as of now, this usage of the noun "glitch" is discouraged.▼
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 glitch]]es".
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 "normal consequences" of other glitches. For example, depositing a [[glitch Pokémon]] in the Day Care results in a glitch Pokémon in the Day Care, which is definitely an unintended game state, but no one would call that a "non-natural glitch" in and of itself. On the other hand, some behaviors are surprising and unintuitive even considering the fact that the game was already in a glitched state. In the double Blue glitch example, since the player is able to play the game largely normally without the Boulder Badge, they probably would not expect anything out of the ordinary on Route 22, let alone a game freeze. Complicating the matter is the fact that "surprising and unintuitive" depends on the player's understanding of the parent glitch. A player accessing the [[expanded item pack]] for the first time may be surprised that there are so many glitch items, or that manipulating them would affect other aspects of the game, but for an experienced glitch researcher, that's just how the expanded item pack works.
▲==Natural glitches, non-natural glitches, and glitch techniques==
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:
* Use a variant of the [[trainer escape glitch]] to encounter [[MissingNo.]] or [[GlitchDex/RB:000|'M (00)]].
* The [[Glitch Pokédex flag|"seen" Pokédex flag]] of MissingNo. or 'M (00) causes item duplication, resulting in an item stack with quantity larger than 100. Repeat this once to get a x255 item stack.
* Do the [[item stack duplication glitch]] by tossing items above the x255 item stack, which desynchronizes the item count with the terminator of the item list.
* When the item count is 1, decrease the item count to 0 by '''swapping the first two items''' to combine those two stacks. (This is of course impossible if there is actually only one item according to the item list terminator.)
* '''Without quitting the item menu''', decrease the item count to -1 (i.e. 255) by swapping the first two items again. (If the item count was not decreased to 0 by swapping, then the player would not be able to scroll onto the second item at all.)
* The player can now scroll beyond the item list and access the [[expanded item pack]].
If one conglomerate all those steps into a single procedure, then it would seem that that procedure should be a "natural glitch". Of course, it is more intuitive to regard the first two steps as part of the setup, and the last step as the consequence, but trying to identify the roles of the middle steps can feel like splitting hair.
== Exploiting glitches ==
Some glitches give the player an obvious and immediate in-game advantage. For example, after the player performs the [[Pewter Gym skip glitch]], they can immediately proceed to the rest of the game without worrying about beating Brock, and possibly return to beat Brock with Pokémon that could only be caught in later areas. Other glitches may initially seem less useful, such as [[Left-facing shore tile glitch|left-facing shore tiles]] giving wild encounters from a previous area, until the player realizes that it means they can encounter Safari Zone Pokémon and catch them like other wild encounters, or that the relevant memory area can be overwritten by in-game events like [[Old man trick|the old man]].
A complete procedure to exploit a glitch in a useful way is known as a [[glitch technique]], or a "trick". A glitch technique can consist of one or more of the following:
==Controversy==▼
* Doing extra setup in order to make the glitch do exactly what the player wants, like talking to the old man before surfing on left-facing shore tiles.
* For glitches with a persistent effect, performing extra steps to make use of the resulting glitched game state. For example, the [[Celadon looping map trick]] allows the player to get almost any normal or glitch item from an [[expanded item pack]].
* As a special case, doing something extra in the middle of a glitch, like encountering a Pokémon with the correct special stat between the two parts of the [[trainer escape glitch]] (possibly using the [[Ditto trick]]).
* Multiple different glitches chained in a specific way, such as the [[dry underflow]] sequence mentioned above.
Again, it can be difficult, and is usually unnecessary, to distinguish between those cases. However, it can be beneficial to understand what are the essential steps of a glitch, and what are the extra steps a specific glitch technique calls for.
=== In speedruns ===
In speedruns, obviously speed is the main objective, which means that runners would perform any glitch that would save time, even if performing the glitch is arguably more difficult than playing the game normally, and thus it would not be helpful to casual players. In addition, people would design complex glitch procedures that exist for the sole purpose of satisfying the criteria of "beating the game".
Usually, for games with helpful glitches, there will be a "glitchless" speedrun category where it is not allowed to make use of glitches. Conversely, categories where glitches are allowed are called "glitched" categories. There are multiple reasons for a glitchless category:
* Some players may not view beating a game by exploiting glitches as legitimate.
* Other players may not want to learn to perform glitches, but still want to have a category where they can compete.
* In some cases, the optimal glitched route becomes so luck-dependent that it becomes unfun to compete on.
* In many cases, allowing glitches will just change the speedrun completely by skipping over a lot of intended gameplay, making the glitched and glitchless categories equally interesting in different ways.
By convention, categories like "any%" without specification are glitched categories by default (assuming that helpful glitches exist). There may also be categories that only disallow specific kinds of glitches. For Pokémon games, two kinds of glitches that are commonly banned in otherwise glitched runs are [[SRAM glitch|save corruption]] glitches (which can skip over the only bit of intended gameplay at the beginning of glitched runs) and [[arbitrary code execution]] glitches (which can trivialize otherwise interesting goals).
Despite the name, some "glitchless" categories actually still allow certain glitches to happen in the gameplay. One reason is that some glitches, such as the [[Generation I miss]], do not need any special setups and are practically impossible to avoid during normal gameplay. Another reason is that it may be difficult to classify whether the game behavior exploited is actually a glitch (see below).
▲== 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 normal consequence of previous glitches. However, even for natural glitches the line is not that clear.
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.
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 is the [[Bike Shop instant text glitch]] and [[Go past the Marowak ghost without a Silph Scope|using a Poké Doll on the ghost Marowak]]. The instant text itself is an intended mechanic, but it being preserved outside of the Bike Shop is unintended, and gives rise to some unintuitive strategic considerations in speedruns. Skipping wild battles with a Poké Doll is of course intended, but in this specific case it leads to what is arguably a sequence break. Currently in the speedrunning community, both exploits are allowed in the "any% glitchless" category, but there exists another category named "any% glitchless (classic)" where both are not allowed.
▲==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").
▲==As an adjective==
▲
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 didn't realized it had such a glitchy nickname."
==See also==
| |||