All versions
1.3.0
Release
WorldEngine 1.3.08 months ago 236
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Server-side
Client and server
Changes
Breaking change:
All existing obsidian-based portals are automatically deactivated on upgrade. Rebuild portals using ore block frames.
What's new:
- Custom portal block — WorldEngine portals now use a dedicated animated block instead of vanilla nether portal blocks. Completely eliminates interference with vanilla nether/end portals.
- Ore block frames — Build portal frames from iron, copper, redstone, lapis, diamond, gold, emerald, or netherite blocks (entire frame must be one type).
- Ore item activation — Right-click a linked frame with the matching ore item (e.g., diamond on diamond block frame) to activate. Consumes 1 item in survival.
- Teleport warmup — 1.5 second delay with action bar countdown. Step out to cancel.
- Client-side rendering — Animated translucent portal texture with colored particles. Requires the mod on both server and client for portals to function.
Bug fixes:
- Fixed vanilla nether portals routing players through WorldEngine portals on return trips.
- Fixed portal re-activation failing when clicking certain frame block positions.
Upgrade notes:
- Old obsidian portals will be cleared automatically on first startup. Rebuild with ore block frames.
- Players need the mod installed client-side to see and use custom portals. Without it, portals are non-functional but the server won't crash.
- Portal setup workflow unchanged: OP right-click frame (empty hand) → /we portal link <world> → any player activates with ore item.
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:qjqEpxGC:JlTy7mTb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qjqEpxGC:JlTy7mTb"
}

