Code: ASM Resource Thread

[Trainer 781]

I did replace the command. It was this pointer: CD 2C 02 08 and I changed it to YY+1 YY YY 08.

Okk, then VM/PM me the offsets. I'll then able to see thd problem.

To fix thd damage berry routine just, change the .hword in the second last line to .word. (The error was due to some issues in Hackmew's compiler)

 

[daniilS]

Okk, then VM/PM me the offsets. I'll then able to see thd problem.

To fix thd damage berry routine just, change the .hword in the second last line to .word. (The error was due to some issues in Hackmew's compiler)

Actually, you can never load a relative halfword.

 

[mariomaniac432]

I've been having some trouble getting the Berry System to work. For some reason, the script crashes when it gets to the first instance of the Get Tree Data routine. I know this is where the problem is because if I remove it from the script, it doesn't crash until it gets to the Berry Bag Selection routine, which for some reason crashes the game if I have a berry in the bag, but that could be a result of removing the Get Tree Ddata routine. I thought that maybe the problem was I installed JPAN's Save Block hack wrong (instructions seemed a little confusing at first, but I'm pretty sure I did it right), so I found this patch with the hack, applied it a clean FireRed 1.0 ROM, and then put all the other routines in, and had the same problem.

My script was a simple copy/paste from this thread, which the offsets filled in properly of course. All the ASM rotuines were also unmodified, and copied directly from this thread, I also tried compiling them myself and inserting them that way, but nothing seems to work.

 

[leyn09]

Edit : already solved. Sorry! I didnt check out first the thread.

 

[Blah]

I've been having some trouble getting the Berry System to work. For some reason, the script crashes when it gets to the first instance of the Get Tree Data routine. I know this is where the problem is because if I remove it from the script, it doesn't crash until it gets to the Berry Bag Selection routine, which for some reason crashes the game if I have a berry in the bag, but that could be a result of removing the Get Tree Ddata routine. I thought that maybe the problem was I installed JPAN's Save Block hack wrong (instructions seemed a little confusing at first, but I'm pretty sure I did it right), so I found this patch with the hack, applied it a clean FireRed 1.0 ROM, and then put all the other routines in, and had the same problem.

My script was a simple copy/paste from this thread, which the offsets filled in properly of course. All the ASM rotuines were also unmodified, and copied directly from this thread, I also tried compiling them myself and inserting them that way, but nothing seems to work.

The berry tree routine is bugged. I will go ahead and redo it sometime in the future. Sorry.

 

[Blah]

Hi FBI, first of all thanks for your work! You've been really helpful.
My question regards your battle routine https://www.pokecommunity.com/showthread.php?p=8527650#8527650 .
I've been trying it without success in my Ruby rom hack hoping it would work just like in Fire Red.
Is there any way to remove the whiteout after losing a battle in a Ruby hack rom?

No clue. I have not even looked at a Ruby ROM since 2008.

Can we have run-like speed for surf and mach bike speed in FR? Even better would be an arbitrary speed value!

That's actually very easy. There's a bit in RAM somewhere which controls this. I vaguely remember posting about it here, but I'll get back to you with more content.

I'd like to say that this thread has been really helpful for me as my ASM skills are far worse than sub-par and, also, the Chain-Fishing one in particular is really cool to me. (◕‿◕✿)

I'd also like to request something for Fire Red BPRE v1.0 (adding to the infinite list of requests...):
Stance Change.
Basically, where a Pokémon uses an offensive move and changes its form to a more offensive Pokémon (or, rather, just a different index-number Pokémon entirely). However, when it uses a certain move (or just a status move would be fine, too), it reverts back to the old form.
EDIT: Oh, and it would also have to revert to the other form outside of battle.
What I was thinking was two separate abilities in order to accomplish this, but if one is possible, then that's great too!
Thanks in advance!

God I sound so rude I am so sorry

EDIT: Also, should I go to DaniilS with this? I noticed that he had his own thread for form(e)s...

EDIT EDIT: Okay, I just noticed something while I was trying to get the Male-only and Female-only evolution methods working on Burmy.
But ALL of the Pokémon generated by your routine are Male unless if they have more of an 82 percent chance of being female, in which case they are, and the Pokémon already caught turn into females. This is also shown in you post showcasing it, as the Tyranitar are also all Male.
Just wanted to say this, haha...

Yes, go to daniilS with this. He should be done by now, 4 or so months ago he said he was working on forms and mega evolutions. He should have everything worked out now if he isn't slacking ;D

Few simple questions on breeding, egg groups and all that. You said it's all doable via a Pokémon Editor. What I want, actually is that Charizard evolutionary line breeds only with its line and/or Ditto. No Dragon/Monster egg groups. Will I have to make an egg group for each evolutionary family?
Also, how can I make Ditto breeds with himself too, not only all other Pokémon? And genderless Pokémon, like Magnemite? How can I make them breed?
Finally, for Nidorans and Volbeat/Illumise, I wanna make the male breed with the female, but not breedable with Ditto. How can I do it?



Here, I just want to know if I can make all Pokémon to be Docile as default or if I can change all natures' data, so all natures behave like Docile. Is either of these possible?
Thanks in advance!

For something specific like this it's better to just add in the exceptions yourself. The game will at some point check species for Ditto :)

If you give up, I can give you hints. My policy about strictly specific routines still stand however.

 

[leyn09]

Well done on that KDS !

Same routine with Emerald offset !

Here :

Spoiler:

Spoiler:

Routine at XXXXXX:

.text
.align 2
.thumb
.thumb_func
.global lifeorbrecoil

[B]SheerForceCheck:
      ldr r1, .UserBank
      ldr r2, .BattleStruct
      ldrb r1, [r1, #0x0]
      mov r0, #0x58
      mul r0, r1
      add r0, r0, r2
      mov r2, #0x20
      add r2, r0, r2
      ldrb r2, [r2]
      cmp r2, [B]#0x7E[/B] /*Sheer Force*/
      bne EffectCheck 
      ldr r0, .CurrMove
      ldrh r3, [r0, #0x0]
      mov r0, #0x0
      ldr r1, .FEHalfWord
      ldr r2, .SheerForceTable

Loop:
      lsl r4, r0, #0x01
      add r4, r4, r2
      ldrh r4, [r4, #0x0]
      cmp r3, r4
      beq Exit
      cmp r4, r1
      beq EffectCheck
      add r0, #0x1
      b Loop
[/B]
EffectCheck:
      mov r1, r8
      cmp r1, #0x1E
      beq KingsRock
      cmp r1, #0x3E
      beq ShellBell
      cmp r1, [U]#0xKK[/U]    /*Life orb held item effect*/
      bne Exit
    
CheckOutcome:
      ldr r0, .Outcome
      ldrb r0, [r0, #0x0]
      mov r5, #0x29
      and r5, r0
      cmp r5, #0x0
      bne Exit

[B]CheckUturnVoltSwitch:
      ldr r0, .CurrMove
      ldrh r0, [r0]
      ldrh r1, .VoltSwitchID
      cmp r0, r1
      beq Exit
      ldrh r1, .UTurnID
      cmp r0, r1
      beq Exit [/B]

CheckIfMoveDamagedSomeTarget:
      ldr r1, .DamageStruct
      ldr r4, .TargetBank
      ldrb r2, [r4, #0x0]
      lsl r0, r2, #0x02
      add r0, r0, r2
      lsl r0, r0, #0x02
      add r6, r1, #0x4
      add r0, r0, r6
      ldr r1, [r0, #0x0]
      cmp r1, #0x0
      beq Exit
      ldr r0, .FFHalfWord
      cmp r1, r0
      beq Exit
      
CheckIfUserIsNotTheTarget:
      ldr r0, .UserBank
      ldrb r3, [r0, #0x0]
      cmp r3, r2
      beq Exit

CheckMagicGuard:
      ldr r2, .BattleStruct
      ldrb r1, [r0, #0x0]
      mov r0, #0x58
      mul r0, r1
      add r0, r0, r2
[B]      mov r2, #0x20
      add r2, r0, r2
      ldrb r2, [r2]
      cmp r2, [U]#0x63[/U] /*Magic Guard*/
      beq Exit

HPCheck:[/B]
      ldrh r1, [r0, #0x28]
      cmp r1, #0x0
      beq Exit

SetLifeOrbRecoilBit:
      ldr r1, .LORBit
      mov r0, #0x1
      strb r0, [r1]

Exit:
      ldr r1, .Return2
      bx r1

KingsRock:
      ldr r0, .Return3
      bx r0

ShellBell:
      ldr r1, .Return1
      bx r1

Divider:
      ldr r2, =0x082E7540+1
      bx r2

ScriptPusher:
      ldr r0, =0x0803FAFC+1
      bx r0

.align 2
.UserBank: .word 0x0202420B
.TargetBank: .word 0x0202420C
.BattleStruct: .word 0x02024084
.DamageStruct: .word 0x0202437C
[B].CurrMove: .word 0x020241EA[/B]
[B].SheerForceTable: .word 0x08XXXXXX[/B]
.Outcome: .word 0x0202427C
[B].FEHalfWord: .word 0x0000FEFE[/B]
.FFHalfWord: .word 0x0000FFFF
.Return1: .word 0x08045794+1
.Return2: .word 0x0804582A+1
.Return3: .word 0x080456EC+1
.LORBit: .word 0x0203E338	/*It's actually a FreeRam loc*/
[B].UTurnID: .word 0x00000YYY[/B]	/*ID number of U-Turn*/
[B].VoltSwitchID: .word 0x00000ZZZ[/B]	/*ID number of Volt Switch*/

/*At 080456DC: 00 48 00 47 XX+1 XX XX 08*/

Spoiler:

Routine at YYYYYY:

.text
.align 2
.thumb
.thumb_func
.global endcommandwithlifeorbsupport

Main:   
      ldr r1, .LORBit
      ldrb r0, [r1]
      cmp r0, #0x1
      bne EndCommand

LifeOrb:
      push {lr}
      push {r2-r7}
      mov r0, #0x0
      strb r0, [r1]
      ldr r0, .UserBank
      ldrb r3, [r0]      
      mov r0, #0x58
      mul r0, r3
      ldr r2, .BattleStruct
      add r2, r2, r0
      ldrh r0, [r2, #0x28]
      cmp r0, #0x0
      beq Exit
      ldr r0, =0x0202420F
      strb r3, [r0, #0x0]
      ldr r0, =0x02024274
      strb r3, [r0, #0x17]
      ldr r4, =0x020241F0
      ldrh r0, [r2, #0x2C]
      mov r1, #0xA
      bl Divider
      strh r0, [r4, #0x0]
      cmp r0, #0x0
      bne NotZero
      mov r0, #0x1

NotZero:
      strh r0, [r4, #0x0]
      bl ScriptPusher
      ldr r1, .ScriptPointer
      ldr r0, .LifeOrbDamageScript
      str r0, [r1, #0x0]
      pop {r2-r7}
      pop {r0}
      bx r0

Exit:
       pop {r2-r7}
       pop {r0}

EndCommand:
      ldr r0, =0x0804B664+1
      bx r0

Divider:
      ldr r2, =0x082E7540+1
      bx r2

ScriptPusher:
      ldr r0, =0x0803FAFC+1
      bx r0

.align 2
.LifeOrbDamageScript: .word 0x08BBBBBB
.ScriptPointer: .word 0x02024214
.UserBank: .word 0x0202420B
.BattleStruct: .word 0x02024084
.LORBit: .word 0x0203E338	/*Same as in previous routine*/

/*YY+1 YY YY 08 must replaces the "end" command pointer */

Spoiler:

Battle Script at BBBBBB:

39 20 00 FA 20 E3 03 02 [B]SS SS SS 08 [/B]10 84 01 12 40 00 35 80 42 02 02 00 01 00 

00 0B 01 0C 01 19 01 00 00 00 00 00 3C

String at SSSSSS:

FD 0F 00 E0 E3 E7 E8 00 E7 E3 E1 D9 00 E3 DA 00 DD E8 E7 00 C2 CA AB FF

Bonus, Life Orb boost (lightball updated included). UPDATE for Emerald : I added a routine to make a new item that boost a certain type of attack. If you have a fairy type in your hack rom, you can now have an item that boost that type. You can adjust the boost the same way than miracle seed and such in G3T. I also implemented the TimeSpace orb in the routine :

Spoiler:

Emerald:

CheckLifeOrb:
cmp r2, #[I][U]0x43[/U][/I]	/*Held item effect of life orb, I chose 0x43 (= 67 in decimal) because it's unused*/
beq Lifeorb

CheckNewItem:
cmp r2, #[I][U]0x44[/U][/I]	/*Held item effect of the boost item, I chose 0x44 (= 68 in decimal) because it's unused*/
beq NewItem

CheckAdamantOrb:
cmp r2, #[I][U]0x45[/U][/I]	/*Unused held item effect*/
bne CheckLustreous
ldrh r0, [r6]
mov r3, #0xFF	/*0xFF + 0xE4 = 0x1E3 = 483 = index number of Dialga*/
add r3, #0xE4
cmp r0, r3
beq AdamantOrb

CheckLustreous:
cmp r2, #[I][U]0x46[/U][/I]	/*Unused held item effect*/
bne CheckGriseous
ldrh r0, [r6]
mov r3, #0xFF	/*0xFF + 0xE5 = 0x1E4 = 484 = index number of Palkia*/
add r3, #0xE5
cmp r0, r3
beq LustreousOrb

CheckGriseous:
cmp r2, #[I][U]0x47[/U][/I]	/*Unused held item effect*/
bne CheckLightBall
ldrh r0, [r6]
mov r3, #0xFF	/*0xFF + 0xE8 = 0x1E7 = 487 = index number of Giratina*/
add r3, #0xE8
cmp r0, r3
beq GriseousOrb
b Back

AdamantOrb:
push {r0-r5}
mov r1, #8	/*Steel type*/
mov r2, #0x10	/*Dragon type*/
b CheckExceptionTypeAttack

LustreousOrb:
push {r0-r5}
mov r1, #0xB	/*Water type*/
mov r2, #0x10	/*Dragon type*/
b CheckExceptionTypeAttack

GriseousOrb:
push {r0-r5}
mov r1, #7	/*Ghost type*/
mov r2, #0x10	/*Dragon type*/
b CheckExceptionTypeAttack

NewItem:
push {r0-r5}
mov r1, #9	/*New type you want to boost*/
mov r2, #9	/*New type you want to boost, here I choose the same because I want it boost only one type*/

CheckExceptionTypeAttack:
ldr r4, CheckTypeLoc
ldr r4, [r4]
ldrb r4, [r4, #0x13]
cmp r4, #0
beq GetMoveType
mov r5, #0x3F
and r4, r5
cmp r4, r1
beq Boost
cmp r4, r2
beq Boost
b PopAndBack

Back:
ldr r0, Return
bx r0

PopAndBack:
pop {r0-r5}
b Back

CheckLightBall:
cmp r2, #0x2D
bne Back
ldrh r0, [r6]
cmp r0, #0x19
beq Lightball
b Back

GetMoveType:
ldr r3, CurMoveIndex
ldrh r3, [r3]
ldr r4, MoveData
mov r5, #0xC
mul r5, r3
add r4, r5
ldrb r4, [r4, #2]
cmp r4, r1
beq Boost
cmp r4, r2
bne PopAndBack

Boost:
pop {r0-r5}
ldrh r3, [r6, #0x2E]
lsl r0, r3, #4
push {r1}
mov r1, #6
mul r3, r1
pop {r1}
add r3, r0
lsl r3, #1
ldr r0, LocItems
add r3, r0
add r3, #0x13
ldrb r0, [r3]
mov r3, #0x52
mul r0, r3
lsr r0, #6
add r0, #0x7B
mul r7, r0
lsr r7, #7
mov r3, r8
mul r3, r0
lsr r3, #7
mov r8, r3
b Back

Lifeorb:
mov r0, r8
mov r3, #0xA7
mul r0, r3
lsr r0, #7
mov r8, r0
mul r7, r3
lsr r7, #7
b Back

Lightball:
mov r0, r8
lsl r0, r0, #0x1
mov r8, r0
lsl r7, r7, #0x1
b Back

.align 2
Return: .word 0x0806983E+1
LocItems: .word 0x085839A0           /*Location of your items Data*/
CurMoveIndex: .word 0x020241EA
MoveData: .word 0x0831C898           /*Location of your move data*/
CheckTypeLoc: .word 0x0202449C

/*00 48 00 47 XX XX XX 08 00 00 00 at 0x6982C*/

Fire Red:

cmp r2, #0x43   /*Held item effect, I chose 0x43 (=67 in dec) because it is unused in the game*/
beq Lifeorb
cmp r2, #0x2D
bne Back
ldrh r0, [r6]
cmp r0, #0x19
beq Lightball
b Back

Lifeorb:
mov r0, r8
mov r3, #0xA7
mul r0, r3
lsr r0, #7
mov r8, r0
mul r7, r3
lsr r7, #7
b Back

Lightball:
mov r0, r8
lsl r0, r0, #0x1
mov r8, r0
lsl r7, r7, #0x1

Back:
ldr r0, Return
bx r0

.align 2
Return: .word 0x0803F00A+1

/*00 48 00 47 XX XX XX 08 00 00 00 at 0803EFF8*/

Yep, it is now updated

How should I use both the recoil and boost effect? Should it be separately compiled and just put the same held item byte effect in each routines?

 

[kleenexfeu]

How should I use both the recoil and boost effect? Should it be separately compiled and just put the same held item byte effect in each routines?

Recoil and boost work indeed seperatly, as you can see the branch aren't done at the same places. So yeah you have to give the same effect in both routine as well as assembling them to have both recoil/boost effects.

 

[Blah]

OAM routines

The first hackathon was probably the worst thing that could have happened for this thread. It completely killed my motivation for hacking and made me quit for a few months. There are some good things that came out of it, I was able to do a lot of research on things I hadn't before including field moves, OAM, trainer generation and such. I was looking around my older routines for OAM manipulation, and I had trouble understanding and ripping my own code! I had lost the source code, so I decided to rip as much as I can and redo the jibberish including some clean up.

Similar routines to these ones I'm presenting were used for the custom intro in team 4's hackoff ROM :)

Generating OAMs

This routine is only to generate OAMs which are trainer or Pokemon sprites. I've modified it to be usable with a script, but honestly, setting the values yourself via ASM would've been faster (not that this is noticeably slow, just comparatively). I will have to do more research on making it portray an arbitrary image, but with the expansion work on the Pokedex and such, I don't see it as very necessary anymore.

How to insert:
Compile and insert the following routine into a free word aligned offset.

Spoiler:

.text
.align 2
.thumb
.thumb_func
 
main:
        push {r0-r4, lr}
        sub SP, SP, #0x14
       
        @load PID
        ldr r2, =(0x20370B8) @PokeSlot
        ldrb r2, [r2]
        cmp r2, #0x6
        beq shiny
        ldr r0, =(0x2024284)
        mov r4, #0x64
        mul r2, r2, r4
        add r2, r2, r0
        ldrh r2, [r2] @PID
       
        @load TID
        ldr r1, =(0x300500C)
        ldr r1, [r1]
        ldrh r1, [r1, #0xA] @TID
        b cont
               
shiny:
        mov r0, #0x0
        mov r1, r0
        mov r2, r0
 
cont:
        @X-pos
        ldr r0, =(0x20370BA)
        ldrh r0, [r0]
        str r0, [SP] @X-Pos
       
        @Y-pos
        ldr r0, =(0x20370BC)
        ldrh r0, [r0]
        str r0, [SP, #0x4] @Y-Pos
       
        @pal #
        ldr r0, =(0x20370BE)
        ldrh r0, [r0]
        str r0, [SP, #0x8] @pal #
       
        ldr r3, =(0x20370C0)
        ldrb r3, [r3]
        cmp r3, #0x1
        bne nonsil
        mov r3, #0x0
        str r3, [SP, #0xC] @occupacity
        b unkn
       
nonsil:
        ldr r3, =(0x0000FFFF)
        str r3, [SP, #0xC] @occupacity
       
unkn:  
        @??? - No idea, but leave as 0s
        @possibly priority?
	ldr r0, =(0x20370C6)
	ldrb r0, [r0]
        str r0, [SP, #0x10]
	mov r0, #0x0
        str r0, [SP, #0x14]
       
        @species/sprite ID
        ldr r0, =(0x20370C2)
        ldrh r0, [r0]
 
        @front VS back
        ldr r3, =(0x20370C4)
        ldrb r3, [r3]
 
        @display func
        ldr r4, =(0x810BDAC +1)
        bl linker
        add SP, SP, #0x14
        pop {r0-r4, pc}
       
 
 
linker:
        bx r4
 
.align 2

Compiled version:

1F B5 85 B0 18 4A 12 78 06 2A 08 D0 17 48 64 24 62 43 12 18 12 88 16 49 09 68 49 89 02 E0 00 20 01 1C 02 1C 13 48 00 88 00 90 13 48 00 88 01 90 12 48 00 88 02 90 12 4B 1B 78 01 2B 02 D1 00 23 03 93 01 E0 0F 4B 03 93 0F 48 00 78 04 90 00 20 05 90 0E 48 00 88 0E 4B 1B 78 0E 4C 00 F0 02 F8 05 B0 1F BD 20 47 C0 46 B8 70 03 02 84 42 02 02 0C 50 00 03 BA 70 03 02 BC 70 03 02 BE 70 03 02 C0 70 03 02 FF FF 00 00 C6 70 03 02 C2 70 03 02 C4 70 03 02 AD BD 10 08

Usage:
The usage is quite simple, but it takes up a lot of temporary variables :P

@var 0x8000 - Slot #. Set 0x6 for shiny.
@var 0x8001 - X-pos
@var 0x8002 - Y-pos
@var 0x8003 - Unoccupied Pal ID number. See OAM viewer.
@var 0x8004 - Occupacity silluette set 1
@var 0x8005 - species/trainer sprite ID
@var 0x8006 - Front (1) or Back (0)
@var 0x8007 - Toggle trainer or Pokemon

Some quick notes about these variables.

Variable 0x8000 is to determine the Pokemon's shinyness. If you're showing a Pokemon in your party just use that Pokemon's party slot. If you're showing a shiny Pokemon go ahead and use 0x6. Basically 0x6 = shiny, anything else (must be lower) depends on party slot.

Variable 0x8003 plays a key role. Make sure in the OAM viewer the sprite ID is free.

Here sprite number 0 is taken by Oak's OAM. Click the Arrow until you find something not occupied, and set this variable to that value!

Variable 0x8007 is a switch of sorts. It determines whether to show a trainer sprite or a Pokemon sprite.

I think the rest of the variables are self explanatory. Mess around with them a little :)

OAM tracking

So I'm sure you can imagine, that at some point in time you want your OAM to disappear. You can't have it on the screen forever, maybe even make it disappear temporarily and reshow it without having to do the painfully expensive creation call again. I made a routine which will take into account the last OAM ID which you created and stores it in var 0x8008. Note that this is an ID assigned by the game code, not the same ID as the one we assigned on creation. Therefore it's important to track this.

How to insert

Compile and insert the following routine into free space.

Spoiler:

.text
.align 2
.thumb
.thumb_func

@ID of last OAM created - 0x8008
@Hook at 0x80070B0 via r1

main:
ldr r1, =(0x20370C8)
strh r0, [r1]
lsl r6, r6, #0x10
lsr r6, r6, #0x10
lsl r4, r4, #0x18
lsr r4, r4, #0x18
lsl r0, r0, #0x4
ldr r1, =(0x80070BA +1)
bx r1

.align 2

Navigate to 080070B0 and insert the following byte changes:

00 49 08 47 XX XX XX 08

Where XX XX XX is the location your inserted your routine in reverse hex +1. The trailing "08" may change to 09 or something depending on where you inserted it. Remember to stay word aligned!

Usage:
This routine doesn't really do anything by itself. It's more of a routine which works in the background. It just writes to variable 0x8008 the last displayed OAM's ID. Basically, just insert it and do nothing :3

A quick explanation of how OAMs are shown/hidden in FireRed.

There's a neat RAM structure in FireRed which controls whether or not to show or unshow an OAM on the screen. This OAM's ID needs to be present in said structure. The structure, for some unknown reason, is 40 bytes in size. It looks like this:

[OAM ID (1 byte)] [OAM ID (1 byte)] [OAM ID (1 byte)] ... [Byte 0x3F] [Filler bytes] ...[40th filler byte]

In case you don't understand by now, it's basically a table of X entries where each entry is an OAM's ID to display. Every entry after the byte 0x3F is not read by game code, and is therefore nothing more than filler bytes!

The reason as to why I'm confused the structure is 40 bytes is because the routines which use this structure restrict themselves by using another structure. This second structure only holds 13 OAMs at a time, which is why we can only have 13 OAMs present in FR on screen at once WITHOUT fully customized code. For the most part you'll never go over 13 anyways. I used 9 in total for the custom intro and the screen was cluttered :X

My guess as to why it's 40 bytes is because it's used for animation frames as well. I'm not sure, I haven't researched that.
This structure is located at 0x2021800.

Hiding OAMs created

Now that you understood the data structure, you need to remove your OAM's byte ID from the table. But how do you know which byte is your OAM's byte? That was what the previous tracker routine was for. Right after you create your OAM the corresponding table ID will be in var 0x8008. Copy this value into somewhere you won't lose it (i,e a non-temporary variable), from there you can callasm this routine with the appropriate parameters :)

How to insert:

Compile and insert the following routine to free space:

Spoiler:

.text
.align 2
.thumb
.thumb_func

@OAM ID to hide - 0x8000

main:
push {r0-r2, lr}
ldr r0, =(0x2021800)
ldr r2, =(0x20370B8)
ldrb r2, [r2]

loop:
ldrb r1, [r0]
cmp r1, r2
beq set
add r0, r0, #0x1
b loop

set:
mov r1, #0x3F
strb r1, [r0]

done:
pop {r0-r2, pc}

.align 2

Usage:

In a script, set variable 0x8000 to the OAM ID you want to vanish, then simply callasm this routine. This data structure is updated every frame from what I was able to see, so the results should be immediate.

Show OAM

Sometimes you want to hide an OAM but only temporary. This routine will show an OAM which has already been loaded, but flagged as hidden or similar.

How to insert:

Compile and insert into free space the following routine:

Spoiler:

.text
.align 2
.thumb
.thumb_func

@OAM ID to set - 0x8000

main:
push {r0-r2, lr}
ldr r0, =(0x2021800)

loop:
ldrb r1, [r0]
cmp r1, #0x3F
beq set
add r0, r0, #0x1
b loop

set:
ldr r2, =(0x20370B8)
ldrb r2, [r2]
strb r2, [r0]
mov r1, #0x3F
add r0, r0, #0x1
strb r1, [r0]

done:
pop {r0-r2, pc}

.align 2

Usage:

In a script, set variable 0x8000 to the OAM ID you want to reappear, then simply callasm this routine. This data structure is updated every frame from what I was able to see, so the results should be immediate.

Closing notes:

I may or may not update these with animations as well. One I'm particularly interested in doing is a slow fade. The biggest thing I want to address is how to use these in a script. I think it's fairly intuitive, but a quick example may help :)

Spoiler:

#dyn 0x740000
#org @start
lock
faceplayer
fadescreen FADEOUT_BLACK

'setting up parameters for OAM creation routine
setvar 0x8007 0x0
setvar 0x8000 0x0
setvar 0x8001 0x74
setvar 0x8002 0x64
setvar 0x8003 0x1
setvar 0x8004 0x0
setvar 0x8005 0x85
setvar 0x8006 0x1
callasm 0x[location you inserted creation routine +1]

'recall our last created OAM is stored in 0x8008

copyvar 0x8009 0x8008

'simply vanishing the OAM
copyvar 0x8000 0x8008
callasm 0x[location you inserted hide routine +1]


'creating a second OAM!
setvar 0x8000 0x0
setvar 0x8001 0x74
setvar 0x8002 0x64
setvar 0x8003 0x2
setvar 0x8004 0x0
setvar 0x8005 0x86
setvar 0x8006 0x1
callasm 0x[location you inserted creation routine +1]


copyvar 0x800A 0x8008
copyvar 0x8000 0x8008
'remove visibility
callasm 0x[location you inserted hide routine +1]
jump @loop

#org @loop
'-----------------------------------
compare 0x8007 0x60
if == jump @done ' Equal To

'show OAM 1
copyvar 0x8000 0x8009
callasm 0x[location you inserted show routine +1]
pause 0x10

'hide OAM 1
copyvar 0x8000 0x8009
callasm 0x[location you inserted hide routine +1]

'show OAM 2
copyvar 0x8000 0x800A
callasm 0x[location you inserted hide routine +1]
pause 0x10

'hide OAM 2
copyvar 0x8000 0x800A
callasm 0x[location you inserted hide routine +1]

'increment loop
addvar 0x8007 0x1
jump @loop

#org @done
'-----------------------------------
fadescreen FADEIN_BLACK
msgbox @text ' Phew.
callstd MSG_LOCK ' Built-in lock command
release
end


#org @text
= Phew.

Play around with it. It can be fun, and hopefully this will open more doors for hackers. I've made it as friendly as possible even opening up the potential to use it in scripts, but if you have any questions you can direct them to me at the ASM help thread or something :D

 

[FamiliaWerneck]

Preventing TMs from being consumed on use

Quick research:
TMs are deleted in two places. The first place is in their own function. When called from the bag, after use the TM has it's own deletion mechanism. The second way is from the bag, after you use a TM the bag attempts to delete it as well. Well, the solution is quite simple. There's two ways to do this, either go to 0809A1D8 call your own function there which checks if the item is a TM, and if it is, just jump to the end. Or much more simply you just remove the parts from the bag and tm function that deletes the TM (Which is what I did). The former way is a way you can make another item you have unconsumable.

To insert:
Do the byte changes below
0x124F78: 00 00 00 00
0x125C80: 00 00 00 00

Make it Ungivable:
insert that at 0x1326B8: 00 00 17 E0

Make it consumable after animation:
Insert: 00 00 00 00 at 0x124F78

To remove the quantities showing up in the bag:

Compile and insert into free space:

Spoiler:

.text
.align 2
.thumb
.thumb_func

main:
	cmp r5, #0x0
	bne end
	ldr r3, =(0x8131EFE +1)
	bx r3

end:
	mov r0, r7
	mov r1, #0x8
	mov r2, r4
	ldr r6, =(0x81335B0 +1)
	bl link
	ldr r3, =(0x8131EFE +1)
	bx r3

link:
	bx r6

.align 2

Here's a compiled version:

00 2D 01 D1 05 4B 18 47 38 1C 08 21 22 1C 04 4E 00 F0 02 F8 01 4B 18 47 30 47 C0 46 FF 1E 13 08 B1 35 13 08

Now navigate to 0x131EF4 and insert:

00 48 00 47 XX XX XX 08

Where XX XX XX is the pointer to where you assembled the routine +1

Now navigate to 0x131EA5 and change the byte to E0

Unsellable:
Basically for the TMs, you can still sell them to vendors. To change this, you need to modify each TM individually. It's unfortunate, but the game checks if an item can be sold my comparing it's market price to zero. If it's strictly greater than zero, then you can sell it to a vendor, seems to be the rule. So to make TMs unsellable you need to set their market prices individually to zero.
I can't use my own checks to disguise the TMs as unique because the sell routine in shops are used for ALL items including potions, berries, TMs, and other items like nuggets.


Present :3

I've got a HUGE problem with this!!!!
I was playing and normally using TMs for 20k Pokémon (not a number, I'm exaggerating). I'm after the league now, and I was giving Toxic to some Pokémon, to help me catch others, so I could get the 60 Pokémon to get National Dex and be able to go to Four Island.
Problem is, when I was going to give Toxic to my Chansey, it was gone! Then I looked for the Psychic TM (other move I give to her, I took it out briefly for Rock Smash), and it was gone too. What the hell happened?
Is there a limit for this?
I got my save back, from the GBA in-game save, and I had Toxic yet. I tested giving it to one Pokémon and it didn't disappear. Then I gave it to other and then it wasn't there anymore. Is there a limited amout of times I can use a TM? Or there's something incomplete about this hack?

 

[Blah]

I've got a HUGE problem with this!!!!
I was playing and normally using TMs for 20k Pokémon (not a number, I'm exaggerating). I'm after the league now, and I was giving Toxic to some Pokémon, to help me catch others, so I could get the 60 Pokémon to get National Dex and be able to go to Four Island.
Problem is, when I was going to give Toxic to my Chansey, it was gone! Then I looked for the Psychic TM (other move I give to her, I took it out briefly for Rock Smash), and it was gone too. What the hell happened?
Is there a limit for this?
I got my save back, from the GBA in-game save, and I had Toxic yet. I tested giving it to one Pokémon and it didn't disappear. Then I gave it to other and then it wasn't there anymore. Is there a limited amout of times I can use a TM? Or there's something incomplete about this hack?

No, there shouldn't be a limit. Can anyone else confirm this bug? Also can you give me a specific case for when the TM disappears? There was a bug where it can get consumed if 4 moves were already learned. I fixed that already (it's in a separate post).

 

[FamiliaWerneck]

No, there shouldn't be a limit. Can anyone else confirm this bug? Also can you give me a specific case for when the TM disappears? There was a bug where it can get consumed if 4 moves were already learned. I fixed that already (it's in a separate post).

I'll confirm this second bug. Also, if you want, I can record a video of me making the TM move magically disappear. HAHAHAHA

EDIT: Second bug not confirmed!
When I noticed this, I used it in my Abra, which only had Teleport. Then it was gone after I used it in my Ekans, which had 4 moves learned.
But now, I used in an Ekans with 4 moves learned first, and I kept the TM. Then I used in my Abra, which had only one, and then the TM disappeared.
So, 4 moves learned bug is not my problem, so it seems.

 

[Blah]

Frontier Routines - Opponent Party generation

I've been meaning to implement a frontier of sorts into FireRed for some time but never really got a good opportunity to do so. Today I got a little bored and decided that I might as well start up. The first problem is obviously to generate a pseudo random party for the opposing trainer. That's what I've done today!

I had made a generation routine in the past as well, but it was incomplete and a little buggy. This one, as far as I can tell in my tests, should work fine :)


Setting up some prerequisites:
When making the routine for Pokemon generation, it was important that the hacker had some customization about which Pokemon were allowed into the opponents party (to prevent legendary Pokemon, or some specific Pokemon into the competition). The best way to do that is to either make a table of the Pokemon allowed to be in the opponent's party, or a table of the Pokemon not allowed to be in it. I decided to make the hacker do a table of all the Pokemon species allowed to be in the opponent's party.

It's important to remember that Pokemon Species ID takes 2 bytes per species, and that each entry in the table is in reverse hex. Bulbasaur for example would be: "01 00" in the table. The size of the table is up to you. The biggest reason I made the table be a table of all the Pokemon allowed is because this allows you to put more than 1 entry of the same Pokemon (thus increasing it's likelihood to be selected) ==> not all Pokemon species have the same chance of being selected!

Find some half-word aligned free space (offset divisible by 2) and fill up your table with as many entries as you'd like in this format:

[2 bytes (ID)] [2 bytes (ID)] ...

Write down how many entries you have, and where the start of the table is.


How to insert:

First take a look at the routine in the spoiler. Scroll to the very bottom, and you will see two fields which need filling. The first is called "Table". Table is supposed to be a location to the table of IDs we made earlier, replace 0x8750000 with your table location. Tsize is supposed to be the amount of Pokemon your table has in it, adjust that accordingly as well.

Finally, the routine is flag toggled. If flag 0x205 is set, the opponent is generated a random party. To adjust this change these lines accordingly:

	mov r0, #0xFF
	lsl r0, r0, #0x1 @0xFF * 2
	add r0, r0, #0x7 @ 0x1FE + 7

Once the adjustments are complete, compile and insert into free space.

Spoiler:

.text
.align 2
.thumb
.thumb_func

@Hook 080112F8 via r0

main:
	push {r0-r7}
	@flag check 205
	mov r0, #0xFF
	lsl r0, r0, #0x1
	add r0, r0, #0x7
	ldr r4, =(0x806E6D0 +1)
	bl linker
	cmp r0, #0x0
	beq end
	
genAmount:
	ldr r4, =(0x8044EC8 +1)@gen random number
	bl linker
	lsl r0, r0, #0x10
	lsr r0, r0, #0x10
	mov r1, #0x6
	ldr r4, =(0x81E4684 +1)
	bl linker
	add r0, r0, #0x1
	mov r5, r0
	
mallocSpace:
	mov r0, #0x64
	mul r0, r0, r5
	ldr r4, =(0x8002BB0 +1) @malloc
	bl linker
	mov r6, r0
	mov r7, #0x0
	
@R5 = amount of mons
@R6 = free space to put them

genLoop:
	cmp r7, r5
	beq moveParty
	
genSpeciesFromTable:
	ldr r4, =(0x8044EC8 +1)@gen random number
	bl linker
	lsl r0, r0, #0x10
	lsr r0, r0, #0x10
	ldr r1, Tsize
	ldr r4, =(0x81E4684 +1)
	bl linker
	lsl r0, r0, #0x1
	ldr r1, Table
	add r1, r1, r0
	ldrh r1, [r1]
	
createMon:
	mov r0, #0x64
	mul r0, r0, r7
	add r0, r0, r6 @free memory
	ldr r2, =(0x20370BA)
	mov r2, #0x32 @level
	mov r3, #0x20 @cnst
	ldr r4, =(0x803DA54 +1)
	bl linker
	add r7, r7, #0x1
	b genLoop
	
moveParty:
	ldr r0, =(0x202402C)
	mov r1, r6
	mov r2, #0x64
	mul r2, r2, r5
	ldr r4, =(0x8040B08 +1) @func
	bl linker
	mov r0, r6
	ldr r4, =(0x8002BC4 +1) @free malloc'd memory
	bl linker
	pop {r0-r7}
	ldr r3, =(0x80116AC +1)
	bx r3
	
end:
	pop {r0-r7}
	ldr r0, =(0x400)
	cmp r1, r0
	bne place
	mov r0, #0x0
	ldr r3, =(0x80116AC +1)
	bx r3
	
place:
	ldr r3, =(0x8011304 +1)
	bx r3
	
linker:
	bx r4

.align 2

Table:
	.word 0x8750000 @your table of Mons
	
Tsize:
	.word 0x32 @Amount of entries in table

Finally, in a hex editor insert the following byte changes at 0x112F8:

00 48 00 47 XX XX XX 08

Where XX XX XX is the place you inserted the routine +1. Note that the trailing 08 may change depending on where you placed the routine.


Usage:

The routine is flag toggled. Set flag 0x205 before entering battle, and the rest is done automatically.

 

[Blah]

I'll confirm this second bug. Also, if you want, I can record a video of me making the TM move magically disappear. HAHAHAHA

EDIT: Second bug not confirmed!
When I noticed this, I used it in my Abra, which only had Teleport. Then it was gone after I used it in my Ekans, which had 4 moves learned.
But now, I used in an Ekans with 4 moves learned first, and I kept the TM. Then I used in my Abra, which had only one, and then the TM disappeared.
So, 4 moves learned bug is not my problem, so it seems.

Try the fix I posted for the 4 move bug. I'm pretty sure it's the same fix for both problems.

 

[Xencleamas]

Set static party level

Is it just me OR and the opponent/AI as well?

 

[azurile13]

Frontier Routines - Opponent Party generation

I've been meaning to implement a frontier of sorts into FireRed for some time but never really got a good opportunity to do so. Today I got a little bored and decided that I might as well start up. The first problem is obviously to generate a pseudo random party for the opposing trainer. That's what I've done today!

I had made a generation routine in the past as well, but it was incomplete and a little buggy. This one, as far as I can tell in my tests, should work fine :)


Setting up some prerequisites:
When making the routine for Pokemon generation, it was important that the hacker had some customization about which Pokemon were allowed into the opponents party (to prevent legendary Pokemon, or some specific Pokemon into the competition). The best way to do that is to either make a table of the Pokemon allowed to be in the opponent's party, or a table of the Pokemon not allowed to be in it. I decided to make the hacker do a table of all the Pokemon species allowed to be in the opponent's party.

It's important to remember that Pokemon Species ID takes 2 bytes per species, and that each entry in the table is in reverse hex. Bulbasaur for example would be: "01 00" in the table. The size of the table is up to you. The biggest reason I made the table be a table of all the Pokemon allowed is because this allows you to put more than 1 entry of the same Pokemon (thus increasing it's likelihood to be selected) ==> not all Pokemon species have the same chance of being selected!

Find some half-word aligned free space (offset divisible by 2) and fill up your table with as many entries as you'd like in this format:

[2 bytes (ID)] [2 bytes (ID)] ...

Write down how many entries you have, and where the start of the table is.


How to insert:

First take a look at the routine in the spoiler. Scroll to the very bottom, and you will see two fields which need filling. The first is called "Table". Table is supposed to be a location to the table of IDs we made earlier, replace 0x8750000 with your table location. Tsize is supposed to be the amount of Pokemon your table has in it, adjust that accordingly as well.

Finally, the routine is flag toggled. If flag 0x205 is set, the opponent is generated a random party. To adjust this change these lines accordingly:

	mov r0, #0xFF
	lsl r0, r0, #0x1 @0xFF * 2
	add r0, r0, #0x7 @ 0x1FE + 7

Once the adjustments are complete, compile and insert into free space.

Spoiler:

.text
.align 2
.thumb
.thumb_func

@Hook 080112F8 via r0

main:
	push {r0-r7}
	@flag check 205
	mov r0, #0xFF
	lsl r0, r0, #0x1
	add r0, r0, #0x7
	ldr r4, =(0x806E6D0 +1)
	bl linker
	cmp r0, #0x0
	beq end
	
genAmount:
	ldr r4, =(0x8044EC8 +1)@gen random number
	bl linker
	lsl r0, r0, #0x10
	lsr r0, r0, #0x10
	mov r1, #0x6
	ldr r4, =(0x81E4684 +1)
	bl linker
	add r0, r0, #0x1
	mov r5, r0
	
mallocSpace:
	mov r0, #0x64
	mul r0, r0, r5
	ldr r4, =(0x8002BB0 +1) @malloc
	bl linker
	mov r6, r0
	mov r7, #0x0
	
@R5 = amount of mons
@R6 = free space to put them

genLoop:
	cmp r7, r5
	beq moveParty
	
genSpeciesFromTable:
	ldr r4, =(0x8044EC8 +1)@gen random number
	bl linker
	lsl r0, r0, #0x10
	lsr r0, r0, #0x10
	ldr r1, Tsize
	ldr r4, =(0x81E4684 +1)
	bl linker
	lsl r0, r0, #0x1
	ldr r1, Table
	add r1, r1, r0
	ldrh r1, [r1]
	
createMon:
	mov r0, #0x64
	mul r0, r0, r7
	add r0, r0, r6 @free memory
	ldr r2, =(0x20370BA)
	mov r2, #0x32 @level
	mov r3, #0x20 @cnst
	ldr r4, =(0x803DA54 +1)
	bl linker
	add r7, r7, #0x1
	b genLoop
	
moveParty:
	ldr r0, =(0x202402C)
	mov r1, r6
	mov r2, #0x64
	mul r2, r2, r5
	ldr r4, =(0x8040B08 +1) @func
	bl linker
	mov r0, r6
	ldr r4, =(0x8002BC4 +1) @free malloc'd memory
	bl linker
	pop {r0-r7}
	ldr r3, =(0x80116AC +1)
	bx r3
	
end:
	pop {r0-r7}
	ldr r0, =(0x400)
	cmp r1, r0
	bne place
	mov r0, #0x0
	ldr r3, =(0x80116AC +1)
	bx r3
	
place:
	ldr r3, =(0x8011304 +1)
	bx r3
	
linker:
	bx r4

.align 2

Table:
	.word 0x8750000 @your table of Mons
	
Tsize:
	.word 0x32 @Amount of entries in table

Finally, in a hex editor insert the following byte changes at 0x112F8:

00 48 00 47 XX XX XX 08

Where XX XX XX is the place you inserted the routine +1. Note that the trailing 08 may change depending on where you placed the routine.


Usage:

The routine is flag toggled. Set flag 0x205 before entering battle, and the rest is done automatically.

This is quite a useful routine. Are there any issues you imagine arising from extending the entries to include custom movesets, held items, ev/iv etc?

 

[FamiliaWerneck]

Try the fix I posted for the 4 move bug. I'm pretty sure it's the same fix for both problems.

It seemed to work. I'll report back if I find anything else.
Bro, please update your Reusable TM post with this information.
Not for me, I already have it working. For other people not to stumble in the same issue.
Thanks for the help!

 

[esperance]

It seemed to work. I'll report back if I find anything else.
Bro, please update your Reusable TM post with this information.
Not for me, I already have it working. For other people not to stumble in the same issue.
Thanks for the help!

Don't worry, they're both linked in the first post. :3

 

[GoGoJJTech]

I don't really feel like doing a challenge cup. Also some of your features can be achieved using the already created party checker routine. Species Clause, Evasion Clause, OHKO clause can all be done by it. Maybe if I feel like it in future :P

Custom nicknames for enemy Pokemon

So this works for any wild or trainer Pokemon. It basically allows you to nickname a Pokemon on the enemy team prior to battling. For those special trainers or maybe special Pokemon :)

How to insert:

There's actually a little bit of work before you can compile and insert routines. First look at the routine below. You'll notice at the last line there is a Pointer to something that I call "TABLE". This table is going to be a table full of nickname with each entry 0xB bytes long. Find some space in your ROM which you will use for this table and correct the offset accordingly.

Spoiler:

.text
.align 2
.thumb
.thumb_func

main:
	mov r0, #0x9C
	lsl r0, #0x2
	push {r1-r7}
    	ldr r2, =(0x806E6D0 +1)
	bl linker
	pop {r1-r7}
	cmp r0, #0x0
	beq old

nick:
	ldr r0, =(0x202402C)
	sub r0, r7, r0
	mov r1, #0x64
	ldr r2, =(0x81E4018 +1) @slot number
	bl linker
	mov r3, r0
	ldr r1, = (0x20370B8) @table entry position
	ldrb r1, [r1]
	mov r2, #0xB
	mul r1, r1, r2
	ldr r0, .TABLE
	add r0, r0, r1 @table start position
	mul r3, r3, r2
	add r0, r0, r3 @name to give
	mov r1, r7
	add r1, r1, #0x8 @nickname location
	mov r4, #0x0

nameLoop:
	cmp r4, #0xB
	beq end
	ldrb r3, [r0]
	strb r3, [r1]
	add r1, r1, #0x1
	add r0, r0, #0x1
	add r4, r4, #0x1
	b nameLoop

end:
	ldr r0, =(0x8040ADA +1)
	bx r0

old:
	mov r2, #0x0
	mov r3, r7
	add r3, #0x8

oldLoop:
	add r0, r3, r2
	add r1, r4, r2
	ldrb r1, [r1]
	strb r1, [r0]
	add r2, r2, #0x1
	cmp r2, #0x9
	ble oldLoop
	ldr r0, =(0x8040ADA +1)
	bx r0

linker:
	bx r2

.align 2

[B].TABLE:
	.word 0x8760000[/B]

Once you've made the modification to the pointer, compile and insert the routine into freespace.
Next navigate to offset 0x406DC and insert the following:

00 48 00 47 XX XX XX 08

Where XX is the pointer to the above routine in reverse hex +1.

Usage:
First navigate to your table which will contain the nicknames (it should be the offset in the routine you changed). You need to keep the table formatted like this [10 bytes (Name in hex)] [1 byte (0xFF)]. Insert as many names as you'd like.

Next, to activate the routine, you must setflag 0x270 AND you need to setvar 0x8000 0x[table starting index].
If you're battling a trainer with 6 Pokemon, the nicknames will be determined from the table. It will read six nicknames starting from the starting index given by variable 0x8000. There is no need to callasm. :)

Danny told me to find this for Emerald, and so I did. 0x406DC is for Fire Red, 0x6AFA8 is for Emerald. I did not test this, but it should theoretically work. (Of course the offsets in the routine will have to be changed, I can start doing that but it's late and stuff)

EDIT: If you ever want me to find the Emerald offsets for you, I'd be glad to.
EDIT^2: Edited routine for Emerald (Changes in Red)

Spoiler:

.text
.align 2
.thumb
.thumb_func

main:
	mov r0, #0x9C [COLOR="DarkOrchid"][B]@0x9C * 4 (which is what the next line does) = 0x270. Change this for the flag since it's most likely not free in Emerald[/B][/COLOR]
	lsl r0, #0x2
	push {r1-r7}
    	[COLOR="Red"]ldr r2, =(0x809D790 +1) @Flag Check[/COLOR]
	bl linker
	pop {r1-r7}
	cmp r0, #0x0
	beq old

nick:
	[COLOR="Red"]ldr r0, =(0x2024744) @Opponent RAM location[/COLOR]
	sub r0, r7, r0
	mov r1, #0x64
	[COLOR="red"]ldr r2, =(0x82E7540 +1) @slot number[/COLOR]
	bl linker
	mov r3, r0
	[COLOR="red"]ldr r1, = (0x20375D8) @table entry position[/COLOR]
	ldrb r1, [r1]
	mov r2, #0xB
	mul r1, r1, r2
	ldr r0, .TABLE
	add r0, r0, r1 @table start position
	mul r3, r3, r2
	add r0, r0, r3 @name to give
	mov r1, r7
	add r1, r1, #0x8 @nickname location
	mov r4, #0x0

nameLoop:
	cmp r4, #0xB
	beq end
	ldrb r3, [r0]
	strb r3, [r1]
	add r1, r1, #0x1
	add r0, r0, #0x1
	add r4, r4, #0x1
	b nameLoop

end:
	[COLOR="red"]ldr r0, =(0x806B3D8 +1)[/COLOR]
	bx r0

old:
	mov r2, #0x0
	mov r3, r7
	add r3, #0x8

oldLoop:
	add r0, r3, r2
	add r1, r4, r2
	ldrb r1, [r1]
	strb r1, [r0]
	add r2, r2, #0x1
	cmp r2, #0x9
	ble oldLoop
	[COLOR="red"]ldr r0, =(0x806B3D8 +1)[/COLOR]
	bx r0

linker:
	bx r2

.align 2

[B].TABLE:
	.word 0x8760000[/B]

 

[Blah]

Is it just me OR and the opponent/AI as well?

Just your party.

This is quite a useful routine. Are there any issues you imagine arising from extending the entries to include custom movesets, held items, ev/iv etc?

Yeah that's not too hard, but I think you'd prefer to make your own trainer if you'd have something memorable like custom items and movesets no? It would mean more tables, and more work for the inserter. So much to the point that it wouldn't really be worth the effort, kind of like having 100 TMs.

Don't worry, they're both linked in the first post. :3

Thanks I was too lazy to edit my post anyways!

Danny told me to find this for Emerald, and so I did. 0x406DC is for Fire Red, 0x6AFA8 is for Emerald. I did not test this, but it should theoretically work. (Of course the offsets in the routine will have to be changed, I can start doing that but it's late and stuff)

EDIT: If you ever want me to find the Emerald offsets for you, I'd be glad to.

My old routines make my eyes bleed my eyes X_X
Someone who's keen can go back and make efficiency changes to some of these. A brave and unlazy soul!