Update catch curve for pokeballs #3685
Conversation
AreaZR
force-pushed
the
catching
branch
3 times, most recently
from
1e87ff2
to
5968b94
Compare
|
Can you link a source? |
|
Can you stop with all the force pushing as previously asked? There is no need for a PR this simple to have all these force pushes in its history and it makes reviewing harder than it has to be. |
https://www.dragonflycave.com/mechanics/gen-vi-vii-capturing#throwing-a-ball sounds like the reason for this change. |
|
Bulbapedia. However, because the power in question is a decimal value, I refactored it so that it's 65536/(a^(3/16)), which is a tiny modification of the method but it allows me to do sqrt 4 times a cubed, which has rounding errors sure but it's the best I could do without delving into floating point madness. |
Where is |
Wolfram alpha when I was making approximations. |
But how though? |
Since Gen 6, the capture rate curve was changed to make pokeballs more effective on lower level pokemon It's by 65536 divided by 255 to the power of(1/5.33) and I did the work of translating that so a rough approximation can be done in integers, and so far, it seems to work close enough. I use this in my romhack for months now and it works fine.
This reverts commit 929ec54.
Since Gen 6, the capture rate curve was changed to make pokeballs more effective on lower level pokemon
It's by 65536 divided by 255 to the power of (1/5.33) and I did the work of translating that so a rough approximation can be done in integers, and so far, it seems to work close enough. I use this in my romhack for months now and it works fine.
Discord contact info
roseareazero