1.1
Compatibility
Changes
- Release for NeoForge 1.21.4
- Release for NeoForge 1.21.1
- Release for 1.19.4
-
Renaming the job site block to any of the village types(Forexample:desert,taiga,swamp) will change the converted villagers type when you right click the wandering trader with it.
> Uppercase or lowercase characters doesn't matter in the item name as long as it spells snow,taiga,desert,swamp,jungle or savanna. > If items name hasn't changed or doesn't match with the 6 village types villager will be plains type instead. -
More extra trades for wandering traders.
-
Some trade fixes for previous extra wandering trader offers.
-
Better&Fixed particles.
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:FkhnenHj:IY3rzjNs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:FkhnenHj:IY3rzjNs"
}

