Tags
Creators
Details
2.0.0
Compatibility
Required content
Changes
<3 Patch Notes v2.0.0 — Lures, Rod Protection & Repair
New: Lure System
Attach lures to your off-hand while fishing for extra catch chances. Each lure boosts specific rarities with a flat weight bonus — set a value like 200 and that rarity becomes near-guaranteed. Lures have limited uses and wear down as you catch fish. Clear attach/detach messages when equipping a lure with a rod in hand.
New: Custom Rod Protection & Repair
Custom rods take general durability same as any other minecraft item, but our system has a custom repair command /rodsplus repair [player] this will repair the rod with a deminishing random % (defined in config) each time it is repaired until it finally cant be repaired anymore.
Custom rods can no longer be renamed or repaired in an anvil. Lures are anvil-proof too — no renaming, no repairing.
Improvements
Catch notifications show exactly which rod/lure bonuses were applied. In-game /rodsplus debug command to inspect your rod and lure. Debug logging written to a dedicated debuglog.txt for easy troubleshooting. All admin commands are locked to operators/permission emf.rodsplus.admin.
Allowed worlds feature added into lures and rods config where you can define specific worlds that you want your bonuses to work in to make dedicated fishing villages etc.
Removed
The in-game shops system has been removed in favor of using external systems simply use /rodsplus givelure <itemid> <playername>
PLEASE NOTE AS PART OF THE OVERHAUL THE FOLDER NAME FOR CONFIGS WAS CHANGED. SO TREAT THIS AS A NEW INSTALL, ANY OLD SETTINGS YOU USED WILL NEED TO BE MOVED OVER TO THE NEW CONFIGS
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:RLqy9ha7:ZayzfnJ4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RLqy9ha7:ZayzfnJ4"
}

