BTC wallet, store and transactions
How to set up server BTC reward, player wallet, exchange for game money, self-service store and check purchases securely.
On this page
BTC in this module is the virtual community server currency. It is not Bitcoin, a cryptocurrency wallet or a real payment service. It is used to reward activity, purchase ready-made products and optional exchange for regular SCUM money.
The advantage is a unified history of every balance change. The player can see their wallet, the administrator can track the purchase and the system does not pretend to be successful in case of unsuccessful delivery.
Where can you find it in the admin
- BTC → Overview - module status and basic summaries.
- BTC → Settings - activity, wallet, exchange, messages and appearance.
- BTC → Categories – order and naming of trade groups.
- BTC → Shop - products, prices, orders and availability.
- BTC → Transactions - purchases, rewards, exchanges, cancellations and errors.
What you can set
Activity rewards
You determine how much BTC the player gets for a certain number of active minutes. You can turn off the reward completely and turn on the notification separately. Choose a pace that supports gaming but doesn't break store prices.
Wallet and statement
The player command can be, for example, /wallet. The output shows the balance and a limited number of recent transactions. Discord wallet can periodically refresh one message; webhook URLs are managed in the common settings Discord webhooks, not directly in the product.
Exchanging BTC and game money
The purchase rate tells how much regular SCUM money the player will pay for 1 BTC. The selling rate determines how much he gets back for 1 BTC. The difference between the exchange rates is a deliberate economic brake. Before turning it on, calculate how quickly players earn both currencies.
BTC Shop
Categories are user-facing groups of products. The product has a name, a price, a unique slug and a ready-made safe effect. The player buys with the command /buy slug. The product may issue a pack, vehicle, item, FAME or other supported reward. Do not put the internal command in the name or description of the product.
Recommended setup procedure
- Choose the server in Settings and turn on only the parts you want to use.
- Set activity reward and both exchange rates. Check whether the selling rate is more favorable than the buying rate.
- Prepare a short player command for wallet and understandable messages.
- Create a simple structure in Categories, for example Vehicles, Food & Drink, Health or Packs.
- Create products in the Shop. Give everyone a unique slug, price and verified delivery method.
- Test a cheap product with a trial balance. Check that the BTC charge and delivery were created correctly.
- After launch, regularly check Transactions and adjust prices according to real BTC income.
What happens when you buy
The player writes, for example, /buy rope. Nodera will verify the product, player, price and balance. It then creates a purchase and sends the delivery via NODERAgent. Success is recorded only according to the result. If the result is clearly unsuccessful, the transaction remains traceable and the system can safely return the balance according to the type of operation. An unclear result is not repeated blindly so that the player does not get the same valuable thing twice.
An optional Discord private message can confirm the purchase to the player. This requires a linked Discord identity; the missing connection must not change the accounting history itself.
Example from the Main server
Status of the database as of 1 September 2026.
| Area | Main example |
|---|---|
| Activity | 1 BTC for every 60 minutes of activity, notification on. |
| Wallet | Command /wallet, Discord refresh every 30 seconds, maximum 50 moves displayed. |
| Exchange | Purchase 1 BTC for 4000 in-game currency; sell 1 BTC for 500. |
| Shop | 8 active categories. Examples: Rope 2 BTC (/buy rope), Flag Material 5 BTC, Cargo Drop 25 BTC, Rager 70 BTC. |
| Brand | Name "BTC Shop", public slug btc-shop. |
Check and frequent problems
- The player does not know the balance: verify the exact wallet command and whether the module and its rollout are enabled.
- The purchase is rejected: check the balance, product status, slug and possible conflict of the command with another module.
- BTC has been deducted, but the reward is not confirmed: open Transactions and check the final delivery result. Do not manually create a second purchase without evaluating the first.
- Discord DM did not arrive: check player connection with Discord and message settings. The DM itself is not an accounting document; the transaction record decides.
- The economy is growing too fast: reduce activity or raise prices. Historical movements are not retroactively calculated by changing the exchange rate.