Tags
Creators
Details
Licensed GPL-3.0-only
Published 7 months ago
Updated 2 months ago
All versions
4.4.0
Release
Emaki CoreLib 4.4.04 months ago 108
Compatibility
Minecraft: Java Edition
1.21.8–1.21.11
Platforms
Folia
Paper
Purpur
Spigot
Changes
Added
- Config precheck on startup and reload, with a console report and
/emakicorelib check; failed prechecks cancel the reload and keep the previous config. - Loop actions (loop-sync / loop-async / cancel-loop) with interval, iteration, and concurrency limits.
- Packet GUI backend that reuses the same window across row changes, switchable via
gui.backend(bukkit / packet / auto); packet only needs PacketEvents. - Oraxen item source and block bridge support, shared by all modules.
- Public Bukkit event infrastructure with cancellable subscriptions and per-plugin cleanup.
- JavaScript extensions: custom conditions, expression functions, host object proxies, and script text APIs, plus
/emakicorelib script. checkanddebugsubcommands for/emakicorelib.
Fixed
- Fixed item rebuilds wiping Lore and custom names added by other plugins.
- Fixed huge values being zeroed out when output in scientific notation by the expression engine.
- Fixed enchanted/starred item names losing translatable text.
- Fixed low-frequency stability issues around action registry, PDC null inputs, cache diagnostics, and cached preview items.
Refactored
- Switchable GUI backend abstraction (bukkit / packet); default behavior unchanged.
- Packet GUI backend split out then merged back, now built-in (needs PacketEvents).
Improved
- Per-module debug log prefixes and externalized debug text.
- Centralized runtime library and bStats handling.
Notes
- Update CoreLib before other Emaki plugins.
- Breaking:
web_console.security.allow_config_write→web_console.security.mode(defaultreadonly). - Breaking: script action aliases
runscript/javascriptremoved; userunjs. - Breaking: legacy condition/GUI/Mythic-bridge fields removed; migrate to the new structure.
- New softdepends (Oraxen, PacketEvents) and new config keys; compare or regenerate your config.
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:hwkSnhHx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EGYz2X2a:hwkSnhHx"
}

