All versions
1.0.1
Release
WenxingTools2 1.20.1-Forge-1.0.18 months ago 28
Uploaded by
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
New Configuration Options (ModConfig)
新增配置项(ModConfig)
New options added to the [enchantment] section in config/wenxingtools2-common.toml:
在 config/wenxingtools2-common.toml 的 [enchantment] 段新增:
enable_ore_resource_amplification- Whether to enable Resource Amplification's multiplier effect for ore block drops.
- 是否启用资源增幅对 矿物方块掉落 的倍增。
enable_crop_resource_amplification- Whether to enable Resource Amplification's multiplier effect for crop (farm produce) drops.
- 是否启用资源增幅对 农产品掉落 的倍增。
enable_entity_resource_amplification- Whether to enable Resource Amplification's multiplier effect for entity loot items.
- 是否启用资源增幅对 生物战利品物品 的倍增。
enable_experience_resource_amplification- Whether to enable Resource Amplification's multiplier effect for experience drops.
- 是否启用资源增幅对 经验掉落 的倍增。
Datapack Extension Method
数据包扩展方式
- Datapacks can create corresponding Tag files in the world save's
datapacks/directory, for example:- 数据包可在世界存档的
datapacks/中创建同名 Tag 文件,例如: data/wenxingtools2/tags/items/resource_amplifiable_tools.jsondata/wenxingtools2/tags/items/attack_amplifiable_weapons.jsondata/wenxingtools2/tags/blocks/amplifiable_ore_blocks.jsondata/wenxingtools2/tags/blocks/amplifiable_crop_blocks.jsondata/wenxingtools2/tags/items/amplifiable_crop_items.json
- 数据包可在世界存档的
- It is recommended to use:
- 推荐使用:
"replace": falseto append blocks/items from other mods."replace": false来 追加 其他 Mod 的方块 / 物品。- Use
"replace": trueto completely rewrite the Tag only when full customization is needed. - 仅在需要完全自定义时使用
"replace": true来 完全重写 Tag。
- You can include an
"_comment"field in the JSON to add notes for easier maintenance. - 可以在 JSON 中使用
_comment字段写说明,便于维护。
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:UWYM6Xj1:IlbhgZ5e"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UWYM6Xj1:IlbhgZ5e"
}

