Glitch: Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
>Torchickens |
>Torchickens No edit summary |
||
Line 17: | Line 17: | ||
There is a degree of controversy of what is a glitch, such as whether intended mechanics that lead to unintended exploits are classed as glitches (such as [[date change exploit]]), or whether accidental exploits (such as [[red bar manipulation]]) are glitches. |
There is a degree of controversy of what is a glitch, such as whether intended mechanics that lead to unintended exploits are classed as glitches (such as [[date change exploit]]), or whether accidental exploits (such as [[red bar manipulation]]) are glitches. |
||
In the Pokémon speedrunning community, [[go past the Marowak ghost without a Silph Scope]] is allowed in glitchless speedruns, despite it not being the developer's intention for the player to skip Marowak without the Silph Scope |
In the Pokémon speedrunning community, [[go past the Marowak ghost without a Silph Scope]] is allowed in standard glitchless speedruns, despite it not being the developer's intention for the player to skip Marowak without the Silph Scope (and became the convention). A later category known as "Any% Glitchless (Classic)" bans using a Poké Doll on the ghost Marowak. |
||
Red bar manipulation is allowed but realistically is impossible to avoid without intentionally trying to avoid getting a Pokémon to low health. [[Bike Shop instant text glitch]] was once allowed as well, but later banned. |
|||
Some differentiate between "bug" and "glitch", for example possibly by identifying a bug as something that was clearly an error in the programming code, i.e. Game Boy ASM etc. ([[programming logic error]]) however the properties of such exploits for distinction between bug and glitch can be vague. Another distinction is of glitch being an error in computer hardware rather than software, however a different definition of glitch was later socially constructed in video gaming communities. |
Some differentiate between "bug" and "glitch", for example possibly by identifying a bug as something that was clearly an error in the programming code, i.e. Game Boy ASM etc. ([[programming logic error]]) however the properties of such exploits for distinction between bug and glitch can be vague. Another distinction is of glitch being an error in computer hardware rather than software, however a different definition of glitch was later socially constructed in video gaming communities. |