AI News
16 Aug 2026
Read 8 min
1666 Amsterdam AI use controversy: Discover what’s true
1666 Amsterdam AI use controversy reveals how the developer cut generative tools and protects art.
The 1666 Amsterdam AI use controversy centers on Panache Digital admitting it still uses AI tools during development while pledging no AI-made assets will ship in the final game. After fans found AI traces in the prologue art, the studio apologized and is phasing the tools out, it says.
Panache Digital, the studio led by Assassin’s Creed creator Patrice Désilets, says it used AI to speed up concept work on 1666: Amsterdam but promises the finished game will not contain AI-generated assets. At a recent hands-off preview in Amsterdam, Désilets said the team now relies on AI “less and less” and has tightened its asset pipeline after the backlash over the prologue.
Use AI for early variation and brainstorming only
Replace or repaint those references with original art
Audit builds to catch leftovers before release
Reduce reliance on AI as more final art locks in
AI is still used inside development for speed, but “less and less” as assets finalize
Shipped content is promised to be AI-free
The team acknowledges past slips and says new reviews should prevent repeats
Expect the final art to be credited work from human artists
If you try Early Access, watch patch notes for any art swaps or audits
Voice, writing, and systems weren’t flagged; the heat was mostly on visuals
Clear art credits and behind-the-scenes breakdowns
Dev updates that document asset revisions post-prologue
Stable visual identity with fewer “AI tell” artifacts
What sparked the 1666 Amsterdam AI use controversy
Players spotted visual tells of generative art in paintings and marketing tied to the game’s playable prologue. Those findings spread fast, and criticism followed. Panache apologized, explained that some images slipped through during a busy phase, and said it would remove AI-made content for the full release. The studio also clarified that any current AI use is internal-only for iteration, not for shipping assets.What Panache says it will ship
No AI-generated assets in the final product
Désilets said the launch version will not include AI-made images, textures, or other content. The team states it has added checks so anything that enters the build goes through review and retouching by artists.A clearer pipeline after the prologue
Panache described stricter guardrails to separate quick ideation from anything that reaches the game:Why a small studio leaned on AI
Panache has about 70 people. During early concepting, the team needed fast visual variations to explore tone, costumes, and props. AI tools produced rough ideas in seconds. That speed is the appeal. But it also creates risk: references can blur into shippable assets if pipelines are loose or deadlines are tight. The studio now says it better separates “idea art” from “game art” and is cutting back the tools as production matures.What the game is aiming to deliver
1666: Amsterdam follows a witch named Noa in 1666, a man named Aaron in 1999, and his descendant Clio today. These timelines overlap across Amsterdam as a sinister “Collector” hunts powerful “Originals.” The concept is bold, with layered eras, stealth and action, and a moody day-night cycle. Early Access is set for 25 August on Steam and the Epic Games Store at $30.Since the 1666 Amsterdam AI use controversy: where things stand
The studio’s position
What this means for players
The bigger picture: tools vs. trust
The debate here is less about whether AI exists in studios and more about boundaries. Many developers use machine learning for search, testing, or concepting. The line is whether AI-generated content ships, how it is disclosed, and how teams credit artists. When teams explain their rules, show audits, and react fast to feedback, trust can recover.What to look for ahead of Early Access
Signals that the promise holds
The game itself
If the story across 1666, 1999, and today clicks, 1666: Amsterdam could stand out for its structure and setting. If the art direction lands and the launch build avoids AI leftovers, the conversation can shift back to design, stealth, and the witchy tone the team wants to highlight.The road ahead
Panache must now prove its pipeline works and that artistic ownership is clear. The studio’s open stance—admitting internal AI use while committing to ship without it—puts accountability on every update from now to launch. If Early Access reflects those promises, the 1666 Amsterdam AI use controversy may fade, leaving the focus on the game’s ideas rather than its tools. (Source: https://www.eurogamer.net/1666-amsterdam-ai-tools-controversy) For more news: Click HereFAQ
Q: What is the 1666 Amsterdam AI use controversy?
A: The 1666 Amsterdam AI use controversy centers on Panache Digital admitting it used AI tools during development after players spotted generative-art tells in the playable prologue, prompting an apology. The studio says it will not ship AI-generated assets in the final game and is phasing the tools out of its pipeline.
Q: Where were AI-generated elements spotted in the game’s material?
A: Players noticed tell-tale signs of generative AI in in-game paintings and marketing tied to the playable prologue, which prompted the backlash. Panache acknowledged those traces and said some slipped through during a busy phase of production.
Q: Will any AI-made art appear in the final release of 1666: Amsterdam?
A: Panache and Patrice Désilets have stated that no AI-generated images, textures, or other visual assets will ship in the final product, with Désilets saying “It won’t be in the final product.” The studio also says it has added review steps and retouching by artists to prevent AI outputs from entering builds.
Q: Why did Panache use AI tools during early development?
A: As a roughly 70-person studio working through concepting—especially during COVID lockdown—Panache used AI to generate quick visual variations and brainstorm ideas because it can produce rough concepts in seconds. That speed helped explore tone, costumes, and props when the team was small.
Q: What pipeline changes did Panache implement after the controversy?
A: Panache tightened its asset pipeline by separating quick ideation from final game art, requiring artists to repaint or replace AI-generated references, and auditing builds to catch leftovers before release. The studio also says it will reduce reliance on AI as final art locks in.
Q: How should players judge whether Panache kept its pledge when Early Access arrives?
A: In light of the 1666 Amsterdam AI use controversy, players should look for clear art credits and developer updates documenting post-prologue asset revisions. Watching patch notes for art swaps or audits and checking for a stable visual identity without common “AI tell” artifacts will help verify the studio’s pledge.
Q: Is Panache still using AI internally now?
A: Yes; Patrice Désilets and the studio say AI is still used internally for iteration and quick idea generation but “less and less” as the project matures. They maintain that current AI use is for ideation only and not intended to result in shipped assets.
Q: What broader industry issues did the 1666 Amsterdam AI use controversy highlight?
A: The 1666 Amsterdam AI use controversy highlighted questions about boundaries between using AI as a tool and shipping AI-generated content, plus the need for disclosure, proper credit for artists, and audit processes to maintain trust. The article notes many studios use machine learning for search, testing, or concepting, and that clear rules and audits can help rebuild trust when mistakes occur.
Contents
