Skip to main content

HUD Display

GroupManager integrates with HUD plugins to show real-time group information on the player's screen.

Supported HUD Plugins

PluginPriorityTypeDetection
MultipleHUD1 (highest)Reflection-basedAutomatic at startup
AutoMultiHud (by Buuz135)2Reflection-basedAutomatic at startup

GroupManager detects these plugins at startup. MultipleHUD is preferred when available; if not, the built-in manager (InternalMultiHud) is used as a fallback. If neither plugin is installed, the HUD still works out of the box via InternalMultiHud.

What the HUD Shows

The group HUD panel displays:

  • Group leader name (highlighted)
  • All group member names with optional prefix/suffix set by external plugins
  • Online/offline status indicators
  • Health bars for each member (via GroupHealthTracker)

The HUD updates in real-time as members join, leave, connect, or disconnect.

HUD Name Customization

External plugins can customize what appears next to each player's name via the prefix/suffix API:

GroupService api = GroupManagerProvider.get();
api.setHudPrefix(playerUuid, "[Lv.5] "); // Before the name
api.setHudSuffix(playerUuid, " [Warrior]"); // After the name
// HUD shows: "[Lv.5] Steve [Warrior] - Leader"

This is useful for RPG plugins (levels, classes, races), rank plugins, or any system that wants to display extra information alongside player names in the group HUD.

See the GroupService API reference for full details.

HUD Lifecycle

  • Created when a player joins a group.
  • Updated periodically and on group events (member join/leave, health changes).
  • Removed when the player leaves their group.
  • Paused/Resumed by external plugins via the API (e.g., during gameplay activities).

Pausing the HUD

External plugins can pause and resume the group HUD:

GroupService api = GroupManagerProvider.get();
api.pauseHud(playerUuid); // Hide during activity
api.resumeHud(playerUuid); // Restore after activity

MultipleHUD / AutoMultiHud Behavior

When MultipleHUD or AutoMultiHud is installed, pauseHud() and resumeHud() are automatic no-ops — GroupManager detects these mods at startup and skips these operations internally, since each plugin's HUD lives in its own isolated group and they coexist without interference.

This means external plugins can call pauseHud/resumeHud unconditionally — no HUD-mod detection code needed.

tip

See the HUD Compatibility page for more details on AutoMultiHud integration and full examples.