Tags
Creators
Details
1.7.4
Compatibility
Changes
1.7.4 BETA
add:
Added PlayerPoints sell economy support and per-fish split rewards; old
valuerewards followeconomy.primary, old fish value records are upgraded automatically, and newsell-valuecan pay Vault coins and PlayerPoints points separately or together:
# config.yml
economy:
primary: vault # old value rewards go to Vault first; use playerpoints to prefer points
fallback: true # if the primary economy is unavailable, try the other one
# fish.yml
fish:
old_fish:
value: 100 # old syntax, still supported
split_fish:
sell-value: # new syntax
vault: 100 # Vault coins
playerpoints: 10 # PlayerPoints points
Added custom item compatibility and syntax for ItemsAdder, Oraxen/OXN, Nexo, and CraftEngine/CE across fish, rods, baits, hooks, GUI displays, item rewards, and ItemsAdder font images:
# ItemsAdder: custom item + font image
# Other plugins: use their own material prefixes in the same fields
fish:
ia_fish:
material: "ia:fish_pack:blue_fish"
display-name: ":fish_pack:blue_icon: &bBlue Fish"
item-value:
- "ia:fish_pack:coin:1"
oraxen_fish:
material: "ox:blue_fish"
nexo_fish:
material: "nx:blue_fish"
craftengine_fish:
material: "ce:blue_fish"
Added off-hand fishing rod detection and casting support. Updated sell reward messages and refund handling for coins, points, mixed rewards, and item rewards. Updated default config examples and economy tests for the new sell reward behavior.
fix:
Fixed sell commands and sell GUI availability when only PlayerPoints is installed. Fixed custom item reward parsing when item IDs contain
:. Fixed off-hand fishing rod interaction causing vanilla fishing to run.
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:aKzS1gyN:xtqjCRqf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aKzS1gyN:xtqjCRqf"
}

