PlagueVonKarma

gp for eseque min html

Dec 9th, 2020
139
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.47 KB | None | 0 0
  1. <h1 class="title">RBY's Recovery Failure Glitch</h1>
  2. <div id="toc"></div>
  3. <h1 id="intro">Introduction</h1>
  4.  
  5. <p>
  6. In RBY, it's possible for recovery moves (Soft-Boiled, Recover and Rest) to fail if your Max HP - Current HP leaves a difference of 255 or 511. Let's call these values "Failure Numbers". This glitch is a rarebut extremely notable problem when it occurs, as it could lead to you losing a Pokemon for making what would usually look like a good play. As a result, you have to take damage in some way just to get the chance to recover again, which can be pretty difficult. So, how does this happen? Why have the RBY Gods smited you with such a horrible glitch? For the sake of simplicity, we will be considering exclusively L100 Pokemon.
  7. </p>
  8.  
  9. <p>
  10. If you want to know what the Failure Numbers are like for Pokemon of different levels, simply take their Max HP and take away 255 or 511. Generally, the lower-levelled the Pokemon, the less likely it is to have one of these numbers. In hacked formats like Balanced Hackmons, however, you're more likely to have two Failure Numbers to consider, due to the sheer amount of HP these Pokemon have.
  11. </p>
  12.  
  13. <p>
  14. The glitch happens because the game only checks the second byte of HP, which causes some unintended issues when checking to see if recovery moves fail. You see, recovery moves are meant fail if Max HP - Current HP = 0. This seems simple, but when you only check the second byte, this can be problematic, especially considering 255 is the highest you can store in one byte. As a result, in the event of an overflow, a carry flag is set to take away 1 when calculating whether the recovery move should fail. Due to only checking one byte, Chansey's Max HP, in the eyes of recovery moves, is 191. So when taking away the current HP and considering the carry flag raised, if it's 192, it will equal 0. Thus, the recovery move fails. Due to the way recovery moves work in the Stadium games, this glitch does not occur there.
  15. </p>
  16.  
  17. <h1 id="intro">The Numbers</h1>
  18.  
  19. <div style="text-align: center;">
  20. <img style="display: inline-block;" src="images/sprites/chansey.png">
  21. <img style="display: inline-block;" src="images/sprites/snorlax.png">
  22. </div>
  23.  
  24. <p>
  25. Pokemon at L100 will have one singular Failure Number where this happens, as the required amount of HP for two to occur is quite large. However, there are two exceptions - Chansey and Snorlax - due to the sheer amount of HP they have. Chansey can fail at 448 or 192 HP, which can be represented as 63.7% or 27.3%. For Snorlax, this is 268 or 12 HP, which can be represented as 51.2% or 2.3%.
  26. </p>
  27.  
  28. <p>
  29. Here's a table featuring every Pokemon's Failure Numbers at L100. Funnily enough, some Pokemon are completely unaffected due to how low their HP is: Diglett, Abra, Magnemite and Magikarp. Magikarp can't learn any recovery at all though, so it doesn't really matter for it. Snorlax and Chansey's second Failure Numbers have not been written in, since it's not really good for presentation.
  30. </p>
  31.  
  32. <h1 id="conclusion">Conclusion</h1>
  33. <p>
  34. I hope this table and resource helps players be better-prepared for the glitch's occurrence. While how the glitch happens is decently well-known, the numbers and specifics were never really put to paper extensively. Sometimes, the RBY Gods will decide you aren't allowed to recover, force you to waste a turn, and make you lose a Pokemon, but with this information under your belt, you're just a little more equipped for those situations and can explore alternative plays.
  35. </p>
Advertisement
Add Comment
Please, Sign In to add comment