5 Commits

Author	SHA1	Message	Date
Remy Oukaour	720cdc72b2	Comments distinguish "move effects" and "effect commands" ... Effect command enums are used like constants, not macros	2017-12-11 17:41:18 -05:00
mid-kid	fd14253796	Clean up labels in battle/moves/move_effects.asm ... There were a lot of unused labels in there, and a few confusing misnomers around move_effects_pointers.asm. They now match up exactly with the names in battle_constants.asm. Also renamed a few effects, to make their purpose clearer, and to match up with their respective event script commands: EFFECT_EXPLOSION -> EFFECT_SELFDESCTRUCT EFFECT_HAZE -> EFFECT_RESET_STATS EFFECT_WHIRLWIND -> EFFECT_FORCE_SWITCH EFFECT_BIND -> EFFECT_TRAP_TARGET EFFECT_TWINEEDLE -> EFFECT_POISON_MULTI_HIT EFFECT_STEEL_WING -> EFFECT_DEFENSE_UP_HIT EFFECT_METAL_CLAW -> EFFECT_ATTACK_UP_HIT EFFECT_ANCIENTPOWER -> EFFECT_ALL_UP_HIT	2017-11-15 16:36:13 +01:00
IIMarckus	4d532beee6	Remove trailing newlines.	2015-06-23 12:24:51 -06:00
yenatch	f36dfc3689	Move-specific effect pointers	2013-04-01 00:53:18 -04:00
yenatch	b998f4594c	Move effect pointers	2013-03-31 21:39:12 -04:00