Change a LoginSecurity password without exposing it to staff

Applies to: LoginSecurity; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

A player who knows the current LoginSecurity password can change it privately through the plugin command. Keep both passwords out of tickets, screenshots and shared console transcripts.

Follow the procedure

Confirm the server uses lenis0012’s LoginSecurity and read the command syntax for the installed version. The documented change command uses the current password followed by the new password.
Log in normally on the account whose password is being changed. If the current password is unknown, use the server’s verified ownership recovery process instead of guessing or sharing credentials with helpers.
Choose a unique random password within the configured length limits and character rules. Do not reuse the CloudExa panel, email or another game server’s password.
Enter /changepass with the required current and new password arguments privately in the Minecraft command interface. Never paste the full command into public chat or a support ticket.
Read the private result, then end the authenticated session through the supported logout or reconnect procedure. Check whether session continuation could otherwise bypass the password prompt.
Log in with the new password and verify the old one is no longer accepted in a controlled test. Store the new password in your password manager without sending it to staff.

Check the result

The account should authenticate with the new password after the old session is ended. A successful reconnect without a prompt may only demonstrate remembered-session behaviour. Verify an actual password authentication path before assuming the change worked.

If the result is wrong

If the command fails, check the installed length limits and exact syntax without disclosing the password. Avoid repeated failed attempts that trigger login limits. If the account becomes inaccessible, retain the error and use verified recovery; do not unregister it or remove its authentication record as a shortcut.

Give a LuckPerms permission an expiry without leaving permanent access

Make a LuckPerms event rank expire while preserving other ranks

Limit a LuckPerms command permission to one Minecraft world

Keep a LuckPerms permission local to one network backend

Move a player along a LuckPerms track without replacing unrelated groups

Fix a LuckPerms prefix priority without changing chat formatting

Remove a direct LuckPerms exception without weakening its parent rank

Apply a small LuckPerms web-editor session to the correct server

Export LuckPerms data before changing its storage configuration

Find an inheritance cycle before it complicates a rank change

Keep default-player permissions separate from staff inheritance

Diagnose LuckPerms edits that reach one backend but not another

Check a player UUID before changing LuckPerms account data

Remove a staff member from one LuckPerms track without clearing their account

Give an EssentialsX rank a fixed home limit

Restrict one EssentialsX warp to an approved player group

Test EssentialsX teleport delay and movement cancellation

Add an EssentialsX cooldown to one utility command

Resolve an EssentialsX command alias conflict without removing either plugin

Check EssentialsX AFK kick exemptions for a staff role

Limit EssentialsX nickname changes without granting formatting control

Give staff a read-only EssentialsX player-information role

Recover from an accidental EssentialsX ignore setting

Restrict EssentialsX repair commands to the intended tool policy

Review EssentialsX command-disabled entries after a plugin change

Test an EssentialsX jail location without trapping a real player

Change the EssentialsX starting balance for new players only

Set EssentialsX maximum and minimum money limits with a boundary test

Change the EssentialsX currency symbol without changing stored money

Test an EssentialsX pay dispute using two controlled accounts

Review EssentialsX worth prices before enabling item selling

Explain an EssentialsX balance leaderboard that looks out of date

Trace an unexpected EssentialsX command charge

Back up EssentialsX money before a player-data migration

Verify a LiteBans temporary ban expires at the intended time

Test whether a LiteBans mute covers a private-message command

Build a LiteBans appeal-review role without punishment access

Check a LiteBans moderator’s maximum punishment duration

Find which plugin handled a ban command on a mixed-plugin server

Verify the server scope of a LiteBans network punishment

Investigate a LiteBans database connection failure without losing history

Reverse one appealed LiteBans punishment while preserving the audit trail

Test an AdvancedBan time layout before staff use it

Check AdvancedBan warnings without accidentally escalating a real player

Give an AdvancedBan helper access to history without ban powers

Check AdvancedBan storage before changing from local files to MySQL

Lift one AdvancedBan restriction after an approved appeal

Locate AdvancedBan correctly on a proxy network

Test SuperVanish visibility with separate staff and player accounts

Check whether a vanished SuperVanish moderator can pick up items

Verify flight is safe when a SuperVanish moderator reappears

Check silent chest inspection without changing container contents

Find a SuperVanish join or player-list information leak

Remove vanish access from a staff role without leaving a hidden account

Check PremiumVanish layered visibility after changing staff ranks

Verify PremiumVanish network vanish across Velocity backends

Check vanished staff interactions before a live investigation

Recognize the PremiumVanish API jar before installing an integration

Give GrimAC alerts to one observer without granting exemptions

Remove a GrimAC exemption and verify when checks resume

Collect a GrimAC prediction log for a false-positive report