BeastTokensProxy

BeastTokensProxy

Network Currency Sync, Proxy Commands & Web Control

Current Release: 4.3.13

Connect your BeastTokens economies across your Minecraft network.

Keep shared currencies connected as players move between servers, manage wallets from the proxy console, and open your backend web editors from one network dashboard.

BUNGEECORD & VELOCITY • WEB DASHBOARD • MULTI-CURRENCY • PROXY SYNC

One Network, Connected Economies

Running Survival, SkyBlock, Prison, or an event server? BeastTokensProxy is the network companion for BeastTokens. Install it on BungeeCord or Velocity to connect participating backend servers through ProxySync.

• Send currency-specific balance refreshes between connected servers.
• Support Tokens, Gems, seasonal points, and your own currency IDs.
• Check, add, remove, or set balances from the proxy console.
• Relay MySQL shop stock and rotating-shop cache updates.
• Discover backend web editors and open them from one dashboard.
• Browse registered MySQL economies and set or reset individual player balances in your browser.
• Receive currency announcements automatically from connected BeastTokens servers.

Your Network Web Dashboard

Enable the optional WebInterfaceProxy to give your administration team one starting point for the network.

Backend Server Directory

• View announced BeastTokens web editors as server cards.
• See each entry's server name, editor address, last-seen time, and Online/Stale status.
• Open a backend editor inside the dashboard or in a new browser tab.
• Keep saved server entries across proxy restarts and remove entries you no longer need.
• Use the backend editor's Back To Proxy control to return to the network hub.

Online/Stale reflects recent announcements from the backend. Each backend supplies its own running web editor and login. Its Shop Studio, shops, drops, backups, and other administration tools remain available through that editor.

MySQL Economy Manager

• Select an enabled, registered currency from the economy list.
• Search player records by name or UUID.
• Sort by largest balance, smallest balance, player name, or last-seen time.
• Display player heads, UUIDs, and exact decimal balances.
• Choose how many records to display, up to 500 per request.
• Set an individual player's balance or reset it to zero.
• Send the matching currency refresh to connected backends after an edit.

This page reads and edits registered MySQL balance tables in the proxy's configured database. For a currency using another storage provider, open its backend editor or use a backend-routed proxy command.

Make The Dashboard Your Own

• Four browser themes: Ocean, Dungeon, Nether, and Paper.
• Responsive layout for desktop and smaller screens.
• Configurable username/password login and expiring sessions.
• Optional temporary auto-login links.
• Configurable listen address, port, and public browser URL.

The panel starts disabled. Configure a strong password before enabling it; the default listen address is 127.0.0.1 and the default web port is 8760. When allowing remote access, use a protected network or a trusted HTTPS reverse proxy.

Currency Commands From The Proxy

Give staff a consistent command entry point, even when players are on different backend servers.

/BTP balance Steve Tokens
/BTP add Steve 100 Tokens
/BTP remove Steve 25 Tokens
/BTP set Steve 500 Tokens
/BTP add Steve 50 Gems -s

• Include a currency ID to choose a wallet, or omit it to use the selected backend's default currency.
• Target an online player, a known offline player name, or a UUID.
• Add -s to suppress the online recipient's balance-change notification.
• Requests run through a connected BeastTokens backend; online targets use their current backend when it is connected to ProxySync.
• The selected backend applies its currency manager and storage rules.

An available backend connection is required. A dispatched balance-change request reports that it was sent; balance queries return the backend's response.

Currency Registry & Administration

/BTP currencies
/BTP currency info Tokens
/BTP currency refresh
/BTP shopweb status
/BTP shopweb start
/BTP shopweb stop
/BTP debug on
/BTP debug status
/BTP debug off
/BTP reload

Currency announcements populate Currencies.yml with IDs, display names, types, table names, and source servers. The registry is stored separately from config.yml. Manual currency register/remove commands are also available; they manage the proxy registry.

Proxy staff need one of these permissions:

BeastTokens.Admin
BeastTokens.admin
BeastTokens.Proxy.Admin

More Than Balance Refreshes

ProxySync also connects network shop features provided by BeastTokens on your backends.

• Relay stock-limit refreshes for MySQL-backed shop stock.
• Relay rotating-shop refreshes for shared MySQL rotation state.
• Deliver shop YAML to selected connected backends using the backend web editor's shop synchronization controls.
• Forward player-name/UUID information and backend currency announcements.
• Share backend editor addresses with WebInterfaceProxy.

Configure each shared currency to use the same MySQL database and balance table on every participating backend. Configure shared stock and rotation storage in the backend shop settings. ProxySync carries update notifications; MySQL holds the shared data.

Requirements & Installation

• A BungeeCord or Velocity proxy, with the Java runtime required by that proxy build. The current BeastTokensProxy Velocity module requires Java 25 or newer.
• BeastTokens and BeastLib 1.7.0 on each participating backend.
• Shared MySQL/MariaDB storage for currencies that should share one network wallet.
• A reachable ProxySync connection between the proxy and participating backends.

1. Install the matching BeastTokensProxy JAR in your proxy's plugins folder, then start the proxy to generate its configuration.
2. Open plugins/BeastTokensProxy/config.yml on BungeeCord, or plugins/beasttokensvelocity/config.yml on Velocity.
3. Enable ProxySync and choose its listen address and port. The default port is 5026.
4. Configure your shared backend currencies to use MySQL with matching database/table settings.
5. Enable ProxySync in each backend's plugins/BeastTokens/config.yml and point it at the proxy's reachable address and the same socket port.
6. Restart the updated servers, then check /BTP currencies and /BTP debug status.
7. Configure WebInterfaceProxy login settings and start it with /BTP shopweb start when you want the browser dashboard.

Proxy Socket Example

Options:
  ProxySync:
    Enabled: true
    Ip: "0.0.0.0"
    Port: 5026

Backend Connection Example

Options:
  ProxySync:
    Enabled: true
    Server: ""
    Ip: "10.0.0.10"
    Port: 5026

Replace 10.0.0.10 with your proxy's reachable address. Use 127.0.0.1 only when the proxy and backend share the same network environment. Merge these fields into the existing configuration. Leave Server blank for address-based backend identification, or set its exact name from your proxy's server configuration.

Does The Proxy Need Its Own MySQL Login?

The ProxySync relay and backend-routed commands can run with Options.MySQL.Enabled: false on the proxy. Enable and configure the proxy's MySQL connection when using the browser Economy Manager. Replace example credentials such as DataName and UserName with real connection settings. The Host must be reachable from the proxy.

Upgrading An Existing Network

• Back up the plugin configurations and database before updating, and use matching BeastTokens/BeastTokensProxy releases across the network.
• Very old Bungee versions used plugins/BeastTokensBungee/bconfig.yml. Transfer your settings into the current plugins/BeastTokensProxy/config.yml, including MySQL credentials and the ProxySync port.
• Current configuration uses Options.ProxySync. When transferring an old Options.BungeeSync section manually, use the current ProxySync names.
• Stop older backends sharing the currency database before legacy migration. An old plugin can recreate the original single-currency tables after migration.
• Use the backend legacy-migration preview before changing stored currency data. Keep verified migration archives as backups.

Can I Use It With Separate File-Based Wallets?

Backend-routed commands can operate on the selected backend's supported wallet, but sharing one wallet across servers requires shared storage. Separate File or SQLite databases remain separate economies. Use MySQL for shared currency balances.

Community & Support

Need help connecting servers, configuring shared currencies, opening backend editors, or upgrading an older network?

Join The Official BeastTokens Discord