Hello guys today I would like to offer you a little routine for asm
change the status of a pokemon of our team
first of all we need to know where is the offset required in this case:
offset_stato: 030043B0 the bytes of the pokemon from each team are distant from each other than 100 bytes
this is the routin we will use:
ldr r0, .8000 /*variabile 8000*/
ldr r1,.100 /*interval between the bytes status in pokemon team*/
ldr r0, .pokemon_data /*byte team pokemon status*/
add r0, r0, r1
mov r1, #0x80 /*poisong status*/
So here, we load the value "100" in r1 and then multiply it with r0 (the var 8000)
because we did? to choose the pokemon you want to change the status first of all we need to set the var 8000 with the number of pokemon to infect -1 for example, the 2 pokemon in team
setvar 0x8000 0x1 ( -1 we have to do to place in the team)
we said that the bytes of the team move away from each other by 100 bytes then the routine will multiply 1 by 100
then adds +100 to pokemon_data and we will have the offset of the state of 2 pokemon
ldr r0 ,.pokemon_data
add r0,r0 ,r1
as I said before, the routine loads the pokemon_data and the sum of the product of the variable * 100.
sum pokemon_data + product and puts everything in r0
mov r1 , # 0x80
strb r1, [ r0 ]
we r1 in the value of 80 (he was poisoned),and finally save the byte
This is a great tutorial, great place to start with little ASM skills (it's the first place I went to) but the tutorial is very specific, especially when the pokemon data block contains so much more information to edit like its level, any stat, pokerus, nickname. This is just a suggestion but it could really broaden your tutorial. It's still great how ever!
Also I think when you select a pokemon from a 'special' (i forget which one) it stores the variable into 0x8004 as either (0,1,2,3,4,5) for the slot which can be used to allow the player to select a pokemon.
While this will work, you should absolutely never directly access the Pokémon data. You should always use the built in encrypter to set data.
The reason being that the checksum can be affected by writes to the data, and not updating it correctly will result in your nice shiny Pokémon turning into a bad egg. Also, most of the encryption functions have built in checks and balances to prevent you writing nonsense data in. Just a little advice for you.
Hey guys, please check out my recreations of the gen 1 and 2 music on my custom engine at my SoundCloud! - Here!