简单的 /tpa 和 /tpahere 安全检测。当有人发送或接收 TPA 请求时,如果对方有最近因自定义原因导致的封禁记录,双方都会自动收到警告。这有助于在玩家接受请求前提醒他们注意潜在的破坏者或有毒玩家。
警告示例(可配置)

为什么使用此插件
大多数服务器都有 /history 命令,但没有人会在接受传送请求前实际去检查。当你意识到自己接受了来自破坏者的传送请求时,为时已晚。此插件会自动进行检查,让玩家在传送前做出明智的决定。
非常适合生存服务器,这些服务器通常常用 TPA,且存在破坏/盗窃问题。
命令
权限
tpawarning.receive - 允许接收警告消息。
使用方法
当玩家使用 LiteBans 被封禁时,该封禁记录会被添加到其历史中。当玩家收到之前被该玩家发出的 tp 请求(或试图传送到他们那里)时,玩家将在聊天栏收到警告。
根据你在配置文件中设置的内容,你可以指定要显示的具体警告类型。例如,我个人只关心关于破坏的封禁。我将关键词 "grief" 添加到列表中。现在,如果玩家的近期历史记录中包含 "grief" 的原因,将会向玩家展示。
要求 / 依赖
- Essentials(必需)
- LiteBans(必需)
配置文件
# ================================
# TPA 警告配置文件
# ================================
# 时间窗口设置
time-window:
# 检查用户历史记录的时间范围(天数)
# 默认值:90(3个月)
check-days: 90
# 封禁原因关键词
# 如果封禁原因包含以下任何关键词,将显示警告
# 所有比较均不区分大小写
ban-keywords:
- "theft"
- "grief"
- "steal"
- "stole"
- "scam"
- "rob"
- "took"
- "destroy"
- "kill"
# 警告消息设置
messages:
# 如果为 true,则在警告中显示实际的封禁原因
# 如果为 false,仅显示封禁数量
# 默认值:true
show-ban-reasons: true
# 关于其他玩家封禁历史的警告消息
# 占位符:%player%(玩家名称),%count%(封禁数量)
warning-header: "&c&l⚠ 警告!&r\n&c玩家 &e%player% &c拥有 &l%count% &r&c个最近的封禁记录,原因是:"
# 列表中每个原因的格式
# 占位符:%reason%(封禁原因文本)
reason-format: "&4• &c%reason%"
# 带有历史命令建议的页脚消息
# 占位符:%player%(玩家名称)
warning-footer: "\n&7查看完整历史:&a/history %player%"
Simple /tpa and /tpahere safety check. When someone sends or receives a TPA request, both players automatically get warned if the other person has recent bans for custom defined reasons. Useful to warn players of a potential griefer or toxic player beforing accepting the request.
Warning Example (Configurable)

Why Use This
Most servers have /history commands, but nobody actually checks before accepting a teleport request. By the time you realize you've accepted a teleport request from a griefer, it's too late. This plugin does the checking automatically so players can make informed decisions before teleporting.
Perfect for survival servers where TPA is commonly used and griefing/theft problem.
Commands
Permissions
tpawarning.receive - Allows receiving the warning message.
How To Use
When a player gets banned using LiteBans, the ban is added to their history. When a player gets a tp request from the previously banned player (or tries to teleport to them), the player will receive a warning in chat.
Depending on what you put in the config, you can specify specific warnings you want to show. For example, I personally only care about griefing bans. I add the keyword "grief" to the list. Now, if a player's recent history has reason containing "grief", it will be shown to the player.
Requirements / Dependencies
- Essentials (required)
- LiteBans (required)
Config
# ================================
# TPA Warning Configuration File
# ================================
# Time Window Settings
time-window:
# How far back (in days) to check for a user's history
# Default: 90 (3 months)
check-days: 90
# Ban Reason Keywords
# If a ban reason contains any of these keywords, a warning will be shown
# All comparisons are case-insensitive
ban-keywords:
- "theft"
- "grief"
- "steal"
- "stole"
- "scam"
- "rob"
- "took"
- "destroy"
- "kill"
# Warning Message Settings
messages:
# If true, show the actual ban reasons in the warning
# If false, just show the count of bans
# Default: true
show-ban-reasons: true
# Message sent when warning about another player's ban history
# Placeholders: %player% (player name), %count% (number of bans)
warning-header: "&c&l⚠ Warning!&r\n&cPlayer &e%player% &chas &l%count% &r&crecent ban(s) for:"
# How each reason is formatted in the list
# Placeholder: %reason% (the ban reason text)
reason-format: "&4• &c%reason%"
# Footer message with history command suggestion
# Placeholder: %player% (player name)
warning-footer: "\n&7Check full history: &a/history %player%"
评论 0
登录后参与评分
还没有评论,来抢沙发吧