0.4.0
Compatibility
Changes
我看文件看一半才发现我没有写下界岩装备和下界黑曜石装备的json文件,导致它们的贴图显示不出来,给我气笑了,没事已经修好了,加入了骷髅旅行商人,可以卖好东西喔😀。另外,我还让僵尸骑士的僵尸马跑得更快了一点,本来是想写马撞击是可以造成伤害的,但不知道为什么没实现,就先不管了。也是终于把除了刷怪蛋之外的贴图都补全了,但盔甲贴图目前还是全部套用下界岩盔甲的。总之,勃勃生机,万物竞发的场景犹在眼前啊(大喜)
I realized halfway through reading the files that I hadn’t written the JSON files for the Netherite and Nether Obsidian gear, which made their textures not show up. It made me laugh out of frustration 😂. No worries, it’s already fixed, and I added the Skeleton Travelling Merchant—you can buy some good stuff from him 😀. Also, I made the zombie horses ridden by the Zombie Knight run a bit faster. I originally wanted the horse attack to deal damage, but I don’t know why it didn’t work, so I’ll just leave it for now. Finally, I’ve completed all the textures except for the spawn eggs, though the armor textures are still all using the Netherite armor ones. Anyway, the scene full of vibrant life and all things competing to grow is right before my eyes (super happy).
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:wYWqYPzQ:g0SHm3Ao"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wYWqYPzQ:g0SHm3Ao"
}

