Tags
Creators
Details
Licensed AGPL-3.0-only
Published 3 years ago
Updated 3 months ago
All versions
2.2.0
Release
PhantomWorlds 2.2.03 months ago 198
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
Platforms
Folia
Paper
Purpur
Spigot
Changes
Added
- Added compatibility with Paper 26.1+ world storage layout.
- Added automatic detection of legacy and modern world storage formats.
- Added WorldFolders utility for resolving and discovering world folders across supported server versions.
- Added semantic version detection using semver4j to determine server storage layout.
- Improved unloaded world discovery for both legacy and modern Paper servers.
Changed
- Refactored world folder resolution throughout the plugin to eliminate direct reliance on Bukkit#getWorldContainer().
- Updated world loading, copying, backup, and deletion operations to use the new WorldFolders abstraction.
- Improved handling of world folder locations for loaded and unloaded worlds.
- Modernized internal filesystem discovery to support Paper's Vanilla world storage implementation.
- Improved compatibility with Paper 1.21.9 / 26.1+.
Fixed
- Fixed world management commands failing on servers using the new Paper storage layout.
- Fixed unloaded worlds being incorrectly detected under modern Paper versions.
- Fixed backup and delete operations resolving incorrect world directories.
- Fixed copied worlds resolving to invalid filesystem locations on newer Paper versions.
- Fixed several command flow issues where failures could still report success.
- Fixed console execution issues in player-only spawn-related commands.
- Improved validation when creating or copying worlds that already exist.
Internal
- Reduced filesystem assumptions by centralizing world discovery logic.
- Improved code maintainability by separating world resolution from world management.
- Updated dependency shading configuration for bundled libraries.
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:Cckdg1sQ:xVoqMdRK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Cckdg1sQ:xVoqMdRK"
}
