Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated 11 hours ago
All versions
0.0.4
Alpha
Pocket Dimensions 0.0.49 months ago 85
Compatibility
Minecraft: Java Edition
1.21–1.21.10
1.20.x
1.19.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Added
/pdleaveCommand: Added a new command to leave the current pocket dimension and return to your previous location (or spawn).- Permission: pocketdimensions.commands.player.pdleave
/pdworldborderCommand: Added a command to set and update the world border size for a specific player's pocket dimension.- Permission: pocketdimensions.commands.pdworldborder
messages.yml: Added a full messages configuration file, allowing you to translate or customize every message sent by the plugin.- Fail-safe Messages: Added hardcoded default messages. The plugin will now safely fall back to internal defaults if a message is missing from your config.
Configuration Changes
- Key Item Customization: You can now fully customize the "Key Item" (used to enter dimensions) in config.yml.
- Change the Material, Display Name, and Lore.
- World Border Settings:
- Added default-world-border-size to config.yml to set the global default size.
- Individual sizes set via /pdworldborder are saved to pdborders.json and now persist across restarts.
Changed
- Folder Organization: All Pocket Dimension worlds are now generated inside a dedicated pocketdimensionworlds/ folder to keep your server root clean.
- Note: If you have existing worlds in the root folder, you may need to move them into this new folder manually.
- Safety Checks: Added strict permission checks to /givepd, /pdgamerule, and other commands to prevent unauthorized use.
- Location Saving: Improved how the "last location" is saved, ensuring players return to the correct spot even after visiting someone else's dimension.
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:2sir62f0:32Scv7rm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2sir62f0:32Scv7rm"
}

