Tags
Creators
Details
1.2
Compatibility
Changes
SimpleCom V1.2 Changelog
SimpleCom V1.2 更新日志
New Features
新增功能
Encrypted Channels
加密信道
- Create encrypted channel: Press C → "创建加密信道" → Enter name and password
- 创建加密信道:按 C →「创建加密信道」→ 输入信道名称和密码
- Connect to encrypted channel: Press C → "连接加密信道" → Get server channel list
- 连接加密信道:按 C →「连接加密信道」→ 获取服务器加密信道列表
- Join encrypted channel: Enter password to join, only players with password can hear/send
- 加入加密信道:输入密码加入,仅知道密码的玩家可收发语音
- Exit encrypted channel: Press C when in encrypted channel to view current channel and exit
- 退出加密信道:在加密信道状态下按 C 可查看当前信道并退出
- Encrypted channel IDs start from 101 (separate from public channels 1–100)
- 加密信道 ID 从 101 起,与普通信道 1–100 区分
Minecraft 1.19.2 Support
Minecraft 1.19.2 支持
- Client mod: Fabric & Forge 1.19.2
- 客户端模组:支持 Fabric 与 Forge 1.19.2
- Server mod: Fabric & Forge 1.19.2 server
- 服务端模组:支持 Fabric 与 Forge 1.19.2 服务端
Version Compatibility
版本兼容
| Platform / 平台 | 1.16.5 | 1.18.2 | 1.19.2 |
|---|---|---|---|
| Client (Fabric/Forge) / 客户端 | ✅ | ✅ | ✅ |
| Server Mod (Fabric/Forge) / 服务端模组 | ✅ | ✅ | ✅ |
| Bukkit/Spigot Plugin / Bukkit 插件 | ✅ | - | - |
Note: V1.2 client requires V1.2 server (mod or Bukkit plugin). Do not mix with V1.1 or earlier. 注意: V1.2 客户端需搭配 V1.2 服务端(模组或 Bukkit 插件)使用,请勿与 V1.1 及更早版本混用。
Technical Changes
技术变更
- 1.19.2 API updates:
LiteralText→Text.literal(),ClientPlayerNetworkEvent.LoggingIn/LoggingOut,PlayerEvent.getEntity() - 1.19.2 API 适配:
LiteralText→Text.literal(),ClientPlayerNetworkEvent.LoggingIn/LoggingOut,PlayerEvent.getEntity() - Server encrypted channel:
EncryptedChannelStore,EncryptedChannelHandler, etc. - 服务端加密信道:
EncryptedChannelStore、EncryptedChannelHandler等 - Bukkit plugin: Encrypted channel create/list/join support
- Bukkit 插件:支持加密信道的创建、列表、加入
Downloads
下载
See GitHub Releases for: 从 GitHub Releases 下载:
simplecom-1.16.5-*/simplecom-1.18.2-*/simplecom-1.19.2-*(client / 客户端)simplecom-server-1.16.5-*/simplecom-server-1.18.2-*/simplecom-server-1.19.2-*(server mod / 服务端模组)bukkitserver-*(Bukkit/Spigot plugin / Bukkit 插件)
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:eioMe3UT:tEO5P2LF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eioMe3UT:tEO5P2LF"
}

