Custom Commands

Custom commands let you create your own prefix-triggered commands (like ?hello or !rank) that respond with dynamic text, embeds, reactions, direct messages and more. Every response is powered by TagScript — a small, easy-to-learn templating language. A response can be as simple as a line of plain text, or as advanced as a mini program with variables, conditions, randomness and math.

You never have to learn TagScript. The dashboard includes a visual, no-code builder that writes TagScript for you. This page documents the language itself so you can build anything you can imagine.

Creating a Command

Select Custom Commands from the sidebar and click Create Command.
Fill in the fields:

Name — the command word typed after the prefix, e.g. hello runs as ?hello. Stored in lowercase.
Aliases — optional alternative names that trigger the same command (e.g. rank, level, lvl).
Response — the TagScript that runs when the command is used. This is the heart of the command.

Save. Your command is live instantly.

A name or alias can only belong to one command per server. If you try to reuse a name that another command already owns, saving fails.

AI Command Assistant

The command editor includes an AI assistant powered by Gemini. Describe what the command should do in plain language, then select Generate. The result opens in TagScript mode so you can review and test it before saving. The assistant receives the same variables, functions and examples shown in the TagScript catalogue. MurFFy validates the generated response and rejects unknown or malformed tags before placing it in the editor. Each user can generate one command every seven days. Failed AI requests do not use the weekly generation. If the shared AI quota is unavailable, the editor shows a temporary service-unavailable message and you can try again later.

Prefixes

By default, custom commands are triggered with the ? prefix, so a command named hello runs as ?hello. You can change or add prefixes under Custom Commands → Settings. When several prefixes could match, the longest one wins (so !! is matched before !).

Plan	Prefixes	Commands
Free	1	5
Premium	3	25
Premium+	5	100

Prefixes cannot contain spaces.

How TagScript Works

Anything you type in the response is sent back as-is, except for tags wrapped in curly braces {}. Tags are replaced with real values or perform an action when the command runs. A tag has up to three parts:

Form	Example
`{name}`	`{user}`
`{name(parameter)}`	`{user(mention)}`
`{name:payload}`	`{upper:hello}`
`{name(parameter):payload}`	`{replace(cat,dog):my cat}`

Tags can be nested — the inside is resolved first:

{upper:{user(name)}}

If the user is named mafi, this outputs MAFI.

Some tags (called actions and restrictions, like {dm}, {delete} or {require}) don’t print anything — they change how the response is sent. They output nothing where you place them.

The Pipe `|`

Many tags use the pipe character | to separate several values or “branches”, for example the true/false branches of {if} or the options of {choose}. If you need a literal | in your text, escape it as \|.

Escaping Special Characters

To output a character that TagScript treats specially, put a backslash \ in front of it: \{, \}, \(, \), \|, \:, \\.

Use \{user\} to mention someone.

Output: Use {user} to mention someone.

Variables

Variables are replaced with information about the user, server, channel or the arguments they typed. Most accept a property in parentheses to pick exactly what you want.

Tag	Description
`{user}` (alias `{author}`)	The member who ran the command. Properties: `mention`, `id`, `name`, `tag`, `nick`, `avatar`, `created`, `joined`, `bot`. Default: username.
`{target}`	The first user mentioned in the arguments. Same properties as `{user}`.
`{server}` (alias `{guild}`)	The server. Properties: `name`, `id`, `membercount`, `icon`, `owner`, `ownerid`, `created`, `boosts`, `boostlevel`. Default: name.
`{channel}`	The current channel. Properties: `mention`, `id`, `name`. Default: mention.
`{args}` (alias `{message}`)	Everything typed after the command. `{args(n)}` returns the n-th word (1-based).
`{arg(n)}`	A single argument by position, e.g. `{arg(1)}`.
`{argcount}`	How many arguments were provided.
`{prefix}`	The prefix used to run the command.
`{command}` (alias `{cmd}`)	The name of the command that was run.
`{unix}` (alias `{timestamp}`)	The current Unix timestamp in seconds.
`{time}`	A Discord relative-time stamp for now. `{time(60)}` adds an offset in seconds.

Discord renders {user(created)}, {server(created)} and {time} as live timestamps that update automatically (e.g. “5 minutes ago”).

Examples

Hi {user(mention)}! You are member #{server(membercount)} of {server}.

{target(name)} was booped by {user(name)}!

Used as ?boop @friend.

This command was run in {channel(mention)} using the {prefix} prefix.

Conditionals & Logic

Make the response react to what the user typed.

`{if(condition):then|else}`

Outputs the first branch when the condition is true, and the branch after | when it is false (the else branch is optional). Conditions support the comparators ==, !=, >, <, >=, <=. Numbers are compared as numbers; anything else is compared as text. A condition with no comparator is true unless it is empty, false, 0, no or none.

{if({args}==hello):Hi there!|I only respond to "hello".}

You have {arg(1)} coins. {if({arg(1)}>=100):You're rich!|Keep saving.}

{if({args}):You said: {args}|You didn't say anything!}

Here the condition is simply whether any arguments were given.

Combining conditions

Tag	Description
`{and:a\|b\|c}`	True only if every value is truthy.
`{or:a\|b\|c}`	True if any value is truthy.
`{not:value}`	Inverts a truthy value.
`{contains(needle):haystack}`	True when the text contains the needle.
`{in(value):a\|b\|c}`	True when the value equals one of the options.

{if({and:{arg(1)}|{arg(2)}}):Both arguments given.|Please provide two arguments.}

{if({contains(discord.gg):{args}}):No invite links allowed!|}{if({contains(discord.gg):{args}}):{delete}|}

{if({in({lower:{arg(1)}}):yes|yep|sure|y}):Confirmed!|Cancelled.}

Utilities

Helpers for text, numbers and randomness.

Tag	Description
`{choose:a\|b\|c}` (alias `{random}`)	Randomly pick one of the options.
`{range:1-100}`	A random whole number between two values (inclusive).
`{math:2 + 2 * 3}` (alias `{calc}`)	Evaluate arithmetic: `+ - * / % ^` and parentheses.
`{len:text}`	Number of characters in the text.
`{lower:TEXT}`	Convert to lowercase.
`{upper:text}` (alias `{caps}`)	Convert to uppercase.
`{replace(find,replacement):text}`	Replace every occurrence of a substring.
`{substr(start,end):text}`	Extract part of the text (0-based; `end` is optional).
`{join(separator):a\|b\|c}`	Join the values with a separator.
`{url:text}`	URL-encode text (useful for building links).

Examples

🎲 You rolled a {range:1-6}!

The magic 8-ball says: {choose:Yes|No|Maybe|Ask again later|Definitely}

{arg(1)} × 1.23 = {math:{arg(1)} * 1.23}

Search Google: https://google.com/search?q={url:{args}}

{upper:{substr(0,1):{args}}}{substr(1):{args}}

Capitalises the first letter of whatever the user typed.

Custom Variables

Store a value once and reuse it, which keeps complex commands readable and avoids repeating expensive tags.

Tag	Description
`{=(name):value}` (aliases `{var}`, `{assign}`, `{let}`)	Store a value. Outputs nothing.
`{get(name)}` or `{name}`	Read the value back.

{=(points):{math:{arg(1)} * 10}}You earned {points} points! ({get(points)} total)

Variable names are stored in lowercase and only exist for the duration of a single command run.

Embeds

Build a rich embed by setting one property per {embed(...)} tag. All the tags in a response combine into a single embed.

Property	Purpose
`{embed(title):...}`	Title.
`{embed(description):...}`	Main body text (alias `desc`).
`{embed(color):...}`	Side color — a name, `#hex`, or a decimal number.
`{embed(url):...}`	Makes the title a clickable link.
`{embed(image):...}`	Large image (URL).
`{embed(thumbnail):...}`	Small top-right image (URL).
`{embed(footer):...}`	Footer text.
`{embed(author):...}`	Author line at the top.
`{embed(field):name\|value\|inline}`	Add a field. `inline` is `true`/`false` and optional. Repeat for more fields.

Named colors: red, green, blue, yellow, orange, purple, blurple, white, black, gold, pink, gray.

{embed(title):Welcome!}{embed(description):Hello {user(mention)}, glad to have you in {server}.}{embed(color):green}{embed(thumbnail):{user(avatar)}}

{embed(title):Server Stats}{embed(color):#5865f2}{embed(field):Members|{server(membercount)}|true}{embed(field):Boosts|{server(boosts)}|true}{embed(field):Owner|{server(owner)}|false}

{embed:some text} with no property is a shortcut that sets the description.

Economy

Economy tags connect a custom command to the server’s configured currencies and inventory. They only work while Economy is enabled for the server.

Reading balances and items

Tag	Description
`{economyenabled}`	Returns `true` or `false`. Alias: `{ecoenabled}`.
`{balance(account,currency,user,format)}`	Reads a balance. Defaults: `wallet`, default currency, `self`, `formatted`. Alias: `{ecobalance}`.
`{currency(property,currency)}`	Reads currency metadata. Alias: `{ecocurrency}`.
`{item(property,item)}`	Reads item metadata by its stable item key. Alias: `{ecoitem}`.
`{itemcount(item,user)}`	Number of copies owned. Alias: `{ecoitemcount}`.
`{hasitem(item,quantity,user)}`	Returns `true` when the user owns at least that quantity. Alias: `{ecohasitem}`.

The account in {balance} can be wallet, bank or total. Its output format can be:

formatted — exact amount with the configured currency symbol, such as 🪙 1,250;
decimal — display amount without the symbol, respecting the currency’s decimal places;
raw — integer base units stored by the ledger.

The user selector can be self, target, a Discord mention or a user ID. target means the first user mentioned in the command arguments. Currency properties: key, name, plural, symbol, decimals, transferable, tradable, bankable, maxwallet. Item properties: key, name, description, emoji, rarity, type, usable, tradable, sellable, giftable.

Wallet: {balance}
Bank: {balance(bank)}
Total raw units: {balance(total,coins,self,raw)}

{if({hasitem(golden-key,1)}):You can open the vault.|You need a {item(name,golden-key)}.}

Currency and item operations

Operations return true when they succeed and false when they cannot be completed. Put them inside {if} to show the correct response without guessing the result.

Tag	Description
`{econgrant(amount,cooldown,currency,bucket)}`	Grants currency to the user running the command. Alias: `{economygrant}`.
`{econcharge(amount,currency)}`	Charges the user through the economy ledger. Alias: `{economycharge}`.
`{econgrantitem(item,quantity,cooldown,bucket)}`	Grants an item to the user running the command. Alias: `{economygrantitem}`.
`{econconsumeitem(item,quantity)}`	Consumes an unlocked item owned by the user. Alias: `{economyconsumeitem}`.

currency is optional and defaults to the server’s default currency. A reward cooldown is mandatory and must be between 60 seconds and 7 days. The optional bucket lets several reward tags or commands share the same per-user cooldown.

Reward tags can only reward the member who runs the command. They cannot edit another member’s balance. Currency changes always pass through the double-entry ledger, while item changes respect supply, ownership and stack limits. Testing a command in the dashboard only reports what would happen and never changes balances or inventory. Separate economy tags are separate operations; use the built-in Shop when a payment and item delivery must be one atomic purchase.

{if({econgrant(100,86400,coins,daily-reward)}):You received 100 coins! Your balance is now {balance}.|You already claimed today's reward.}

{if({econcharge(50,coins)}):The secret clue is: look under the bridge.|You need 50 coins to reveal the clue.}

{if({econconsumeitem(vault-key,1)}):The vault opens! 🎁|You need a vault key.}

Actions

Actions change how the response is delivered. They print nothing where you write them, so you can place them anywhere in the response.

Tag	Description
`{dm:message}`	Send the payload to the user in DMs.
`{react:👍 🎉}`	React to the bot’s reply with one or more emojis (space-separated).
`{reactu:👀}`	React to the user’s command message.
`{delete}`	Delete the message that triggered the command.
`{deletein:10}`	Delete the bot’s reply after n seconds (max 300).
`{silent}`	Don’t send a channel reply (useful when the command only performs actions).
`{redirect:#channel}`	Send the reply to a different channel (mention, ID or name).
`{allowmentions}`	Allow the reply to actually ping roles and `@everyone`/`@here`.

For safety, replies never ping roles or @everyone unless you add {allowmentions}. A {user(mention)} still shows as a mention but won’t send a notification without it.

Thanks {user(name)}, check your DMs! {dm:Here is your secret info 🎁}

✅ Suggestion received.{reactu:👍}{reactu:👎}

This message will self-destruct in 5 seconds… {deletein:5}

Restrictions

Restrictions decide who and where a command can be used. If a restriction fails, the command stops. If you provide a reason, it is shown to the user; otherwise the command fails silently.

Tag	Description
`{require(reason):Role\|#channel}`	Only allow the listed roles and/or channels.
`{blacklist(reason):Role\|#channel}`	Block the listed roles and/or channels.
`{nsfw}`	Only allow the command in age-restricted (NSFW) channels.
`{cooldown(seconds,bucket):message}`	Per-user cooldown. The optional `bucket` shares a cooldown across commands; `message` is shown while on cooldown.

Roles and channels can be given as a mention (@Staff, #logs), an ID, or a plain name.

{require(This command is staff-only.):Moderator|Admin}🔒 Secret staff dashboard link: ...

{cooldown(30):⏳ Slow down! Try again in a bit.}You claimed your daily reward! 🎁

{blacklist(You are muted.):Muted}Your message: {args}

Worked Examples

Simple

Hello — a friendly greeting

Hello {user(mention)}, welcome to {server}! 👋

Coinflip

🪙 {user(name)} flipped **{choose:Heads|Tails}**!

Roll — a dice roll

🎲 You rolled a **{range:1-6}**.

Boop — mention another user

{if({target}):{user(mention)} booped {target(mention)}! 👉|You need to mention someone to boop.}

Used as ?boop @friend.

Avatar

{embed(title):{user(name)}'s avatar}{embed(image):{user(avatar)}}{embed(color):blurple}

Complex

8-ball with input validation

{if({args}):🎱 {user(name)} asks: *{args}*
The 8-ball says: **{choose:It is certain|Without a doubt|Yes|Ask again later|Don't count on it|My reply is no|Very doubtful}**|Please ask a question, e.g. `{prefix}{command} will it rain?`}

Only answers when a question is provided, otherwise explains how to use it.

Reward — math, variables and a cooldown

{=(amount):{range:50-200}}{if({econgrant({get(amount)},86400,coins,daily)}:{embed(title):Daily Reward 🎁}{embed(description):{user(mention)} claimed **{get(amount)}** coins! New balance: {balance}.}{embed(color):gold}{embed(footer):Come back tomorrow for more.}|⏳ You already claimed your daily reward.}

Rolls a random reward, records it through the economy ledger, and enforces a one-day per-user reward cooldown in the shared daily bucket.

Staff announcement to another channel

{require(Only staff can announce.):Moderator|Admin}{redirect:#announcements}{allowmentions}{embed(title):📢 Announcement}{embed(description):{args}}{embed(color):red}{embed(author):{user(name)}}{silent}

Restricts to staff, posts the embed into #announcements (with pings enabled), and stays silent in the channel where it was typed.

Suggestion box with reactions

{if({args}):{redirect:#suggestions}{embed(description):{args}}{embed(author):Suggested by {user(name)}}{embed(color):blue}{react:👍}{react:👎}{delete}|Please include your suggestion: `{prefix}{command} <idea>`}

Deletes the trigger, reposts the suggestion as an embed in #suggestions, and adds vote reactions.

Tier lookup with nested conditions

{=(coins):{arg(1)}}{embed(title):Rank for {user(name)}}{embed(description):You have **{get(coins)}** coins.
Tier: **{if({get(coins)}>=1000):💎 Diamond|{if({get(coins)}>=500):🥇 Gold|{if({get(coins)}>=100):🥈 Silver|🥉 Bronze}}}**}{embed(color):{if({get(coins)}>=1000):blue|gold}}

Uses nested {if} tags to pick a tier and a matching color from a number.

Good to Know

Responses are limited to 2000 characters (Discord’s message limit). Longer output is trimmed.
A single command has an execution budget (a maximum number of tags and nesting depth) to keep things fast — normal commands never come close to it.
If a tag can’t be resolved, it is shown back as plain text so you can spot the typo.
Custom commands respect the Allowed / Ignored roles and channels you set on the command itself, in addition to any {require} / {blacklist} tags in the response.

Test a command safely from the dashboard before going live — the Test button renders the response (including embeds) without actually sending anything to Discord.

Overview

Server configuration

Custom Commands

Custom Commands

Creating a Command

AI Command Assistant

Prefixes

How TagScript Works

The Pipe `|`

Escaping Special Characters

Variables

Conditionals & Logic

`{if(condition):then|else}`

Combining conditions

Utilities

Custom Variables

Embeds

Economy

Reading balances and items

Currency and item operations

Actions

Restrictions

Worked Examples

Simple

Complex

Good to Know

​Custom Commands

​Creating a Command

​AI Command Assistant

​Prefixes

​How TagScript Works

​The Pipe |

​Escaping Special Characters

​Variables

​Conditionals & Logic

​{if(condition):then|else}

​Combining conditions

​Utilities

​Custom Variables

​Embeds

​Economy

​Reading balances and items

​Currency and item operations

​Actions

​Restrictions

​Worked Examples

​Simple

​Complex

​Good to Know

Custom Commands

Creating a Command

AI Command Assistant

Prefixes

How TagScript Works

The Pipe `|`

Escaping Special Characters

Variables

Conditionals & Logic

`{if(condition):then|else}`

Combining conditions

Utilities

Custom Variables

Embeds

Economy

Reading balances and items

Currency and item operations

Actions

Restrictions

Worked Examples

Simple

Complex

Good to Know