Economy
Configure currency, jobs, shop activity, rewards, and member balances.
How it works
Airwavy's economy combines balances, work and job flows, shops, transfers, daily rewards, games, inventories, and leaderboards. The fixed /economy jobs ladder now uses the renamed career labels shared across Discord and the dashboard, and /economy shop, /economy inventory, and /economy jobs each show an inline action button (Buy, Use, or Set Job) on every row. /economy inventory's listing is public so members can show off what they own.
Before you start
- Choose clear currency branding and reward values before enabling the system broadly.
- Review cooldowns and payouts together to avoid runaway inflation.
Configure it
- Open Economy in the dashboard.
- Configure currency presentation, rewards, jobs, shop items, and enabled activities.
- Save, use /economy balance to confirm a test account, then exercise one earning and one spending flow.
Vote rewards
The /economy vote command opens Airwavy's official voting page. When Airwavy receives a valid vote notification, the voter receives a global economy reward and the result is reflected in their economy totals.
- Consecutive eligible votes increase the reward through a capped streak bonus.
- Eligible weekend votes receive the configured weekend bonus.
- A successful vote also grants a temporary 12-hour leveling boost in servers where the member has a leveling profile.
- Airwavy attempts to send the voter a private reward summary; closed direct messages do not cancel an already recorded reward.
Daily login streak
/economy daily tracks a separate consecutive-day streak on top of the base reward, rewarding members who come back day after day rather than claiming once and disappearing. This applies identically whether /economy daily is run in Discord or claimed from the dashboard.
- Each consecutive claim within a 48-hour window of the last one adds +10% to that day's reward, stacking up to a +100% cap at a 10-day streak.
- Missing the 48-hour window resets the streak back to 1 on the next claim.
- A Streak Freeze shop item protects the streak through exactly one missed window instead of losing it, and any member can buy one — it is not a Premium-exclusive item.
- The item the streak reward pulls from can never itself be sped up by a cooldown-skipping item — /economy daily is deliberately excluded from Energy Drink's cooldown skip so a single drink can't be used to farm multiple streak-days at once.
Robbing: risk and reward
/economy rob targets another member's wallet at a configurable success rate. A shielded, opted-out, or already-recently-robbed target changes the outcome before any cooldown is spent.
- A member who was just successfully robbed is protected from being robbed again for the same cooldown a robber must wait between attempts, so one victim cannot be piled on by repeated attempts.
- A Rob Shield blocks the attempt outright and also requires the attacker to pay the shielded member the cut they tried to steal.
- A failed attempt isn't free: the fine the robber pays goes to the target, not just out of the economy, and the target gets a DM naming the failed attacker and the amount they were paid.
- A Bounty Contract lets its buyer bypass a target's recent-robbery protection for one attempt; it never bypasses a Rob Shield or either member's robbing opt-out.
- Opting out of robbing (in both directions) now requires a purchased Protection Contract; turning it back off stays free from the authenticated profile editor.
Gambling limits
/economy gamble covers Coinflip, Slots, and Roulette (Red/Black or a straight-up single-number bet at 35:1); Blackjack runs through its own interactive Hit/Stand controls started from the same command.
- Every wager is capped at 50% of the player's current net worth (wallet plus bank combined) at the moment they bet — there is no separate flat maximum to configure.
- Roulette's straight-up number bet targets one exact number from 0-36 for a 35:1 payout, alongside the existing Red/Black option.
- /economy buy, /economy sell, and /economy gift each allow up to 1,000 of an item per use.
Safe balance changes
Member-to-member payments, robbery outcomes, gifts, and shop purchases use protected balance operations so related changes complete together.
Buying a shop item or lottery tickets can draw from both your wallet and bank balance together, so you don't need to move funds into your wallet first — /economy pay and /economy gift still only move funds you already hold in your wallet.
- If secure balance transfers are temporarily unavailable, Airwavy stops the action and confirms that no balance changed.
- Retry once after a short wait. If the same message persists, ask a server manager to check service status or contact Airwavy support.
- Use /economy history after a completed action when you need to confirm the recorded balance change.
- A successful /economy pay or /economy gift sends the recipient a private message naming the sender, the server, and what was sent, so a received payment or item is never a silent surprise.
Keep the economy fair
- Publish major payout, shop, or balance-policy changes before they take effect.
- Review earning rates and prices together rather than tuning one command in isolation.
- Treat games of chance and member-to-member transfers according to your community rules and local requirements.
- Use account history to investigate discrepancies before manually changing a balance.
Expected result
- Economy actions use the configured currency and rules.
- Balance-changing actions appear in account history and leaderboard data where applicable.
Common errors
Rewards feel too large or too small
Review payouts, prices, cooldowns, and starting balances as one system. Make incremental changes and communicate resets or balance adjustments to members.
Saved changes do not take effect
Reload the feature page and confirm the saved values. Then verify that the selected Discord channel or role still exists and that Airwavy can access it.
Discord reports missing permissions
Check the permission on both the server role and the target channel. Channel overwrites and role hierarchy can deny an action even when the server-level permission is present.