Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 2 years ago
Updated 20 hours ago
All versions
5.0.0
Release
datapack-function-library_v5.0.0_1.21.1120 hours ago 8
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Data Pack
Required content
Any compatible version
Changes
- 兼容:支持范围由 1.13–1.21.10 扩展至 1.13–26.3;
- 兼容:适配 Minecraft 26.x 的命令语法变更(
gamerule与time query),旧版本由构建系统自动转换; - 破坏性:
dfl:lib/count_items新增{namespace}参数,记分项由dfl_{name}_num改为dfl_{namespace}.{name}_count; - 破坏性:基于
count_items的函数(clear_and_execute_single、clear_and_execute_multiple、maintain_item_count、convert_items_to_xp)同步新增{namespace}参数; - 破坏性:
dfl:child/smelt重命名为dfl:tick/smelt_item,dfl:tick/smelt重命名为dfl:tick/coal_smelt,两者参数均有调整; - 破坏性:移除
dfl:lib/spawn_dummies批量生成假人函数; - 破坏性:移除 tick 入口函数与
minecraft:tick标签; - 修复:
kill_by_density的村民豁免在部分版本下失效; - 修复:
teleport_request的传送目标判定错误; - 修复:冶炼函数中
count_items调用缺少宏前缀导致无法执行。
- Compatibility: supported version range extended from 1.13–1.21.10 to 1.13–26.3;
- Compatibility: adapted to the command syntax changes of Minecraft 26.x (
gameruleandtime query), with older versions converted automatically at build time; - Breaking:
dfl:lib/count_itemsnow takes a{namespace}parameter, and its scoreboard objective changed fromdfl_{name}_numtodfl_{namespace}.{name}_count; - Breaking: functions built on
count_items(clear_and_execute_single,clear_and_execute_multiple,maintain_item_count,convert_items_to_xp) now take a{namespace}parameter as well; - Breaking:
dfl:child/smeltrenamed todfl:tick/smelt_itemanddfl:tick/smeltrenamed todfl:tick/coal_smelt, both with adjusted parameters; - Breaking: removed the
dfl:lib/spawn_dummiesfunction; - Breaking: removed the tick entry point function and the
minecraft:ticktag; - Fix: villager exemption of
kill_by_densitydid not work on some versions; - Fix: wrong teleport target check in
teleport_request; - Fix: missing macro prefix on
count_itemscalls in the smelting functions.
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:xfcXTP3W:rFWtbwwG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xfcXTP3W:rFWtbwwG"
}

