ModLogs Plugin
A server-side plugin that works with ModLog Mod to verify player mods, resource packs, and client versions, helping administrators monitor and prevent cheating.
ModLogs Plugin
Server-side verification and monitoring plugin for Minecraft servers.
📌 Summary
| Item | Description |
|---|---|
| Type | Server-side plugin |
| Purpose | Client verification, moderation & logging |
| Works With | ModLog Mod (client-side) |
| Edition | Java Edition (Paper / Spigot compatible) |
| Bedrock | Ignored automatically (Geyser/Floodgate) |
| Accounts | Offline & Online |
🧩 Overview
ModLog Plugin is a server-side moderation and verification plugin that receives client environment data from ModLog Mod and processes it for logging, monitoring, and anti-cheat purposes.
The plugin allows server administrators to:
- Inspect player mods and resource packs
- Monitor client-side changes in real time
- Enforce server join rules
- Receive notifications in-game or via Discord webhooks
The plugin does not modify gameplay and runs independently in the background.
🔗 Required Client Mod
This plugin requires players to use ModLog Mod.
| Resource | Link |
|---|---|
| ModLog Mod | /mod/modlog-mod |
Servers may deny access to Java players who attempt to join without the required mod.
📊 Received Client Data
The plugin processes the following information sent by the client mod:
| Data | Description |
|---|---|
| Username | Player name |
| Mods | List of loaded client mods |
| Resource Packs | Enabled & disabled resource packs |
| Version | Minecraft client version |
No personal or system-level data is collected.
🔐 Server Enforcement & Behavior
| Feature | Behavior |
|---|---|
| Join verification | Player data checked on join |
| Missing mod | Player may be blocked |
| Change tracking | Resource pack changes detected |
| Notifications | In-game & Discord supported |
This system helps detect:
- X-Ray via suspicious resource packs
- Unauthorized client mods
- Modified client environments
- Version mismatches
⚙️ Configuration
The plugin is fully configurable using a single YAML configuration file.
📄 Full Configuration
discord:
# master switch for all Discord webhook notifications
enabled: false
# bot token used to create/validate webhooks in target channels
bot-token: ""
# fallback channel for any event that does not define its own channel
# recommended to keep this empty when you configure channelid per event
channel-id: ""
notifications:
join:
# in-game admin notification switch
enabled: true
# supported: all, mods, resourcepack_all, resourcepack_enabled, resourcepack_disabled, version
# you can use either a string ("all") or a yaml list
types: "all"
# Discord controls
discord-enabled: true
channelid: ""
resourcepack-change:
# in-game admin notification switch
enabled: true
# supported: all, show-enabled, show-disabled
# you can use either a string ("all") or a yaml list
types: "all"
# Discord controls
discord-enabled: true
channelid: ""
freecam:
# in-game admin notification switch
enabled: true
# when enabled, admins with modlogs.notify can see a live floating marker for active freecam users
admin-view: true
# Discord controls
discord-enabled: true
# supported: all, start, stop
discord-types: "all"
channelid: ""
viewer:
# if true, /modlog show only works for online targets
require-online-player: false
# show how old the last snapshot is in /modlog show output
show-last-update: true
