From 5b53aff5b7ddb21eda5ebd5cedbd1b96aefc0877 Mon Sep 17 00:00:00 2001
From: NightKev <34855794+DayKev@users.noreply.github.com>
Date: Sun, 8 Sep 2024 19:16:32 -0700
Subject: [PATCH] Remove impossible `if` statement

---
 src/data/move.ts | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/src/data/move.ts b/src/data/move.ts
index cfd75591f93..369a0ae0dcd 100644
--- a/src/data/move.ts
+++ b/src/data/move.ts
@@ -2005,9 +2005,7 @@ export class PsychoShiftEffectAttr extends MoveEffectAttr {
 
     if (target.status) {
       return false;
-    }
-    //@ts-ignore - how can target.status.effect be checked when we return `false` before when it's defined?
-    if (!target.status || (target.status.effect === statusToApply && move.chance < 0)) { // TODO: resolve ts-ignore
+    } else {
       const canSetStatus = target.canSetStatus(statusToApply, true, false, user);
 
       if (canSetStatus) {
@@ -2021,8 +2019,6 @@ export class PsychoShiftEffectAttr extends MoveEffectAttr {
 
       return canSetStatus;
     }
-
-    return false;
   }
 
   getTargetBenefitScore(user: Pokemon, target: Pokemon, move: Move): number {