We just had the update of Pokémon Sword & Shield... from v1.2.1 to v1.3.0
Pokémon Sword
- TitleID: 0100abf008968000
- v1.2.1 (BuildID: 157abfb96262aeb9)
- v1.3.0 (BuildID: 479bd2b581f4bc6a)
Pokémon Shield
- TitleID: 01008db008c2c000
- v1.2.1 BuildID: 896900182175428b
- v1.3.0 (BuildID: x)
There's a code we need converted from v1.2.1 to v1.3.0. The code will be the same on both Sword & Shield.
(Unfortunately, I only familiar with the theory otherwise I would be trying to hunt this myself. I can use Windows Calculator to produce known HEX shifts but that's the extent of my skills in this area.)
The code we need converted from v1.2.1 code to v1.3.0 is this one:
[Insta-KO Raid Pokémon v1.2.1]
04000000 008028C0 7900E808
04000000 008028C0 7900E81F
The code hunters who provided this explained this code changes the "CURRENT HP" value of all Pokémon in the Raid so any amount of damage is guaranteed to register as a value of 0 or less when dealt damage (which is when the game checks to see if the Pokémon should be KO'd.)
We had another code which alters one of the battle parameters provided by a Code Hunter which was a shift of +12950 HEX from v1.2.1 to v1.3.0. Since these were both battle related, I tested the shift to the above Insta-KO code:
[Tested +12950 HEX v1.3.0]
04000000 00815210 7900E808
04000000 00815210 7900E81F
The shifted code is in the correct "general area" of memory as the +12950 HEX does result in a v1.3.0 code that adjusts the "MAXIMUM HP" values of all Pokémon in the Raid (instead of "Current HP" values.)
The memory blocks for "CURRENT HP" values & "MAXIMUM HP" values should be in the same general area of memory (and are VERY likely right next to each other.)
(Unfortunately, adjusting the "MAXIMUM HP" values is useless as it turns all the Pokémon immortal and the Raid lasts until the time-out condition of 10 turns without the player winning.)
If someone is able to help fix this, that would be awesome! (This situation including the memory shift resulting in MAX HP instead of CUR. HP occurred when we updated from v1.0.0 to v1.1.0 but no one ever fixed the code on v1.1.0 and simply waited until v1.1.1 to provide a new code. So we never had a code in which I could use to compare the memory shift between CUR. HP & MAX HP to fix this with Windows Calculator in HEX MODE.)