Skip to content

Config Documentation

Basic Settings

Mila has a handful of basic configuration settings, currently they are:

  • Custom Prefixes
  • Custom Greeting
  • Custom Goodbye
These can be used for general purposes and aren't entirely necessary.

Custom Prefix

Mila has the ability to set a single custom prefix for every guild. This setting will replace the default prefix of m. with the prefix you choose. In case you and everyone else in the server forgets the prefix you set, you can always use @Mila#6910 instead. This setting can be changed with m.config -prefix <prefix>.

Prefix

Custom Greeting

Mila has a setting that allows you to change the message displayed in user logs to whatever you want. To prevent spam the message can't be any longer than 300 characters, including spaces and non-ascii text. This setting has a series of dynamic variables, they are:

  • {user} - Username & tag
  • {user.mention} - Username mention
  • {server} - Server name
To change this setting, you must use m.config -greeting <message>.

Gretting

Custom Goodbye

This setting is the same as greeting messages except it is displayed when a user leaves. To change this setting, you must use m.config -goodbye <message>.

Goodbye

Config Resetting

Resetting Mila's configuration is really simple, you can reset everything with m.config -reset.

Reset

Automatic Setup

If you're struggling with configuration, Mila has a useful command that will re-create the recommended configuration for you! This is done using m.config -autosetup and will take about 5 seconds to finish.

Auto


Logging Module

Mila has 4 logging systems built-into it, the three types of logging include:

  • Message logging
  • Mod logging
  • User logging
  • Action logging
These can come in handy for people that like to keep a record of all the things that happen in their server. To change a logging channel, simply do m.config -logs -<log type> <channel>.

Mod Logging

Mila's mod logging can be controlled via m.config -logs -mod <channel>. Mod-logs are created every time a user is:

  • Warned
  • Kicked
  • Muted
  • Unmuted
  • Banned
  • Unbanned

Mod

User Logging

Mila's user logging can be controlled via m.config -logs -user <channel>. User-logs are created every time a user:

  • Joins
  • Leaves

User

Message Logging

Mila's message logging can be controlled via m.config -logs -msg <channel>. Message-logs are created every time a message is:

  • Deleted
  • Edited

Message

Action Logging

Mila's action logging can be controlled via m.config -logs -action <channel>. Action-logs are created every time a channel, role or guild setting is:

  • Created
  • Deleted
  • Edited

Action

Log Layout

The team has come up with a recommended log layout that they suggest novice user's follow to keep everything simple for them.

Logs


Role Management

Mila has 5 different role management systems, each role assigned to each of the five systems plays a significant role in many of Mila's other systems, like moderation. Here is a list of all four different role options:

  • Bot role
  • Human role
  • Muted role
  • Moderator role
  • Administrator role
Roles can be controlled via m.config -roles -<role type> <@role>.

Bot Role

When given a specific role to assign, Mila will automatically give a bot account said role once it joins the server, it can be changed with m.config -roles -bot <@role>.

Bot

Human Role

When given a specific role to assign, Mila will automatically give a human account said role once it joins the server, it can be changed with m.config -roles -human <@role>.

Human

Muted Role

Assigning a muted-role allows Mila to hand users this role when they are muted, typically this role should not have the ability to speak in general channels else it defeats the point of being muted. This role is controlled using m.config -roles -muted <@role>. If this role isn't configured when a mod attempts to mute a user, Mila attempts to find a role called Muted in your server and assign that instead.

Muted

Moderator Role

By assigning a Moderator role you are essentially assigning everyone with that role as a Moderator, thus allowing them to use most of Mila's moderation commands, however some are limited to Administrators and above. This role is controlled via m.config -roles -mod <@role>. When a user has the Moderator role, their perks are:

  • Access to moderation commands without requiring specific permissions
  • Bypasses the <Mila:NoCmd> setting
  • Bypasses the auto-moderator functionality

Mod

Administrator Role

An Administrator role is something that should be chosen carefully, users with the Administrator role have the ability to change configurations and do just about anything with Mila. This role is assigned via m.config -roles -admin <@role>.

Admin

Role Layout

A recommended role layout has been designed by the Mila developers as it ensures that all roles work correctly, this doesn't mean that other roles can't be there, this is just a demonstration of the order of Mila's roles.

Roles


Moderation Management

Mila comes built in with some handy auto-moderation features these features essentially allow the bot to punish users if they do a certain thing.

Violation Limit

This setting allows you to control how many times a user can trigger auto-mod except for Anti-Hoist in 10 minutes. This value must be above 0 else Mila will send an error. If this limit is hit, Mila will preform the configured action. This setting is controlled using m.config -anti -violations <number>.

Limit

Violation Action

This setting allows you to control what action is performed on a user when they exceed the specified number of auto-mod violations, this can only be one of Ban, Kick & Mute. This setting is controlled using m.config -anti -action.

Action

Note

Anti-invite sets a nickname for user's whose nickname contains an invite link. Anti-porn also sets a nickname for user's whose nickname contains a pornographic link.

Anti Invite

Enabling this will ensure that Mila deletes every Discord server invite that a non-staff user sends, regardless whether the invite is valid or not.

Invites

Anti Porn

Anti-porn removes pornographic links sent outside of channels marked as NSFW. This doesn't tend to get much use but for very large servers it can be necessary.

Porn

Anti Hoist

This setting automatically removes nicknames contain hoisting or Zalgo content, which is useful if your server's policy involves mentionable nicknames.

Hoist

Anti Spam

Anti-spam is, without a doubt, one of the most essential auto-moderation settings out there. If a user sends 5 messages consecutively within a 5 second time frame, the messages are removed and the perpetrator is handed a warning from Mila.

Spam