13,284
edits
Move data structure (Generation III): Difference between revisions
Move data structure (Generation III) (view source)
Revision as of 18:52, 13 August 2012
, 13 August 2012no edit summary
m (Type) |
mNo edit summary |
||
| Line 58: | Line 58: | ||
|} | |} | ||
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. | 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 the 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, {{M|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. | * '''Priority''' determines the moves speed. For example, {{M|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. | ||
* '''Flags''' determine additional properties of the move: | * '''Flags''' determine additional properties of the move: | ||