Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated 11 hours ago
All versions
0.0.8
Alpha
Pocket Dimensions 0.0.811 hours ago 8
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
1.19.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Pocket Dimensions 0.0.8-ALPHA
Minecraft 26.3 support, stronger protection, and storage/admin reliability improvements.
- Minecraft 26.3 (Wilderness Bound):
- One jar now supports Minecraft 1.19.4 through 26.3; Java 17+ (26.x servers need Java 25).
- Gamerules work across 1.19.4, 1.21.11+ and 26.3 spellings; /pdgamerule accepts either camelCase or snake_case and configs keep working unchanged.
- Dimensions are found, loaded, reset and deleted correctly on 26.1+ servers, where world data lives under <main world>/dimensions/minecraft/..., as well as on older servers and hosts that flatten folder names.
- 26.3 shelves are protected like containers; cushions and the new block variants need no extra setup.
- Configs are upgraded automatically; new protection options are added without touching existing values.
- Protection:
- Visitors can no longer strip logs, till/path blocks, bone-meal crops, wax copper, carve pumpkins, brush suspicious blocks or harvest beehives with right-click tools.
- Boats, minecarts, armor stands, end crystals, spawn eggs and sign editing are blocked for untrusted visitors; riding normal minecarts/boats and using cushions still works.
- Pets stay protected even if the attacker leaves the dimension before a projectile lands.
- Chested animals, storage minecarts/boats and armor stands stay protected even when mob damage is disabled.
- Malformed pocket-dimension worlds now remain protected instead of becoming public.
- Admin and data safety:
- Border sizes are validated, so a bad value can no longer make a dimension unenterable; economy upgrades only charge for valid tiers.
- /pdadmin cleanup rejects negative or overflowing day counts.
- /pdadmin reset clears the old in-dimension position and logout flag, so players return to the new spawn instead of stale coordinates.
- Delete/reset removes every copy of a dimension folder, verifies deletion and refuses suspicious paths.
- /pdleave only saves your own dimension position; /pdtp remembers the admin's return point.
- Storage:
- Interrupted JSON -> SQL migrations resume on the next start instead of being skipped forever.
- Source files are never renamed after a failed import.
- Unreadable JSON is quarantined and writes are refused instead of rewriting the store from empty data.
- SQL purges are transactional.
- Quality of life:
- /pdgamerule is owner-or-admin only and rejects extreme integer values.
- Invites are re-checked on accept, so revoked trust cannot be used to enter.
- GUI trust promotion and border upgrades require their matching permission nodes.
- Shift-click crafting produces keys bound to the crafter.
- /givepd drops leftover keys at your feet instead of deleting them on a full inventory.
- Glow on key items works on modern servers.
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:QmzTj70a"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2sir62f0:QmzTj70a"
}

