Future/pokecrystal
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Use constants for move struct positioning.

Browse Source 
This eliminates the need for arbitrary move labels like Move2 and Move1 that don't have anything to do with their respective moves.
This commit is contained in:
yenatch
2014-06-10 23:23:55 -07:00
parent 86c1e0feea
commit 23f9b5d21e
7 changed files with 29 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
battle/core.asm
View File

@@ -915,7 +915,7 @@ GetMoveEffect: ; 3c5ec
ld a, b
dec a
ld hl, Moves + MOVE_EFFECT
ld bc, Move2 - Move1
ld bc, MOVE_LENGTH
call AddNTimes
ld a, BANK(Moves)
call GetFarByte
@@ -3436,7 +3436,7 @@ Function3d5d7: ; 3d5d7
push bc
dec a
ld hl, Moves + MOVE_ANIM
ld bc, Move2 - Move1
ld bc, MOVE_LENGTH
call AddNTimes
ld de, EnemyMoveAnimation
ld a, BANK(Moves)
@@ -8580,7 +8580,7 @@ Function3f662: ; 3f662
push hl
dec a
ld hl, Moves + MOVE_PP
ld bc, Move2 - Move1
ld bc, MOVE_LENGTH
call AddNTimes
ld a, BANK(Moves)
call GetFarByte