Fixed [Indev 0.52] Computer Pokémon Have Infinite Power Points

[Narx221]

I started a combat and all time was the same i used pursuit (20) pp vs recover ( theoretically 16 )pp. I sold out my pursuit pp's and the poke still doing recover now

 

[jianmingyong]

I started a combat and all time was the same i used pursuit (20) pp vs recover ( theoretically 16 )pp. I sold out my pursuit pp's and the poke still doing recover now

I think this should be in the bugs thread

 

[Tornado9797]

I think this should be in the bugs thread

Done.

 

[-IcedUp-]

This would be a very good thing if this was installed in the game.

 

[Shiketh]

I caught a pokemon after a longer battle (didn't have any pokemon that could cause status effects) and when she was added to my battle group she had used more pp then available for a certain move. I had noticed on some trainer battles they use more pp then is normally allowed with certain skills, like Picnicker Gina had her hoppip use synthesis more the 5 times.

What I expected to happen:
Corsola to use Ancient power against me 5 times.

What actually happened:
Used it 6 times.

Steps to reproduce:
1. Have a long battle with a pokemon
2. capture it with 5 or fewer pokemon in your battle lineup
3. pokemon will use more pp then available for that certain skill

 

[Tornado9797]

I caught a pokemon after a longer battle (didn't have any pokemon that could cause status effects) and when she was added to my battle group she had used more pp then available for a certain move. I had noticed on some trainer battles they use more pp then is normally allowed with certain skills, like Picnicker Gina had her hoppip use synthesis more the 5 times.

What I expected to happen:
Corsola to use Ancient power against me 5 times.

What actually happened:
Used it 6 times.

Steps to reproduce:
1. Have a long battle with a pokemon
2. capture it with 5 or fewer pokemon in your battle lineup
3. pokemon will use more pp then available for that certain skill

View attachment 6981

I have moved this post from the duplicate thread to this thread because of its blatant evidence that helps to confirm this bug.

Edit: I have confirmed this for Indev 0.52.