# Check a LiteBans moderator’s maximum punishment duration

A junior moderator’s temporary-ban permission should not accidentally allow permanent or excessive bans. Check the release-specific duration limits with a short authorized test before granting the role widely.

## Follow the procedure

1. Read the maximum-duration permission section for your installed LiteBans build and record the intended limit in ordinary language. Distinguish the right to issue a command from the limit on its duration.
2. Inspect the moderator group’s inherited permissions for unrestricted ban access, permanent-punishment rights or competing limit entries. A restrictive-looking direct node may not describe the effective result.
3. Create a non-operator test moderator and a separate disposable target. Ensure the target has no active punishment and that a senior administrator can reverse this trial.
4. Apply the documented limit permission, then try one short duration within policy. Record the accepted duration and reverse that specific trial punishment after checking its output.
5. Test a duration above the policy limit using the same disposable target. Confirm the command is refused or constrained exactly as the installed reference describes; do not assume it silently clamps the value.
6. Check permanent punishment and other punishment types separately. A temporary-ban duration limit does not automatically establish the policy for mutes, warnings or IP-based restrictions.

## Check the result

The restricted moderator can perform the approved short action but cannot exceed the chosen policy or issue an unintended permanent restriction. Save the effective permission result and command response as a staff training example without publishing the target’s identifiers.

## If the result is wrong

If the upper-limit test succeeds unexpectedly, remove the trial role’s punishment access while investigating inherited permissions. Do not experiment on a real disciplinary case. Reverse only trial records, then use the exact limit syntax from the matching release before testing again.

## References and related help

- [LiteBans maintainer reference](https://gitlab.com/ruany/LiteBans/-/wikis/Permissions)
- [LiteBans maintainer reference](https://gitlab.com/ruany/LiteBans/-/wikis/Commands)
- [Configure LiteBans moderation and preserve punishment history](https://help.cloudexa-hosting.com/books/minecraft-plugins/page/configure-litebans-moderation-and-preserve-punishment-history)
- [Connect a Minecraft plugin to a MySQL database](https://help.cloudexa-hosting.com/books/game-hosting/page/connect-a-minecraft-plugin-to-a-mysql-database)