Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 4 years ago
Updated last month
All versions
2.3.0-beta.5+1.20
Beta
OptiGUI 2.3.0-beta.5+1.202 years ago 31.2K
Compatibility
Minecraft: Java Edition
1.20–1.20.1
Platforms
Fabric
Quilt
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
OptiGUI 2.3.0-beta.5
What's new since 2.1.7
- New selectors. Check the docs for usage
player.name,player.name.wildcard,player.name.wildcard.ignore_case,player.name.regex,player.name.regex.ignore_case,player.biomes,player.heightsinteraction.handhorse.has_saddle,horse.variants,horse.markings,llama.variants
- Filter priority (
load.priority) - OptiGUI Inspector for resource pack creators
- Press
F12(by default) when a GUI screen is open to copy the interaction data to the clipboard - German translation by Lucanoria
- Mexican Spanish translation by Santiago Hernandez
- Chinese translations by dirtTW and notlin4
- Press
What changed since 2.1.7
- Basically the entire codebase
- Performance improvements
- Better caching
- Less memory allocation
- OptiGlue library is now gone
- Incompatible Minecraft versions will receive different OptiGUI JARs.
What got fixed since 2.1.7
- Crash with mod menu and map atlases
- OptiGUI
villager.typeselector - OptiGUI
dateselector- OptiFine
christmas=falsechests
- OptiFine
- OptiFine
container=inventorycompatibility - Trader llama not working
About this release
- Recommended for everyday users
- Recommended for modpacks
- Check out the documentation!
Optional dependencies
Any compatible version
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| optigui-2.3.0-beta.5+1.20-sources.jar | Unknown | 70.36 KiB |
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:JuksLGBQ:Fdam47G9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JuksLGBQ:Fdam47G9"
}

