?️ OPShield
适用于 Paper 1.21+ 的高级安全与命令保护插件
保护你的服务器免受滥用——锁定 OP 权限,追踪所有操作,即时阻止攻击者。
? 目录
- ✨ 功能特性
- ? 安全系统
- ? 审计与日志
- ? 运行环境
- ? 安装指南
- ⌨️ 指令与权限
- ? 配置说明
- ? 故障排除
- ❓ 常见问题
- ? 致谢
✨ 功能特性
? OP 权限保护
- 密码锁定的
/op 和 /deop 指令——无密码则无法更改权限
- 异步 PBKDF2 验证——密码哈希计算在主线程之外进行;即使遭遇暴力破解攻击,也不会影响 TPS
- 认证会话令牌——一次成功登录后,可配置的会话窗口允许管理员跳过重复输入密码(
security.session_timeout_minutes,默认 30 分钟)
- 断开连接时清除会话——会话不会在重连时保留
- 全局认证并发上限——全服 PBKDF2 操作限制为最多 4 个并发验证,防止在大规模攻击下导致 CPU 过载
- PBKDF2-HMAC-SHA256 哈希存储——配置文件中绝不保存明文密码
- 可配置的 PBKDF2 迭代次数(
security.password.pbkdf2_iterations)
- 自动从旧版明文和 SHA-256 哈希迁移
- 自动升级旧版哈希——下次成功登录时,SHA-256 将静默替换为 PBKDF2(
security.password.auto_upgrade_legacy_hash)
- 启动时若检测到旧的 SHA-256 哈希,控制台会发出警告
- OP 白名单——仅允许预定义的玩家名称使用
/op
? 敏感指令保护
- 禁止非 OP 玩家执行危险指令(
blocked_commands)
- 可选择性地禁止 OP 玩家执行某些指令(
blocked_op_commands)
- 通过前缀列表屏蔽整个指令命名空间(
blocked_command_prefixes)
- 别名与命名空间解析——拦截通过
minecraft:op 或插件别名进行的绕过尝试
- 受信任的工作人员拥有单玩家绕过权限(
opshield.bypass)
? 暴力破解检测与锁定
- 可配置的最大失败尝试次数以触发锁定(
security.lockout.max-attempts)
- 指数退避机制——每次违规后锁定时间翻倍
- 可选的 IP 镜像锁定(
security.lockout.track_ip)
- 冷却期后锁定计数衰减(
security.lockout.count_decay_hours)
- 持久化跟踪——锁定状态在服务端重启后依然保留
- 通过
/opshield unlock <player|ip> 手动解锁
?️ 影子封禁系统
- 当触发被屏蔽的敏感指令时,发送虚假的成功消息而非错误提示
- 每次触发都会增加玩家隐藏的“影子封禁”等级
- 等级在服务端重启后持久保留
- 当达到
shadow_ban.auto_punish_level 时,自动升级为真实惩罚
- 设置
auto_punish_level: 99 可保持伪装行为而不进行升级惩罚
- 虚假消息来自语言文件——支持按区域设置完全自定义
⚠️ 自动惩罚系统
- 惩罚模式:
kick(踢出)、ban(封禁)、ban-ip(封禁 IP)、firewall(防火墙)、custom(自定义)
- 持久化的滚动窗口阈值——重启和崩溃后状态不丢失
- 防火墙模式通过
ProcessBuilder 异步运行操作系统脚本,并支持可配置的超时时间
- 自定义模式支持
{player} 和 {ip} 占位符
- 针对检测到共享同一 IP 的账户实施 IP 限制自动惩罚
? 多语言支持
- 内置语言文件:English (
en)、Vietnamese (vn)、Russian (ru)
- 缺失键值时自动回退到英语
- 通过在
config.yml 中设置 language: "en" 切换语言
? 审计与日志
- 记录所有权限变更、密码失败、指令拦截和惩罚操作
- 异步队列——日志写入绝不影响主线程
- 队列容量限制——
audit.max_queue_size 防止因磁盘写入长时间失败而导致 OOM(内存溢出)
- 双输出格式——
audit.format: plain(默认人类可读)或 audit.format: json(机器可读,每行一个 JSON 对象)
- UTF-8 安全——使用 NIO
Files.write() 并显式指定字符集
- 失败重试——写入失败时会重新入队,而不是静默丢弃
- 可配置的文件轮转:
audit.max_file_size_mb 和 audit.log_retention(最多保留 N 个备份文件)
- 可选的控制台镜像输出:
audit.console_output: true
- 日志文件位置:
plugins/OPShield/audit.log、audit.log.1 … audit.log.N
? 运行环境
| 组件 |
版本 |
| Java |
21+ |
| Paper |
1.21+ |
| Folia |
❌ 不支持 |
? 安装指南
- 下载插件
.jar 文件
- 将其放入服务端的
plugins/ 文件夹
- 启动服务端——OPShield 会生成随机密码并在控制台首次打印显示
- 将密码保存在安全的地方(它只会显示一次)
- 授予权限——在你的权限插件(如 LuckPerms)的管理员组中添加
opshield.admin。OPShield 不再仅基于 OP 状态授予权限(v1.8.0 起更改)
- 打开
plugins/OPShield/config.yml 以自定义行为
- 在游戏中运行
/opshield reload 或重启服务端以应用更改 ✅
从 1.7.0 升级? data.yml 将在首次启动时自动迁移。你只需更新权限插件的设置——请参阅更新日志中的 CRITICAL 注意事项。
提示: 如果你已有旧版本的 op_password 明文值,
OPShield 会自动将其迁移至 op_password_hash 并移除明文条目。
⌨️ 指令
| 命令 |
描述 |
/op <player> [password] |
使用密码验证授予 OP 权限 |
/deop <player> [password] |
使用密码验证移除 OP 权限 |
/opshield reload |
重新加载配置 |
/opshield unlock <player|ip> |
清除玩家或 IP 的所有跟踪状态 |
/opshield status |
显示运行时统计信息(活跃会话、认证队列、被标记的 IP 等) |
? 权限
⚠️ v1.8.0 变更: 所有权限默认值为 false。你必须通过权限插件显式授予它们。
| 权限 |
默认值 |
描述 |
opshield.* |
false |
通配符 — 授予所有权限 |
opshield.admin |
false |
授予所有子权限 |
opshield.reload |
false |
重新加载 OPShield 配置 |
opshield.unlock |
false |
解锁受跟踪的玩家或 IP |
opshield.status |
false |
查看运行时统计信息 |
opshield.op |
false |
使用受密码保护的 /op |
opshield.deop |
false |
使用受密码保护的 /deop |
opshield.bypass |
false |
绕过非 OP 受限命令的拦截 |
LuckPerms 设置示例
/lp group admin permission set opshield.admin true
? 配置
在 plugins/OPShield/ 下生成的文件:
config.yml — 主配置文件
data.yml — 持久化运行时状态(封禁、影子ban等级、IP窗口)
languages/en.yml — 英文消息
languages/vn.yml — 越南语消息
languages/ru.yml — 俄语消息
⚙️ 关键配置选项
# 启用详细的控制台日志以便调试(生产环境请禁用)
debug: false
# 密码安全
security:
lockout:
enabled: true
max-attempts: 3
duration-minutes: 3
track_ip: true
count_decay_hours: 168
# 成功认证后的会话超时时间(0 = 禁用,始终需要密码)
session_timeout_minutes: 30
password:
pbkdf2_iterations: 120000 # 范围:10000 – 1000000
auto_upgrade_legacy_hash: true # 登录时静默升级 SHA-256 → PBKDF2
# 自动惩罚
auto_punishment:
enabled: true
threshold: 5
window_seconds: 300
command: "kick" # kick | ban | ban-ip | firewall | custom
firewall_timeout_seconds: 10
# 影子ban (Shadow Ban)
shadow_ban:
enabled: true
auto_punish_level: 5
# 审计日志
audit:
console_output: true
max_file_size_mb: 5
log_retention: 3
max_queue_size: 10000 # 0 = 无限制(不推荐)
format: "plain" # plain | json
? 按服务器规模推荐的设置
小型服务器(≤ 20 名玩家)
security.lockout.max-attempts: 3
security.lockout.duration-minutes: 5
ip_limit.max_accounts: 2
auto_punishment.enabled: false
shadow_ban.auto_punish_level: 10
中型服务器(20–100 名玩家)
security.lockout.max-attempts: 3
security.lockout.duration-minutes: 3
ip_limit.max_accounts: 3
auto_punishment.enabled: true
auto_punishment.command: kick
auto_punishment.threshold: 5
shadow_ban.auto_punish_level: 5
大型服务器(100+ 名玩家)
security.lockout.max-attempts: 2
security.lockout.duration-minutes: 10
ip_limit.max_accounts: 2
auto_punishment.enabled: true
auto_punishment.command: ban-ip
auto_punishment.threshold: 3
shadow_ban.auto_punish_level: 3
? 防火墙模式设置
防火墙模式会异步执行操作系统脚本。要启用它:
auto_punishment:
command: "firewall"
allow_unsafe_firewall_exec: true
firewall_timeout_seconds: 10
# Linux:
firewall_script: "iptables -A INPUT -s {ip} -j DROP"
# Windows:
# firewall_script: "netsh advfirewall firewall add rule name=OPShield dir=in action=block remoteip={ip}"
如果 allow_unsafe_firewall_exec 为 false,防火墙模式将回退到安全的踢出操作。
? 故障排除
管理员每次输入 /op 命令都需要输入密码
OPShield 在每次成功认证后授予一个会话。请检查:
config.yml 中的 security.session_timeout_minutes — 如果设置为 0,则禁用了会话
- 当你断开连接时,会话会被清除;如果你不断重连,则需要重新进行身份验证
- 运行
/opshield status 以查看有多少个活跃会话
无法使用 /op — “密码错误”
需要提供密码。请运行:
/op <yourname> <password>
如果你忘记了密码,请在 config.yml 中清除 op_password_hash 并重启服务器 —— 将生成新密码并在控制台中打印出来。
从 1.7.0 升级后,管理员无法使用 /opshield
在 v1.8.0 中,权限现在默认为 false 而不是 op。你需要显式授予该权限:
/lp group admin permission set opshield.admin true
玩家被锁定且无法再次尝试
管理员可以手动清除锁定:
/opshield unlock <playername>
/opshield unlock <ip-address>
自动惩罚未触发
请检查以下内容:
config.yml 中的 auto_punishment.enabled: true
- 玩家使用的命令是否列在
auto_punishment.sensitive_commands 中
shadow_ban.enabled — 如果为 true,玩家可能会先收到虚假的成功消息;等级必须达到 auto_punish_level
- 任何配置更改后运行
/opshield reload
- 运行
/opshield status 以查看当前的影子ban等级和惩罚状态
审计日志为空或未更新
- 检查
audit.console_output: true 以确认日志记录已激活
- 检查
plugins/OPShield/ 文件夹的写入权限
- 如果达到
audit.max_queue_size,控制台会出现 SEVERE 警告 —— 请检查磁盘空间
配置更改未生效
在游戏内或控制台中运行:
/opshield reload
❓ 常见问题
OPShield 会取代 /op 吗?
不会——它只是拦截并包装了该命令。原始的 /op 行为得以保留,但被密码保护所限制。
密码存储安全吗?
是的——密码使用 PBKDF2-HMAC-SHA256 进行哈希处理,并带有随机盐值和 120,000 次迭代(可配置)。明文永远不会写入磁盘。
它支持 Spigot 或 Folia 吗?
仅支持 Paper 1.21+。Spigot 可能可用,但未经验证。Folia 明确不支持(folia-supported: false)。
我可以完全禁用自动惩罚吗?
可以——设置 auto_punishment.enabled: false。影子禁令虚假消息仍将独立正常工作。
如果服务器在封禁期间重启会发生什么?
封禁状态会持久化到 data.yml,并在启动时恢复。玩家无法通过崩溃或重启服务器来绕过封禁。
我可以有多个语言文件吗?
可以——所有三个捆绑文件(en、vn、ru)始终存在。通过 config.yml 中的 language: 进行切换。缺失的键会自动回退到捆绑的英文默认值。
v2.0.0 有什么变化?
线程安全重构——修复了五个竞态条件和可见性 bug:
ArrayDeque 竞态条件 — 替换为 ConcurrentLinkedDeque,以防止当异步清理任务和主线程事件处理器同时访问同一个双端队列时出现 ConcurrentModificationException 和数据损坏。
- 非易失性配置字段 —
lockoutDecayHours、autoPunishmentWindowSeconds、ipLimitTimeWindowSeconds 和 sessionTimeoutMs 现在设为 volatile,以便异步任务在 /opshield reload 后始终看到最新值。
- 非易失性
AuditLogger 字段 — consoleOutput、maxBytes、maxBackups、maxQueueSize 和 format 现在设为 volatile。
- IP 范围检查 — 将 16 个手动
startsWith() 检查替换为 InetAddress 谓词,补充了之前缺失的链路本地范围检测。
- 审计日志级别 — 审计控制台输出现在使用
INFO 而不是 WARNING。
详见 Changelog。
v1.9.1 有什么变化?
补丁版本中修复了六个 bug:审计日志中的重复时间戳、缺少会话授予/活跃消息、影子禁令诱饵消息丢失颜色、指数退避计数过早重置(导致 count_decay_hours 无效),以及 /opshield reload 权限检查顺序。详见 Changelog。
v1.9.0 有什么变化?
最大的变化是 异步 PBKDF2 认证(不再受暴力破解影响 TPS)和 会话令牌(在会话窗口内无需每次输入密码即可执行命令)。完整列表请参见 Changelog。
v1.8.0 有什么变化?
最重要的变化是 权限默认值 — 完整列表请参见 Changelog。简而言之:在 LuckPerms 中将 opshield.admin 授予你的管理员组。
? 致谢
作者: Duong2012G
许可证: Apache 2.0
网站:
专为安全、专业的 Minecraft 服务器打造。
?️ OPShield
Advanced security & command protection plugin for Paper 1.21+
Protect your server from abuse — secure OP access, track every action, stop attackers instantly.
? Table of Contents
- ✨ Features
- ? Security System
- ? Audit & Logging
- ? Requirements
- ? Installation
- ⌨️ Commands & Permissions
- ? Configuration
- ? Troubleshooting
- ❓ FAQ
- ? Credits
✨ Features
? OP Protection
- Password-gated
/op and /deop — no password, no privilege changes
- Async PBKDF2 verification — password hashing runs off the main thread; zero TPS impact even under brute-force attack
- Authenticated session tokens — after one successful login, a configurable session window lets admins skip re-entering the password (
security.session_timeout_minutes, default 30 min)
- Session cleared on disconnect — sessions are never carried across reconnections
- Global auth concurrency cap — server-wide PBKDF2 operations capped at 4 concurrent verifications to prevent CPU saturation under mass attack
- PBKDF2-HMAC-SHA256 hashed storage — plaintext never kept in config
- Configurable PBKDF2 iteration count (
security.password.pbkdf2_iterations)
- Automatic migration from legacy plaintext and SHA-256 hashes
- Auto-upgrade legacy hashes — on next successful login, SHA-256 is silently replaced with PBKDF2 (
security.password.auto_upgrade_legacy_hash)
- Console warning if a legacy SHA-256 hash is detected on startup
- OP whitelist — restrict
/op to a predefined set of player names
? Sensitive Command Protection
- Block dangerous commands for non-OP players (
blocked_commands)
- Optionally block commands even for OP players (
blocked_op_commands)
- Block entire command namespaces via prefix list (
blocked_command_prefixes)
- Alias and namespace resolution — bypass attempts via
minecraft:op or plugin aliases are caught
- Per-player bypass permission (
opshield.bypass) for trusted staff
? Brute-force Detection & Lockout
- Configurable failed-attempt limit before lockout (
security.lockout.max-attempts)
- Exponential backoff — each offence doubles the lockout duration
- Optional IP-mirrored lockout (
security.lockout.track_ip)
- Lockout count decay after a cooling-off period (
security.lockout.count_decay_hours)
- Persistent tracking — lockout state survives server restarts
- Manual unlock via
/opshield unlock <player|ip>
?️ Shadow Ban System
- Sensitive blocked commands send a fake success message instead of an error
- Each trigger increments the player's hidden shadow-ban level
- Level persists across restarts
- Auto-escalates to real punishment when
shadow_ban.auto_punish_level is reached
- Set
auto_punish_level: 99 to keep decoy behaviour without escalation
- Fake messages come from language files — fully customisable per locale
⚠️ Auto Punishment System
- Punishment modes:
kick, ban, ban-ip, firewall, custom
- Persistent rolling-window threshold — survives restarts and crashes
- Firewall mode runs an OS script asynchronously via
ProcessBuilder with configurable timeout
- Custom mode supports
{player} and {ip} placeholders
- IP-limit auto-punishment for accounts detected sharing the same IP
? Multi-Language Support
- Bundled language files: English (
en), Vietnamese (vn), Russian (ru)
- Automatic fallback to English for any missing key
- Switch language via
language: "en" in config.yml
? Audit & Logging
- Every privilege change, password failure, command block, and punishment is logged
- Async queue — log writes never touch the main thread
- Queue capacity limit —
audit.max_queue_size prevents OOM if disk writes fail for extended periods
- Dual output format —
audit.format: plain (default human-readable) or audit.format: json (machine-readable, one JSON object per line)
- UTF-8 safe — uses NIO
Files.write() with explicit charset
- Retry on failure — failed writes are re-queued instead of silently discarded
- Configurable rotation:
audit.max_file_size_mb and audit.log_retention (up to N backup files)
- Optional console mirror:
audit.console_output: true
- Log files:
plugins/OPShield/audit.log, audit.log.1 … audit.log.N
? Requirements
| Component |
Version |
| Java |
21+ |
| Paper |
1.21+ |
| Folia |
❌ Not supported |
? Installation
- Download the plugin
.jar
- Drop it into your server's
plugins/ folder
- Start the server — OPShield will generate a random password and print it once in the console
- Save the password somewhere safe (it is only shown once)
- Grant permissions — add
opshield.admin to your admin group in your permission plugin (e.g. LuckPerms). OPShield no longer grants permissions based on OP status alone (changed in v1.8.0)
- Open
plugins/OPShield/config.yml to customise behaviour
- Run
/opshield reload in-game or restart to apply changes ✅
Upgrading from 1.7.0? data.yml is automatically migrated on first boot. You only need to update your permission plugin setup — see the CRITICAL note in the changelog.
Tip: If you already have an op_password plaintext value from an older version,
OPShield will automatically migrate it to op_password_hash and remove the plaintext entry.
⌨️ Commands
| Command |
Description |
/op <player> [password] |
Grant OP with password verification |
/deop <player> [password] |
Remove OP with password verification |
/opshield reload |
Reload configuration |
/opshield unlock <player|ip> |
Clear all tracking state for a player or IP |
/opshield status |
Show runtime statistics (active sessions, auth queue, flagged IPs, etc.) |
? Permissions
⚠️ Changed in v1.8.0: All permissions now default to false. You must grant them explicitly via a permission plugin.
| Permission |
Default |
Description |
opshield.* |
false |
Wildcard — grants all permissions |
opshield.admin |
false |
Grants all child permissions |
opshield.reload |
false |
Reload OPShield configuration |
opshield.unlock |
false |
Unlock a tracked player or IP |
opshield.status |
false |
View runtime statistics |
opshield.op |
false |
Use password-protected /op |
opshield.deop |
false |
Use password-protected /deop |
opshield.bypass |
false |
Bypass non-OP restricted command blocking |
Example LuckPerms setup
/lp group admin permission set opshield.admin true
? Configuration
Files generated under plugins/OPShield/:
config.yml — main configuration
data.yml — persistent runtime state (lockouts, shadow-ban levels, IP windows)
languages/en.yml — English messages
languages/vn.yml — Vietnamese messages
languages/ru.yml — Russian messages
⚙️ Key Config Options
# Enable verbose console logging for troubleshooting (disable in production)
debug: false
# Password security
security:
lockout:
enabled: true
max-attempts: 3
duration-minutes: 3
track_ip: true
count_decay_hours: 168
# Session timeout after successful auth (0 = disable, always require password)
session_timeout_minutes: 30
password:
pbkdf2_iterations: 120000 # range: 10000 – 1000000
auto_upgrade_legacy_hash: true # silently upgrade SHA-256 → PBKDF2 on login
# Auto-punishment
auto_punishment:
enabled: true
threshold: 5
window_seconds: 300
command: "kick" # kick | ban | ban-ip | firewall | custom
firewall_timeout_seconds: 10
# Shadow ban
shadow_ban:
enabled: true
auto_punish_level: 5
# Audit log
audit:
console_output: true
max_file_size_mb: 5
log_retention: 3
max_queue_size: 10000 # 0 = unlimited (not recommended)
format: "plain" # plain | json
? Recommended settings by server size
Small server (≤ 20 players)
security.lockout.max-attempts: 3
security.lockout.duration-minutes: 5
ip_limit.max_accounts: 2
auto_punishment.enabled: false
shadow_ban.auto_punish_level: 10
Medium server (20–100 players)
security.lockout.max-attempts: 3
security.lockout.duration-minutes: 3
ip_limit.max_accounts: 3
auto_punishment.enabled: true
auto_punishment.command: kick
auto_punishment.threshold: 5
shadow_ban.auto_punish_level: 5
Large server (100+ players)
security.lockout.max-attempts: 2
security.lockout.duration-minutes: 10
ip_limit.max_accounts: 2
auto_punishment.enabled: true
auto_punishment.command: ban-ip
auto_punishment.threshold: 3
shadow_ban.auto_punish_level: 3
? Firewall mode setup
Firewall mode executes an OS script asynchronously. To enable it:
auto_punishment:
command: "firewall"
allow_unsafe_firewall_exec: true
firewall_timeout_seconds: 10
# Linux:
firewall_script: "iptables -A INPUT -s {ip} -j DROP"
# Windows:
# firewall_script: "netsh advfirewall firewall add rule name=OPShield dir=in action=block remoteip={ip}"
If allow_unsafe_firewall_exec is false, firewall mode falls back to a safe kick.
? Troubleshooting
Admin needs to enter password every single /op command
OPShield grants a session after each successful authentication. Check:
security.session_timeout_minutes in config.yml — if set to 0, sessions are disabled
- The session is cleared when you disconnect; if you keep reconnecting you will need to re-authenticate
- Run
/opshield status to see how many active sessions exist
Cannot use /op — "Incorrect password"
The password is required. Run:
/op <yourname> <password>
If you forgot the password, clear op_password_hash in config.yml and restart — a new password will be generated and printed in the console.
Admin cannot use /opshield after upgrading from 1.7.0
In v1.8.0, permissions now default to false instead of op. You need to explicitly grant the permission:
/lp group admin permission set opshield.admin true
Player is locked out and cannot try again
An admin can manually clear the lockout:
/opshield unlock <playername>
/opshield unlock <ip-address>
Auto-punishment is not triggering
Check the following:
auto_punishment.enabled: true in config.yml
- The command the player used is listed in
auto_punishment.sensitive_commands
shadow_ban.enabled — if true, the player may be getting fake success messages first; level must reach auto_punish_level
- Run
/opshield reload after any config change
- Run
/opshield status to see current shadow-ban levels and punish state
Audit log is empty or not updating
- Check
audit.console_output: true to confirm logging is active
- Check write permissions on the
plugins/OPShield/ folder
- If
audit.max_queue_size is reached, a SEVERE warning appears in console — check disk space
Config changes are not taking effect
Run in-game or console:
/opshield reload
❓ FAQ
Does OPShield replace /op?
No — it intercepts and wraps it. The original /op behaviour is preserved but gated behind a password.
Is the password stored securely?
Yes — passwords are hashed using PBKDF2-HMAC-SHA256 with a random salt and 120,000 iterations (configurable). The plaintext is never written to disk.
Does it support Spigot or Folia?
Paper 1.21+ only. Spigot may work but is not tested. Folia is explicitly not supported (folia-supported: false).
Can I disable auto-punishment entirely?
Yes — set auto_punishment.enabled: false. Shadow-ban fake messages will still work independently.
What happens if the server restarts during a lockout?
Lockout state is persisted to data.yml and restored on startup. Players cannot bypass lockouts by crashing or restarting the server.
Can I have multiple language files?
Yes — all three bundled files (en, vn, ru) are always present. Switch via language: in config.yml. Missing keys automatically fall back to the bundled English defaults.
What changed in v2.0.0?
Thread-safety overhaul — five race conditions and visibility bugs fixed:
ArrayDeque race condition — replaced with ConcurrentLinkedDeque to prevent ConcurrentModificationException and data corruption when the async cleanup task and main-thread event handler accessed the same deque simultaneously.
- Non-volatile config fields —
lockoutDecayHours, autoPunishmentWindowSeconds, ipLimitTimeWindowSeconds, and sessionTimeoutMs are now volatile so async tasks always see up-to-date values after /opshield reload.
- Non-volatile
AuditLogger fields — consoleOutput, maxBytes, maxBackups, maxQueueSize, and format are now volatile.
- IP range check — replaced 16 manual
startsWith() checks with InetAddress predicates, adding previously missing link-local range detection.
- Audit log level — audit console output now uses
INFO instead of WARNING.
See the Changelog for details.
What changed in v1.9.1?
Six bugs fixed in a patch release: double timestamps in audit log, missing session-granted/active messages, shadow-ban decoy messages losing their colours, exponential backoff count being reset too early (making count_decay_hours ineffective), and the /opshield reload permission check order. See the Changelog for details.
What changed in v1.9.0?
The biggest changes are async PBKDF2 authentication (no more TPS impact under brute-force) and session tokens (no need to re-type the password every command within the session window). See the Changelog for the full list.
What changed in v1.8.0?
The most important change is permission defaults — see the Changelog for the full list. The short version: grant opshield.admin to your admin group in LuckPerms.
? Credits
Author: Duong2012G
License: Apache 2.0
Website:
Built for secure, professional Minecraft servers.
评论 0
登录后参与评分
还没有评论,来抢沙发吧