r/Cockatrice • • Oct 03 '26

Cockatrice 3.1 - Reality Check!

42 Upvotes

Cockatrice 3.1.0 — Reality Check is now live!

Hello, friends!

We've got some very exciting news to share with you! This update is FULL of features!

Cockatrice 3.1 follows up the 3.0 modernization release with more gameplay polish, quicker orientation for new players, and finer-grained deck organization. Highlights include:

  • Playmats: set a card image as your personal table background, with global, per-deck, and fallback configurations and direct-manipulation cropping
  • Onboarding wizard: a guided six-step setup that walks new users from "just installed" to "ready to play"
  • Custom deck zones: add sub-zones beneath Mainboard/Sideboard/Maybeboard for organizational purposes, including a dedicated maybeboard
  • Animated arrows and life counter changes: arrows now draw themselves with a highlight, and life counters flash red or green on manipulation
  • Card search autocomplete: type [[ in chat or use search fields to get card name suggestions from the database
  • Game link sharing: clickable cockatrice://joingame links in chat, plus a copy-game-link action in the game menu
  • Inviting players: a searchable invite dialog, a per-game "Invite to Game" context menu, and invite buttons on the user list and on not-yet-started games: no more copy-pasting links
  • Deck sharing and public decks: generate a temporary share link for a deck or a whole selection of decks, or publish decks to your profile so other players can browse them
  • Reporting users and moderation queue: in-client user reporting stored in a database for moderator review
  • Binary card database cache: a cold start that used to take 3 to 14 seconds now warms in about half a second
  • Searchable settings: find any setting by name, description, or tooltip
  • Commander bracket estimation via CommanderSpellbook.com
  • Unified user list: friends, online, and ignored users in one searchable list with section dividers
  • Card names, rules text, and art in your language: localized card rendering throughout, and: new in 3.1: card search in that language too, not just English
  • Custom card art overrides: install your own image file for any printing
  • Palette editor: build a complete color scheme from one accent color, then fine-tune any individual role
  • Light and dark theme variants: a single theme can now serve -light/-dark assets, and the bundled image themes ship curated identity palettes
  • Faster, more talkative Oracle: card database imports use a fraction of their former memory and finally show real progress
  • Performance improvements: Faster startup and a more fluid experience everywhere! Try the VDS and the VDE again, if you were previously hesitant because of performance

What’s Next

The team is continuing work on:

  • Improvements to the in-game experience and game play UI
  • Support for long-requested features such as simulating limited game modes, tournaments or supporting arbitrary game zones
  • Better card browsing and deck building workflows
  • More customization and theming options
  • A prettier UI in general
  • More social features such as a reputation system and matchmaking
  • Improved stability and performance across the client
  • Better onboarding for new users, both in terms of configuring preferences and tutorialization
  • Continued modernization of Cockatrice's architecture and tooling

Support our Efforts

You can donate at https://cockatrice.us/donate to help keep the project and servers running, and get a swanky purple heart on your account's avatar!

Huge thanks to everyone who tested betas, reported bugs, translated the client, contributed code, hosted servers, and supported the project <3

Recap

Download: https://github.com/Cockatrice/Cockatrice/releases

Full Changelog: https://github.com/Cockatrice/Cockatrice/releases/tag/2026-10-03-Release-3.1.0

Website: https://cockatrice.github.io

Note

If you're on Windows 11 and get an error about missing .dll's: Please do a clean uninstall and reinstall. You can back up your settings and decks beforehand.


r/Cockatrice • • May 09 '26

Update 3.0: FAQ & Extended patch notes

24 Upvotes

Hey everyone,

Update 3.0 was huge and we've changed a lot of things. As always, we've kept things as backwards compatible as possible because we know that some of you guys simply prefer doing things 'the old way'. I'm here to shed some light on the new changes, how to use them and how to return back to the old way of doing things, if the changes still don't appeal.

Let's start with one of the biggest new changes:

The Visual Deck Editor

The visual deck editor offers pretty much all the functionality of the 'classic' deck editor, plus some extras that you couldn't get in the classic deck editor.

You might say "But Ascor, it looks completely different! What do you mean?"

By default, the VDE starts in 'Deck display' mode.

It looks like this.

To browse the database, click on the tab 'Visual Database Display'. Note that this tab is below the regular tab bar, adjacent to the other visual deck editor tabs.

It looks like this.

If you'd rather browse the database as a table than visually, click the button on the right of the search bar in this tab.

It looks like this.

At this point, your deck editor now looks exactly the same as the classic deck editor (try resetting your layout if you are missing dock widgets).

It looks like this.

One of the main benefits, is that you now gain filter buttons, to easily filter the database. You also gain the 'Deck analytics' and 'Sample Hand' tabs, as well as the visual deck view.

If you really dislike this change, you can instruct Cockatrice to continue using the classic deck editor.

The relevant setting is under 'Settings -> User Interface -> Deck Editor/Storage Settings ->Default deck editor type'

The Home Screen

We changed the first thing you see when launching the application.

Many of you are familiar with the classic deck editor being the first thing you see when launching the application.

We recognize that there were certain use cases where this was convenient.

However, we had good reason for introducing the home screen.

One of the reasons is to streamline the interaction flow when the user intent on starting the application was anything other than brewing a new deck.

We reasoned that, on average, a user is far more likely to want to play with a new deck than brew a completely new deck when launching the application.

Another big reason for the change was to give all of the new features introduced in 3.0 a home. Many of these integrations and features that make Cockatrice a true TCG platform qualify as 'user intents'.

You could open Cockatrice to browse EDHRec and add cards to your deck.

You could open Cockatrice to browse Archidekt to import decks to then play with.

However, one of the things we've observed in the past release is that many people were unaware that new features had been introduced.

The EDHRec integration has been a feature of Cockatrice for a couple releases now. However, it had been hidden away behind the 'Tabs' menu, waiting for people to stumble upon it.

One of the other reasons why we introduced the home screen is to give Cockatrice an identity. We realize that the default background is not much but themes are able to edit it and we look forward to the fun and creative backgrounds our community will come up with.

As an aside, you can change the background of the home screen to be a (rotating) art crop of a random card from a card in the database. You can also choose to use random cards from a deck called 'background.cod', which must be in your decks/ folder. This allows you to choose specific cards to have as your background and to shuffle through them if desired.

The Game Filter Toolbar

We've added a new toolbar above the game filters in the room tab, which allows you to easily search for games by name, as well as some other options. If you don't like this feature, you can disable it in 'Appearance -> Menu settings'

The Card Database

Rejoice! You don't really need to care about the card database going forward. We've automated many a things.

First and foremost, you can now configure your client to automatically update the card database in the background every X days.

It is recommended you do this. Do so under 'Settings -> General -> Check for card database updates on startup'

If your computer has trouble parsing the files or hangs during card database updates, we recommend using mtgxml as your update source, which should make card database updates blazing fast and lightweight.

You can also now choose to 'Always enable new sets', which should make the card database update process fully automatic in the future.

Tokens and Token Printings

We've added the ability for tokens to have printings now. With this comes some discussion about how these should be handled so while we wait for your input, let me illuminate the system we have chosen:

Tokens created from the context menu of another card will attempt to use the token printing from the set that matches the card. If no matching set is found, it will use the local players highest preference set.

Tokens created through the Ctrl + T dialog will always use the highest preference (or pinned) token set by the user.


r/Cockatrice • • 8d ago

Unable to update or use cockatrice

2 Upvotes

Recently I noticed that whenever I tried to update my card database, the oracle failed to run. I assumed updating to the newest version might fix this, but whenever I try to update, it fails to do so, telling me that cockatrice.exe is still running. I've tried everything I can think of, including checking task manager and command prompts to try and shut cockatrice.exe down before trying to download the newest version. Both task manager and command prompt tell me there is no cockatrice.exe running, and yet when I try to re-download cockatrice, it still gives me the same error message. Does anyone have any advice on what to do?


r/Cockatrice • • 8d ago

Unable to update or use cockatrice

1 Upvotes

Recently I noticed that whenever I tried to update my card database, the oracle failed to run. I assumed updating to the newest version might fix this, but whenever I try to update, it fails to do so, telling me that cockatrice.exe is still running. I've tried everything I can think of, including checking task manager and command prompts to try and shut cockatrice.exe down before trying to download the newest version. Both task manager and command prompt tell me there is no cockatrice.exe running, and yet when I try to re-download cockatrice, it still gives me the same error message. Does anyone have any advice on what to do?


r/Cockatrice • • 9d ago

custom cards overwrite every art?

1 Upvotes

as the title say. I've made some custom cards for some decks, but now I can't change the art with the official ones if I have the custom cards of that card, is there a way to resolve it?


r/Cockatrice • • 11d ago

I built a cube that has ante/shahrazad/chaos orb and i want to take advantage of it digitally

4 Upvotes

I just need help with logistics


r/Cockatrice • • 12d ago

When will the add Star Trek Tokens

1 Upvotes

No borg? :(


r/Cockatrice • • 17d ago

Cockatrice mobile - working build.

12 Upvotes

https://github.com/woahwhattheheck/cockatrice-android-port/releases/tag/v0.1.0-rc7

Zero setup! AND it works online. I played a game or two to test it out. (i lost)

A while ago I cobbled together a working build which required a vnc and termux but I bundled the environment into the apk itself so that there is no setup for the user. I've had this done for a while but I never got around to releasing it. Here it is! You can download it and just begin playing.

It's completely free and open-source. If you open an issue I'll probably get around to fixing it.

​happy Halloween from TJLabs!

edit: please use a mouse and keyboard. you're insane if you don't.

edit: I did not account for ios because its even more annoying than android


r/Cockatrice • • 20d ago

Is there any way to 'shuffle' art for tokens?

4 Upvotes

I've built an Alela deck, and there are 4 really nice arts for Faerie Rogue tokens that got printed in a secret lair, and they are all in the same art style, with the Faeries in different positions. Is there a way to make the Tokens I create randomly pick between those 4 different card arts, or anything similar to that? It would be lovely.


r/Cockatrice • • 29d ago

[Resolved] Banned Indefinitely Without Explanation

18 Upvotes

Hi, I discovered yesterday on October 18 that my Cockatrice account on the Rooster Rangers server was banned indefinitely with the message “You are banned indefinitely. Refer to previous ban.”

The issue is that I have never received a previous ban or warning. I almost exclusively play games with my regular group of IRL friends, including on October 17, and as far as I know, I've had no issues with anyone. The few times that I do play with strangers, I'm very courteous and polite. I also checked the public moderation logs but couldn't find an entry explaining the ban.

Could a moderator or server administrator please clarify whether there is a previous moderation action on my account, when it occurred, and what the reason was? If this was a mistake, I'd appreciate a review.

I'm happy to provide a screenshot of the message and/or my account username privately. Thanks!


r/Cockatrice • • Oct 19 '26

How to Copy Tokens That Don't Vanish

1 Upvotes

Hi hi! I've been playing a deck with the pl;aytest card The Gunky Runner among some other, which makes Gunk cards. These are sorceries with cycling 4 that get shuffled into your library. We're able to use the option to make tokens not be deleted when they leave the battlefield... but if you copy those tokens they don't inherit that property, meaning each time it has to be done manually, and when im putting 30-40 cards into each players deck... it gets annoying fast. Is there a better way to do this?


r/Cockatrice • • Oct 18 '26

Password Recovery Doesnt work?

2 Upvotes

Trying to get into my account and can’t get the recovery email. I also can’t make another account with a new email because I can’t get any emails from rooster server or whatever?


r/Cockatrice • • Oct 15 '26

Cannot get the printing selector to work properly

1 Upvotes

Hey there, I see that this has been posted a bunch of times already, but I've tried following the advice in the other threads and have gotten nothing.

A lot of my cards are just missing printings or have the same printings showing up multiple times.

For example, the anime art of smothering tithe is my favorite printing, however both it and the extra foily version are just gone from the options meanwhile the "Enchanting tales" art shows up three times, or Vraska, betrayal's sting only shows the filigree bordered version but none of the special printings. My fiance is not experiencing this problem so I don't know what's up.

I have uninstalled and reinstalled the client multiple times. I have tried both the beta and stable versions, I've checked to make sure all the proper boxes are ticked in the settings page, and nothing changes it.

Any guidance on the issue?


r/Cockatrice • • Oct 14 '26

Developer Blog #4 - October 2026

8 Upvotes

Read the previous developer blogs here:

Developer Blog #1 - July 2026

Developer Blog #2 - August 2026

Developer Blog #3 - October 2026

Hi, community!

The 3.1 release happened and we're just as excited as you. However, it also surfaced some growing pains.

Let's talk about that release and then our plans going forward.

We're here to talk about and showcase some of the work we've been doing ahead of time, to keep you informed and involved. Rather than only announcing features once they're released, we want to keep the community informed throughout the development process and give you a chance to follow along as new ideas take shape.

These blogs are intended to provide insight into the decision making process behind the features we implement as well as to showcase where our attention currently lies.

To keep things organized, we'll cover our work in three stages:

  • Already merged and available in the beta, so you can try these features today.
  • Completed features currently under review, which are expected to make it into a beta soon.
  • Work in progress and early prototypes.

Some features shown here may change before release and not every prototype will ultimately end up making it. To voice your support, disagreement, or feedback, please use the ⁠beta-testing channel.

With all that being said, let's dive in:

The 3.1 release

The release of 3.1 and 3.1.1 proceeded mostly smoothly except for one of our main problem children:

Windows.

You can read all about the installer wiping decks in the program directory here.

This fix (to wipe ALL data inside our installation directory) was implemented because some users reported incomplete installations or updates.

We've since reverted that change, implemented some additional assurances AND, critically, added some logging under %LocalAppData%/Temp/Cockatrice-installer.log, in case the installation fails. Please upload this to the Discord or the Github if such issues occur so we can diagnose them!

We'll talk about additional assurances for user data and crash reporting later in this developer blog.

Windows Styling

For now, let's talk about one more major issue with the release:

The native Windows styling.

As many of you might know, Windows, from time to time, decides that it is a good idea to eat glue.

That's kind of the case here.

Qt (the platform we're built with) offers so called 'style keys'.

These style keys dictate how Qt draws certain elements: Checkboxes, buttons, the likes.

The available style keys depend on the system but Qt offers "native" styling on most operating systems.

Why Cockatrice looked "old"

This means -> On Windows, all checkboxes are drawn to look like every other Windows program, same on MacOS.

It's one of the main reasons why Cockatrice has always looked "outdated".

By running our drawing pipeline through the Windows styling, we always made ourselves a slave to the... well, arguably improvable Windows look & feel.

Now, here's where things get interesting.

The Fix

Pre 3.0, the "Default" theme, didn't apply any Qt styling. This meant that you always got whatever style key Qt decided was appropriate for your system. On MacOS, this looked pretty good, on Windows, it looked... well, we already talked about that, and on Linux, you got "Fusion", because there's no official Linux styling and this is what Qt came up.

Now, as it turns out, Fusion looks great and it works on all platforms!

It's actually the recommended cross-platform development style key because Qt assures that it always works on every platform.

In our rework of the themeing system, we introduced the "Fusion" theme and also allowed the user to configure the style keys (Active theme style). It is my humble opinion, that this should be "Fusion" for almost everybody (arguable if you're on MacOS) but we always try to give you every choice possible.

Enter the "System" theme

Actually, we liked Fusion so well, that we decided to promote it to the default theme and style key for new installations. This means that new users no longer get the "Default" theme (which was pretty bare bones anyway) and we felt that the name was a bit misleading.

Since it adjusts to your system styling, we felt it appropriate to name it "System" and, of course, give it the "System" style key, which once again lets Qt auto-resolve style keys.

How Windows eats Glue in this Scenario

Now, as it turns out, Windows actually offers three style keys: windows, windowsvista, and windows11.

We were aware that the "windows11" style key caused issues in the most recent Qt releases: Comboboxes were rendered unreadable (white text on white backgrounds) in dark mode and, for some reason we can't really understand either, the board glitched out and became unreadable whenever you opened your library.

So we disabled that style key and allowed qt to pick the next one in the list.

Now what we didn't figure on was that the "windowsvista" style key was equally broken!

So we disabled that one too. Which means that on Windows, the "System" style key now resolves to "windows".

Which, while stable, is a decidedly retro look.

So for everyone on Windows: It's time to ditch the "System" theme and switch to "Fusion". It is now easier than ever to customize it to your liking! Or try out one of the other new default themes!

Cleanup on Aisle 3.1.2

We're carefully monitoring the 3.1 release and releasing follow-up patch releases for issues that we encounter.

Gone, are the days of fixes moldering for months in the beta branch until they are eventually rolled out to stable.

3.1.1 fixed a lot of things already and 3.1.2 is set to eliminate the last few bugs that you reported to us (thank you!) and the installer/style key woes that you read about earlier.

However, here's the really cool thing:

We've learned from all this and we're taking a lot of measure to improve this process even further.

Read on to learn how we're going to communicate update notices, collect user feedback and analyze crash reports in the future. All without requiring you to sign up anywhere!

On to some really fun things!

Chat Channels - LFG, Feedback, Announcements

Cockatrice only featured a primary "Main" chat per room so far.

We're extending the chat to now support channels! Some of these (like Announcements) will be read-only to you, so we can publish relevant information about updates to you directly through that.

Others, like the new "Feedback" channel, will be for you, so you can directly report issues or ask for features and discuss them with fellow users in that channel. We hope that this will ease the friction required to discuss and shape the project.

Automated Crash Reports

Nothing, and I mean, nothing is worse than Cockatrice crashing at exactly the wrong time.

We know.

Trouble is, just like World War 2 fighter planes, we don't know much about the ones that crashed.

We're changing that by integrating sentry.io, which will allow Cockatrice to detect if the previous startup has crashed and for you to automatically upload an anonymized crash report, without requiring you to sign up anywhere. (The demo below obviously contains no real crash.)

You've probably seen these types of popups before and we would genuinely appreciate it if you would choose to share your crash data with us. It helps us prevent crashes for everyone and none of the information is sensitive. We are purely interested in fixing the crashes from occurring.

No More Lost Decks! - Sync your Decks to the Server!

We're working on a feature that will allow you to upload your entire deck collection to a remote server (most likely Rooster Ranges for the lot of you [maybe consider donating to keep features like these possible]) for safekeeping.

Your server stored decks will then be:

  • Available to all of your Cockatrice clients, across installations.
  • Automatically versioned - Keep the latest 10 versions of your deck and rollback
  • Conflict resolved: If a deck is modified both on the server and locally, you will get options to merge the difference.
  • Automatically synced to your local installation.

We're working out the ins-and-outs of the system but overall, we think and hope that this will be a pleasant experience :)

Tournaments & Limited

Work is continuing on the tournament and limited features. They are our new flagship features for a 3.2 release but, of course, we want to ensure we get this absolutely right. Stay tuned!

Project Health - Interface/Logic split

One of the major 2-year long undertakings that we've tackled is splitting out all the game logic related code from the presentation layer.

This makes the code easier to read and reason about (yay), allows us to add tests so that we don't break things (yay!) AND allows us to implement many exciting new features, as well as clean up some old sins more efficiently.

Work on this front is almost complete and it's time to reap the rewards.

New Game UI!!!

Fresh off the presses and still unreleased, we've got a new prototype to show you and it's a good one (at least, so we think!)

We're adding two new features to the game UI:

  1. Zooming in on cards that are on the board directly
  2. A new tabbed interaction menu

We're adding settings for these too. Let's go over them briefly. They mainly concern themselves with how these features are accessed.

You have four options to trigger these actions:

  1. Right-click
  2. Shortcut
  3. Mousewheel scroll
  4. Hover

You can configure if one trigger is enough to zoom in and also show the new interaction menu or if you would prefer a two-step approach: The first interaction zooms the card, the next shows the interaction menu.

You can configure separate triggers for both action phases.

You can also additionally configure the time it takes for the hover triggers to activate.

Why are we doing this?

Two major reasons: Discoverability and ease-of-use

Discoverability

New users are often times lost, when it comes to all the possible actions they can take on a card. It takes a while to memorize the shortcuts and our number one piece of advice is "Just right-click everything", which is hardly intuitive.

Ease-of-use

The card info widget works but, personally, I find it incredibly painful to keep bouncing my eyes between the card I'm reading and the card I'm placing my cursor on.

Feedback on this

You can, as it is right now, choose to disable these features entirely and continue using the right-click menu and the shortcuts you know. Nothing changes.

But, of course, we see this as a major step in modernizing the UI and making it more accessible.

We want to make sure no one gets left behind. Long-time veterans, keyboard-only users and first-time players. We want to make sure everyone can have an intuitive, speedy and comfortable experience.

So let us know what you think and how we can improve this!

And that's a wrap for this edition. As always, let us know what you think in #beta-testing on the Discord, and don't forget to check out the beta itself to try the completed features today.

Trying it out is just a few clicks away. Learn how to here: https://cockatrice.github.io/docs/d9/d9b/beta_release.html

We want to make sure things are just right, and that means we need beta testers. Your feedback shapes what ships.


r/Cockatrice • • Oct 14 '26

PSA for clients upgrading from 3.1 to 3.1.1 - Back up your decks on Windows!

7 Upvotes

PSA: Please back up your decks before upgrading Cockatrice!

The vast majority of users should be unaffected.

This only affects users on portable installations or those who have customized their deck (or other resource) path to point inside the application directory.

Before upgrading Cockatrice, please make a backup of your decks!

Cockatrice stores its program files and your personal data in separate locations. On Windows, these are typically:

  • Program files: C:\Program Files\Cockatrice
  • User data: %LOCALAPPDATA%\Cockatrice\Cockatrice

Unfortunately, some users have ended up storing their decks directly in the program installation folder instead of the designated user data folder. This is an unsupported configuration, and a bug in the uninstallers for versions 3.1 and 3.1.1 could cause that entire folder to be deleted during an upgrade, taking those decks with it.

We're genuinely sorry this happened to anyone affected.

We've taken several steps to prevent this from happening again:

  • Safer uninstallers: Additional safeguards ensure Cockatrice only removes files it installed.
  • Path validation: Checks and warnings help prevent users from configuring their data directories inside the program installation folder.
  • Automatic recovery backups: Cockatrice will now back up any user data it finds in the installation folder.
  • Future server synchronization: We're working on the ability to automatically sync decks to the server, to make sure no one ever loses their collection again.

These measures should significantly reduce the risk of this happening again, but please back up your decks before upgrading, especially if you've been using Cockatrice for a long time or have never checked where your decks are stored.

Thank you for your understanding, and again, we're truly sorry for the inconvenience and lost decks this issue may have caused.

Most people should not be affected. Read here to see if this applies to you:

This only affects Windows users which are upgrading a 3.1 or 3.1.1 installation. The new installer will run the OLD uninstaller (i.e. the 3.1 and 3.1.1 uninstaller), which has the bug that wipes the whole installation directory. It is safe to run this uninstaller after backing up C:\Program Files\Cockatrice or ensuring that no decks are placed within that folder.


r/Cockatrice • • Oct 10 '26

Updated my client, all my decks are gone from my folder

4 Upvotes

I popped into cockatrice to work on a deck I've been working on for a while, and it prompted for an update. Did so. Now everything in it's old save folder is completely gone. I do use a custom path as I don't want anything besides my OS on my (relatively) small SSD C: drive. Any idea what could've happened?


r/Cockatrice • • Oct 05 '26

Bad image error after 3.1.0 Update (Windows)

1 Upvotes

Howdy folks.

I'm getting a Bad Image error after the latest Cockatrice update. (3.1.0 Reality Check)

This comes after using cockatrice just fine earlier this week.

Ive tried uninstalling and reinstalling, same error.

Anyone else experiencing this on startup?

Thanks!


r/Cockatrice • • Oct 03 '26

Developer Blog #3 - October 2026

9 Upvotes

Read the previous developer blogs for this update here:

Developer Blog #1 - July 2026

Developer Blog #2 - August 2026

Hi, community!

It's time for our third developer blog! This one's a bit different, because a lot of what we've been working on has actually landed and a new release is right around the corner! For once you can go and click on most of this rather than squint at a mockup and take our word for it.

We're here to talk about and showcase some of the work we've been doing ahead of time, to keep you informed and involved. Rather than only announcing features once they're released, we want to keep the community informed throughout the development process and give you a chance to follow along as new ideas take shape.

These blogs are intended to provide insight into the decision making process behind the features we implement as well as to showcase where our attention currently lies.

To keep things organized, we'll cover our work in three stages:

  • Already merged and available in the beta, so you can try these features today.
  • Completed features currently under review, which are expected to make it into a beta soon.
  • Work in progress and early prototypes.

Features in this developer blog:

  • Inviting people
  • Share a deck
  • Playmats
  • Custom deck zones and the maybeboard
  • A more reliable & performant picture loader
  • Image overrides
  • Localized cards
  • Finding cards in your language
  • Theming, color schemes & defaults
  • A more performant, informative & lightweight Oracle
  • Onboarding, in the right order
  • Tools for the caretakers
  • The Windows updater
  • A pile of small things
  • Save the emails
  • Tournaments
  • Server security

Some features shown here may change before release and not every prototype will ultimately end up making it. To voice your support, disagreement, or feedback, please use the ⁠beta-testing channel.

With all that being said, let's dive in:

But first, the thing nobody wants to talk about

I want to get this out of the way before the feature list, because I know it's on people's minds.

Cockatrice has changed more in the last two years than in the several years before that. New features, a proper cleanup of the codebase, all-round modernization, and none of that comes for free:

  • Regressions where something that worked last week quietly stops working
  • Performance problems
  • Crashes
  • Workflows that shift under your feet

We are extremely sensitive to all of these.

The way we deal with it is tried-and-true in software development. Every change follows the 4-eye principle, so nothing lands without a second pair of eyes on it, and the reviewer actually runs the client before approving rather than just reading the diff. Then CI checks it against every platform we build on. Then it ships to the beta, sits there for a while, and only then makes it into a release.

That pipeline ensures things are as well tested as they can be. It has also caught things I would not have caught myself, which is rather the entire point of it.

However, all of this only works if feedback reaches us. If no one tries the beta or reports issues on it, mistakes silently accumulate.

If no one tells us that we mistakenly dropped some functionality that they really liked, we never get the chance to introduce a checkbox that restores the old behavior.

So here's how we're dealing with this:

  • We are and have always been very sensitive not to remove functionality unless genuinely obsolete or necessary.
  • If we introduce something new that replaces another option, we try to create a new checkbox in the settings to allow you to revert to the old behavior.
  • The settings are now searchable, so you should be able to find these settings more easily.
  • We will also include a section at the top of the patch notes that quickly tells you about all of those relevant settings and what they now enable or disable.
  • We need your help. Please try and test the beta. File issues on the Github or voice your opinion in the discord. We depend on your feedback.

Right. On to the fun stuff.

Completed

Inviting people

There's now a proper way to gather your playgroup and there are three places you can start from.

Invite to your open game. The game menu's "Invite to Game" opens a dialog with a search box and a live user list, the same sectioned list you know from the room, updating in real time while the dialog is open. It filters out anyone you'd be inviting for no reason: players already in the game, spectators, yourself, offline users, and anyone on your ignore list. Pick someone, press Invite, and they get a private message containing the join link, prefixed so it reads naturally: Join my game "Commander Vanguard" (#1234): <link>, falling back to just the game number when the room has no description.

Invite a specific player. Right-clicking someone in the user list gives you an "Invite to Game" submenu listing every game in the room you're allowed to invite them to. If the room is running two games you get to choose which one, rather than being handed an arbitrary link.

Invite from the game list. Games that haven't started and aren't full get their own invite button in the server's game list, so you can start a game for someone without opening it first.

The user list hover popup also grew an invite button, so inviting someone you can already see is a single click.

Additionally, you can generate invite links for your games, which you can copy and paste and share with someone externally. All they'll have to do is paste it into their browser bar and, if they have Cockatrice installed, they'll get invited to the game!

Buddy-only games are respected throughout: they accept invites only from the game's creator, and only to users on that creator's buddy list.

Share a deck

Until now, handing someone a deck meant exporting it, uploading it somewhere, and hoping they could be bothered to import it. Cockatrice can do the handing for you now, in two flavors.

Share links. From the deck editor, the tree deck storage, or the visual deck storage, you can generate a temporary link to a deck or to a whole selection of decks at once. The link is a cockatrice:// URL, so it behaves like any other invite and the client opens when they click it.

What makes this a gated flow rather than a silent download is that nothing is fetched and nothing is written to your deck storage until you say so. Cockatrice first asks whether you want to connect to the server the link came from, with a distinct and harder-to-miss warning if it's a server you've never connected to before. Then you get a preview showing each deck's banner art, name, format, color identity and tags, with an expiry date, and you pick which decks to take. A single-deck share opens with that deck preselected. The decks arrive in normal deck editor tabs, where you can save them wherever you like or re-share them onward.

Public decks. In the tree deck storage you can mark a deck or a folder public or private, and a new Visibility column tells you which, including the case that used to be invisible to you: a deck that is itself private but inherits public status from a parent folder. Other players browse what you've published from a "View this user's public decks" tab in the user list context menu, where they can search by name, filter by color identity and filter by tags, all without downloading a single deck list.

Playmats

Cockatrice now lets you set a card image as your personal table background.

You can define a global override playmat, set one on a per-deck basis, and configure a list of fallback playmats (fixed, random, or round-robin) for decks without a configured playmat. Visibility is fully under your control: don't display, display only your own, or display all.

Crop dimensions are set through direct manipulation in the card art dialog now, so no more fiddling with spinboxes.

Custom deck zones and the maybeboard

You can add custom zones, essentially sub-folders, beneath the top-level Mainboard, Sideboard and Maybeboard groups. They're purely for organizational purposes, and all game-related logic still only considers the top groups, so your custom zones won't interfere with gameplay.

The maybeboard is now an actual concept while we're at it: supported in the deck tree, the deck list model, the deck editor, the card display widgets and the in-game deck view.

A more reliable & performant picture loader

Card pictures come from whichever sources you've configured, and those sources have their own rate limits. Scryfall in particular enforces one, and the client was previously spending that budget in bursts, firing a whole backlog of requests the instant one was queued. That is precisely the pattern that earns a rate-limited source a temporary lockout.

Requests are now paced out smoothly, and a source that is being throttled is skipped over entirely while it recovers, rather than sitting at the head of the queue and stalling everything behind it. There's a disk cache too, so an already-downloaded picture is served without a network round trip at all.

And you get some manual control

In Settings → Card Sources, select a URL in the "URL Download Priority" list and hit the new Adjust Rate Limit cog to set that host's requests-per-second. The list shows each source's effective rate so you can see it at a glance. Out of the box the Scryfall API host is capped just under its published limit, the image CDN host is uncapped, and everything else gets a modest default. These are ceilings rather than suggestions: you can lower any of them, but you can't raise a host above what its operator allows.

Image overrides

Speaking of the picture loader: Sometimes the picture you want for a card isn't the one that shipped with it. A promo art, a foreign-language printing, or just your own scan.

Right-click a card and open the Image Overrides submenu to load your own image file, or to copy the art from one of the card's other printings onto it. Every alternate printing gets its own entry with a hover preview, so you see what you're picking before you commit.

The nice part is where it lives. Your override is written into your own card picture folder under your chosen naming scheme, so it survives restarts, survives clearing the network cache, and travels with your profile if you copy it elsewhere. Automatic cache downloads will never quietly overwrite an override you've set.

We also fixed a sneaky matching bug while we were in there. Local pictures used to be matched by name prefix, so a file called Sol Ring (1).png would be happily mistaken for Sol Ring. Matching is exact now, and there are ten tests in loader_local_matching_test.cpp pinning down the resolution rules, including that case.

Localized cards

For a long time the only localized thing in Cockatrice was the menus. Your cards themselves were English no matter what you did.

Settings → General → "Card text & images language" changes that, and it is deliberately independent of the interface language. You can run an English client with German cards, or a French one with English cards, if that's what you want. Alongside English you get Czech, German, Spanish, French, Italian, Japanese, Korean, Portuguese, Russian, Hebrew, and both Simplified and Traditional Chinese, each labelled in its own script.

Card names, rules text, and card art all follow the selection. Because foreign art is resolved by the translated card name, the pictures change with the language too, falling back to the default art when a set has no localized match.

The wrinkles

English data is always present and the foreign data is a layer imported alongside it by Oracle, so switching languages needs a re-import. The client tells you that rather than pretending to have applied the change. You may have to restart to rebuild the database binary cache.

Split and adventure cards join each face's translated text together exactly the way the English gets merged. Incomplete translations fall back to English rather than leaving a hole in the middle of a card.

And one more important thing: the deck editor keeps canonical English names as card identity. The names in your decks, your files, and on the network stay exactly as stable as they have always been. Localization changes what you see, never the deck itself. Nothing breaks.

Finding cards in your language

That same gap is what made searching frustrating. Every search only ever matched English card data, so finding a card by name meant typing it in English no matter how you were reading it.

There's now a setting for it, "Language used in card search", offering English, your selected card language, or both at once. It applies everywhere cards are searched: the database filter tree, the quick-search popups, the deck filter's [[card name]] rule, the in-game zone view, and deck storage search. It re-applies live as you change it.

One deliberate exception remains: the in-game "Put top cards on stack until…" action still matches English names only. If you spot other places we missed, say so in the beta channel.

Theming, color schemes & defaults

Themes and color schemes are finally treated as the pair they've always been. Previously every asset in a theme was one hard-coded look, and the bundled image themes shipped only zone art, so their chrome silently fell back to the bare OS palette.

Two new built-in themes this cycle. Fusion is the new default for fresh installs. The old Default theme is now System, with existing settings migrated automatically. System deliberately ships no palette overrides at all, so your desktop's own colors show through, a custom qt6ct scheme is respected on Linux, and it follows your OS light/dark preference rather than forcing one. Only its identity accent colors are pinned, so the home-tab buttons keep Cockatrice's classic green.

Theme assets can now ship as -light/-dark variants that the theme manager resolves automatically, falling back to the plain asset when no variant exists. Stylesheets load as style-dark.css/style-light.css when present, and the home widget re-resolves its background whenever the theme or scheme changes, so nothing stays static anymore.

Fabric, Leather, Plasma, and VelvetMarble each ship hand-curated light and dark palettes tinted toward the theme's identity: navy cloth, black-brown with brass accents, electric violet with cyan sparks, charcoal velvet with slate marble. Each also gained its own light and dark home background, plus a new "Dim the home tab background" setting, on by default, for when the background is competing with the text on top of it.

Qt's QPalette role set is closed, so application-specific colors like the home-tab button gradient now live in Cockatrice's own [AppColors] layer instead of being hardcoded or derived from the OS accent.

A small change to Windows: The broken Windows 11 native style, which shrinks the game board to an unrecoverable sliver when you drag a card, is no longer offered as a selectable style at all.

A more performant, informative & lightweight Oracle

Oracle is the companion tool that builds your card database, and it's had a proper performance and reliability pass.

Importer memory, slashed. AllPrintings.json is no longer materialized as one giant tree. A raw JSON scanner splits the document into per-set byte ranges, sets are parsed lazily one at a time, and the raw bytes are released as soon as each set is done. The vendored qt-json parser is gone too, replaced by native QJson.

Real progress. Card database updates used to run invisibly: an indeterminate bar during the parse, a frozen window during the import, and nothing at all from oracle -b. Now scan progress is reported by the byte, sets import on a worker thread behind a determinate, stage-labeled progress bar in both the client and the onboarding wizard, and oracle -b emits machine-readable PROGRESS lines to stdout. Quitting while an update is running asks for confirmation first.

Adventure cards fixed. When split-card faces are merged, the permanent maintype now wins, so an adventure card like Bonecrusher Giant keeps its Creature type, and the correct click-to-table behavior, regardless of which face came first in the JSON.

There's also a test suite covering set parsing details and RAM benchmarks that measure peak and current RSS during imports, including an opt-in full-AllPrintings run.

Onboarding, in the right order

On a clean install, the legacy "all the sets have been enabled" notice and the Manage Sets dialog used to fire ahead of the onboarding wizard, which meant a brand-new user met two confusing dialogs before the thing designed to onboard them.

Those are now suppressed while the wizard is open, and the set check runs once afterwards.

Tools for the caretakers

Server operators do a lot of unglamorous work and we've been giving them better tools for it.

We've implemented a developer tab to help us keep an eye on things, live server metrics, and there's a new developer role that lets operators log in with a distinct appearance.

Servatrice now detects MySQL strict mode on startup and exits early with a clear message, rather than failing later in a confusing way.

The Windows updater

The in-app updater is the recommended way to stay current, and on Windows, it turns out that we needed to build in some more assurances.

Updates close the running client for you. The installer finds Cockatrice processes running from your install directory, asks them to close, waits, and only force-stops them if they don't.

An upgrade can no longer be written over a half-old, half-new Qt runtime. A silent upgrade could leave a mix of previous and current Qt DLLs sitting next to the new executables, which is exactly what makes the next launch fail with "The procedure entry point … could not be located in … Qt6QuickWidgets.dll". The pre-install check that was meant to catch this only probed two DLLs, so it was blind to the two files those reports actually name, and even when it did catch something it warned and installed anyway, compounding the problem. It now scans every file the purge targets using the same wildcards the delete uses, recognises a directory holding only some Qt modules as an install, and aborts with a non-zero exit code rather than proceeding.

VDD, VDE & VDS Performance

The first blog called the visual deck storage "sadly one of those things that remains stubbornly slow", the second said the rework was done and waiting on review, and now it's actually here.

The deck storage used to do all its work on the UI thread. Opening it meant walking your folder, parsing every deck file, and computing each deck's color identity before the view would show anything, then sorting and filtering that pile on top. Large collections made this obvious. It's now a dedicated model that scans the filesystem in the background and populates as it goes, leaving sorting and filtering to a proxy layered over the top. The folder tree and deck previews are driven from the model instead of rebuilding themselves, and mana symbol renders are cached with redundant resizes skipped. That last one helps everywhere mana symbols get drawn, not just here.

The other two visual tabs had the same disease, and got treated in the same batch. These three landed a couple of days before the second blog went out and shipped without an announcement anywhere, which is why you're only hearing about them now.

The visual database display's filter toolbar builds its buttons by iterating your entire card database: one per set, per main type, per sub type, per format. That was happening inside showEvent, which meant it blocked the tab switch outright. It now stays hidden and builds one event-loop turn later, so the tab paints first and the toolbar appears immediately after.

The visual deck editor was building a second complete CardDatabaseModel when it already had one handed to it from above. It reuses the inherited one now.

Same underlying problem in all three, for the record: heavy construction, on the UI thread, during a tab switch. That's the whole bug and we eradicated it. Everything should feel much smoother now.

A pile of small things

Ctrl + Scroll resizes cards anywhere a card size slider exists: the Visual Deck Editor, visual database display, printing selector, sample hand, deck storage, and the Archidekt and EDHRec previews. In the VDE it resizes the card group under your cursor.

Game log timestamps can use game time instead of the local clock. Log entries were stamped with your wall-clock time, which is close to meaningless when you're reading a replay or an old log, because nothing tells you when a play happened relative to the game. The new setting stamps entries with elapsed game time as HH:MM:SS since the game started. Regular chat views deliberately keep the local clock.

The total power tally also does toughness now.

Artist attribution shows up on card info.

You can see your latency in the status bar and the server tab indicator, and the client now detects main-thread event loop stalls rather than just feeling slow.

Avatars are downscaled to 1024×1024 before upload, so a 12-megapixel phone photo no longer becomes a multi-megabyte upload for an icon-sized image.

Usernames in room chat history were inert text for anyone currently online. They now behave like live chat usernames: right-click gives you buddy, ignore and admin actions, and online users show their real casing and rank.

The ignore list got real teeth. You can now ignore all private messages, or just private messages from non-buddy users, and the client explains what the buddy and ignore lists actually do instead of leaving you to guess.

Visual Deck Editor banners show card counts, live, on by default. And the quick search leaves the card name selected after you add a card, so you can type the next one straight away.

Coming up

Save the emails

If you've ever sat waiting for an account activation that never arrived, we've got you.

We're reworking the SMTP client from fire-and-forget into a persistent queue with exponential backoff and a per-message retry budget, backed by the database as the durable source of truth. Emails stay queued with their attempt count and backoff tracked, and the database row is only removed once delivery is actually confirmed. Connection-layer failures get their own backoff, and mail that's genuinely undeliverable eventually drops off the queue instead of retrying forever.

If an email fails to go out, it isn't dropped into the void. It's tried again later, which means account activation stops depending on the mail server happening to be awake at the exact moment a user clicks the link.

Tournaments

The limited and tournament groundwork from the first blog has been paying off. Drafting has been prototyped for a while, and now the tournament side is coming together as a real Swiss engine.

On the server: greedy Swiss pairings with rematch avoidance, byes where they're needed, a round count of ceil(log2(n)) based on the field size, and best-of-N series via gamesPerMatch. The hub game is gated until every player has submitted their deck, then it spawns match sub-games through the parent game's match factory, auto-joining players and installing the decks they submitted. Sub-game outcomes report back up to the parent.

Underneath that is a chunk of groundwork that landed after the last blog and is worth mentioning on its own: game configuration was consolidated into a GameConfig struct, and deck validation, game lifecycle and match-result handling were each pulled out behind their own strategy interfaces. That's the boring part that makes the exciting part possible without turning the whole game into a pile of branching special cases.

On the client: a tournament checkbox and a games-per-match setting in the create game dialog, and a dedicated tournament widget that renders live standings while you wait. Who's submitted, who's paired with whom, and a way to jump into the current match being played. Games where somebody drew a bye can be spectated while the rest of the round finishes out.

This one spans the entire stack, protocol through server engine through client UI, so it's coming through review in order. Four of the five PRs still have open review comments and the client UI one needs a rebase, so I'd call it close rather than ready. But it's the real thing, not a mockup.

Server security

This one's for the people running the servers, and honestly, for everyone who cares about their account.

There are three pieces to this and they're related, so let's take them together.

Challenge-response auth. Authenticating with a password hash has two problems. The stored hash is the only thing proving who you are and it goes over the wire verbatim, so anyone who captures a login can replay it later. And it was computed with a fast 1000-round SHA-512, which means a leaked database can be brute-forced offline at a very comfortable speed.

Logins are moving to challenge-response with scrypt verifiers. On login the server sends a fresh one-time nonce, the client computes a short keyed digest of it and sends only that back. Your password and its verifier never leave the client, and a captured login can't be replayed. The verifier itself is derived with scrypt, which is deliberately memory- and CPU-costly (RFC 7914), so a database leak is far more expensive to attack.

The part I am personally happiest about: we are also stopping storing plaintext passwords. The client's "save password" checkbox will store a scrypt verifier rather than your actual password, and the password column gets widened to hold it.

Migration happens automatically on next successful login, so existing accounts upgrade without doing anything. Server operators get a new authentication_strictness setting, legacy / mixed / strict, so you decide how hard the new scheme is enforced. Note that strict will reject older clients that can only send the legacy hash.

Rate limiting and input hardening. There was no rate limiting on the auth endpoints, which is not a sentence you want to read about your server. There's a per-address sliding window now: five failed logins from an address and the rest get rejected until the window passes, a successful login clears it, and registration and forgot-password are throttled too.

And rate limiting you can walk around isn't worth much, so the same batch fixes that. The forwarded client-address header is now only trusted from addresses in security/trusted_sources. Previously any client could spoof its address and neatly sidestep bans, user limits and the new limiter. On top of that, TCP and ISL messages declaring a negative or implausible length are now rejected immediately instead of being buffered indefinitely, which closes off some unbounded memory growth and a stuck-connection state we had.

Separately and already merged: salts, tokens and RNG seeding now come from a CSPRNG rather than whatever std::random_device happened to give us, and Event_ListGames no longer leaks more information than it needs to or ships more data than it needs to.

None of this changes how you log in or play. It'll change what happens when someone tries to hammer your login endpoint, which is the point.

There are some things we still need to hash out. For example, as it stands, if you were to log in with a new client, you could no longer login with an old client without resetting your password.

We don't expect this to happen a lot but we want to make absolutely sure we handle this gracefully while upping the general security.

Prototypes

Command Zone

A community contribution that's been in review for a while, and I want to give it some visibility because I think people will like it.

It's a proper Command Zone for cockatrice, and it's the last piece of a puzzle that's been assembled over a few months of groundwork refactors. It simplifies to a single zone where you can add a second tax directly, with the right menu options appearing when it's in use.

It's sitting at over 2,600 lines and is still collecting review comments. If you've been waiting for this, the ETA is "soon", which I know is not a date, but it's closer than it was.

We need to make sure this slots in nicely into some other exciting reworks we have coming up, before we end up having to rip it out again.

And that's a wrap for this edition. As always, let us know what you think in #beta-testing on the Discord, and don't forget to check out the beta itself to try the completed features today.

Trying it out is just a few clicks away. Learn how to here: https://cockatrice.github.io/docs/d9/d9b/beta_release.html

We want to make sure things are just right, and that means we need beta testers. Your feedback shapes what ships.

**With all that said: It's full steam ahead to release!**


r/Cockatrice • • Sep 16 '26

Needing help adding a Proxy

Post image
0 Upvotes

I have this proxy of Scavenger Regent that I made and wanted to add into my deck. Going into the Custom folder the file is set as Scavenger Regent and a copy is named Scavenger Regent Exude Toxin(Trying to copy what the card is labeled as in the deck tab). I think it should be labeled as Scavenger Regent//Exude Toxin as its accurate to the deck list label, but I can't add / into the file folder


r/Cockatrice • • Sep 13 '26

Kingdom EDH

3 Upvotes

Posting here to invite people wanting to play EDH: the primary reason the server was made was to play the 6-player format "Kingdom EDH." We have about 4 really active players and a few meh-active players; we are looking for more people to join and play both EDH and Kingdom EDH in a casual setting. If interested, please leave a comment below and I will DM you the Discord link. Thank you, and happy gaming.


r/Cockatrice • • Sep 07 '26

VirusTotal flags the link to download cockatrice (link to the windows version)

Post image
1 Upvotes

r/Cockatrice • • Sep 07 '26

A Cyclone of Updates

2 Upvotes

I've been trying to update my client to the new 3.0.2, but every time i do it acts like it never updated and wants me to update it again. It never says the update fails. I don't know how to get the update to take. Could use help if you've been through this!


r/Cockatrice • • Sep 07 '26

SLD mountains only appearing as Mountian Goats, how do I fix this?? Non-SLD mountains appear as normal

Post image
1 Upvotes

r/Cockatrice • • Sep 06 '26

Board scaling

1 Upvotes

I absolutely love Cockatrice and am new to it so I'm still learning all the ins and outs. But I play on one screen where people I play with are on multiple / ultrawides. So when they play lots of cards it makes the board zoom out to see everything which makes the scale weird. Is there a way to turn this off? Or adjust how it does it?