0.1.0-release
Compatibility
Changes
English
"I'm making a note here: HUGE SUSCCESS!"
Sound System
Implemented Sound System. Now mobs of SEEKERS can react to sounds made from players' actions, such as moving, mining and destroying, placing, eating, and more.
Sound Wave Indicator HUD
Added a new HUD for Sound System. The HUD only reflects player self's action's sound - not including arrow-shot-by-player sticking into something, TNT or Creeper explosion, etc..
Throwable Items
Most Throwable Item likes Snowball, Egg or Potion, can all make sounds to distract enemies. But the most cost-effective one is new Pebble Item. Now you can use 2*2 Cobblestones to craft a Pebble Block, which can become 9 Pebbles. Pebbles can easily attract enemies, making them go away.
Bugfixes
- Fixed the issue that the mod cannot be loaded on a dedicated server.
- Fixed an issue caused by enemies' AI trying to set players as attack target.
- Fixed AI issues when an enemy is investigating the LKP.
- Fixed an issue that when a player died while enemies are aware of or tracking him, the Alert Indicators may remain and abnormally display.
Optimizations
Optimized data cleansing, making sure Alert Data of enemies to players, and static fields of client, can be cleaned timely.
Data Persistence
Made Crawling Data persistent in world.
中文
“我要在这儿做点记录:心花怒放。”
声音系统
实现了声音系统。现在带有 SEEKERS 标签的生物能对玩家的各种动作产生的声音做出反应,如移动、挖掘和破坏方块、放置方块和吃食物等。
声波指示器 HUD
为声音系统添加了一个新的 HUD。此 HUD 仅反映玩家自身行为的声音——不包括由玩家射出的箭矢插入某物的声音、TNT 或苦力怕爆炸的声音,等等。
可投掷物品
大多数可投掷物品,如雪球、鸡蛋或药水瓶,均可制造声音使敌人分心。但最有性价比的是“石子”。现在可通过 2*2 的圆石来合成一个石子块,一个石子块可合成九个“石子”。石子能轻易地吸引敌人注意力,让他们走开。
Bug 修复
- 修复了模组无法在专用服务端上加载的问题。
- 修复了敌人 AI 因试图将玩家设置为攻击目标而产生的问题。
- 修复了敌人调查 LKP 时的有关 AI 问题。
- 修复了当玩家死亡且正被敌人察觉或追踪时,警戒指示器残留并异常显示的问题。
优化
优化了数据清理,保证敌人对玩家的警戒数据,和客户端的静态字段,能被及时清理。
数据持久化
使匍匐数据在存档中持久化。
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:6V9H3TEr:FcovM1tE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6V9H3TEr:FcovM1tE"
}

