Overview
Server configuration
How changes are applied
Read live file
Current content is fetched before editing.
Local snapshot
The previous version is saved in browser revision history.
Write to Pelican
The updated file is written directly to the server.
Reload when supported
LuckTAB and VScoreboard reload automatically.
Installed plugins
Tab list designer
Header & footer
Create default, world-specific or permission-specific layouts.Player list
AFK
Player list & ping
More of LuckTAB’s tab-list and connection styling, without raw YAML.Fake tab entries
Nametags & below-name
Control the name above players and optional stat below it.Below-name stat
LuckTAB sidebar
Stat sidebar like your reference image: player profile, statistics and server status.Rank prefixes
Scoreboard designer
Lines
Reorder with arrows; structured lines can keep refresh and score metadata.LuckTAB design targeting
Show this design only in matching contexts.Chat formatting
Hover card
Click action
Mentions
Player ranks & tags
Ranks are applied through LuckPerms commands, while their visual tab/chat prefixes are kept synchronized with LuckTAB. Existing MHQ visual ranks are loaded from LuckTAB’s prefix list.
Badges & secondary tags
LuckTAB can show extra LuckPerms groups through%lucktab_badges% and %chatBadges%, even when another group owns the main prefix.Select a player
Choose a player on the left to manage them without typing server commands.
Player
Unknown UUID
Quick actions
Gamemode
Server access
Rank
Move player
Coordinates
Inventory tools
Balance controls
Uses the installed Essence /eco administrator command.
Message player
Discipline
Moderation buttons use your configured LibertyBans command aliases.
Danger zone
These actions ask for confirmation before they run.
Player action history
RexWelcome designer
First-join broadcast
Title timing
Join sound
Select a plugin
Open any installed plugin to browse its configuration files and available options.
Configuration
Live server console
/logs/latest.log.Connect to MHQ SMP
Apply settings
Host this folder under your Pelican panel’s own HTTPS origin and keep the API key session-only. Do not publish a copy with a hard-coded key.
Integration details
GET /api/client/servers/{server}/resources
GET /api/client/servers/{server}/websocket
GET /api/client/servers/{server}/files/list?directory=…
GET /api/client/servers/{server}/files/contents?file=…
POST /api/client/servers/{server}/files/write
POST /api/client/servers/{server}/command
POST /api/client/servers/{server}/power