Links
Tags
Creators
Details
All versions
1.0.0
Release
Create: Recipe Hooks 1.0.04 months ago 30
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Forge
NeoForge
Supported environments
Server-side
Singleplayer
Required content
Unavailable version
Changes
Create Recipe Hooks v1.0.0
Server-side API mod that fires a unified Forge event whenever a recipe completes in a Create machine, with player attribution via UUID.
Features
- Single event
CreateRecipeFinishedEventcovering 17 recipe sources: Basin (Mixer/Compactor), Mechanical Press (belt + world), Millstone, Crushing Wheel, Mechanical Saw, Mechanical Crafter, Deployer, Sand Paper, Sequenced Assembly, all 4 Fan processing types (belt + world modes), Spout, Item Drain, and CEI Printer. - Player attribution:
owner_uuidmetadata identifies who placed the machine (for the Crushing Wheel who threw the item). Persists across server restarts via block entity NBT. - Full recipe context: recipe ID, item/fluid outputs and inputs, block position.
- Spout fires on both filling paths: recipe-based and fluid-capability (buckets;
recipeIdisnullthere). - Server-side only, clients without the mod can join. Required in the instance for singleplayer.
- Ready-to-use KubeJS script examples (FTB Quests integration, output filtering, per-player counters), see the README on GitHub.
Compatibility
- Minecraft 1.20.1, Forge 47+, Create 6.0.8+.
- KubeJS scripting requires the EventJS addon (only a Forge build of EventJS exists).
- Tested on both Forge and NeoForge clients; verified on a dedicated server and in multiplayer.
License: LGPL-3.0-or-later. Source: GitHub.
Optional dependencies
Unavailable version
Unavailable 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:sbGNpoEo:7TPX2Gws"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sbGNpoEo:7TPX2Gws"
}

