Discord LiteBans Bridge for Velocity
Moderate your Velocity network directly from Discord with clean slash commands powered by LiteBans.
This resource connects a Discord bot to your Velocity proxy through a lightweight bridge plugin, allowing staff to execute LiteBans moderation commands without joining the server or opening the console manually. It is built for networks that already use Discord for reports, staff communication, and moderation workflow, and want a faster way to punish players across the network. LiteBans supports cross-server punishment management, and Velocity is a modern high-performance proxy platform, which makes this combination ideal for network moderation.
What this product does
This resource lets your staff use Discord slash commands to send moderation actions to your Velocity proxy, where they are executed through LiteBans. That means your team can handle punishments directly from Discord while still using the LiteBans system already installed on your network. LiteBans is available for Velocity-compatible network setups, and Velocity’s plugin system supports storing plugin data in its own directory for simple configuration.
Main use cases
- Discord-based report handling
- Staff teams that moderate from mobile or outside the game
- Velocity networks already using LiteBans
- Communities that want faster moderation response times
- Owners who want a simpler staff workflow without panel hopping
Included commands
- /banplayer
- /muteplayer
- /kickplayer
- /warnplayer
- /unbanplayer
- /unmuteplayer
- /history
- /checkban
- /checkmute
- /warnings
- /staffhistory
- /banlist
- /mutelist
- /warnlist
- /ipban
- /unbanip
Key features
- Discord slash command moderation workflow
- Designed for Velocity + LiteBans
- Administrator-only Discord command access
- Bot configuration through config.yml
- Bridge plugin configuration through its own config.yml
- Pterodactyl-friendly deployment
- Shared-secret authentication between bot and bridge
- Input validation for player names, durations, and IPs
- Lightweight setup with simple file-based configuration
How it works
- A staff member runs a slash command in Discord.
- The bot checks that the user has the required permission.
- The bot sends the request to the bridge endpoint.
- The Velocity bridge plugin validates the request.
- The plugin executes the corresponding LiteBans command on the proxy.
Why this is useful
Most networks already manage reports and staff communication in Discord. This resource removes the delay between a report and an action by letting staff punish directly from Discord while keeping LiteBans as the actual punishment system. It keeps the workflow familiar for staff and reduces the need to constantly switch between Discord, panel, and console.
Configuration
The bot can be configured with:
- bot token
- guild ID
- bridge URL
- shared secret
The bridge plugin can be configured with:
- port
- shared secret
This makes the resource easier to install and easier to resell to legitimate buyers because they do not need to edit source code.
Requirements
- Velocity proxy installed and working.
- LiteBans installed on the network.
- Java environment for the bot.
- Discord bot application with bot and applications.commands scopes.
- Network access between the bot and the bridge endpoint.
Important note
Punishment commands are the main focus of this resource. Lookup commands such as history and warning checks depend on how LiteBans outputs those results in your setup.
Installation tutorial
Installation
- Install and configure Velocity on your network.
- Install LiteBans and confirm it is working correctly on your proxy/network.
- Upload the Discord bot jar to your host or Pterodactyl server.
- Start the bot once so it generates config.yml.
- Edit the bot config.yml with your bot token, guild ID, bridge URL, and shared secret.
- Upload the bridge plugin jar to the Velocity plugins folder.
- Start the proxy once so the plugin generates its own config.yml.
- Edit the bridge plugin config.yml with the port and matching shared secret.
- Make sure the configured bridge port is reachable from the bot host.
- Invite the Discord bot to your server with bot and applications.commands.
- Restart both the bot and the proxy.
- Test commands like /banplayer, /muteplayer, and /warnplayer.
Example bot config
bot-token: "YOUR_BOT_TOKEN"
guild-id: "YOUR_GUILD_ID"
bridge-url: "http://YOUR_PROXY_IP:8085/bridge"
shared-secret: "YOUR_SHARED_SECRET"
Example bridge config
port: 8085
shared-secret: "YOUR_SHARED_SECRET"
