Tags
Creators
Details
Licensed ARR
Published 10 months ago
Updated last week
All versions
2.0
Release
Recipe Item Sync 2.03 months ago 169
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Server-side
Client and server
Changes
Recipe Item Sync v2.0
New
- Added automatic datapack item synchronization for dedicated servers.
- Added JEI, REI, and EMI support through independent viewer integrations.
- Added /recipeitemsync status to show current sync state.
- Added /recipeitemsync clientstatus to show each playerβs viewer sync status.
- Added /recipeitemsync resync to manually resync one player or all players.
- Added /recipeitemsync dump to generate a troubleshooting report.
Changes
- Improved synchronization so custom recipe outputs appear in viewers without needing to craft, receive, or manually configure the item first.
- Improved handling of datapack reloads, reconnects, and server changes.
- Improved preservation of custom item data, including components, names, lore, CustomModelData, and stack counts.
- Improved JEI variant handling for multiple custom versions of the same base item.
- Client configuration is now focused on local preferences instead of required synced item lists.
Fixes
- Fixed custom datapack recipe items not appearing in JEI sidebars on dedicated servers.
- Fixed sync being skipped after reconnecting or reloading datapacks.
- Fixed synced data being lost when received before the client or recipe viewer was ready.
- Fixed reloads causing stale or duplicate viewer entries.
- Fixed cases where the server treated a sent packet as a successful sync before the client applied it.
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:jQbAVNQr:W3jQZejb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jQbAVNQr:W3jQZejb"
}

