Tags
Creators
Details
mc1.20.1-1.0.48-forge
Compatibility
Changes
v1.0.48
-
Added inflate width/height values to pair with x/y offset. Allows stacking of textures of different sizes without multiple widgets.
-
Added option for smooth progress texture, on by default to prevent breaks, how many steps to make.
-
Added overflow and pop out text types.
-
Added background inflate x/y values, intended for easily making the background on pop out text larger.
-
Made ResourceContainer use pop out text for better readability. Also changed render order to render what's under the mouse last in ResourceContainer to fix text rendering on top of pop out text.
-
Changed ResourceContainer pop out text to have background texture. Added option to SelectableWidgetGroup to render the selected overlay under the group's widgets. Added factory setter for TextTexture's backgroundTexture.
-
Added optional background texture to TextTexture.
-
Added NineSliceMode to ResourceBorderTexture with FIT, STRETCH, and TILE modes.
-
Added default ResourceBorderTextures for vanilla button textures.
-
Added new default textures to built-in.
-
Added factory setter methods in ResourceTexture.
-
Added test ui for SlotWidget/PlayerInventoryWidget.
-
CodeEditorWidget: option for unformatted text, basically just a text pane. (UNTESTED)
-
Added SliderWidget
- Known issue: when dragging a slider, if the cursor passes a slider widget lower on the update order, the dragging will be stolen.
-
Fixed bug where drag splitting an itemStack would not render correctly.
-
Fixed missing lang for some widget
-
Fixed EMI invisible tooltips for slots
-
Improve Renderer to check blockstate if the medeldata not found
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| ldlib-forge-1.20.1-1.0.48-sources.jar | Unknown | 1.78 MiB |
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:B1CBVXHX:yhlCY3k1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:B1CBVXHX:yhlCY3k1"
}

