Skip to content

Auto-Thread

Auto-Thread keeps your channels organised by letting Aleeva create a new thread for every message in specific channels. This lets you effortlessly set up ticketing systems, LFGs and help desks, with a new thread generated for every new message in the channels you choose.

How it works

By default, Aleeva adds two buttons to the message in the thread, which allow the initial message sender to archive the thread or change its name. The initial message sender does not need any special permissions to do this. Only the initial message sender and users with the Manage Threads permission are allowed to use these buttons.

Setup

To enable this feature and change its configuration, add it to the topic of the channel you want it for. You configure it by adding the corresponding settings to the text. A semicolon separates single settings. To enable Auto-Thread, add the following to the channel topic:

{#auto-thread:}

Settings

name

Defines the title of the thread. This can also contain placeholders, which Aleeva replaces during creation.

Examples:

{#auto-thread:name=Let's talk here.}
{#auto-thread:name=%nickname% - %date%}
{#auto-thread:name=%content-20%}
{#auto-thread:name=Join %gw2-account%}

Available placeholders:

  • %nickname% : the nickname of the message sender
  • %date% : the current date
  • %gw2-account% : the GW2 account name of the sender
  • %content-10% : the first 10 characters of the message content

If you do not set a name, Aleeva uses the first 50 characters of the message.

allowArchive, archiveName and archiveColor

Defines whether the archive button is shown (allowArchive), which name it has (archiveName) and which colour it has (archiveColor).

Examples:

{#auto-thread:allowArchive=false}
{#auto-thread:archiveName=Close this LFG;archiveColor=red}
  • allowArchive : by default this is true, which means the button is shown. If set to false, Aleeva does not show the button.
  • archiveName : the name of the button can have up to 80 characters. By default the name is "Archive thread".
  • archiveColor : the colour of the button is green by default. Possible colours: green, blurple, grey, red.

allowEdit and editColor

Defines whether the button for editing the title is shown (allowEdit) and which colour it has (editColor).

Examples:

{#auto-thread:allowEdit=false}
{#auto-thread:editColor=red}
  • allowEdit : by default this is true, which means the button is shown. If set to false, Aleeva does not show the button.
  • editColor : the colour of the button is blurple by default. Possible colours: green, blurple, grey, red.

archiveMode

Defines what should happen when Aleeva archives a thread. By default, the thread is archived (closed).

Examples:

{#auto-thread:archiveMode=deleteEmpty}
{#auto-thread:archiveMode=delete}
{#auto-thread:archiveMode=lock}
  • archive : archives the thread (default)
  • deleteEmpty : deletes the thread if no messages were sent
  • delete : always deletes the thread
  • lock : locks the thread

archiveAction

Defines whether to archive the thread immediately or after 1 hour. This setting is only relevant if archiveMode is set to archive. By default, the thread is archived immediately.

Examples:

{#auto-thread:archiveAction=instant}
{#auto-thread:archiveAction=timeout}

archiveAfter

Defines the auto-archive duration Discord applies to the newly created thread, after which Discord hides it from the active thread list. By default this is 24 hours.

Examples:

{#auto-thread:archiveAfter=1w}
  • 1h : one hour
  • 24h : one day (default)
  • 3d : three days
  • 1w : one week

deleteMode

Defines what should happen when the original message gets deleted. By default, the thread is deleted if no message was sent to it, otherwise nothing happens.

Examples:

{#auto-thread:deleteMode=lock}
{#auto-thread:deleteMode=nothing}
{#auto-thread:deleteMode=archive}
  • deleteEmpty : deletes the thread if empty, otherwise does nothing (default)
  • nothing : does nothing
  • archive : archives the thread
  • lock : locks the thread
  • delete : deletes the thread

startsWith, endsWith and matchEmote

By default Aleeva creates a thread for every message in the channel. These settings limit thread creation to messages that match a condition. If a message does not match, no thread is created.

Examples:

{#auto-thread:startsWith=LFG}
{#auto-thread:endsWith=?}
{#auto-thread:matchEmote=✅,<:custom:123456789>}
{#auto-thread:startsWith=Ticket;caseSensitive=true}
  • startsWith : only create a thread when the message starts with this text.
  • endsWith : only create a thread when the message ends with this text.
  • caseSensitive : whether startsWith and endsWith compare upper and lower case exactly. False by default.
  • matchEmote : a comma-separated list of emotes. Aleeva only creates a thread when the message contains at least one of them. You can use a standard emoji, a custom emote (<:name:id>) or a custom emote ID.