data/radio/oaks_pkmn_talk_routes.asm

; Oak's Pokémon Talk will list wild Pokémon on these maps.

OaksPKMNTalkRoutes:
	map_id ROUTE_29
	map_id ROUTE_46
	map_id ROUTE_30
	map_id ROUTE_32
	map_id ROUTE_34
	map_id ROUTE_35
	map_id ROUTE_37
	map_id ROUTE_38
	map_id ROUTE_39
	map_id ROUTE_42
	map_id ROUTE_43
	map_id ROUTE_44
	map_id ROUTE_45
	map_id ROUTE_36
	map_id ROUTE_31
.End
Move radio channel data into data/ 2018-01-10 11:30:12 -05:00			`; Oak's Pokémon Talk will list wild Pokémon on these maps.`

Pkmn -> Mon Since we're aiming for consistency across the codebase, I believe it includes a uniform way to refer to the creatures this game consists of in the labels of the code. The only exceptions to this rule are labels referring to things named through the use of the <PK><MN> or <PKMN> characters, in which case PKMN is used. Most of this was already consistent enough™, I just picked the convention with the most occurences and fixed the outliers. 2018-02-22 17:13:29 +01:00			`OaksPKMNTalkRoutes:`
map → map_id; map_def → map; map_data → map_attributes 2018-02-03 16:58:49 -05:00			`map_id ROUTE_29`
			`map_id ROUTE_46`
			`map_id ROUTE_30`
			`map_id ROUTE_32`
			`map_id ROUTE_34`
			`map_id ROUTE_35`
			`map_id ROUTE_37`
			`map_id ROUTE_38`
			`map_id ROUTE_39`
			`map_id ROUTE_42`
			`map_id ROUTE_43`
			`map_id ROUTE_44`
			`map_id ROUTE_45`
			`map_id ROUTE_36`
			`map_id ROUTE_31`
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 22:22:41 -05:00			`.End`