MineVerify
一个轻量级的 PaperMC 插件,允许应用程序通过生成的游戏内代码验证 Minecraft 玩家。
? 概述
MineVerify 让外部应用能够验证 Minecraft 账号是否由你服务器上的真实玩家控制。
应用会创建内部验证请求,并要求玩家运行 /mineverify。
随后插件轮询已配置的应用,生成临时代码,在游戏内验证 /mineverify <code>,并将已验证的 Minecraft UUID 和用户名返回给应用。
MineVerify 仅向已配置的应用发起出站请求。它不会在 Minecraft 服务器上暴露公共 HTTP API。

✨ 功能
- 验证真实连接的玩家是否拥有生成的代码
- 允许多个外部应用共用同一个 Minecraft 服务器进行验证
- 仅使用出站应用调用,保持 Minecraft 服务器的私密性
- 验证完成后向应用发送已验证的 Minecraft UUID 和用户名
- 自动过期未使用的代码
- 在服务器优雅关闭期间过期待处理的验证请求
- 提供管理员状态命令以检查当前的验证活动
- 支持本地化的游戏内消息
? 安装
- 安装带有 Java 25+ 的 PaperMC server
- 从 发布页面 下载最新的
MineVerify-x.x.x+mcx.x.x.jar
- 将 jar 文件放入服务器的
plugins/ 文件夹中
- 重启服务器或运行
/reload confirm
- 在
plugins/MineVerify/config.yml 中配置你的应用
? 命令用法
| 命令 |
权限 |
描述 |
/mineverify |
mineverify.use |
开始检查已配置应用中是否有待处理的验证请求。 |
/mineverify <code> |
mineverify.use |
验证当前连接玩家生成的代码。 |
/mineverify status |
mineverify.admin |
显示轮询状态、已配置应用、存储的请求以及上一次应用的响应。 |
/mineverify status requests |
mineverify.admin |
显示包含存储请求详细信息的管理员状态。 |
/mineverify 和 /mineverify <code> 必须由真实玩家执行。管理员状态命令可由管理员或从控制台运行。
⚙️ 配置
config.yml 定义了语言、远程应用和代码有效期。
language: "en_us"
apps:
my-app:
name: "Your App"
base-url: "https://your-app.com"
token: "generated-token-from-your-app"
poll-interval-seconds: 3
linking:
code-ttl-seconds: 60
| 键 |
默认值 |
描述 |
language |
en_us |
游戏内消息语言。可用值列于 config.yml 中。 |
apps.<id>.name |
<id> |
面向玩家的應用名称。 |
apps.<id>.base-url |
必填 |
完整的應用后端 URL,以 http:// 或 https:// 开头。 |
apps.<id>.token |
必填 |
MineVerify 在调用此應用时使用的 Bearer token。 |
apps.<id>.poll-interval-seconds |
3 |
仅在活跃的玩家触发轮询会话期间使用的轮询间隔。 |
linking.code-ttl-seconds |
60 |
生成代码的有效持续时间。 |
? 验证流程
- 應用为其自身用户创建内部请求。
- 應用要求玩家加入 Minecraft 服务器并运行
/mineverify。
- MineVerify 启动临时轮询会话。
- MineVerify 调用每个已配置的应用以获取待处理请求。
- MineVerify 为每个新的待处理请求生成代码并将其发送给所属應用。
- 應用向用户显示
/mineverify <code>。
- 玩家在游戏中运行
/mineverify <code>。
- MineVerify 验证代码并读取连接玩家的 UUID 和用户名。
- MineVerify 向應用报告验证结果或过期事件。
? 應用端点
始终是 MineVerify 联系應用,反之则不然。
因此,config.yml 中配置的每個應用都必須在其后端实现这些端点。
| 端点 |
方法 |
描述 |
/api/mineverify/pending-requests |
GET |
返回等待生成代码的應用请求。 |
/api/mineverify/code-created |
POST |
接收生成的代码和过期时间。 |
/api/mineverify/validated |
POST |
接收已验证的 Minecraft UUID 和用户名。 |
/api/mineverify/expired |
POST |
接收未使用代码的过期事件或服务器优雅关闭事件。 |
MineVerify 发送的每个请求均包含:
Authorization: Bearer <app-token>
[!IMPORTANT]
要将 MineVerify 完全集成到你的應用中,请遵循
docs/APP_INTEGRATION.md。
Crafted by

Sukikui
MineVerify
Lightweight PaperMC plugin allowing apps to verify Minecraft players through generated in-game codes.
? Overview
MineVerify lets external apps verify that a Minecraft account is controlled by a real player on
your server.
The app creates an internal verification request and asks the player to run /mineverify.
The plugin then polls configured apps, generates a temporary code, validates /mineverify <code>
in game, and reports the verified Minecraft UUID and username back to the app.
MineVerify only makes outbound requests to configured apps. It does not expose a public HTTP API on
the Minecraft server.

✨ Features
- Verifies that a real connected Minecraft player owns a generated code
- Lets several external apps use the same Minecraft server for verification
- Keeps the Minecraft server private by using outbound app calls only
- Sends the app the verified Minecraft UUID and username after validation
- Expires unused codes automatically
- Expires pending verifications during graceful server shutdowns
- Provides admin status commands to inspect current verification activity
- Supports localized in-game messages
? Installation
- Install a PaperMC server with Java 25+
- Download the latest
MineVerify-x.x.x+mcx.x.x.jar from the releases page
- Drop the jar into your server's
plugins/ folder
- Restart the server or run
/reload confirm
- Configure your apps in
plugins/MineVerify/config.yml
? Command Usage
| Command |
Permission |
Description |
/mineverify |
mineverify.use |
Starts checking configured apps for pending verification requests. |
/mineverify <code> |
mineverify.use |
Validates a generated code for the connected player. |
/mineverify status |
mineverify.admin |
Shows polling state, configured apps, stored requests, and last app responses. |
/mineverify status requests |
mineverify.admin |
Shows admin status with stored request details. |
/mineverify and /mineverify <code> must be run by a real player. Admin status commands can be
run by admins or from the console.
⚙️ Configuration
config.yml defines the language, remote apps, and code validity.
language: "en_us"
apps:
my-app:
name: "Your App"
base-url: "https://your-app.com"
token: "generated-token-from-your-app"
poll-interval-seconds: 3
linking:
code-ttl-seconds: 60
| Key |
Default |
Description |
language |
en_us |
In-game message language. Available values are listed in config.yml. |
apps.<id>.name |
<id> |
Player-facing app name. |
apps.<id>.base-url |
Required |
Full app backend URL, starting with http:// or https://. |
apps.<id>.token |
Required |
Bearer token used by MineVerify when calling this app. |
apps.<id>.poll-interval-seconds |
3 |
Poll interval used only during an active player-triggered polling session. |
linking.code-ttl-seconds |
60 |
Generated code validity duration. |
? Verification Flow
- The app creates an internal request for its own user.
- The app asks the player to join the Minecraft server and run
/mineverify.
- MineVerify starts a temporary polling session.
- MineVerify calls each configured app for pending requests.
- MineVerify generates a code for each new pending request and sends it to the owning app.
- The app shows
/mineverify <code> to the user.
- The player runs
/mineverify <code> in game.
- MineVerify validates the code and reads the connected player's UUID and username.
- MineVerify reports either validation or expiration to the app.
? App Endpoints
It's always MineVerify that contacts the app, never the opposite.
In this way, each app configured in config.yml must implement these endpoints on its own backend.
| Endpoint |
Method |
Description |
/api/mineverify/pending-requests |
GET |
Returns app requests waiting for a generated code. |
/api/mineverify/code-created |
POST |
Receives the generated code and expiration time. |
/api/mineverify/validated |
POST |
Receives the verified Minecraft UUID and username. |
/api/mineverify/expired |
POST |
Receives an expiration event for an unused code or a graceful server shutdown. |
Every request sent by MineVerify includes:
Authorization: Bearer <app-token>
[!IMPORTANT]
To fully integrate MineVerify into your app, follow
docs/APP_INTEGRATION.md.
Crafted by

Sukikui
评论 0
登录后参与评分
还没有评论,来抢沙发吧