Tags
Creators
Details
Licensed GPL-3.0-only
Published 3 years ago
Updated 3 years ago
All versions
0.6.0
Beta
CoreExtensions 0.6.0-Beta-B3 years ago 174
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
中文
- 新增新命令/cex getNbt,用于查询手中物品的NBT属性
- 为所有自带的新增命令自动加上了命名空间前缀
- 现在所有自动导出(BRRP-DataGen)的资源包会自动生成pack.mcmeta了
- 现在命令加上了coreextensions和cex的命名空间前缀,但不加仍然能起作用
- 现在自定义画和自定义村民的寻路方块Tag会自动生成了
- 新增命令/coreextensions:iareload和/coreextensions:iazip,分别用于重载ItemsAdder注册表和导出文件
- 修复方块在不设置挖掘工具的时候会无法掉落的错误
- 修复ItemsAdder重复添加Tag崩溃的逻辑问题
- 重置有序合成配方的配置文件格式
- 删除早期的无用调试命令
- coreconfig.yml已换用新版配置文件格式,现有旧版本的该文件会被自动删除
- 不再需要Cloth-Config作为依赖
English
- Added new command /cex getNbt, used to query the NBT attributes of the items in hand
- Automatically add namespace prefixes to all new built-in commands
- Now all automatically exported (BRRP-DataGen) resource packages will automatically generate pack.mcmeta
- Now the command is prefixed with the coreextensions and cex namespaces, but it still works without them.
- Custom paintings and custom villager pathfinding block tags will now be automatically generated
- New commands /coreextensions:iareload and /coreextensions:iazip are used to reload the ItemsAdder registry and export files respectively. *Fixed the bug where blocks would not fall when the mining tool is not set up
- Fix the logic problem of ItemsAdder crash when adding tag repeatedly
- Reset the configuration file format of ordered synthesis recipes
- Delete early useless debugging commands
- coreconfig.yml has been switched to the new version of the configuration file format, and the existing old version of the file will be automatically deleted
- Cloth-Config is no longer required as the dependency
Supplementary resources
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:UA7U5LDf:DbEBB53I"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UA7U5LDf:DbEBB53I"
}

