Economy
Rewards and progression with practical safeguards.
Before you start
Dashboard changes are currently restricted to the configured Yume owner. Sign in with Discord and choose Yume. Public documentation is available to everyone.
Verify channel access and role membership before changing exclusions or immunity.
Set it up
- Check feature availability: Open General settings → Feature availability. Enable this module, save, then use Apply feature availability to update the running bot.
- Set up onboarding: Open Economy service and choose the channel and access roles used by the existing economy onboarding flow.
- Choose safeguards: Open Economy safeguards and Cooldowns. Save each changed section and check any Waiting to apply notice.
Check it works
Use a controlled account to check economy onboarding and balance lookup. Balance adjustments and game refunds are staff actions, not setup tests.
How it works
Quest exclusions are additional to built-in exclusions. They do not replace the existing counting, spam and command-channel exclusions.
Effect immunity protects members of the selected roles from supported disruptive effects. It does not grant currency or reset progress.
Member rewards and transfers continue in Discord. The owner dashboard supports individual account balance changes, access freezes, casino access, cooldown resets and notes; every change needs a reason and a reviewed record.
Use Save after editing. If a change is marked as requiring a restart, it is stored but will only apply when Vault next starts. Refresh after the restart to check the pending indicator.
Manage one account at a time
Tokens are virtual and have no cash value. Review the balance, access, casino key/session and cooldowns before changing an account. Freeze preserves balances. Resetting cooldowns retains protection against repeated stealing. Closing an active individual game requires an explicit refund choice; cancelling betting roulette refunds eligible wagers once. Database changes and Discord notifications have separate results.
Staff actions, privacy and refresh
Staff actions require Discord sign-in and current authorized server access. Recovery sign-in supports settings only. Review the exact confirmation before submitting; changes and partial deliveries have a request receipt.
An uncertain outcome is not a confirmed failure. Check the receipt, record and Discord before acknowledging it. Acknowledgment does not retry an effect or remove the server’s duplicate-action protection. Safe notes and other records remain usable; unresolved effects require owner investigation.
Active workspace pages refresh every 30 seconds and Overview every minute while visible. Refresh pauses for drafts or focused controls. Manual refresh preserves edits; a changed staff record requires explicit review before keeping its draft. Private drafts remain in this tab and are not saved in browser storage.
Use Save after editing. If a change is marked as requiring a restart, it is stored but will only apply when Vault next starts. Refresh after the restart to check the pending indicator.
If something is not working
Check that the feature is enabled, that the selected channel or role still exists, and that Vault has the required Discord permissions. A higher role cannot be assigned or moderated by a bot below it.
If the dashboard cannot load or save, keep your edits on the page, check Status, then try again. An expired session requires signing in again. Do not repeatedly submit an action whose result is uncertain.