summaryrefslogtreecommitdiff
path: root/src/contest_ai.c
diff options
context:
space:
mode:
authorGriffinR <griffin.g.richards@gmail.com>2021-09-23 21:49:49 -0400
committerGitHub <noreply@github.com>2021-09-23 21:49:49 -0400
commit9d0f9042febd46d506110778a3beeec90c8c9c1e (patch)
treec3bf2f4b0b3183de111bfcc89fac3316f562c937 /src/contest_ai.c
parent0c2e9a5b4c1c0c0f2a62be6165e826760dd572cb (diff)
parenta6ab2eb883b4cef727a6caee993745cfeff1274b (diff)
Merge pull request #1498 from LOuroboros/trailingSpaces
Removed trailing spaces in the most relevant files
Diffstat (limited to 'src/contest_ai.c')
-rw-r--r--src/contest_ai.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/contest_ai.c b/src/contest_ai.c
index 8fe339790..7aeba828a 100644
--- a/src/contest_ai.c
+++ b/src/contest_ai.c
@@ -1732,7 +1732,7 @@ static void ContestAICmd_if_user_doesnt_have_exciting_move(void)
// BUG: This is checking if the user has a specific move, but when it's used in the AI script
// they're checking for an effect. Checking for a specific effect would make more sense,
-// but given that effects are normally read as a single byte and this reads 2 bytes, it
+// but given that effects are normally read as a single byte and this reads 2 bytes, it
// seems reading a move was intended and the AI script is using it incorrectly.
// The fix below aligns the function with how it's used by the script, rather than the apparent
// intention of its usage
@@ -1750,7 +1750,7 @@ static void ContestAICmd_check_user_has_move(void)
#else
u16 move = gContestMons[eContestAI.contestantId].moves[i];
#endif
-
+
if (move == targetMove)
{
hasMove = TRUE;