Tags
Creators
Details
1.6.5
Compatibility
Changes
The following files have been updated again and must be reset for the changes to apply. These resets are optional, but you won't get the new copper gear recipes if you don't.
- recipes/grid_recipes.json (copper tools and armor)
- recipes/disabled_recipes.yml (to prevent interference with vanilla recipes)
If you are not aware. Resetting a file means to DELETE the file while the server is OFFLINE, then starting the server (counts for most plugins, this restores the default file).
Basically, because copper equipment and tools and weapons and such don't exist on 1.19 (the oldest version the plugin supports) the game can't properly read items made of copper EVEN on versions where they exist. It mistakes them as older materials. As a result, it tries to parse copper items with an older item reader, which creates an invalid item which causes errors. As a result, these fixes implement a workaround where I never actually use these copper items within recipes themselves (so the items saved aren't actually MADE of copper) and instead replace them with the copper material dynamically (this doesn't reference items made of copper, avoiding the legacy item reader, but basically just the material name which isn't read a special way)
ADDED New ingredient option which allows avoiding this issue within ingredients
FIXED The copper item recipes were reworked with new ingredients and results and modifiers to allow them to use and become actual copper items during crafting (lol)
FIXED Flash effect (crit) throwing a console error
FIXED Copper equipment often times not loading as a result of legacy material support being initialized improperly
FIXED Recipes often not copying properly due to their ingredient filters being linked
FIXED Typo in language file, submerged digging speed was called mounted damage
FIXED Infinite stat accumulation with compatible external inventories (like ValhallaTrinkets)
UNDO Discarded the spear recipe which was broken on older versions (1.21.8 and lower)
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:rxrgsoud:li7P6Y4M"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rxrgsoud:li7P6Y4M"
}

