You've already forked pokecrystal-board
mirror of
https://gitlab.com/xCrystal/pokecrystal-board.git
synced 2025-04-09 05:44:44 -07:00
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.
This commit is contained in:
@@ -178,15 +178,15 @@ ENDM
|
||||
battle_tower_struct: MACRO
|
||||
\1Name:: ds NAME_LENGTH +- 1
|
||||
\1TrainerClass:: ds 1
|
||||
\1Pkmn1:: party_struct \1Pkmn1
|
||||
\1Pkmn1Name:: ds MON_NAME_LENGTH
|
||||
\1Pkmn1NameEnd::
|
||||
\1Pkmn2:: party_struct \1Pkmn2
|
||||
\1Pkmn2Name:: ds MON_NAME_LENGTH
|
||||
\1Pkmn2NameEnd::
|
||||
\1Pkmn3:: party_struct \1Pkmn3
|
||||
\1Pkmn3Name:: ds MON_NAME_LENGTH
|
||||
\1Pkmn3NameEnd::
|
||||
\1Mon1:: party_struct \1Mon1
|
||||
\1Mon1Name:: ds MON_NAME_LENGTH
|
||||
\1Mon1NameEnd::
|
||||
\1Mon2:: party_struct \1Mon2
|
||||
\1Mon2Name:: ds MON_NAME_LENGTH
|
||||
\1Mon2NameEnd::
|
||||
\1Mon3:: party_struct \1Mon3
|
||||
\1Mon3Name:: ds MON_NAME_LENGTH
|
||||
\1Mon3NameEnd::
|
||||
\1TrainerData:: ds BATTLETOWER_TRAINERDATALENGTH
|
||||
\1TrainerEnd::
|
||||
ENDM
|
||||
|
Reference in New Issue
Block a user