Tags
Creators
Details
Licensed GPL-3.0-only
Published 7 months ago
Updated 2 months ago
All versions
4.6.0
Release
Emaki CoreLib 4.6.03 months ago 128
Compatibility
Minecraft: Java Edition
26.2
26.1.2
26.1
1.21.8–1.21.11
Platforms
Folia
Paper
Purpur
Changes
Added
- 15 built-in actions usable in any action list:
giveitem,takeitem,setitem,damageitem,repairitem,setblock,breakblock,explosion,ignite,extinguish,feed,killentity,spawnentity,bossbarshow,bossbarhide. /corelib actionwithaction listandaction run <actionId> [key=value ...]to inspect and directly fire registered actions./corelib debug all on|off|statusruntime global debug toggle, backed by the new config keydebug.global_all(defaultfalse).- Unified gameplay event layer: one shared listener republishes kill / block break / block place / craft / fish / tame / brew / furnace-extract / MythicMobs-kill events to dependent Emaki plugins, configured through the new
gameplay_eventsblock (enableddefaulttrue,last_damager_expire_ticks200,brew_attribution_expire_ticks6000). - Configured-item / item-component pipeline for config authors and API consumers, plus a shipped
item-components.ymlcatalog documenting eachminecraft:*component id, itssinceversion, and accepted format. - EcoItems as an item source, declared as an optional soft dependency.
- Config key
release_default_data(defaulttrue); setfalseto stop writing the bundledscripts/examplessample files. - Shared chat-input service so plugins can ask a player to type a value in chat outside a GUI.
- Localizable config precheck output instead of hardcoded English.
- Additive
EmakiCoreLibApisurface: compatibility report, configured-item create/apply, item component capabilities, and third-party action registration. All previously released methods still exist.
Changed
- GUI click vocabulary expanded from 3 to 11 types:
CLICK,LEFTCLICK,RIGHTCLICKplusSHIFT_LEFTCLICK,SHIFT_RIGHTCLICK,MIDDLECLICK,DOUBLECLICK,NUMBER_KEY,SWAP_OFFHAND,DROP,CONTROL_DROP. - The packet GUI backend resolves click types explicitly, so its click types match the Bukkit backend across the full vocabulary.
script.enableddefault flippedtrue->false; JavaScript is now opt-in.script.server_api.enableddefault flippedtrue->false; scripts calling the server API need it re-enabled explicitly.- Runtime library loading now uses Paper's official plugin-loader classpath API instead of injecting jars at enable time.
- bStats is shaded into the plugin instead of shipping as a separate bundled runtime-library jar. No config key change.
- Message prefix switched to a new brand gradient.
- Descriptor migrated from
plugin.ymltopaper-plugin.ymlwith a loader entry; soft-depends became structured server dependencies.api-versionraised1.21->1.21.8. Java target unchanged at 25. - Commands are no longer declared in the descriptor; the root command plus the
corelib/emakicorealiases register at runtime. Owner-facing usage is unchanged.
Fixed
- Config precheck messages were hardcoded English and ignored the
languagesetting; they now route through language keys present in bothen_US.ymlandzh_CN.yml.
Removed
- The built-in Web Console, including its bundled frontend, the
web-console.ymlresource, and the wholeweb_console:config block (host, port, auth username/password, session timeout, security mode, request body limit, allowed modules, config-browser limits, history/snapshot settings). - The commands
/corelib web(aliaseswebconsole,url,link) and/corelib webdebug [frontend|backend|all]. - The permission
emakicorelib.web, including its child entry underemakicorelib.admin. - The language sections
web_console:andweb_debug:and their keys; custom language files carrying them now have dead entries. - Support for plain Spigot. Paper or a Paper fork is required.
Notes
- Update CoreLib before the other Emaki plugins that depend on it.
- Upgrade actions: delete the stale
web_console:block andweb-console.yml, removeemakicorelib.webgrants, re-addscript.enabled: trueandscript.server_api.enabled: trueif scripting was in use, and confirm the server is Paper 1.21.8+. - Servers below 1.21.8 are out of contract.
folia-supported: truewas already declared before this release. - Back up
plugins/EmakiCoreLib/before updating production, then verify GUI clicks, action triggers, and/corelib debug all status.
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:laTGMtqs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EGYz2X2a:laTGMtqs"
}

