pokecrystal-board/data/moves/tmhm_moves.asm

; The add_tm, add_hm, and add_mt macros in constants/item_constants.asm simultaneously
; define constants for the item IDs and for the corresponding move values.

TMHMMoves:
; entries correspond to *_TMNUM constants (see constants/item_constants.asm)
	table_width 1, TMHMMoves

; TMs
for n, 1, NUM_TMS + 1
	db TM{02d:n}_MOVE
endr
	assert_table_length NUM_TMS

; HMs
for n, 1, NUM_HMS + 1
	db HM{02d:n}_MOVE
endr
	assert_table_length NUM_TMS + NUM_HMS

; Move tutors
n = 1
for n, 1, NUM_TUTORS + 1
	db MT{02d:n}_MOVE
endr
	assert_table_length NUM_TM_HM_TUTOR

	db 0 ; end
add_tm, add_hm, and add_mt define TM##_MOVE, HM##_MOVE, and MT##_MOVE constants, to avoid repeating the move names in tmhm_moves.asm 2020-07-06 13:53:05 -07:00			`; The add_tm, add_hm, and add_mt macros in constants/item_constants.asm simultaneously`
			`; define constants for the item IDs and for the corresponding move values.`

Remove all address comments 2018-06-24 07:09:41 -07:00			`TMHMMoves:`
Eliminate enum: use const instead, with case-by-case parallel const implementations 2020-07-08 12:30:23 -07:00			`; entries correspond to *_TMNUM constants (see constants/item_constants.asm)`
Verify data table sizes with table_width and assert_table_length macros This was discussed in #706 It also uncovered some off-by-one issues with defining some constants. A few structs now use rsreset/_RS to define their offset constants, as discussed in #739 2021-03-03 19:22:41 -08:00			`table_width 1, TMHMMoves`
add_tm, add_hm, and add_mt define TM##_MOVE, HM##_MOVE, and MT##_MOVE constants, to avoid repeating the move names in tmhm_moves.asm 2020-07-06 13:53:05 -07:00
Move lots of data tables into individual data/ files (This is not expected to be their final location, but it makes them easier to relocate when necessary, and easier for users to edit until the whole project's file structure is finalized.) 2017-12-11 10:47:58 -08:00			`; TMs`
Use rgbds 0.5.0 2021-04-19 13:31:37 -07:00			`for n, 1, NUM_TMS + 1`
			`db TM{02d:n}_MOVE`
add_tm, add_hm, and add_mt define TM##_MOVE, HM##_MOVE, and MT##_MOVE constants, to avoid repeating the move names in tmhm_moves.asm 2020-07-06 13:53:05 -07:00			`endr`
Miscellaneous cleanup 2021-03-22 13:41:17 -07:00			`assert_table_length NUM_TMS`
add_tm, add_hm, and add_mt define TM##_MOVE, HM##_MOVE, and MT##_MOVE constants, to avoid repeating the move names in tmhm_moves.asm 2020-07-06 13:53:05 -07:00
Move lots of data tables into individual data/ files (This is not expected to be their final location, but it makes them easier to relocate when necessary, and easier for users to edit until the whole project's file structure is finalized.) 2017-12-11 10:47:58 -08:00			`; HMs`
Use rgbds 0.5.0 2021-04-19 13:31:37 -07:00			`for n, 1, NUM_HMS + 1`
			`db HM{02d:n}_MOVE`
add_tm, add_hm, and add_mt define TM##_MOVE, HM##_MOVE, and MT##_MOVE constants, to avoid repeating the move names in tmhm_moves.asm 2020-07-06 13:53:05 -07:00			`endr`
Miscellaneous cleanup 2021-03-22 13:41:17 -07:00			`assert_table_length NUM_TMS + NUM_HMS`
add_tm, add_hm, and add_mt define TM##_MOVE, HM##_MOVE, and MT##_MOVE constants, to avoid repeating the move names in tmhm_moves.asm 2020-07-06 13:53:05 -07:00
Use rgbds 0.5.0 2021-04-19 13:31:37 -07:00			`; Move tutors`
add_tm, add_hm, and add_mt define TM##_MOVE, HM##_MOVE, and MT##_MOVE constants, to avoid repeating the move names in tmhm_moves.asm 2020-07-06 13:53:05 -07:00			`n = 1`
Use rgbds 0.5.0 2021-04-19 13:31:37 -07:00			`for n, 1, NUM_TUTORS + 1`
			`db MT{02d:n}_MOVE`
add_tm, add_hm, and add_mt define TM##_MOVE, HM##_MOVE, and MT##_MOVE constants, to avoid repeating the move names in tmhm_moves.asm 2020-07-06 13:53:05 -07:00			`endr`
Verify data table sizes with table_width and assert_table_length macros This was discussed in #706 It also uncovered some off-by-one issues with defining some constants. A few structs now use rsreset/_RS to define their offset constants, as discussed in #739 2021-03-03 19:22:41 -08:00			`assert_table_length NUM_TM_HM_TUTOR`

Move lots of data tables into individual data/ files (This is not expected to be their final location, but it makes them easier to relocate when necessary, and easier for users to edit until the whole project's file structure is finalized.) 2017-12-11 10:47:58 -08:00			`db 0 ; end`