Complete Command List

Below, you will find a list of all the commands. Each command links to a section that expands further on the command. To run these commands, use your guilds prefix followed by the command name.


The heart of Threadstorm. This command can be used in multiple ways. The most basic way to use this is to invoke it without any arguments. Doing so will take you through a setup process to make a thread. At the end, you will have made your own thread. Alternative ways of using tmake include using flags to make a thread in one message or supplying a json file to create a thread.

tmake flags

As of now, there are only two flags. -t and -b. -t represents the title part of a thread and -b represents the body. You must use these two flags together to have a sucessful action. The order in which you use these do not matter, just that both are used.

Example: .tmake -t This is my title -b this is something that isn't a title

tmake json

Additionally, json files are supported for thread creation. In order to use a json file you must provide a properly formatted file when you invoke the command. For an example of a properly formatted file, refer to this website. If you opt for this option there are four things you should know.

1 The "content" key from the json file must be removed. 2 The bot can only post one embed. If you supply multiple embeds in one file, only the last one processed will be posted. 3 If you need to edit the thread for any reason, you can only use the json flag with tedit. 4 The author and footer will be overriden.

See below for a format Threadstorm can accept:

"embeds": [
    "title": "A title or something",
    "description": "If I had something to talk about, I'd put it here. But I don't so nothing will go here",
    "url": "",
    "color": 3866008,
    "image": {
        "url": ""

To use a json file, simply upload a json file when you run the command. The file should be attached to the message.


In some cases, you need to edit something. tedit lets you do just that. You are able to edit any of the following properties if the thread was made by you or you have the Manage Messages permission.


This will override the current thread title. Doing so will also update the channel name and the embed to match what you typed. Along with these updates, the time of the edit will be recorded at the bottom of the thread so other users know when a thread was edited.


Unlike title, this will not override any text. Instead, it will append text to the original message. Use this as a way to further clarify a point or add more on to your thread. This will also append an edit timestamp to the bottom of the original message. If you are a moderator (Someone with Manage Messages), your edits will be highlighted with a "MOD >" tag on the bottom with a timestamp.


The picture argument lets you either add or replace an image in an embed. You similar to making a json-based thread, you will need to upload a picture when you use this command that is attached to the message.


This option is only available if the thread was created with a json file. If it wasn't, you will receive a warning saying this cannot be done. Otherwise, you run this command with your new json file attached to the command. NOTE: This will replace all of the content in the original thread except the author and footer areas.


If you desire to have a more organized experience, you can also setup custom categories people can use. By default, all threads made will be dumped into the default channel. If you find Threadstorm is getting a lot of use, you may find creating another category to be helpful.

To do so, simply type .tcreate name of category here and a category will be made. In addition to this category, a channel will be made in it. This channel is to be used to place threads in that category. I have plans on improving this process but for now, that's how it is.

You will need the Manage Channel permissions to run this.


This will delete a thread. Only the owner or someone with Manage Channels can run this command. There is no confirmation for this command so be careful!


This the parent command for various guild-specific settings you can change. Below are all of the settings you can change:


You may use any prefix you desire. To do so, run .settings prefix new_prefix with new_prefix being the prefix you want to use. Trailing spaces are removed for this command.

You will need the Manage Guild permissions to run this.

Role Whitelisting

In some cases, it may be a good idea to limit who can make threads in your server. There is a feature built-in feature for this. By default, it is not enabled. Use .settings user_roles to enabled it.

After enabling, no one will be able to make threads because there are no roles specified. To add roles, run the command again but append the roles you want to add.

Example: .settings user_roles @Admins "Power User" Platinum

As you can see, you can add roles multiple ways. You can mention the role or type it out. Just be aware that if you type a role out, it must match exactly. It is case-sensitive. If a role has a space, you must enclose it in quotes. In the event you have two or more roles with the same name, you should mention the role instead of typing it out as typing it out can lead to the wrong role being added to the whitelist.

Once you add your roles, only those that have any of the defined roles can make threads. If you wish to remove a role, run the command again like above but mention/type the role you wish to remove. If you wish to disable this, run .settings user_roles and it will return to the state where everyone can make a thread.

You will need the Manage Guild permissions to run this command.

Admin Roles

Admins roles are roles that have the ability to bypass the cooldown if enabled. That's it. They don't get any other special priviledges. In the future, this may change. But the procedure to enable this and add/remove roles is exactly the same as Role Whitelisting with the exception being you do admin_roles instead of user_roles.

You will need the Manage Guild permissions to run this command.

Role Bypassing

Currently, this does nothing that admin_roles doesn't. This just toggles if admin roles can bypass the cooldown or not.

You will need the Manage Guild permissions to run this.

Inactivity Timer

By default, a thread is marked as inactive if no messages have been sent in the channel for 3 days. This setting maybe changed with .settings timetodead <number> where <number> is a whole number of days to wait. This can be any number you wish.

You will need the Manage Guild permissions to run this.


No sane person will change this. But if you are so inclined to do so, you may. Running .settings cleaning will toggle whether or not Threadstorm deletes messages used for thread creation. The default action is to delete setup messages.

You will need the Manage Guild permissions to run this.


Certain threads may be worth saving. If you feel a thread should be preserved, use .tkeep in the thread you want to preserve. Alternativly, you can run .tkeep #channel_mention anywhere to toggle the keep flag for that thread. In order to run this command, you must have Manage Channels permission.


This should never be used, but it's here in-case you need to use it. This command will essentially recreate the actions taken when Threadstorm joined your guild. This means any active threads that are being tracked by Threadstorm will be lost. Not deleted, but they wont automatically be cleaned up if they become inactive.


Pretty simple. This will post the most recent changes to Threadstorm in the invoked channel.


A command that is used to display all of your guilds settings excluding active threads. Useful to verify if settings are correct. This command requires you have the Manage Guild permission.