From 2a4a056426efcedbc90a5d312fcbc531a616bc99 Mon Sep 17 00:00:00 2001
From: Zach Day <zachdayz@gmail.com>
Date: Wed, 19 Jun 2024 16:28:58 -0400
Subject: [PATCH] Fix explosive moves used by a mon with Damp not getting
 suppressed

---
 src/phases.ts | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/src/phases.ts b/src/phases.ts
index 55619a5c869..9a711bdafc7 100644
--- a/src/phases.ts
+++ b/src/phases.ts
@@ -3050,9 +3050,7 @@ export class MoveEffectPhase extends PokemonPhase {
 
       // Check if other Pokemon on the field have an ability that prevents this move
       const prevented = new Utils.BooleanHolder(false);
-      for (const other of this.scene.getField(true).filter(p => user.id !== p.id)) {
-        applyAbAttrs(FieldPreventMovesAbAttr, other, prevented, move, user as Pokemon);
-      }
+      this.scene.getField(true).forEach(p => applyAbAttrs(FieldPreventMovesAbAttr, p, prevented, move, user));
       if (prevented.value) {
         // Just bail out of the move if it got prevented. No need to manually show message; the Attr handles that.
         moveHistoryEntry.result = MoveResult.FAIL;