Links
Tags
Creators
Details
1.0.5
Compatibility
Changes
Added
NativeGL Engine Integration: Integration of the NativeGL Engine C++ (Not yet published, but I'm working on it soon)and presence detection. Off-Heap Arena (C++): Implementation of an off-heap memory arena to reduce GC load. Lazy JEI Search Indexing: Lazy indexing of items in the background to prevent freezes at startup (massive RAM savings). Lazy Unicode Font Paging: On-the-fly loading of character pages (Unicode) to save VRAM. LRU-LFU 3D Model Eviction: Dynamic eviction of complex 3D models not recently viewed with a "FlatSprite" (quad 2D) fallback (very significant RAM savings).
Distant NBT Off-Heap Compression: LZ4 compression and off-heap storage of inactive/distant entity NBTs.
Agrona KineticSoABuffer: Replaces resource-intensive Java objects in Create with an off-heap SoA architecture for kinetic block entities. Audio Pool Bridge: Native sound pool to reduce Java memory usage. Toggles UI (Sodium/Embeddium/OptConfigScreen): Added ON/OFF toggles to the options pages to control these new optimizations (JEI, Fonts, Model Eviction, Off-Heap NBT). SodiumCompanion: Automatically adjusts the number of chunk rendering threads based on the mobile SoC. FerriteCore Companion: The MemoryWatchdog detects the absence of a FerriteCore and automatically lowers the purge threshold. ThermalMonitor: Monitors the temperature via /sys/class/thermal and forces the FrameBudgetManager to REDUCED/CRITICAL.
Fixed
Save behavior (UI): The ESC key in the OptConfigScreen menu now cancels any ongoing changes. Saving is only done via the "Apply" or "Finish" buttons, in accordance with the Sodium/Embeddium integration.
Removed
ChunkPreloader: Completely removed chunk preloading (on slow Android eMMC/UFS, it consumed too much RAM) and replaced with the intelligent FreezeDebugger.
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:q30sS7vR:4gqcAuvM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:q30sS7vR:4gqcAuvM"
}

