PerRegionChat: Region-Based Chat for Minecraft Servers

Understanding PerRegionChat: Localized Communication for Minecraft Servers Running a multiplayer Minecraft server often means managing a global chat where every player sees every message. While this works for small communities, larger servers with distinct areas—like spawn towns, minigame zones, ...

Download PerRegionChat for Minecraft 1.16, 1.14

Original name: PerRegionChat

Minecraft: 1.14, 1.16

FileVersionLoaderSize
PerRegionChat-1.0.jar1.14—6 КБDownload
PerRegionChat-1.0-SNAPSHOT.jar1.14—8 КБDownload
PerRegionChat-1.2.jar1.14—7 КБDownload
PerRegionChat-1.3.jar1.16—11 КБDownload

Understanding PerRegionChat: Localized Communication for Minecraft Servers

Running a multiplayer Minecraft server often means managing a global chat where every player sees every message. While this works for small communities, larger servers with distinct areas—like spawn towns, minigame zones, or roleplay regions—can quickly become chaotic. PerRegionChat solves this by introducing region-based chat restrictions, allowing you to create isolated communication channels tied directly to WorldGuard regions. If you have ever wished that players inside a castle could talk privately without cluttering the global chat, this plugin delivers exactly that.

What Is PerRegionChat?

PerRegionChat is a lightweight Spigot/Paper plugin that integrates with WorldGuard to add a custom region flag called restrict-chat. When this flag is enabled on a region, any chat message sent from within that area will only be visible to other players who are also inside the same region. Players outside the region will not see those messages, and by default, they cannot send messages into the restricted zone either. This creates a natural, localized chat experience that feels organic to the game world.

The plugin does not alter the appearance of messages. It simply modifies the recipient list, so any chat formatting plugins you already use—such as Essentials Chat or VentureChat—will continue to style messages exactly as you have configured them. This makes PerRegionChat a seamless addition to an existing server setup without breaking your established chat aesthetics.

Key Features at a Glance

  • Adds the restrict-chat WorldGuard flag to any defined region.
  • Chat messages from within a restricted region are only delivered to players in that same region.
  • Optionally restrict team chat commands (/teammsg and /tm) to the sender's current region.
  • Bypass permissions allow specific players to send or receive messages across all regions.
  • Configurable default behavior for newly created regions.
  • Full compatibility with chat formatting plugins—only the audience changes, not the message style.
  • Simple reload command to apply configuration changes without restarting the server.

How Region-Restricted Chat Works

Once you have WorldGuard installed and your regions defined, PerRegionChat adds a new flag to each region. You can set it with a simple command: /region flag restrict-chat allow. From that moment, any player standing inside that region who types in public chat will have their message broadcast exclusively to others within the same region boundaries. Players in a different region, or in the global wilderness, will not see the message. This is perfect for creating private marketplaces, faction headquarters, or event areas where you want focused conversation.

By default, unrestricted chat (messages sent from outside any restricted region) will not be visible to players inside a restricted region. This prevents outside noise from leaking in. However, you can change this in the configuration file if you prefer a one-way communication flow. The plugin also offers an option to override the vanilla team chat commands, making /teammsg and /tm respect region boundaries. If you enable this, team messages will only reach teammates who are in the same region as the sender, adding another layer of tactical communication for team-based games.

Configuration and Customization

PerRegionChat’s config.yml is straightforward, with only a few settings to adjust. The main options include:

  • Restrict chat by default: When set to true, every new region automatically gets the restrict-chat flag enabled. The default is false, so you must manually flag regions you want to isolate.
  • Send unrestricted chat to restricted regions: If true, players inside a restricted region will still see global chat from outside. This can be useful for keeping everyone informed while allowing localized replies.
  • Override vanilla /teammsg and /tm commands: When enabled, the plugin registers its own versions of these commands that check region restrictions. The vanilla commands remain accessible via /minecraft:teammsg if needed.

After editing the config, a quick /prc reload applies the changes instantly—no server restart required. For server admins who prefer a unified management tool, the foxygame.net launcher provides a convenient way to add PerRegionChat to your server, letting you browse and install plugins directly from its intuitive menu. This modern launcher streamlines the process, so you can focus on building your world rather than wrestling with file uploads.

Permissions for Fine-Tuned Control

PerRegionChat includes several permission nodes that let you grant exceptions to trusted players or staff. These are essential for maintaining oversight while keeping the chat system intact.

  • perregionchat.bypass.send — Allows a player to send messages that will be received by everyone, regardless of region restrictions. Ideal for moderators making server-wide announcements.
  • perregionchat.bypass.receive — Lets a player see chat from all regions, even if they are standing in an unrestricted area. Useful for admins who need to monitor conversations.
  • perregionchat.command.reload — Grants access to the /prc reload command for refreshing the configuration.
  • perregionchat.command.teammsg — Permits use of the plugin’s overridden /teammsg and /tm commands. Without this, players will fall back to the vanilla commands if the override is enabled.

These permissions can be assigned via your usual permission plugin (LuckPerms, PermissionsEx, etc.) and give you granular control over who can break the regional chat boundaries.

Compatibility and Dependencies

PerRegionChat is designed for Minecraft versions 1.14 and 1.15, though it may work on newer releases if the WorldGuard API remains consistent. The only hard dependency is WorldGuard itself—you must have it installed and properly configured with at least one defined region. The plugin does not interfere with other chat managers; it simply adjusts the set of recipients before the message is formatted and dispatched. This means your carefully designed chat colors, prefixes, and suffixes from plugins like Essentials Chat or DeluxeChat will remain untouched.

If you are running a large network with multiple game modes, PerRegionChat can be deployed on each server instance independently. The configuration is per-server, so you can tailor the behavior to each world’s needs. The plugin is also lightweight, adding negligible overhead to server performance.

Practical Use Cases

Imagine a medieval roleplay server where the king’s castle, the village market, and the dark forest each have their own chat channels. Players inside the castle can discuss court matters without villagers overhearing, while traders in the market haggle in their own space. Or consider a minigame hub where each game lobby is a separate region—players waiting for a match can chat among themselves without distracting others. PerRegionChat makes these scenarios possible with minimal configuration.

For faction or survival servers, you can designate each faction’s claimed land as a restricted chat zone, encouraging members to communicate privately while in their base. Combined with the team chat override, you can even ensure that tactical commands stay within the region, adding a layer of realism to coordinated attacks.

Getting Started with PerRegionChat

Installation is simple. Download the plugin JAR file and place it in your server’s plugins folder. Ensure WorldGuard is already installed and running. Restart the server, and PerRegionChat will generate its default config. Then, use WorldGuard commands to flag your regions. For example, if you have a region named spawn, run /region flag spawn restrict-chat allow. Immediately, chat inside spawn becomes localized. You can test it by having two players stand in different regions and typing messages.

If you want to change the default behavior, edit the config.yml and reload with /prc reload. Assign bypass permissions to staff as needed. The plugin is intentionally minimal, so you can set it up in minutes and let it run quietly in the background.

Conclusion

PerRegionChat fills a niche that many server owners didn’t realize they needed until they experienced the clutter of a fully global chat. By tying communication to physical location, it enhances immersion, reduces spam, and gives players a sense of place. The integration with WorldGuard is seamless, and the permission system offers just enough flexibility without overcomplicating things. Whether you run a roleplay world, a minigame network, or a survival community, this plugin can help you craft a more organized and engaging chat environment. Give it a try, and watch your server’s social dynamics transform one region at a time.