1.3.2
Compatibility
Required content
Changes
RS Integration 1.3.2
Release Date: August 11, 2026
This release includes all changes from 1.3.1-fix to 1.3.2. It focuses on improving Refined Storage special searches, complex recipe previews, multiplayer batch crafting, recipe-tree material accounting, and JEI integration.
Fixes
- Fixed Sol Carrot's “Eaten/Not Eaten” status being incorrectly stored in the shared static tooltip cache.
- Fixed several issues with Goety sacrifice, conversion, and summoning rituals, and added clearer confirmation messages.
- Small synchronous crafting jobs now display a completion message instead of finishing without feedback.
- Fixed several reusable catalyst recipes. Reusable crafting hammers are no longer multiplied by the batch size.
- Fixed single-layer steamer structures not being recognized.
- Fixed batch quantities being scaled twice between the recipe tree and the total requirements view.
- Fixed the Dimensional Feeding Upgrade not working correctly.
- Fixed recursive crafting slowdowns caused by wool and dye conversion loops.
- Fixed the Dark Altar being unusable under certain conditions.
- Stack-based auto-feeding now correctly recognizes Gnaw's Gift.
- Fixed the recipe transfer key using
Fin certain screens and preventing normal offhand swapping. - Fixed potion charm conversion and material recognition. Missing-material names such as Apotheosis Eternal Potion Charms are now formatted correctly instead of displaying
Format error: %s. - Wizards Reborn Crystal Infusion no longer requires exact NBT for crowns unless the recipe explicitly declares it. Durability and unrelated runtime data will no longer prevent matching.
- Improved SlashBlade smithing compatibility with dynamic blade NBT and assembled outputs. The known empty
rodairecipe override has also been fixed. - Fixed machine panels not closing correctly in some situations.
New Features and Improvements
- Reworked Refined Storage searches for
#tooltips,$tags, and@mod names. Results now appear progressively instead of freezing for several seconds. Search data is also prewarmed during gameplay and cached for future sessions. - Missing-material names can now be clicked directly to add individual items to JEI bookmarks.
- Added reusable-catalyst recipe preference. For example, compatible ore-processing requests can prefer the Gold Orchid crafting route.
- Adjusted the total requirements interaction layer so individual JEI bookmark buttons are no longer covered by other UI elements.
- Added nearby machine binding with the semicolon
;key:- Wireless connectors can remain equipped in Curios slots.
- Already-bound machines are skipped and never added twice.
- Clear messages are shown for invalid networks, replaced connectors, multiple equipped connectors, and scans already in progress.
- FTB Chunks claims are respected. Machines inside claims where the player lacks permission will not be bound.
- The completion message reports discovered, newly bound, already bound, permission-blocked, and invalid machines separately.
- Added expanded kettle crafting support, including one-click crafting for additional kettle recipes.
- Added no-gain conversion protection for wool colors, concrete powder, wood families, and similar materials. This prevents recursive searches from cycling through equivalent variants while preserving exact-output conversions and recipes with a real quantity gain.
- Added compatibility support for Ars Nouveau add-ons.
Compatibility
- The recipe preview data format has changed, and the network protocol has been updated from version 29 to 30. Clients and servers must both use RS Integration
1.3.2. - Older versions will be rejected during connection instead of continuing with incompatible packet formats.
- Updating will not remove existing Refined Storage networks, machine bindings, or search disk caches.
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:vtvveeqA:mQd0KwpF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vtvveeqA:mQd0KwpF"
}



