1.3.1-fix
Compatibility
Required content
Changes
RS Integration 1.3.1-fix Update Notes
This update includes all changes from version 1.3.0 to 1.3.1-fix:
-
Improved game startup and recipe loading speeds, reducing lag when entering a world and during gameplay.
-
Improved recursive crafting speed and responsiveness when handling large numbers of materials and recipes.
-
Fixed incorrect material calculations and output amounts in some crafting plans.
-
Fixed issues where some machines could not start batch crafting, repeated operations, or incorrectly occupied materials.
-
Fixed some Goety recipes failing to create a crafting plan when materials were missing.
-
Fixed items stored inside a Resonance Disk being incorrectly detected and used as normal RS storage items.
-
Resonance Disks can now correctly provide immunity to negative effects from the Artificial Flower.
-
Fixed some item rewards not dropping correctly when using FTB Quests' Claim All feature.
-
Fixed inventory count errors, connection issues, and lag related to the RS side panel. Side panel inventory syncing has been temporarily disabled to improve stability.
-
Improved claim permission checks to prevent remote crafting from operating machines in protected areas without permission.
-
Improved SlashBlade recipe support and fixed some blades with special data not being recognized or crafted correctly.
-
Added missing SlashBlade upgrade recipes so the affected blades can be upgraded normally.
-
Fixed automation issues involving brewing stands, cooking pots, Aether furnaces, Spirit Crucibles, Enchantal Coolers, and several other machines.
-
Fixed some recipes not updating correctly after recipes were reloaded.
-
Improved data syncing between clients and servers, reducing incorrect item displays, unresponsive actions, and unexpected disconnections.
-
Added stability improvements to reduce lost materials, duplicate material usage, and interrupted crafting during complex crafting jobs.
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:MHm8uj2Y"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vtvveeqA:MHm8uj2Y"
}

