Ubisoft shelved Patrice Désilets' 1666: Amsterdam and suspended him, then the legal fight won

Few games have a history as turbulent as 1666: Amsterdam. It is the project Patrice Désilets, the founding director of the Assassin's Creed series, fought Ubisoft for, and it is the kind of creative conflict that tends to leave scars on everyone involved, from teams and studios to boards and investors.

The timeline is the story here. The project was in development at Ubisoft in some form for about 13 years, before Ubisoft decided to shelve 1666 and suspend Désilets. That decision did not just stall a game. It triggered a legal battle that Désilets eventually won three years later, setting the stage for why a “new and witchy” demo can feel less like a normal reveal and more like a live wire.

To understand why this matters beyond fandom, it helps to understand how this kind of project gets treated inside big publishers. A long-running game can be “in development” for years, but it is still subject to shifting priorities: platform cycles, internal leadership changes, budget pressure, and risk tolerance around new IP or ambitious production plans. When a publisher shelves a project after a decade-plus runway, it signals that the internal case for continuing did not survive the moment it met the business. And when the same publisher also suspended the creator tied to that effort, it turns a resource decision into an accountability one.

That distinction is where the strategic stakes sharpen for decision-makers. For Ubisoft, shelving 1666 and suspending Désilets suggests the company believed it needed to reset both the project and its internal governance. For Désilets, fighting back through legal channels and eventually winning three years later signals that the dispute was serious enough to challenge not only an outcome, but the process that led to it. In board terms, this is the difference between “we changed our mind” and “we took action that the other side contested successfully.”

Now comes the part that naturally raises more questions than answers: Désilets has wanted to make 1666 for a long time, and the appearance of a “new and witchy 1666: Amsterdam demo” keeps the project alive in the public conversation. But a demo is not a contract. It is a signal, and signals can be read multiple ways. From an exec perspective, the demo raises practical questions about continuity, ownership, and how the work that survives a shelving can later be packaged into something new. From a governance perspective, it also highlights the long tail of creative conflict. Even after a legal win, timelines and relationships do not just snap back to “normal.”

There is also a broader market context to consider. The creative engine that made Assassin's Creed a standout depends on confident world-building and iterative development, but the industry has become more risk-managed in recent years. Publishers regularly balance long gestation periods against the need for reliable pipeline outputs. When a high-profile creator’s project goes through a years-long fight, it becomes a case study in what happens when that balance breaks down. It can influence how boards scrutinize claims of creative value versus cost and control. It can also affect how leadership teams assess who should have leverage when the project and the creator are tightly linked.

Regulatory and legal framing matters too, even when the public story is about games. Legal battles in the creative sector often turn on intellectual property, employment status, and the terms under which decisions are made. This particular saga is already anchored by two clear facts in the source: Ubisoft shelved 1666 and suspended Désilets, and Désilets eventually won the legal battle three years later. For executives, the second-order implication is that long-term disputes can persist in reputational and operational form, influencing future negotiations, contract structures, and internal escalation paths.

So what should leaders take away if they are watching this from the outside, whether as a publisher exec, an investor, or a studio operator? 1666: Amsterdam is not just a potentially intriguing game pitch. It is a reminder that when a publisher halts a major project and suspends its most visible creative driver, the consequences can outlive the shelving itself. If you are running teams in this space, the question becomes less “will the demo be good?” and more “what happens to our projects, people, and incentives when the business case changes?” The answers are still being written, but the precedent is already there.