Where the Card Data Comes From

Where the information starts

Card names, rules text, artwork, collector numbers, rarity, and artist credits are source material. Riot Games creates the cards, and public archives make much of that information available to tools like this one. Nexus-Atlas uses those records to build its English card database.

The site's own work is in how the information is organized and used: bringing matching records together, keeping printings distinct, showing connections in Atlas and Galaxy, and helping you move from browsing to a deck or collection entry. These guides explain those tools and the choices behind them.

Why a card can have information from two places

One archive may have a useful artist credit while another has clearer treatment information or a collector number. When the records refer to the same printing, Nexus-Atlas can combine the details. That is more useful than showing two incomplete entries for the same physical card.

Matching takes care. Similar names alone are not enough, especially when a champion appears on several different cards. Set and collector details help establish which records belong together. If those details do not support a match, the entries need to stay separate.

How updates reach the site

The card archives are fetched when the site is built for a release. Nexus-Atlas checks the records and prepares a card-data file for visitors to load. Your browser uses that file rather than having to ask every upstream archive for its own copy on each visit.

This means the public catalog reflects the last successful site build. A card announced today may reach a source archive before it appears here. A source update can also require a small repair to the map or a correction to how the new printing is grouped.

If the live sources cannot be reached, a normal release stops. Keeping the previous working catalog online is preferable to replacing it with a much smaller sample or incomplete update.

What gets checked before a release

The checks cover the card list, known release numbering, standard tokens, card-page links, and the Galaxy map. Every retained printing needs a route to its card page and a place in the visual catalog. Newly added cards should not disappear simply because one part of the site has not caught up.

These checks catch missing records and broken connections, but they cannot prove that every source field is correct. A collector number copied incorrectly upstream can still need a human correction. Reports from people comparing the database with their cards are valuable for exactly that reason.

Read summaries alongside the card text

Card-page descriptions summarize the fields in the database. They help you find the page and understand its contents quickly. For the card's actual wording, read the rules text and inspect the printing itself.

Mechanic explanations provide context and link to an official rules source when one is available. If a question affects a tournament ruling, use the current official Riftbound rules. A browsing tool cannot settle every interaction that comes up during a game.

Send a correction that is easy to check

A useful report includes the page link, full card name, set and collector number, what the page currently says, and what you believe it should say. Add a reliable reference if you have one. That gives us enough detail to check the source record and the way Nexus-Atlas uses it.

You can also report broken artwork, confusing controls, or accessibility problems. For a display issue, the browser, device, and view you were using are helpful. Keep private account information and anything you do not want published out of the public issue tracker.

The contact page links to that tracker. Whether the problem is in the source data or in the site, a specific example makes it much easier to find and correct.