summaryrefslogtreecommitdiff
path: root/constants/type_constants.asm
AgeCommit message (Collapse)Author
2021-03-04Verify data table sizes with table_width and assert_table_length macrosRangi
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
2020-07-10Use const_skip and const_next macros for brevityRangi
2020-03-21Add suffixes to some constants to avoid ambiguityRangi
- `PSYCHIC` → `PSYCHIC_TYPE` (not the trainer `PSYCHIC_T` or the move `PSYCHIC_M`) - `BLACKBELT` → `BLACKBELT_I` (not the trainer `BLACKBELT_T`) - `CURSE_T` → `CURSE_TYPE` (not the move `CURSE`) - `TOWN_MAP_D` → `TOWN_MAP_POSTER` (not the item `TOWN_MAP`) This also uncovered a misidentified event: `EVENT_DECO_PLANT_4` → `EVENT_DECO_POSTER_1`. (There are three plants and four posters.)
2018-01-22Move type data to data/types/Rangi
2018-01-11More constants and data tablesRemy Oukaour
2017-12-26Split battle/ into data/ and engine/ componentsRemy Oukaour
2017-12-09Document constants with comments, actual names, and more thorough usageRemy Oukaour
2014-07-09Recomment type names.yenatch
This is mostly just whitespace reduction.
2014-06-13More battle code cleanup.yenatch
- Use more substatus constants. - Reformat some code to be more atomic. - Add constants for unused status prevention held item effects. - Remove pointless or redundant comments.
2014-01-05enumerate type constantsyenatch
2014-01-05move type constants into constants/type_constants.asmyenatch