Palworld Studio Rejects Generative AI in Games

Pocketpair, the developer of Palworld, has publicly rejected generative AI in game development, with Head of Publishing John Buckley stating 'Gamers don't want it.' The studio faces legal action from Nintendo over alleged asset disputes, while platform policies like Steam's disclosure requirements increase scrutiny on AI use in games.

Palworld Studio Rejects Generative AI in Games Push Square and TechSpot report that Pocketpair , the developer of Palworld , is not using generative AI in its games. Push Square cites Head of Publishing and Communications John Buckley saying, "Gamers don't want it," and reporting that Pocketpair has "distanced itself" from generative-AI production tools. Push Square also notes that Valve's Steam requires developers to disclose generative-AI use on storefront pages, a policy that has highlighted varying levels of AI use across upcoming titles. TechSpot additionally reports ongoing legal friction involving Nintendo and Pocketpair over alleged asset and design issues. Editorial analysis: Consumer backlash and disclosure rules are creating a visible fault line for studios weighing generative-AI adoption. What happened Push Square and TechSpot report that Pocketpair , the Japanese studio behind Palworld , has distanced itself from generative AI, and that Head of Publishing and Communications John Buckley told interviewers, "Gamers don't want it." Pocketpair confirmed it is not using generative AI to make its games. TechSpot's coverage describes a broader controversy around the studio, and reports that Nintendo has pursued legal action related to alleged plagiarism and asset disputes involving Palworld. PC Gamer adds that Buckley said: "It feels like everyone who is super gung-ho about it isn't from the industry." Background Coverage of generative AI in game production has emphasized two technical roles the tools commonly fill: rapid prototyping or placeholder asset generation, and automated text/chat features. Multiple outlets note that some teams use AI-generated assets as temporary scaffolding before replacing them with hand-crafted art. Disclosure requirements such as Steam 's generative-AI notice reported by Push Square increase visibility into that variance across projects and make usage levels easier for players and critics to audit. Context and significance Public-facing studio statements rejecting generative AI, like the one reported here, sit alongside several recent friction points: community backlash to perceived AI-assisted art, platform disclosure policies, and high-profile disputes over originality and asset provenance. Reporting by TechSpot and other outlets places Pocketpair's stance within that sequence of controversies rather than presenting it as an isolated decision. For practitioners: the story highlights non-technical adoption barriers that can be as consequential as engineering trade-offs. Community sentiment, platform-policy requirements, and legal scrutiny around asset provenance affect how visible and defensible AI-assisted pipelines will be in production environments. Disclosure and provenance tracking should be treated as operational requirements in many distribution channels. What to watch - •Whether platform policies on disclosure for example, Steam's notices converge on standard metadata or provenance APIs. - •Follow-up statements or documentation from Pocketpair, if any, about internal tooling or verification processes; currently coverage cites Buckley's comments but notes no technical disclosure beyond the non-use claim. - •How ongoing legal actions referenced in TechSpot develop and whether they produce precedent about asset ownership and AI-assisted creation. Scoring Rationale A high-visibility game studio publicly rejecting generative AI on community sentiment grounds is a solid, practitioner-relevant story about adoption barriers and public perception of AI in creative industries. Relevant for game developers, platform teams, and tooling vendors, but limited to a niche audience rather than the broader ML frontier. Practice interview problems based on real data 1,500+ SQL & Python problems across 15 industry datasets — the exact type of data you work with. Try 250 free problems /problems