All versions
1.2.0
Release
WorldEngine 1.2.08 months ago 20
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Unavailable version
Changes
Changelog
[1.2.0] - 2026-02-23
Added
- Named portals — assign a persistent name to any portal with
/we portal name <name> - Bidirectional portal linking — link two named portals to each other with
/we portal link <portal-name>; both sides update automatically - Dual key block support — portals with two key blocks now scan both correctly and use the first detected key block for particle color
- Portal info command —
/we portal infoshows name, world, position, size, key block, link type, and destination coordinates for the selected portal - Custom destination coordinates —
/we portal link <world> <x y z>links a portal to a specific coordinate in the target world
Fixed
- Bidirectional portal spawn location now correctly places the player inside the destination frame rather than at the frame's lower corner
- Dual key block detection no longer skips the second key block when the first scanned position is air
Changed
/we portal linknow auto-detects whether the target is a named portal (bidirectional) or a world name (one-way)- Portal list output now shows link direction:
↔ "name"for bidirectional links,→ worldfor one-way links
[1.0.0] - 2026-02-01
Initial release.
- Multi-world creation and management via Fantasy API (9 generator types)
- Per-world gamemode enforcement, PvP, difficulty, and gamerule overrides
- Inventory isolation with configurable shared groups (items, armor, ender chest, hunger, XP, effects)
- Granular mob spawn control by entity type and spawn category
- Fast-placement throttle for survival worlds
- Custom obsidian-frame portals with key block particle colors
- Performance optimizations: lazy loading, idle auto-unload, staggered async saves
- Full
/wecommand suite with tab completion
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:qhSkXWZc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qjqEpxGC:qhSkXWZc"
}

