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
This commit is contained in:
@@ -2,6 +2,8 @@ BattleTowerTrainers:
|
||||
; The trainer class is not used in Crystal 1.0 due to a bug.
|
||||
; Instead, the sixth character in the trainer's name is used.
|
||||
; See BattleTowerText in engine/events/battle_tower/trainer_text.asm.
|
||||
table_width (NAME_LENGTH - 1) + 1, BattleTowerTrainers
|
||||
; name, class
|
||||
db "HANSON@@@@", FISHER
|
||||
db "SAWYER@@@@", POKEMANIAC
|
||||
db "MASUDA@@@@", GUITARIST
|
||||
@@ -23,6 +25,7 @@ BattleTowerTrainers:
|
||||
db "KAUFMAN@@@", SWIMMERM
|
||||
db "LANCASTER@", SKIER
|
||||
db "McMAHILL@@", CAMPER
|
||||
assert_table_length BATTLETOWER_NUM_UNIQUE_MON
|
||||
; The following can only be sampled in Crystal 1.1.
|
||||
db "OBRIEN@@@@", GENTLEMAN
|
||||
db "FROST@@@@@", BEAUTY
|
||||
@@ -73,3 +76,4 @@ BattleTowerTrainers:
|
||||
db "DYKSTRA@@@", SWIMMERF
|
||||
db "EATON@@@@@", BIKER
|
||||
db "WONG@@@@@@", FIREBREATHER
|
||||
assert_table_length BATTLETOWER_NUM_UNIQUE_TRAINERS
|
||||
|
Reference in New Issue
Block a user