From 1d4a9259b83441c358a6ca591afb282a2e7c88ca Mon Sep 17 00:00:00 2001
From: Dean <69436131+emdeann@users.noreply.github.com>
Date: Thu, 30 Oct 2025 20:14:48 -0700
Subject: [PATCH] [Hotfix] Fix Queenly Majesty/Dazzling affecting user's moves
 instead of enemy's (#6722)

Fix QM/Dazzling
---
 src/phases/move-phase.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/phases/move-phase.ts b/src/phases/move-phase.ts
index 6350791e9bb..5115e3da595 100644
--- a/src/phases/move-phase.ts
+++ b/src/phases/move-phase.ts
@@ -286,7 +286,7 @@ export class MovePhase extends PokemonPhase {
 
     // Apply queenly majesty / dazzling
     if (!failed) {
-      const defendingSidePlayField = user.isPlayer() ? globalScene.getPlayerField() : globalScene.getEnemyField();
+      const defendingSidePlayField = user.isPlayer() ? globalScene.getEnemyField() : globalScene.getPlayerField();
       const cancelled = new BooleanHolder(false);
       defendingSidePlayField.forEach((pokemon: Pokemon) => {
         applyAbAttrs("FieldPriorityMoveImmunityAbAttr", {