All versions
1.1.0
Release
Custom Worlds 1.1.02 weeks ago 13
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Changes
Added
/cw config worldedit <true|false>- let every player (not just OPs) use WorldEdit commands in a specific dimension, without granting them OP. WorldEdit is creative-only for everyone, OPs included (survival players are refused). Requires WorldEdit to be installed; no build/block limits are enforced, it's an admin-trust decision per world./cw config worldspawn [<pos>] [<angle>]- set a custom spawn point for a custom dimension (used the first time any player arrives with no remembered position). No arguments uses your current position/facing;resetreverts to the automatic safe-spawn search./cw create <name> <type> [seed] [structures]- optional trailing flag to disable structure generation (villages, strongholds, etc.) for a new world. Defaults totrue(vanilla behavior) when omitted.
Fixed
- World border no longer leaks between dimensions. Vanilla only gives the overworld
its own border; every other dimension (nether, end, and therefore every custom world)
shared that same border object by default. Running
/cw config worldborderin one custom world was silently rewriting the overworld's border and every other custom world's border at the same time. Every dimension now gets its own independent border. - Fixed a related, not-yet-reported issue at the same root cause: a custom dimension's
spawn point was aliased to the overworld's, so vanilla's own
/setworldspawnused inside a custom world would have corrupted the real overworld spawn point.
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:DR117uDO:RC95l3Jo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DR117uDO:RC95l3Jo"
}

