Overview
PER WORLD PLUGINS
Control plugin events, commands, and chat in every world from one clean GUI.
Version 3.2 | GUI Configuration | Optional PlaceholderAPI Support
A DIFFERENT EXPERIENCE IN EVERY WORLD Per World Plugins (HPWP) gives multi-world servers fine-grained control over where plugin features are available. Configure every loaded world through an intuitive inventory GUI or edit the generated YAML files directly. Run a survival world, creative world, lobby, event world, and minigames on the same server while keeping standard plugin events and commands where they belong. FEATURES
- Per-world plugin control - Filter standard Bukkit events and plugin-owned commands in selected worlds.
- Complete in-game GUI - Configure global options, worlds, plugins, and chat tunnels without hand-editing YAML.
- Blacklist and whitelist modes - Disable only selected plugins or allow only selected plugins in a world.
- Fast bulk controls - Enable or disable all listed plugins, then fine-tune individual choices.
- Automatic world discovery - Browse worlds currently loaded by Bukkit and refresh after adding worlds or plugins.
- Chat tunnels - Group worlds into separate chat channels so only players in the same tunnel receive each other's messages.
- Optional tunnel labels - Add a configurable prefix to chat messages so players can see where a message came from.
- PlaceholderAPI integration - Use
%pwp-chat_tunnel%to display the player's current tunnel format. - YAML configuration - Every setting remains available in readable configuration files.
- No required dependencies - PlaceholderAPI support is completely optional.
- Survival and creative worlds on one server
- Lobby, event, and minigame worlds
- Worlds that need different gameplay plugins
- Networks that want local chat groups without another required dependency
- Administrators who prefer a GUI but still want editable configuration files
- Stop your server.
- Place
HPWP-3.2.jarin the server'spluginsfolder. - Optionally install PlaceholderAPI if you want to use the tunnel placeholder.
- Start the server and run
/pwp gui. - Open Worlds' Config, choose a world, and select which plugins should be enabled there.
- Changes made through the GUI are saved automatically. Restart the server after manual YAML edits so they are reloaded.
/hpwpor/pwp- Show command help./pwp gui- Open the configuration GUI./pwp events PLUGIN_NAME- List the Bukkit events registered by a plugin./pwp togglechat- Toggle between tunnel chat and global chat for yourself.
hpwp.gui- Use/pwp gui. Default: operators.hpwp.events- Use/pwp events. Default: operators.hpwp.toggle.chat- Use/pwp togglechat. Default: operators.hpwp.notify- Receive update notifications. Default: operators.hpwp.bypass.chat- Use global chat instead of tunnel-restricted chat. Default: false.hpwp.*- Grants the GUI, events, and notification permissions. Default: operators.hpwp.bypass.*- Grants all declared HPWP bypass permissions. Default: false.
plugins/HPWP/:
global.yml- Global messages and notification settings.chat_tunnels.yml- Tunnel definitions, formats, and chat options.WORLD_NAME.yml- Per-world plugin mode, plugin list, allowed events, and selected chat tunnel.
%pwp-chat_tunnel%%pwp-chat_tunnel% placeholder.
Can I configure HPWP without editing files?
Yes. Run /pwp gui to manage global settings, chat tunnels, and per-world plugin choices.
Why does part of a disabled plugin still run?
That feature may use a scheduler, background task, or another mechanism that is not tied to a Bukkit event or command. See the filtering explanation above.
SUPPORT
For the fastest help, include your server software and version, Java version, HPWP version, the plugin you are filtering, the relevant world configuration, and any console errors when posting in the resource Discussion tab.
PRIVACY
HPWP includes bStats for anonymous usage statistics. Server owners can disable bStats through the shared bStats configuration.
Build each world your way with HPWP.
[/CENTER
Product Options
Product Type
Plugin
Lifecycle
Stable
Compatibility
PaperSpigot
26.326.226.11.21.11