Jump to content

Glitch: Difference between revisions

m
→‎Controversy: Grammar fix.
m (→‎Controversy: Grammar fix.)
 
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 isare 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==
Cookies help us deliver our services. By using our services, you agree to our use of cookies.