All versions
1.6.330
Release
MaoPhone - Trial Version 1.6.3302 months ago 678
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
Updates
- Removed config tool. Now config data is edited using mod config files (.toml file)
- Replace "Hearing Protection" with "Silent Mode". When players activate "Silent Mode", their phones will not ring
- Now MaoPhone uses Forge Energy (FE) as its battery (energy) capacity, with a maximum capacity of 1000 FE
- This means that the methods used in other mods to restore FE (charging) for items will also work for MaoPhone
- Minor redesign of Charging Station
- Now, after placement, it will restore FE storage at a rate of 40 FE/t, with a maximum capacity of 100 kFE
- Now any item with FE attribute can be placed on the charging station to charge it
- The fixed charging speed for items is 0.5% of the item's maximum capacity per tick, and charging consumes the FE storage of the charging station
- Increased the basic mining speed of the charging station, and further increased the mining speed using pickaxes
- Fixed memory overflow on the server caused by repeated data requests from client under network latency conditions
- Fixed contents would not drop when charging station was destroyed
- Fixed abnormal explosion resistance of charging station
- Updated mod credit list (View in "Settings - About Phone")
更新内容
- 移除了配置工具,现在使用mod配置文件(.toml文件)编辑配置数据
- 将“听觉保护模式”替换为“静音模式”。玩家开启“静音模式”后,持有的手机将不会响铃
- 现在MaoPhone使用FE能量作为电量,最大容量为1000FE
- 这意味着其他mod中能为物品恢复FE能量(充电)的方式也对MaoPhone生效
- 充电站小重做
- 现在在放置后将以40FE/t的速度恢复FE储存,最大可储存100kFE
- 现在可将任意拥有FE属性的物品放置在充电站上为其充电
- 物品充电的固定速度为0.5%物品最大容量/t,充电会消耗充电站的能量储存
- 提升了充电站的基础挖掘速度,并且使用镐的挖掘速度提升
- 修复了网络延迟的情况下客户端重复请求数据导致服务端内存溢出的问题
- 修复了充电站被破坏时内容物不会掉落的问题
- 修复了充电站的爆炸抗性异常的问题
- 更新了模组致谢名单(可在“设置-关于手机”界面查看)
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:ShABinKy:MvhPv65j"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ShABinKy:MvhPv65j"
}

