Skip to main content

Palworld devs can't keep up with cheaters, but it's working on a solution

No word on when the solution is being introduced, though.

Palworld is slightly struggling with cheaters at the moment, which developer Pocketpair has acknowledged it's failed to deal with so far.

If you're one of the numerous players unable to log in to Palworld at the moment due to server issues, you won't be the only one, as apparently cheaters are making it difficult to play the game across the board. This is something Pocketpair is aware of, and in a recent Steam post it has admitted to the problem, and while it doesn't have a solution just yet, it does have a plan on how to deal with it. "First of all, we plan to release a player list function for servers in an update at the end of February," reads the post.

"Through this, we will strengthen the identification of players who engage in cheating and the suspension of their use by the development team. Following this, we plan to introduce an external anti-cheat solution to take measures against particularly frequent fraudulent activities and cheating… In addition to the above measures, we will continue to take thorough measures against further cheating and fraudulent activities."

The post did also note that this applies to official servers; for community servers, single-player, and co-op, the anti-cheat solution will be optional, so I guess if you want to just cheat with your friends, Pocketpair is open to that. Though, earlier in the post it did write that it does "not tolerate any fraudulent activity or cheating," so I'd still err on the side of caution.

With how popular Palworld has become, Pocketpair has pretty much been struggling across the board since launch, whether it be from very high server costs, or the general lack of staff (which it's trying to recruit more of). Personally, I'd expect it to be a while before Palworld is a completely smooth experience, but at least you can always pick up a very unofficial looking Halloween costume in the meantime.

Read this next