LevelStats

LevelStats

LevelStats is a lightweight statistics tracking plugin designed to collect and analyse server-wide activity across your Minecraft server.

Unlike traditional statistics plugins that focus on individual player data, LevelStats tracks collective server statistics, allowing server owners to gain a better understanding of how their community interacts with the server over time.

The plugin was originally released as DTMStats and has since been reworked into LevelStats as part of the growing Level Check ecosystem.

All data is stored locally using JSON files and automatically persists between server restarts.

Features

• Tracks server-wide statistics across all players.
• Persistent JSON-based data storage.
• Automatic statistic loading and saving.
• Hourly automatic data saves.
• Discord webhook integration.
• Optional Discord startup notifications.
• Lightweight and performance friendly.
• Simple administration commands.
• Long-term data collection support.
• Designed for economy balancing and server analytics.

Why Use LevelStats?
Many server owners balance economies based on assumptions.

LevelStats provides real data.

By tracking how players interact with your server, you can identify:

• Popular resources.
• Frequently gathered materials.
• Common player activities.
• Economy trends.
• Resource demand.
• Long-term gameplay habits.

This allows server owners to make informed decisions rather than relying on guesswork.

Data Storage
LevelStats stores all statistics inside:

plugins/LevelStats/

Each statistic is saved as an individual JSON file, making backups and data management simple.

Statistics automatically persist between:

• Server restarts.
• Plugin reloads.
• Server shutdowns.

Discord Webhook Setup
LevelStats supports optional Discord webhook notifications, allowing your server to send startup messages directly to a Discord channel.

Step 1 - Create a Discord Webhook

1. Open Discord.
2. Navigate to the channel you want LevelStats to post messages in.
3. Click Edit Channel.
4. Select Integrations.
5. Click Webhooks.
6. Click New Webhook.
7. Give the webhook a name (for example: LevelStats).
8. Click Copy Webhook URL.

Step 2 - Open the Configuration File
Navigate to:

plugins/LevelStats/config.yml

Step 3 - Configure the Webhook
Locate the Discord section:

Update it with your webhook URL:

Step 4 - Restart the Server
Restart your Minecraft server.

If configured correctly, LevelStats will send a startup notification to the configured Discord channel whenever the plugin loads successfully.

Example Startup Message
+ LevelStats Connected Successfully

Troubleshooting
No message appears in Discord

• Ensure enabled is set to true.
• Ensure startup-message is set to true.
• Verify the webhook URL is correct.
• Make sure the webhook has not been deleted from Discord.

Plugin starts but Discord message does not send

• Check your server console for webhook-related errors.
• Verify the server has internet access.
• Confirm Discord is not blocking the webhook.

Commands
Player Commands
/levelstats

Administrative Commands
/levelstats reload

Permissions

• levelstats.admin
• Administrative access to LevelStats.
• levelstats.stats
• Allows viewing statistics.
• levelstats.top
• Allows viewing top statistics.
• levelstats.save

Allows manually saving statistics.

• levelstats.reload

Allows reloading the plugin configuration.

• levelstats.discord

Allows Discord integration commands.

• levelstats.reset

Allows resetting statistics.

Privacy
LevelStats does not collect:

• Player IP addresses.
• Player locations.
• Chat messages.
• Passwords.
• Personal information.
• Any sensitive data.

The plugin is designed purely for server-wide statistical analysis.

Dependencies
Required:

• LevelCore

Part of the Level Check Ecosystem
LevelStats is part of the Level Check ecosystem of Minecraft plugins and operates through the LevelCore framework.

Future Level Check projects may integrate directly with LevelCore to provide additional functionality and shared services.

Support
If you encounter bugs, have suggestions, or require assistance, please use the discussion section or GitHub repository for support and issue reporting.