Jump to content

Recommended Posts

Posted

Right, because the MovePP/PPups storage only uses 1 byte for each move.

2 bits for PP up count (0-3)

6 bits for Current PP (0-63)

When PP is 64, an &= 0x3F sets it back to 0 as 7 bits are needed to store '64'.

Will need to see how the pkm actually stores 64 PP...

==============

http://bulbapedia.bulbagarden.net/wiki/Power_Point#Base_value_alteration

fix'd https://github.com/kwsch/PKHeX/commit/63b3c8b020509d6c1bcebd6d02756b76da576593

thanks for reporting!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...