Accuracy

Template:Move
Template:Samename
**Accuracy** (Japanese: **めいちゅう** *accuracy*) is an aspect of moves that, in conjunction with the user's in-battle accuracy stat and the target's evasion stat, determines how reliable they can hit their target. Although the concept was introduced in Generation I, a move's accuracy was not displayed until Generation III.

A move's accuracy can be any number from 1-100, reflecting the probability of the move being successful as a percentage (if neither accuracy nor evasion are modified in-battle). Currently, however, only multiples of 5 between 30 and 100 (inclusive) are used.

Many moves have an accuracy of "—", indicating that they are exempt from regular accuracy calculations. Oftentimes, these moves affect no one but the user (and/or the partner in a Double Battle), or are simply intended to be moves that cannot miss (unless the target has used a move that grants it semi-invulnerability for a turn such as Fly).

## 1/256 miss glitch

In the Generation I handheld games, moves with 100% accuracy have a chance to miss if neither accuracy nor evasion stats are modified, due to accuracy being internally stored as a single byte ranging from 0 to 255, and the probability of a move hitting being determined by comparing a randomly generated byte to the accuracy value, with the move hitting if it was less and missing if it was equal or greater. There is therefore a 1/256 chance of the randomly generated byte being equal to 255, which can never be less than even the highest possible accuracy value, causing moves intended to be 100% accurate to miss 1/256 of the time (yielding an effective accuracy of about 99.6%). Swift is unaffected, as it automatically skips all accuracy checks (including the invulnerability effects of Fly and Dig) and thus truly has 100% accuracy. A similar bug also applied to critical hits.

The bug was partially fixed in Pokémon Stadium by allowing the move to hit if the random byte is either less than the accuracy value or exactly equal to 255; this fix effectively causes every move in the game to hit 1/256 more often than indicated. The fix does not apply to critical hits, which are still capped at a 255/256 probability. In Generation II, the glitch was entirely fixed by removing the extra check and instead allowing moves calculated to have 100% accuracy (after applying all modifiers) to skip the random byte generation entirely, and by introducing new critical hit mechanics.

## In the Pokémon Mystery Dungeon series

Template:Incomplete

 File:Move Summary PSMD.png
In the Pokémon Mystery Dungeon series until Pokémon Mystery Dungeon: Gates to Infinity, accuracy was instead called "Hit Ratio" and displayed with a number of stars instead of a numerical value. More stars indicated a higher accuracy. For example, Scratch had a Hit Ratio of File:PMD Star IV.pngFile:PMD Star IV.pngFile:PMD Star IV.pngFile:PMD Star IV.pngFile:PMD Star IV.pngFile:PMD Star IV.pngFile:PMD Star IV.png. Hit Ratio did not always correlate with accuracy from the main series. For instance, some moves such as Scratch and Crunch which share the same accuracy in the main series had different Hit Ratios (or vice versa).

The term "accuracy" started to be used from Pokémon Mystery Dungeon: Gates to Infinity.

In Pokémon Super Mystery Dungeon, accuracy is displayed as a blue bar in the move summary. Unlike previous games, the Speed stat is used as an accuracy modifier; the higher speed a Pokémon has, the more likely its moves will be to hit.

In the Mystery Dungeon series, there are several ways of increasing the accuracy of moves. Much like in the core series games, Abilities such as Compound Eyes boost the accuracy of moves. Additionally, beginning from Gates to Infinity, moves can be ranked up when they are used over time, which will also increase the move's accuracy. The increase is permanent and will carry over to other teammate's with the same move. Items such as Accuracy ManualsTemplate:Sup/md or Accuracy DrinksTemplate:Sup/md can also permanently increase accuracy. Certain emeras can also increase accuracy when added to looplets.

## In other languages

Template:Project Games notice

de:Attackengenauigkeit und Trefferchance
fr:Précision
it:Precisione
pl:Accuracy
zh:命中率