2.9-ADV
Compatibility
Changes
Added repair system for auto-fill structure Added crafting table 添加了自动填充结构的修复系统 添加了合成表 Added a repair system with auto-repair regions, use it just like structure blocks. 添加了自动修复区域的修复系统 如同结构方块一样使用就好 Added two fields that deplete based on incoming speed. All shields now have configurable cooldowns via configuration file. fix a bug 添加了两款根据来袭速度消耗的护盾 为所有护盾可通过配置文件修改cd 修了一个方法错误bug Modified the mod dependencies (forgot that Create is actually not necessary). If there is no need, you can continue to use 2.5 or 2.4. 修改了mod依赖关系 (忘记了其实Create不是必要) 如无需求 继续使用2.5或2.4即可 Increased startup time requirement Optimized the compatibility layer Increase the locally calculated reflection-triggered special effects (may not trigger reliably, but does not use network packets) If there is no need, you can continue to use 2.4 增加启动时间要求 优化了vs兼容层 增加本地计算的反射触发的特效(不一定能稳定触发,但不占用网络发包) 若无需求可继续使用2.4
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:nnf9too7:SzEwecUk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nnf9too7:SzEwecUk"
}

