> 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/other-commands.md). # Other Commands Stuff that doesn't really belong anywhere else. | Command | What it does | | ------------------------- | ------------------------------------------------------------------------------------------ | | `%selfprefix ` | Set your own personal prefix that works for you in any server, instead of the server's `%` | | `%invite` | Get the bot's invite link and the support server link | | `%compensation` | Claim a compensation grant, if one's currently open, see below | | `%set [#channel]` | Confine most commands to one channel, see below | | `%reroute [#channel]` | Lock pulling to one specific channel, see below | | `%dropchannel [#channel]` | Turn on activity-triggered auto-drops, see below | ## `%selfprefix` Handy if a server's `%` clashes with another bot you use a lot. Your prefix works alongside the server's, not instead of it. Set `t!` as yours and both `%pull` and `t!pull` work for you, while everyone else in that server still only has `%`. A few rules: * Up to 5 characters, no spaces * Can't be the same as the bot's own default prefix, since that wouldn't do anything * Type `clear`, `remove`, `reset`, `none`, or just leave it blank, to get rid of it. The server's `%` keeps working either way It follows your account everywhere, not just one server. ## `%invite` Posts a link to add the bot to your own server, plus a link to the support server if you've got questions, found a bug, or have an idea. ## `%compensation` Not something that's always available - this opens up sometimes, usually after something's gone wrong and people are owed a make-good. When it's open, each run gives you one guaranteed 4 or 5 star card (still never Ascended, see Pulling & Claiming), preferring something off your wishlist, with a random frame equipped on it for free. That frame works a little differently than one you buy yourself: it's locked to that one card. You can take it off if you don't want it, but you can't move it onto anything else, since you didn't actually buy it, see Frames. Compensation cards show a plain `C` instead of a mint number, since they're pulled from a separate count that doesn't touch the real numbered prints, whoever pulls or claims that same card normally later still gets the actual next number in line. You'll see them marked with a 🎁 in `%collection`, see Collection & Card IDs. Each time it's open, you get a limited number of claims, and you'll be told how many you have left each time you use it. Running `%compensation` while it's closed, or after you've used up your claims, just tells you so instead of doing anything. ## `%set` - confine most commands to one channel A server can confine most commands (pulling included) to a single channel: * `%set #channel` - confines commands to that channel from now on * `%set` (nothing after it) - shows the current setting * `%set off` (also `clear`/`remove`/`reset`/`none`) - removes the confinement, commands work anywhere again A short list of commands always work anywhere, `%set` or not - gifting, trading, compensation, checking your Tickets balance or melting dupes with `%melt`, checking `%help`, and setting your own `%selfprefix`. The slash version (`/set`) takes the same channel argument, plus a `clear` option instead of typing `off`. ## `%reroute` - lock pulling to one channel `%pull`/`/pull` works everywhere by default, exactly like every other command - `%set` can confine it to one channel same as anything else, but nothing about pulling is ever gated by how active a channel currently is. `%reroute` is the one exception: it overrides everything else (including `%set`) and locks pulling to exactly one channel, no matter what: * `%reroute #channel` - locks pulling to that channel, regardless of what `%set` says * `%reroute` (nothing after it) - shows the current setting * `%reroute off` (also `clear`/`remove`/`reset`/`none`) - goes back to following `%set`/working anywhere ## `%dropchannel` - activity-triggered auto-drops The one place chat activity actually matters. Turns on a channel where Tome watches real activity and, once it's been active enough, drops 1-5 cards entirely on its own - no command involved at all, same claim-by-button mechanics as a normal pull. The announcement looks just like a normal drop, just from Tome itself instead of a person who ran `%pull`. * `%dropchannel #channel` - turns auto-drops on in that channel * `%dropchannel` (nothing after it) - shows the current setting * `%dropchannel off` (also `clear`/`remove`/`reset`/`none`) - turns auto-drops off How much activity it takes before the next drop isn't a fixed number - it's re-randomized within a range every time one fires, so it's not something people can count along to and predict. Bot messages (including Tome's own drop announcements) never count toward it. ## A note on shortcuts A lot of commands answer to more than one name, whichever's quickest for you. A few examples: `%p` for `%pull`, `%tp` for `%tickets pull`, `%c` for `%collection`, `%v` for `%view`, `%bal` for `%balance`, `%m` for `%market`, `%tr` for `%trade`, `%eq` for `%equip`, `%up` for `%upgrade`, `%comp` for `%compensation`, `%sl`/`%au`/`%ul` for `%sell`/`%auction`/`%unlist`, and `%h` for `%help`. Run `%help` any time to see the full list. --- # 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/other-commands.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.