Skip to content

Questions and Answers

/solve captures a question and its accepted answer together, as a single searchable pair. This is the difference between a wiki entry (one flagged message) and a Q&A pair (two linked messages, question and answer) - and it’s usually the better fit for support channels, where the value is in the pairing, not either message alone.

/solve answer_link:https://discord.com/channels/123.../456.../789...

/solve needs an answer (which you always provide, as a message link) and a question. It looks for the question in three ways, in this priority order:

  1. An explicit question_link. If you pass question_link:, that’s used, full stop, regardless of what the answer replies to or where you are.
  2. The answer’s own reply target. If you didn’t pass question_link but the answer message was posted as a Discord reply to another message, that replied-to message is used as the question.
  3. The thread starter. If neither of the above applies and you’re running /solve inside a thread, the thread’s starting message is used as the question.

If none of these resolve to a message, /solve tells you so and asks you to either reply to the question when posting the answer, or pass question_link: explicitly.

/solve answer_link:https://discord.com/channels/.../.../999 question_link:https://discord.com/channels/.../.../111

/solve works in any channel or thread that’s opted in to the wiki (see Getting Started) - a plain text channel, a public thread, or a forum post. It does not work in private threads; those are excluded entirely, the same as every other capture path.

A few link rules apply regardless of channel type:

  • The answer message must be in the same channel where you run /solve. You can’t point /solve at an answer in a different channel.
  • If you pass question_link:, that message must be in the same wiki-enabled channel as the answer (the same opted-in parent channel, for thread-based channels).
  • The answer must be a real member’s text message - not a bot message, and not an empty one.

Authorization is based on who asked, not who’s running the thread. You can mark a question solved if you are:

  • the author of the question message, or
  • someone with Manage Messages in that channel, or
  • someone with Manage Threads or Manage Server anywhere in the server.

Being the person who posted the answer isn’t, by itself, enough - if you answered someone else’s question, either the asker needs to run /solve, or a moderator needs to.

When /solve succeeds, MemoryCord adds a white checkmark reaction to the answer message, as a visual marker in the channel that the question was resolved. This is cosmetic only - if Discord fails to add the reaction for any reason, the Q&A pair is still saved; the reaction failing never blocks the capture.

A saved Q&A pair appears in /ask and /wiki search results labeled Q&A, with a snippet combining the question and the answer, and a jump link to the answer message. See Searching for the full result format and how permissions filter results.

  • Reply to the question when you answer it. This is the cheapest way to make /solve work with no extra typing - just answer_link: and the question resolves automatically.
  • In threads, you often don’t need a reply at all. If the thread itself is the question (a typical “help wanted” thread), /solve answer_link:<the good answer> picks up the thread starter automatically.
  • Use question_link: when the conversation branched. If the actual question was asked earlier in a longer conversation and the answer wasn’t a direct reply, pass the link explicitly rather than relying on inference.
  • One answer per question. /solve records one specific question message and one specific answer message; if a question gets several good answers, whoever runs /solve picks which one becomes the searchable pair.
  • Removing a pair. There’s currently no per-pair delete command; a Q&A pair is removed when the question author, the answerer, or the person who solved it runs /forgetme, or when an admin runs /forgetserver. See Privacy for the full deletion picture, including the caveat that Q&A pairs are not automatically removed if the original question message is later deleted.