From 29dbdce850f232a23cdc3024dc558bd0d8a2881a Mon Sep 17 00:00:00 2001
From: WillKolada <57021938+WillKolada@users.noreply.github.com>
Date: Tue, 7 May 2024 17:25:18 -0500
Subject: [PATCH] Update battle_dynamax.c

IsMoveBlockedByDynamax now simply returns the move's "doesntAffectDynamax" flag.
---
 src/battle_dynamax.c | 8 +-------
 1 file changed, 1 insertion(+), 7 deletions(-)

diff --git a/src/battle_dynamax.c b/src/battle_dynamax.c
index 7286045684..2e4397d276 100644
--- a/src/battle_dynamax.c
+++ b/src/battle_dynamax.c
@@ -241,13 +241,7 @@ bool32 IsMoveBlockedByMaxGuard(u16 move)
 bool32 IsMoveBlockedByDynamax(u16 move)
 {
     // TODO: Certain moves are banned in raids.
-    switch (gMovesInfo[move].effect)
-    {
-        case EFFECT_HEAT_CRASH:
-        case EFFECT_LOW_KICK:
-            return TRUE;
-    }
-    return FALSE;
+    return gMovesInfo[move].doesntAffectDynamax;
 }
 
 // Returns whether a move should be converted into a Max Move.