Tags
Creators
Details
Licensed GPL-3.0-or-later
Published last year
Updated 2 weeks ago
All versions
1.1.3-26.1.2
Beta
Just Enough Book 1.1.3-26.1.22 weeks ago 42
Compatibility
Minecraft: Java Edition
26.1.1–26.1.2
Platform
NeoForge
Supported environments
Client-side
Server-side
Client and server
Changes
1.1.3
Fixes
- Fixed a client crash when opening the inventory. Searching with
~(show ingredients of an item) crashed the game on recipes without an ingredient list, which some modded and special recipes have. Since JEB restores the last search when a screen opens, the crash then repeated every time the inventory was opened. - Fixed the server freezing and being stopped by the watchdog when a player joins. Some mods (e.g. Ender IO's Alloy Smelter) use recipe types that can't be sent to clients. JEB already skipped them, but logged a full stack trace for each one. In large modpacks that took long enough for the server watchdog to stop the server. These recipes are now skipped without the stack-trace logging, and the log gets one short summary line per recipe type, once per server start.
- Clicking a recipe now fills the crafting grid even if the recipe isn't unlocked yet. JEB shows all recipes, but the server only placed ingredients for unlocked ones, so clicking a locked recipe (bucket, anvil, cobblestone slab before unlocking them) silently did nothing. Ingredients are still taken from your inventory, and the
doLimitedCraftinggame rule is still respected. - Fixed some modded recipes showing as craftable with no ingredients in the inventory. Recipes that a mod marks as not placeable (e.g. Little Big Redstone sticky notes) arrived with an empty ingredient list, which counted as "nothing required". They are no longer marked craftable or shown by the craftable filter, but you can still view them and craft them by hand.
Notes
- Recipes that can't be sent to clients (such as Ender IO Alloy Smelter recipes) still won't appear in the recipe book. The mod that adds them has to fix this on its side.
- Install the update on both the client and the server. The locked-recipe fix only works when JEB is on the server.
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:vCHGW3kJ:ZyRr6Afv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vCHGW3kJ:ZyRr6Afv"
}

