256
edits
Catch rate: Difference between revisions
→Trivia: to make the distinction clear, since signed integers don’t count from 0
DaneeBound (talk | contribs) (→Trivia: to make the distinction clear, since signed integers don’t count from 0) |
|||
| Line 643: | Line 643: | ||
* The line if a Pokémon escapes at three shakes in [[Generation III]] and {{gen|IV}}, "Shoot! It was so close, too!", remains in the internal data of the [[Generation V]] games despite not being used. | * The line if a Pokémon escapes at three shakes in [[Generation III]] and {{gen|IV}}, "Shoot! It was so close, too!", remains in the internal data of the [[Generation V]] games despite not being used. | ||
* In {{g|Sun and Moon}}, a Heavy Ball will always fail to catch a Pokémon whose weight is less than 220.46 lbs (100.0 kg) and whose catch rate is less than or equal to 20. This is because the game will set the catch rate to 0 when the catch rate becomes negative due to the -20 modifier that is applied. The only catchable Pokémon that this affects are {{p|Beldum}} and the [[guardian deities]]. This error was corrected in {{g|Ultra Sun and Ultra Moon}}. | * In {{g|Sun and Moon}}, a Heavy Ball will always fail to catch a Pokémon whose weight is less than 220.46 lbs (100.0 kg) and whose catch rate is less than or equal to 20. This is because the game will set the catch rate to 0 when the catch rate becomes negative due to the -20 modifier that is applied. The only catchable Pokémon that this affects are {{p|Beldum}} and the [[guardian deities]]. This error was corrected in {{g|Ultra Sun and Ultra Moon}}. | ||
* The numbers 255, 4096, and 65536 result from the data types used. 255 is the highest number a byte can encode. 4096 is the amount of space | * The numbers 255, 4096, and 65536 result from the data types used. 255 is the highest number a single unsigned byte can encode. 4096 is the amount of space an unsigned 12-bit integer can encode. 65536 is the amount of space two unsigned bytes can encode. | ||
==See also== | ==See also== | ||