Tags
Creators
Details
Licensed GPL-3.0-only
Published 3 months ago
Updated last month
All versions
1.1.0+mc1.21.11-neoforge
Release
VillagersTradingPlus 1.1.0 (NeoForge) 1.21.11last month 375
Compatibility
Minecraft: Java Edition
1.21.11
Platform
NeoForge
Supported environments
Client and server
Changes
Minecraft 1.21.11, 26.1.2, 26.2 and 26.3 (Fabric, NeoForge). First release for these versions, with the same features as 1.1.1 for 1.20.1 to 1.21.8.
Added
- Vanilla trades as templates in
data/villagertradingplus/vanilla_trades/. They are not loaded. Copy one into your own datapack and change it. - New trade type
sell_dyed_armor. - Trades read the vanilla
merchant_predicateformat, for example to offer a trade only to desert villagers. - Trades accept large cost amounts, map icons and map names.
- The wandering trader file has a
buyingtier for the offers where the trader buys items. - The trade catalog lists every enchanted book a librarian can offer, shows explorer map trades as a fixed row and shows the buying tier of the wandering trader.
- Mods can give a merchant its own catalog pool.
- Option
reroll_permission_level: sets the permission level a player needs for the re-roll buttons and the level control. - 26.3:
sell_mapstill reads the five structure tags that 26.3 renamed (for exampleon_woodland_explorer_maps).
Changed
trade_cost_scale, the day time prices andtrade_price_multiplier_scaleapply to every new offer of a merchant, vanilla trades included. The default config changes nothing.- Trade buttons the player is not allowed to use are hidden.
- With JEI, REI or EMI installed, the trade buttons sit in a row below the trading window, away from the item list.
Optional dependencies
Any compatible version
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:DhOXUfnP:LWyydXPl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DhOXUfnP:LWyydXPl"
}

