8 min · Easy
Logging
One default staff log, then split events if you want.
You will
Cases and at least one event type land in a staff channel.
Examples use the default prefix, a comma.
Before you start
- A staff channel near can talk in, or let logs setup create #all-logs.
Set it up
- See the current channel. Bare logs shows where cases and events go right now.
,logs
- Point it. Use an existing staff channel, or logs setup to create #all-logs. Most servers stop here.
,logs channel #staff
- Split later. Messages, members, roles, and channels can go to extra channels with logs add, or from Logs on the dashboard if you own the server.
,logs add #staff message
See it in Discord
This is the help card for this command. It uses the same syntax and example as `,help`.
member
,help logs
nearAPP
Examples
,logs
,logs setup
,logs channel #staff
,logs add #staff message
Do not
- Do not skip this before you start banning. You will not have history after a restart.
Troubleshooting
- Missing logs usually mean the channel was deleted or near cannot send.
- Jail-log is not the antinuke log. Keep antinuke on #all-logs.
Verify it works
- Edit a message in a test channel and confirm the log lands. Warn an alt and confirm a case appears.