Command Currency Settings
What are Command Currency Settings?
Command Currency Settings control how a command handles rewards, costs, cooldowns, and streak-based bonuses.
Admins can configure:
- Rewards — Give users currencies or cards when they use the command
- Costs — Require users to pay currencies to use the command
- Cooldowns — Control how often users can receive rewards from the command
- Custom messages — Send an extra message for rewards or costs
- Streak multipliers — Increase rewards based on streak length
- Milestone rewards — Give bonus rewards at specific streak milestones
These settings are used by commands such as /daily, /weekly, and /monthly.
How it works
Open the command settings
Go to the command you want to edit and open Currency Settings.
Configure rewards or costs
Choose whether the command should give rewards, require costs, or both.
Select the currencies and amounts
Choose which currencies the command uses and configure the reward or cost amounts.
Add optional settings
You can also configure cards, cooldowns, custom messages, streak multipliers, and milestone rewards.
Save the settings
Save the command settings so the changes apply.
Rewards and costs
Rewards
When Rewards are enabled, the command gives users rewards when they use it.
Rewards can include:
- Currencies
- Cards
For currency rewards, admins can:
- Select one or more currencies
- Set a fixed reward amount for each currency
- Use a range reward if supported by the command
If the command supports card rewards, admins can also configure how many cards are given per use.
Costs
When Costs are enabled, users must pay the configured currencies to use the command.
For command costs, admins can:
- Select one or more currencies
- Set the cost amount for each selected currency
Users must have enough of the required currency or currencies before they can use the command.
Required rewards
Some commands can use rewards optionally, while others must have rewards configured before they can be used.
For example:
/daily/weekly/monthly
cannot be used until an admin has configured their rewards.
This is separate from cooldown behavior. A command can still have an editable cooldown even if rewards are not required.
- Some commands work without rewards being configured
- Some commands require rewards before users can run them
- Cooldown settings do not automatically mean rewards are required
Cooldown
The Cooldown setting controls how long a user must wait before receiving rewards from that command again.
If the cooldown is set to 0, the command has no cooldown.
Custom reward and cost messages
Admins can optionally enable custom messages for rewards and costs.
These settings send an extra message when the command is used.
Reward messages
A reward message can show additional information after the command gives its rewards.
Cost messages
A cost message can show extra information when a user pays the command cost.
Some commands may use default reward templates.
If default rewards are enabled for a command, parts of the reward message may need to be changed in that command’s default settings under Response Design instead of only in the Currency Settings section.
Command streak settings
All commands support Command Streak Settings, but admins only need to configure them if they want to use streak-based rewards.
Command streak settings are split into two parts:
- Streak Multipliers
- Milestone Rewards
Streak Multipliers
Streak Multipliers increase the base reward depending on the user’s streak length.
When enabled, admins can create multiple multiplier tiers.
Each tier can define:
- Minimum streak days
- Maximum streak days (optional)
- Reward multiplier
Example
A command could be configured like this:
- Day 1 to 6 →
0.5x - Day 7 and above →
1x
This means the command reward changes automatically based on the user’s current streak tier.
Milestone Rewards
Milestone Rewards give users bonus rewards when they reach a specific streak day.
When milestone rewards are enabled, admins can create milestone entries such as:
- Day 7
- Day 30
- Day 100
Each milestone can include:
- A streak day
- A reward multiplier (optional)
- A card bonus (optional)
- Bonus currencies
This allows milestone rewards to give extra value on important streak days.
Award Past Milestones
If Award Past Milestones is enabled, already-qualified users can also receive milestone rewards retroactively.
This is useful when milestone rewards are added after users have already built a streak.
Important notes
- Rewards and costs can be configured separately
- Some commands require rewards to be configured before they can be used
- Reward and cost messages send an extra message when enabled
- Streak multipliers and milestone rewards are optional to configure