All versions
1.0.3.2
Release
Tuanzi's Server Mod 1.0.3.2last month 2
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Server-side
Singleplayer
Changes
v1.0.3.2 更新日志
新增功能
-
- Carpet 假人智能联动:
-
- 新增与 Carpet 模组的智能联动功能。
-
- 登录验证模块现能自动、智能识别 Carpet 生成的假人信息(
carpet.patches.EntityPlayerMPFake)。
- 登录验证模块现能自动、智能识别 Carpet 生成的假人信息(
-
- 假人加入时将自动激活免密登录(安全置为已登录状态),无需输入
/login或/register人在后台流畅运作。
- 假人加入时将自动激活免密登录(安全置为已登录状态),无需输入
修复与优化
- 商店多维度支持与告示牌更新错误修复:
- 商店实例(
ShopInstance)现在完全在持久化数据和内存模型中存储并索引维度信息(dimensionId),杜绝了相同坐标跨维度的哈希键碰撞。 - 定时衰减系统不再默认使用主世界更新告示牌,而是自适应检索并使用每个商店所在的维度(如
minecraft:the_nether等),彻底修复了非主世界下界商店因跨世界查找抛出的“目标方块实体不是告示牌”警告。 - 优化了定时告示牌刷新逻辑的区块状态检测,对于未加载的区块不再强制读取,极大降低卡顿开销。
- 旧商店智能维度修复系统:在服务器启动时,能够全自动扫描所有未标识维度的旧版商店。若在主世界对应坐标处没有告示牌,而在下界或末地能检测到该告示牌,系统将自动将商店属性修补为正确的维度并永久保存。用户无需手动打任何指令,也不用劳神去修改存档 NBT 文件。
- 商店实例(
v1.0.3.2 Update Log
New Features
- Carpet Mod Fake Player Support:
- Added smart integration with Carpet mod fake players (
carpet.patches.EntityPlayerMPFake). - The login system automatically bypasses verification and registers carpet fake players as logged in, enabling them to operate smoothly without typing
/loginor/register.
- Added smart integration with Carpet mod fake players (
Bug Fixes & Optimizations
- Shop Multi-Dimension Support & Sign Update Fix:
- The
ShopInstancenow stores and indexes dimension info (dimensionId) across persistence and memory, preventing coordinate hash key collisions across different dimensions. - The system stock decay task now dynamically resolves the corresponding
ServerLevelof each shop instead of only using Overworld, resolving the "block entity is not a sign" warning in non-overworld shops. - Added chunk loaded checks to prevent crash issues or performance drops during sign updates.
- Legacy Shop Auto-Repair System: On server startup, the mod automatically scans all legacy shops (defaulted to
minecraft:overworld). If a sign is missing at that location in Overworld but present in Nether/End, it will silently migrate the shop dimension and write it back to save. No manual action or NBT editing required!
- The
Optional dependencies
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:RDMGNOTc:xGndDRfU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RDMGNOTc:xGndDRfU"
}


