Skip to main content
Riftvelocity Pn
Resource Link: Rift Velocity
Supported Versions: 1.7 - 1.21.5
Supported Software: Velocity
View our detailed general setup installation guide to install your setup!

Dependencies

Setup with Ace Lobby

Linking the Ace Lobby setup is simple, as it’s already preconfigured for seamless integration.

Add the server to velocity.toml

velocity.toml
[servers]
# Configure your servers here. Each key represents the server's name, and the value
# represents the IP address of the server to connect to.
lobby = "127.0.0.1:30066"

# In what order we should try servers when a player logs in or is kicked from a server.
try = [
  "lobby",
]

Setup the /hub command

Go to plugins/velocity-tools/config.yml
config.yml
  hub:
    enabled: true
    servers:
      - "lobby" # Use the lobby server name from velocity.toml

Secure your server

Secure your backend servers to prevent players from joining them directly and bypassing the proxy. For a detailed guide click here.
If you get stuck at any point, I recommend checking Velocity’s official documentation.

FAQs

Simply replace the server-icon.png file with your own 64x64 icon, then restart your server.
Use /maintenance toggle
There are three levels of staff chat: staff, developer, and admin. Use the following commands to send messages in each:
  • /sc <message> for staff chat
  • /dc <message> for developer chat
  • /ac <message> for admin chat
Replace the world.nbt file in the **LimboAuth **plugin with your custom schematic.
To create a .nbt schematic, copy your build using WorldEdit and run the command: //schem save world structure
After that, position the lobby below the player by updating the world coordinates in the config:
config.yml
  world-coords:
    x: -12
    y: 110
    z: -13
This setup uses LuckPerms. If you haven’t merged the databases with your backend (Spigot servers), use /luckpermsvelocity to edit permissions and ranks.

Since the Tab plugin runs on the proxy, you need to manage prefixes there, because prefixes from the backend servers won’t be applied. To simplify this, you can create a single MySQL database shared between the proxy and backend servers. This isn’t mandatory, but it makes managing ranks easier since you only need to update them once instead of twice.