RoBot setup

Prerequisites and economy configuration

A dashboard owner must approve this server for RoBot before ordinary economy slash commands run. Members must accept the displayed RoBo Bot Rules with I accept the RoBo Bot Rules; an economy ban can still refuse access. Read the rules before accepting. Dashboard configuration access, Discord permissions, game-host controls, and the grant whitelist are different authorities. Keep grants with the exact server whitelist; Administrator alone does not authorize /grant. Before spending or granting, ask staff whether this installation uses shared global accounts (the default) or separate server accounts. Guild-only commands do not by themselves establish a separate server wallet.

Member profiles and balances

Begin with /profile view, /balance, /inventory, and /stats for your own account. Self views can create an account; viewing another member does not always create one. Read Wallet, Bank, and Withdraw Today together. /deposit amount:all moves available wallet credits to the bank. /withdraw can refuse an amount above the remaining UTC-day allowance instead of partially withdrawing it. /daily has a separate 24-hour elapsed cooldown and a 48-hour streak window, with rewards based on saved server settings. Follow the returned wait or refusal instead of assuming a midnight reward reset.

Rewards, shops, and items

Inspect /shop for item IDs, price, stock, and Manual or Rotation labels before /buy item:<listed-item-id> quantity:1. Check the actual purchase result, /balance, and /inventory. Shop and inventory views are bounded and can omit entries. Craft with an exact recipe ID after checking its materials; equip selects the highest-refinement owned variant. Refinement consumes a crystal even on a failed roll, use consumes one consumable, and selling or gifting can remove lower-refinement variants first. Do not infer a complete inventory change from an acknowledgement alone; inspect the relevant stacks before spending or transferring more.

Games and RPG progression

Read /stats and /inventory before equipment, refinement, hunting, gacha, or PvP. /hunt can spend energy and lose credits on defeat; read its Credits, EXP, Energy, Loot, and Level Up results when present. Gacha consumes owned boxes before charging the wallet for remaining pulls, with box-specific pity rules. /pvp defaults to no bet, and only the challenged member can accept its two-minute request. Casino wagers require explicit bets. Blackjack, dice, slots, and crash controls belong to their player; /color and /colorgame have distinct round and lobby workflows. Read the command’s stake, control, and result guide before playing.

Restricted grants

Use /grant only when your Discord ID is in this server’s exact grant whitelist. Choose a different human recipient, amount, and optional reason; bots and self-grants are refused and the runtime caps the amount at 1,000,000,000 credits. Confirm whether the recipient wallet is shared or server-scoped before submitting. Credits Granted or its text fallback reports the actual amount and new wallet. Transaction and log writes are best effort. After a missing or failed reply, inspect /balance user:<recipient> and ask staff to reconcile the existing grant before considering another submission.

Social systems

Use /profile bio, title, and wallpaper to customize your own profile, then /profile view to read it back. Wallpaper must be owned and tagged wallpaper. Follow or unfollow the intended member and inspect both followers/following lists; each list shows at most 20 entries. A marriage proposal names a ring to consume and only the invited member can accept it within 15 minutes. Changing rings consumes a new ring; divorce immediately costs half the caller’s wallet rounded down. /mdaily has its own elapsed cooldown. Check profiles, inventory, and balances after uncertain relationship changes before acting again.

Confirm the result

For each chosen workflow, retain the actual acknowledgement or final game message and inspect the current account, inventory, profile, or active round afterward. A saved change can precede a later transaction, log, or Discord reply failure; an error does not prove rollback. Bounded lists, expired controls, and missing messages do not prove non-execution or authorize a repeated purchase, grant, wager, refund, or item action. Ask staff to reconcile ambiguous state before another mutation. These instructions come from current source; actual Discord workflow results, redacted screenshots, rendered documentation checks, and release verification still require their separate checks.

1. Before you begin

   Confirm server access.

   Expected: The intended server is identified.

2. Invite the bot

   Open the RoBot invite.

   Expected: RoBot joins the intended server.

3. Choose a server

   Select the intended server.

   Expected: The selected server is visible.

4. Configure

   Apply the reviewed settings.

   Expected: The settings can be read back.

5. Confirm the result

   Run one bounded check.

   Expected: The expected result is visible.