Tags
Creators
Details
Licensed GPL-3.0-only
Published 7 months ago
Updated 2 months ago
All versions
3.1.0
Release
EmakiCorelib 3.1.06 months ago 29
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Spigot
Changes
EmakiCoreLib Changelog
[3.1.0] - 2026-04-16
Added
- Added shared
AbstractEmakiPlugin,AbstractConfigurableEmakiPlugin,BaseAppConfig, and a reusableGuiTemplateLoaderso gameplay modules can share one runtime, config, and GUI template foundation. - Added
ItemSourceService.displayName,InventoryItemUtil, andPlayerSessionMapto unify item display-name lookup, inventory counting/removal, and per-player session tracking.
Improved
- Refactored the reflective CraftEngine, ItemsAdder, MMOItems, NeigeItems, and Nexo item resolvers behind shared base classes so availability checks, loaded-state detection, and fallback behavior stay consistent.
- Updated
GuiService,GuiSession,GuiTemplateParser, andItemComponentParserto supportsounds.left_click/sounds.right_click,hide_tooltip, andtooltip_display, while tightening session switching during async GUI rendering. - Normalized item-source comparisons and text bridging so
minecraft:prefixes,itemName, vanilla translation keys, and custom names all flow through one display pipeline.
Fixed
- Fixed a race where an older GUI session could overwrite a newer one after async rendering completed, reducing stale pages, orphaned sessions, and mismatched close callbacks.
- Fixed item-name handling so it no longer depends on
displayNameonly;itemNameand vanilla translated names now work without relying on runtime-specific APIs. - Fixed vanilla item-source matching when one side used a
minecraft:prefix and the other did not.
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:EGYz2X2a:nmbyzsJY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EGYz2X2a:nmbyzsJY"
}

