Palworld developer says it will not publish games using NFTs, Web3, or large-scale AI systems
Palworld publisher Pocketpair says it will avoid games using NFTs, Web3, or major AI integration

Pocketpair, the developer and publisher behind Palworld, has confirmed it will not publish games using NFTs, Web3, or extensive AI technologies, stating that such tools do not align with the company’s creative philosophy.
In an interview with Game Developer, Pocketpair communications director and publishing manager John “Bucky” Buckley said the company wants to maintain authenticity in game creation.
“People are going to say I’m lying, but these are just the hard facts. We don’t believe in it. We’re very upfront about it,” Buckley said. “If you’re big on AI stuff or your game is Web3 or uses NFTs, there are lots of publishers out there, but we’re not the right partner for that.”
Buckley expressed concern that a rise in low-quality, AI-generated games could impact digital platforms. “I think over the next two or three years we’re going to get into this weird era—of really low quality, AI-made games,” he said.
“It’s something that has plagued other stores but Steam had been good at keeping them out. But it’s happening. This wave is coming, and I think we’re going to enter this kind of authenticity market.”
Pocketpair’s stance comes after the studio faced accusations that Palworld used AI during development, which the company continues to deny. Buckley addressed the claims, explaining that cultural differences contributed to misunderstandings.
“One of their biggest pieces of ‘evidence’ was that because we hadn’t published the individual names of the translators it must be AI. Well, no, this is just poor Japanese culture in general,” he said.
As debate around AI in gaming continues, Pocketpair has made its position clear: it will focus on creative, human-driven projects that prioritise authenticity over automation.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ