pokecrystal-board/data/maps/spawn_points.asm

MACRO spawn
; map, x, y
	map_id \1
	db \2, \3
ENDM

SpawnPoints:
; entries correspond to SPAWN_* constants (see constants/map_data_constants.asm)
	table_width 4, SpawnPoints

	spawn LEVEL_1_MAP_1,               3,  3  ; SPAWN_LEVEL_1
;	spawn LEVEL_2_MAP_1,               5,  3  ; SPAWN_LEVEL_2
if DEF(_DEBUG)
	spawn DEBUGLEVEL_1_MAP_1,          3,  3, ; SPAWN_DEBUGLEVEL_1
	spawn DEBUGLEVEL_2_MAP_1,          3,  3, ; SPAWN_DEBUGLEVEL_2
	spawn DEBUGLEVEL_3_MAP_1,          3,  3, ; SPAWN_DEBUGLEVEL_3
	spawn DEBUGLEVEL_4_MAP_1,          3,  3, ; SPAWN_DEBUGLEVEL_4
	spawn DEBUGLEVEL_5_MAP_1,          3,  3, ; SPAWN_DEBUGLEVEL_5
endc
	spawn N_A,                        -1, -1

	assert_table_length NUM_SPAWNS + 1
RGBDS syntax updates (#905) New MACRO and DEF syntax 2022-06-06 14:25:42 -07:00			`MACRO spawn`
Consistent (x, y) coordinate formatting in map scripts 2017-12-28 11:31:25 -08:00			`; map, x, y`
map → map_id; map_def → map; map_data → map_attributes 2018-02-03 13:58:49 -08:00			`map_id \1`
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 \2, \3`
			`ENDM`

Remove even more address comments That should be all of them this time 2018-06-24 17:10:37 -07:00			`SpawnPoints:`
Remove original maps and object events (#1) 2023-07-25 06:33:08 -07:00			`; entries correspond to SPAWN_* constants (see constants/map_data_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 4, SpawnPoints`
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
Remove original maps and object events (#1) 2023-07-25 06:33:08 -07:00			`spawn LEVEL_1_MAP_1, 3, 3 ; SPAWN_LEVEL_1`
			`; spawn LEVEL_2_MAP_1, 5, 3 ; SPAWN_LEVEL_2`
Organize debug-only structures for test maps and levels (#16) 2023-09-02 15:22:23 -07:00			`if DEF(_DEBUG)`
			`spawn DEBUGLEVEL_1_MAP_1, 3, 3, ; SPAWN_DEBUGLEVEL_1`
Add debug maps for testing 2023-10-02 07:11:52 -07:00			`spawn DEBUGLEVEL_2_MAP_1, 3, 3, ; SPAWN_DEBUGLEVEL_2`
			`spawn DEBUGLEVEL_3_MAP_1, 3, 3, ; SPAWN_DEBUGLEVEL_3`
			`spawn DEBUGLEVEL_4_MAP_1, 3, 3, ; SPAWN_DEBUGLEVEL_4`
			`spawn DEBUGLEVEL_5_MAP_1, 3, 3, ; SPAWN_DEBUGLEVEL_5`
Organize debug-only structures for test maps and levels (#16) 2023-09-02 15:22:23 -07:00			`endc`
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			`spawn N_A, -1, -1`
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_SPAWNS + 1`