
Serverauth Mod
A purely server-side Fabric login module, where the administrator has full control over accounts. Forced login, automatic binding, AFK timeout, and position restoration provide a complete securi 纯服务端 Fabric 登录模组,管理员完全掌控账号。强制登录、自动绑定、挂机超时,为服务器提供完整的安全验证体系
1.6.0(1.20.x-1.21.x)
Compatibility
Changes
新增功能
1.兼容 Carpet 等假人模组,新增了独立的假人检测系统支持类名检测、接口检测、行为特征检测(如网络连接判断)。支持配置化(fake_player_detection.json),可自定义关键词、白名单(确保真玩家不被误判)、并支持日志记录。假人将自动绕过登录验证。
2.优化mod判断程序,轻微减少服务器占用 修复问题
1.修复了玩家从下界或末地登录时,因为目标区块未加载导致的掉虚空、扣血、人物看不见(黑屏)、无法移动等问题
2.修复首次登录降落在 (0,0,0) 的问题
3.修正了出生点获取逻辑,新账号首次登录将准确回到服务器世界出生点,而不是坐标原点。
4.修复下界/末地退出后位置丢失问题
5.修复虚空误覆盖真实位置的问题
New Features
-
Compatible with plugins like Carpet, we've added an independent fake player detection system that supports class name detection, interface detection, and behavior detection (like network connection checks). It's configurable (fake_player_detection.json), allowing custom keywords, whitelists (to make sure real players aren’t misidentified), and log recording. Fake players will automatically bypass login verification.
-
Optimized the mod detection program to slightly reduce server load.
Bug Fixes
-
Fixed issues where players would fall into the void, take damage, see a black screen, or be unable to move when logging in from the Nether or End because the target chunk hadn’t loaded.
-
Fixed the problem of first-time logins landing at (0,0,0).
-
Corrected spawn point logic, so new accounts will now correctly respawn at the server world’s spawn point instead of the coordinate origin on first login.
-
Fixed Nether/End logouts causing position loss.
-
Fixed the issue of the void wrongly overriding the real position.
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:DTnPsdAq:Q2SNlGoh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DTnPsdAq:Q2SNlGoh"
}
