Move data structure (Generation III): Difference between revisions

This article does not yet meet the quality standards of Bulbapedia. Please feel free to edit this article to make it conform to Bulbapedia norms and conventions.

Format

Every move in Ruby, Sapphire, FireRed, LeafGreen, and Emerald has a 12-byte data structure.

Notes:

1. All numbers are to be treated as unsigned unless otherwise specified.
2. Numbers prefixed with "0x", "$" or suffixed with "h" are hexadecimal.
3. Numbers prefixed with "0" are octal.
4. Numbers with no specific prefix or suffix are decimal.

• Accuracy determines the move's accuracy. Divide this value by 100 to get the actual accuracy. In Generation I, this value was 0-255 and divided by 256, which explains why sometimes attacks like Swift missed. This no longer happens in Generation III. This value is also set to 0 to reach 100% accuracy.
• Effect accuracy determines probability that the effect associated with a given move will happen. Divide this value by 100 to get the actual effect's accuracy. So that, for instance, a value of 100 gives the player 100% chances for the effect to trigger. For yet-unknown reasons, some moves have this value set to 0 which results in 100% accuracy as well.
• Affects whom determines who the move will hit on a 2 on 2 battle. It can be selected target, user, both foes, random foe, both foes and partner, field, opponent field (Spikes) and last opponent who moved. The following table indicates which value matches a certain target type.

Please note that it is theoretically possible to combine those values. For example, the player could have a move with this value set to 0x18. This would mean it would affect everyone except partner. But, no move seems to use such a combination in the games. Also, the special case 0x01 has a different target depending on the move. Counter targets the last attacker, while Metronome could target anything.

• Priority determines the moves speed. For example, ExtremeSpeed is faster than most other moves. This byte is signed, i.e. this value can be either positive or negative. If it is strictly less than 0x80 (128) then the player got the actual value. If not, the actual value equals: -1 * (256 - Current Value). Thus, value 0xFE (254) must be treated as -2 instead.
• Contact determines whether there is physical contact during the attack or not, for determining effects of certain abilities such as Static and Rough Skin. This byte also determines whether this move is affected by items such as King's Rock or BrightPowder.
• Padding consists of a sequence of 3 bytes. Each one of those bytes should be set to 0x00.