Tags
Creators
Details
Licensed GPL-3.0-only
Published 7 months ago
Updated 2 months ago
All versions
4.0.0
Release
Emaki CoreLib 4.0.06 months ago 67
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Spigot
Changes
EmakiCoreLib 4.0.0 Release
A major update introducing a JavaScript scripting engine, reversible item modification system, and new built-in actions for the Emaki plugin family.
New Features
- JavaScript Scripting Engine: Execute custom
.jsscripts via therunjsaction (aliases:runscript,javascript). Scripts access player data, trigger context, item info, random utilities, shared state, and action dispatch via the built-inemakiglobal object. Powered by GraalJS with configurable timeout (default 1000ms), content-hash caching, and security sandboxing. dropitemAction: Drop items at specified world coordinates with relative coordinate support and all item source types (vanilla / CraftEngine / ItemsAdder / Nexo).placeblockAction: Place blocks at specified coordinates, supporting vanilla and custom blocks. Properly firesBlockPlaceEventfor compatibility with other plugins.- Item Operation Ledger: Reversible item name/lore modification system stored in item PDC. Supports precise single-operation revert or batch revert by namespace. Provides unified text modification infrastructure for gem socketing, strengthening, forging, etc.
- EmakiAttribute Bridge API: Stable interface for soft-depending on EmakiAttribute — read resources, consume resources, query attribute values, and invoke the damage pipeline.
- Enhanced Condition System: New
none_ofcondition type and nested condition groups (type: group) for combiningall_of/any_of/none_ofin complex logic.
Improvements
- Config and language files auto-merge new keys on upgrade without manual editing.
- YAML loading errors now show specific error messages and file locations in console.
- Item text read/write uses legacy format for better compatibility with plugins using traditional color codes.
Upgrade Notes
- Config version updated to
4.0.0with newscriptsection (auto-merged on upgrade). - Script engine enabled by default; set
script.enabled: falseto disable. - Script files are placed in
plugins/EmakiCoreLib/scripts/— categorized subdirectories and example scripts are auto-created on first startup.
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:7oDeAvJL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EGYz2X2a:7oDeAvJL"
}

