Repository navigation
Backend Menus
VelocityNavigator has two different inventory systems:
| Menu | Opened with | Configured in |
|---|---|---|
| Proxy lobby selector | /lobby menu |
Proxy gui.toml and messages.toml
|
| Backend custom menu |
/vnavmenu open or an NPC menu:<name> target |
Backend plugins/VelocityNavigator/menus/*.yml
|
Use the proxy selector when you want live health, player counts, pagination, and the normal routing pool. Use a backend YAML menu when you want a hand-built hub menu with submenus or player commands.
-
Put the same VelocityNavigator JAR on Velocity and the Paper/Spigot/Folia backend where the menu will open.
-
Restart both processes.
-
Confirm the backend log says
BACKEND GUI BRIDGE mode. -
Check this backend setting:
menus_enabled: true
-
Join the backend and run:
/vnavmenu list /vnavmenu open main
The first startup creates example main.yml, games.yml, and lobbies.yml files. Their example server names may not exist on your network; replace them before giving the menu to players.
Create plugins/VelocityNavigator/menus/network.yml:
title: "&b&lNETWORK MENU"
rows: 3
items:
main_lobby:
slot: 11
target: "lobby-1"
material: "NETHER_STAR"
name: "&a&lMain Lobby"
lore:
- "&7Return to the main lobby"
- "&eClick to connect"
games:
slot: 13
target: "menu:games"
material: "DIAMOND_SWORD"
name: "&e&lGames"
lore:
- "&7Open another YAML menu"
spawn:
slot: 15
target: "cmd:/spawn"
material: "COMPASS"
name: "&bSpawn"
lore: []Run:
/vnavmenu reload
/vnavmenu open network
You should see a three-row menu titled NETWORK MENU.
| Target | Result |
|---|---|
lobby-1 |
Sends the player to that exact Velocity server |
menu:games |
Opens menus/games.yml
|
cmd:/spawn |
Makes the player run /spawn
|
Server targets must match Velocity's [servers] names. A server click travels through the plugin-message bridge and is validated by Velocity before connection.
-
rowsmust be from2to6. - Slots start at
0. - A three-row menu has slots
0through26. - Each item needs a unique slot, target, material, and nonblank name.
- Lore is optional and supports up to 16 lines.
- Materials use Bukkit names such as
PAPER,COMPASS, orNETHER_STAR.
Backend administrators need velocitynavigator.admin.
| Command | Purpose |
|---|---|
/vnavmenu open <menu> |
Opens a menu for yourself |
/vnavmenu open <player> <menu> |
Opens a menu for another player |
/vnavmenu list |
Lists loaded menus |
/vnavmenu reload |
Reloads all YAML menu files |
/vnavmenu add <menu> <slot> <target> <material> <name> [lore...] |
Adds or replaces an item |
/vnavmenu remove <menu> <slot> |
Removes an item |
/vnavmenu title <menu> <title...> |
Changes the title |
/vnavmenu rows <menu> <2-6> |
Changes the row count |
In the add command, separate lore lines with |.
Create an NPC whose target is menu:network:
/vnavnpc create selector menu:network &b&lSERVER SELECTOR
Clicking it opens network.yml on that backend.
The menu is not listed.
Check the backend log after /vnavmenu reload. A file is rejected when rows, slots, required values, or lore limits are invalid.
The inventory opens but a server click does nothing.
Confirm the player has velocitynavigator.use, the server exists in Velocity, the proxy also has the same plugin version, and the player connected through Velocity.
I expected live health and player counts.
Those belong to the proxy lobby selector configured in gui.toml. Backend YAML menus are intentionally static.
Home · Quick Start · Configuration · Operations · FAQ
Website · GitHub · Support / Discord · Report a Bug
VelocityNavigator v4.5.0 · by DemonZ Development
![]()
Getting Started
Routing
- Routing Algorithms
- Algorithm Visualizations
- Initial Join Balancing
- Contextual Routing Guide
- Player Affinity
- Health & Circuit Breakers
- Retries & Fallbacks
- Geo Routing
Player Experience
- Java & Bedrock Selectors
- Selector Customization
- Backend NPCs
- Backend YAML Menus
- Language Packs
- Party System
- Capacity Queue
Configuration
- Configuration Guide
- Modular Configuration
- MOTD Configuration
- Authentication & Security
- Backend Bridge Configuration
- Migration Guide v3 → v4
- Migration Guide v4.4 → 4.5
Network & Operations
- Advanced Proxy Systems
- Redis & Multi-Proxy
- Common Core Architecture
- NavigatorAPI
- Storage & Databases
- Server Management
- Backend Lifecycle States
- Maintenance Mode
- HTML Dashboard
- Operations Runbook
- Prometheus & Grafana Setup
- Troubleshooting Guide
- FAQ
VelocityNavigator 4.5.0