}`
{% hint style="warning" %}
if using an item name in the variable, the name must be **exact.** for example, if I have an item named "chocolate chip cookie", the variable must be `{modifyinv: chocolate chip cookie | 1}`, not `{modifyinv: cookie | 1}` or any other variants. for this reason, we always recommend using the item's ID option.
{% endhint %}
* notice: the user option is *optional.* you must have an item name/ID and quantity in the variable when using it.
## ✎ what does this have to do with user arguments?
* you're probably thinking, "oookay, so why is this more advanced?"
* the concept in practice can get very tricky for beginners, especially as we introduce user arguments.
* let's say I want to make a command called `.shake tree` that requires another user. this command will give an item for both users\
`/autoresponder add trigger:.shake trees reply:{requirearg: 1 | user}{range:2-10}{embed}{modifyinv: coconut | 1}{modifyinv: coconut | 1 | [$1]} you shook a tree . . . [range] coconuts fell out! you each took one and stashed it in your inventory.`\
\
`/autoresponder editmatchmode trigger:.shake trees matchmode:startswith`
the command after use
the button at the bottom of /balance
you must have an emoji or a label
button colors that are available - these colors are preset by discord and cannot be a custom hex code.
creating a button responder
here's the result!
blue role button!
yellow role button!
creating the embed
our role panel working in action!
limited buttonresponder limitation
strict buttonresponder limitations
variable example description variable example description {user}@iara the user's @mention {user_tag}iara the user's username and tag {user_name}iara the user's username {user_avatar}https://cdn.discordapp.com the user's avatar {user_discrim}0 the user's discriminator (the numbers after your username) {user_id}395526710101278721 the user's id {user_nick}iara c: the member's nickname in the server, if applicable {user_joindate}Wed, Aug 15, 2018 2:32 AM the date of when the member joined the server {user_createdate}Wed, Dec 27, 2017 10:41 AM the date of when the user joined discord {user_displaycolor}#ffdfdf the member's hex color when chatting {user_boostsince}Wed, Mar 17, 2021 7:13 PM the date the member has been boosting the server since (if they're not a booster, it'll say "Not a Booster") {user_balance}21983 the member's balance {user_balance_locale}21,983 the member's balance but with locale (comma separator) {user_item:}{user_item:apple} = 1 × appleshows the user's quantity & name of a specified item {user_item_count:}{user_item_count:apple} = 1shows the quantity of a specified item {user_inventory}1 × apple shows the user's entire inventory
### ♪ server general information
| variable | example | description |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------ |
| `{server_name}` | = m i m u = | the server's name |
| `{server_id}` | 479115079338557469 | the server's id |
| `{server_membercount}` | 407 | the server's member count |
| `{server_membercount_ordinal}` | 203rd | the ordinal number of the member count |
| `{server_membercount_nobots}` | 400 | the server's member count, but without bots\* |
| `{server_membercount_nobots_ordinal}` | 309th | the ordinal number of the server's member count without bots\* |
| `{server_botcount}` | 7 | the server's bot count\* |
| `{server_botcount_ordinal}` | 2nd | the ordinal number of the server's bot count\* |
| `{server_icon}` |
| the server's icon |
| `{server_rolecount}` | 40 | the server's role count |
| `{server_channelcount}` | 20 | the server's channel count (includes all types of channels) |
| `{server_randommember}` | @iara | the @mention of a random member of your server\*\* |
| `{server_randommember_tag}` | iara | the user and tag of a random member of your server\*\*
|
| `{server_randommember_nobots}` | @iara | the @mention of a random member (that is not a bot) of your server\*\* |
| `{server_owner}` | @iara | the @mention of the server owner |
| `{server_owner_id}` | 395526710101278721 | the user id of the server owner |
| `{server_createdate}` | Wed, Dec 27, 2017 10:41 AM | the date the server was
created on
|
\* = due to discord's constraints with intents, the numbers of bots / without bots can be unreliable since october 2020. this is a result of not being able to cache every bot without caching all members in your server. servers with **premium** are equipped with premium caching to bypass these restraints.
\*\* = due to discord's constraints with intents, random member variables only consists of cached members (usually members who are active in your chat). servers with **premium** are equipped with premium caching to bypass these restraints.
### ♪ server boost information
| variable | example | description |
| ---------------------------------------- | ------- | ------------------------------------------------------------------------------ |
| `{server_boostlevel}` | 2 | the boost level, from 0 to 3, of the server |
| `{server_boostcount}` | 7 | the number of boosts the server has |
| `{server_nextboostlevel}` | 3 | the boost level the server is heading towards.\* |
| `{server_nextboostlevel_required}` | 14 | the number of boosts needed in total to reach the next boost level.\* |
| `{server_nextboostlevel_until_required}` | 7 | the number of boosts the server needs in order to reach the next boost level\* |
\* = returns "Max Level Reached" if it's already at level 3.
### ♪ server settings' information
| variable | example | description |
| ------------------- | ------- | ------------------------------------------------------------------------------------------------------ |
| `{server_prefix}` | / | the server's prefix -- globally, mimu uses slash (/) commands, so this variable will always return "/" |
| `{server_currency}` | 🍪 | the server's currency |
### ♪ channel information
| variable | example | description |
| ---------------------- | ------------------------- | ---------------------------------------- |
| `{channel}` | #general | the mention of the channel |
| `{channel_name}` | media | the name of the channel |
| `{channel_createdate}` | Sun, Dec 27, 2020 3:11 AM | the date of when the channel was created |
### ♪ message information
| variable | example | description |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `{message_id}` | 8832493284932843t | the id of the message that triggered the autoresponder |
| `{message_content}` | hi! i'm new! | the content of the message that triggered the autoresponder. pro-tip! it's the same as \[$1+], but with the trigger.
|
| `{message_link}` |
| the link to the message that triggered the autoresponder. |
### ♪ misc
| variable | example | description |
| ----------- | ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `{date}` | Tue, April 27, 2021 10:41 AM | the date, now. |
| `{newline}` | text line one
| adds a new line. note: this only works with `/embed edit` and `/autoresponder add/editreply` commands due to discord's limitation on new lines within slash commands. |
### ♪ unique / situational
these refer to variables that only work in special situations.
variable example usable in... description {pick_code}j0yZ pick message the code to /pick with. only valid if pickhard is on. {pick_amount}31 pick message the amount the /pick gives. if your picktype is multiple then it will say "handful of currency" instead.
### ♪ advanced placeholders
there are no examples for these because this depends on either user input, or something else, and could **simply be anything**.
{% hint style="info" %}
there are no examples for these because this depends on either user input, or defined elsewhere in your autoresponder. this can be simply anything.
for information on using this, please view intermediate guides on[ ranges and making choices](/autoresponder/guide/intermediate-i-ranges-and-making-choices), [locked choices](/autoresponder/guide/intermediate-ii-locked-choices), as well as advanced guides on [different matchmodes](/autoresponder/guide/advanced-i-different-matchmodes) and using [user arguments](/autoresponder/guide/advanced-ii-using-user-arguments).
{% endhint %}
| variable | description |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `[range]` | the range response made from the range in the {range:} function. |
| `[choice]` | the choice made from the chosen list in the `{choose:}` function. |
| `[lockedchoice]` | the corresponding locked choice made from `{lockedchoose:}` function |
| `[$N]` | the Nth argument/word used to trigger the autoresponder send by the user. only applicable for modes of autoresponder that is not`exact.` |
| `[$N+]` | the Nth word and words after that was used to trigger the autoresponder send by the user. only applicable for modes of autoresponder that is not`exact.` |
| `[$N-Z]` | the Nth to Zth words / arguments used to trigger the autoresponder send by the user. only applicable for modes of autoresponder that is not`exact.` |
## ✎ function list
{% hint style="info" %}
completely lost? check out our beginner guide on [using simple functions](/autoresponder/guide/beginner-ii-using-simple-functions).
{% endhint %}
### ♪ formatting and redirecting
| `{dm}` | `{dm}` | redirects the response to be in dms. |
| ----------- | ----------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `{sendto:}` | `{sendto:#general}` | redirects the response to the channel specified. by default, it is the channel the autoresponder is invoked in. |
| `{embed:}` | {embed}{embed:#ffffff}{embed:embed\_name}
| turns the reply to an embed. if input is provided, then you can put in a hex color, or a premade custom embed from the `/embed` command. |
| `{silent:}` | {silent}{silent: u cant use dis!}
| allows you to silent long-form errors, like permission errors and \[$N] argument related errors. this isn't an exhaustive list, but it silents a majority.
|
### ♪ auto-deletions
| variable | usage | description |
| ----------------- | ------------------- | -------------------------------------------------------- |
| `{delete}` | `{delete}` | delete's the triggering message to the autoresponder |
| `{delete_reply:}` | `{delete_reply:10}` | deletes the bot's reply after a given number of seconds. |
### ♪ limit autoresponder permission
{% hint style="info" %}
you can enable this to multiple users / permissions / roles / channels etc. by putting multiple function variables in your autoresponder.
{% endhint %}
| variable | usage | description | | | |
| ------------------- | -------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `{requireuser:}` | {requireuser:iara#0001}{requireuser:395526710101278721}
| limit the autoresponder to only respond to a specified user. | | | |
| `{requireperm:}` | `{requireperm:manage_server}` | limit the autoresponder to only respond if they have specified permission | | | |
| `{requirechannel:}` | {requirechannel:#general}{requirechannel:598897082450968617}
| limit the autoresponder to only respond if it's ran in specified channel | | | |
| `{requirerole:}` | `{requirerole:@mods} {requirerole:484312842821173250}` | limit the autoresponder to only respond if the user has the specified role
if the user does not have the specified role, it replies stating that they need specific roles
| | | |
| `{denychannel:}` | {denychannel:#general}
{denychannel:693258562603843707}
| ignores the autoresponder trigger when run in the specified channel | | | |
| `{denyperm:}` | {denyperm:Manage Roles}
{denyperm:Manage\_Messages}
| ignores the autoresponder trigger when the user has the specified permission | | | |
| `{denyrole:}` | {denyrole:@mischevious}
{denyrole:693486619751350293}
| ignores the autoresponder trigger when the user has the specified role | | | |
| `{requirebal:}` | {requirebal:100}{requirebal: 100 | iara}
| requires the user’s balance to be at least the specified amount. | | |
| `{requireitem:}` | {requireitem:apple}{requireitem: apple | 3}{requireitem: apple | 3 | \[$1]}
| requires an item in the user's inventory with the option to require an amount of an item as well as a user
|
### ♪ misc
\| `{modifybal:}` | {modifybal:+1000}
{modifybal:+1000}
{modifybal:=10000}
{modifybal:\*2}
{modifybal:/3}
{modifybal:+1000 | iara#0001}
{modifybal:-1000 | iara#0001}
{modifybal:=10000 | iara#0001}
{modifybal:*2 | iara#0001}
{modifybal:/3 | iara#0001}
{modifybal:+1000 | \[$1]}
| adds, removes, sets, divides, or multiplies from user balance.
supports the following simple math functions:+ adds specified amount to existing balance
- subtracts specified amount to existing balance
= sets balance to be that specified amount
* multiplies the existing balance by specified amount
/ divides the existing balance by specified amount
|
\| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
\| `{modifyinv:}` | {modifyinv: apple | 2}{modifyinv: 53ab4795-d628-467d-bc59-20252a1d55bc | -2}{modifyinv: apple | 2 | \[$1]}{modifyinv: apple | -2 | iara}
| adds or removes a specified amount of an inventory item from a user's /balance with an optional user argumentpremium servers , where it is 1,000,000,000.
+ adds specified item amount to existing inventory
- subtracts specified item amount to existing inventory/shop add - it will not reduce your amount of stock.
|
\| `{cooldown:}` | `{cooldown:600}` | sets a cooldown for the autoresponder to be ran in, in seconds. |
\| `{addrole:}` | {addrole:@cool kids}
{addrole:@verified | iara#0001}
{addrole:@verified | \[$1]}
| adds role to the user.
optionally, you can add roles to other users, too, if you add the optional argument "user" after the pipe |.
|
\| `{removerole:}` | {removerole:@cool kids}
{removerole:@muted | iara#0001}
{removerole:@muted | \[$1]}
| removes role from the user.
optionally, you can remove roles to other users, too, if you add the optional argument "user" after the pipe |.
|
\| `{setnick:}` | {setnick:a real cutie}
{setnick:i love {user\_nick}!}
{setnick: iawa | iara#0001}
{setnick: appropriate name | \[$1]}
| edits the user’s nickname in the server.
optionally, you can change other users’ nicknames, too, if you add the optional argument “user” after the pipe |
|
\| `{react:}` | `{react::pancakes:}` | reacts the emoji to the triggering message to the autoresponder |
\| `{reactreply:}` | `{reactreply::cute_dance:}` | reacts the emoji to the bot reply |
\| `{addbutton:}` | `{addbutton:clickie}` | adds a button to the desired trigger (ie. greet / leave / boost, autoresponders). make these with `/buttonresponder add`. |
\| `{addlinkbutton:}` | `{addlinkbutton: press me to go to the website! \| https://mimu.bot}` | adds a link-style button |
### ♪ advanced functions
{% hint style="info" %}
using these functions can be pretty difficult! read up on our intermediate section on [ranges and making choices](/autoresponder/guide/intermediate-i-ranges-and-making-choices), as well as [locked choices](/autoresponder/guide/intermediate-ii-locked-choices), to fully understand.\
\
for using arguments, read the [advanced ii: using user arguments](/autoresponder/guide/advanced-ii-using-user-arguments) guide.
{% endhint %}
| variable | description | | | | | | | | | | |
| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | --- | --------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ | - | - | - | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `{range:}` | chooses a value between a minimum and maximum, separated with `-`. (e.g. `{range:1-10}`). supports up to 4 ranges, you can reference these in your autoresponder via `[range] [range1] [range2] [range3]`, also mentioned in [advanced placeholders](/autoresponder/resources/variables-placeholders-and-functions#advanced-placeholders). | | | | | | | | | | |
| `{choose:}` | chooses from a provided list of choices that are separated by the pipe | symbol. supports up to 4 choices, {choose:} {choose1:} {choose2:} {choose3:}.\[choice] \[choice1] \[choice2] \[choice3], also mentioned in advanced placeholders .
| | | | | | | | | |
| `{weightedchoose:}` | {choose:} list. the order should match.
for example, for
{choose: apple | banana | orange} if {weightedchoose: 20% | 50% | 30%} was set, \[choice] would have a 20% chance of being apple, 50% chance of being banana and 30% being orange.
| | | | | | |
| `{lockedchoose:}` | "locks" or "forces" a choice to happen based on a corresponding {choose:} decision. the order of the \[choice] found in the {choose:} corresponds to the order of the \[lockedchoice] found in the {lockedchoose:}. {choose:x | y | z | a | b | c}, then n MUST be chosen from {lockedchoose1:k | r | m | n | o | p}. this is because a is the 4th option which was chosen, and n is the 4th option.
\[lockedchoice] \[lockedchoice1] \[lockedchoice2] \[lockedchoice3], also mentioned in advanced placeholders .
|
| `{requirearg:}` | requires an argument to be specified so you can refer to them properly in the \[$N] placeholder. you can put the number of the argument in. for example, {requirearg:1}
optionally takes an input type after the pipe | symbol, which forces the user to follow that type, e.g. {requirearg:2 | number}. the types supported are user, channel, color, role and number.
| | | | | | | | |
# examples
attached to this page are various different premade autoresponder commands for you to take inspiration or add to your server!
### quick links
* [custom currency command examples](/autoresponder/resources/autoresponder-examples/custom-currency-command-examples)
* [manager/moderation commands](/autoresponder/resources/autoresponder-examples/manager-moderation-commands)
* [utility/fun commands](/autoresponder/resources/autoresponder-examples/utility-fun-commands)
# custom currency command examples
included in our documentation are various guides/premade commands for you to easily implement into your server!
the guides progress from easy to make commands into harder, more complex commands.
# .bake command
*this command utilizes basic variables and gives a sweet currency command for your server members to use!*
### ✎ autoresponder command
`/autoresponder add trigger:.bake reply:{range:200-1000} {choose: cookies :cookies: | cupcake :cupcake: | pie :pie: | cake :cake:} {choose1: they loved it ! | they nommed happily c: | they love you for being so thoughtful !}{modifybal:[range]} you bake a [choice] for {server_randommember} . . .` \
`[choice1] and gave you [range] ! <3`\
`your balance is now {user_balance_locale} {server_currency} ^-^`
{% hint style="info" %}
confused about the variables used? see our variables guide [here](/autoresponder/resources/variables-placeholders-and-functions)
{% endhint %}
# .bake command with items
*this command utilizes shop items and the modifyinventory feature, making your bake commands more accurate. this replaces the previous bake command, shown on the previous page.*
### ✎ add your shop items
`/shop add name: milk price:10 stock:0`
`/shop add name: wheat price:15 stock:0`
`/shop add name: egg price:5 stock:0`
### ✎ autoresponder command
`/autoresponder add trigger:.bake reply:{requireitem: milk | 3}{requireitem:wheat | 5}{requireitem:egg | 3}{modifyinv: milk | -3}{modifyinv:wheat | -5}{modifyinv:egg | -3}{range:10-25}{range1:25-40}{choose:[range]|[range1]}{modifybal:[choice]}{embed} with the ingredients in your inventory, you decided to make a cake! you sold it, earning [choice] {server_currency}!`
for help with understanding how modifyinv works, please view the following guide:
{% content-ref url="/pages/2733RFaz4LDz4rl4MMtP" %}
[advanced iii: modifying inventory and using args](/autoresponder/guide/advanced-iii-modifying-inventory-and-using-args)
{% endcontent-ref %}
# .harvest command
*in this command, we've made it so that some fruits cost more than certain fruits. you can refer to below table for the pricing it can be sold for:*
fruit price fruit price bananas 10 apples 20 strawberries 30 oranges 25 pears 15
### ✎ autoresponder command
`/autoresponder add trigger:.harvest reply:{choose:bananas|apples|strawberries|oranges|pears} {lockedchoose:10|20|30|25|15} {modifybal:+[lockedchoice]} you have harvested some [choice] . . . and earned [lockedchoice] {server_currency}!`
{% hint style="info" %}
confused about the variables used? see our variables guide [here](/autoresponder/resources/variables-placeholders-and-functions)
{% endhint %}
# .stealcookie command
*server members can playfully interact with mimu in this steal cookie command!*
### ✎ autoresponder command
`/autoresponder add trigger:.stealcookie reply:{embed} {cooldown:1000} {choose1: You were caught by mimu for trying to steal some cookies from the cookie jar! >:( mimu took away 200 | You stole some cookies successfully! Nom nom nom~ you earned 50 | but mimu caught you and isn't happy <:angerybean:678534873828556810> ! mimu took away 300 | You stole the whole cookie jar and got away with it! Hurray!! You earned 500 } {lockedchoose1: -200 | 50 | -300 | 500} {modifybal:[lockedchoice1]} **You tried to take some cookies from the cookie jar . . .** [choice1] {server_currency} your balance is now {user_balance_locale} {server_currency} !`
{% hint style="info" %}
confused about the variables used? see our variables guide [here](/autoresponder/resources/variables-placeholders-and-functions)
{% endhint %}
# .crime command
*allow your server members to get into some trouble with this custom command example c:*
### ✎ autoresponder command
`/autoresponder add trigger:.crime reply:{cooldown:6000} {choose: you robbed a bank and earned 10000 {server_currency} | you stole 200 {server_currency} from someone at a restaurant! | you pickpocketed with great stealth but only picked up 50 {server_currency}. | you tried to steal from someone, but you accidentally dropped 600 {server_currency} as you ran away.} {lockedchoose:+10000 | +200 | +50 | -600} {modifybal:[lockedchoice]} . . . let's commit a crime . . . [choice] !`\
`now you have {user_balance} balance.`
{% hint style="info" %}
confused about the variables used? see our variables guide [here](/autoresponder/resources/variables-placeholders-and-functions)
{% endhint %}
# .steal \[user] \[amount] command
*this example uses our more complex variables, diving into user arguments with choices/locked choices!*
### ✎ autoresponder command
`/autoresponder add trigger:.steal reply:{requirearg:1|user} {requirearg:2|number}`\
`{choose:-[$2]|0|[$2]} {lockedchoose:you tried to steal money from [$1] but failed and ended up losing [$2] {server_currency} instead! :notsopog: | you tried to steal money from [$1] but didn't earn any {server_currency}! oops. | you tried to steal money from [$1] and was able to steal [$2] {server_currency} :pog:} {modifybal:-[choice] | [$1]} {modifybal:[choice]}`\
\
`[lockedchoice]`
`/autoresponder editmatchmode trigger:.steal reply:startswith`
the functioning .steal command
).
* then, make a role that can't view the rest of the server and remember to set up all the channels so that this particular role cannot view the rest of the server, but can still view your rules / landing channel!
* confused on how to set up permissions? check out the [template we've prepared](https://discord.new/JBKDfcGeRMhK). it includes 2 main roles (mod & verified member role), 4 main categories (info - everyone can see, verify category - unverified can see, main chat - verified can see, and mod corner category - only mod can see).
# click a button to verify
{% hint style="info" %}
please make sure you have set up the verified role (instructions can be found in [self-verification system](/autoresponder/resources/autoresponder-examples/manager-moderation-commands/self-verification-system))
for typing "i agree" or ".verify" commands, please read [type "i agree" to verify](/autoresponder/resources/autoresponder-examples/manager-moderation-commands/self-verification-system/type-i-agree-to-verify)
{% endhint %}
### use a button responder and /send command
1. create a button responder:
`/buttonresponder add name:verify label:click to verify color:green reply:{addrole: read n agreed to rules}{embed:#ceb3af}hello {user} ~ thank you for agreeing to the rules of in {server_name} ! you have gained access to the rest of our server ^-^ we hope you enjoy your stay!`
> `{addrole:}` - adds the specified role in the brackets; this should refer to the verified role that gives the permission
> `{embed}` - would make it embed with the default embed color of the server; in this case to customise the color, we used {embed:#ceb3af} instead.
>
> *you can also link a premade embed with `{embed:embed_name_here}`. more information on embeds can be found in the guide:* [*your first embed*](/embeds/your-first-embed)*.*
***note**: you can also use the `{dm}` variable - but buttons respond ephemerally (only to the user in the channel, and never have permission issues) so it is recommended not to for buttons.*
2. send instructions and button to the rules channel:
`/send channel:#rules content:{addbutton:verify}{embed} click the button below to verify !`
> `{addbutton:}` - attaches a button (with the name of the button in the brackets) to the message.
# type "i agree" to verify
{% hint style="info" %}
please make sure you have set up the verified role (instructions can be found in [self-verification system](/autoresponder/resources/autoresponder-examples/manager-moderation-commands/self-verification-system))
for setting up button-style verify, check out [click a button to verify](/autoresponder/resources/autoresponder-examples/manager-moderation-commands/self-verification-system/click-a-button-to-verify)
{% endhint %}
### message autoresponder (users type 'i agree' or '.verify' to verify)
1. at the end of your rules, we suggest typing something like "type `i agree` to gain access to the rest of the server \~ !" to guide new members joining your server.
2. create an autoresponder with `i agree` or `.verify`
`/autoresponder add trigger:i agree reply:{dm}{delete}{embed:#ceb3af}{addrole: read n agreed to rules}hi ! thank you for agreeing to the rules of our server, {user}! you have gained access to the rest of the server.`
> `{dm}` - makes it dm the user instead, so it doesn't clog up your channel
> `{delete}` - makes it autodelete the invoked autoresponder
> `{embed}` - would make it embed with the default embed color of the server; in this case to customise the color, we used {embed:#ceb3af} instead
>
> *you can also link a premade embed with `{embed:embed_name_here}`. more information on embeds can be found in the guide:* [*your first embed*](/embeds/your-first-embed)*.*
> `{addrole:}` adds the specified role in the brackets, this is the verified role the remaining text is the message in the embed you're sending to them
> `{requirechannel:}` - optionally, you can add `{requirechannel:#verify}` to limit the autoresponder to be done in the verification channel, so people cannot run this AR elsewhere.
# manual verification system
### ✎ .verify \[user] (manual verification) command
* this command is useful for servers with "gates" to them, where some "gatekeepers" can manually verify the user after they have posted a valid introduction or some other form of verification requirement.
`/autoresponder add trigger:.verify reply:{requirearg:1|user} {requirerole:gatekeepers} {delete} {addrole:verified | [$1]}{embed} verified [$1]!`
`/autoresponder editmatchmode trigger:.verify matchmode:startswith`
* you can also have it so that once the user is verified, it sends a premade embed that greets the user in the chat channel, so that they get notified:
`/autoresponder add trigger:.verify reply:{requirearg:1|user} {requirerole:gatekeepers} {delete} {addrole:verified | [$1]} {sendto: #general} [$1] {embed:greet}`
# self assignable roles
## 3 types of self-assignable roles available:
### **1. button roles:**
allows the user to select roles from a roles channel.
button roles example
command roles example
command x button roles example
the roles created within your server's roles
an example with color roles
expanded add roles
expanded remove roles
the functioning self assignable roles
user-activated roles menu
the .roleadd command
the message written that triggers mimu to delete it based on the autoresponder
mimu's response after deleting the message c:
the completed disable pings example
disable partner pings role creation
it should look like this
the command in completion
the completed send command
basic .say command
an embedded say
the completed command
the completed hug command
a role you provided is not valid or could not be found in the server. this usually happens if:
the role id / mention / name is wrong the role was deleted mimu can’t resolve it from the text you typed the permission name you provided is not a valid discord permission.ADMINSTRATOR instead of ADMINISTRATOR.
| `{requireperm:}` / `{denyperm:}` | | | |
| `CHANNEL_ERROR`: `INVALID_CHANNEL` | the autoresponder is used in a channel *not* listed in `{requirechannel:}` | `{requirechannel:}` | | | |
| `CHANNEL_ERROR`: `DENIED_CHANNEL` | the autoresponder is used in a channel listed in `{denychannel:}` | `{denychannel:}` | | | |
| `USER_ERROR`: `REQUIRED_USER_MISMATCH` | the invoking user is *not* listed in `{requireuser:}` | `{requireuser:}` | | | |
| `USER_ERROR`: `DENIED_USER` | the invoking user *is* listed in `{denyuser:}` | `{denyuser:}` | | | |
| `ROLE_ERROR`: `DENIED_ROLES` | the member has a role listed in `{denyrole:}` | `{denyrole:}` | | | |
| `PERMISSION_ERROR`: `INSUFFICIENT_PERMISSIONS` | the member does *not* have the permissions listed in `{requireperm:}` | `{requireperm:}` | | | |
| `PERMISSION_ERROR`: `DENIED_PERMISSIONS` | the member *has* a permission listed in `{denyperm:}` | `{denyperm:}` | | | |
| `ITEM_ERROR`: `DENIED_ITEM` | the user has an item or amount blocked by `{denyitem:}` | `{denyitem:}` | | | |
| `CHANNEL_ERROR` : `INVALID_CHANNEL` | the channel you provided is invalid or could not be found in the server. this can happen if:
the channel id / mention / name is wrong the channel was deleted mimu doesn’t have access to see that channel the user you provided is invalid or could not be found in the server. this can happen if:
you typed an id / mention that doesn’t exist the user left the server mimu can’t resolve the input text to a member
INVALID\_USER\_DENYUSER
| you used `{denyuser:user\|not_valid_user}` but the not\_valid\_user isn't valid. | `{denyperm:}` | | | |
| `INVALID_USER_REQPERM` | you used `{requireperm:user\|not_valid_user}` but the not\_valid\_user isn't valid. | `{requireperm:}` | | | |
| `INVALID_USER_DENYPERM` | you used `{denyperm:user\|not_valid_user}` but the not\_valid\_user isn't valid. | `{denyperm:}` | | | |
| `INVALID_USER_REQROLE` | you used `{requirerole:user\|not_valid_user}` but the not\_valid\_user isn't valid. | `{requirerole:}` | | | |
| `INVALID_USER_DENYROLE` | you used `{denyrole:user\|not_valid_user}` but the not\_valid\_user isn't valid. | `{denyrole:}` | | | |
| `INVALID_USER_REQBAL` | you used `{requirebal:amount\|user}` but the user part could not be resolved to a valid member. | `{requirebal:}` | | | |
| `INVALID_USER_REQITEM` | you used `{requireitem:item\|amount\|user}` but the target user could not be resolved to a valid member. | `{requireitem:}` | | | |
| `INVALID_USER_DENYITEM` | you used `{denyitem:item\|amount\|user}` but the target user could not be resolved to a valid member. | `{denyitem:}` | | | |
| `INVALID_USER_IS_BOT` | you tried to modify a balance or inventory for a **bot user**, which is not allowed. | `{modifybal:}` or `{modifyinv:}` | | | |
| `INVALID_ITEM_NAME` or `INVALID_ITEM` |
you used {user\_item:} or {user\_item\_count:} without a valid item name or id. typically:
the item name part is blank, or the placeholder couldn’t parse the item name at all inside {modifyinv:}, the amount (middle part) is not a valid number.{modifyinv:sword | abc | @user} wwhere abc is not a number.
| `{modifyinv:}` | |
| `INVALID_SHOP_ITEM_ID` | you tried to **add** inventory with `{modifyinv:item\|amount\|user}` using an item id / name that doesn’t match any valid shop product. | `{modifyinv:}` | | | |
| `INVALID_INVENTORY_ITEM` | you tried to **remove** inventory with `{modifyinv:}` using an item name / id that the user does not have. | user doesn't have this item in inventory | | | |
| `INVALID_INV_OPERATION` | you used {modifyinv:} with an invalid operator.+ and -. anything else will error.
| `{modifyinv:}` | | | |
| `INVALID_AMOUNT` | inside {modifybal:}, the amount is not a valid number.{modifybal:abc} or {modifybal:+abc | @user}.
| `{modifybal:}` | | |
| `INVALID_BAL_OPERATION` | you used {modifybal:} with an invalid operator.+, -, \*, /, =.
| `{modifybal:}` | | | |
| `TOO_MANY_EMBEDS` | you tried to use {embed} more than the allowed number of times in a single autoresponder.10.
| `{embed:}` | | | |
| `NO_BUTTON_NAME_PROVIDED` | you used `{addbutton:}` without specifying a button name. | `{addbutton:}` | | | |
| `INVALID_BUTTON_NAME` | you used `{addbutton:name}` but that name does not match any existing saved buttonresponder. | `{addbutton:}` | | | |
| `NO_LINKBUTTON_TEXT_PROVIDED` | you used `{addlinkbutton:label\|link}` without a text label. | `{addlinkbutton:}` | | | |
| `NO_LINKBUTTON_URL_PROVIDED` | you used `{addlinkbutton:text\|}` without a url, url is missing | `{addlinkbutton:}` | | | |
| `LINKBUTTON_INVALID_URL_PROVIDED` | the url you provided to `{addlinkbutton:}` is not a valid url. it needs to start with http and be a full link like you used {lockedchoose:a | b | c} but there isn’t a corresponding choice at the original random index.{choose} picked the third item, but your locked list only has 2 items.
| `{lockedchoose:}` list is shorter than `{choose:}` list. | |
| `INVALID_WEIGHTS` |
you used {weightedchoose:} but the weights are invalid. for example:
non-numeric entries negative numbers all weights are zero nothing parseable as a number you provided fewer weights than there are choices attached to that slot.{choose:a | b | c} then {weightedchoose:1 | 2}.
| `{weightedchoose:}` |
| `INSUFFICIENT_RANGE` |
you used {range:start-end} but:
start or end is not a valid number, orstart is greater than end
a user did not have enough currency for the autoresponder to run.
iara needs (at least) 10 💰 for this autoresponder to run.
a user is missing an item, or does not have enough of that item, for the autoresponder to run successfully.
xyz needs 1 × apple for this autoresponder to run successfully.
one or more of the required arguments to your autoresponder are invalid or missing.which argument failed, and (if possible) show what you typed, e.g.:
the 2nd argument is not a valid number. you wrote abc.
the autoresponder tried to delete the trigger message , but:
mimu does not have Manage Messages, or the message was already deleted.
the autoresponder tried to dm the user , but could not, usually because:
the user has dms disabled for the server, or the user left the server. the embed create command
created embed with buttons below it
this what the first button, editing basic information, brings you to!
your freshly edited embed c:
a list of your server's embeds
successfully deleting your embed
embed edit all
this allows mimu to give you advice on exactly what you should choose.
autocomplete to prompt you to claim a key.
an easy way to claim up to 25 keys at once.
pet caretaker $1 + sales tax -> $1.49 or $14.99 / yearly (save $3) mimu plus previously called "mimu premium" $5 + sales tax -> $4.99 custom mimu previously called "my own mimu" $25 + sales tax -> $19.99
### individual keys: cheaper pricing!
key pricing is mostly unchanged, but due to the limitations of stripe billing, the model of which it works is a little bit different.
**previously:**
* keys were $4 each, then keys after the 3rd would be $3.50 each
* e.g. for 5 keys: $4 x 3 + $3.5 x 2 = $19
* e.g. for 2 keys: $4 + $4 = $8
* e.g. for 50 keys: $4 x 3 + $3.5 x 47 = $176.50
**now:**
* now provides a similar model, but at a less discounted price to encourage usage of **/purchase** instead:
* keys are $4 each, then keys after the 3rd would be $3.80 each
* **/purchase** now provides threshold-based key pricing. for most scenarios, the pricing is about the same as before, or cheaper.
* $4 per key (unchanged)
* 8% off for 3 or more keys
* e.g. for 5 keys: $4 x 5 x (100-8%) = $18.4
* 12% off for 20 or more keys
* e.g. for 50 keys: $4 x 50 x (100-12%) = $176
### role names
one feedback we got very often was that the role names were not intuitive, with users asking what "sugar pastries" was.
{% hint style="info" %}
**fun fact!** the origination of "sugar pastries" was inspired by one of our earliest donators dating back in **2020!**
{% endhint %}
* sugar pastries -> supporter
* premium beans -> stellar supporter
* my own mimu -> celestial supporter
colors still cuter than ever.
or [our support server.](https://mimu.bot/support) We are committed to providing excellent customer support and will work with you to resolve any issues within the scope of our policies and capabilities.
Your satisfaction is important to us, and we encourage open communication to address any concerns you may have regarding your purchase or use of our digital goods.
## Refund Policy
We understand that sometimes you may run into issues with your purchase, and we're here to help.
#### General Refund Policy
The nature of digital distribution makes it challenging to provide refunds. We provide comprehensive descriptions and previews of our Products to help you make informed decisions before making a purchase. However, we do offer refunds for up to **7 days** from your original purchase, as long as any keys that are associated with your purchase (if applicable) are intact and unused. To be eligible under these circumstances, you must ensure that the digital key (also coined as 'mimu key') has not been redeemed or used.
If you qualify for a refund based on the above criteria, please note that the refund amount will be subject to a **non-refundable payment processing fee**. This fee consists of $0.30 plus 3% of the original transaction amount. This is to cover the cost of processing the transaction and the refund
To request a refund under these terms, reach out to us via the [Support Server (talk-to-devs)](https://mimu.bot/support) or .
#### **Chargebacks**
Initiating a chargeback or dispute through your bank, or credit card issuer is against our [Terms of Use](https://mimu.bot/terms). Filing a chargeback for transactions made without following our refund process may result in immediate termination of your access to our digital goods and services. We take fraud and chargeback abuse seriously and may pursue legal action or other remedies to recover losses incurred.
If you have concerns about a transaction or believe you are entitled to a refund, we urge you to contact us directly before considering a chargeback. We are committed to addressing your concerns and finding a resolution within our policies.
# swapping over as an existing patron: early patron badge & more!
#### hello pastry! or should i say supporter? \~
thank you for supporting mimu so far - i really appreciate it! below i'll be sharing insights on exactly how the badge works, and how to transfer stuff over.
## the early patron role and badge (the "move-over" badge!)
to appreciate you for supporting us even through the patreon era, we're giving away a badge to anyone who's moving over to the new system within the **next 3 months**, i.e. before **June 10, 2024**.
shows in /balance, just like other badges.
the role received! :)
The exchange rate of 29.4 Euros to USD
