1.1
Compatibility
Changes
This is a global update to the plugin, introducing full multi-world support, a mob swapping mechanic, and numerous fixes to improve stability and performance.
IMPORTANT UPDATE NOTE
Due to a complete overhaul of the configuration file structure, old versions of config.yml (v1.x) are not compatible with this version.
For the plugin to work correctly, please completely delete your old config.yml file before the first launch of this new version. The plugin will automatically generate a new config.yml v2 with all the new features and detailed comments.
[+] Added
-
Multi-World Support:
- You can now configure mob spawning individually for each world on your server.
- Added
global-settings(default settings) andworld-settings(world-specific settings) sections toconfig.yml.
-
Mob Swapping Mechanic:
- Added the ability to replace one spawning mob with another (e.g., a Skeleton with a Zombie).
- This feature can be enabled, disabled, and configured for each world separately.
-
New Command
/ms swap:/ms swap <world> enable|disable— to enable/disable the swap system in a world./ms swap <world> <from_mob> <to_mob|none>— to create or remove swap rules.
-
Config Versioning System:
- Added a
config-versionfield toconfig.ymlto track its version and assist with future updates.
- Added a
[*] Changed
- Complete
config.ymlRework: The file structure has been completely redesigned to support the new features, making it more logical and flexible. - Expanded Existing Commands: All old commands (
set,enable,disable,info) now accept an optional[world]argument. - Improved Tab-Completion: Command auto-completion has been significantly reworked to support new arguments, including world names.
- Spawn Handling Logic: The spawn event interception and handling mechanism has been rewritten for better stability and compatibility with different server versions.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:IPfNxlB3:yWe1Htz3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IPfNxlB3:yWe1Htz3"
}

