Event logs keep your staff up to date on what happens on the server. Miyu posts a short message to a log channel whenever something you care about happens, like a member joining or a channel being deleted.
You choose a log channel for each kind of event. You can send everything to one channel or split it up.
You need the Administrator permission for these commands.
m!events enabled on
This is the same as m!modules enable eventLogging. Use off to turn it off again. m!events activate on works too.
m!events set channel <#channel> <event type>
For example:
m!events set channel #join-log JoiningEvents
m!events set channel #server-log ChannelEvents
m!events set channel #server-log InviteEvents
m!events set channel #message-log ReactionEvents
Running the command again for the same event type moves that log to the new channel.
Make sure Miyu can see and post in your log channels, and that normal members can't.
| Event type | What Miyu posts |
|---|---|
JoiningEvents |
Member joined: who joined, what number member they are, which invite they used and who created that invite. Member left: who left, when they had joined and which roles they had. |
ChannelEvents |
Channels being created, changed or deleted |
InviteEvents |
Invites being created (code, creator, channel, max uses, expiry) or deleted |
ReactionEvents |
Reactions being added or removed |
Bots joining or leaving aren't logged.
Miyu keeps track of your server's invites so it can tell you which invite a new member used. This works best when Miyu can see your invites, so give the Miyu role the Manage Server permission. If your server has a vanity URL and someone joins through it, the log shows that too.
You might see more event types when Miyu lists them, like MemberEvents, MessageEvents, VoiceEvents, RoleEvents, ThreadEvents, WebhookEvents, AutoModEvents and IntegrationEvents. You can already pick channels for them, but Miyu doesn't post anything for these yet.