WorldManager

# WorldManager – MV Alternative WorldManager is a **modern world management plugin** for Paper servers, designed as a direct replacement and improvement over the long-standing Multiverse-Core. Built with the Paper 1.21 API and modern Java tooling, it provides a **fast, safe, and highly configurable system** for creating, importing, managing, and teleporting between worlds. Unlike legacy world managers, WorldManager fully embraces **asynchronous operations**, **per-world registries**, and **configurable rules**, ensuring performance, reliability, and ease of use. Nearly every feature is accessible through both direct commands and an intuitive in-game **/world GUI**, making it just as friendly for casual admins as for power users. --- ## 1. Philosophy and Goals WorldManager was developed to solve the common frustrations that many server administrators encounter with Multiverse-Core and similar plugins. The goals are: * **Modern Implementation**: Fully Paper 1.21 compatible, written with Java 21, and leveraging async APIs where possible. * **Ease of Use**: Centralized `/world` command with subcommands and GUI options. * **Safety First**: Built-in checks to prevent data loss or accidental deletions. * **Persistence**: Per-world settings stored in `worlds.yml` and reapplied automatically when worlds are reloaded. * **Configurability**: Messages, safety checks, GUI rows, teleport warmups, cooldowns, and per-world rules are all configurable. * **Extensibility**: Modular design, backups, and migration tools ensure the plugin can evolve without breaking worlds. In short: WorldManager is designed to be a **drop-in alternative to Multiverse-Core** that feels native to modern Paper servers. --- ## 2. Core Features ### 2.1 World Lifecycle Management WorldManager provides complete control over every stage of a world’s lifecycle. * **Create Worlds**: Instantly generate new worlds with `/world create <name> `. Supports NORMAL, NETHER, and THE\_END environments, plus optional parameters for seed, structures, and custom generators. * **Import Worlds**: Use `/world import <folder>` to bring existing world folders into the server. The process is asynchronous, providing progress percentages and ETA updates to prevent lag. * **Unload Worlds**: Free up server memory with `/world unload <world>`. Safety checks ensure no players are inside before unloading. * **Delete Worlds**: Permanently remove world folders from disk with `/world delete <world>`. Requires the world to be unloaded first. * **Backups and Migration**: Automatically creates timestamped backups of `worlds.yml` and offers `/world migrate` to update the schema safely. ### 2.2 Teleportation and Navigation Teleportation is a major component of world management, and WorldManager makes it seamless. * **Teleport Command**: `/world tp <world>` teleports you or another player directly to the spawn of a target world. * **Back Command**: `/world back` returns you to your previous location, swapping places with your current one. * **History Command**: `/world history` lists previous teleport locations for quick reference. * **Teleport Options**: Warmup timers, cooldowns, and movement cancellation are fully configurable. ### 2.3 World GUI All world operations are accessible through an in-game inventory GUI opened with `/world gui`. * Browse loaded worlds with icons, player counts, and environments. * Favorite worlds with `/world fav add <world>`, then access them quickly in the GUI. * Teleport directly from the GUI with a single click. * Configurable row size in `config.yml` ensures the GUI scales to the number of worlds. ### 2.4 Per-World Settings and Enforcement Each world can be customized with specific rules, enforced automatically by the plugin. * **GameRules**: Keep-inventory, random-tick speed, natural regeneration, mob griefing, fire tick, max entity cramming, and more. * **World Rules**: Gamemode, difficulty, PvP, spawn location, time lock, weather lock, keep-spawn-loaded. * **Mob Allowlist**: Restrict which mobs can spawn naturally in a given world. Changes are applied instantly with `/world config <world> <key> <value>` and persisted in `worlds.yml`. --- ## 3. Commands All commands are registered under `/world` (or alias `/wm`). Below is the full list of implemented subcommands: | Command | Description | Permission | | | | ---------------------------------------- | ---------------------------------------------- | -------------------------------------------- | ---------------------- | ------------------------ | | `/world list` | Lists all loaded worlds with player counts | `worldmanager.list` | | | | `/world info <world>` | Displays settings for a world