Tags
Creators
Details
All versions
2.0.0
Release
Dimension Daddy 2.0.04 months ago 251
Compatibility
Minecraft: Java Edition
26.1.2
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Unavailable version
Changes
2.0.0 - 2026-07-02
Added
- Unified command tree under a single
/DimensionDaddyroot, withenable,disable,status,backup,restore,reset, andlistsubcommands, each takingoverworld,nether,end, orallas the target - Overworld toggle support; previously only the End and Nether could be disabled
- Blocking of the Nether portal's return trip and the End's exit portal when the Overworld is disabled, in addition to the existing entry-side blocking
- Real world data backup, restore, and reset, covering the
region,entities,poi, and per-dimensiondatafolders for each dimension, rather than only an enabled and disabled flag - A one-time Initial Backup, captured automatically the first time the mod runs on a world, preserving the world exactly as it was before the mod made any changes
- An in-game report broadcast the moment a scheduled restore or reset finishes applying, showing per-dimension file counts or the specific failure reason
- Retry logic with a short backoff on every file delete and copy operation, to avoid silent failures caused by brief file locks right after a world reload
- Tab completion for dimension names and known backup ids
- Support for Minecraft 26.1's restructured world save layout, where each dimension's data lives under
dimensions/minecraft/<dimension>/instead of the previous root-level layout
Changed
- Replaced the previous six separate commands,
enableend,disableend,endstatus,enablenether,disablenether, andnetherstatus, with the unified/DimensionDaddycommand tree. This is a breaking change for anyone with the old commands saved in scripts, macros, or keybinds - Backup storage changed from a single properties file per backup to a folder per backup, containing a metadata file plus copied world data
- Removed the automatic safety backups that were previously taken on every server startup and immediately before every restore or reset; the mod now only creates a backup automatically once, the Initial Backup, and otherwise only when explicitly requested
Fixed
- Restore and reset previously only ever changed the enabled and disabled flag and never touched actual block or entity data on disk; they now genuinely restore or regenerate world data
- Fixed a bug where a partially completed Initial Backup left behind by an earlier failed run would permanently prevent the mod from ever creating a valid one; it now retries automatically on the next server start
- Fixed dimension folder paths to match Minecraft 26.1's new world save layout; the previous paths were left over from the pre-26.1 layout and caused every backup to silently capture no data at all
- Fixed a bug where a single file that could not be deleted, typically due to a brief lock immediately after a world reload, would cause the entire delete step to be silently treated as successful
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:9DANKgmT:MbqHHZOw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9DANKgmT:MbqHHZOw"
}

