Tags
Creators
Details
Licensed ARR
Published last year
Updated last week
All versions
1.26.10.15
Release
1.26.10.15last week 134
Uploaded by
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1
1.21.x
1.20.x
1.19.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
Fixes
- ExecutableCrafting: recipes that use Nexo items as ingredients craft again. By default Nexo empties the result of other plugins' recipes that contain its items; EC now gives its result back, with the recipe conditions still checked. Thanks to grim.
- SCore: picking up an ExecutableItem with an incompatible CoreProtect version could give the item twice (a copy stayed on the ground). CoreProtect logging can no longer interrupt a pickup. If your CoreProtect isn't compatible, its pickup logging turns off with a single console warning. Thanks to wassabi.
- SCore:
silenceOutput: truehides the feedback of/attributeagain ("The base value for attribute ... set to ..."), for example in a LOOP activator. Thanks to theserversowner. - SCore: on LIST variables,
setfollowed bylist-addno longer throws an error, and the added value is kept. - MyFurniture: on a fresh install with a furniture pack already in place, the first start no longer creates duplicate furniture configs, and keeps the pack's ExecutableItems (name, lore, restrictions).
New
- ExecutableCrafting: option
accurateRecipeBookinconfig.yml(off by default). The vanilla recipe book only compares item types and ignores enchanted or renamed items, so EC recipes with custom ingredients showed the wrong state: "craftable" with a plain item, "uncraftable" with the real one. WithaccurateRecipeBook: true, EC checks each player's real items: a recipe shows as craftable only when the player has the right ones, including enchanted, renamed and Nexo items, and the book updates live. This is unique to ExecutableCrafting: no other crafting plugin fixes the vanilla recipe book this way. Requires Paper 1.21.2 or newer. To turn it on, setaccurateRecipeBook: trueon the line EC adds at the end of the file, then run/ec reload. Thanks to grim.
The only new setting is accurateRecipeBook, and it is off by default; your configs are otherwise unchanged. If something looks wrong after updating, open a post in the bug channel.
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:4G8ckuub:ZMjHMNbX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4G8ckuub:ZMjHMNbX"
}

