This feature allows you to set up custom commands that Cakey Bot can handle. For example, you can make your own command called
!support which will post a message informing your users where they can get support for your server.
You will need
Administratorpermission to manage servers and custom commands.
The command trigger will use a custom set prefix if you have changed Cakey Bot's prefix.
Custom Commands will work with BOTH Basic Placeholders & Advanced Placeholders. Placeholders can be included in the response section and can modify the behavior/output of the response. You can find the full list of supported placeholders here.
Emoji/Emotes CAN be used in Custom Commands. However, it requires slightly more work due to how discord parses emotes. Normally in Discord, you could just type
:smile: to get an emote, however in Cakey Bot, neither of these will work. In order to get valid emojis you have to send the emojis in discord but place a backward slash in front of it to get the emote's full ID. Like so:
\:smile: which will produce these results:
<:lel:408424717217693717> or for Unicode emoji:
😄 . Once you have the full emoji id or the raw Unicode output, you can paste these into Cakey Bot's web dashboard and they should work as long as Cakey Bot is in a server that has that custom emote in it.
It is worth noting that Cakey Bot can use emojis in between servers (similar to nitro users). So if you have an emoji in Server #1, you can use that emoji in a response for Server #2 if Cakey bot is in both of those servers.
To use images in responses, you can simply just type the image URL/link like you would in a normal message. If you have the file on your local machine/PC but no URL/link, you can upload it to an image hosting website (such as Imgur) and paste the URL they provide into the response. Cakey Bot should automatically embed the image in Discord's client if it's a valid URL/image.
Using custom embeds on responses is a Premium Only feature.
You can include an optional embed on responses by following the steps below:
You must apply via support tickets to get access to Bulk Import. Anyone can use Bulk Export without applying. This is to decrease potential abuse.
Responsefields MUST be Base64 encoded.
Base64 is a group of binary-to-text encoding schemes that represent binary data in sequences of 24 bits that can be represented by four 6-bit Base64 digits. This sounds complicated, however, it's EXTREMELY easy to convert text to and from Base64 encoding. There are tons of online tools just like this one that automates the entire process just by you pasting your text in it.
If you are using the tool linked above, all you have to do is paste your text in the top text input and it'll convert it into Base64 encoding and display it in the second text box. You can also convert Base64 back into text by using this tool OR by selecting "Decoding" at the top of the page and using the same process.
Note: The convert file process on this page converts the ENTIRE raw file itself and not just the contents of the file. This means you can NOT use the convert file process when converting for Cakey Bot.
This is easy as well! Using the same Base64 encoding tool linked above you can simply paste all of your data (each row on a new line) and simply check the
"Encode each line separately (useful for when you have multiple entries)." option. This will then convert each line individually rather than treating every single line as a single blob of text.
Note: If you are doing this for a ton of data, you can only process/paste one column of data at a time. If you try to copy multiple columns in the spreadsheet and paste all of them at once it'll merge the rows together as a single string.
The template CSV file and bulk exported CSVs will have a few different columns with various restrictions. These are explained below: