To get started with CommandBridge, follow these simple steps to download and install the plugin on your servers. CommandBridge is available on Modrinth, which provides secure and easy access to the latest versions.
CommandBridge has the following aliases:
commandbridge <command>
cb <command>
Installation
Step 1: Download CommandBridge
Visit the Modrinth pages below to download the latest versions of CommandBridge for both Bukkit and Velocity servers:
After downloading the necessary files, follow these steps:
Place the CommandBridgeBukkit-1.7.1-SNAPSHOT.jar file into the plugins folder of your Bukkit server.
Place the CommandBridgeVelocity-1.7.1-SNAPSHOT.jar file into the plugins folder of your Velocity server.
Step 3: Restart Your Servers
Restart your servers to load and initialize the CommandBridge plugin. This step is crucial for the proper activation and configuration of the plugin.
Step 4: Configure CommandBridge
Access the configuration files in the plugins/CommandBridge directory on each server to customize settings such as command placeholders, execution delays, and verbose output.
Configuration
The primary configuration settings for CommandBridge are located in a config.yml file. This file is always located on the Velocity side.
config.yml
config-version: 2 #Do not change the config version
server-id: "main" #The ID of the Proxy. You can name it something like main-proxy or just main
verbose-output: false #Whether to output verbose information to the console
config-version: 2 #Do not change the config version.
server-id: "lobby" #The ID of the server. This is used to identify the server in the network. Change this to a unique value for each server.
verbose-output: false #Whether to output verbose information to the console
Velocity:scripts/example.yml
Scripts on the Velocity side are used to dispatch commands that will be executed on the Bukkit server. This is an example script:
script-version: 2 #Do not change the script version
# The name of the command that will be dispatched
name: examplecommand
# Whether the command is enabled
enabled: true
# The list of commands to execute
commands:
# The command to execute on the target server
# IMPORTANT: The command must be enclosed in single quotes
- command: 'say Hello from 72S!'
# The delay in seconds before executing the command
delay: 0
# The ID of the target server.
# Use the server-id from the config.yml file of the target server
target-server-ids: ['lobby']
# The executor of the command.
# This can be either "player" or "console"
target-executor: 'console'
# Whether to wait until the player
# is online on the target server before executing the command
wait-until-player-is-online: true
# Whether to disable the check if the executor is a player
disable-check-if-executor-is-player: false
# Whether to disable the check if the executor is on the server
disable-check-if-executor-is-on-server: false
# Add more commands here
- command: 'say I love Coding!'
delay: 0
target-server-ids: ['hub', 'lobby']
target-executor: 'player'
wait-until-player-is-online: false
disable-check-if-executor-is-player: false
disable-check-if-executor-is-on-server: false
Bukkit:bukkit-scripts/example-bukkit.yml
Scripts on the Bukkit side are used to dispatch commands that will be executed on the Velocity server. This is an example script:
script-version: 2 #Do not change the script version
# The name of the command that will be dispatched
name: examplebukkit
# Whether the command is enabled
enabled: true
# The list of commands to execute on the Velocity server
commands:
# The command to execute on the target server
# IMPORTANT: The command must be enclosed in single quotes
- command: 'velocity info'
# This can be either "player" or "console"
target-executor: 'player'
# Target Velocity server ID
target-server-ids: ['main']
# Add more commands here
In summary:
Velocity Scripts: Dispatch commands on the Velocity server, which are then executed on the Bukkit server.
Bukkit Scripts: Dispatch commands on the Bukkit server, which are then executed on the Velocity server.
Feedback and support
Please report any issues, usability improvements, or feature requests to Github Issues (you will need to have a GitHub account or need to register). You can also open a ticket on my Discord Server.