Foreword

✨ Imagine An App…

…That makes building Discord bots easy with beginner-friendly functions. An app that’s capable of developing nearly all types of bots - from simple echo bots, to advanced multi-purpose administration ones. Where simplicity meets functionality and scalability. That’s Bot Designer for Discord.

What are you waiting for? Create the bot of your dreams today!

Start with Bot Designer for Discord

📎 Links

• Discord Server
• Website
• Android App
• iOS App
• Web App (Alpha Version)

📓 Wiki

Welcome to our humble abode. You’re currrently viewing Bot Designer for Discord’s wiki.

📂 Wiki Index

• Guides
• Resources
• BDScript
• Premium
• JavaScript
• Callbacks

Want to contribute to the wiki?

Head over to the GitHub repository contribution file and learn how you can help out!

Changelog

2024

July

• Added $setUserRoles[]
• Added $getLeaderboardPosition[]
• Added $isBooster[]

2023

June

• Fixed custom images not always being displayed
• Allowed for empty string values in $jsonSetString[]
• Added $jsonArraySort[]
• Added $jsonArrayReverse[]
• JSON Array function now can interact with JSON root
• Emoji argument now allows for emoji aliases
• Added $nodeVersion[]
• Added $removeEmoji[]
• Added $addMessageReactions[]
• Fixed $nickname[] to work with the new Discord username system
• Added $displayName[]
• Added $userBadges[]
• Added $userBannerColor[]

2022

December

• Added limit on input numbers to 2¹²⁸ on the basic math functions
• Fixed BDScript 2 having problems with handling unicode characters
• Fixed $stop causing undefined behaviour
• Added $getBanReason[]
• Fixed caching issues for the text splitting functions
• Fixed issues with custom images

2021

December

• Saving a command no longer causes the bot to restart
• Fixed $noMentionMessage[] in BDScript 2
• Added $timeout[] and $untimeout[]
• $mute[] and $unmute[] has been marked as deprecated
• Added guildID argument to $getUserVar[] and $setUserVar[]
• Fixed the issue with some bots not starting with invalid intents enabled
• Fixed the role cache
• Slash command’s option description is now required
• Added $shardID[]
• Added sharding
• Improved interaction handling
• Added $defer
• Fixed getting invites
• Added debug information inside the app for translators
• Fixed $serverNames
• Added % (modulo) to $calculate[]
• Fixed removing custom images
• Added missing permissions
• Fixed unintentional server restarts
• The last argument in $replaceText[] is now optional

2019

December

• Fixed high ping issues
• Fixed whole bunch of other issues
• Added to JS:
  • authorId,
  • channelId,
  • userMentions,
  • roleMentions,
  • unban(),
  • takeRole(),
  • giveRole(),
  • channelTyping(),
  • createChannel(),
  • removeChannel(),
  • unpinMessage(),
  • banWithReason(),
  • kickWithReason(),
  • removeRole(),
  • createRole()
• Created status website https://status.botdesignerdiscord.com
• Web version of Bot Designer for Discord has been moved to new address https://botdesignerdiscord.com
• Fixed some issues in web version
• Fixed $banID[]
• Preparations for premium points

If you want to access this changelog externally, we have a JSON version of the changelog to which you can send a GET request and work with a JSON document further.

Terms of service

Your use of our service (“Bot Designer for Discord”) implies that you agree to the Terms stated on this page, and these Terms will remain in effect while you use the service.

Context and Reference

• “Bot Designer for Discord” refers to “our service”.

• “our service” refers to the mobile application, “web app”, and any other related product or service that Bot Designer for Discord provides. It should be noted that Bot Designer for Discord is a service provided by company NilPointer Software.

• “web app” refers to our web panel (the “web app” is accessible via most major web browsers) from which users may modify their bot(s) and/or account.

• “template store” refers to the platform which Bot Designer for Discord’s mobile application provides. It serves as a way for users to share and use bot command code(s).

• “bot” refers to a user’s Discord Bot. A “(bot) command” is a certain order which can be called by a user (a “user” referring to anyone that has access, not just a user of our service in this case) typically in a Discord text or DM channel.

• “using our service” refers to having the application installed on your device, being logged in to our web app, or accessing any related product or service. If you use our service, you are considered a “user”. When the phrase “user” is utilized in these Terms; it refers to an individual using our service (unless stated otherwise).

• “spam” refers to an action that’s repeated in mass form.

• “Premium Points” are our in-app currency which users can buy via the premium points store. A premium point grants the user one week of premium-hosting for a singular bot, which allows for some extra functionalities that the app provides for said amount of time. For premium-hosted bots, we do guarantee 90% of uptime per week. If it is less, the user (after contacting support), will receive some sort of compensation (e.g. Premium Points) if applicable.

• “promo codes” or “promocodes” are codes (randomized text) that transfer into bot hosting time. Promo codes can be earned by winning an event, giveaway, or Discord Nitro Boosting our Discord Server.

• Users can get free bot hosting time by watching advertisements; using the one-time hosting without-AD button; using Premium Point(s); or by receiving a hosting time promo code.

• “bug” refers to unintended behavior happening, often these “bugs” can be observed by users.

• “token” refers to a Discord Bot Token, a token is essentially a password (and should be treated as such) which grants full access to the bot.

• “ban” refers to a user of our service being temporarily or permanently suspended from using our service.

• “warn”/“warning” refers to a user of our service being notified that they neglected to comply with one or more of our Terms.

Terms

1. You agree that you will not contribute any content/actions that use our service or interact with our service in a manner that:

   1. is dangerous, harmful, fraudulent, deceptive, threatening, harassing, defamatory, obscene, or otherwise objectionable.

   2. is any form of “spam”, or any processes that interfere with Bot Designer for Discord’s services. As an example, mass creating or modifying your bot(s) with the intent of crashing or otherwise harming the service.

   3. infringes or violates the intellectual property rights or any other rights of anyone else, including ours.

2. You agree to not decompile or modify our software in any way. We may take legal steps if we detect these actions.

3. You understand that we reserve the right to warn/ban users of our service, for any reason and without previous notice; even if the user isn’t directly violating our Terms. You also understand, we may ban any user that breaks Discord’s Terms of Service and/or Discord’s Community Guidelines.

4. You agree not to spam or overuse our computing/storage resources.

5. You agree not to resell your Bot Designer for Discord account, “Premium Points”, or “promo codes”.

6. You agree not to exploit a detected bug. It should be sent as a report to the developers instead.

7. You agree to cope with any applicable limitations that Bot Designer for Discord has. This includes the 2,399 guild limit per bot. We do not guarantee any amount of uptime (for non-premium hosted bots), however hosting is our best effort.

8. You understand that prices for Premium Points should, but may not include; sales and use taxes. If they do not, the user is responsible for the payment of such taxes related to the purchase.

9. When submitting or using Bot Designer for Discord’s “Template store” feature, you are agreeing to the Template Store Terms.

10. You agree to our Privacy Policy.

11. You agree to first contact support before reversing your payment method if you have purchased Premium Points.

12. You agree we shall not be held liable for users that abuse our service to perform malicious, or otherwise unlawful ventures. However, as stated previously in these Terms; we do uphold the right to warn/ban in these circumstances.

We reserve the right to change, modify, add, or remove portions of our Terms at any time, and you will still be expected to comply. It is recommended to check this page periodically for changes.

We may warn/ban users if we discover they didn’t comply with these Terms.

All your usage and access to our service is subject to these stated Terms, if you do not agree with them, you shall not use the service.

In case we change our Terms, if you don’t agree with the new Terms, you are free to reject them by no longer using our service.

Registered users may withdraw their data through the mobile application, and request the deletion of data by contacting support.

Contact

If you have questions/concerns about these Terms or our service, you may contact us via email.

Support for regular users is available at support@mail.botdesignerdiscord.com and for paying users at premium-support@mail.botdesignerdiscord.com.

Context

• Bot Designer for Discord is a service provided by NilPointer Software.
• “Our service” refers to “Bot Designer for Discord”.
• “Bot” refers to data held by BDFD describing the behaviour of a Discord Bot on our service.
• “Hosting time” refers to the time duration left of a singular bot during which it will be hosted by our service.
• “Premium point” refers to BDFD premium in-app currency, granting users the ability for bots to have extended functionality for a limited time.
• “Premium time” refers to the time duration left for a singular bot during which it can access the extended functionality. Premium time is related, but not strictly linked, with hosting time. Premium time might end before hosting time, but not vice-versa.
• “Promocode” or “promo code” refers to a randomly generated string of characters used to gain hosting or premium time.
• “BDFD entity” or “entity” refers to any piece of data that is being held by BDFD, that ownership of it or itself can be transferred. In this policy, “entity” mainly refers to bots, hosting and premium time, and premium points.
• “Transfer request” refers to a request made by a user to BDFD developers for an entity transfer. These requests can be made through a ticket on our official Discord server.

Policy

• Entities that can be transferred can only be transferred through a transfer request by the user that holds ownership of that entity.

• Requesting users must provide proof of ownership of the entities in question for the request to be granted.

• BDFD Accounts can not be transferred in any way.

• Bots can only be transferred between BDFD accounts owned by a single user.

• Bot after its transfer retains any hosting or premium time the bot in question had left.

• A bot previously not assigned to any BDFD account can be transferred to an account of the user that holds ownership over the bot in question.

• Premium points can be transferred between BDFD accounts owned by a single user.

• Premium points can be donated for a giveaway promotion on our official Discord server.

• Hosting and Premium time can only be transferred between bots owned by a single user.

• Hosting and Premium time can not be transferred to a promocode.

• Only premium time can be donated for a giveaway promotion on our official Discord server.

Guides

In this section, you’ll find guides that contain helpful tutorials on certain elements of the app. These contain example codes and images to help explain functions and their usages.
Here you can learn how to create your first BDFD bot, as well as how to use functions such as select menus, buttons, and more!

Beginning

In this guide, you will learn how to create your own bot using BDFD.

Content

Functions Used > Creating > Inviting > First Code > Bot Online > Test it!

Functions Used

• $nomention

Step 1: Creating

• Go to Discord Developer Portal.
• Click on the “New Application” button and provide a name for your application.
• In top-left corner, click on the hamburger icon (≡) and select the “Bots” tab.
• Once done, press the “Reset Token” button and copy your bot token.

Never share your Discord bot token with anyone. Learn more

• Now, open your BDFD app (If you haven’t installed the app yet, head over to Play Store/App Store and download it) and press “Create New Bot”.

Make sure that when you are creating a new bot, your Discord account is signed into the BDFD app. This is so that you don’t lose access to your bot in the future.

• Enter your bot’s name and its token (the one that you copied earlier from the Discord Developer Portal).
• If you have a share code, toggle on “Use share code” and put the code into the text field.
• After agreeing to the Terms of Service of both BDFD & Discord, press “Create bot” to create your Discord bot.

Step 2: Inviting

• Open the BDFD app and select your bot.
• Click on the “Invite bot to server” button.
• Press the “Edit invite link permissions” button and choose the permissions that the bot will have when joining a server.
• Then, click on “Add your bot to your server” and select the server.
• Click on the “Continue” button and your bot will be added to the selected server.

Step 3: First Code

To create the first command, you must click on the “Commands” tab after selecting your bot and press on the “+ Command creator”. You will see 3 categories (“Command Name”, “Command Trigger”, “Template Functions”).

• Come up with a name for your command and paste it into the “Command Name” field. (You can leave it blank).
• Now come up with a trigger for the command. (Example: !ping).

It is important that the trigger of the command matches its meaning.

After completing the command setup, press the “Create Command” button. Now you can create your first code! In “Reply Message” you can paste this code:

$nomention
Pong!

• Click on “Save command” to save the code.

Step 4: Bot Online

Method 1 - 30 Minutes

• Click on the “Dashboard” tab after selecting your bot and press on the “+ Add free hosting time” button.
• Enter the indicated numbers and click “Confirm”.

Note: This method only works when your bot is offline.

Method 2 - 140 Minutes

• Press on “Dashboard” tab after selecting your bot and click on “+ Watch ad for 140 minutes of free hosting time”.
• After watching the ad, your bot will receive 140 minutes of hosting time.

Method 3 - Premium

• Use premium points to get hosting time without watching ads.

If the bot is not online after these methods, then take a look at this page: Why my bot is offline?

Step 5: Test it!

Send a !ping command in a channel of the server you invited your bot to.

Bot Status

Here, you will learn how to set-up a custom bot status & activity.

Status

To set a custom status,

• Select your bot.

• Go to the “Status” tab and press gear icon ⚙️ at top-right corner.

• Toggle on “Enable bot presence”.

• In “Bot status”, choose your preferred bot presence (i.e Online, Idle, Invisible etc.)

• In “Interval amount”, set a custom interval duration. This changes how many seconds your bot will wait before refreshing its status (Minimum interval duration is 12 seconds while maximum is 600 seconds).

  📝 If you have multiple bot status entries, it will switch to next status instead of refreshing current status.

Activity

⚠️ You need to toggle on Enable bot presence in “Bot status settings” in order to show activity.

To set custom rich presence,

• Select your bot.
• Go to the “Status” tab and press Add new entry.
• Choose activity type (i.e PLAYING, STREAMING, LISTENING etc.) in the “Status prefix” dropdown selection.
• In “Status”, type any text that you would like to display as your bot’s status. Additionally, you can also use some BDFD functions in your bot’s status.
• “Status details” is just a text for you to see. It won’t display anywhere.
• Save the changes.

📝 If the activity type is STREAMING, there will be an additional required field called “Streaming URL”. You can only put either YouTube or Twitch URL.

Available functions

Here are the available functions that you can use in your bot’s status:

• $membersCount

  Returns your bot total members count.

• $serverCount

  Returns your bot total server count.

• $numberSeparator[number;(separator)]

  Separates numbers in thousands format.

Example

Commands Anatomy

There are 3 main components to commands, these are: Name, Trigger and Code.

Command Names

Think of this like a note. Command names don’t impact your command at all, but they can help you find commands within the app. You can leave this field empty if you choose.

Command Triggers

What the user types to run the command. Triggers should contain both a prefix (e.g !) and the actual command name (like help). This combines to !help. Do not include any spaces at the end of the trigger. Triggers are case sensitive (unless the premium function: $ignoreTriggerCase is used in the command code). You can use callbacks in this field.

Command Code

The soul of your command. This is what the bot responds when the command is executed, you can use functions like $ping and $message here.

Example

Output

Gateway Intents

In this guide, you will learn about Discord’s Gateway Intents and how to enable them in BDFD.

What are Gateway Intents?

When a bot is connected to the Discord Gateway, it receives events on actions happening on Discord. Bots can receive a large amount of events from Discord, so in order to decrease the amount of events each bot receives, Discord requires bots to send Gateway Intents when connecting to the Gateway.
Gateway Intents allow to specify which events the bot wants to receive.

Gateway Intents can be further divided into:

• Standard Intents¹
• Privileged Intents

For example, a bot needs to send the GUILD_MESSAGES standard intent and the MESSAGE_CONTENT privileged intent to receive the MESSAGE_CREATE event with the messsage content.

📚 Learn more about Gateway Intents here.

Privileged Gateway Intents

Privileged Gateway Intents are special intents which need to be manually enabled in your bot application settings. Due to their sensitive information nature, Discord disables them by default. You should only enable them when it is required.

Currently, there are only 3 privileged gateway intents:

• GUILD_MEMBERS
• GUILD_PRESENCES
• MESSAGE_CONTENT

📌 Verified bots require approval from Discord in order to enable these intents.

Presence Intent

Allows the bot to receive PRESENCE_UPDATE event. This intent is primarily used to allow for retrieval of user presences data. For example, Activities (i.e PLAYING, LISTENING), Presence (i.e Online, Idle) and Custom status.

The following functions require this intent:

• $getCustomStatus[]
• $getUserStatus[]
• $membersCount[]

Server Members Intent

Allows the bot to receive GUILD_MEMBER_ADD, GUILD_MEMBER_UPDATE, GUILD_MEMBER_REMOVE, and THREAD_MEMBERS_UPDATE events. This intent is primarily required to fetch the entire list of guild members, and to receive specific guild member info (like guild joining, leaving, profile update etc.).

The following callbacks require this intent:

• $onJoined[]
• $onLeave[]

Message Content Intent

Unlike the two intents above, Message Content Intent doesn’t allow for any new events. Instead, it allows the bot to receive message content data, which includes content, attachments, embeds, and components.

If your bot is based on prefix-based commands, then this intent is required. Otherwise, you will need to use slash commands instead.

📌 Without this intent, your bot can only read message content data in DMs, messages where your bot was mentioned, and it’s own messages.

The following functions/callbacks require this intent:

• $awaitedCommand[]
• $messageContains[]
• $argsCheck
• $banID (First & Second Usage)
• $getEmbedData
• $getMessage (Only for content type)
• $ignoreTriggerCase
• $message
• $noMentionMessage
• $removeContains
• $trimContent
• $unban
• $unbanID

Enabling Privileged Gateway Intents

To enable Privileged Gateway Intents in your bot, follow these steps:

1. Open your bot dashboard in the BDFD app (Make sure your app version is 2.2.2 or above).

2. Click on the “Settings” tab, and then on “Go to gateway intents settings”.

3. After that, click on “Change gateway intents on Developer Portal”.

4. Select your required intents and save the changes.

   📌 The intents you have enabled in the Developer portal should be reflected in the BDFD app. If they aren’t, click on “Sync intents with Developer Portal settings”.

Example

Variables

Introduction

Variables are how we store data in BDFD. Data can be assigned to users, servers, channels, and globally. Each variable has two elements, which we will breakdown in this section.

Variable Elements

• Name: The name of the variable. This can’t be modified by the bot, its used to “call” the current variable.
• Value: The value of the variable. This can be modified by the bot, its returned when the variable name is called in $getVar/$getUserVar/$getServerVar/$getChannelVar.

Creating Variables

📌 Creating variables can only be done in the app.

Here’s how to create a variable, which you can get and modify later:

1. Select the bot you want to add the new variable to.

2. Go to “Variables” tab.

   

3. Then, click “+ New variable” button.

   

4. Give the variable a name and value.

   

5. Finally, save the changes!

   

Editing Variables

Here’s how you can modify an existing variable’s name/default value:

1. Select the bot you want to edit the variable for.

2. Go to “Variables” tab.

   

3. Click the edit/pencil icon near the variable name that you want to edit.

   

4. Provide a new variable name and/or value.

   

5. Finally, save the changes!

   

Deleting Variables

Here’s how you can delete variables:

1. Select the bot you want to delete the variable for.

2. Go to “Variables” tab.

   

3. Select the variable you want to delete.

   

4. Finally, confirm the deletion!

   

📌 Deleting variables might return error message in those commands which were using the deleted variables.

Global/Global-User Variables

$setVar/$getVar are global variable functions, which means they apply universally (i.e they don’t change per-server, per-channel, or per-user).
However, if you provide a user ID in the optional User ID parameter then it becomes a global-user variable.

Global-user variables value stay same with the user in every server. The usage of global-user variables looks like this:

• $setVar[Variable Name;New Value;User ID]
• $getVar[Variable Name;User ID]

Global Variables - Functions

• $setVar[Variable Name;New Value]: Changes the provided global-variable’s value to ‘New Value’.
• $getVar[Variable Name]: Gets the current value of the provided global-variable.

📌 Global variables are universal, meaning if the variable gets modified, the modification applies to everyone.

Global Variables - Example

This is the variable we’re working with:

This command adds 1 cool point to the ‘CoolCount’ variable value, everytime it is ran.

$nomention
$setVar[CoolCount;$sum[$getVar[CoolCount];1]]
Cool counter updated! 😎
$c[Updates the variable for all servers.]

This command returns how many cool points have been earned.

$nomention
Cool counter is at $getVar[CoolCount] currently! Keep running `!cool` for more cool points.
$c[This is the same for everyone, no matter who runs it.]

Global-User Variables - Functions

• $setVar[Variable Name;New Value;User ID]: Sets the provided variable to ‘New Value’ for the provided ‘User ID’.
• $getVar[Variable Name;User ID]: Gets the provided variable’s value for the given ‘User ID’.

📌 Global-user variables stay with the user in every server. Unlike user variables which are unique per-user and differ in each server.

Global-User Variables - Examples

This is the variable we’re working with:

This command modifies the user’s bio.

$nomention
$argsCheck[>1;❌ Please provide text!]
$setVar[Bio;$noMentionMessage;$authorID]
Successfully updated your bio!
$c[Updates the variable for the user in all servers.]

This command returns the user’s current bio.

$nomention
**<@$mentioned[1;yes]>'s Bio:**
$getVar[Bio;$mentioned[1;yes]]
$c[Gets the author/mentioned-user's current bio.]

User Variables

User variables are unique per-user and differ in each server.

User Variables - Functions

• $setUserVar[Variable Name;New Value;(User ID;Guild ID)]: Sets the provided variable to ‘New Value’ for the given ‘User ID’ and ‘Guild ID’, or the author of the command if no ‘User ID’ is provided and current guild if no ‘Guild ID’ is provided.
• $getUserVar[Variable Name;(User ID;Guild ID)]: Gets the current value for the provided user variable. Returns the author’s variable value if no ‘User ID’ is provided and uses the current guild if no ‘Guild ID’ is provided.

User Variables - Examples

⚠️ This example would require premium to be fully functional! ⚠️

Here’s the variable we’re working with:

This command adds 1 to the user’s ‘Mentions’ variable, everytime the user mentions someone.

📌 The trigger for this command would be $messageContains[<@].

$nomention
$setUserVar[Mentions;$sum[$getUserVar[Mentions];1]]

This command returns how many times the user has mentioned others, in the current server:

$nomention
You have mentioned others `$getUserVar[Mentions]` times in $serverName[$guildID]!

Server Variables

Server variables are unique per-server.

Server Variables - Functions

• $setServerVar[Variable Name;New Value;(Server ID)]: Sets the provided variable to ‘New Value’ for the given ‘Server ID’, or the server that the command was ran in; if no ‘Server ID’ was provided.
• $getServerVar[Variable Name;(Server ID)]: Gets the current value for the provided server variable. Returns the current server’s variable value if no ‘Server ID’ is provided.

Server Variables - Examples

Here’s the variable we’re working with:

This command adds 1 cookie to the ‘ServerCookies’ variable value, everytime it is ran.

$nomention
This server now has `$sum[$getServerVar[ServerCookies];1]` cookies picked 🍪
$setServerVar[ServerCookies;$sum[$getServerVar[ServerCookies];1]]

This command returns how many cookies the server has currently.

$nomention
Total Server Cookies: 🍪 $getServerVar[ServerCookies]

Channel Variables - Functions

• $setChannelVar[Variable Name;New Value;(Channel ID)]: Sets the provided variable to ‘New Value’ for the provided ‘Channel ID’, or the channel that the command was ran in; if no ‘Channel ID’ was provided.
• $getChannelVar[Variable Name;(Channel ID)]: Gets the current value for the provided channel variable. Returns the current channel’s variable value if no ‘Channel ID’ is provided.

Channel Variables - Examples

Here’s the variable we’re working with:

This command adds 1 uses to the ‘Uses’ variable value, everytime it is ran.

📌 The trigger for this command will be your bot’s prefix, example: !.

$nomention
This channel has now `$sum[$getChannelVar[Uses];1]` uses of the command.
$setChannelVar[Uses;$sum[$getChannelVar[Uses];1]]

This command returns how many command uses the channel has currently.

$nomention
Command used `$getChannelVar[Uses]` times in this channel

Economy

Local vs Global

• Local Economy: Changes per server. If a user has 10,000 coins in one server, in another server they would have a different amount. For example, Unbelievaboat has a local economy. (local economy uses user-variables)
• Global Economy: Does not change per server. If a user has 10,000 coins in one server, in another server they would have the same amount. For example, Dank Memer has a global economy. (global economy uses global-user variables)

Local Economy

• Replace “Money” with your cash/money variable, if “Money” is the name of your money variable then you can just leave it as is!
• Replace “Amount” with the amount of money you want to add/remove to/from the user. Like this: 100, $random[1;11], $random[100;1001], 10000.

Gets the user’s current balance. If a user mention is provided, then the bot will return that user’s balance:

$getUserVar[Money;$mentioned[1;yes]]

Adds money to the mentioned user:

$setUserVar[Money;$sum[Amount;$getUserVar[Money;$mentioned[1]]];$mentioned[1]]

Adds money to the user running the command:

$setUserVar[Money;$sum[Amount;$getUserVar[Money]]]

Removes money to the mentioned user:

$setUserVar[Money;$sub[Amount;$getUserVar[Money;$mentioned[1]]];$mentioned[1]]

Removes money from the user running the command:

$setUserVar[Money;$sub[Amount;$getUserVar[Money]]]

Leaderboard:

$userLeaderboard[Money;asc]

Global Economy

• Replace “Money” with your cash/money variable, if “Money” is the name of your money variable then you can just leave it as is!
• Replace “Amount” with the amount of money you want to add/remove to/from the user. Like this: 100, $random[1;11], $random[100;1001], 10000.

Gets the user’s current balance/amount of money. If a user mention is provided then the bot will return that user’s balance:

$getVar[Money;$mentioned[1;yes]]

Adds money to the mentioned user:

$setVar[Money;$sum[Amount;$getVar[Money;$mentioned[1]]];$mentioned[1]]

Adds money to the user running the command:

$setVar[Money;$sum[Amount;$getVar[Money;$authorID]];$authorID]

Removes money to the mentioned user:

$setVar[Money;$sub[Amount;$getVar[Money;$mentioned[1]]];$mentioned[1]]

Removes money from the user running the command:

$setVar[Money;$sub[Amount;$getVar[Money;$authorID]];$authorID]

Global leaderboard:

$globalUserLeaderboard[Money;asc]

Leaderboards

You can generate variable leaderboards, using the functions below.

• $globalUserLeaderboard - Global-User Variables.
• $userLeaderboard - User Variables.
• $serverLeaderboard - Server Variables.
• $getLeaderboardValue - Fetchs leaderboard value.

BDScript 2

Introduction

BDScript 2 is the default in-app scripting language (as of October 2021). It has been created with intention of enhancing its capabilities and fixing some of the problems previous versions had.

The first edition of BDScript has one big issue, commands like $sum[$sum[3;2];1] didn’t work. The reason it didn’t work is because BDScript has a pre-defined order for executing functions.

In order to fix the issue, a new BDScript edition was developed called BDScript Unstable. It executes function in a command from bottom to top and from right to left. It fixes the issue, but the new edition has its quirks which could be problematic for some commands. That’s where BDScript 2 comes in. This edition executes commands from top to bottom and from left to right (basically, just the way you read most of the books).
Besides that, BDScript 2 has additional features like $eval[], $try and $catch and more.

Features

$eval[]

Evaluates the provided BDScript code. Read this for more information.

$try, $catch and $error[]

This works in a very similar way to the equivalents available in other programming languages.
You can read more about it here.

$async

Runs functions asynchronously. Read Async Guide for more information.

$elseif

Read If Statements Guide for more information.

$var[]

Creates a temporary variable. Read this for more information.

$stop

It stops the command execution. It may seem like a useless function but it can come in handy with $ifs or $trys.

$optOff[]

Executes functions with turned off optimizations. Read this for more information.

Async

Runs functions in the background. Using async features properly can optimize your code and make it faster!

Warning: Async features only work in BDScript 2.

Basics

• Use $async[name] to start an async block. The name must be unique for each block. Functions inside async blocks run in the background without blocking the command’s thread.
• Use $endasync to end the async block.
• Use $await[name] to wait for the async block’s result.

Examples

Example #1

$async[test]
  $setVar[money;0]
  $addReactions[👌]
$endasync

Money set to 0

Example #2

$async[test1]
  $setVar[banned;1]
$endasync

$async[test2]
  $banID[some reason;246604909451935745]
$endasync

$await[test1]
$await[test2]

Done

Error Handling

In BDScript 2 you can handle errors returned by functions or limiters (such as $cooldown[] or $onlyIf[]).

Error Handling Functions

$try

Used to open the Error Handling block.

$endtry

Used to close the Error Handling block.

$catch

Used to create a sub-block between $try and $endtry that will contain the code that will be executed when an error occurs.

$error[]

Used in the $catch block to return error information.

Possible Arguments

• command - returns the name of the function that returned the error.
• message - returns the error message that was received.
• source - returns the content of the line where the error occurred.
• row - returns the number of the row in the code where the error occurred.
• column - returns the number of the column in the code where the error occurred.

Examples

Function Error

$nomention

$try
  $color[FFFFFF]
  $title[Hi]
  $description[Some broken code;]
$catch
  $color[E74C3C]
  $title[Error Handling]
  $addField[Function:;$error[command]]
  $addField[Error:;$error[message]]
$endtry

Limiter Error

As a way to use Error Handling with Limiter Errors, we’ll use $cooldown[]. With the help of Error Handling, we can make a nice cooldown error message.

To handle only the error of our limiter, we will use a temporary variable and if statements. If $cooldown[] returns an error, the value of the temporary variable will be set to true (in which case our nice error message will be sent).

Note: The error message argument in $cooldown[] must be left blank.

$nomention

$var[cooldownError;false]

$try
  $cooldown[3m;]
$catch
  $var[cooldownError;true]
$endtry

$if[$var[cooldownError]==false]
Hey $username, are you making an example for the guide?
$else
$color[E74C3C]
$author[Oops, $username!]
$authorIcon[$authorAvatar]
$title[You have a cooldown!]
$description[Come back <t:$sum[$getTimestamp;$getCooldown[normal]]:R>.]
$endif

Buttons

In this section, you’ll learn how to use the button component.

Content

Functions Used > Button Style > Button Type > $addButton[] > $editButton[] > $removeButtons > $removeButtons[] > $removeComponent[] > Create Interaction

Functions Used

• $addButton[]
• $editButton[]
• $removeButtons
• $removeButtons[]
• $removeComponent[]
• $onInteraction
• $onInteraction[]

Button Style

Buttons can have different styles (background colors). Here, are all possible values for the style function argument.

• primary - Blue button
• secondary - Gray button
• success - Green button
• danger - Red button
• link - Redirect button

If link style is used, the button won’t send any interactions!

Button Type

There are 2 types of buttons : interactive and link.

When an interactive button is pressed, it sends an interaction which can be used together with $onInteraction[ID].

Every interactive button has an ID. A $onInteraction[ID] callback, will only get triggered when the button with the same ID is pressed. Interactive buttons can use every style except link.

Link buttons don’t send any interactions. When they’re pressed they forward the user to a website.

Link buttons need to set their style argument value to link.

$addButton

Adds a button to the response message.

Syntax

$addButton[New row?;Interaction ID/url;Label;Style;(Disable?;Emoji;Message ID)]

Parameters

• New row? (Type: Bool || Flag: Required): If set to yes the button will appear in a new row. If it’s set to no the button will appear in the same row as a previous button.

  A message can have a maximum of 25 buttons (5 rows of 5 buttons).

• Interaction ID/URL (Type: String, URL || Flag: Required): Depending on the button type, you either set it to an Interaction ID which is then used in the $onInteraction[Interaction ID] or $onInteraction callback or a URL if it’s a link button.

You don’t need $onInteraction/$onInteraction[] for URL.

• Label (Type: String || Flag: Emptiable): The text visible on the button.
• Style (Type: Enum || Flag: Required): It’s used to specify the button’s background color. If the button has a link/url you have to set this value to link. Check this section for more details.
• Disable? (Type: Bool || Flag: Vacantable): If set to yes the button can’t be pressed. Defaults as no.
• Emoji (Type: Emoji || Flag: Vacantable): Adds an emoji inside the button. Emojis have to be either pasted as unicode or be in the following format <:emoji name:emoji ID>.
• message ID (Type: Snowflake || Flag: Vacantable): Adds a button to the provided message ID. It’s important to note that provided message ID author has to be the bot.

Interactive buttons can’t have duplicated ID’s in the same message. So for example, you can’t have two buttons with the ID set to test.

If URL is used in Interaction ID/url argument, it has to start with http:// or https://

Example

$nomention
Hello
$addButton[no;test;Say hello!;primary;no;]

$editButton

Edits an already existing button.

Syntax

$editButton[Interaction ID/URL;Label;Style;(Disable?;Emoji;Message ID)]

Parameters

• Interaction ID/URL (Type: String, URL || Flag: Required): Depending on the button type, you either set it to an Interaction ID which is then used in the $onInteraction[Interaction ID] callback or a URL if it’s a link button.
• Label (Type: String || Flag: Emptiable): The text visible on the button.
• Style (Type: Enum || Flag: Required): It’s used to specify the button’s background color. If the button has a link/url you have to set this value to link. Check this section for more details.
• Disable? (Type: Bool || Flag: Vacantable): If set to yes the button can’t be pressed. Defaults as no. (Optional)
• Emoji (Type: Emoji || Flag: Vacantable): Edits an emoji inside the button. Emojis have to be either pasted as unicode or be in the following format <:emoji name:emoji ID>. (Optional)
• Message ID (Type: Snowflake || Flag: Vacantable): Edits a button in a message with the provided ID. It’s important to note that provided message ID author has to be the bot. (Optional)

Example

Trigger: $onInteraction[test]

$nomention
$username said hello!
$editButton[test;Say hello!;danger;yes;]

$removeButtons

Removes all buttons from the triggered message.

Syntax

$removeButtons

Example

Trigger: $onInteraction[test]

$nomention
$username removed all buttons from this message
$removeButtons

$removeButtons[]

Removes all buttons from the specified message.

Syntax

$removeButtons[Message ID]

Parameters

• Message ID (Type: Snowflake || Flag: Required): Removes buttons from the message with the provided ID. It’s important to note that provided message ID author has to be the bot.

Example

$nomention
$username removed all buttons from the specified message id
$removeButtons[$message]

$removeComponent

Removes a certain component from a message.

Syntax

$removeComponent[Interaction ID/URL;(Message ID)]

This function supports select-menu and button.

Parameters

• Interaction ID/URL (Type: String || Flag: Required): The interaction ID of the button, to remove from the message.
• Message ID (Type: Snowflake || Flag: Vacantable): Removes the button from the message with the provided ID. It’s important to note that provided message ID author has to be the bot. (Optional)

Example

$nomention
$username successfully removed the button!
$removeComponent[test;$message]

Create interaction

Example with $onInteraction[] callback:

1. Create two commands with !example and $onInteraction[test] triggers.
2. Paste the following code: Code for the command with the !example trigger:

$nomention
Click the button below!
$addButton[no;test;Click;primary]
$addButton[no;button;Button disabled;secondary;yes]
$addButton[yes;https://botdesignerdiscord.com/;Link;link]

Code for the command with the $onInteraction[test] trigger:

$nomention
$editButton[test;Clicked;danger;yes]
$sendMessage[$username hello!]

Note that the interaction ID provided in $onInteraction[] is the same as the one provided in $addButton[]

In $addButton[], yes is being used for the new row? argument so that the button would appear in the next row.

3. Execute command !example

Example with $onInteraction callback:

1. Create two commands with !example and $onInteraction triggers.
2. Paste the following code: Code for the command with the !example trigger:

$nomention
Click the button below!
$addButton[no;test;Click;primary]
$addButton[no;button;Button disabled;secondary;yes]
$addButton[yes;https://botdesignerdiscord.com/;Link;link]

Code for the command with the $onInteraction trigger:

$nomention
$if[$customID==test]
    $editButton[test;Clicked;danger;yes]
    $sendMessage[$username hello!]
$endif

Note that the interaction ID returned by $customID will be the same as the one provided in $addButton[]

In $addButton[], yes is being used for the new row? argument so that the button would appear in the next row.

3. Execute command !example

How $onInteraction or $onInteraction[] works?

Modals

In this section, you’ll learn how to use the modal message component.

⚠️ Warning: Modals are only supported for interaction responses (like slash commands, buttons, select menus, etc), you can’t open a modal from just a message command.

Creating a Modal

$newModal[Modal ID;Title]

• Modal ID - Used in $onInteraction[ID] callback. It works same way as buttons and select menus.
• Title - The text which is displayed on top of a modal. This value must be less than or equal to 45 characters.

Adding Input Fields

$addTextInput[Text Input ID;Style;Label;(Minimum length;Maximum length;Required;Value;Placeholder)]

• Text Input ID - ID that is used to retrieve the text input in the field. This value must be unique. (Used in $input[Text Input ID])

• Style - The text input field style, either short or paragraph.

  

• Label - Name of the text input field. This value must be less than or equal to 45 characters.

• Minimum length - Minimum number of characters a user needs to input. This value must be an integer between 0 and 4000, and can’t be greater than the Maximum length.

• Maximum length - Maximum number of characters a user can input. This value must be an integer between 0 and 4000, and can’t be less than the Minimum length.

• Required - Whether a user must fill in the text input field, defaults to true.

• Value - The text that is written by default in the text input field. This value must be less than or equal to 4000 characters and must not be less than Minimum length and no more than Maximum length.

• Placeholder - The text that is displayed if the text input field is empty. This value must be less than or equal to 100 characters.

🧙‍♂️ Note: You can’t add more than 5 text input fields.

Getting Input from a Modal Submission

Use this function in response to the modal submission interaction:

$input[Text Input ID]

• Text Input ID - The text input field to get the user’s input from.

Example

Command Trigger: !modal | Command Code:

$nomention
Modal Example
$addButton[no;bio;Click me!;primary]

Command Trigger: $onInteraction[bio] | Command Code:

$nomention
$newModal[modal;User Bio]
$addTextInput[modalInput1;short;What is your name?;3;30;yes;;Mikołaj]
$addTextInput[modalInput2;short;What are your pronouns?;2;30;yes;;He/Him]
$addTextInput[modalInput3;paragraph;Can you tell us about yourself?;5;1000;no;;I am a Developer]

🤔 Explanation: The code above executes when the button from the previous code gets clicked. So, when the user clicks the button the modal appears.

Command Trigger: $onInteraction[modal] | Command Code:

$nomention
Name : $input[modalInput1]
Pronouns : $input[modalInput2]
About me : $input[modalInput3]

🤔 Explanation: The code above executes when the modal is submitted, because in the previous command we inputted the custom ID ‘modal’ into the $newModal[] function: $newModal[modal;User Bio].

Result

Select Menu

In this section you’ll learn how to use the select menu component.

Creating a Select Menu

$newSelectMenu[Menu ID;Min;Max;(Placeholder;Message ID)]

• Menu ID - it’s used for $onInteraction[ID] callback. It works the same way as buttons.
• Min - minimum amount of values that can be selected.
• Max - maximum amount of values that can be selected.
• Placeholder - it’s a text that appears if no option is selected.
• Message ID - ID of a message that should have select menu added to it. By default it’s the bot’s response.

Adding an Option

$addSelectMenuOption[Menu option ID;Label;Value;Description;(Default;Emoji;Message ID)]

• Menu option ID - it has to be the same as the ID used in $newSelectMenu[].
• Label - the name of the option.
• Value - it’s the data that gets passed to $onInteraction[] callback. The value has to be unique in the select menu!
• Description - it shows up under the label.
• Default - should the option be selected by default. There can be only one default option!
• Emoji - it shows up next to the label.
• Message ID - same as in $newSelectMenu[].

Example

Select Menu Code

$newSelectMenu[Example;1;1;Choose some option]
$addSelectMenuOption[Example;First;first-option;The first option]
$addSelectMenuOption[Example;Second;second-option;The second option]
$addSelectMenuOption[Example;Third;third-option;The third option]

Interaction Code

$onInteraction[Example]

$if[$message==first-option]
You have chosen the first option
$elseif[$message==second-option]
You have chosen the second option
$elseif[$message==third-option]
You have chosen the third option
$endif

Usage

Multi-Select Menu

In the Select Menu you can choose not only one option, but several at once. You could understand this by the presence of arguments Min and Max.

Example

Select Menu Code

Here we will change the argument Max to 3.

$newSelectMenu[Example;1;3;Choose some option]
$addSelectMenuOption[Example;First;first-option;The first option]
$addSelectMenuOption[Example;Second;second-option;The second option]
$addSelectMenuOption[Example;Third;third-option;The third option]

Interaction Code

$if[$checkContains[$message;first-option]==true]
$addCmdReactions[1️⃣]
$endif

$if[$checkContains[$message;second-option]==true]
$addCmdReactions[2️⃣]
$endif

$if[$checkContains[$message;third-option]==true]
$addCmdReactions[3️⃣]
$endif

If we choose several options, several reactions will be added.

Usage

Editing a Select Menu

You can edit Select Menu, as well as options in this menu.

$editSelectMenu

Usage

$editSelectMenu[Menu ID;Min;Max;(Placeholder;Message ID)]

$editSelectMenuOption

Usage

$editSelectMenuOption[Menu option ID;Label;Value;Description;(Default;Emoji;Message ID)]

As you can notice, the arguments are exactly the same.

Example

Select Menu Code

$newSelectMenu[Example;1;1;Choose some option]
$addSelectMenuOption[Example;First;first-option;The first option]
$addSelectMenuOption[Example;Second;second-option;The second option]
$addSelectMenuOption[Example;Third;third-option;The third option]

Interaction Code

Example 1

$editSelectMenuOption[Example;First;first-option;The first option;no;1️⃣]
$editSelectMenuOption[Example;Second;second-option;The second option;no;2️⃣]
$editSelectMenuOption[Example;Third;third-option;The third option;no;3️⃣]

We just added emoji to our options after choosing (any) option.

Example 2

$editSelectMenu[Example;1;1;Choose some option 😀]
$addSelectMenuOption[Example;First;first-option;The first option]
$addSelectMenuOption[Example;Second;second-option;The second option]
$addSelectMenuOption[Example;Third;third-option;The third option]

We just changed the placeholder of our Select Menu after choosing (any) option.

Slash Commands

In this guide, you will learn more about implementing slash commands to your bot.

Slash commands are type of interactive application commands. It let’s users to interact with your bot by typing /<command name>.

General information

• Discord allows up to 200 slash commands (100 global & 100 guild based commands).

• To use slash commands, you need to invite the bot with applications.commands scope.

• Creating/modifying/deleting global slash commands might take up to 1 hour.

• Creating a guild slash command is instant but it won’t appear unless you have registered them in the current guild using $registerGuildCommands[(slash command name;...)] function.

  📝 Guild slash commands don’t appear in DMs unlike global slash commands.

Getting started

Before you start, you need 2.0.18 version of the app or later.

Inviting the bot

• Method #1

  • Visit Discord Developer official website and select your bot application.
  • Click hamburger icon ≡ on top-left of the website and choose OAuth2 tab.
  • In OAuth2 tab, click URL Generator sub-tab.
  • Choose bot & application.commands in scopes and desired bot permissions.
  • Copy the generated url below and invite your bot into your server.

• Method #2

  • Open BDFD app and select your bot.
  • Press Add invite bot to server button in dashboard tab.
  • Click Edit invite link scopes and enable “Slash commands” if its disabled.
  • Now, go back & press “Add your bot to your server”
  • Finally, invite the bot into your server.

Creating a slash command

• Create or modify an existing command.
• Click “Slash command trigger”.
• Choose “Enable global slash command” or “Enable guild slash command” as per your preference.
• Fill-up necessary data and save it.

📝 Slash commands can have a maximum of 4000 characters (combined name, description, and value properties) per slash.

Example

Slash options

Slash options are great way to get an user’s input in slash commands.

To create a slash option,

• Open your slash command edit trigger page.
• Click “Add” button in Options section.
• Fill-up necessary data and save the changes.

📝 Slash commands can have up to maximum 25 options per slash.

Slash options types

• Text - Accepts any string data input.
• Integer - Accepts only integer value input. For example: 3, -70 etc.
• Number - Accepts only number value input. For example: 5.3, -35, 23 etc.
• Boolean - Accepts either true or false input.
• User - It allows to mention any user.
• Channel - It allows to mention any channel.
• Role - It allows to mention any role.
• Mentionable - It allows to mention any user or role.
• Attachments - It allows to upload attachments.

Retrieving value from options

To retrieve a value from an option, use $message[<option name>].

📝 If you want this function to work both in normal and slash command,
then you can use $message[<arg number>;<option name>].

Example

Pre-defined choices

To create choices in options,

• In your slash command edit trigger page, create an option and fill-up the necessary data.
• Toggle “Enabled” in Predefined choices section.
• Then, click “Add a new choice” button.
• Type your choice name and value.
• Click “Add” and save the changes.

📝 A slash command can have upto maximum 25 choices per option.

Retrieving choices

You can retrieve user’s option choices using $if statements.

Format

$if[$message[<option name>]==<choice #1 value>]
      $c[Text/code here when user select 1st choice]
$elseif[$message[<option name>]==<choice #2 value>]
             $c[Text/code here when user select 2nd choice]
$endif

⚠️ Above code snippet requires BDScript 2 in order to execute since it contains $elseif.

Example

Auto Complete for Slash Command Options

Auto complete allows your bot to read user input as they type it and give user suggestions based on that.

Check example to get started quickly.

General Information

• You can only create up to 25 suggestions per option
• You need to enable autocomplete for the option
• You can’t use option choices with autocomplete

$onAutoComplete[Name] callback

This callback receives information about current user input. It’s used for adding suggestions.
Name is the name of a slash command.

Avaliable functions

$appendOptionSuggestion[Label;Value]

Used for adding new suggestions.

• Label - text which will be displayed in the suggestion list (for example: arg-ad from the previous example)
• Value - data that can be accessed in a slash command by using $message[] function. label is only a display name but value holds the actual value for a suggestion.

Note: value must have the same type as the currently typed option! Meaning, if the option’s type is Integer, value can’t be set to Hello but it can be set to 123

$autoCompleteOptionName

Returns the name of currently being typed option. For example arg from the previous example

$autoCompleteOptionValue

Returns the current user input. For example ad from the previous example

Example

New slash command with a new option:

Slash option:

Slash command code:

$message[arg]

$onAutoComplete[] callback:

Callback code

$nomention
$appendOptionSuggestion[$autoCompleteOptionName-$autoCompleteOptionValue;$autoCompleteOptionValue]

Explanation

• $appendOptionSuggestion[] - adds new suggestion
• $autoCompleteOptionName-$autoCompleteOptionValue - suggestion’s label. It’s set to the option name and user input (<option name>-<user input>)
• $autoCompleteOptionValue - suggestion’s value. It’s set to whatever user typed.

Result:

1.

2.

Awaited Commands

Awaited commands are a special type of command where the bot waits for the user’s response.

Content

Functions Used > Supported Filters > $awaitFunc[] > $awaitedCommand[] > $awaitedCommandError[] > Creating an awaited command

Functions Used

• $awaitFunc[]
• $awaitedCommand[]
• $awaitedCommandError[]

Supported Filters

• <numeric>: Accepts only number input.
• <word1/word2/...>: Accepts only specified words provided inside <>. Use / as a separator for multiple words.

$awaitFunc

Used to initiate an awaited command.

Syntax

$awaitFunc[Command name;(User ID;Channel ID)]

Parameters

• Command name (Type: String || Flag: Required): The name used inside $awaitedCommand[] and $awaitedCommandError[] callbacks.
• User ID (Type: Snowflake || Flag: Vacantable): The user the awaited command will trigger for. Uses command author, if User ID is not given.
• Channel ID (Type: Snowflake || Flag: Optional): The channel where the command will be awaited. Uses current channel, if Channel ID is not given.

Example

$nomention
What do you want me to say?
$awaitFunc[say]

$awaitedCommand

Triggered when an awaited command gets responded to.

$awaitedCommand[] is a callback, which means it’s used in the command trigger (not the code). The command is only run when an awaited command gets responded to.

Syntax

$awaitedCommand[Name;(Filter)]

Parameters

• Name (Type: String || Flag: Required): The name used in $awaitFunc[] function.
• Filter (Type: String || Flag: Emptiable): Used to limit user input (Supported filters). If no filter is provided, it accepts any input.

Example

Without filter

Trigger: $awaitedCommand[say;]

$nomention
$message

With choose filter

Trigger: $awaitedCommand[odd;<yes/no/cancel>]

$nomention
$if[$message==yes]
   Your answer is correct!
$elseif[$message==no]
   Your answer is incorrect!
$elseif[$message==cancel]
   Command cancelled!
$endif

With numeric filter

Trigger: $awaitedCommand[odd;<numeric>]

$nomention
You have provided a number: $message

$awaitedCommandError

Triggered when an awaited command doesn’t match with provided filter.

$awaitedCommandError[] is a callback, which means it’s used in the command trigger (not the code). The command is only run when an awaited command doesn’t match with provided filter.

Syntax

$awaitedCommandError[Name]

Parameters

• Name (Type: String || Flag: Required): The name used in $awaitFunc[] function.

Example

Trigger: $awaitedCommandError[number]

$nomention
Invalid number!

Creating an awaited command

Without filter

1. Create two commands with !say and $awaitedCommand[say;] triggers.
2. Paste the following code:

Code for the !say command:

$nomention
What do you want me to say?
$awaitFunc[say]

Code for the command with the $awaitedCommand[say;] trigger:

$nomention
$message

3. Execute command !say

With choose filter

1. Create two commands with !odd and $awaitedCommand[odd;<yes/no/cancel>] triggers.
2. Paste the following code:

Code for the !odd command:

$nomention
Is '19' an odd number?
$awaitFunc[odd]

Code for the command with the $awaitedCommand[odd;<yes/no/cancel>] trigger:

$nomention
$if[$message==yes]
   Your answer is correct!
$elseif[$message==no]
   Your answer is incorrect!
$elseif[$message==cancel]
   Command cancelled!
$endif

3. Execute command !odd

With numeric filter

1. Create two commands with !number and $awaitedCommand[number;<numeric>] triggers.
2. Paste the following code:

Code for the !number command:

$nomention
Provide a number!
$awaitFunc[number]

Code for the command with the $awaitedCommand[number;<numeric>] trigger:

$nomention
You have provided a number: $message

3. Execute command !number

HTTP Requests

• A HTTP request is an action to be performed on a resource identified by a URL.

Before reading this guide, please note that this feature is not intended for new BDFD users, as it is pretty advanced.

HTTP Request Types

This is a list of all HTTP request types available.

GET

• Retrieves data from a resource.

$httpGet[url]

POST

• The data sent to the server with POST is stored in the request body of the HTTP request.

$httpPost[url;(body)]

PUT

• The PUT method replaces all current representations of the target resource with the request payload.

$httpPut[url;(body)]

DELETE

• The DELETE method deletes the specified resource.

$httpDelete[url;(body)]

PATCH

• The PATCH method applies partial modifications to a resource.

$httpPatch[url;(body)]

HTTP Headers

• HTTP Headers is used to add more information. Most of the time, this is used to send an API Key to the API.

$httpAddHeader[header name;header value]

HTTP Statuses

• If the API doesn’t return anything after making a request, but you need to know the result, HTTP Statuses can help. You can read more about them here.

$httpStatus

HTTP Results

• To return the result of a HTTP method function, you can use $httpResult/$httpResult[].

Usage #1

$httpResult

Retrieves text value from HTTP request.

Usage #2

$httpResult[JSON Key;...]

Retrieves JSON from HTTP request. All arguments after JSON Key are optional.

Examples

Basic level

An example using a $httpGet function

$nomention
$httpGet[https://nekos.best/api/v2/neko]
$title[Here is a Neko for you!]
$description[**Source:** $httpResult[results;0;source_url]]
$image[$httpResult[results;0;url]]
$footer[nekos.best API]
$color[#e91e63]

{
    "results":[
        {
            "artist_href":"https://www.pixiv.net/en/users/4284365",
            "artist_name":"イカたると",
            "source_url":"https://www.pixiv.net/en/artworks/55142454",
            "url":"https://nekos.best/api/v2/neko/0023.png"
        }
    ]
}

API: nekos.best

Advanced level

An example using a function that has a request body (e.g. $httpPost) and using $httpAddHeader

$httpAddHeader[content-type;application/x-www-form-urlencoded]
$httpPost[https://pastebin.com/api/api_post.php;api_dev_key=7CP52G-BTQP_1AhyBBlTa94qyjE6vHzU&api_paste_code=$url[encode;$message]&api_option=paste]
$httpResult

API: pastebin.com

If Statements

In this section, you’ll learn how to use the if statement.

Content

Functions Used > Signs > $if[] > $endif[] > $else > $elseif[] > $and[] > $or[] > Simple Example

Functions Used

• $if[]
• $endif
• $else
• $elseif[]

Support Functions Used

• $and[]
• $or[]

Signs

== - Equal

!= - Not equal

< - Less than

> - Greater than

>= - Greater than or equal to

<= - Less than or equal to

• These signs could vary in meaning based on the order or intent of the if statement.
• If you are using text as your x and/or y, you can not use any other signs besides == and !=. However for numbers, you can use any sign shown in the above list.

$if

Executes the following block of code if the provided condition is true.

Syntax

$if[Condition]

$if[] uses the format of: if x is related accordingly (based on the “sign”) with y then the code below runs.

Parameters

• Condition (Type: String || Flag: Required): Check that will be carried out. Use Signs.

Example

$nomention
$if[5>$random[0;10]]
  5 is bigger than $random[0;10]
$endif

$endif

Ends an if statement.

Syntax

$endif

Example

$nomention
$if[$message==abc]
  Good work!
$endif

With $endif

Without $endif

$else

A block of code to be executed, if the $if[] condition is false.

Syntax

$else

Example

$if[5>$random[0;10]]
  5 is bigger than $random[0;10]
$else
  5 is less than $random[0;10]
$endif

$elseif

Checks provided condition only if previous $if[] or $elseif[] conditions returned false. If the provided condition is true, the following block of code will be executed.

You can use multiple $elseifs. Only for BDScript 2!

Syntax

$elseif[Condition]

Parameters

• Condition (Type: String || Flag: Required): Check that will be carried out. Use Signs.

Example

BDScript 2:

$nomention
$if[5<$random[0;10]]
  5 is less than $random[0;10]
$elseif[5==$random[0;10]]
  5 equals $random[0;10]
$endif

BDScrpt and BDScript Unstable:

$nomention
$if[5<$random[0;10]]
  5 is less than $random[0;10]
$else
  $if[5==$random[0;10]]
    5 equals $random[0;10]
  $endif
$endif

$and

Returns true if every provided condition is true, otherwise false is returned.

Syntax

$and[Conditions;...]

Parameters

• Conditions (Type: String || Flag: Required): Checks that will be carried out. All conditions must be true for this function to return true. Separate conditions using ;. Use Signs.

Example

$nomention
$if[$and[$nickname==MineBartekSA;$message==Update]==true]
  Hi developer
$else
  Hi user
$endif

$or

Returns true if at least one of the provided conditions is true, otherwise false is returned.

Syntax

$or[Conditions;...]

Parameters

• Conditions (Type: String || Flag: Required): The condition to check. Separate conditions using ;. Use Signs.

Example

$nomention
$if[$or[$nickname==MineBartekSA;$message==Update]==true]
  Hi
$else
  Bye
$endif

Simple Example

1. Create command with !example trigger.

2. Paste the following code:

   $nomention
   $if[$message==BDFD]
     Hi BDFD User!
   $elseif[$message==Bartek]
     Are you Bartek?
   $elseif[$message==Premium]
     Do you want to get premium?
   $else
     I can't find this:(
   $endif
   

3. Execute command !example

JSON Functions

Before you read this guide, you should be familiar with what JSON is and where and how it’s being used.
You can familiarize yourself with JSON by reading a tutorial on W3Schools.

This guide will utilize Character Escaping and the $optOff function.

$jsonParse

$jsonParse is the primary function used when working with JSON data.
This function parses a JSON string into an object which can then be used by other JSON functions.

Syntax

$jsonParse[JSON string]

Parameters

• JSON string (Type: String || Flag: Required): The JSON string to parse into an object.

Examples

See examples further down the guide.

$json

$json function retrieves JSON values from a specified key in the current JSON object.

The $json function will return an empty string if the value is null, the key doesn’t exist, no $jsonParse or $jsonSet function was executed, or $jsonClear was executed.

Syntax

$json[Key;...]

Parameters

• Key (Type: String || Flag: Required): The JSON key which will be retrieved.

Examples

Without Arrays

$nomention
$jsonParse[{
    "username": "NightNutSky",
    "tag": "6700",
    "identity": {
        "age": 16
    }
}]

Username: $json[username]
Tag: $json[tag]
Age: $json[identity;age] years old

With Arrays

$nomention
$jsonParse[{
    "computer": [{
        "apps": {
            "software": ["BlueStacks", "Krita", "Visual Studio Code"\],
            "games": ["GTA 5", "RDR 2", "CS:GO", "Cyberpunk 2077"\]
        }
    },{
        "cpu": "Intel",
        "gpu": "NVIDIA",
        "ram": "XPG"
    }\]
}]

Software: $json[computer;0;apps;software]
Games: $json[computer;0;apps;games]
Brands: CPU - $json[computer;1;cpu], GPU - $json[computer;1;gpu], RAM - $json[computer;1;ram]

$jsonSet

$jsonSet sets or replaces the value at the specified JSON key.

Syntax

$jsonSet[Key;...;Value]

Parameters

• Key (Type: String || Flag: Required): The JSON key where the value will be set or replaced.
• Value (Type: Integer, Bool, Float, String || Flag: Required): The value to set or replace with.

Example

$nomention
$jsonParse[{
    "username": "NightNutSky",
    "tag": "6700",
    "identity": {
        "age": 16
    }
}]

Username: $json[username]
Tag: $json[tag]
Age: $json[identity;age] years old

$jsonSet[username;Priyanuj]
$jsonSet[tag;2626]
$jsonSet[identity;age;19]

$optOff[Username: $json[username]
Tag: $json[tag]
Age: $json[identity;age] years old]

$jsonSetString

$jsonSetString function sets or replaces the value at the specified JSON key. Always sets the value as a string.

Syntax

$jsonSetString[Key;...;Value]

Parameters

• Key (Type: String || Flag: Required): The JSON key where the value will be set or replaced.
• Value (Type: String || Flag: Required): The value to set or replace with.

This function is recommended to be used mostly in economic-related commands. Why? The next example will explain it.

Example

• $jsonSet

  $nomention
  $jsonParse[{}]
  
  $jsonSet[balance;$message]
  
  Balance key was set to: $json[balance]
  

  

• $jsonSetString

  $nomention
  $jsonParse[{}]
  
  $jsonSetString[balance;$message]
  
  Balance key was set to: $json[balance]
  

  

If we set this value as a number manually, we’ll encounter issues.

$nomention
$jsonParse[{
    "balance": 788895455566645444567
}]

Balance key: $json[balance]

$nomention
$jsonParse[{
    "balance": "788895455566645444567"
}]

Balance key: $json[balance]

Therefore, we should set big numbers as strings.

$jsonUnset

$jsonUnset removes the value at the specified JSON key.
In short, the opposite of the $jsonSet function.

Syntax

$jsonUnset[Key;...]

Parameters

• Key (Type: String || Flag: Required): The JSON key which will be unset.

Example

$nomention
$jsonParse[{
    "username": "NightNutSky",
    "tag": "6700",
    "identity": {
        "age": 16
    }
}]

Username: $json[username]
Tag: $json[tag]
Age: $json[identity;age] years old

$jsonUnset[username]
$jsonUnset[tag]
$jsonUnset[identity;age]

$optOff[Username: $json[username]
Tag: $json[tag]
Age: $json[identity;age] years old]

$jsonClear

$jsonClear clears out the current JSON object.

Syntax

$jsonClear

Example

$nomention
$jsonParse[{
    "username": "NightNutSky",
    "tag": "6700",
    "identity": {
        "age": 16
    }
}]

Username: $json[username]
$jsonClear
Username: $optOff[$json[username]]

$jsonExists

$jsonExists checks if the specified JSON key exists in the current JSON object.

Returns an empty result if no $jsonParse or $jsonSet function was executed, or $jsonClear was executed.

Syntax

$jsonExists[Key;...]

Parameters

• Key (Type: String || Flag: Required): The JSON key which will be checked.

Examples

See examples further down the guide.

$jsonStringify

$jsonStringify turns the current JSON object into a string value.

The $jsonStringify function will return an empty string if no $jsonParse or $jsonSet function was executed, or $jsonClear was executed.

Syntax

$jsonStringify

Example

$nomention
$jsonParse[{
    "computer": [{
        "apps": {
            "software": ["BlueStacks", "Krita", "Visual Studio Code"\],
            "games": ["GTA 5", "RDR 2", "CS:GO", "Cyberpunk 2077"\]
        }
    },{
        "cpu": "Intel",
        "gpu": "NVIDIA",
        "ram": "XPG"
    }\]
}]

$jsonStringify

$jsonPretty

$jsonPretty turns the current JSON object into a pretty string value.

The $jsonPretty function will return an empty result if no $jsonParse or $jsonSet function was executed, or $jsonClear was executed.

Syntax

$jsonPretty[Indent length]

Parameters

• Indent length (Type: Integer || Flag: Required): The length of the indentation. Usually it’s 2 or 4.

Example

$nomention
$disableInnerSpaceRemoval
$jsonParse[{"computer":[{"apps":{"software":["BlueStacks","Krita","Visual Studio Code"\],"games":["GTA 5","RDR 2","CS:GO","Cyberpunk 2077"\]}},{"cpu":"Intel","gpu":"NVIDIA","ram":"XPG"}\]
}]

$jsonPretty[4]

For the output to really be pretty, we have to use the $disableInnerSpaceRemoval function.

$jsonArray

$jsonArray marks a specified JSON key as an array.

Syntax

$jsonArray[Key;...]

Parameters

• Key (Type: String || Flag: Required): The JSON key which will be marked as an array.

Example

$nomention
$jsonParse[{
    "games": ""
}]

Non-array `games` key:
$jsonPretty[4]

$jsonArray[games]

Array `games` key:
$optOff[$jsonPretty[4]]

$jsonArrayCount

$jsonArrayCount counts the elements in the specified JSON key.

Syntax

$jsonArrayCount[Key;...]

Parameters

• Key (Type: String || Flag: Required): The JSON key where the elements will be counted.

Example

$nomention
$jsonParse[{
    "computer": [{
        "apps": {
            "software": ["BlueStacks", "Krita", "Visual Studio Code"\],
            "games": ["GTA 5", "RDR 2", "CS:GO", "Cyberpunk 2077"\]
        }
    },{
        "cpu": "Intel",
        "gpu": "NVIDIA",
        "ram": "XPG"
    }\]
}]

$onlyIf[$jsonExists[computer;0;apps;$message]==true;The specified category doesn't exist! Available categories are `software` and `games`]
The count of the `$message` apps is $jsonArrayCount[computer;0;apps;$message]. 

$jsonArrayIndex

$jsonArrayIndex gets the array index of a given value.

The $jsonArrayIndex function will return -1 if value not found and will return an empty result if no $jsonParse or $jsonSet function was executed, or $jsonClear was executed.

Syntax

$jsonArrayIndex[Key;...;Value]

Parameters

• Key (Type: String || Flag: Required): The JSON key where the value will be searched for.
• Value (Type: String, Integer, Float || Flag: Required): The value to search for.

Example

$nomention
$jsonParse[{
    "computer": [{
        "apps": {
            "software": ["BlueStacks", "Krita", "Visual Studio Code"\],
            "games": ["GTA 5", "RDR 2", "CS:GO", "Cyberpunk 2077"\]
        }
    },{
        "cpu": "Intel",
        "gpu": "NVIDIA",
        "ram": "XPG"
    }\]
}]

The $message's index in `apps/software` is $jsonArrayIndex[computer;0;apps;software;$message].

$jsonArrayAppend

$jsonArrayAppend appends the value at the end of the specified JSON key.

Syntax

$jsonArrayAppend[Key;...;Value]

Parameters

• Key (Type: String || Flag: Required): The JSON key where the value will be appended.
• Value (Type: Integer, Bool, Float, String || Flag: Required) : The value to append.

Example

$nomention
$jsonParse[{
    "computer": [{
        "apps": {
            "software": ["BlueStacks", "Krita", "Visual Studio Code"\],
            "games": ["GTA 5", "RDR 2", "CS:GO", "Cyberpunk 2077"\]
        }
    },{
        "cpu": "Intel",
        "gpu": "NVIDIA",
        "ram": "XPG"
    }\]
}]

$onlyIf[$jsonExists[computer;0;apps;$message[1]]==true;The specified category doesn't exist! Available categories are `software` and `games`]

$var[value;$replaceText[$message;$message[1] ;]]

$jsonArrayAppend[computer;0;apps;$message[1];$var[value]]

A new app was added to the `$message[1]` category!
Current apps in the `$message[1]` category: $json[computer;0;apps;$message[1]]

$jsonArrayPop

$jsonArrayPop function removes the last element of an array and returns the removed element.

Syntax

$jsonArrayPop[Key;...]

Parameters

• Key (Type: String || Flag: Required): The key of the array from which an element will be removed.

Example

$nomention
$jsonParse[{
    "music": ["Paranoid - MADKID", "Ping! 2 - Exyl", "Tokyo - Leat'eq"\]
}]

Removed: $jsonArrayPop[music]

Current music:
> $jsonJoinArray[music;, ]

$jsonArrayShift

$jsonArrayShift function removes the first element of an array and returns the removed element.

Syntax

$jsonArrayShift[Key;...]

Parameters

• Key (Type: String || Flag: Required): The key of the array from which an element will be removed.

Example

$nomention
$jsonParse[{
    "music": ["Paranoid - MADKID", "Ping! 2 - Exyl", "Tokyo - Leat'eq"\]
}]

Removed: $jsonArrayShift[music]

Current music:
> $jsonJoinArray[music;, ]

$jsonArrayUnshift

$jsonArrayUnshift function adds the value in the front of the array.

Syntax

$jsonArrayUnshift[Key;...;Value]

Parameters

• Key (Type: String || Flag: Required): The JSON key of the array to which the value will be added.
• Value (Type: Float, String, Bool, Integer || Flag: Required): The value to be added.

Example

$nomention
$jsonParse[{
    "music": ["Paranoid - MADKID", "Ping! 2 - Exyl", "Tokyo - Leat'eq"\]
}]

$jsonArrayUnshift[music;Side Character - Cloudfodder]

Music:
> $jsonJoinArray[music;, ]

$jsonArraySort

$jsonArraySort sorts a specific JSON array in ascending order.

The function sorts the elements in the order of integers from lowest to highest, and then strings based on their ASCII/Unicode values.

Syntax

$jsonArraySort[Key;...]

Parameters

• Key (Type: String || Flag: Emptiable): The key of the JSON array to be sorted.

Example

$nomention
$jsonParse[{
  "data": ["Oranges", "banana", 10, "apple", "Apples", 2, 30\]
}]

$jsonArraySort[data]

After sorting:
> $json[data]

$jsonArrayReverse

$jsonArrayReverse reverses the order of a specific JSON array.

Syntax

$jsonArrayReverse[key;...]

Parameters

• Key (Type: String || Flag: Emptiable): The key of the JSON array to be reversed.

Example

$nomention
$jsonParse[{
  "fruits": ["apple", "orange", "banana", "grape"\]
}]

$jsonArrayReverse[fruits]

After reversing:
> $json[fruits]

$jsonJoinArray

$jsonJoinArray function joins a JSON array under the specified key with the given separator.

The $jsonJoinArray function will return an empty string if the value is null, the key doesn’t exist, no $jsonParse or $jsonSet function was executed, or $jsonClear was executed.

Syntax

$jsonJoinArray[Key;...;Separator]

Parameters

• Key (Type: String || Flag: Required): The JSON key to an array which will be retrieved.
• Separator (Type: String || Flag: Required): The separator which will separate the JSON keys.

Example

$nomention
$jsonParse[{
    "music": ["Paranoid - MADKID", "Ping! 2 - Exyl", "Tokyo - Leat'eq"\]
}]

Music:
> $jsonJoinArray[music;, ]

We separated the list with , .

Threads

In this section, you’ll learn how to integrate threads in your bot.

Make sure your bot has SEND_MESSAGES_IN_THREADS permission.

Content

Functions Used > Archive Duration > $startThread[] > $editThread[] > $threadAddMember[] > $threadRemoveMember[] > Simple Code

Functions Used

• $startThread[]
• $editThread[]
• $threadAddMember
• $threadRemoveMember[]

Archive Duration

60 - 1 Hour
1440 - 1 Day
4320 - 3 Days (Only for servers with level 1 boosted)
10080 - 7 Days (Only for servers with level 2 boosted)

$startThread

Creates a new thread in the provided channel.

Syntax

$startThread[Thread name;Channel ID;Message ID;(Archive duration;Return thread ID?)]

Required permissions that the bot must have for this function to work properly:

• createpublicthreads

Parameters

• Thread name (Type: String || Flag: Required): The name of the newly created thread.
• Channel ID (Type: Snowflake || Flag: Required): The channel where the thread will be created.
• Message ID (Type: Snowflake || Flag: Emptiable): The message from which the thread will be created. Can be left empty.
• Archive duration (Type: Integer || Flag: Optional): The archive duration after which the thread will be auto-archived due to inactivity. Defaults to 60.
• Return thread ID? (Type: Bool || Flag: Optional): Whether to return the thread channel ID or not. Defaults to no.

Example

$nomention
I created a new thread! <#$startThread[Cool Thread;$channelID;;1440;yes]>

$editThread

Modifies an existing thread.

Syntax

$editThread[Thread ID;(Thread name;Archived?;Archive duration;Locked?;Slowmode)]

Parameters

• Thread ID (Type: Snowflake || Flag: Required): The thread channel to edit.
• Thread name (Type: String || Flag: Optional): The new name of the thread.
• Archived? (Type: Bool || Flag: Optional): Whether to archive this thread or not.
• Archive duration (Type: Integer || Flag: Optional): The archive duration after which the thread will be auto-archived due to inactivity. Defaults to 60.
• Locked? (Type: Bool || Flag: Optional): Whether to lock this thread or not. Note that archived threads can’t be locked.
• Slowmode (Type: Integer || Flag: Optional): The slowmode of this channel, expressed in seconds.

Use !unchanged as an argument for the option to remain in its current state.

Example

$nomention
$editThread[1098166444111433819;Cool Thread 😎;no;!unchanged;!unchanged;5]

$threadAddMember

Adds a user to a thread.

Syntax

$threadAddMember[Thread ID;User ID]

Parameters

• Thread ID (Type: Snowflake || Flag: Required): The ID of the thread channel to add the user to.
• User ID (Type: Snowflake || Flag: Required): The user to add to the thread.

Example

$nomention
$threadAddMember[1021054508975009793;$authorID]

• In the thread:

$threadRemoveMember

Removes a user from a thread.

Syntax

$threadRemoveMember[Thread ID;User ID]

Parameters

• Thread ID (Type: Snowflake || Flag: Required): The ID of the thread channel to remove the user from.
• User ID (Type: Snowflake || Flag: Required): The user to remove from the thread.

Example

• In the thread:

Simple Code

$nomention
$var[id;$startThread[Cool Thread;$channelID;;1440;yes]]
New thread - <#$var[id]>
$threadAddMember[$var[id];$authorID]

• In the thread:

If you want to learn more about threads, read Discord’s support article.

Text Splitting

In this section, you’ll learn how to use the text splitting.

Content

Functions Used > $textSplit[] > $splitText[] > $getTextSplitLength > $getTextSplitIndex[] > $joinSplitText[] > $removeSplitTextElement[] > Simple Code

Functions Used

• $textSplit[]
• $splitText[]
• $getTextSplitLength
• $getTextSplitIndex[]
• $joinSplitText[]
• $removeSplitTextElement[]
• $editSplitText[]

$textSplit

Splits the provided text by a given separator and saves the value temporarily.

Syntax

$textSplit[Text;Separator]

Parameters

• Text (Type: String || Flag: Emptiable): The text to split.
• Separator (Type: String || Flag: Emptiable): The separator to split the text with. If this parameter is empty, it separates the text by each character.

Example

$nomention
$textSplit[hello-world-!;-]
> $splitText[2]

$splitText

Each separated text has a number, i.e. an index. $splitText is a function that returns one of the elements of the separated text by an index or the sign < - the very first element, or > - the very last element.

Syntax

$splitText[Index]

Parameters

• Index (Type: HowMany || Flag: Required): The split value to get (e.g. 2 for the second split). You can also use > to return the last split value i.e $splitText[>].

Example

$nomention
$textSplit[hello world !; ]
> $splitText[<]
> $splitText[2]
> $splitText[>]

$getTextSplitLength

Returns the number of splits.

Syntax

$getTextSplitLength

Example

$nomention
$textSplit[hello%world%!;%]
> $getTextSplitLength

$getTextSplitIndex

Retrieves index from the provided value. Returns -1 if it couldn’t find the value.

Syntax

$getTextSplitIndex[Value]

Parameters

• Value (Type: String || Flag: Emptiable): The value to search in the text split.

Example

$nomention
$textSplit[hello_world_!;_]
> $getTextSplitIndex[$message]

$joinSplitText

This function returns the current elements of the separated text with the specified (sometimes new) separator.

Syntax

$joinSplitText[Separator]

Parameters

• Separator (Type: String || Flag: Emptiable): The separator to be put between the text split values.

Example

$nomention
$textSplit[hello#world#!;#]
> $joinSplitText[
> ]

$removeSplitTextElement

This function removes an element from the separated text by the specified index.

Syntax

$removeSplitTextElement[Index]

Parameters

• Index (Type: Integer || Flag: Required): The index of the $textSplit[] value to remove.

Example

$nomention
$textSplit[hello-world-!;-]
$removeSplitTextElement[3]
> $joinSplitText[-]

$editSplitText

This function replaces the element at the specified index with a new element instead of the previous one.

Syntax

$editSplitText[Index;Value]

Parameters

• Index (Type: Integer || Flag: Required): The index of the element to edit.
• Value (Type: String || Flag: Required): The new value to assign to the provided index.

Example

$nomention
$textSplit[hello-world-!;-]
$editSplitText[2;bdfd]
> $joinSplitText[-]

Simple Code

$nomention
$textSplit[$message;]
Characters: $getTextSplitLength
$textSplit[$message; ]
Words: $getTextSplitLength
Random word: $splitText[$random[1;$sum[$getTextSplitLength;1]]]
First word: $splitText[<]

Webhooks

This wiki explains how to create and use webhooks in BDFD.

Creating A Webhook

$webhookCreate[channelID;username;avatarURL (can be left empty)]

Creates a webhook in the provided ‘channelID’, with the inputted ‘username’ and ‘avatarURL’ assets. This function returns the URL of the newly created webhook (webhook URLs should be kept private, treat them like a password).

Note: Only ten webhooks can be created per channel.

Editing A Webhook

$webhookAvatarURL[webhookURL;avatarURL]

Changes the provided webhook’s avatar.

$webhookUsername[webhookURL;username]

Changes the provided webhook’s username.

Webhook Messages

You can send messages via a webhook using the following functions:

• $webhookTitle[webhookURL;text] - Adds a title to the webhook embed.
• $webhookDescription[webhookURL;text] - Adds a description to the webhook embed.
• $webhookFooter[webhookURL;text] - Adds a footer to the webhook embed.
• $webhookContent[webhookURL;text] - The webhook non-embedded message content.
• $webhookColor[webhookURL;colorHex] - The color of the webhook embed.

Alternatively, you can use $webhookSend[] for more options and condensement:

$webhookSend[webhookURL;content;title;titleURL;description;color;author;authorIcon;footer;footerIcon;thumbnail;image;addTimestamp (yes/no)]

Note: Unneeded fields can be left empty.

Deleting A Webhook

$webhookDelete[webhookURL]

Deletes the provided webhook.

Example

$nomention
$var[webhookURL;$webhookCreate[$channelID;Cool Webhook;]]
$webhookContent[$var[webhookURL];Hello World!]
$c[❗️This example requires BDScript 2 enabled❗️]

Explaination:

This code is storing the newly created webhook URL returned from $webhookCreate[] (using $var[]). Then, in the rest of the code $var[webhookURL] was called to get the webhook URL, which allowed the webhook message to send using $webhookContent[].

🧙‍♂️ Remember, you need to be in BDScript 2 mode to use $var[]!

Output:

Argument Flags

Function argument flags mark how arguments within a function may be used (or hence, not used at all), it will be displayed near or below the function argument. Example: (- userID (Flag: Required)) etc.

• Optional - The argument can be excluded but cannot be left empty, they show up as (something) and will always be after all required arguments.
• Required - The argument must be included and cannot be empty.
• Emptiable - The argument must be included but can be empty.
• Vacantable - The argument can be excluded and if included can be empty.

Argument Types

This section will explain the various argument types used for function arguments. Function arguments are anything that goes in the brackets [] of a function, it will be displayed near or below the function argument. Example: (- userID (Type: Snowflake || Flag: Required)) and if it has more than one option it will be (Type: String, Snowflake || Flag: Required) etc.

• String - This is the most generalized function, a string can be any character or text.
• Snowflake - A valid discord ID, can be of a role, channel, user, server, emoji and message.
• Integer - Any number without decimal (-5, -1, 1, 5 10, etc).
• Float - A number with decimal (-2.5, -0.5, 1.5, 5.2, 7.30, etc).
• URL - A valid domain link, must be prefixed by http:// or https:// and have a valid domain name.
• HowMany - A number that is prefixed or suffixed with < or >, or just a plain integer.
• Enum - Strings that match a certain key value (case insensitive).
• Emoji - Emoji as 🌹 or emoji aliases in form of :+1: for :+1: or the discord custom emojis in form of <a:emoji_name:emoji-id> for gif emojis and <:emoji_name:emoji-id> for non-gif emojis, for how to get that, check $addReactions as it has explanations for that. Characters <> can be omitted from the discord custom emoji form.
• Duration - A time based duration, an integer suffixed with a valid time format (s, m, h, d, w).
• Permission - Discord permission (case insensitive), see this for all valid permissions.
• Bool - yes/no or true/false.
• Color - Color Hex Code you can get from here as an example

Pairs

• Tuple - A tuple is a set of arguments that depend on others to function, they are shown with <> on either side.
• Ellipsis - Ellipsis notations (...) symbolize an argument that can be repeated multiple times. Ellipsis is denoted with ... as the argument after the argument which can be repeated.

Character Escaping

(for advanced users)

What are Escape Characters?

Escape characters are used to indicate that the character should not be interpreted as a modification of the code, rather just text that appears in the code or bot’s response. Basically, escape characters let your bot return the function-triggering characters (e.g ;, $, [, ]) without any changes to the code.

Escapable Characters

Example

$nomention
$sendMessage[[ Hi, this is pretty cool\; right? \]]

Hyperlinks

A hyperlink is clickable-text. When the user clicks on the text, it directs them to a certain URL.

General Hyperlinks

You can use hyperlinks inside $description[], $addField[], webhook content/description, slash command response content, and ephemeral $onInteraction response content.

Syntax

[text\](link)

Note: This is the syntax for BDScript 2 and BDScript Unstable. For the BDScript, the syntax is [text](link).

Note: In the case of using hyperlinks inside slash command response content or ephemeral $onInteraction response content, the syntax for BDScript should be used. Does not apply to hyperlinks that are inside functions that support hyperlinks.

Example

$nomention
$description[This bot is made with [Bot Designer For Discord\](https://botdesignerdiscord.com)]

Title Hyperlinks

Use the $embeddedURL function to add a hyperlink in $title.

Author Hyperlinks

Use the $authorURL function to add a hyperlink in $author.

Share code

“Share code” is a feature that lets users share a copy of their entire bot.

Creating a Share code

Here is how you can create a share code of your bot:

• Select your bot in BDFD app homepage.
• Head over to “Bot Settings” tab.
• In “Share code” section, click “Create a share code” button.
• Then, click “Generate share code” button and copy the code.

Now, you can give the code to your friend or someone other, and they will be able to create a carbon copy of your bot.

⚠️ Once a share code has been used, it expires after a month.

Resources

This section of the wiki contains useful information that will allow you to expand your knowledge.

API

Public Bot Designer for Discord API

Endpoints

The base URL is https://botdesignerdiscord.com/public/api

GET /function_list

Returns an array of functions

GET /function_tag_list

Returns an array of function tags

GET /function/:function

• :function - function tag
  Returns a function

GET /emoji_alias_list

Returns a map, mapping emoji to a list of its aliases

Data Structures

• Can be empty means the field can be set to a default value.
• Can be omitted means the field might not be included in the response.

Function

Argument

Argument Types

Multiple types can be merged together with | (OR).
Possible argument types:

• String
• Integer
• Float
• Snowflake
• Bool
• Color
• Permission
• Duration
• HowMany (>, 2, <, etc)
• URL
• Enum
• Tuple

BDFD’s Creation

How Bot Designer For Discord became what it is today.

Who Develops BDFD?

The Company

NilPointer Software is the company that made Bot Designer For Discord. NilPointer Software, a start-up focused on providing fast and quality software.

BDFD’s Beginning and Growth

Kubastick was inspired by one of his friends to create the application. One day, his friend stated, “It would be nice if there’d be an app for creating bots”. Kubastick having previous programming knowledge, took this idea and ran with it.

By early 2019, the premature version of BDFD was created. Later on, Kubastick acquired two developers, MineBartekSA and noituri. This is when the app’s functions and UI got majorly improved.

BDFD was slowly growing, until Discord’s explosion during the COVID-19 pandemic, which caused a uproar of users coming to BDFD to create their very own bots… and the rest is history… The growth of BDFD isn’t stopping though, as the developers are actively integrating new features; and the community is growing larger by the day.

Have more questions? Ask in our community server.

Discord’s ID System

Discord’s ID System allows bot’s to manage and use IDs to get/edit object data (e.g. returning user’s name, deleting a role etc).

What’s an ID?

An ID is a Discord object identifier. Let’s break this down:

• An ‘object’ refers to a Discord channel, role, user, server/guild, etc.
• An ‘identifier’ (typically called ‘ID’) refers to the multi-digit number that the object belongs to.

Enabling Developer Mode

In order to access and copy IDs in the Discord client, you must enable developer mode. Here’s how:

• Desktop

  

  

  

• Mobile

  Go to User Settings > Appearance > Advanced and turn on Developer Mode.

  

Finding IDs

Where do I find these ‘IDs’?

You can use ‘Functions That Return IDs’ to retrieve IDs.

If you want to get IDs using your client, check out Discord’s full guide on getting IDs!

Using IDs in Commands

There are a lot of functions that use IDs. Like, $deleteChannels, $modifyRole $banID, and many more.

Let’s use $deleteChannels for this example. In order to delete a channel, we need the channel’s ID. Here’s how $deleteChannels could look:

$deleteChannels[320949943877437847]
$c[Deletes the provided custom channel ID.]

$deleteChannels[$channelID]
$c[Deletes the channel where the command was ran.]

$deleteChannels[$mentionedChannels[1]]
$c[Deletes the mentioned channel.]

⚠️ Be careful not to mix up ID types. For example, you can’t do $deleteChannels[$authorID]. This is because $authorID returns a user ID, not a channel ID.

Functions That Return IDs

• $authorID/$userID/$roleID/$channelID
• $findUser/$findChannel/$findRole
• $mentioned/$mentionedChannels/$mentionedRoles
• … (a few others)

Using IDs For Mentions

• Mentioning an User - <@userID>
• Mentioning a Role - <@&roleID>
• Mentioning a Channel - <#channelID>
• Using an Emoji
  • Static - <:emojiName:emojiID>
  • Animated - <a:emojiName:emojiID>
• Mentioning a Slash
  • Normal - </name:commandID>
  • Subcommand - </name subcommandName:commandID>
  • Subcommand group - </name subcommandGroup subcommandName:commandID>
• Mentioning a Guild - Guilds can’t be mentioned.

📝 Non-bots can use IDs to mention objects too!

Discord Timestamps

Discord timestamps are used to provide time in multiple formats. The information is given according to the user’s timezone and locale. Discord timestamps are built with the Unix Time system, meaning that they are dynamic. These can be used by anyone; This includes users, webhooks, and applications.

Syntax

Timestamp syntax: <t:unixTime:Style>

Styles

Here’s a list of all supported time format styles.

📌 The default style is f, if no style provided.

Usability

Functions which return UNIX timestamp:

• $getTimestamp
• $hostingExpireTime
• $premiumExpireTime

Example

$nomention
<t:$getTimestamp:D>

Embed Indexes

If you look around BDFD embed functions (eg. $title, $footer, $addTimestamp etc.). You’ll see an argument called index. This argument is used to create multi-embeds.

📝 Discord supports creating upto a maximum of 10 embeds per bot message.

Creating Multi-Embeds

By default, the index is set to 1 (the first embed). To create a second embed, you have to write 2 in index argument and so on. You can specify any number between 1 to 10 in index argument.

📝 Total character length of the overall response should not exceed more than 6,000. If it does, the bot won’t send the message.

Example

$nomention

$title[Title #1]
$description[Description #1]

$title[Title #2;2]
$description[Description #2;2]

$title[Title #3;3]
$description[Description #3;3]

2FA and Elevated Permissions

If a guild owner enables the server’s “Two-factor authentication for moderation” setting, everyone executing a certain segment of actions will need to have two-factor authentication (2FA) enabled on their account. Since, bots do not have 2FA themselves, you as the bot owner, will need to enable it on your account.

The permissions assigned to these actions are referred to as “Elevated permissions”. Elevated permissions include but may not limited to :

• admin
• ban
• kick
• managechannels
• manageemojis
• managemessages
• manageroles
• manageserver
• managethreads
• managewebhooks

📝 More info about enabling 2FA can be found in Discord’s support article.

Permissions

Permissions allow users to have specific privileges and access in the server. Some permissions can be as basic as allowing users the ability to add reactions to messages while other permissions grant users more administrative actions. These permissions are based on the roles assigned to users in a server and permissions can be assigned per role on both the server level and channel level.

List of Permissions

Following is the list of permissions which are supported in BDFD -

📝 All permissions are case insensitive (i.e both BAN and Ban will work).

Security

Security is an important topic to discuss. If security measures are disregarded, your bot and/or account could be at risk of being hacked.

This article will share tips about how you can keep your bot and account safe.

Sharing Tokens and Passwords

Do not share token(s) with anyone. This includes both bot and regular user account tokens. Sharing your bot token with someone (or posting it publicly) will grant them full access to edit your bot. While sharing your user account token with someone (or posting it publicly) will allow them to have full access to your account (even if they don’t have your password or email). Once someone has your account or bot’s token, there is a high chance of it being used for malicious purposes. For example, stealing personal info, spreading scams, modifying your bot to nuke/raid servers, etc.

In the event, that your bot’s token is shared, the only thing you can do to secure it is to regenerate the bot’s token. But by then, the damage has most likely been done. In the case of a user account token, if you still have access to your account, regenerate your token by changing your password. If you cannot or don’t have access to it anymore, you will need to contact Discord support for an optimal solution.

Passwords, like tokens, should not be shared. If, however, you accidentally share your account password, you should change it as soon as possible.

📌 If your account is hacked, you should contact Discord for further assistance.

Account 2FA

Bot owners should consider enabling two-factor authentication on their accounts. Learn more about 2FA and why it’s essential for bot owners.

Sessions

Discord recently added the ability to see all your current sessions and their respective locations.

If you see a device or location that you haven’t authorised, you can log out of that particular device by pressing the ‘X’ button or all known devices by clicking the button at the bottom of the page. This will log out those sessions, invalidating the tokens. 

Avoid Scams and Untrusted Links/Files

Scam (or “phishing”) links put user’s accounts, personal information, and IP addresses in the hands of scammers and hackers. There’s some good news, these scams are preventable! This section will discuss how to protect yourself and your friends from harmful scams.

Link Diagnosis

• Trusted Links are links that can be trusted to visit.
• Untrusted Links are links that should be avoided.

This sub-section will breakdown how you can identify between a trusted link and an untrusted link.

1. Does the link have a weird spelling?

   If a link looks shortened or altered, that usually means it’s an untrusted link. For example, discord.com is the official Discord site; while something like dlscird.com is not.

2. Is it out of context?

   If a user sends you a link that is out of context of your previous discussions (or if you’ve never talked to them) then you can bet on it being untrustworthy.

3. Was the link sent by a friend?

   At first glimpse, you’d assume this makes the link more trustworthy. But, it could be that their account has been compromised, so you should still be careful when clicking links from friends.

4. Too good to be true?

   Free Nitro scams are extremely common. If you get a DM from a random user/bot telling you that you won something or can earn Nitro, just disregard it.

5. Asking for your password/user token?

   If a site is asking for your Discord account information—don’t input it. You should only share your Discord password via Discord’s official login page. Discord will never ask for your user token.

System Messages

If a message is officially by Discord, there will be a ‘system’ badge next to the system user’s name, like:

Discord Offical Links

The following is a list of all official Discord links that are operated by Discord themselves.

• discordapp.com
• discordapp.net
• discord.com
• discord.dev
• discord.new
• discord.gift
• discord.gifts
• discord.media
• discord.gg
• discord.co
• discord.app
• dis.gd
• watchanimeattheoffice.com

Common Scams

This scam is using a phishing “steam community” URL, to potentially steal your account details.

Inviting the bot will cause your server members to be mass DMed, with the same/similar message you got. Also, Nitro Generators break Discord ToS.

“I reported your steam account on an accident” scam.

Files

Files are like links, treat them with the same care. Avoid downloading non-image/text files. And, don’t fall for these types of scams:

Maintain a Safe Account

Keep in mind, if your account gets hacked; said hacker will have access to all your bots and their tokens. For more info about setting up a secure account, read Discord’s Support Article.

Summary

Never share your account token or password with anyone, the same stands for your bot token(s). Do not visit untrusted sites or download untrusted files. Keep your account safe, as if your account gets hacked; then your bot(s) could be hacked as well.

Sharding

Sharding is only available for bots with premium hosting time (AKA only for premium bots).

Sharding brings automatic separation of your bot between servers in order to speed up its operations and keep it stable when it has joined a large number of guilds.

Learn more about the sharding definition on TechTarget.

As stated in our Terms Of Service, we can’t guarantee you stable operation of your bot when it has joined a large number of guilds unless your bot has premium hosting time.

It should be noted that sharding doesn’t allow your bot to bypass the guild cap limit which is stated in our Terms Of Service.
Once your bot reaches the guild cap limit, the bot will no longer be able to be invited to any guild, unless the bot will leave other guilds.

If you’re wondering about if it’s possible to increase a guild cap limit for your bot, yes it’s possible.
You will have to contact the developers on this subject. But keep in mind, they may refuse for any reasons they see unfit and won’t increase it for reasons like “just in advance”, etc.
Also, your bot should be a premium bot in order to stably operate with a big number of guilds.

Time Format

Custom time formatting values for $creationDate, $userJoinedDiscord, and $userJoined functions.

Time Formats

List of supported time format values :

📌 All time format values are case-sensitive.

Troubleshooting

This page contains a number of troubleshooting that can help you to solve problems that BDFD users often encounter.

Summary

Troubleshooting for…

1. $onJoined[]
   • The Callback Doesn’t Work
2. Moderation And Server Management Related Commands
   • The Bot Can’t Assign Or Take Roles
   • Gives an Error When Trying To Moderate a Member
   • Gives an Error When Trying To Purge Messages
3. $addReactions, $addCmdReactions and $addMessageReactions
   • The Bot Fails To Add Reactions
4. $time
   • The Function Returns an Error
5. Economy Related Commands
   • Negative Balance
     • Pay Command
     • Roulette Command
   • Desynchronized Balance
     • The Balance Is Different On Different Servers
     • The Displayed Balance Is Different For Different Commands
6. Leaderboards
   • The Leaderboard Is Empty
   • The User’s Value Isn’t Updated
7. Bot Issues
   • The Bot Is Offline
   • The Bot Doesn’t Respond
   • The Bot Goes Offline From Time To Time
   • Desynchronization of Commands
     • Ghost Command
   • The Bot Takes A Long Time To Respond
   • The Slash Commands Don’t Appear
   • Integration Requires Code Grant
8. App Issues
   • The Ad Button Doesn’t Work
   • Ghost Functions From The Changelog
   • The Translation Feature Doesn’t Work

Let’s Troubleshoot Everything!

$onJoined[]

The Callback Doesn’t Work

The Null Reason
You misspelled the callback name. Make sure you don’t make any mistakes in the callback name.
Also, remember that callbacks are case-sensitive: you can’t write $onjoined[Channel ID], you must write $onJoined[Channel ID].

The 1st Reason
You specified the wrong Channel ID. How to get the Channel ID correctly:

The 2nd Reason
Your bot doesn’t have the sendmessages and/or the embedlinks permission that allow the bot to send messages (or embed messages) in a given channel.
Best Practice Solution
Grant both of these permissions to the bot in the desired channel through the channel’s permissions settings:

The 3rd Reason
There’s a critical error in your code.
Callbacks can’t return errors that occurred during code execution. Therefore, sometimes it’s difficult to solve errors in the callback code.
Best Practice Solution
Try debugging your command as a text command. In most cases, they’re backward compatible with the $onJoined callback, since both, by default, process the actions of the command author (when a user joins the server, this user becomes the “author” of this callback).

The 4th Reason
Members Intent isn’t enabled.
This callback requires the Members Intent to be enabled.

Read the Gateway Intents Guide for more details.

The 5th Reason
You have several commands with this callback.
You can only have one command with this callback. If you want to make a unique welcome message for multiple servers instead of just one, then check out Per-Server $onJoined.

Moderation And Server Management Related Commands

The Bot Can’t Assign Or Take Roles

The 1st Reason
Your bot doesn’t have the manageroles permission. Make sure that one of the roles that the bot has, has this permission enabled.

The 2nd Reason
You are trying to assign or take roles that are higher than the highest role your bot has.

Gives an Error When Trying To Moderate a Member

The 1st Reason
Your bot has lower priority than the specified user.
This means that the highest role your bot has is lower in position than the highest role the specified user has.
Or, the specified user is the owner of the server.

The 2nd Reason
Your bot doesn’t have the required permissions. Make sure that the permission list of any role that the bot has, have these required permissions.

• If you’re trying to ban a user.
  
• If you’re trying to kick a user.
  
• If you’re trying to timeout a user.
  
• If you’re trying to change user’s nickname.
  

  ⚠ Important note: bots can’t change the owner’s nickname!

Gives an Error When Trying To Purge Messages

The 1st Reason
Your bot doesn’t have the managemessages permission. Make sure that one of the roles that the bot has, has this permission enabled.

The 2nd Reason
You are trying to purge messages that have been around for more than two weeks.
BDFD uses a bulk request to purge messages, and it can’t process messages that are more than two weeks old.

$addReactions, $addCmdReactions and $addMessageReactions

The Bot Fails To Add Reactions

The 1st Reason
The user has blocked the bot, so the bot can’t react to the user’s messages. This works exactly the same if the user has blocked another user.

The 2nd Reason
You’re specifying the emoji in the function argument incorrectly.

• Default emojis.

  - $addCmdReactions[joy]
  + $addCmdReactions[:joy:]
  + $addCmdReactions[😂]
  

• Custom emojis.

  - $addCmdReactions[:pikachu:]
  - $addCmdReactions[\:pikachu:]
  + $addCmdReactions[<:pikachu:951437967711420456>]
  

  You must use the Emoji ID form of the desired emoji.

The 3rd Reason
Case with custom emojis.
Your bot must share a server with the specified emoji in order to use it. It works like Discord Nitro.

$time

The Function Returns an Error

The 1st Reason
Incorrect use of the function. The function doesn’t return the current time or anything like that.
The function’s role is to change the timezone for time-related functions (such as $day, $hour, and so on)

The 2nd Reason
Incorrect time zone or incorrect time zone format.
BDFD uses the official IANA time zone database for time zone information.
Please use the TZ Database name from this list in the $time function.

- $time[America]
- $time[New_York]
+ $time[America/New_York]

Economy Related Commands

• This part will have fully working and quality code examples that you can use in your bot.
• In this part, examples and more will be based on the local economy and BDScript 2.

Negative Balance

The 1st Possible Solution
Adding limiters or if statements that will prevent actions in which the executor’s or target’s balance becomes negative.
This solution can be an alternative to “Prevent actions when the amount is greater than the user’s balance”.

• Limiters Method

  $var[ourNewBalance;$sub[$getUserVar[Money];$var[amount]]]
  
  $onlyIf[$var[ourNewBalance]>0;Error Message]
  

• If Statements Method

  $var[ourNewBalance;$sub[$getUserVar[Money];$var[amount]]]
  
  $if[$var[ourNewBalance]<0]
      Error Message
  $else
      Code
  $endif
  

Pay Command

$nomention
$allowMention

$if[$argCount[$message]<2]
    $color[FF544C]
    $title[Payment System]
    $description[Missing Argumets! Example Command: `!pay <user> <amount> (comment)`]
    $stop
$endif

$var[target;$findUser[$message[1];no]]
$var[amount;$message[2]]
$var[comment;$trimSpace[$replaceText[$replaceText[$message;$message[1];];$message[2];]]]

$if[$var[target]==]
    $color[FF544C]
    $title[Payment System]
    $description[User (1st argument) not found on the server!]
    $stop
$endif

$if[$var[target]==$authorID]
    $color[FF544C]
    $title[Payment System]
    $description[You cannot pay yourself!]
    $stop
$endif

$if[$isNumber[$var[amount]]==false]
    $color[FF544C]
    $title[Payment System]
    $description[Amount (2nd argument) must be a number!]
    $stop
$endif

$if[$checkContains[$var[amount];.]==true]
    $color[FF544C]
    $title[Payment System]
    $description[Amount (2nd argument) must be an integer!]
    $stop
$endif

$if[$var[amount]<0]
    $color[FF544C]
    $title[Payment System]
    $description[Amount (2nd argument) cannot be less than 0!]
    $stop
$endif

$if[$var[comment]==]
    $var[comment;Not provided.]
$endif

$var[ourNewBalance;$sub[$getUserVar[Money];$var[amount]]]

$if[$var[ourNewBalance]<0]
    $color[FF544C]
    $title[Payment System]
    $description[❌ Hey <@$authorID>! What are you left with if you try to make such a payment?]
$else
    $color[7EFF88]
    $title[Payment System]
    $description[✔ You have successfully paid <@$var[target]> $var[amount] money! **Comment**: $var[comment]]

    $setUserVar[Money;$sum[$getUserVar[Money;$var[target]];$var[amount]];$var[target]]
    $setUserVar[Money;$var[ourNewBalance]]

    $if[$isUserDMEnabled[$var[target]]==true]
        $sendEmbedMessage[$dmChannelID[$var[target]];;Payment System;;Good time! <@$authorID> paid you $var[amount] money and left a comment: $var[comment];7EFF88]
    $endif
$endif

The 2nd Possible Solution
Setting the balance to 0 if the future balance becomes negative.
This solution may be suitable for gambling-related commands, if you do not want the user’s balance to become negative in case of losses.

$var[ourNewBalance;$sub[$getUserVar[Money];$var[bet]]]

$if[$var[ourNewBalance]<0]
    $var[ourNewBalance;0]
$endif

Roulette Command

$nomention

$var[bet;$message[1]]

$if[$isNumber[$var[bet]]==false]
    $color[FF544C]
    $title[Roulette]
    $description[Bet must be a number!]
    $stop
$endif

$if[$checkContains[$var[bet];.]==true]
    $color[FF544C]
    $title[Roulette]
    $description[Bet must be an integer!]
    $stop
$endif

$if[$var[bet]>$getUserVar[Money]]
    $color[FF544C]
    $title[Roulette]
    $description[The bet cannot be higher than your balance!]
    $stop
$endif

$if[$var[bet]<0]
    $color[FF544C]
    $title[Roulette]
    $description[The bet cannot be less than 0!]
    $stop
$endif

$var[bet;$multi[$var[bet];2]]

$if[$random[1;3]==1]
    $var[ourNewBalance;$sum[$getUserVar[Money];$var[bet]]]
    
    $color[7EFF88]
    $title[Roulette]
    $description[Wow, you are lucky! You have won $var[bet]!]
$else
    $var[ourNewBalance;$sub[$getUserVar[Money];$var[bet]]]
    
    $color[FF544C]
    $title[Roulette]
    $if[$var[ourNewBalance]<0]
        $var[ourNewBalance;0]
        $description[What a pity! You lost and became bankrupt!]
    $else
        $description[What a pity! You have lost the $var[bet].]
    $endif
$endif

$setUserVar[Money;$var[ourNewBalance]]

Desynchronized Balance

The Balance Is Different On Different Servers

This is because you’re probably using $setUserVar and $getUserVar in your economy. But these functions are based as local variables. Their values are unique for each server.
If you want the same balance on all servers, you should use $setVar and $getVar (with userID arguments). These functions are based on global user variables.

The Displayed Balance Is Different For Different Commands

Most often this is because you’ve mixed up the variable functions and you’re using the wrong variable type.
For example, if you use $setUserVar and $getUserVar in the Roulette command and $getVar in the Balance command, this will show different values. The solution to this is to replace $getVar with $getUserVar in the Balance command, or vice versa, replace $setUserVar and $getUserVar with $setVar and $getVar accordingly in the Roulette command.
Note: don’t forget that global user variables require a userID argument.

Leaderboards

The Leaderboard Is Empty

The 1st Reason
You’ve chosen the wrong leaderboard function.

• If you’re using the $setUserVar/$getUserVar functions, you should use the $userLeaderboard function.
• If you’re using the $setVar/$getVar functions, you should use the $globalUserLeaderboard function.
• If you’re using the $setServerVar/$getServerVar functions, you should use the $serverLeaderboard function.

The 2nd Reason
(In case you are using the $getLeaderboardValue function)
You specified the wrong variable type.

• If you’re using the $setUserVar/$getUserVar functions, you should specify the user as type.
• If you’re using the $setVar/$getVar functions, you should specify the globalUser as type.
• If you’re using the $setServerVar/$getServerVar functions, you should specify the server as type.

The 3rd Reason
The leaderboard haven’t generated yet.
Sometimes it takes a while to generate the leaderboard.

The User’s Value Isn’t Updated

As with the generation of the leaderboard, updating it can also take a while.
This can be mainly due to the fact that the leaderboard has a large database (i.e. the total number of users with a modified variable value other than the default).

Bot Issues

The Bot Is Offline

The 1st Reason
The node is restarting. While the node is restarting, logically, the bot can’t work.
Usually restarting doesn’t take more than 5-10 minutes.
So please wait a while and have a cup of tea or coffee while the node restarts.

The 2nd Reason
For some reason, your bot’s token is no longer valid or the BDFD app thinks so.
You can solve this problem by regenerating your bot’s token on the developer portal and then replacing the old token with the new one in the BDFD app bot’s Settings tab.

The 3rd Reason
Not a common problem, but possible. The node your bot is running on is experiencing problems.
In this case, join the support server, create a ticket using the !new command and tell the staff your bot’s ID and node number, if you know it (node number can be found out using the $botNode function when your bot is online).
The staff will inform the developers of the current problems, providing the scale of the problem (affected bots and/or nodes).
Please don’t regenerate your bot token in this case, as it leads to node change. If everyone starts changing their node because there is a problem on that node, then a healthy node can also be affected by this problem.

The Bot Doesn’t Respond

The 1st Reason
If your bot is based on text commands and you don’t have the Message Content Intent enabled.
You must enable it in your bot’s settings to use text commands.
Read the Gateway Intents Guide for more details.

The 2nd Reason
Your bot doesn’t have the necessary permissions.
In order for your bot to respond correctly to a command, it must have permissions for Send Messages, Embed Links (if your code has embed functions), and Read Messages in order for the bot to have access to the channel.

The Bot Goes Offline From Time To Time

This is due to the fact that nodes are restarted from time to time to maintain the stable operation of all the bots that also work on this node.

Desynchronization of Commands

Desynchronization of commands means, for example, that you have deleted a command but the bot still responds to it (aka. Ghost Command), or you see a different code of your command in the web app and another in the mobile app.

Ghost Command

Not many people encounter this problem, but it’s still worth mentioning.
This problem is related to database synchronization (between your application data and your bot’s data in the database).
Solution Options
The 1st Solution
Restart the app.
Close the app from Recent apps and reopen it. This may result in a deleted command reappearing due to desync with the database. You can just delete that command again.

The 2nd Solution
Attempting to forcibly restart the bot.
You can do this in the settings of your bot in the app. Restarting the bot can send a retransfer of data from the application to the database, and then the deleted command will be deleted for real.

The Solution Options Didn’t Help
In this case, join the support server, create a ticket using the !new command and tell the staff your bot’s ID.
The staff will mention one of the developers to take a look at this problem with your bot.

The Bot Takes A Long Time To Respond

The 1st Reason
Your code is too long and/or complicated.
This may be the obvious reason if it is. Executing large and complex code takes more resources.
When writing code, you should think about how to make it more compact and less complex, but in a way that makes your idea come to fruition.

The 2nd Reason
Your bot was rate limited. This can happen because of excessive requests to the Discord API, performed by BDFD functions (such as $addEmoji and others).
You should not stack such functions and try to perform them all at once.

The 3rd Reason
The node your bot is running on is experiencing some slight problems (such as a rate limit). If you’re sure this is the case, you can regenerate the bot’s token and replace it with a new one. This will cause your bot to change its node.

The Slash Commands Don’t Appear

The 1st Reason
Old version of the application. Make sure that you have the latest version of the application installed.
New versions of the application have been improved and updated, and new features have been added. In addition, errors with the validity check of the slash commands have been fixed. You will be warned if you set up your slash command incorrectly, in which case the application will not allow you to save the slash command.

The 2nd Reason
Slash commands are cached by discord, so it takes time before they appear in discord.

They’re also cached on the client side, if they were successfully cached in discord. If other users have a new slash command and you don’t, restart your discord client.
Restarting will cause existing slash commands to be cleared and new ones will cache.

The 3rd Reason
Conflict of slash commands due to other services that you’re no longer using. For example, if two slash commands of same type have the same name, but one is created using a third-party service, and the other through the BDFD App, this can cause a conflict and the slash command will not appear.
You can solve this problem by Syncing slash commands with discord in the bot’s settings. This removes third-party service slash commands and leaves only those that were created in our application.

Integration Requires Code Grant

You can only get this error when trying to invite a bot to any server.
Most likely, you have accidentally or unknowingly enabled the Require OAuth2 Code Grant option in your bot’s settings in the developer portal.
This is the reason why you get this error.

This option is required only for applications with scopes such as identify, email, and others to work with the user account in Discord. BDFD doesn’t have such support, so you should not enable this option or choose any other scopes other than bot.

App Issues

The Ad Button Doesn’t Work

The 1st Reason
Unstable Internet connection. Make sure your Internet connection is stable and not too slow, because you have to load the ad first to watch it. This is why you see “Loading ad…”.

The 2nd Reason
There’re no more ads for you. If that’s the reason, there’s nothing we can do about it, it’s the provider who provides the ads, not us. Try to see the ad later. If the case persists, go to our support server, create a ticket using the !new command and inform the staff about your problem by providing a screen recording longer than 30 seconds.

The 3nd Reason
The advertising provider we use is blocked in your country or region. There is nothing we can do in this case.

Possible Solutions

1. Clearing the application cache and restarting it.
2. Using VPN services. This may be the best solution for the 2nd and 3rd reasons, and in some cases for the 1st reason.
3. In a desperate case, restart the smartphone and/or reinstall the app.

   If you decide to reinstall the app, make sure that you are logged in to the app, otherwise you will lose access to your bots.

Ghost Functions From The Changelog

In this section, the easiest way to explain everything is through dialogue:

The Translation Feature Doesn’t Work

The 1st Reason
There’s no translation support for your language yet. You should wait patiently for them, or if you speak English well, you can help to translate our app yourself!
If you would like to help, go to our support server and create a ticket (using the !new command). You can then apply for the Translator role there by asking support for it.

The 2nd Reason
Your main system language is incorrect.
Our app uses the main system language for translations and it disregards any secondary languages.
So, for example, if you have English as your main system language and Russian as your second system language, the app will stay in English.

In order to have the app in Russian, you should reorder your language settings and set Russian as the main one.

That’s Where The List Of Troubleshootings Ends

If you know of other problems that users often encounter or have suggestions, feel free to let us know on the support server or by contributing!

BDScript

In this section of the wiki, you will learn about the functions that exist in BDScript. Using functions is an integral part of your bot, because thanks to them you will bring functionality to your bot!

Remember that any function starts with a $ sign. For example, $nomention or $ping. It is also worth remembering that the name is case sensitive.

$addButton

Adds a button to a message.

Syntax

$addButton[New row?;Interaction ID/URL;Label;Style;(Disable?;Emoji;Message ID)]

Parameters

• New row? (Type: Bool || Flag: Required): If set to yes, the button will appear in a new row. If set to no, the button will appear in the same row as the previous button.

  A message can have a maximum of 25 buttons (5 rows of 5 buttons).

• Interaction ID/URL (Type: String, URL || Flag: Required): Depending on the button type, you either set it to Interaction ID which is then used in $onInteraction[ID] callback or URL if it’s a link button.

• Label (Type: String || Flag: Emptiable): The text value visible on the button.

• Style (Type: Enum || Flag: Required): It’s used to specify the button’s background color. If the button has a link/URL, you have to set the value to link. Check this section for more details.

• Disable? (Type: Bool || Flag: Vacantable): If set to yes, the button can’t be pressed. Defaults to no.

• Emoji (Type: Emoji || Flag: Vacantable): Adds an emoji inside the button. Emojis have to be either pasted as unicode, alias or be in the following format <:emoji name:emoji ID>.

• Message ID (Type: Snowflake || Flag: Vacantable): Adds the button to the provided message ID. It’s important to note that the provided message ID author has to be the bot.

Interactive buttons can’t have duplicated ID’s in the same message. So for example, you can’t have two buttons with the ID set to test.

If URL is used in the Interaction ID/URL argument, it has to start with http:// or https://.

Button Style

Buttons can have different styles (background colors). Here, are all possible values for the style function argument.

• primary - Blue button
• secondary - Gray button
• success - Green button
• danger - Red button
• link - Redirect button

If link style is used, the button won’t send any interactions!

Example

$nomention
Hello
$addButton[no;test;Say hello!;primary;no;]

For more info, see the Buttons Guide.

$addCmdReactions

Adds reactions to the message that triggered the command.

Syntax

$addCmdReactions[Emojis;...]

Parameters

• Emojis (Type: Emoji || Flag: Required): The emoji(s) the bot reacts with. Use semicolons ; as a separator to separate multiple emojis.

You can use unicode emojis, emoji IDs, and emoji aliases.

For emoji aliases, make sure to put : in front and at the end of the alias.
For emoji IDs, the bot must be present in the server that the emoji originates from.

List of unicode emojis: 😋 Get Emoji
List of supported emoji aliases: Emoji Aliases

Example

$nomention
$addCmdReactions[$message]

How to get emoji ID?

This method requires Developer Mode to be enabled!

1. Type \:TheEmojiName:
2. Send the message.
3. Copy the ID it returns. (The emoji ID should be in this format: <:emojiName:ID>. If the emoji is animated, it should look like this: <a:emojiName:ID>)
4. Input the emoji ID into $addCmdReactions[]. (e.g. $addCmdReactions[<:hollyDab:828628880629825546>])

If you’re still having issues, check the Troubleshooting page.

$addEmoji

Adds an emoji to the server.

Syntax

$addEmoji[Name;Image URL;Return emoji?]

Parameters

• Name (Type: String || Flag: Required): The name of the new emoji.
• Image URL (Type: URL || Flag: Required): The image of the new emoji. The link needs to be a valid image URL.
• Return emoji? (Type: Bool || Flag: Required): Whether to show the emoji in the bot’s message or not. (yes/no)

Example

$nomention
$argsCheck[>2;Provide all needed arguments! Usage: `!add-emoji (imageURL) (emojiName)`]
Added new emoji: $addEmoji[$replaceText[$message;$message[1];;1];$message[1];yes]

$addField

Adds a field to an embed.

Syntax

$addField[Name;Value;(Inline?;Index)]

📌 You can add up to 25 fields per embed.

Parameters

• Name (Type: String || Flag: Required): The name of the field. It cannot exceed more than 256 characters.
• Value (Type: String || Flag: Required): The value of the field. It cannot exceed more than 1024 characters.
• Inline? (Type: Bool || Flag: Optional): If yes, fields will appear in the same line. However, if you have more than 3 fields (or the fields are just too long) with inline enabled, the bot will return rows with 3 fields (2 if there is a thumbnail) in each row. It is set to no by default.
• Index (Type: Integer || Flag: Optional): Adds the field to a specified embed index number. (learn more)

💡 Inline fields may not appear inline on some mobile devices.

Examples

Without inline fields

$nomention
$addField[The field name 1!;The field value 1!]
$addField[The field name 2!;The field value 2!]
$addField[The field name 3!;The field value 3!]

With inline fields

$nomention
$addField[The field name 1!;The field value 1!;yes]
$addField[The field name 2!;The field value 2!;yes]
$addField[The field name 3!;The field value 3!;yes]

$addMessageReactions

Adds reactions to the specified message.

Syntax

$addMessageReactions[Channel ID;Message ID;Emojis;...]

Parameters

• Channel ID (Type: Snowflake || Flag: Required): The ID of the channel where the message is located.
• Message ID (Type: Snowflake || Flag: Required): The ID of the message to which the reactions will be added.
• Emojis (Type: Emoji || Flag: Required): The emoji(s) to add as reaction to the message. Use semicolons ; as a separator to separate multiple emojis.

You can use unicode emojis, emoji IDs, and emoji aliases.

For emoji aliases, make sure to put : in front and at the end of the alias.
For emoji IDs, the bot must be present in the server that the emoji originates from.

List of unicode emojis: 😋 Get Emoji
List of supported emoji aliases: Emoji Aliases

Example

$nomention
$trimContent
$addMessageReactions[$channelID;$message[1];👍;✨;<:coolemoji:991742553340792882>]

Successfully added the reactions to the message.

How to get emoji ID?

This method requires Developer Mode to be enabled!

1. Type \:TheEmojiName:
2. Send the message.
3. Copy the ID it returns. (The emoji ID should be in this format: <:emojiName:ID>. If the emoji is animated, it should look like this: <a:emojiName:ID>)
4. Input the emoji ID into $addMessageReactions[]. (e.g. $addMessageReactions[$channelID;1123254137547653222;<:hollyDab:828628880629825546>])

If you’re still having issues, check the Troubleshooting page.

$addReactions

Adds reactions to the bot’s response.

Syntax

$addReactions[Emojis;...]

Parameters

• Emojis (Type: Emoji || Flag: Required): The emoji(s) the bot reacts with. Use semicolons ; as a separator to separate multiple emojis.

You can use unicode emojis, emoji IDs, and emoji aliases.

For emoji aliases, make sure to put : in front and at the end of the alias.
For emoji IDs, the bot must be present in the server that the emoji originates from.

List of unicode emojis: 😋 Get Emoji
List of supported emoji aliases: Emoji Aliases

Example

$nomention
Yes or No?
$addReactions[✅;:x:]

How to get emoji ID?

This method requires Developer Mode to be enabled!

1. Type \:TheEmojiName:
2. Send the message.
3. Copy the ID it returns. (The emoji ID should be in this format: <:emojiName:ID>. If the emoji is animated, it should look like this: <a:emojiName:ID>)
4. Input the emoji ID into $addReactions[]. (e.g. $addReactions[<:hollyDab:828628880629825546>])

If you’re still having issues, check the Troubleshooting page.

$addSelectMenuOption

Adds a new select menu option to an existing select menu.

Syntax

$addSelectMenuOption[Menu option ID;Label;Value;Description;(Default?;Emoji;Message ID)]

Parameters

• Menu option ID (Type: String || Flag: Required): The ID used in $newSelectMenu[].
• Label (Type: String || Flag: Required): The name of the option.
• Value (Type: String || Flag: Required): It’s the data that gets passed to the $onInteraction[] callback. The value has to be unique in the select menu!
• Description (Type: String || Flag: Emptiable): A text which shows up under the Label.
• Default? (Type: Bool || Flag: Vacantable): Whether the option should be selected by default or not. Defaults to no. (yes/no) There can be only one default option!
• Emoji (Type: Emoji || Flag: Vacantable): The emoji that shows up next to the Label.
• Message ID (Type: String || Flag: Vacantable): The ID of a message that should have a new select menu option added to an existing select menu. By default it’s the bot’s response.

Example

$nomention
$newSelectMenu[Example;1;1;Choose some option]
$addSelectMenuOption[Example;First;first-option;The first option]
$addSelectMenuOption[Example;Second;second-option;The second option]
$addSelectMenuOption[Example;Third;third-option;The third option]

For more info, see the Select Menu Guide.

$addTextInput

Adds a new text input field to a modal.

Syntax

$addTextInput[Text input ID;Style;Label;(Minimum length;Maximum length;Required?;Value;Placeholder)]

📌 You can add up to 5 text input fields to a modal.

Parameters

• Text input ID (Type: String || Flag: Required): The ID that is used to retrieve the text input in the field. This value must be unique!
• Style (Type: Enum || Flag: Required): The text input field style, either short or paragraph.
• Label (Type: String || Flag: Required): The name of the text input field. This value must be less than or equal to 45 characters.
• Minimum length (Type: Integer || Flag: Vacantable): Minimum number of characters a user needs to input. This value must be an integer between 0 and 4000, and can’t be greater than the Maximum length.
• Maximum length (Type: Integer || Flag: Vacantable): Maximum number of characters a user can input. This value must be an integer between 0 and 4000, and can’t be less than the Minimum length.
• Required? (Type: Bool || Flag: Optional): Whether a user must fill in the text input field or not. Defaults to yes. (yes/no)
• Value (Type: String || Flag: Vacantable): The text that is written by default in the text input field. This value must be less than or equal to 4000 characters and must not be less than Minimum length and no more than Maximum length.
• Placeholder (Type: String || Flag: Vacantable): The text that is displayed if the text input field is empty. This value must be less than or equal to 100 characters.

Styles

• short - A small text input field.
• paragraph - A big text input field.

Example

$nomention
$newModal[modal;User Bio]
$addTextInput[modalInput1;short;What is your name?;3;30;yes;;Mikołaj]
$addTextInput[modalInput2;short;What are your pronouns?;2;30;yes;;He/Him]
$addTextInput[modalInput3;paragraph;Can you tell us about yourself?;5;1000;no;;I am a Developer]

For more info, see the Modals Guide.

$addTimestamp

Adds a timestamp to an embed.

Syntax

$addTimestamp

Example

$nomention
$description[Hi!]
$footer[That is the timestamp =>]
$addTimestamp

$addTimestamp[]

Adds a timestamp to a specific embed.

Syntax

$addTimestamp[Index]

Parameters

• Index (Type: Integer || Flag: Optional): To which embed the timestamp should be added to. (learn more)

Example

$nomention
$description[Hi!]
$description[Timestamp!;2]
$footer[That is the timestamp =>;2]
$addTimestamp[2]

$allMembersCount

Returns the total number of users from every server the bot is in.

Syntax

$allMembersCount

Example

$nomention
I'm serving $allMembersCount users!

$allowMention

Disables replacing mentions in $message with text.

Syntax

$allowMention

Example

$nomention
$allowMention
$message

With $allowMention:

Without $allowMention

$allowRoleMentions

Enables role pings only for the provided role IDs, while the roles not provided will be “fake pinged” (the role will be pinged, but users will not be notified).

Syntax

$allowRoleMentions[Role IDs;...]

Parameters

• Role IDs (Type: Snowflake || Flag: Emptiable): The role(s) that can be pinged, leave empty to disable pings for every role. Separate role IDs using ;.

Example

$nomention
$allowRoleMentions[]
I'm pinging <@&858376972303204362>, but no one got notified; wow!

$allowUserMentions

Enables user pings only for the provided user IDs, while the user not provided will be “fake pinged” (the user will be pinged, but user will not be notified).

Syntax

$allowUserMentions[User IDs;...]

Parameters

• User IDs (Type: Snowflake || Flag: Emptiable): The user(s) that can be pinged, leave empty to disable pings for every user. Separate user IDs using ;.

Example

$nomention
$allowUserMentions[]
Hi <@696368083517964288>! I mentioned you, but you didn't get pinged.

$alternativeParsing

Changes the way how triggers are read.

Syntax

$alternativeParsing

This function was added at the end of 2019 as an experiment, and it can be unstable and break your commands. You should not use $alternativeParsing when making your bot.

Example

1. Create two commands and set the trigger hello for one command and helloworld for the other.

2. Add the $alternativeParsing function to the command code with the hello trigger.

   Code with trigger hello:

   $nomention
   $alternativeParsing
   $description["hello"]
   

   Code with trigger helloworld:

   $nomention
   $description["helloworld"]
   

3. Execute commands.

   With $alternativeParsing

   hello "hello" helloworld "helloworld"

   Without $alternativeParsing

   hello "hello" helloworld "helloworld" "hello"

$and

Returns true if every provided condition is true, otherwise false is returned.

Syntax

$and[Conditions;...]

Parameters

• Conditions (Type: String || Flag: Required): Checks that will be carried out. All conditions must be true for this function to return true. Separate conditions using ;.

Signs

== - Equal

!= - Not Equal

< - Less Than

> - Greater Than

>= - Greater Than Or Equal To

<= - Less Than Or Equal To

• These signs could vary in meaning based on the order or intent of the if statement.
• If you are using text as your x and/or y, you can not use any other signs besides == and !=. However for numbers, you can use any sign shown in the above list.

Example

$nomention
$and[$nickname==MineBartekSA;$message==Update]

For more info, see the If Guide.

$argCount

Returns how many words (aka arguments/args) are in the provided text.

Syntax

$argCount[Text]

Parameters

• Text (Type: String || Flag: Emptiable): The text to get the word count for.

Example

$nomention
Word count: $argCount[$message]

$argsCheck

When this function is used, the command can only be executed if the user’s message contains a certain amount of arguments (words).

Syntax

$argsCheck[How many?;Error message]

Parameters

• How many? (Type: HowMany || Flag: Required): How many arguments there should be in the user’s message.

  If you want users to have 3 or more arguments in their message, you can use >3. If you want users to have less than 3 arguments in their message, you can use <3. If you want the users to have exactly 3 arguments in their message, put 3.

• Error message (Type: String || Flag: Emptiable): The message that the bot will send if the user has too many/few arguments.

Example

$nomention
$argsCheck[>1;❌ Please provide something for me to say!]
$message

$author

Adds author text to an embed.

Syntax

$author[Text;(Index)]

Parameters

• Text (Type: String || Flag: Emptiable): The text that appears in the author text. It cannot exceed more than 256 characters.
• Index (Type: Integer || Flag: Optional): To which embed the author text will be added. (learn more)

Example

$nomention
$author[This is the author text!]

$authorAvatar

Returns the author’s avatar URL.

Syntax

$authorAvatar

Example

$nomention
$image[$authorAvatar]

You can use ?size=size at the end of the avatar URL to increase/decrease the image size. Example sizes: 1024, 2048, 4096.

(e.g. $image[$authorAvatar?size=4096])

$authorIcon

Adds an icon to the author section in the embed.

Syntax

$authorIcon[Image URL;(Index)]

$authorIcon[] will not work if there is no text provided in $author[].

Parameters

• Image URL (Type: URL || Flag: Emptiable): The image for the author icon. This must be a valid image URL.
• Index (Type: Integer || Flag: Optional): To which embed the author icon will be added. (learn more)

Example

$nomention
$authorIcon[$authorAvatar]
$author[⬅️ That is the author icon. This is the author text.]

$authorID

Returns message’s author ID.

Syntax

$authorID

Example

$nomention
This command was executed by <@$authorID>!

$authorOfMessage

Returns the ID of the provided message’s author.

Syntax

$authorOfMessage[Channel ID;Message ID]

Parameters

• Channel ID (Type: Snowflake || Flag: Required): The channel where the message is located.
• Message ID (Type: Snowflake || Flag: Required): The message for which the author ID will be returned.

How to get the Message/Channel ID guide.

Example

$nomention
Author of message: $username[$authorOfMessage[$message[1];$message[2]]]

$authorURL

Adds a hyperlink to the author text.

Syntax

$authorURL[URL;(Index)]

$authorURL[] will not work if there is no text provided in $author[].

Parameters

• URL (Type: URL || Flag: Emptiable): The link to set as the author hyperlink.
• Index (Type: Integer || Flag: Optional): To which embed the author URL will be added. (learn more)

Example

$nomention
$author[Click me to visit the BDFD website!]
$authorURL[https://botdesignerdiscord.com]

$awaitFunc

Used to initiate an awaited command.

Syntax

$awaitFunc[Name;(User ID;Channel ID)]

Parameters

• Name (Type: String || Flag: Required): The name used inside the $awaitedCommand[] and $awaitedCommandError[] callbacks.
• User ID (Type: Snowflake || Flag: Vacantable): The user the awaited command will trigger for. Uses command author, if User ID is not present.
• Channel ID (Type: Snowflake || Flag: Optional): The channel where the command will be awaited. Uses current channel, if Channel ID is not present.

Example

$nomention
What do you want me to say?
$awaitFunc[say]

For more info, see the Awaited Commands Guide.

$ban

Bans the mentioned user.

Syntax

$ban

Example

$nomention
$ban
<@$mentioned[1]> was banned!

$ban[]

Bans the mentioned user with a reason.

Syntax

$ban[Reason]

Parameters

• Reason (Type: String || Flag: Emptiable): The reason for the ban, which will be saved in the audit-log.

Example

$nomention
$ban[$noMentionMessage]
<@$mentioned[1]> was banned!

$banID

Bans a user using their ID without reason. The user ID will be taken from the last part of the author’s message.

Syntax

$banID

Example

$nomention
$onlyPerms[ban;You need the `ban` permission to use that command!]
<@$findUser[$message;no]> was banned!
$banID

How $findUser[] works?

$banID[]

Bans a user using their ID.

Syntax

$banID[Reason;(User ID)]

Parameters

• Reason (Type: String || Flag: Emptiable): The reason for the ban, which will be saved in the audit-log.

  Use $getBanReason[] to get the ban reason.

• User ID (Type: Snowflake || Flag: Vacantable): The user to ban. If empty, the ID will be taken from the last part of the author’s message.

Example

$nomention
$onlyAdmin[You need the `admim` permission to use that command!]
$argsCheck[>1;Please provide a `user`. Syntax: `!ban (user) <reason>`]
$onlyIf[$findUser[$message[1];no]!=;Failed to find user!]
<@$findUser[$message;no]> was banned!
$banID[$replaceText[$message;$message[1];;1];$findUser[$message[1];no]]

How $findUser[] works?

$blackListIDs

Blocks certain users from using the command.

Syntax

$blackListIDs[User IDs;...;Error message]

Parameters

• User IDs (Type: Snowflake || Flag: Emptiable): The user(s) to blacklist from using the command. Use semicolons ; as a separator to separate multiple user IDs.

  How to get user ID?

• Error message (Type: String || Flag: Emptiable): The message that will be sent when the user running the command is blacklisted.

Example

$nomention
$blackListIDs[566613317972394004;437154602626973697;❌ You can't use this command!]
Pong! $ping ms

$blackListRoles

Blocks users with certain role(s) from using the command. If the user has any role in the blacklist, they will not be able to run the command. Uses role names instead of role IDs.

Syntax

$blackListRoles[Role names;...;Error message]

Parameters

• Role names (Type: String || Flag: Emptiable): The name(s) of the role(s) to blacklist. Use semicolons ; as a separator to separate multiple role names.
• Error message (Type: String || Flag: Emptiable): The message that will be sent if the user has a role from the blacklist.

Example

$nomention
$blackListRoles[Owner;Bot;❌ You can't use this command!]
Pong! $ping ms

$blackListRolesIDs

Blocks users with certain roles from using the command. If the user has any role in the blacklist, they will not be able to run the command.

Syntax

$blackListRolesIDs[Role IDs;...;Error message]

Parameters

• Role IDs (Type: Snowflake || Flag: Emptiable): The role(s) that will be blacklisted. Use semicolons ; as a separator to separate multiple role IDs.
• Error message (Type: String || Flag: Emptiable): The message that will be sent if the user has a role from the blacklist.

Example

$nomention
$blackListRolesIDs[1009019299987476540;1014547313957539901;❌ You can't use this command!]
Pong! $ping ms

$blackListServers

Blocks certain servers from using the command.

Syntax

$blackListServers[Guild IDs;...;Error message]

Parameters

• Guild IDs (Type: Snowflake || Flag: Emptiable): The server(s) to blacklist from using a command. Use semicolons ; as a separator to separate multiple server IDs.

  Where do I find server IDs? (click-me)

• Error message (Type: String || Flag: Emptiable): The message that will be sent if the command is run in a blacklisted server.

Example

$nomention
$blackListServers[1009018669982031912;❌ You can't use this command!]
Pong! $ping ms
*Guild ID: $guildID*

$blackListUsers

Blocks certain users from using the command. Uses usernames instead of user IDs.

Syntax

$blackListUsers[Usernames;...;Error message]

Parameters

• Usernames (Type: String || Flag: Emptiable): The username(s) to blacklist. Use semicolons ; as a separator to separate multiple usernames.
• Error message (Type: String || Flag: Emptiable): The message that will be sent when the username of the user running the command is blacklisted.

Example

$nomention
$blackListUsers[RainbowKey;❌ You can't use this command!]
Pong! $ping ms

$boostCount

Returns the current guild’s number of nitro boosts.

Syntax

$boostCount

Example

$nomention
This server currently has $boostCount boost(s).

$boostCount[]

Returns a guild’s number of nitro boosts.

Syntax

$boostCount[Guild ID]

Parameters

• Guild ID (Type: Snowflake || Flag: Required): The guild to get the number of boosts for.

Example

$nomention
This server currently has $boostCount[$message[1]] boost(s).

$botCommands

Returns a list of the bot’s commands.

Syntax

$botCommands[Separator]

Parameters

• Separator (Type: String || Flag: Required): Will be used to separate each command.

Example

$nomention
$botCommands[🔹]

$botID

Returns the bot’s ID.

Syntax

$botID

Example

$nomention
My ID is: $botID

$botLeave

Forces the bot to leave the current server.

Syntax

$botLeave

Example

$nomention
$sendMessage[I left this server!]
$botLeave

If you are using BDScript 2, put $botLeave at the very bottom of the code so that the code works correctly i.e:

❌ Not correct:

$botLeave
$nomention
$sendMessage[I left this server!]

✅ Correct:

$nomention
$sendMessage[I left this server!]
$botLeave

$botLeave[]

Forces the bot to leave the server matching the provided server ID.

Syntax

$botLeave[Guild ID]

Parameters

• Guild ID (Type: Snowflake || Flag: Required): The ID of the guild to leave.

Example

$nomention
$sendMessage[I left out `$serverName[$message]` server.]
$botLeave[$message]

If you are using BDScript 2, put $botLeave[] at the very bottom of the code so that the code works correctly i.e:

❌ Not correct:

$botLeave[$message]
$nomention
$sendMessage[I left this server!]

✅ Correct:

$nomention
$sendMessage[I left this server!]
$botLeave[$message]