1.11.0-beta
Compatibility
Required content
Changes
Beta 1.11.0
Release date: 2026-09-02
Stage: Beta
Summary: The in-game Logicore manual is finally real. Press L, click what you want to learn, and rotate some tiny datacenter hardware because plain walls of text were never going to be enough.
Added
- The full-screen Logicore Interactive Guide with the game still visible behind a dark tint.
- Homepage categories, category page lists, Back navigation and search across titles, terms and referenced items.
- Hold-
Litem shortcuts with the intentionally simple[|||| ]progress tooltip. - Detailed current-system pages with local glossaries and no future-feature spoilers.
- Client-only 3D dioramas made from the mod's actual baked models, with mouse rotation and contextual hover tooltips.
- A compressed three-second Jetpack demonstration whose exhaust gets weaker as its simulated buffer drops.
Changed
- The 1.11 plan now uses one complete guide text instead of splitting everything into Basic and Advanced versions.
- Current Logicore terminology and 1.10 storage behaviour are documented directly inside the game.
- Category strips, their labels and the 3D dioramas now render at three times their original size.
Fixed
- Players no longer need to guess what a Core, Request, DSD, VSC or SDFC is from scattered tooltips alone.
Removed
- The proposed persistent guide sidebar. Navigation stays as Homepage → Category → Page.
Known Issues
- The guide now has a solid first content pass, but some wording and diorama framing will probably get more polish after wider testing at different GUI scales.
Still beta
Keep in mind this is still beta. Visual bugs, logic bugs and strange edge cases may still show up, especially when spinning tiny hardware around at questionable angles.
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:AJmOFSPL:lcmIfN8g"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AJmOFSPL:lcmIfN8g"
}

