Creators
Details
2.0.0
Compatibility
Changes
Babel Core 2.0.0 — Major Framework Update
Babel Core 2.0 is a major overhaul of the framework, greatly expanding its UI, rendering and mod-development foundations.
What's New
- Introduced Babel UI 2, a new retained-mode UI framework for complex and responsive mod interfaces.
- Added improved layout, styling, rendering and interaction systems.
- Added resource-driven UI support with templates, CSS-like styling and hot reload capabilities.
- Added new Minecraft-specific UI components and improved inventory/menu integration.
- Added server-authoritative UI synchronization and inventory primitives.
- Added code editor and compact input foundations for advanced editor interfaces.
- Reworked the icon system with a new named, high-resolution icon atlas and additional editor/administration icons.
- Added and expanded UI development and debugging infrastructure, including Inspector/devtool foundations.
UI Improvements
- Improved button layout and interaction with nested/composed content.
- Fixed select menus and popovers rendering behind modal interfaces.
- Improved composite control sizing and layout behavior.
- Improved styled text rendering and Forge render-state handling.
- Improved number fields to display integer values without unnecessary decimal suffixes.
- Added better width control for color and compact input fields.
Developer & Framework Improvements
- Expanded reusable platform, entity, data and UI utilities for dependent mods.
- Improved separation between loader-neutral code and Forge-specific implementations.
- Added better support for using Babel Core directly as a development subproject.
- Expanded automated behavior and compatibility coverage.
- Preserved compatibility infrastructure for mods still using previous Babel UI APIs.
This release establishes the new foundation used by current and future SatD mods.
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:ew9qW5hd:ViFuKzgF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ew9qW5hd:ViFuKzgF"
}

