Palworld’s “Fraud Watch” Is Getting Real: Why Are Bellanoir and Other Pals Suddenly Refusing to Attack?
🚨 PALWORLD PLAYERS ARE CALLING FOUL — THEIR PALS ARE LITERALLY REFUSING TO FIGHT.
Bellanoir, raid teams, even normally reliable Pals can suddenly stand there and do NOTHING… and players are now asking the same terrifying question: Is this a cooldown issue, bad pathfinding, or a full-blown AI bug?
The strangest part? Some players say recalling and redeploying fixes it. Others say it keeps happening — even in the middle of raids. And when the timer is ticking, one frozen Pal can mean the entire fight is over.
So what’s actually causing your Pals to “quiet quit” combat?
🔥 Watch the evidence and see what players have discovered 👇
For a game built around commanding powerful creatures into battle, there may be nothing more frustrating than watching your carefully prepared Pal team simply… stop fighting.
That is exactly what some Palworld players say they have been experiencing in recent weeks, with reports of Pals freezing during combat, refusing to use Active Skills, losing their targets or standing motionless while bosses continue attacking.
The problem becomes especially serious during raid encounters, where a Pal that stops attacking is not merely an annoyance. It can cost an entire run.
Recent community reports have repeatedly pointed to Bellanoir fights as one of the places where the problem becomes most visible. Players have described raid teams suddenly becoming inactive, sometimes after initially fighting normally. Others say the behavior can also appear in regular combat, arenas and encounters with newer bosses.
And that has turned an amusing “my Pal is taking a break” moment into a much bigger question: Is Palworld’s combat AI malfunctioning?
The answer, based on current community evidence, appears to be more complicated than a simple cooldown problem.
The Bellanoir problem
Bellanoir is particularly important here because she is not an ordinary Pal.
The Dark-element Pal is a raid boss and is also obtainable by players after defeating the encounter. According to the current Palworld Wiki, Bellanoir has a base Attack stat of 150 and a combat-focused moveset that includes Dark Cannon, Umbral Surge, Dark Arrow, Spirit Flame, Nightmare Ball, Apocalypse and Nightmare Ray.
Her Partner Skill is Nightmare Iris, which allows Bellanoir to attack a targeted enemy with Nightmare Ray.
That makes her a particularly valuable combat Pal — and potentially a particularly painful victim when combat AI starts misbehaving.
In a Steam community discussion from July, players specifically reported Bellanoir sometimes refusing to use moves despite apparently having no cooldown issue. One player said Bellanoir had stopped using Nightmare Ray even after several minutes without combat. Another reported that recalling the Pal and throwing it back out could restore its behavior.
Those reports matter because they make a simple explanation — “the skill is on cooldown” — much less convincing in at least some cases.
It isn’t just Bellanoir
The bigger concern is that similar complaints have appeared across multiple Pals and different combat situations.
A Reddit discussion published in late July described Pals suddenly stopping their attacks during a boss raid. Players reported seeing their Pals stand still while the boss continued fighting. Some suspected navigation or pathfinding problems, while others said the issue could happen even when there were no obvious obstacles.
One particularly frustrating detail is that the problem does not always appear immediately.
According to players, a Pal can begin a fight normally and then become effectively useless later in the encounter.
That distinction is important.
If a Pal simply refuses to fight because the player has accidentally selected a passive or defensive combat command, the solution is relatively straightforward. But reports of Pals beginning combat normally and subsequently becoming unresponsive suggest that something deeper may sometimes be happening.
Another Reddit discussion from early August described Pals that would receive the combat indicator but still refuse to move or attack. The poster said the behavior occurred in raids and other boss encounters, while commenters described similar experiences in overworld combat.
The “it’s just cooldowns” theory doesn’t explain everything
Cooldowns are an obvious suspect.
Every Active Skill has a cooldown, and a Pal cannot simply spam its strongest ability continuously. Bellanoir, for example, has different cooldowns across her Active Skills, while Nightmare Ray is listed by the current wiki as a 50-second cooldown ability.
But players reporting this issue say the problem sometimes goes beyond waiting for a move to recharge.
The Steam discussion includes reports of Pals refusing to use attacks even when the players believed cooldowns were not the explanation. One player described a Pal simply staring at an enemy, while another said Bellanoir could stop using Nightmare Ray despite having been out of combat long enough that the cooldown should not have been the issue.
That has led some players to suspect an AI-state or targeting problem rather than ordinary combat timing.
And there is another clue.
Pathfinding may be part of the problem
Several community members have suggested that navigation and targeting are involved.
In one Reddit discussion, players theorized that Pals can become stuck because they cannot properly calculate a path to their target. If the Pal can see an enemy but its navigation system does not establish a usable route, the creature may effectively remain idle rather than attacking.
That explanation is not officially confirmed as the root cause by Pocketpair, so it should remain a community theory rather than established fact.
Still, it fits some of the reported behavior.
Raid arenas can become chaotic. Multiple Pals, large bosses, effects, structures and terrain can all exist in the same combat space. If a Pal’s combat AI loses track of where it should stand or how it should approach its target, the result could look exactly like what players are describing: a Pal that appears ready for combat but simply does nothing.
Interestingly, similar complaints have appeared against Panthalus, with players reporting that Pals sometimes refuse to attack even when brought close to the boss. A Steam discussion from late July contains a report that Pals would not attack Panthalus at close range, while another player said only long-range attacks or mounted ranged attacks were reliably working for them.
Other Reddit reports mention the same basic behavior against Panthalus and describe Pals losing their ability to engage even when positioned directly beside the boss.
That makes this look less like a Bellanoir-specific problem.
The community is finding temporary fixes — but no universal solution
Players have been experimenting with workarounds.
One commonly reported solution is recalling the affected Pal and deploying it again. In some cases, this appears to reset its combat state. Players have also discussed switching Pals, changing combat commands, restarting the game or server, and reloading the session.
One Bellanoir player reported that returning to the Main Menu and loading back into the game fixed the problem.
Another player reported that restarting a dedicated server resolved an issue affecting specific Pals that repeatedly refused to attack.
These workarounds are useful, but they also highlight the underlying problem.
There is no indication from these reports that one universal player-controlled setting consistently fixes every case.
And during a raid, that’s a serious limitation.
A workaround that takes 10 seconds in the overworld may be useless when a boss has a limited timer and your entire team is supposed to be dealing damage continuously.
The timing is especially awkward
The complaints are also arriving during a major period for Palworld.
The game is now on the 1.0 branch, with the current dedicated-server documentation listing version 1.0.3.
The 1.0 era introduced a large amount of new content, including new Pals, items and other gameplay changes.
Meanwhile, version 1.0.3 was released on August 12 and included balance changes and bug fixes.
That makes reports of combat AI problems particularly noteworthy.
It does not, however, establish that version 1.0.3 caused the problem.
Players have described similar AI behavior before and after the full-release transition, and community reports vary significantly by Pal, boss, platform and situation.
In other words, there is currently insufficient evidence to say, “Patch X broke Pal AI.”
What can be said is that players are continuing to encounter combat behavior they consider abnormal.
Some players are losing more than just a fight
The consequences range from annoying to devastating.
In ordinary gameplay, an inactive Pal may simply mean a slower victory.
In a raid, it can mean a failed attempt.
And in hardcore gameplay, the stakes are even higher.
One Reddit player described losing a hardcore world after a Pal unexpectedly stopped attacking during a boss encounter. Another said their Pal became completely unresponsive during repeated arena fights.
Those experiences help explain why the community reaction is so intense.
Players invest significant time into breeding, leveling, awakening and optimizing their combat teams. When a fully prepared Pal suddenly refuses to fight, the resulting loss does not necessarily feel like a legitimate defeat.
It can feel like the game simply stopped playing by its own rules.
What about the “Fraud Watch” label?
That is where the humorous community framing comes in.
Calling Bellanoir or other Pals “frauds” is obviously not a technical diagnosis. It is player slang for the absurd situation where a supposedly powerful combat Pal stands around while the player gets destroyed.
The joke works precisely because the underlying frustration is real.
A Pal with excellent stats and an optimized moveset is only useful if its AI actually executes those attacks.
Bellanoir illustrates the point particularly well. Her current documented kit includes high-powered Dark attacks, including Apocalypse and Nightmare Ray.
On paper, that makes her an impressive combat option.
But if the Pal enters a broken AI state and refuses to engage, those numbers become irrelevant.
Is Pocketpair facing a major AI problem?
It would be premature to say so definitively.
The available evidence is primarily made up of player reports rather than a formal developer diagnosis. Community discussions also demonstrate several different possible causes: navigation, targeting, combat-state bugs, cooldown misunderstandings, commands, server behavior and other conditions.
Some reports may therefore represent completely different problems that produce similar symptoms.
What is harder to dismiss is the sheer variety of recent complaints.
Reports have appeared involving Bellanoir, Panthalus, other raid encounters, arena battles, overworld combat and even individual Pals that repeatedly become inactive.
That suggests the issue deserves attention even if its exact technical cause remains unclear.
The bottom line
For now, the safest conclusion is simple: some Palworld players are experiencing genuine combat-AI behavior that goes beyond ordinary skill cooldowns.
Bellanoir is one of the most visible examples because raid battles make every second count. But community reports indicate that similar problems can occur with other Pals and other encounters.
Players have reported temporary fixes ranging from recalling and redeploying a Pal to restarting the game or server. None should be treated as a guaranteed solution.
And there is an important distinction between what the community suspects and what has actually been confirmed: theories about navigation meshes, targeting states or specific updates remain theories unless Pocketpair officially identifies the cause.
For players preparing for difficult raids, the practical lesson may be less glamorous than a new meta build: watch your Pals.
If a supposedly aggressive Pal suddenly stops moving, stops using skills or stares at the enemy instead of attacking, it may not be a strategic decision.
It may simply be broken.
And in a timed raid, finding out which one it is can happen only after the timer has already started ticking.
