12.8.0 rename settings to config
This commit is contained in:
4 files changed
+29
-29
No files matched your search
@@ -2,7 +2,7 @@ const { EmbedBuilder, ActionRowBuilder, ButtonBuilder, ButtonStyle } = require('
|
|||||||
const bitfieldCalculator = require('discord-bitfield-calculator');
|
const bitfieldCalculator = require('discord-bitfield-calculator');
|
||||||
|
|
||||||
module.exports = {
|
module.exports = {
|
||||||
name: "settings",
|
name: "config",
|
||||||
debug: false,
|
debug: false,
|
||||||
global: false,
|
global: false,
|
||||||
description: "Configure your server settings",
|
description: "Configure your server settings",
|
||||||
+3
-3
@@ -26,7 +26,7 @@ module.exports = {
|
|||||||
}]
|
}]
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
name: "settings",
|
name: "config",
|
||||||
description: "How to configure the settings",
|
description: "How to configure the settings",
|
||||||
value: "settings",
|
value: "settings",
|
||||||
type: 1,
|
type: 1,
|
||||||
@@ -117,12 +117,12 @@ module.exports = {
|
|||||||
|
|
||||||
return interaction.send({ embeds: [embed] });
|
return interaction.send({ embeds: [embed] });
|
||||||
}
|
}
|
||||||
} else if (args[0].name == 'settings') {
|
} else if (args[0].name == 'config') {
|
||||||
const userID = client.exists(interaction.user) ? interaction.user.id : interaction.member.user.id;
|
const userID = client.exists(interaction.user) ? interaction.user.id : interaction.member.user.id;
|
||||||
|
|
||||||
let settingsMenu = new SelectMenuBuilder()
|
let settingsMenu = new SelectMenuBuilder()
|
||||||
.setCustomId(`SettingsHelp-${userID}`)
|
.setCustomId(`SettingsHelp-${userID}`)
|
||||||
.setPlaceholder('Select Setting you require help with')
|
.setPlaceholder('Select the configuration you require help with')
|
||||||
|
|
||||||
settings.settings.map((setting) => {
|
settings.settings.map((setting) => {
|
||||||
settingsMenu.addOptions({
|
settingsMenu.addOptions({
|
||||||
|
|||||||
+1
-1
@@ -2,7 +2,7 @@ require('dotenv').config();
|
|||||||
|
|
||||||
module.exports = {
|
module.exports = {
|
||||||
Dev: "PROD.",
|
Dev: "PROD.",
|
||||||
Version: "12.7.15", // (major).(feature).(revision/bug/refactoring)
|
Version: "12.8.0", // (major).(feature).(revision/bug/refactoring)
|
||||||
Admins: ["362791661274660874", "329371697570381824"], // Admins of the bot
|
Admins: ["362791661274660874", "329371697570381824"], // Admins of the bot
|
||||||
DefaultPrefix: "?",
|
DefaultPrefix: "?",
|
||||||
ServerID: "955668596745461830",
|
ServerID: "955668596745461830",
|
||||||
|
|||||||
+24
-24
@@ -3,47 +3,47 @@ module.exports = {
|
|||||||
{
|
{
|
||||||
name: "allowed_channels",
|
name: "allowed_channels",
|
||||||
description: `
|
description: `
|
||||||
If you wish to limit users to use the bot in some channels, you can configure \`allowed_channels\`. To do so, use \`/settings allowed_channels add <your channel>\` to add a channel to a list of allowed channels.
|
If you wish to limit users to use the bot in some channels, you can configure \`allowed_channels\`. To do so, use \`/config allowed_channels add <your channel>\` to add a channel to a list of allowed channels.
|
||||||
|
|
||||||
To remove a channel, use \`/settings allowed_channel remove <your channel>\`.
|
To remove a channel, use \`/config allowed_channel remove <your channel>\`.
|
||||||
`
|
`
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
name: "action_channel",
|
name: "action_channel",
|
||||||
description: `
|
description: `
|
||||||
To save the hastle of cluttered channels, you can configure a dedicated channel for the \`/action\` command. To do so, use \`/settings action_channel set <channel>\`. This will send any output for the \`/action\` command to this channel.
|
To save the hastle of cluttered channels, you can configure a dedicated channel for the \`/action\` command. To do so, use \`/config action_channel set <channel>\`. This will send any output for the \`/action\` command to this channel.
|
||||||
|
|
||||||
To remove this configuration, use \`/settings action_channel remove\`
|
To remove this configuration, use \`/config action_channel remove\`
|
||||||
`
|
`
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
name: "tweet_channel",
|
name: "tweet_channel",
|
||||||
description: `
|
description: `
|
||||||
To save the hastle of cluttered channels, you can configure a dedicated channel for the \`/tweet\` command. To do so, use \`/settings tweet_channel set <channel>\`. This will send any output for the \`/tweet\` command to this channel.
|
To save the hastle of cluttered channels, you can configure a dedicated channel for the \`/tweet\` command. To do so, use \`/config tweet_channel set <channel>\`. This will send any output for the \`/tweet\` command to this channel.
|
||||||
|
|
||||||
To remove this configuration, use \`/settings tweet_channel remove\`
|
To remove this configuration, use \`/config tweet_channel remove\`
|
||||||
`
|
`
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
name: "adverts_channel",
|
name: "adverts_channel",
|
||||||
description: `
|
description: `
|
||||||
Users with the configured commercial role can create advertisements for their commercial business. To keep your channels clean, you can limit the output of this command to a dedicated channel. To do so, use \`/settings adverts_channel set <channel>\`. This will send any adverts to this channel.
|
Users with the configured commercial role can create advertisements for their commercial business. To keep your channels clean, you can limit the output of this command to a dedicated channel. To do so, use \`/config adverts_channel set <channel>\`. This will send any adverts to this channel.
|
||||||
|
|
||||||
To remove this configuration, use \`/settings adverts_channel remove\`.
|
To remove this configuration, use \`/config adverts_channel remove\`.
|
||||||
`
|
`
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
name: "dispatcher_channel",
|
name: "dispatcher_channel",
|
||||||
description: `
|
description: `
|
||||||
In order for the \`/311\` or \`/911\` commands to be used, you need to configure two settings. \`dispatcher_channel\` is one of the settings to configure. This will redirect all \`/311\` or \`/911\` reports to a dedicated channel. Use \`/settings dispatcher_channel set <channel>\` to configure this setting.
|
In order for the \`/311\` or \`/911\` commands to be used, you need to configure two settings. \`dispatcher_channel\` is one of the settings to configure. This will redirect all \`/311\` or \`/911\` reports to a dedicated channel. Use \`/config dispatcher_channel set <channel>\` to configure this setting.
|
||||||
|
|
||||||
To remove this configuration, use \`/settings dispatcher_channel remove\`.
|
To remove this configuration, use \`/config dispatcher_channel remove\`.
|
||||||
`
|
`
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
name: "starting_balance",
|
name: "starting_balance",
|
||||||
description: `
|
description: `
|
||||||
New users in your guild receive $1000.00 as their starting balance. This can be configured, use \`/settings starting_balance <amount>\`. This can be a floating point number, e.g 150.40
|
New users in your guild receive $1000.00 as their starting balance. This can be configured, use \`/config starting_balance <amount>\`. This can be a floating point number, e.g 150.40
|
||||||
|
|
||||||
floating point number: a number value with a decimal.
|
floating point number: a number value with a decimal.
|
||||||
`
|
`
|
||||||
@@ -51,59 +51,59 @@ module.exports = {
|
|||||||
{
|
{
|
||||||
name: "income_role",
|
name: "income_role",
|
||||||
description: `
|
description: `
|
||||||
Users can work once a day to earn money, but this will require a role with a set daily income. To configure a new income role, use \`/settings income_role set <role> <daily income>\`.
|
Users can work once a day to earn money, but this will require a role with a set daily income. To configure a new income role, use \`/config income_role set <role> <daily income>\`.
|
||||||
|
|
||||||
Users with one of these configured roles can use the \`/work\` command once a day to earn their set daily income.
|
Users with one of these configured roles can use the \`/work\` command once a day to earn their set daily income.
|
||||||
|
|
||||||
Note: If a user has more than one role to earn income, using the \`/work\` command will earn them the highest income from one of the roles they have.
|
Note: If a user has more than one role to earn income, using the \`/work\` command will earn them the highest income from one of the roles they have.
|
||||||
|
|
||||||
To remove one of the configured roles, use \`/settings income_roles remove <role>\`.
|
To remove one of the configured roles, use \`/config income_roles remove <role>\`.
|
||||||
`
|
`
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
name: "bot_admin_role",
|
name: "bot_admin_role",
|
||||||
description: `
|
description: `
|
||||||
Some commands are limited to users who can manage the guild (Admin privilages), but if you wish for users without admin privilages to access commands such as \`/settings\` \`/money\` or \`/reset\`. You can configure a bot admin role.
|
Some commands are limited to users who can manage the guild (Admin privilages), but if you wish for users without admin privilages to access commands such as \`/config\` \`/money\` or \`/reset\`. You can configure a bot admin role.
|
||||||
|
|
||||||
Use \`/settings bot_admin_role set <role>\` to configure the bot admin role.
|
Use \`/config bot_admin_role set <role>\` to configure the bot admin role.
|
||||||
|
|
||||||
To remove this configuration, use \`/settings bot_admin_role remove\`.
|
To remove this configuration, use \`/config bot_admin_role remove\`.
|
||||||
`
|
`
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
name: "commercial_role",
|
name: "commercial_role",
|
||||||
description: `
|
description: `
|
||||||
Users with the commercial_role have access to business related commands, to configure this role to give to some users, use \`/settings commercial_role set <role>\`.
|
Users with the commercial_role have access to business related commands, to configure this role to give to some users, use \`/config commercial_role set <role>\`.
|
||||||
|
|
||||||
To remove this configured role, use \`/settings commercial_role remove\`.
|
To remove this configured role, use \`/config commercial_role remove\`.
|
||||||
`
|
`
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
name: "officer_role",
|
name: "officer_role",
|
||||||
description: `
|
description: `
|
||||||
The \`/fine\` command requires a user to have a configured officer role. To configure this role, use \`/settings officer_role set <role>\`
|
The \`/fine\` command requires a user to have a configured officer role. To configure this role, use \`/config officer_role set <role>\`
|
||||||
|
|
||||||
To remove this configured role, use \`/settings officer_role remove\`.
|
To remove this configured role, use \`/config officer_role remove\`.
|
||||||
`
|
`
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
name: "dispatcher_role",
|
name: "dispatcher_role",
|
||||||
description: `
|
description: `
|
||||||
In order for the \`/311\` or \`/911\` commands to be used, you need to configure two settings. \`dispatcher_role\` is one of the settings to configure. This will allow users to interact with all \`/311\` or \`/911\` reports. Use \`/settings dispatcher_role set <role>\` to configure this setting.
|
In order for the \`/311\` or \`/911\` commands to be used, you need to configure two settings. \`dispatcher_role\` is one of the settings to configure. This will allow users to interact with all \`/311\` or \`/911\` reports. Use \`/config dispatcher_role set <role>\` to configure this setting.
|
||||||
|
|
||||||
To remove this configuration, use \`/settings dispatcher_role remove\`.
|
To remove this configuration, use \`/config dispatcher_role remove\`.
|
||||||
`
|
`
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
name: "only_officers_search",
|
name: "only_officers_search",
|
||||||
description: `
|
description: `
|
||||||
The \`/search\` command allows users to view other users inventories. If you wish to limit this command, you can do so by configuring \`only_officers_search\`. Use \`/settings only_officers_search <true/false>\`. This will optionally limit the \`/search\` command to users with the configured officer role.
|
The \`/search\` command allows users to view other users inventories. If you wish to limit this command, you can do so by configuring \`only_officers_search\`. Use \`/config only_officers_search <true/false>\`. This will optionally limit the \`/search\` command to users with the configured officer role.
|
||||||
`
|
`
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
name: "view",
|
name: "view",
|
||||||
description: `
|
description: `
|
||||||
There is a lot of settings you can configure. To view a all configured settings, use the following: \`/settings view\`. This will display all configured settings, and their values if configured.
|
There is a lot of settings you can configure. To view a all configured settings, use the following: \`/config view\`. This will display all configured settings, and their values if configured.
|
||||||
`
|
`
|
||||||
}
|
}
|
||||||
]
|
]
|
||||||
|
|||||||
Reference in new issue
Block a user