Modmail: server picker, transcripts, and a setup fix
Three modmail changes this release, one of them a bug that quietly swallowed messages.
Choosing which server you are writing to
If you shared more than one server with exceed that had modmail turned on, DMing the bot sent your message to whichever of them happened to come first. You were never asked, and the servers you actually meant never saw it.
You now get a menu listing every server you can reach, and your message goes where you pick.
The menu only appears when there is something to choose. One shared server, or a conversation you already have open, goes straight through the way it always did.
Being blocked in one server no longer silences the rest
A modmail block used to drop your DMs entirely, including messages meant for a completely different server. Blocks now only apply to the server that set them.
Modmail transcripts
Closing a modmail now produces a full HTML transcript, the same kind tickets have had, instead of a plain text file. Avatars, roles, embeds, attachments, replies, code blocks and clickable profiles all survive.
The link is posted to your modmail log channel, so set one to receive them:
,modmail setup #category #logsOnly people who can manage the server can open a modmail transcript. The member is deliberately not sent a link, because staff often talk privately in a modmail channel that the member never sees.
Turning modmail on without a category
Modmail needs a category to create its conversation channels under. The dashboard let you switch modmail on without picking one, which left it silently doing nothing at all: the toggle read as on, and every DM was ignored.
The category selector now appears before you turn modmail on, and enabling without one is refused with an explanation instead of saving a setting that cannot work. ,modmail status calls out the same problem.
If your server was in that state, modmail has been switched off so the setting matches what was actually happening. Pick a category and turn it back on.
Full command list on the configuration commands page.