Tags
Creators
Details
Licensed MIT
Published 5 months ago
Updated 4 months ago
All versions
1.1.0
Release
GUIAPI 1.1.04 months ago 95
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8.8–1.8.9
Platforms
Folia
Paper
Purpur
Spigot
Changes
[1.1.0] - 2026-06-14
⚠️ Breaking Changes
GUIAPI.get(Plugin)has been deprecated. UseGUILibs.init(Plugin)to create a per-plugin instance, orGUILibs.getDefault()to retrieve the global default instance (available when GUIAPI is installed as a server plugin).
✨ Features
- Dual Distribution Model: GUIAPI can now be used in two ways:
- Plugin Dependency (
guiapi-plugin) — Install GUIAPI as a plugin on the server and use it as a shared library withprovided/compileOnlyscope. - Shade / Bundle (
guiapi-core) — Bundle GUIAPI directly into your plugin JAR using Maven Shade or Gradle Shadow with relocation.
- Plugin Dependency (
GUILibs.init(Plugin)— New static method to create a dedicatedGUILibsinstance bound to your plugin.GUILibs.getDefault()— New static method to retrieve the global defaultGUILibsinstance (only available when using the plugin dependency approach).- Expanded Version Support — Added version adapters for Minecraft 1.8, 1.13, 1.16, 1.19, and 1.20, extending backward compatibility to Minecraft 1.8+.
- Folia Support — Added compatibility with Folia servers through dedicated scheduling adapters.
🏗️ Internal
- Project restructured into multi-module Maven layout:
api— Core API interfaces and abstractionscore— Main implementation (for shading)plugin— Server plugin wrapperv1_8_R3,v1_13_R2,v1_16_R3,v1_19_R3,v1_20_R4— Version-specific adapters
📋 Migration from 1.0.0
- Replace
GUIAPI.get(this)→GUILibs.init(this)in youronEnable(). - Update your dependency coordinates:
- If using as a server plugin:
com.github.downnfalls.guiapi:guiapi-plugin - If shading:
com.github.downnfalls.guiapi:guiapi-core
- If using as a server plugin:
- Remove the
import io.downn_falls.libs.guiapi.GUIAPI;import (no longer needed).
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:ipt81Sgf:U0H2hV7Q"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ipt81Sgf:U0H2hV7Q"
}

