Use constants for move struct positioning.

This eliminates the need for arbitrary move labels like Move2 and Move1 that don't have anything to do with their respective moves.
2014-06-10 23:23:55 -07:00
parent 86c1e0feea
commit 23f9b5d21e
7 changed files with 29 additions and 34 deletions
--- a/text/types.asm
+++ b/text/types.asm
@@ -42,13 +42,13 @@ PrintMoveType: ; 5093a
 	push hl
 	ld a, b
 	dec a
-	ld bc, Move2 - Move1
+	ld bc, MOVE_LENGTH
 	ld hl, Moves
 	call AddNTimes
 	ld de, StringBuffer1
 	ld a, BANK(Moves)
 	call FarCopyBytes
-	ld a, [StringBuffer1 + PlayerMoveType - PlayerMoveStruct]
+	ld a, [StringBuffer1 + MOVE_TYPE]
 	pop hl

 	ld b, a