Getting Started

This walks a server owner or admin through setting MemoryCord up from scratch: install, opt in your channels, seed the wiki from what your community already has, run a first search, and turn on the weekly digest.

1. Add the bot

Add MemoryCord to your server

You’ll need Manage Server on the Discord server to complete the invite. The authorization screen asks for two scopes and five permissions - here’s what each one is actually used for:

Permission	Why MemoryCord needs it
View Channels	To see the channels you opt in, and to check whether a member can see a channel before showing them search results from it.
Send Messages	To reply to slash commands and post the weekly digest.
Read Message History	To fetch the message someone just flagged or linked, and to scan history for /import history and /import pins.
Add Reactions	To put a checkmark on the answer message when /solve marks a question solved.
Embed Links	To format search results and the digest as embeds instead of plain text walls.

That’s the complete list. MemoryCord does not ask for Manage Server, Manage Messages, Kick/Ban, or any moderation permission - it doesn’t need them, and admin-only commands are enforced by checking the invoking member’s own permissions, not the bot’s.

2. Opt in your channels

MemoryCord captures nothing until you tell it where to look. Channels that are never opted in are invisible to it - no reading, no storing, nothing.

/optin channel:#support channel2:#guides channel3:#faq

Notes on /optin:

• You can pass up to five channels in a single command (channel through channel5). Run it again to opt in more.
• Run it with no arguments and it opts in the channel you ran it from. If you run it from inside a thread, it opts in the thread’s parent channel instead - threads always inherit their parent channel’s opt-in status, they can’t be opted in separately.
• Both regular text channels and forum channels can be opted in.
• Requires Manage Server. This is checked at the moment the command runs, not just at invite time, so it applies even if someone changes the command’s default permissions in Discord’s integration settings.

Opting a channel in only affects what happens going forward (pushpin reactions, /solve, /wiki save) plus what /import can pull from it. It does not, by itself, pull in anything old - that’s the next step.

To reverse this later, /optout disables capture in a channel; add purge:True to also delete everything already captured from it. See Saving to the Wiki for the full capture rules.

3. Seed the wiki from what you already have

Most servers already have years of good answers sitting in pins and old threads. Two commands pull that in without anyone re-flagging it by hand:

/import pins

Imports every pinned message from your opted-in text channels (limit to one with channel:). Pins from bots are skipped, and pins with no text content are skipped too - an image pinned with no caption won’t produce a useful wiki entry.

/import history min_reactions:2 depth:1000

Scans recent history in your opted-in text channels and imports any message the community already flagged with enough pushpin or star reactions. min_reactions defaults to 2 (range 1-20); depth defaults to 500 messages per channel scanned (range 100-2000). On a smaller server, running min_reactions:1 catches more.

Both commands are admin-only, share a five-minute per-guild cooldown per subcommand, and are idempotent - running either one twice never creates duplicate entries. Re-running just refreshes the content and reaction count of anything already captured. Full details, including exactly what gets skipped and why, are in Importing and Exporting.

Note: forum channels aren’t scanned by /import pins or /import history (forum posts pin per-thread, not on the forum channel itself), so seed forum-based support channels by having members flag or /wiki save the good threads going forward.

4. Run a first search

/ask how do I reset my password

You’ll get a private (only-you-see-it) reply with up to five matching results, each with a short snippet and a jump link back to the original message. If nothing’s been saved yet, you’ll get a nudge to flag the next good answer instead of a wall of nothing. Query tips and how results are filtered by channel permission are in Searching.

5. Turn on the weekly digest

/digest action:setup day:Friday hour:17 timezone:America/New_York

This posts a short roundup - what got saved, what got solved, what’s still open - in the channel you ran the command from, once a week at the day/hour/timezone you picked. Full behavior, including what happens if the bot is offline at post time, is in Weekly Digest.

6. Tell your members

The loop only works if people know the pushpin reaction exists. Point them at /help for an in-Discord summary, or just tell them: react with the pushpin on anything worth keeping, /ask to search, /solve when a question gets answered.

What good setup looks like

• The bot is invited with the standard link above (no extra permissions granted).
• Every channel where good answers actually happen is opted in - support channels, FAQ channels, guide channels.
• /import pins and /import history have both been run at least once against your existing channels, so the wiki isn’t starting from zero.
• /ask returns real results for a question a new member would actually ask.
• The digest is configured and posting to a channel people will actually see it in.
• Regulars know the pushpin reaction exists and use it without being reminded.
• An admin has read Privacy and can answer “what does this bot store” if a member asks.