- 1666 Amsterdam lawsuit: A legal dispute involving Patrice Désilets, Ubisoft, and control of the project.
- Main outcome: Désilets regained the project’s rights and creative and business control.
- Project status: 1666 Amsterdam remains an unreleased game concept without a confirmed public launch date.
- Key context: The dispute followed studio closures, corporate ownership changes, and Désilets’ dismissal.
- Best takeaway: The settlement resolved ownership concerns, but it did not confirm an active production schedule.
1666 Amsterdam Lawsuit: Background and Timeline
The 1666 Amsterdam lawsuit is closely connected to the career of Patrice Désilets, one of the creative figures associated with the early Assassin’s Creed series. After leaving Ubisoft, Désilets joined THQ Montreal and began developing a new historical action game known as 1666 Amsterdam.
The project was designed around a darker historical setting and a distinct supernatural tone. Its name refers to Amsterdam in the year 1666, a period associated with social upheaval, religious tension, war, and the threat of devastating urban fires. Although the game was never released, early concept material made it a notable unreleased project among fans of historical action-adventure games.
The corporate situation changed after THQ entered financial difficulties. Ubisoft acquired THQ Montreal, bringing the studio and its projects under Ubisoft ownership. Désilets returned to Ubisoft through that acquisition, but the relationship soon broke down. Ubisoft dismissed him, and control of 1666 Amsterdam became the center of a legal dispute.
| Event | Significance | Effect on 1666 Amsterdam |
|---|---|---|
| Désilets leaves Ubisoft | The creative director moves away from his former employer | A new project begins outside Ubisoft |
| Désilets joins THQ Montreal | He starts developing 1666 Amsterdam | The project enters active pre-release development |
| Ubisoft acquires the Montreal studio | Ubisoft gains control of the studio and its projects | 1666 Amsterdam becomes part of Ubisoft’s portfolio |
| Désilets is dismissed | The developer and publisher relationship deteriorates | Legal action follows |
| Settlement is reached | Both parties resolve the dispute | Désilets regains control of the project |
Treat 1666 Amsterdam as an unreleased development project, not as a finished title with a conventional launch history, roster, or platform list.
The timeline matters because the lawsuit was not simply a disagreement over creative direction. It involved employment, corporate acquisition, project ownership, and the rights of a creator to continue developing his work after leaving a publisher-controlled studio.
What the Settlement Changed
The dispute ended through an agreement between Désilets and Ubisoft. The practical result was that Désilets received the rights to 1666 Amsterdam and regained creative and business control over the project. He withdrew the complaint as part of the settlement.
That distinction is important. A withdrawn complaint does not necessarily mean that one party lost in court. In this case, the settlement gave Désilets the outcome he had sought: control over the game project. The agreement allowed Ubisoft to step away from 1666 Amsterdam while Désilets retained the ability to decide what would happen next.
| Settlement Question | Practical Answer |
|---|---|
| Did Ubisoft keep control of the project? | No. Control transferred back to Désilets under the agreement. |
| Was the project released immediately? | No. The settlement did not create a launch date. |
| Did the agreement guarantee renewed development? | No. Ownership and development activity are separate issues. |
| Was the lawsuit continued to a public trial? | No. The complaint was withdrawn as part of the settlement. |
| Did the settlement confirm a sequel or revival? | No. It resolved control of 1666 Amsterdam rather than announcing a new production. |
The settlement also explains why the legal story is often described as a victory for Désilets, even though the case did not end with a dramatic courtroom judgment. The important result was control of the intellectual property and the freedom to make future creative and business decisions.
Do not confuse a settlement with a full public court ruling. The known outcome concerns transferred control and withdrawn legal action, not a detailed judgment on every allegation.
For fans, the most meaningful part of the agreement was the change in ownership. Before the settlement, Ubisoft controlled the project through its connection to the acquired studio. Afterward, Désilets could determine whether 1666 Amsterdam would be revived, redesigned, licensed, or placed on hold.
Project Identity and Creative Direction
1666 Amsterdam attracted attention because it appeared to offer a different direction from the Assassin’s Creed formula. The project was associated with Patrice Désilets, but it was not presented as an Assassin’s Creed game. Its identity centered on a historical Amsterdam setting, a protagonist connected to supernatural elements, and an atmosphere that leaned toward mystery and dark adventure.
Early descriptions and concept material suggested a game built around exploration, stealth, action, and supernatural abilities. However, the available public information does not establish a final feature list. Many ideas may have changed during development, and unreleased concepts should not be treated as confirmed gameplay systems.
Historical Setting
Amsterdam in 1666 provides the project’s central time and place, with a focus on period atmosphere rather than a modern setting.
Dark Tone
The concept is associated with mystery, danger, and supernatural themes that distinguish it from a standard historical adventure.
Creator-Led Vision
Patrice Désilets’ involvement made the project notable to fans tracking the creative lineage of historical action games.
Unreleased Status
Public concept material reveals direction and ambition, but not a finished product or confirmed final mechanics.
| Known Element | What Can Be Said Safely | What Remains Unconfirmed |
|---|---|---|
| Setting | Amsterdam during the year 1666 | Final map size and districts |
| Genre direction | Historical action-adventure concept | Final combat and progression systems |
| Tone | Dark, supernatural, and atmospheric | Final narrative structure |
| Creative leadership | Associated with Patrice Désilets | The complete final development team |
| Release history | Unreleased project | Any confirmed launch window |
The setting is one of the project’s strongest hooks. A city shaped by canals, narrow streets, trade, religious divisions, and political tension could support stealth-focused movement and environmental storytelling. The supernatural angle also opened room for unusual abilities and a more stylized interpretation of historical fiction.
Still, responsible wiki writing must separate concept information from confirmed production details. A prototype, pitch, or early demonstration can show a creative direction without proving that the same systems would have appeared in a finished game.
The strongest confirmed identity of 1666 Amsterdam is its historical setting, creator-led development, and supernatural action-adventure concept—not a finalized gameplay specification.
How to Read the Project’s Current Status
The settlement gave Désilets control of 1666 Amsterdam, but ownership alone does not indicate that development resumed. A project can be legally recovered and still remain inactive while its creator focuses on another game, studio, or business priority.
Use the following process when evaluating new claims about the project:
Check the announcement source
Look for a statement from Désilets, his studio, or another rights holder. Avoid treating forum posts, fan edits, or unattributed screenshots as confirmation.
Separate rights from production
Confirm whether a report discusses ownership, active development, a prototype, or a commercial release. These are different milestones.
Verify the project name
Make sure the announcement refers specifically to 1666 Amsterdam rather than another project connected to the same creator.
Look for concrete details
A genuine revival would normally identify a developer, production status, platform strategy, or public development update.
Update cautiously
Record confirmed facts first and label speculation clearly. Do not convert concept art or old demonstrations into release promises.
| Status Label | Meaning | Use for 1666 Amsterdam |
|---|---|---|
| Rights recovered | The creator or rights holder controls the project | Confirmed settlement outcome |
| In development | Active production is publicly acknowledged | Not established by the settlement alone |
| Announced revival | A new development effort has been formally presented | Requires a new official announcement |
| Release scheduled | A date or launch window is publicly confirmed | No confirmed date established here |
| Cancelled | Rights holder formally ends the project | Should not be claimed without confirmation |
The most accurate status description is therefore “unreleased project with rights returned to Patrice Désilets.” That wording captures the legal outcome without implying that a playable commercial version exists.
For archival research, the best approach is to preserve the distinction between historical reporting, concept material, and later official announcements. The Panache Digital Games website is the most relevant official channel for tracking future statements from Désilets’ studio, although an official channel should only be treated as confirmation when it directly discusses 1666 Amsterdam.
A rights transfer can reopen possibilities, but it does not establish active production, a release window, or a downloadable version of the game.
Research Checklist for Fans and Wiki Editors
The legal history of 1666 Amsterdam is easy to oversimplify. Use this checklist before adding claims to a wiki page, video description, or fan discussion.
Fact-Checking Checklist:
- Confirm that the claim refers specifically to 1666 Amsterdam
- Identify whether the information concerns ownership, development, or release
- Use official statements for any new revival or production claim
- Label concept art and prototype footage as pre-release material
- Avoid listing platforms, prices, or release dates without confirmation
A useful editorial summary should include four core points:
- Patrice Désilets was connected to the project after his work at Ubisoft.
- 1666 Amsterdam was developed through THQ Montreal before Ubisoft acquired the studio.
- Désilets sued Ubisoft after being dismissed and losing control of the project.
- The settlement returned project rights and creative and business control to him.
These points explain the dispute without overstating what happened afterward. They also help readers understand why the project remains relevant despite never reaching a public release.
Use “unreleased,” “concept,” and “settlement” precisely. These terms provide useful context without suggesting that unfinished material represents the final game.
FAQ: 1666 Amsterdam Lawsuit and Future
Q: What was the 1666 Amsterdam lawsuit about?
The dispute involved Patrice Désilets, Ubisoft, and control of 1666 Amsterdam after Ubisoft acquired the Montreal studio where the project was being developed and later dismissed Désilets.
Q: Who received control of 1666 Amsterdam after the settlement?
Patrice Désilets regained the project’s rights along with creative and business control under the settlement agreement.
Q: Was 1666 Amsterdam released after the lawsuit?
No. The settlement resolved control of the project but did not announce a commercial release, launch window, or completed version.
Q: Is 1666 Amsterdam the same as Assassin’s Creed?
No. The projects are connected through Désilets’ creative history, but 1666 Amsterdam was presented as a separate historical action-adventure concept.
The lawsuit remains an important part of 1666 Amsterdam’s history because it changed who controlled the project. It did not, by itself, determine whether the game would return to production. Any future update should therefore be judged by the same standards: identify the rights holder, confirm active development, and look for a direct announcement.
For now, 1666 Amsterdam is best understood as a historically themed, supernatural game concept whose ownership dispute ended with control returning to its creator. That outcome preserves the possibility of a future revival while leaving the project’s production and release status unresolved.
Do not describe 1666 Amsterdam as released, cancelled, or actively in development unless a future rights-holder announcement clearly confirms that status.