Links
Tags
Creators
Details
2.2.4-Stable
Compatibility
Changes
ProAuthMeLogin v2.2.4-Stable
▎ 插件已更名为 ProAuthMeLogin
✨ 新功能
- Dialog 用户协议弹窗:玩家完成登录/注册后,若客户端版本支持(1.21.5+),将弹出用户协议对话框,提供 接受 和 拒绝 两个按钮
- 接受后显示欢迎消息
- 拒绝后自动踢出服务器
- 不支持 Dialog 的客户端不显示,完全向下兼容
- 通过 enable-agreement 配置项控制开关,协议内容由 agreements 列表配置
🐛 修复
- Folia 线程调度异常:修复 StatisticsManager 在 Folia 端使用 BukkitScheduler 导致的 UnsupportedOperationException,改用 SchedulerUtil 统一调度
- 修复https://github.com/ian171/AuthAnvilLogin/issues/17
- 修复https://github.com/ian171/AuthAnvilLogin/issues/16
🔧 其他
- 插件 api-version 更新至 1.21
- 插件名称从 AuthAnvilLogin 更名为 ProAuthMeLogin
Full Changelog: https://github.com/ian171/AuthAnvilLogin/compare/2.2.3...2.2.4
ProAuthMeLogin v2.2.4-Stable
▎ The plugin has been renamed ProAuthMeLogin
✨ New Features
-
Dialog User Agreement Pop-up: After players complete login/registration, if the client version supports it (1.21.5+), a user agreement dialog box will pop up, providing two buttons: Accept and Reject.
-
A welcome message will be displayed after acceptance.
Automatically kicking players out of the server after rejection.
-
Clients that do not support Dialog will not display it; fully backward compatible.
-
The switch is controlled via the enable-agreement configuration item; the agreement content is configured by the agreements list.
🐛 Fixes
-
Folia thread scheduling exception: Fixed the UnsupportedOperationException caused by StatisticsManager using BukkitScheduler on the Folia side; SchedulerUtil is now used for unified scheduling.
🔧 Other
-
Plugin API version updated to 1.21
-
Plugin name changed from AuthAnvilLogin to ProAuthMeLogin
Full Changelog: https://github.com/ian171/AuthAnvilLogin/compare/2.2.3...2.2.4
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:uhk4EMXY:HhnxqckN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uhk4EMXY:HhnxqckN"
}

