# Wraids – say NO to raid farms!
If you want to prevent players from using raid farms on your server, this is for you!
This plugin spawns a Vex on every new raid wave to prevent the player from standing AFK on the raid farm.
# WorldTP
## The simplest world management plugin.
**Teleport, list, and delete worlds with clean commands — fast, lightweight, and easy to use.**
_Usage:_
> – /wtp tp
> – /wtp tp
> – /wtp list
> – /wtp delete
**No bloat. Just simple world control.**
*Currently only available on versions 1.19-1.21+.* _More version support available if needed (join the discord)_
# Detailed Introduction to Minecraft WorldTag Plugin
WorldTag is a lightweight identification plugin specially developed for Minecraft servers. Its core positioning is to realize the associated visualization of players’ names and their current worlds, while balancing practicality, convenience and server performance optimization. It does not rely on any redundant dependency plugins, supports the deployment of Minecraft servers of all scales, provides server administrators with an efficient and flexible world identification management solution, and enhances the interactive experience between players.
## Where can I use WorldTag?
## Detailed Explanation of Core Features
As a dedicated plugin focusing on world identification display, WorldTag abandons redundant functions and focuses on the accurate implementation of core needs. Every function is optimized and designed to balance ease of use and stability.
### 1. Automatic Mounting of Player Name World Tags
The core function of the plugin is to automatically add an identification tag corresponding to the current world before players’ names, realizing intuitive visualization of players’ locations. Whenever players switch between different worlds on the server, the tags will be updated in real time without manual operation by administrators. This allows all online players to quickly identify the current world location of target players, facilitating cross-world interaction guidance between players, helping administrators quickly locate players’ scenarios, and improving server management efficiency.
### 2. Customizable Adaptation of Tag Text and Color
The plugin supports highly flexible tag customization. Server administrators can freely configure the display text and color parameters of each world tag according to their server’s operation style and world themes (such as Survival World, Creative World, Dungeon World, etc.). Through simple configuration operations, the tag text can be accurately matched with the server’s world names. Meanwhile, color parameters can be used to distinguish different world types, enhancing the recognition of tags, making world tags not only practical but also consistent with the overall visual style of the server.
### 3. Comprehensive Fault-Tolerance Adaptation Mechanism
To ensure the stable operation of the plugin, WorldTag has built-in intelligent fault-tolerance logic with special optimization for abnormal configuration file scenarios. When the plugin reads the configuration file, if it cannot recognize the target world folder on the server (such as abnormal folder naming, path changes, missing world files, etc.), it will automatically trigger the fault-tolerance mechanism and display the corresponding world tag as [Unknown]. This design can effectively avoid plugin errors, crashes or display disorders caused by configuration abnormalities, ensuring the plugin runs normally in various complex configuration environments.
## Core Advantages of the Plugin
### Lightweight Design with Low Resource Consumption
The plugin adopts a streamlined development logic, eliminating all non-core redundant code for an extremely compact size. It occupies minimal server resources during operation and does not impose any additional burden on server performance indicators such as TPS. It supports various deployment scenarios including small private servers and large public servers, and runs smoothly even on servers with limited resource configurations.
### Zero Dependencies for Easy Deployment
WorldTag does not require the installation of any extra dependency plugins or libraries. After downloading the plugin file, you can directly put it into the server plugin directory to complete deployment, without complex configuration and debugging. This greatly reduces the deployment cost and operation difficulty for server administrators. Both novice administrators and senior operation and maintenance personnel can quickly install and enable the plugin to implement world tag functions rapidly.
## Applicable Scenarios and Summary
WorldTag is suitable for all Minecraft servers with a multi-world architecture, whether it is a comprehensive server with coexisting modes such as Survival, Creative and Adventure, or a dedicated server focusing on specific gameplay. The plugin can realize standardized display of world identifications. Its features of lightweight, zero dependencies and high fault tolerance perfectly solve the pain points of inconvenient player world positioning and unclear identification in multi-world servers, while balancing server performance and management convenience.
In conclusion, WorldTag is a “small yet sophisticated” dedicated identification plugin. Guided by core functions and based on stability, it can add practical world identification functions to the server without complex operations. It not only improves the interactive experience of players but also helps administrators optimize server management efficiency, making it an ideal auxiliary plugin for multi-world Minecraft servers.
## Where can we get WorldTag?
[](https://github.com/Hi-PolarBear/WorldTag)[](https://modrinth.com/plugin/worldtag)[](https://hangar.papermc.io/Hi-PolarBear/WorldTag)
***
WorldSystem is a plugin where every player can get a world.
There they can do anything they want without creating stress in a single world.
The world owner can also add other players and manage their permissions on his world.
When a player creates a new world you can also set a template which will then be cloned.
Many answers about optimization and installation are available on the wiki.
# WorldSlim
Reduce Minecraft world file size by automatically cleaning chunks that players barely visit. Three layers of defense catch what vanilla autosave would otherwise commit to disk.
—
## What it does
Modern Minecraft (1.18+) keeps chunks loaded much longer than a player’s view distance, and autosave writes them all to disk regardless of activity. WorldSlim hooks every layer of that pipeline:
1. **ChunkUnloadListener** — when a chunk does unload, intercept the save if `InhabitedTime` is low.
2. **AutosaveShield** *(new in 2.0)* — every 2 seconds, pre-emptively clear the dirty flag on loaded low-`InhabitedTime` chunks so autosave skips them.
3. **ChunkCleaner** — periodically rewrite region files, removing chunks that slipped through the first two layers.
Player activity (placing blocks, attacking mobs, opening containers, picking up / dropping items) marks chunks as “force-save” so they survive cleanup.
—
## Highlights
– **Three-layer architecture** — unload + autosave + region rewrite. Aggressive without being unsafe.
– **File-based ChunkRegistry** — managed/force-save state stored in `plugins/WorldSlim/data/`, survives server restarts and Leaf/Moonrise’s chunk-PDC strip. Crash-safe (lost marks degrade to “leave it alone”).
– **Aggressive mode** *(`cleanup.aggressive: true`)* — restores the pre-1.0.6 cleanup logic, achieves 90%+ cleanup rate on fresh servers. Off by default to protect builds on established worlds.
– **Diagnostics** — `/worldslim diagnose` for runtime counters, `/worldslim scan` for raw-NBT inspection of any region file, `/worldslim chunk` for full decision-tree of the chunk you’re standing in.
– **Daily-rotating file logger** at `plugins/WorldSlim/logs/`, configurable level.
– **Config migration** *(new in 2.0.1)* — new fields auto-injected on upgrade, preserving your edits and comments.
– **Async + bounded** — every disk operation runs off the main thread, with a 5-second timeout that safely skips when the server is busy.
—
## Compatibility
| Server | PDC Persistence | Registry | AutosaveShield |
|——–|—————–|———-|—————-|
| Paper 1.21.x | Yes | Yes | Yes |
| Purpur 1.21.x | Yes | Yes | Yes |
| Folia 1.21.x | Yes | Yes | Partial |
| Leaves 1.21.x | Yes | Yes | Yes |
| Leaf 1.21.x | Stripped | **Load-bearing** | Limited |
Requires Minecraft 1.21.x and Java 21.
—
## Commands
| Command | Description |
|———|————-|
| `/worldslim status` | Show plugin status and active configuration |
| `/worldslim stats` | Total chunks scanned/cleaned and space saved |
| `/worldslim chunk` | Full decision tree for the chunk you’re standing in |
| `/worldslim cleanup` | Run a cleanup pass immediately |
| `/worldslim diagnose [here]` | Runtime diagnostic snapshot. Append `here` for current-chunk details |
| `/worldslim scan` | Parse the current region file’s raw NBT and report what tags survived |
| `/worldslim reload` | Reload `config.yml` (also runs config migration) |
| `/worldslim reset` | Reset cleanup statistics |
Aliased to `/ws`. Permission: `worldslim.admin` for mutating commands; `worldslim.use` for the read-only ones.
—
## Quick start
1. Drop the jar in `plugins/`, restart.
2. Default config is conservative (preserves any chunks that look pre-existing). Works without configuration on most servers.
3. **On a fresh server** — set `cleanup.aggressive: true` for the best cleanup rate.
4. **On an established server with builds** — leave `aggressive: false` (default) and let the registry track new chunks going forward.
—
## Configuration highlights
“`yaml
# Chunk lifetime threshold. Below this, chunks may be cleaned.
# Default 1200 ticks = 60 seconds.
min-inhabited-time: 1200
cleanup:
interval-minutes: 30
run-on-startup: false
# Pre-1.0.6 cleanup behavior. Highly recommended for fresh servers.
aggressive: false
autosave-shield:
enabled: true
interval-ticks: 40 # 2s
logging:
file-enabled: true
level: INFO # DEBUG / INFO / WARN / ERROR
worlds:
enabled: [] # if non-empty, ONLY these worlds are managed
disabled: [] # always-skipped worlds
“`
Full default config (with all comments) is generated on first run.
—
## Reporting issues
Please include:
– `/worldslim diagnose` screenshot
– Latest log from `plugins/WorldSlim/logs/`
– Server type and version
**🌎 WorldsColors** brings visual clarity and style to your Minecraft server by automatically coloring player nicknames depending on the dimension they are in.
Make Nether inhabitants glow in intimidating red, let Overworld adventurers keep a clean look, and give End explorers a soft, mystical pink — all fully automated and seamless.
**✨ Key Features**
Instant dimension-based coloring
Player name colors update immediately when entering or leaving a dimension.
Everywhere you need it
Colors are shown in chat, the TAB player list, and above player heads.
100% server-side
No client-side installation required — players can join with a vanilla client.
Highly compatible
Designed to work smoothly with other mods that modify chat or TAB lists.
Fully customizable
Configure colors for any dimension using a simple and flexible config file.
**🔧 Commands**
/worldscolor reload
Reload the configuration instantly without restarting the server.
# WorldSaveBroadcast
WorldSaveBroadcast is a plugin for [Bukkit](https://bukkit.org), [Spigot](https://spigotmc.org) or [Paper](https://papermc.io) that broadcasts a message to all players when the server is saving the world.
# About
This is a very simple plugin for your Minecraft server.
It sends a message to all players when the server saves a world.
It creates a configuration file with a default message that you can change.
The message also supports the placeholder `%name%`, which is replaced by the name of the world.
Please note that this plugin sends a message for each world / dimension that is saved.
This means, if you have `world`, `world_nether` and `world_the_end`, the message will be sent 3 times.
# Features
* Lightweight
* Easy to use
* Plug and play
* Customizable message
* Placeholder support
* Supports color codes and formatting codes
* Supports multiple worlds / dimensions
* Supports Bukkit, Spigot and Paper
* Works on pretty much all versions of Minecraft
* Open source and free
# How to use
* Download the plugin
* Put the plugin in your plugins folder
* (Re)start your server
* Open the config file to edit the message
* (Re)start or reload your server
# Config
“`yaml
message: “&o[Server: Saved the world %name%]”
“`
# WorldRulesManage Plugin Overview
**WorldRulesManage** is a professional plugin for managing world rules. It allows you to freely configure player behavior (e.g., blocking block breaking, block triggering, block interaction, etc.) and world behaviors (e.g., blocking fire spread, liquid flow, etc.) in specific worlds. You can also define radius-based rules using coordinates to restrict player or world actions within a certain area.
**Use cases:** Server lobbies, spawn protection, and controlled world zones.
> English [README.md](https://github.com/MaddyJace/WorldRulesManage/blob/5.0/README.md)
> 中文简体 [CN-README.md](https://github.com/MaddyJace/WorldRulesManage/blob/5.0/CN-README.md)
—
## 📦 Plugin Features
– Supports global and radius-based world rules: prevent fire spread, prevent leaf decay, prevent block ignition (non-player), prevent entity block destruction, and block liquid flow (e.g., lava and water).
– Supports global and radius-based player rules: custom permission control, prevent block ignition, block breaking, block placing, item pickup/drop, bucket usage (e.g., collect water), hunger,
auto-restore hunger to full, prevent player damage, block all portals (overrides Nether/End), block Nether portal, block End portal, block specific item usage (configured by you),
block interaction with specific entities/blocks, block triggering of specific blocks.
– Radius rule shapes (for world and player): 2D Circle (ignores Y), 3D Sphere (includes Y), 2D Square (ignores Y), 3D Cube (includes Y), custom origin and radius values.
– Supports blacklist/whitelist configuration
– Supports multiple worlds
– Supports auto-hot-reload of configuration files
—
# ⚙️ WorldRulesManage Configuration Guide
> [config.yml](https://github.com/MaddyJace/WorldRulesManage/blob/5.0/src/main/resources/config.yml)
> [world.yml](https://github.com/MaddyJace/WorldRulesManage/blob/5.0/src/main/resources/world.yml)
> [radius.yml](https://github.com/MaddyJace/WorldRulesManage/blob/5.0/src/main/resources/radius.yml)
> [message.yml](https://github.com/MaddyJace/WorldRulesManage/blob/5.0/src/main/resources/message.yml)
### ✅ `worldName:
### ✅ `globalRules:` # Rules applied to the world, regardless of player permissions
– `flameSpread: true` # Prevent fire from spreading
– `leavesDecay: true` # Prevent leaf decay
– `blockIgnite: true` # Prevent block ignition
– `entityBlockBreak: true` # Prevent entities from breaking blocks
– `liquidFlow: true` # Prevent liquid flow
### ✅ `playerRules:` # Rules applied to players without permission
– `permission: “wm.world”` # Permission node
– `blockIgnite: true` # Prevent players from igniting blocks
– `blockBreak: true` # Prevent players from breaking blocks
– `blockPlace: true` # Prevent players from placing blocks
– `itemPickup: false` # Prevent players from picking up items
– `itemDrop: false` # Prevent players from dropping items
– `usePail: true` # Prevent players from using buckets (e.g., to collect water)
– `food: true` # Prevent hunger
– `foodSatiety: true` # Restore hunger to full
– `playerDamage: true` # Prevent player damage
– `portalAll: false` # Prevent all portal access (overrides portalNether and portalEnder)
– `portalNether: false` # Prevent Nether portal access
– `portalEnder: false` # Prevent End portal access
######
– `🎯playerUseItem:` # Block item usage
– `type:` `BLACKLIST` / `WHITELIST`
– `list:`
– “EGG” # Egg
– “FLINT_AND_STEEL” # Flint and Steel
######
– `🧍PlayerInteractEntity:` # Block entity interaction
– `type:` `BLACKLIST` / `WHITELIST`
– `list:`
– “ITEM_FRAME” # Item Frame
– “PAINTING” # Painting
– “ARMOR_STAND” # Armor Stand
######
– `🧱PlayerInteractBlock:` # Block block interaction
– `type:` `BLACKLIST` / `WHITELIST`
– `list:`
– “LEVER” # Lever
– “FURNACE” # Furnace
######
– `🎛️PlayerTriggerBlock:` # Block block triggering
– `type:` `BLACKLIST` / `WHITELIST`
– `list:`
– “SOIL” # Farmland
– “TRIPWIRE” # Tripwire
—
### `This option only takes effect in radius.yml`
– `✅settingsRadius:`
– `type:` `2DRange`, `3DRange`, `2DCube`, `3DCube`
– `xyz:` # Starting coordinates (e.g., 0 0 0)
– `radius:` # Radius in blocks
## 📌 Case Sensitivity Warning
> ⚠️ **Important:** All configuration keys are case-sensitive. Misuse of uppercase/lowercase may result in errors or ignored settings.
—
## 🛠 Recommended Practices
– When using TNT near the radius edge, explosions may affect blocks just outside the protected area. To avoid this, expand the radius by 7 blocks for edge safety.
– Remove or comment out unused configuration sections to keep your setup clean and readable.
—
# 🌍 WorldRules
**WorldRules** is a lightweight yet powerful **Paper plugin** that gives you full control over player interactions and chat — both globally and per-player.
Perfect for **event, minigames**.
—
## ✨ Features
### 🔒 Interaction Control
– Enable/disable:
– Block placing & breaking
– Item usage (bows, food, etc.)
– Door & container interactions
– Item drop & pickup
– Player movement & jumping
– PvP combat
– Command usage
### 💬 Chat Management
– Toggle **global chat** on/off
– Control chat per-player
– Allow bypass permissions
### 👤 Per-Player Rules
– Apply rules individually to players
– Override global settings easily
– Perfect for staff moderation or event control
### 🛡️ Admin Bypass
– Permission: `worldrules.bypass`
– Ignore all restrictions when needed
### ⚙️ Runtime Commands
Manage everything without restarting:
######  Made in Germany with love (and [beer](https://s.moep.tv/beer))
######
_Did you ever want to set a different server resource pack for your each of your worlds? Or switch your current resource pack with just one command? Then you came to the right place!
_
This plugin lets you set one Server Resource Pack for each of your worlds or event your whole server! It also allows you to specify packs that should be usable on multiple worlds!
It is also compatible with my [Bungee Resourcepacks](https://modrinth.com/plugin/bungeeresourcepacks) and [Velocity Resourcepacks](https://modrinth.com/plugin/velocityresourcepacks) plugin and will not make the player redownload a resource pack after server switching if it got already applied by Bungee/Velocity Resourcepacks on another server!
**Please check if there are newer [development builds](https://ci.minebench.de/job/resourcepacksplugins/) before reporting issues!**
> Please note that the Vanilla Minecraft client only applies server resource packs that are smaller than **250MiB**! (50MiB before 1.15, 100MiB before in 1.18)
>
> Also certain new **SSL certificates** for URLs (like Let’s Encrypt) do not work with the old Java version shipped with Minecraft (Java 1.8.0_51, [a bug report](https://bugs.mojang.com/browse/mc-143768) regarding that has been filed with Mojang) so you’ll have to either use a different certificate or a non encrypted download (not recommended!)
**Note:** This plugin does not work with older Minecraft versions above 1.8 that do not support server resourcepacks!
### **Features**
* Set different server resourcepacks per world or whole server
* Match world names with regex!
* Commands to configure the plugin ingame
* Language system with messages depending on the locale of the client
* Simplified compoment/json message formatting syntax ([MineDown](https://wiki.phoenix616.dev/library:minedown:syntax))
* Configurable delay before sending the pack to a player
* Remembers which pack a user has currently applied and doesn’t resend on world switch
* Let the user set the pack himself. The pack can be re-applied on each login and will be used for resets on servers that don’t have the pack
* Inform the user which pack the server send them if it was done automatically
* [ResourcePackSendEvent](https://docs.phoenix616.dev/resourcepacksplugins/de/themoep/resourcepacksplugin/bukkit/events/resourcepacksendevent.html) and [ResourcePackSelectEvent](https://docs.phoenix616.dev/resourcepacksplugins/de/themoep/resourcepacksplugin/bukkit/events/resourcepackselectevent.html) for developers to react on the sending or selecting of a pack in their own plugins
* Send the correct pack format depending on the client’s version (requires ViaVersion or ProtocolSupport) with pack-variants either via the version, protocol number or pack format id.
* Automatically generates the sha1 hashes!
* Compatible with [AuthMe Reloaded](https://www.spigotmc.org/resources/authme-reloaded.6269/), [OpenLogin](https://www.spigotmc.org/resources/openlogin-1-7x-1-19x.57272/), NLogin, [LibrePremium](https://www.spigotmc.org/resources/librepremium-proxy-authorization-plugin-automatic-login-2fa.101040/), JPremium.
Do you need it to be compatible with more plugins? [Contact me](https://github.com/phoenix616/resourcepacksplugins/issues/new)!
### **Statistics**
* [McStats.org](http://metrics.griefcraft.com/plugin/worldresourcepacks/)
* [bStats.org](https://bstats.org/plugin/bungeecord/worldresourcepacks)
### **Commands**
To execute every /wrp command you need the `worldresourcepacks.command` permission!
**/wrp reload [resend]** – `worldresourcepacks.command.reload` – Reloads the config file; resends the packs to every online player if the 2nd argument is “resend”
**/wrp version** – `worldresourcepacks.command.version` – Shows the version of this plugin
**/wrp generatehashes** – `worldresourcepacks.command.generatehashes` – Manually generate the resource pack hashes
**/wrp addpack
**/wrp pack
**/wrp listassignments** – `worldresourcepacks.command.listassignments` – View all world assignments
**/wrp deleteassignment
**/wrp assignment
**/wrp globalassignment** – `worldresourcepacks.command.globalassignment` – View and edit the global assignment
**/resetpack [
To execute every /usepack command you need the `worldresourcepacks.command.usepack` permission!
To execute it for other players you need `worldresourcepacks.command.usepack.others`!
To have access to a specific pack a player needs the `worldresourcepacks.pack.
**/usepack** – List all packs available to you
**/usepack
### **Config**
The config.yml allows you to configure everything you can do set up via the commands and a lot more, take a look at the commands in the [file on GitHub](https://github.com/phoenix616/resourcepacksplugins/blob/master/bukkit/src/main/resources/config.yml) for an explanation on all options! (Some might only be available on the [latest development builds](https://ci.minebench.de/job/ResourcepacksPlugins/)!
### **About the client freeze**
> **This should no longer be an issue starting with 1.20.3!**
When a server resource pack is send to a client it will shortly freeze after the download is complete. (Same as manually applying a local pack) This happens because the client has to reload all resources, check which resources overlap and do some other calculation and manipulation with them. (Like stitching all the textures together to a single image like they were in the first texture pack format) It’s not a download issue as the client will locally cache the pack files and not re-download them if their hash didn’t change.
How long this takes generally depends on the PC’s performance and the size of the textures (HD packs take longer) that are used in all resource packs that the player has applied. (So even if the server resource pack doesn’t contain any HD textures or textures at all the client will still completely reload all locally applied resource packs) This is something that has to be fixed in the client by Mojang for example by only reloading resources that changed.
**1.14, 1.15 and 1.16 have some major improvements there and 1.20.3 basically fixed it all so suggest players to use these if they have issues with your server resourcepack!**
### **Dev-Resources**
The source is available on [GitHub](https://github.com/phoenix616/resourcepacksplugins) and licensed under the [GPLv3](https://github.com/phoenix616/resourcepacksplugins/blob/master/license).
Development builds can be found on the Minebench.de [Jenkins](http://ci.minebench.de/job/resourcepacksplugins/).
There are also some [Javadocs](http://docs.phoenix616.dev/resourcepacksplugins/) if you intend to develop plugins based on mine.
### **Support**
You can receive support in the [resource discussion thread on SpigotMC](https://www.spigotmc.org/threads/world-resourcepacks.125581/), the [GitHub issue tracker](https://github.com/phoenix616/resourcepacksplugins/issues), [my IRC channel](https://irc.phoenix616.dev/), or [my Discord](https://phoenix616.dev/discord).
### **Metrics**
This resource includes [bstats.org](https://bstats.org/) metrics. If you don’t want bstats to collect info on your server then you can disable it in the *bStats/config.yml* file. The license the used bStats-lite class is under can be found [here](https://github.com/btobastian/bstats-metrics/blob/master/license).
#####