-
Notifications
You must be signed in to change notification settings - Fork 2
Setup Guide
- Open your Velocity Proxy plugins folder
- Put the VexelCore-Proxy .jar file into the plugins folder.
- Stop the proxy if it is running, then start it.
You should see the message "All configs have been loaded!" from VexelCore in the console.
Navigate to the plugins folder for your proxy. There should be a folder called "vexelcore". Inside, there should be a "config.toml" file. That is the file used to control and customize VexelCore.
VexelCore is modular. This means you can enable/disable and customize the majority of the plugin. The [features] section accepts booleans (true/false).
Allows you to create aliases for commands that players will execute on the proxy or server. As this plugin is running on the proxy, the command(s) will work on any server connected to the proxy.
Type is the type of custom command. Options are playerProxyExecute and playerServerExecute. More types are planned to come out soon.
The newCommand option is for playerProxyExecute and playerServerExecute. It is the command the player will type.
The execute option is for playerProxyExecute and playerServerExecute. It is the command that the proxy or server thinks the player executed.
The passArgs option is for playerProxyExecute and playerServerExecute. This allows arguments of a command to be passed in addition to the value of execute.
customCommand = [
{ type = "playerProxyExecute", newCommand = "hub", execute = "server hub", passArgs = "no" },
{ type = "playerProxyExecute", newCommand = "survival", execute = "server survival", passArgs = "no" },
{ type = "playerServerExecute", newCommand = "helpplz", execute = "help", passArgs = "yes" },
]