Find which plugin handled a ban command on a mixed-plugin server
When multiple moderation plugins register the same command, a successful-looking response can update the wrong punishment system. Identify the command owner before correcting any player record.
Follow the procedure
- Record the exact command, execution location and response that caused confusion. A command entered through Velocity may be handled before a Paper backend sees it.
- Inspect the installed plugin lists on the proxy and relevant backend. Compare command aliases in their maintainer documentation and the server’s command registration information.
- Query LiteBans directly using a read-only status or history command for the affected account. Compare the record, executor, timestamp and punishment ID with the message staff originally received.
- On a disposable account, use the documented plugin-qualified command where your platform supports it. Confirm the selected namespace actually resolves before issuing any trial punishment.
- Review custom command aliases and command-routing plugins. Adjust only the ambiguous alias or staff procedure, keeping the original punishment records unchanged during diagnosis.
- Repeat an approved trial through the same public route staff normally use. Record the correct command form in the moderation handbook, including whether it runs on the proxy or backend.
Check the result
A staff command should create a record in the intended system, and the corresponding read-only query should identify that same action. The public join result and the record must agree. A console response alone cannot establish which database was changed.
If the result is wrong
If two systems contain active restrictions, have an authorized moderator review each record independently. Do not remove both or disable a moderation plugin merely to permit a login. Restore the old alias if routing changes affect unrelated commands and retain the diagnostic timestamps.