So, I Built a Card Database
Why Riftbound FAQ now has a card database, what it does, and what it deliberately will not become.
A few weeks ago, in The Future of Riftbound FAQ, I wrote that I did not plan to build a comprehensive card database like Scryfall. That sentence has aged poorly. Riftbound FAQ now has a Card Database.
I am aware that this is exactly the kind of feature I had explicitly declined to build. The reasons for that decision have not gone away, either.
Why I was reluctant
Building the pages and search interface is not the hardest part of maintaining a card database. The difficult part is assembling correct information about every card.
Card data is distributed across several sources, and I do not have access to one source of truth that is complete and consistently correct. Some information is missing, some is inaccurate, and differences between sources need to be investigated rather than accepted automatically. The database therefore collates information from multiple sources to provide as much useful detail as possible. It also requires manual corrections when those sources are incomplete or wrong.
That process is arduous, and it creates an ongoing maintenance commitment rather than a one-time development task. The database should be treated as an early preview for that reason. There will be incorrect or missing information, particularly while I continue reviewing the existing card pool.

Why I changed my mind
Riftbound FAQ began as a way to help players and judges find answers to common rules questions. The Card Text Updates page expanded that idea by providing a reference for printed text that has received errata. The Rules Documents section made current and historical rules easier to navigate and compare. A card database is another step in that same direction.
If you are already using the site to check a ruling or confirm current card text, it is much easier to quickly search for another card without leaving the website. It also gives rulings, errata, and card information a more useful shared home over time. In the future, detailed card pages will also be able to link directly to relevant rulings and card text updates that already exist on the site, making those references easier to discover together.
I want to build tools that act as practical references for judges and players. This is another way for me to give back to the community that has supported and improved this project.
What the database does today
You can currently search for a card by name, browse galleries through the Set Directory, and open a page for a specific printing. Those pages bring together current card text, characteristics, format legality, set and collector information, artists, and other known printings.
Search is deliberately simple at the moment. It supports card names, without advanced filters or a search syntax. I am considering adding more powerful search capabilities over time, but that will depend largely on whether the community finds the card database useful in the first place. I would rather learn how people actually use it before committing to a large filtering system.
Current coverage is primarily focused on cards from regular sets. Promotional cards and their many variants are a lower priority for now and are more likely to be incomplete.
Card links without a dedicated bot
Every card printing has its own URL, which makes it easy to reference a specific card in a ruling, message, or community discussion. When one of those links is posted on a platform such as Discord, it can display the card and its text directly in the link preview. The people in that server do not need to install a dedicated bot or remember a bot command before they can see which card is being discussed. They can often get the necessary context without even opening the website. That may sound like a small convenience, but quickly sharing an exact card is useful when answering questions across several different communities.

What this will not become
The card database does not mean that Riftbound FAQ is becoming an all-purpose Riftbound platform. I am not going to build a deck builder, collection tracker, metagame analysis platform, or price checker. Those are not hidden items on a long-term roadmap. I am very confident that they will never be within the scope of this project.
Other resources already serve those needs. The official Riftbound Wiki contains extensive information about the game and its cards, while projects such as Piltover Archive provide card search, deck building, and metagame tools. Riftbound FAQ's card database exists in addition to those resources, not as an attempt to replace them. Its purpose is narrower: to provide a convenient card reference alongside the rulings, errata, and rules documents that are already here.
Yes, it looks like Scryfall
I do not want to beat around the bush: the card database deliberately uses a design and layout similar to Scryfall. The reason is simple: it works.
The Scryfall team has spent ten years building and refining a stellar card-reference experience. That work contains lessons and proven interaction patterns worth carrying over. I would be stupid to ignore what has already been established to work merely for the sake of making this database look different.
That does not mean I intend to reproduce every Scryfall feature. I am borrowing familiar ideas for search, set galleries, card details, and printing navigation while keeping the scope appropriate for Riftbound FAQ.
Keeping it current
I will periodically add new sets and cards, and correct missing or inaccurate data as time permits. There will not be a fixed update schedule. Regular releases will generally take priority over comprehensive coverage of promotional variants.
You can submit corrections through the feedback control at the bottom of every card database page. The page where you submit feedback is included automatically, so you only need to describe what appears to be wrong.
Feedback about the feature itself is equally useful. In particular, it will help me decide whether advanced filtering and search syntax would meaningfully improve the database.
I said I would not build a card database, and then I changed my mind. I changed it because a focused card reference supports the same goal Riftbound FAQ has had from the beginning: helping players and judges find, verify, and share useful information. If it makes that work a little faster, the maintenance will have been worth it.
How was this page?
Written by Christian “Near” Ivicevic.
Last updated on .