InvisibleRegionsRK

Reduce Visual Clutter in Crowded Areas

Is your spawn area crowded with players?

Large hubs and busy areas can become visually cluttered and may increase the rendering workload for players' clients. Minecraft must render every nearby player model, skin, armor piece, held item, and nametag.

InvisibleRegionsRK automatically hides players when they enter selected WorldGuard regions. It uses ProtocolLib packets to create a vanish-like effect without applying Minecraft's invisibility potion effect.

Please note: This plugin may reduce client-side rendering work and visual clutter in crowded areas. It does not guarantee higher server TPS.

Main Features

• Automatic invisibility inside selected WorldGuard regions
• Packet-based entity hiding through ProtocolLib
• No invisibility potion effects
• Hides the player model, vanilla nametag, armor, and held items
• Keeps invisible players visible in the TAB player list
• Detects WorldGuard regions across all loaded worlds
• Stores region states independently as world:region
• Provides an interactive, paginated region management GUI
• Stores region data in YAML
• Creates backups before changing saved region data
• Supports priorities for overlapping regions
• Provides VIP bypass and staff visibility permissions
• Includes a temporary manual visibility override
• Offers optional, editable chat or action-bar notifications
• Includes a notification cooldown to prevent message spam
• Provides an optional PlaceholderAPI integration for custom nametag plugins

How It Works

When a player enters an enabled region, InvisibleRegionsRK sends entity-removal packets to other clients. While that player remains invisible, the plugin filters outgoing spawn, movement, equipment, and metadata packets to prevent the entity from reappearing after chunk updates or reconnections.

When the player leaves the region, their entity and equipment are restored automatically.

Players with the invisiblerk.see permission are excluded from the packet filter and can always see invisible players.

Dependencies

Required:

• WorldGuard
• ProtocolLib

Optional:

• PlaceholderAPI - required only for custom nametag integrations
• UnlimitedNameTags - supported through the provided PlaceholderAPI condition

Commands

Manual toggle behavior:

• If the target player is invisible, the command forces them to become visible.
• If the target player is visible, the command forces them to become invisible.
• The manual override is cleared when the player disconnects.

Permissions

• invisiblerk.admin - access to the GUI and administrative commands
• invisiblerk.toggle - access to the manual toggle command
• invisiblerk.see - always see invisible players
• invisiblerk.vip.bypass - never become invisible automatically

Default Region Behavior

WorldGuard regions are detected automatically but remain disabled by default. This prevents all existing regions from becoming invisibility zones immediately after installation.

You can enable regions from the GUI or configure selected regions to start enabled:

In this example, only the region named spawn starts enabled. All other detected regions remain disabled until an administrator enables them.

Optional Notifications

Player notifications are disabled by default and can be enabled at any time:

UnlimitedNameTags Integration

When PlaceholderAPI is installed, InvisibleRegionsRK registers the following placeholder:

It returns true when the player is invisible and false when the player is visible.

Apply this modifier to every UnlimitedNameTags line group that should disappear with the player:

Vanilla nametags and standard TAB plugin nametags disappear automatically with the player entity. The additional condition is needed only for plugins that create separate display entities for their nametags.


Important: Do not use Bukkit's global /reload command. Restart the server completely after installing or replacing the plugin.


Always test the plugin on a staging server before using it in production, especially after updating Minecraft, ProtocolLib, or WorldGuard.

Support Requests

When reporting a problem, please include:

• Minecraft server version
• Server software and build number
• ProtocolLib version
• WorldGuard version
• InvisibleRegionsRK configuration
• Relevant console errors or warnings
• Clear steps to reproduce the problem