Links
Tags
Creators
Details
All versions
1.1.0
Release
Simple Craft Editor 1.1.02 weeks ago 61
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Changelog
Version 1.1.0
A stability release. Simple Craft Editor now behaves the same in a large modpack as it does on its own.
Added
- Debug logging, off by default, for reporting problems:
/sce debug truewrites what the mod does to the log. It can be narrowed to one area, it survives a restart, and it can be turned on before the world loads with-Dsce.debug=true /sce debug status,/sce debug verifyand/sce debug findreport what the mod is doing and where a given recipe stands
Fixed
- A modpack that builds its recipes from scripts could lose them: editing a single recipe emptied the pack's recipe list
- Opening an existing recipe in the editor showed an empty screen in some modpacks
- Creating, editing, disabling and deleting took effect only after a reload when certain performance mods were installed
- A deleted recipe could still be crafted, and stayed craftable until the player logged out, when a recipe-choice mod was installed
- The editor key appeared in Controls but did nothing on Forge 1.20.1
- Deleting an edit of an existing recipe left the recipe missing instead of restoring the original
Changed
- Recipes created by script mods can no longer be opened or disabled. Those scripts rewrite their recipes every time the pack loads, so any change made here would be undone. The editor now says so instead. Recipes from datapacks, from the game and from other mods are unaffected
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
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:gj2KV14c:kGWgFPF7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gj2KV14c:kGWgFPF7"
}

