Moderation
flanker gives you a full moderation toolkit, and every action is recorded in a searchable case history.
Core actions
/ban,/moderation softban,/moderation tempban,/moderation hardban,/unban/kick/timeoutand/untimeout/jailand/unjail(role-based isolation that survives rejoins)/warn,/warnings,/cases clearwarns/purge messageswith filters: member, bots, humans, links, images, embeds, mentions, orcontains <text>(1 to 1000 messages)
See the full Moderation commands for syntax, limits and examples.
Channel control
/lockand/unlocka channel/slowmodeto rate-limit a channel
Mutes
flanker supports several mute styles depending on your setup, including
image mutes and reaction mutes. See /help module imute and /help module rmute.
Case history
Every moderation action creates a case with the moderator, target, reason and timestamp. Staff can look up and review cases, and add notes. This gives you an audit trail independent of Discord’s own logs.
Set a mod log with /moderation settings modlog #channel and every case is posted there as a
card. The case number in the moderator’s reply links to that post. Under each
post are buttons:
- Unban, Remove timeout, Unjail and the like undo the action, after a confirm. It runs as whoever clicks, so their permissions apply, and the post shows who undid it.
- Add evidence opens a form for text, links, message links and up to five images (8 MB each) or videos (15 MB each). A message link saves a copy of the message, so the evidence stays if it’s deleted. Only the moderator who made the case, or a server manager, can add evidence.
- History shows the member’s other cases.
/cases history @member shows a member’s cases a few per page: when, who, why, how
long, the evidence, and a link to each case’s post. /cases case 42 shows one case,
and /cases proof add 42 adds evidence from a command.
Bulk role updates
Give several safe roles in one batch:
/role all @Member @Events @Updates/role humans @Member @Events/role bots @BotRole/role all @Events @Updates removeA batch accepts up to ten distinct roles. A trailing remove removes all listed roles. Mentions, IDs and quoted role names are accepted; separate roles with spaces. Flanker validates every selected role before starting. Dangerous permissions cannot be granted through a mass command.
Only one bulk role job can be running or queued per server, shared by all, humans and bots. Choose all your roles in one command rather than submitting parallel jobs. Other long tools also share limits by task family, with an overall bounded queue and one active bulk worker per server.
Panic pauses pending requests and keeps the job’s progress. Jobs recheck permissions before continuing after recovery. Requests already in flight may finish, and jobs do not survive a bot restart.