# WorldProtection<\/p>\n
A comprehensive world protection plugin for Paper\/Spigot servers that allows administrators to protect specific worlds with a whitelist system. Even operators are blocked from accessing protected worlds unless explicitly whitelisted.<\/p>\n
## Features<\/p>\n
### Core Features ### Security Features ## Requirements<\/p>\n – Paper 1.21.x or compatible ## Installation<\/p>\n 1. Download the latest JAR from the releases page ## Configuration<\/p>\n ### config.yml<\/p>\n “`yaml # Default message when access is denied # Block operators from accessing protected worlds (unless whitelisted) # Kick players who try to access protected worlds # Safe world to teleport players to when access is denied (if kick_on_deny is false) # Kick message when player is not whitelisted ### Configuration Options<\/p>\n **messages** **block_operators** **kick_on_deny** **safe_world** **kick_message** ## Commands<\/p>\n ### Player Commands<\/p>\n **\/worldprotection go ### Admin Commands<\/p>\n All admin commands require `worldprotection.admin` permission (default: OP).<\/p>\n **\/worldprotection toggle **\/worldprotection whitelist **\/worldprotection whitelist **\/worldprotection list** or **\/wp list** **\/worldprotection info **\/worldprotection reload** or **\/wp reload** ## Permissions<\/p>\n **worldprotection.admin** **worldprotection.bypass** ## Usage Examples<\/p>\n ### Protecting a World<\/p>\n 1. Protect a world: 2. Whitelist players: 3. Check protection status: ### Unprotecting a World<\/p>\n 1. Remove protection: 2. Note: Whitelist is preserved but not enforced when world is unprotected<\/p>\n ### Managing Whitelist<\/p>\n **Add a player:** **Remove a player:** **View all protected worlds:** ## How It Works<\/p>\n ### Protection Mechanism<\/p>\n When a player attempts to access a protected world, the plugin:<\/p>\n 1. **Checks if world is protected** 2. **Checks if player is whitelisted** 3. **Checks bypass permission** 4. **Blocks access if all checks fail** ### Access Methods Blocked<\/p>\n The plugin blocks access through:<\/p>\n – **World Changes**: When a player changes worlds (via any method) ### Operator Blocking<\/p>\n Operators are handled specially: ### Data Storage<\/p>\n Protected worlds and whitelists are stored in: This file is automatically created and updated when: ## File Structure<\/p>\n “` ## Troubleshooting<\/p>\n **Operators can still access protected worlds:** **Players can still access protected worlds:** **Whitelist not working:** **Players getting stuck:** **Multiverse worlds not working:** ## Security Considerations<\/p>\n ### Operator Blocking<\/p>\n By default, operators are blocked from accessing protected worlds. This is intentional and provides additional security:<\/p>\n – Prevents accidental access by admins To allow operators access, you must: **Important**: Even if `kick_on_deny` is enabled, operators are teleported instead of kicked, as server protections may prevent kicking operators.<\/p>\n ### Bypass Permission<\/p>\n The `worldprotection.bypass` permission exists for special cases but: ## API<\/p>\n ### Public Methods<\/p>\n “`java \/\/ Check if a player is whitelisted for a world \/\/ Check if a player can access a world ### Events<\/p>\n The plugin listens to and handles: ## Version<\/p>\n Current Version: 1.0.0<\/p>\n ## Support<\/p>\n For issues, feature requests, or questions, please open an issue on the project repository.<\/p>\n ## License<\/p>\n This plugin is provided as-is for use on Minecraft servers.<\/p>\n ## Credits<\/p>\n Developed for Paper 1.21.x servers with optional Multiverse-Core integration.<\/p>\n","protected":false},"excerpt":{"rendered":" A comprehensive world protection plugin that allows administrators to protect specific worlds with a whitelist system<\/p>\n","protected":false},"featured_media":101686,"template":"","meta":{"_minecraft_slug":"worldprotection","_minecraft_project_id":"ESAr41Z7","_minecraft_author":"sidastuff","_minecraft_license":"LicenseRef-All-Rights-Reserved","_minecraft_downloads":89,"_minecraft_follows":1,"_minecraft_client_side":"unsupported","_minecraft_server_side":"required","_minecraft_storage_type":"zip","_minecraft_archive_name":"worldprotection.zip","_minecraft_size_bytes":9671,"_minecraft_version_count":1,"_minecraft_updated_at":"2026-05-15T19:58:43.489092Z","_minecraft_date_created":"2025-12-14T01:24:08.540030Z","_minecraft_date_modified":"2025-12-09T15:32:39.468180Z","_minecraft_project_url":"https:\/\/modrinth.com\/mod\/worldprotection","_minecraft_icon_attachment_id":101686,"_minecraft_imported_at":"2026-06-09T21:31:58+00:00","_minecraft_import_hash":"1af0b7600352589fdb6ea786207d9d2b","_minecraft_versions":"","_minecraft_links":"","_minecraft_gallery":"","_minecraft_api_metadata":""},"mod_category":[87,124,89,126,127,129,91,869,92],"mod_loader":[130,132,134],"minecraft_version":[40,41,38,78,79,80,81,82],"class_list":["post-171590","mod","type-mod","status-publish","has-post-thumbnail","hentry","mod_category-adventure","mod_category-bukkit","mod_category-game-mechanics","mod_category-management","mod_category-paper","mod_category-spigot","mod_category-storage","mod_category-transportation","mod_category-utility","mod_loader-bukkit","mod_loader-paper","mod_loader-spigot","minecraft_version-1-21-10","minecraft_version-1-21-11","minecraft_version-1-21-4","minecraft_version-1-21-5","minecraft_version-1-21-6","minecraft_version-1-21-7","minecraft_version-1-21-8","minecraft_version-1-21-9"],"yoast_head":"\n
\n– **World Protection Toggle**: Enable or disable protection on any world
\n– **Whitelist System**: Only whitelisted players can access protected worlds
\n– **Operator Blocking**: Blocks operators from accessing protected worlds (unless whitelisted)
\n– **Case-Insensitive World Lookup**: World names are matched case-insensitively for convenience
\n– **Player Teleport Command**: `\/wp go
\n– **Multiple Access Methods Blocked**: Prevents access via:
\n – World changes
\n – Teleportation commands
\n – Portal usage (nether portals, end portals, etc.)
\n – Direct world joining
\n– **Data Persistence**: Protected worlds and whitelists are saved automatically
\n– **Config Reload**: Reload configuration without restarting server
\n– **Multiverse Support**: Compatible with Multiverse-Core (soft dependency)<\/p>\n
\n– Operators are blocked by default (configurable)
\n– Operators are always teleported away (kicks may not work on ops)
\n– Bypass permission available but still respects operator blocking
\n– Automatic teleportation to safe world when access is denied
\n– Configurable safe world for teleportation
\n– Optional kick on access denial (default: enabled)
\n– Customizable kick message<\/p>\n
\n– Java 21
\n– Multiverse-Core (optional, for Multiverse world management)<\/p>\n
\n2. Place `WorldProtection-1.0.0.jar` in your server’s `plugins\/` folder
\n3. Start or restart your server
\n4. Configure `plugins\/WorldProtection\/config.yml` to your preferences
\n5. Use `\/wp toggle
\n6. Use `\/wp whitelist
\n# World Protection Configuration<\/p>\n
\nmessages:
\n prefix: “&c[WorldProtection]&f ”
\n access_denied: “&cYou do not have permission to access this world!”
\n world_protected: “&eWorld &6%world% &eis protected. Only whitelisted players can access it.”
\n world_unprotected: “&aWorld &6%world% &ais now unprotected.”
\n world_protected_enabled: “&aWorld &6%world% &ais now protected.”
\n player_whitelisted: “&aPlayer &e%player% &ahas been whitelisted for world &6%world%&a.”
\n player_unwhitelisted: “&cPlayer &e%player% &ahas been removed from whitelist for world &6%world%&c.”
\n not_whitelisted: “&cYou are not whitelisted for world &6%world%&c.”
\n world_not_found: “&cWorld &6%world% &cnot found!”
\n no_worlds_protected: “&7No worlds are currently protected.”
\n teleport_success: “&aTeleported to world &6%world%&a.”
\n teleport_denied: “&cYou do not have permission to teleport to world &6%world%&c.”<\/p>\n
\nblock_operators: true<\/p>\n
\nkick_on_deny: true<\/p>\n
\n# Leave empty to auto-find a safe world
\nsafe_world: “”<\/p>\n
\nkick_message: “&4You are not whitelisted on this world”
\n“`<\/p>\n
\n– All messages can be customized with color codes
\n– Use `%world%` placeholder for world names
\n– Use `%player%` placeholder for player names<\/p>\n
\n– `true`: Operators are blocked from protected worlds (unless whitelisted)
\n– `false`: Operators can access protected worlds (not recommended)<\/p>\n
\n– `true`: Players are kicked when they try to access a protected world (default)
\n– `false`: Players are teleported back to a safe world
\n– Note: Operators are always teleported (kicks may not work on ops)<\/p>\n
\n– Name of the world to teleport players to when access is denied and `kick_on_deny` is `false`
\n– Leave empty (`””`) to automatically find a safe world
\n– Must be a valid world name<\/p>\n
\n– Custom message shown when a player is kicked for accessing a protected world
\n– Supports color codes (use `&` prefix)
\n– Default: `”&4You are not whitelisted on this world”`<\/p>\n
\n– Teleport to a world (available to all players)
\n– Blocks teleportation if the world is protected and you’re not whitelisted
\n– Example: `\/wp go creative`
\n– Note: World names are case-insensitive<\/p>\n
\n– Enable or disable protection on a world
\n– Example: `\/wp toggle creative`
\n– Note: World names are case-insensitive<\/p>\n
\n– Add a player to the whitelist for a protected world
\n– Example: `\/wp whitelist creative add PlayerName`
\n– Note: World names are case-insensitive<\/p>\n
\n– Remove a player from the whitelist for a protected world
\n– Example: `\/wp whitelist creative remove PlayerName`
\n– Note: World names are case-insensitive<\/p>\n
\n– List all currently protected worlds
\n– Shows the number of whitelisted players per world<\/p>\n
\n– Show detailed information about a world’s protection status
\n– Displays protection status and whitelisted players
\n– Note: World names are case-insensitive<\/p>\n
\n– Reload the configuration file and data
\n– Requires admin permission
\n– Example: `\/wp reload`<\/p>\n
\n– Full admin access to all world protection commands
\n– Default: `op` (operators only)
\n– Allows: toggle protection, manage whitelist, view info<\/p>\n
\n– Bypass world protection (not recommended)
\n– Default: `op` (operators only)
\n– Note: Still blocked if `block_operators: true` in config<\/p>\n
\n “`
\n \/wp toggle creative
\n “`
\n Output: `[WorldProtection] World creative is now protected.`<\/p>\n
\n “`
\n \/wp whitelist creative add PlayerName
\n \/wp whitelist creative add AnotherPlayer
\n “`<\/p>\n
\n “`
\n \/wp info creative
\n “`<\/p>\n
\n “`
\n \/wp toggle creative
\n “`
\n Output: `[WorldProtection] World creative is now unprotected.`<\/p>\n
\n“`
\n\/wp whitelist creative add PlayerName
\n“`<\/p>\n
\n“`
\n\/wp whitelist creative remove PlayerName
\n“`<\/p>\n
\n“`
\n\/wp list
\n“`<\/p>\n
\n – If not protected, access is allowed<\/p>\n
\n – If whitelisted, access is allowed<\/p>\n
\n – If player has `worldprotection.bypass`, access is allowed
\n – Exception: If `block_operators: true` and player is OP, still blocked<\/p>\n
\n – If `kick_on_deny: true`: Kicks player with configured kick message
\n – If `kick_on_deny: false`: Teleports player to safe world (configured or auto-found)
\n – Operators are always teleported away (kicks may not work on ops)
\n – Sends access denied message
\n – Multiple event handlers ensure blocking works regardless of access method<\/p>\n
\n– **Player Join**: When a player joins the server in a protected world
\n– **Teleportation**: All teleportation commands and events (including `\/wp go`)
\n– **Portals**: Nether portals, end portals, and other portal types<\/p>\n
\n– They are always blocked from protected worlds (when `block_operators: true`)
\n– They are always teleported away (kicks may not work on operators)
\n– Multiple event handlers ensure operators cannot stay in protected worlds
\n– Even if a kick fails, operators are immediately teleported to a safe world<\/p>\n
\n“`
\nplugins\/WorldProtection\/data.yml
\n“`<\/p>\n
\n– Worlds are protected\/unprotected
\n– Players are added\/removed from whitelists<\/p>\n
\nplugins\/WorldProtection\/
\n\u251c\u2500\u2500 config.yml # Configuration file
\n\u2514\u2500\u2500 data.yml # Protected worlds and whitelists (auto-generated)
\n“`<\/p>\n
\n– Check `block_operators` in config.yml (should be `true`)
\n– Ensure operators are not whitelisted
\n– Verify they don’t have `worldprotection.bypass` permission
\n– Operators should be teleported away immediately – if not, check server logs
\n– Try using `\/wp go
\n– Check if world is actually protected: `\/wp list`
\n– Verify player is not whitelisted: `\/wp info
\n– Check if player has bypass permission<\/p>\n
\n– Ensure world is protected: `\/wp toggle
\n– Verify player was added correctly: `\/wp info
\n– Check data.yml file for correct UUIDs<\/p>\n
\n– If a player is in a protected world when protection is enabled, they will be teleported out immediately
\n– Use `\/wp whitelist
\n– Or temporarily unprotect the world: `\/wp toggle
\n– Players can use `\/wp go
\n– Ensure Multiverse-Core is installed (optional but recommended)
\n– World names are matched case-insensitively, so you can use any case
\n– Use `\/mv list` to see world names, but you can use any case variation<\/p>\n
\n– Ensures only explicitly whitelisted players can access
\n– Maintains strict access control
\n– Operators are always teleported away (kicks may not work on operators)
\n– Multiple event handlers ensure operators cannot bypass protection<\/p>\n
\n1. Whitelist them: `\/wp whitelist
\n2. Or set `block_operators: false` in config.yml (not recommended)<\/p>\n
\n– Still respects `block_operators` setting
\n– Should be used sparingly
\n– Consider whitelisting instead for better tracking<\/p>\n
\n\/\/ Check if a world is protected
\nboolean isWorldProtected(String worldName)<\/p>\n
\nboolean isPlayerWhitelisted(UUID playerUUID, String worldName)<\/p>\n
\nboolean canAccessWorld(Player player, String worldName)
\n“`<\/p>\n
\n– `PlayerJoinEvent` – Blocks players joining in protected worlds
\n– `PlayerChangedWorldEvent` – Blocks world changes
\n– `PlayerTeleportEvent` – Blocks teleportation
\n– `PlayerPortalEvent` – Blocks portal usage<\/p>\n