All versions
1.0.3
Beta
CloudeEngine 1.0.35 months ago 201
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.4
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
Changelog v1.2.0 — Architecture Rebrand & ServerFix
Release Date: 2026-04-29 Target: Minecraft 1.21.4 (Fabric)
Core Architecture & Rebranding
- Identity Migration: Completed the full codebase transition from "Renderix" to CloudeEngine.
- Namespace Update: All internal Java package paths and resource namespaces migrated to com.cloude.engine.
- Config Migration: Config file path moved to config/cloudeengine.json.
- Metadata Alignment: Updated fabric.mod.json to reflect new Mod ID and All-Rights-Reserved status.
Critical Bug Fixes
- [Fixed] 1.21.4 Mixin Crash: Resolved method not found error for SpriteContents$Animation. Corrected the injection point descriptor to match current Yarn mappings.
- [Fixed] Vulkan Driver Loading: Resolved a path mismatch in the Termux build script that caused native .so files to be missing or stale in previous builds.
- [Fixed] Server Loading Crash: Implemented environment-aware guards on all client entrypoints to prevent crashes when the mod is present on a dedicated server.
- [Fixed] Injection Failure: Corrected a malformed @At descriptor in the chunk rebuild throttle system that was causing silent performance degradation.
Internal Technical Changes
- Set defaultRequire = 0 globally to increase stability against minor version mapping changes.
- Verified all 39 client-side mixin entries against the new package hierarchy.
- Standardized log prefixes to [CloudeEngine].
Final Note: This version is now fully stable for both singleplayer and server-connected play on 1.21.4.
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:cNev0BGn:TyE8zfnO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cNev0BGn:TyE8zfnO"
}

