You must have `Administrator` or `Manage Server` permissions to change/view server settings.
[C_SETTINGS_RESETPROMPT]
Are you sure you want to reset **all** of your {type} settings to the default values? This cannot be undone. *(__y__es, __n__o)*
This prompt will time out in __30 seconds__.
[C_SETTINGS_RESETINVALID]
You provided an invalid input, please try again.
[C_SETTINGS_RESETABORT]
Successfully aborted the operation.
[C_SETTINGS_RESETSUCCESS]
All {type} settings were successfully deleted and set to default.
[C_SETTINGS_EXPORT]
Attached the JSON-formatted {type} settings file in the file below.
You may want to format this file for your viewing pleasure.
[C_SETTINGS_SETTINGNOTFOUND]
That setting does not exist!
[C_SETTINGS_FORMATTYPE]
switch("{type}") {
case "GUILD":
"server";
break;
case "USER":
"user";
break;
}
//Grant Command
[C_GRANT_DESCRIPTION]
Grant roles or users permissions to use commands or modules.
To view all grantable permissions, use the command `{prefix}perms list`.
[C_GRANT_MISSINGRESOLVEABLES]
Unable to find any roles or members, view `{prefix}cmd grant` for more information.
[C_GRANT_MISSINGPERMISSIONNODES]
Unable to find any grantable permissions, view `{prefix}cmd grant` for more information.
[C_GRANT_DATABASEERROR]
There was an issue pushing the permissions to the database. Contact a bot developer.
[C_GRANT_SUCCESS]
Successfully granted targets {targets} the following permissions: {permissions}{channel}.
[C_GRANT_SUCCESSCHANNELS]
in channel{plural} {channels}
[C_GRANT_WARNING]
You granted a command from the **Administration** module. This is potentially dangerous, as whoever you granted the administration commands to could have access to vital parts of the server. Only grant administration commands to people you trust.
//Revoke Command
[C_REVOKE_DESCRIPTION]
Revoke permissions granted to roles or users.
NOTE: If a user left the server, you must use the ID to revoke the permissions.
[C_REVOKE_MISSINGRESOLVEABLES]
Unable to find any roles or users, view `{prefix}cmd revoke` for more information.
[C_REVOKE_DATABASEERROR]
There was an issue pushing the permissions to the database. Contact a bot developer.
[C_REVOKE_SUCCESS]
Successfully revoked targets {targets} the following permissions: {permissions}{channel}.
[C_REVOKE_SUCCESSCHANNELS]
in channel{plural} {channels}
//Permissions Command
[C_PERMISSIONS_DESCRIPTION]
View permissions granted to roles or users.
[C_PERMISSIONS_LIST]
You can **grant**/**revoke** the following permissions: {permissions}.
[C_PERMISSIONS_SHOWTITLE]
switch({user}) {
case true:
"User Permissions"
break;
case false:
"Role Permissions"
break;
}
[C_PERMISSIONS_SHOWDESCRIPTION]
An overview of all {resolve}'s permissions in the server. If you would like to see an in-depth view of the role or user's permissions, use `{prefix}perms [user|role]`.
[C_PERMISSIONS_MAXFIELDS]
:warning: **You have met the max amount of fields and you will need to use `{prefix}perms --json` to view them.** :warning:
[C_PERMISSIONS_NOTFOUND]
Unable to find any roles or users with those arguments.
[C_PERMISSIONS_JSON]
Attached the JSON-formatted permission file in the file below.
You may want to format this file for your viewing pleasure.
[C_PERMISSIONS_GLOBAL]
**Global Permissions:** {permissions}
Global permissions can be used in all channels, but you can add specific channels if needed.
[C_PERMISSIONS_GLOBALALT]
Channel-specific permissions are listed below.
[C_PERMISSIONS_NOPERMISSIONS]
**No permissions found!** Try granting some permissions by using:
Found {type} **{resolveable}** but {they}had no permissions.
[C_PERMISSIONS_NOPERMISSIONS]
Your server has no granted permissions to any roles or users.
If you would like to grant permissions, use the command `{prefix}grant` for more information.
//Disable Command
[C_DISABLE_DESCRIPTION]
Disable commands in your server to prevent usage.
[C_DISABLE_LIST]
The command{plural} currently disabled in your server are: {commands}
[C_DISABLE_LISTFAIL]
There are no disabled commands in your server.
[C_DISABLE_MISSINGCOMMANDS]
You must provide commands to disable.
[C_DISABLE_SUCCESS]
Successfully **disabled** command{plural} {commands} in your server.
[C_DISABLE_FAIL]
Failed to disable command{plural} {commands}. You are unable to disable the **command:enable** and **command:disable** commands.
[C_DISABLE_WARNING]
You disabled a command inside of the **Administration** module. It is dangerous to do so, as it may disable configurability of your server. Note you are unable to disable the `command:enable` and `command:disable` commands.
These changes will be reverted if a shard restarts; edit the file{plural} for sustainability.
[C_ENABLE_FAILGLOBAL]
Failed to globally enable command{plural} {commands}. **`[0/{total}]`**
// Moderation Module
//Note Command
[C_NOTE_DESCRIPTION]
Note members with a description, will not be logged.
The only way to view notes is through moderation history.
[C_NOTE_MISSINGMEMBERS]
You must provide members to assign notes to.
[C_NOTE_MISSINGMEMBERPERMISSIONS]
//Warn Command
[C_WARN_DESCRIPTION]
Warn members for a particular reason.
[C_WARN_MISSINGMEMBERS]
You must provide members to warn.
[C_WARN_INSUFFICIENTPERMISSIONS]
you don't have permission to run this command.
//Unmute Command
[C_UNMUTE_DESCRIPTION]
Unmute members from the server.
[C_UNMUTE_MISSINGMEMBERS]
You must provide members to unmute.
[C_UNMUTE_INSUFFICIENTPERMISSIONS]
I don't have permission to manage roles
[C_UNMUTE_CANNOTFINDMUTE]
they were not previously muted
[C_UNMUTE_ROLEDOESNOTEXIST]
the mute role does not exist anymore
[C_UNMUTE_1FAIL]
I had an issue removing the role
[C_UNMUTE_2FAIL]
I had issues assigning roles to them
[C_UNMUTE_3FAIL]
I had issues granting roles to them
//Mute Command
[C_MUTE_DESCRIPTION]
Assign members to be muted from the server for a specified amount of time.
[C_MUTE_MISSINGMEMBERS]
You must provide members to mute.
[C_MUTE_DURATIONEXCEPTION]
The duration must be more than `1 minute` and less than `1 month`.
[C_MUTE_INSUFFICIENTPERMISSIONS]
I don't have permission to manage roles
[C_MUTE_NOMUTEROLE]
You don't have a mute role set in your server, use the command `-set mute` for more information.
[C_MUTE_INVALIDMUTEROLE]
It seems like the mute role was deleted, use the command `-set mute` for more information.
[C_MUTE_1FAIL]
I had an issue adding the role
[C_MUTE_2FAIL]
I had issues assigning roles to them
[C_MUTE_3FAIL]
I had issues revoking roles from them
//Kick Command
[C_KICK_DESCRIPTION]
Kick provided members from the server.
[C_KICK_MISSINGMEMBERS]
You must provide members to kick.
[C_KICK_INSUFFICIENTPERMISSIONS]
I don't have permission to kick members
[C_KICK_CANNOTBEKICKED]
they are unable to be kicked
//Softban Command
[C_SOFTBAN_DESCRIPTION]
Bans and then unbans the member from the server.
Primarily used to prune the member's messages in all channels.
[C_SOFTBAN_MISSINGMEMBERS]
You must provide members to softban.
[C_SOFTBAN_INSUFFICIENTPERMISSIONS]
I don't have permission to ban members
[C_SOFTBAN_CANNOTBESOFTBANNED]
they are unable to be softbanned
//Ban Command
[C_BAN_DESCRIPTION]
Ban provided members or users from the server. Works with users not in the server.
Optionally assign a time to ban them for.
[C_BAN_MISSINGMEMBERS]
You must provide members to ban.
[C_BAN_DURATIONREQUIRED]
You must provide a duration while using the **tempban** alias.
[C_BAN_DURATIONEXCEPTION]
The duration must be more than `1 minute` and less than `3 months`.
[C_BAN_INSUFFICIENTPERMISSIONS]
I don't have permission to ban members
[C_BAN_CANNOTBEBANNED]
they are unable to be banned
[C_BAN_ALREADYBANNED]
they are already banned
//Unban Command
[C_UNBAN_DESCRIPTION]
Unban provided users from the server.
[C_UNBAN_MISSINGMEMBERS]
You must provide users to unban.
[C_UNBAN_INSUFFICIENTPERMISSIONS]
I don't have permission to unban members
[C_UNBAN_NOTBANNED]
they are not banned
//Prune Command
[C_PRUNE_DESCRIPTION]
Mass delete messages from provided channels. The amount provided is the amount of messages it searches, not deletes. Filters messages using a logical OR by default. **You cannot prune messages older than 2 weeks.**
[C_PRUNE_CHANNELEXCEPTION]
You are only able to prune up to `3` channels at a time.
[C_PRUNE_INTEGERINVALID]
You must provide an amount to prune.
[C_PRUNE_INTEGEREXCEPTION]
The amount must be more than `1` and less than `300`.
[C_PRUNE_INSUFFICIENTPERMISSIONS]
I don't have permission to manage messages
[C_PRUNE_NOTFETCHED]
I was unable to fetch any messages
[C_PRUNE_NOTDELETABLE]
I could not delete those messages
[C_PRUNE_NOFILTERRESULTS]
I could not find any messages with those arguments
[C_PRUNE_NODELETE]
I had issues deleting those messages
//Vckick Command
[C_VCKICK_DESCRIPTION]
Kick provided members from their connected voice-channel.
Shows helpful information for commands, settings, and moderation.
[C_HELP]
**__HELP MENU__**
For a list of all available commands, use `{prefix}commands [ group ]`.
**❯ Arguments**
The bot splits arguments by space unless specified otherwise. To pass an argument that contains spaces you have to encapsulate it in quotes, some exceptions exist.
**Ex:**
`{prefix}grant "rolename that contains spaces" < permission >` - quotes are necessary
`{prefix}user some user` - quotes not necessary
**Typically** if the argument is at the end of a command it won't require quotes.
**❯ Documentation notation**
**Optional** arguments are denoted by being encapsulated in brackets `[ ]` - means that the command will run either with default values or show usage prompt.
**Required** arguments are denoted by less and greater than `< >` - means that the command will not run and return an error.
**Infinite** arguments (ones you can list several) are denoted by `..` after the argument. Ex `< argument.. >` - means you can pass more than one argument.
**Alternatives** are denoted by being separated by a `|`.
**Actual values** that you can use in a command are denoted by being surrounded by single quotes `' '`.
**❯ Moderation**
For help with moderation, see `{prefix}help modhelp`.
__**Warning:** This is a long embed.__
**❯ Command aliases**
Most commands and settings have some kind of aliases associated with them, some of which change the behaviour of the command or setting.
For instance the mute setting has a `createmute` (`{prefix}settings createmute <rolename>`) alias, which changes the behaviour to be identical to `{prefix}settings mute create <rolename>`.
Shows information about the bot and component usage.
To show help for commands `{prefix}help [command]`
[C_HELP_404]
Dude stop, {component} doesn't exist!
[C_HELP_TAGS]
**TAG SEARCH**
Commands and settings matching tag `{keyword}`.
For further help on how to use them, see `{prefix}help <component>`.
[MODHELP_TITLE]
**Moderation help menu**
[MODHELP_DESC]
**Galactic Bot** offers extensive moderation tools for servers, small and large, ranging from simple warnings and notes to mutes and tempbans. One of our more recent additions is automod. While not necessarily being a true automod, it'll keep track of moderation escalation for you with some configuration. Automod utilizes configurable modpoints and thresholds, for more information about automod see `{prefix}settings modpoints` and `{prefix}settings automod`.
**Galactic's** moderation commands can be viewed by using `{prefix}commands moderation`. The moderation utility follows a specific syntax for moderation, some parts allow for variation, while others require the arguments to be in specific locations in the command.
**The general syntax is:** `{prefix}<command> @user [time] [reason]`
Arguments that don't follow a strict pattern can be put anywhere **in the reason**. Such arguments are flags (and points, though they don't follow the same syntax as flags, more on that in a bit). For now there aren't many flags used by the moderation utility, though more may come in the future. The flags currently in use are `--force` and `--expires:<time>`, which are used to guide the automod.
[MODHELP_FIELD_1_NAME]
**❯ Moderation flags**
[MODHELP_FIELD_1_VALUE]
`--force` is the flag used to bypass automod, i.e. if you think automod will change your infraction due to a threshold being exceeded pass the `--force` flag to override.
**Ex:** `{prefix}warn @user 2pts obnoxious --force` - this would force the infraction to be a warning even if the points issued would cause the total amount of points to exceed a threshold.
`--expire <time>` is the flag used to tell the automod that a custom infraction expiration time should be used instead of the defined modpoints expiration value.
**Ex:** `{prefix}warn @user 2pts obnoxious --expires 2d` - This tells the system that the infraction will expire in 2 days, instead of whatever was configured in the setting.
`--silent` is the flag used to tell the bot not to DM the infraction the user if the bot otherwise was configured to do so.
**Ex:** `{prefix}ban @user really obnoxious --silent` - with default configuration the bot would DM the user when removed from the server, passing the `--silent` flag will stop the bot from doing so.
[MODHELP_FIELD_2_NAME]
**❯ Points**
[MODHELP_FIELD_2_VALUE]
Points are the point values defined either when running the command or in the modpoints setting. Issuing points is fairly simple, as they get picked up from anywhere in the **reason**, so long they follow the correct format. Points follow this pattern: `integer value points|point|pts|pt|p`. Any point values that exceed 100 will default to 100, and any point values that go below 0 will default to 0.
**Ex:** `{prefix}warn @user obnoxious 2 points`
[MODHELP_FIELD_3_NAME]
**❯ Infraction history**
[MODHELP_FIELD_3_VALUE]
Infraction history will always be logged to the bot's database regardless of text channel output. As such GalacticBot provides tools to search logs and filter them to some extent with flags, such as `--filter:warn` or `--exclude:mute`.
When viewing a user's infraction history, the total amount on **unresolved infractions** is shown, and if modpoints are enabled, their unexpired points as well. This does **not** mean that they are not displayed in their history!
[MODHELP_FIELD_4_NAME]
**❯ NOTE**
[MODHELP_FIELD_4_VALUE]
All flags and points will be parsed **out of the reason**, meaning that when issuing them they will not show up in the reason for the infraction. Points will be displayed in the infraction if the modpoints system is enabled and flags don't need to be displayed anywhere.
//Guild command
[C_GUILD_DESCRIPTION]
View data about the server.
[C_GUILD_TEMPLATE]
__Server information for **{name}**__
{description}
{emoji_owner} **Owner:** <@{owner}>
{emoji_booster4} **Boost tier:** {tier}
{emoji_booster3} **Boosters:** {boosters}
{emoji_calendar} **Date created:** {createdAt}
{emoji_region} **Voice region:** {region}
[C_GUILD_MEMBERS_NAME]
__Members__
[C_GUILD_MEMBERS]
{emoji_members} **Count:**
{memberCount}/{maxMembers}
{emoji_online} **Online:**
{approxPresences}/{maxPresences}
[C_GUILD_CHANNELS_NAME]
__Channels__
[C_GUILD_CHANNELS]
**Total:** {totalChannels}/500
{emoji_category-channel} **Categories:** {cat}
{emoji_text-channel} **Text:** {tc}
{emoji_voice-channel} **Voice:** {vc}
{news}
{store}
[C_GUILD_NEWS]
{emoji_news-channel} **News:** {news}
[C_GUILD_STORE]
{emoji_store-channel} **Store:** {store}
[C_GUILD_OTHER_NAME]
__Other__
[C_GUILD_OTHER]
{emoji_role} **Roles:**
{roleCount}/250
{emoji_sunglasses} **Emojis:**
{emojiCount}/{emojiTotal}
{emoji_flushed-awkward} **Gif emojis:**
{gifEmojiCount}/{emojiTotal}
[C_GUILD_FEATURES_NAME]
__Server features__
[C_GUILD_FEATURES]
{features}
[C_GUILD_NODESC]
No description set for guild, set one with `{prefix}set description <description here>`, alternatively the description of a community enabled server is shown here.
Galactic (stable) and Galactic Canary (testing) bots only collect Discord user ID and message attachments (if applicable) data for moderation purposes.
We need your Discord user ID for remembering who you are, and your message attachments for logging tools for Discord server moderators.
We use message attachments in order to view what users post after they're deleted by Discord, this ensures a safe place for users and a useful tool for moderators.
This data is not shared with anyone. If you have questions or concerns about the bot, contact the developers in the Discord server [here]({invite}).
