Fixed casing in comment on "dual non-immunity" glitch
This commit is contained in:
parent
3122d744f5
commit
5ddf3e2ee5
1 changed files with 2 additions and 2 deletions
|
@ -1484,7 +1484,7 @@ static void Cmd_get_highest_type_effectiveness(void)
|
|||
|
||||
if (gCurrentMove != MOVE_NONE)
|
||||
{
|
||||
// TypeCalc does not assign to gMoveResultFlags, Cmd_TypeCalc does
|
||||
// TypeCalc does not assign to gMoveResultFlags, Cmd_typecalc does
|
||||
// This makes the check for gMoveResultFlags below always fail
|
||||
#ifdef BUGFIX
|
||||
gMoveResultFlags = TypeCalc(gCurrentMove, sBattler_AI, gBattlerTarget);
|
||||
|
@ -1525,7 +1525,7 @@ static void Cmd_if_type_effectiveness(void)
|
|||
gBattleMoveDamage = AI_EFFECTIVENESS_x1;
|
||||
gCurrentMove = AI_THINKING_STRUCT->moveConsidered;
|
||||
|
||||
// TypeCalc does not assign to gMoveResultFlags, Cmd_TypeCalc does
|
||||
// TypeCalc does not assign to gMoveResultFlags, Cmd_typecalc does
|
||||
// This makes the check for gMoveResultFlags below always fail
|
||||
// This is how you get the "dual non-immunity" glitch, where AI
|
||||
// will use ineffective moves on immune pokémon if the second type
|
||||
|
|
Loading…
Reference in a new issue