> For the complete documentation index, see [llms.txt](https://studio0.gitbook.io/tome-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studio0.gitbook.io/tome-docs/collection-and-card-ids.md). # Collection & Card IDs | Command | What it does | | ------------------------------ | ----------------------------------------------------------------------------------------------------------- | | `%collection [@user] [search]` | Look through a collection, newest cards last. Add a user to see their cards, add a search to narrow it down | You get 10 cards per page with buttons to flip through. Each line shows the Card ID, wishlist count, any tags, a status emoji, stars, mint number, and any tags on it. ## Card ID vs card code Any command that needs to know which card you mean (`%tag`, `%view`, `%sell`, `%gift`, `%trade`, `%equip`, `%upgrade`, `%melt`, all of them) will take either of these: * Card ID: the number next to a card in `%collection`, like 1, 2, 3. It's just your own personal list order based on when you got each card, so it can shuffle around if cards leave or join your collection (like after a trade). Fine for quick use right now, not something to write down for later. * Card code: a short code like `n7FQHj` that gets handed to a card the moment someone claims it. It never changes, it's unique to that one copy across the whole bot, and it's what actually gets used behind the scenes whenever you trade, gift, or sell something. Totally safe to write down or send to a friend. A Card ID points at your own collection unless you're checking someone else's on purpose (`%view @user`, `%lu @user`), in which case it points at theirs instead. Several commands (`%tag`, `%untag`, `%equip`, `%upgrade`, `%melt`, and offering cards mid-trade) let you list more than one Card ID at once, comma or range separated, like `275, 274, 265-260`, to act on all of them in a single command instead of running it over and over. ## Melting dupes Melt cards down into Gold, either specific copies you pick, or just the spares beyond your first of something. | Command | What it does | | -------------------- | -------------------------------------------------------------------------------------------------- | | `%melt ` | Melt specific card(s) outright, even if it's your only copy. Comma or range separated for multiple | | `%melt ` | Melt every extra copy of a card beyond your first (your best copy stays safe) | `%melt` (aliases `%convert` / `%cv`) reads what you give it: a Card ID or code (or a list of them) melts exactly those cards, your only copy included. A card name instead falls back to the older behavior, melting just the spares beyond your first copy and leaving that one alone. There's no mixing the two in one command; if what you typed doesn't resolve to any owned Card ID or code at all, it's treated as a name. How much Gold a copy is worth starts from its stars, then scales up the earlier its print number is, the exact same rarity curve `%lu` uses for value, so an early mint duplicate is worth meaningfully more melted down than a late one, not just at face value. The 1 through 5 star values track actual pull odds closely, so melting nets you roughly the same expected value no matter which star you happen to land on. Ascended (A1 through A5) tracks how many identical dupes `%ascend` actually needs to reach each level instead, so the jump into A1 (the hardest wall in the game) is the single biggest one on the whole table: | Stars | Base Gold | Mint #1 | | ----- | --------- | ------------ | | ★ | 10 | up to 30 | | ★★ | 15 | up to 45 | | ★★★ | 25 | up to 75 | | ★★★★ | 50 | up to 150 | | ★★★★★ | 150 | up to 450 | | A1 | 3,000 | up to 9,000 | | A2 | 6,000 | up to 18,000 | | A3 | 11,000 | up to 33,000 | | A4 | 18,000 | up to 54,000 | | A5 | 28,000 | up to 84,000 | That mint bonus tapers off the higher the print number climbs, gone entirely by print #500. See Card Valuation for the exact curve. ## Tickets and the guaranteed pull Tickets come from daily quests and finishing a whole series, not from melting. See Currencies & Daily Rewards for where they come from. | Command | What it does | | -------------------------- | ----------------------------------------------- | | `%tickets` | Check your Tickets | | `%tickets pull` (or `%tp`) | Spend 25 Tickets on a guaranteed high star pull | ### How `%tickets pull` works You need at least one card on your wishlist before you can even use this. If your wishlist's empty, it'll just tell you to go add something first with `%wishlist add`. Once that's sorted, spending your Tickets gives you one of three things, picked at random: * A card straight off your wishlist * A random poster * A random misprint Whatever you get is always at least a 4 or 5 star, and rarely (about 1 in 2,000 pulls), Ascended instead. That's the one guaranteed-pull method that CAN reach Ascended, heavily weighted toward A1 over anything rarer, see Pulling & Claiming. If the bot doesn't have any poster or misprint art yet, those options just aren't available and you'll get something off your wishlist instead. See Pulling & Claiming for how star odds work, Currencies & Daily Rewards for upgrading a card's stars after the fact, and Wishlist for managing your list. ## Searching your collection `%collection` lets you search using little tags typed into your search text, mixed however you like: | Type this | To find | | ------------- | --------------------------------------------------------------- | | `c:name` | A character. Can be more than one word, like `c: Erwin Smith` | | `s:name` | A show. Same deal, `s: Attack on Titan` works fine | | `v:2` | A specific art variant number | | `★5` | A star quality, 1 through 5 (or `A1` through `A5` for Ascended) | | `p<9` / `p>9` | Mint number below or above a number | | `-posters` | Only posters | | `-misprints` | Only misprints | | `-notag` | Only cards with no tags | | `:emoji:` | Cards tagged with that emoji | The dash in `-posters`, `-misprints`, and `-notag` is just part of how those are spelled, not some special symbol. There's no way to search for "everything except X" right now, just those three specific options. `c:` and `s:` both grab everything up to the next search tag as their value, so full names work fine. `c: Erwin Smith s: Attack on Titan` correctly picks up Erwin Smith as the name and Attack on Titan as the show, not just the first word of each. Any word that isn't one of these tags just gets searched for as a plain tag on its own. That's also how typing `:emoji:` works without needing anything special. It also means if you typo something like `-posterz`, it won't error out, it'll just look for a tag literally called "posterz" and probably find nothing. A few examples: * `%collection s: Attack on Titan` shows every card you own from that show * `%collection c: Erwin Smith` shows every copy you own of that character * `%collection c:Sato ★5 -notag` shows untagged five star Sato cards * `%collection v:2` shows cards using art variant 2 * `%collection :vhs:` shows cards tagged with `:vhs:` Check out Tags & Auto-tagging for how to actually put those emoji on your cards, and Trading & Gifting for handing cards off to other people. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://studio0.gitbook.io/tome-docs/collection-and-card-ids.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.