LogPass
LogPass 允许服务器设置一个登录受限的服务器,任何拥有 LogPass 账户用户名和密码的用户都可以登录。
这不是一个允许用户使用其他服务器的用户名和密码连接的插件。没有在线认证服务器。
LogPass 账号与 Minecraft 用户名完全独立——它是一个独立的“用户名/密码”组合,仅由管理员创建。在玩家登录之前,无法在服务器上执行任何操作(移动、破坏方块、受到伤害、聊天或运行命令)。玩家的几乎所有属性——包括物品栏、末影箱、经验值、游戏模式、生命值、饥饿度、药水效果,甚至权限和 OP 状态——都属于 账号,而非其当前登录的 Minecraft 个人资料。
聊天格式为 <Minecraft用户名> [<Logpass用户名>] <消息>
例如:<Epiz [admin]> hi
首次设置时,请在控制台中使用 /pass create <用户名> <密码>
非 OP 的命令
/login <username> <password> - 登录 LogPass 账户
/login <username> <password> --force - 即使已登录其他账户也强制登录;会先干净地结束该会话,而不是拒绝操作
/logout - 登出你的 LogPass 账户(返回重生点)
/pass change <oldPassword> <newPassword> - 更改账户密码
/pass delete <password> - 永久删除你自己的 LogPass 账户,需通过输入密码确认
/uuid - 返回用户的 LogPass UUID
控制台或 OP 使用的命令
/pass create <username> <password> - 创建一个 LogPass 账户
/pass reset <username> <newPassword> - 重置 LogPass 账户的密码
/pass delete <username> - 删除一个 LogPass 账户(及其保存的物品栏/权限数据)
/pass setspawn - 设置新玩家的出生点,以及未登录成员停留的位置
/pass uuid <username> - 显示账户的 LuckPerms UUID,如果已安装 LuckPerms(参见 Permissions)
/pass op <username> <true|false> - 设置账户是否为 OP,如果 未 安装 LuckPerms(参见 Permissions)
/pass perm add <username> <node> - 授予账户一个权限节点,如果 未 安装 LuckPerms
/pass perm remove <username> <node> - 从账户撤销一个权限节点
/pass perm list <username> - 列出账户的权限节点
/pass uuid <username> - 获取 LogPass 用户 UUID
账户数据如何跟随玩家
从玩家加入游戏到其登录之前,所有数据均为空白:空物品栏、空末影箱、无经验值、默认生命值/饥饿值、无药水效果。他们还会被冻结在最后一次运行 /pass setspawn 时的位置。
他们一旦执行 /login,所有数据就会替换为该 账户 下保存的内容——一个新创建的账户将保持空白。他们也会被传送至该账户上次登出的位置,而不是服务器的出生点。
/logout(或断开连接)会将玩家当前的物品栏/末影箱/经验值/生命值/饥饿值/药水效果/位置保存回账户,然后立即清空。手动执行 /logout 还会将玩家传送回出生点。
由于这一切都与 Minecraft 配置文件无关,完全相同的账户可以从完全不同的 Minecraft 用户名登录,并接续之前的进度继续游戏。
权限
LogPass 将账户的权限(包括原版 OP)与当前登录到该账户的人关联起来。有两种工作方式,LogPass 会自动使用可用的方式:
安装 LuckPerms 时(可选,完整支持节点/组/继承关系):每个账户都会获得一个固定的 UUID,与任何真实的 Minecraft 账户无关,可通过 /pass create 或 /pass uuid 查看。使用正常的 LuckPerms 命令针对该 UUID 进行管理:
/lp user <uuid> permission set some.permission true
/lp user <uuid> permission set logpass.op true
未安装 LuckPerms 时:LogPass 会回退到其自带的简单内置存储——仅包含一个 OP 标志和每个账户的权限节点扁平列表,没有分组功能,但也无需额外插件:
/pass op <username> true|false
/pass perm add <username> <node>
/pass perm remove <username> <node>
/pass perm list <username>
无论哪种情况,权限都会在有人登录时立即生效,并在登出或断开连接时立即移除。
这种链接也支持反向操作。 如果管理员直接对当前已登录到某个账户的玩家运行原版 /op 或 /deop,这会自动保存到该账户上,因此此后它将跟随该账户而非特定的 Minecraft 配置文件。如果玩家当时没有登录到任何账户,原版的 op/deop 将按正常方式执行,不进行任何链接。
无论如何都有一个需要注意的地方:原版 OP 状态本身存储在服务器 ops.json 中,对应玩家的真实配置文件。LogPass 会在每次正常登出/断开连接时将其还原。
配置
config.yml
# 玩家在被踢出前必须 /login 的秒数
login-timeout-seconds: 60
# 允许的最小密码长度
min-password-length: 4
日志
以下内容均位于 plugins/LogPass/logs/ 目录下。这三个文件均为纯文本格式。
chat.log
每条发送的聊天消息,均带有双方身份标记。
[yyyy-mm-dd hh:mm:ss] Epiz [管理员] 嗨
[yyyy-mm-dd hh:mm:ss] Epiz [管理员] 你好
[yyyy-mm-dd hh:mm:ss] Epiz [管理员] 你是谁?
[yyyy-mm-dd hh:mm:ss] Epiz [管理员] 欢迎来到我的服务器
[yyyy-mm-dd hh:mm:ss] Epiz [管理员] 我是管理员
[yyyy-mm-dd hh:mm:ss] Epiz [管理员] 我很酷
[yyyy-mm-dd hh:mm:ss] Epiz [管理员] 英语?
[yyyy-mm-dd hh:mm:ss] Epiz [管理员] 嗨
commands.log
记录每一位玩家(无论是否已登录)执行的所有命令。由于 /login 和 /pass 的参数为密码,因此它们始终显示为 <redacted>(已隐藏),这些密码在磁盘上永远不会以明文形式存在。在玩家登录之前执行的任何操作,其账户标签均显示为 [-]。
[yyyy-mm-dd hh:mm:ss] Epiz [-] /login <redacted>
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /logout
[yyyy-mm-dd hh:mm:ss] Epiz [-] /login <redacted>
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /logout
[yyyy-mm-dd hh:mm:ss] Epiz [-] /login <redacted>
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /logout
[yyyy-mm-dd hh:mm:ss] Epiz [-] /login <redacted>
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /give
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /plugins
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /give
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /logout
[yyyy-mm-dd hh:mm:ss] Epiz [-] /plugins
[yyyy-mm-dd hh:mm:ss] Epiz [-] /login <redacted>
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /xp set @a 51 points
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /xp set @a 10 points
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /xp set @a 3 points
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /logout
stats.log
在三个时刻:LOGIN(登录)、LOGOUT(登出)和 QUIT(断开连接但仍处于登录状态时)捕获的生命值/食物/经验/游戏模式/位置的快照。有助于重建某人在任何时间点的位置和状态。
[yyyy-mm-dd hh:mm:ss] Epiz [-] JOIN health=20.0 food=20 xp-level=0 gamemode=SURVIVAL world=world x=-6.4 y=249.0 z=-91.5
[yyyy-mm-dd hh:mm:ss] Epiz [admin] LOGIN health=20.0 food=20 xp-level=0 gamemode=SURVIVAL world=world x=33.6 y=102.0 z=-63.0
[yyyy-mm-dd hh:mm:ss] Epiz [admin] LOGOUT health=20.0 food=20 xp-level=0 gamemode=CREATIVE world=world x=31.6 y=103.0 z=-63.2
[yyyy-mm-dd hh:mm:ss] Epiz [admin] LOGIN health=20.0 food=20 xp-level=0 gamemode=CREATIVE world=world x=31.6 y=103.0 z=-63.2
[yyyy-mm-dd hh:mm:ss] Epiz [admin] LOGOUT health=20.0 food=20 xp-level=0 gamemode=CREATIVE world=world x=28.8 y=104.0 z=-62.7
[yyyy-mm-dd hh:mm:ss] Epiz [admin] LOGIN health=20.0 food=20 xp-level=0 gamemode=CREATIVE world=world x=28.8 y=104.0 z=-62.7
[yyyy-mm-dd hh:mm:ss] Epiz [admin] LOGOUT health=20.0 food=20 xp-level=0 gamemode=CREATIVE world=world x=36.3 y=101.0 z=-55.9
[yyyy-mm-dd hh:mm:ss] Epiz [admin] LOGIN health=20.0 food=20 xp-level=0 gamemode=CREATIVE world=world x=36.3 y=101.0 z=-55.9
[yyyy-mm-dd hh:mm:ss] Epiz [admin] LOGOUT health=20.0 food=20 xp-level=0 gamemode=CREATIVE world=world x=37.2 y=102.0 z=-57.1
[yyyy-mm-dd hh:mm:ss] Epiz [admin] LOGIN health=20.0 food=20 xp-level=0 gamemode=CREATIVE world=world x=37.2 y=102.0 z=-57.1
PlayerData
每个账户在 plugins/LogPass/playerdata/ 下有一个文件,命名为 <logpassUsername>.yml。这是 /login 时恢复以及 /logout 时移除的所有内容——包括背包、盔甲、副手物品、末影箱、经验、游戏模式、生命值/饥饿度、活跃药水效果以及账户的最后位置。空的背包/盔甲/末影箱槽位存储为 null;在某些版本中,空的副手物品会显示为实际的 minecraft:air 物品而非 null——两者在重新加载时都被视为“无”。
<logpassUser>.yml
inventory:
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
armor:
- null
- null
- null
- null
offhand:
==: org.bukkit.inventory.ItemStack
id: minecraft:air
DataVersion: 4903
schema_version: 1
enderchest:
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
exp-level: 0
exp-progress: 0.42857143
total-experience: 0
gamemode: SURVIVAL
health: 20.0
food-level: 20
saturation: 5.0
exhaustion: 2.6739995
potion-effects: []
location:
world: world
x: 38.497286889540916
y: 99.0
z: -69.89819584703928
yaw: -60.59815
pitch: -47.39998
accounts.yml
每个账户在存储时都经过完整的加盐和哈希处理,如果发生数据泄露,密码也不会被泄露。
admin:
salt: pbBZNTh99eC4ytaVRCu0zw==
hash: do58nOGbw8JJcld9u46XUkmHCE72Z3zYsuqTj7H2rs4=
permissions.yml
仅在未安装 LuckPerms 时存在——这是上述原生权限存储,以账户用户名为键。通过 /pass op 和 /pass perm 进行管理,而非手动编辑。这基本上是一个简化版的 LuckPerms,没有群组或特殊聊天标签功能。
admin:
op: true
nodes:
- essentials.fly
- worldedit.wand
spawn.yml
由 /pass setspawn 设置。每位玩家加入时的落点、手动 /logout 发送回的位置,以及任何尚未认证的玩家保持冻结的位置。
world: world
x: -6.369723867482072
y: 249.0
z: -91.52465770728853
yaw: 0.4498288
pitch: 2.0999684
支持:
Logpass 邮箱:logpass@atomicmail.io
网站:
LogPass
LogPass allows servers to have a locked down server with login that can be logged in from any user with the username and password for their LogPass account.
This is NOT a plugin that allows people to connect with a username and password of a different server. There is no online authentication server.
A LogPass account is completely separate from a Minecraft username - it's its own username/password pair, created only by an admin. Nobody can do anything on the server (move, break blocks, take damage, chat, or run commands) until they log in, and everything about a player - inventory, ender chest, XP, game mode, health, hunger, potion effects, and even permissions/OP - belongs to the account, not the Minecraft profile it's currently logged in from.
Chat is in the format <MinecraftUsername> [<LogpassUsername>] <message>
e.g. <Epiz [admin]> hi
When First Setting Up Use /pass create <username> <password> In The Console
Commands for non OP
- /login <username> <password> - Log into a LogPass account
- /login <username> <password> --force - Log in even if you're already logged into a different account; cleanly ends that session first instead of refusing
- /logout - Log out of your LogPass account (returns you to spawn)
- /pass change <oldPassword> <newPassword> - Change your account's password
- /pass delete <password> - Permanently delete your own LogPass account, confirmed with its password
- /uuid - Returns with the users' LogPass UUID
Commands for Console or OP
- /pass create <username> <password> - Create a LogPass account
- /pass reset <username> <newPassword> - Resets a LogPass account's password
- /pass delete <username> - Deletes a LogPass account (and its saved inventory/permissions data)
- /pass setspawn - Sets where new players spawn, and where unlogged-in members linger
- /pass uuid <username> - Shows an account's LuckPerms UUID, if LuckPerms is installed (see Permissions)
- /pass op <username> <true|false> - Sets whether an account is OP, if LuckPerms is not installed (see Permissions)
- /pass perm add <username> <node> - Grants an account a permission node, if LuckPerms is not installed
- /pass perm remove <username> <node> - Revokes a permission node from an account
- /pass perm list <username> - Lists an account's permission nodes
- /pass uuid <username> - Retrieves LogPass user UUID
How an account's data follows it around
From the moment a player joins until they log in, everything is blank: empty inventory, empty ender chest, no XP, default health/hunger, no potion effects. They're also frozen in place at whatever location /pass setspawn was last run at.
The moment they /login, all of that gets swapped for whatever's saved under that account - a brand-new account just stays blank. They also get teleported to wherever that account last logged out from, not wherever the join spawn happens to be.
/logout (or disconnecting) saves the player's current inventory/ender chest/XP/health/hunger/potions/location back onto the account, then wipes it live again. A manual /logout also teleports the player back to spawn.
Because none of this is tied to a Minecraft profile, the exact same account can be logged into from a completely different Minecraft username and pick up right where it left off.
Permissions
LogPass links an account's permissions - including vanilla OP - to whoever is currently logged into it. There are two ways this works, and LogPass automatically uses whichever is available:
With LuckPerms installed (optional, full node/group/inheritance support): every account gets a fixed UUID unrelated to any real Minecraft account, shown by /pass create or /pass uuid. Manage it with normal LuckPerms commands targeting that UUID:
/lp user <uuid> permission set some.permission true
/lp user <uuid> permission set logpass.op true
Without LuckPerms: LogPass falls back to its own simple built-in store - just an OP flag and a flat list of permission nodes per account, no groups, but no extra plugins needed either:
/pass op <username> true|false
/pass perm add <username> <node>
/pass perm remove <username> <node>
/pass perm list <username>
Either way, permissions apply the moment someone logs in and are removed the moment they log out or disconnect.
The link also works in reverse. If an admin runs vanilla /op or /deop directly on a player who's currently logged into an account, that gets saved onto the account automatically, so it keeps following the account from then on - not just that one Minecraft profile. If the player isn't logged into anything at the time, the vanilla op/deop just happens normally with nothing linked.
One caveat either way: vanilla OP status itself lives in the server's ops.json against the player's real profile. LogPass reverts it on every normal logout/disconnect.
Config
config.yml
# Seconds a player has to /login before being kicked
login-timeout-seconds: 60
# Minimum allowed password length
min-password-length: 4
Logs
Everything below lives under plugins/LogPass/logs/. All three files are plain text format.
chat.log
Every chat message sent, tagged with both identities.
[yyyy-mm-dd hh:mm:ss] Epiz [admin] hi
[yyyy-mm-dd hh:mm:ss] Epiz [admin] hello
[yyyy-mm-dd hh:mm:ss] Epiz [admin] who are you?
[yyyy-mm-dd hh:mm:ss] Epiz [admin] welcome to my server
[yyyy-mm-dd hh:mm:ss] Epiz [admin] im a admin
[yyyy-mm-dd hh:mm:ss] Epiz [admin] im cool
[yyyy-mm-dd hh:mm:ss] Epiz [admin] english?
[yyyy-mm-dd hh:mm:ss] Epiz [admin] hi
commands.log
Every command run by every player, logged in or not. /login and /pass are always shown as <redacted> since their arguments are passwords - those never touch the disk in plain text. The account tag shows [-] for anything run before that player has logged in.
[yyyy-mm-dd hh:mm:ss] Epiz [-] /login <redacted>
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /logout
[yyyy-mm-dd hh:mm:ss] Epiz [-] /login <redacted>
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /logout
[yyyy-mm-dd hh:mm:ss] Epiz [-] /login <redacted>
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /logout
[yyyy-mm-dd hh:mm:ss] Epiz [-] /login <redacted>
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /give
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /plugins
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /give
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /logout
[yyyy-mm-dd hh:mm:ss] Epiz [-] /plugins
[yyyy-mm-dd hh:mm:ss] Epiz [-] /login <redacted>
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /xp set @a 51 points
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /xp set @a 10 points
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /xp set @a 3 points
[yyyy-mm-dd hh:mm:ss] Epiz [admin] /logout
stats.log
A snapshot of health/food/XP/gamemode/location taken at three moments: LOGIN, LOGOUT, and QUIT (disconnect while still logged in). Useful for reconstructing where someone was and what state they were in at any point.
[yyyy-mm-dd hh:mm:ss] Epiz [-] JOIN health=20.0 food=20 xp-level=0 gamemode=SURVIVAL world=world x=-6.4 y=249.0 z=-91.5
[yyyy-mm-dd hh:mm:ss] Epiz [admin] LOGIN health=20.0 food=20 xp-level=0 gamemode=SURVIVAL world=world x=33.6 y=102.0 z=-63.0
[yyyy-mm-dd hh:mm:ss] Epiz [admin] LOGOUT health=20.0 food=20 xp-level=0 gamemode=CREATIVE world=world x=31.6 y=103.0 z=-63.2
[yyyy-mm-dd hh:mm:ss] Epiz [admin] LOGIN health=20.0 food=20 xp-level=0 gamemode=CREATIVE world=world x=31.6 y=103.0 z=-63.2
[yyyy-mm-dd hh:mm:ss] Epiz [admin] LOGOUT health=20.0 food=20 xp-level=0 gamemode=CREATIVE world=world x=28.8 y=104.0 z=-62.7
[yyyy-mm-dd hh:mm:ss] Epiz [admin] LOGIN health=20.0 food=20 xp-level=0 gamemode=CREATIVE world=world x=28.8 y=104.0 z=-62.7
[yyyy-mm-dd hh:mm:ss] Epiz [admin] LOGOUT health=20.0 food=20 xp-level=0 gamemode=CREATIVE world=world x=36.3 y=101.0 z=-55.9
[yyyy-mm-dd hh:mm:ss] Epiz [admin] LOGIN health=20.0 food=20 xp-level=0 gamemode=CREATIVE world=world x=36.3 y=101.0 z=-55.9
[yyyy-mm-dd hh:mm:ss] Epiz [admin] LOGOUT health=20.0 food=20 xp-level=0 gamemode=CREATIVE world=world x=37.2 y=102.0 z=-57.1
[yyyy-mm-dd hh:mm:ss] Epiz [admin] LOGIN health=20.0 food=20 xp-level=0 gamemode=CREATIVE world=world x=37.2 y=102.0 z=-57.1
PlayerData
One file per account under plugins/LogPass/playerdata/, named <logpassUsername>.yml. This is everything that gets restored on /login and removed on /logout - inventory, armor, off-hand, ender chest, XP, game mode, health/hunger, active potion effects, and the account's last location. Empty inventory/armor/ender chest slots are stored as null; an empty off-hand shows up as an actual minecraft:air item rather than null on some versions - both are treated as "nothing" when loaded back in.
<logpassUser>.yml
inventory:
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
armor:
- null
- null
- null
- null
offhand:
==: org.bukkit.inventory.ItemStack
id: minecraft:air
DataVersion: 4903
schema_version: 1
enderchest:
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
- null
exp-level: 0
exp-progress: 0.42857143
total-experience: 0
gamemode: SURVIVAL
health: 20.0
food-level: 20
saturation: 5.0
exhaustion: 2.6739995
potion-effects: []
location:
world: world
x: 38.497286889540916
y: 99.0
z: -69.89819584703928
yaw: -60.59815
pitch: -47.39998
accounts.yml
Every Account is Fully salted and hashed when stored and if data leaks occur passwords will not get leaked.
admin:
salt: pbBZNTh99eC4ytaVRCu0zw==
hash: do58nOGbw8JJcld9u46XUkmHCE72Z3zYsuqTj7H2rs4=
permissions.yml
Only present if LuckPerms is not installed - this is the native permission store described above, keyed by account username. Managed with /pass op and /pass perm rather than by hand. This is basically a simple version of LuckpPerms with no groups or special chat tags.
admin:
op: true
nodes:
- essentials.fly
- worldedit.wand
spawn.yml
Set by /pass setspawn. Where every player lands on join, where a manual /logout sends them back to, and where anyone still unauthenticated stays frozen.
world: world
x: -6.369723867482072
y: 249.0
z: -91.52465770728853
yaw: 0.4498288
pitch: 2.0999684
Support:
Logpass Email: logpass@atomicmail.io
Website:
评论 0
登录后参与评分
还没有评论,来抢沙发吧