> 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/trading-and-gifting.md). # Trading & Gifting Two ways to hand a card to someone else. A trade lets both people put cards and currency up, a gift is just a one way offer someone accepts or turns down. ## Trading | Command | What it does | | -------------- | ----------------------- | | `%trade @user` | Invite someone to trade | Trading is entirely chat based, there's no Add Cards button to click through: 1. Run `%trade @user`. They get an invite with a Decline button, but accepting is done by just typing **done** or **accept** in chat. 2. Once they've accepted, a live trade table opens for both of you. From here, just type things into the channel: * A Card ID or card code offers that card. List a few at once, comma or range separated, like `275, 274, 265-260`, to offer a bunch in one message. * A currency name with an amount offers that currency, like `gold 500` or `500 gold`. Works for all four currencies. * `remove ` takes something back out of your offer. Also takes a list. 3. Type `confirm` or `lock` when you're happy with your side. Changing your offer after confirming resets it, you'll need to confirm again. 4. Once you're both confirmed, everything swaps at the same time, cards and currency alike. 5. Either person can bail with the Cancel button at any point before it goes through. 6. If nobody touches it for 5 minutes, it closes on its own. The invite itself expires after 60 seconds if nobody accepts. You can't open a trade with someone who's already mid trade or has a pending invite sitting somewhere, and the same goes for you. ## Gifting | Command | What it does | | ------------------------------- | -------------------- | | `%gift @user ` | Offer someone a card | Simpler than a trade. One card, one direction, and the other person has to say yes: 1. You run `%gift @user `. Nothing moves yet, it just sends an offer. 2. They see Accept and Decline buttons. 3. Accept, and the card's theirs right away, as long as you still have it. If you already sold it or gave it away somehow, the gift just fails instead of transferring something you no longer own. 4. Decline, or just don't answer for 2 minutes, and it goes away with nothing happening. You can't gift yourself a card. One thing to watch out for: if a card's currently up for sale or auction (see Marketplace: Listings and Auctions), the bot won't stop you from also trying to trade or gift it away, so it's best to just not do that. Unlist it first if you want to trade or gift it instead. ## What happens to a frame when a framed card changes hands If a card has a frame equipped on it (see Frames), that frame goes right along with it through a trade or a gift, whoever ends up with the card keeps seeing it framed. What doesn't come along is the ability to use that frame on anything else. Frames belong to whoever bought them, not to the card, so the new owner can still take the frame off that one card if they want to, they just can't move it onto any of their other cards unless they've bought it themselves too. --- # 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/trading-and-gifting.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.