Repository navigation
Diagnostics
This page explains the diagnostic tools available in LederProtections.
Diagnostics help server owners check plugin status, protection data, compatibility and update information.
| Command | Purpose |
|---|---|
/lep check |
Runs protection diagnostics. |
/lep version |
Shows the plugin core version and update-checker status. |
/lep info |
Shows runtime plugin information. |
/lep status |
Shows plugin/server status information. |
Some commands require permissions.
The command:
/lep check
runs a protection diagnostic check.
It is focused on protection data, not update information.
Example output:
Check complete. Protections: 1 | Problems: 0
No problems detected.
This command can help detect issues with protection data, missing regions or invalid protection states.
Use /lep check when you want to verify:
- protection count;
- possible protection data issues;
- missing or invalid protection regions;
- stone-related issues;
- world or location issues;
- general protection consistency.
/lep check does not focus on update status.
For version and update-checker information, use:
/lep version
The command:
/lep version
shows:
- installed LederProtections core version;
- update-checker status.
Example:
Core: 1.0.0
Update checker: up to date
This is useful when reporting issues or verifying that the correct jar is installed.
The command:
/lep info
shows runtime plugin information.
It may include:
- plugin version;
- server software;
- Minecraft version;
- Bukkit/Paper API version;
- Java version;
- online-mode status;
- WorldGuard status;
- WorldEdit status;
- Vault/economy status;
- PlaceholderAPI status;
- loaded protection count;
- loaded stone types.
This command is useful for support reports.
The command:
/lep status
shows a general plugin/server status overview.
It can be used by administrators to quickly check if LederProtections is running correctly.
When reporting an issue, include:
| Information | How to get it |
|---|---|
| LederProtections version | /lep version |
| Runtime info | /lep info |
| Protection diagnostics | /lep check |
| Server software | Console startup or /version
|
| Minecraft version | Console startup or /version
|
| WorldGuard version | Plugin list or console |
| WorldEdit version | Plugin list or console |
| Vault version, if used | Plugin list or console |
| PlaceholderAPI version, if used | Plugin list or console |
| Console errors | Server logs |
Common permissions for diagnostics:
| Permission | Description |
|---|---|
lederprotections.info |
Allows using runtime information commands. |
lederprotections.admin |
Allows administrative plugin access. |
lederprotections.update |
Allows receiving update notifications. |
Recommended staff permissions:
lederprotections.info
lederprotections.update
Administrators may also need:
lederprotections.admin
During startup, LederProtections prints useful information to the console.
Examples of information shown:
- detected platform;
- Minecraft version;
- WorldGuard/WorldEdit connection;
- loaded language;
- loaded stone types;
- rule engine status;
- protection index status;
- PlaceholderAPI registration;
- update-checker result.
LederProtections may print a platform summary similar to:
Platform detected: Paper | Minecraft 1.21.x | Online-mode yes
This helps confirm that the plugin detected the server environment correctly.
LederProtections can report whether dependencies are connected.
| Dependency | Expected result |
|---|---|
| WorldGuard | Connected |
| WorldEdit | Connected |
| Vault | Connected if installed and used |
| PlaceholderAPI | Connected if installed |
If WorldGuard or WorldEdit is missing, LederProtections cannot work correctly.
LederProtections uses a protection index to make protection lookups efficient.
Startup may show information such as:
Protection index built. Indexed protections: 0
This means the plugin built its internal lookup data.
The update checker may show messages such as:
| Message type | Meaning |
|---|---|
| Up to date | Installed version matches latest Modrinth version. |
| New version available | A newer version exists on Modrinth. |
| Installed version newer | Local version is newer than published version. |
| Check failed | The server could not check Modrinth. |
Use /lep version for current version status.
Use diagnostic commands when:
- installing the plugin for the first time;
- updating LederProtections;
- changing
config.yml; - changing
stones.yml; - changing permissions;
- investigating missing protections;
- investigating WorldGuard issues;
- reporting a bug;
- testing a new server setup.
After installation or update:
- Start the server.
- Check the console for errors.
- Run
/lep version. - Run
/lep info. - Run
/lep check. - Open
/p. - Test placing a protection stone.
- Restart the server.
- Run
/lep checkagain.
Check:
- whether WorldGuard regions exist;
- whether the protection stone still exists;
- whether the world exists;
- whether the protection data is valid;
- whether the server was recently changed or restored from backup.
Check that:
- the old jar was removed;
- the new jar is in the
pluginsfolder; - the server was fully restarted;
- there are not multiple LederProtections jars in the plugins folder.
Check that:
- WorldGuard is installed;
- WorldEdit is installed;
- both dependencies are compatible with your Minecraft version;
- WorldGuard loaded successfully before LederProtections.
Check that:
- PlaceholderAPI is installed;
- the server was restarted;
- LederProtections loaded successfully;
- no startup errors occurred.
Recommended practices:
- Run
/lep checkafter major configuration changes. - Run
/lep versionafter updating. - Keep startup logs when reporting issues.
- Do not ignore console warnings.
- Test on a staging server before applying major changes to production.
- Keep backups before changing protection data.