Creative Logger

See what your staff actually do — in Discord. Creative-menu grabs, commands, punishments, gamemode changes and more, each with its own channel and its own on/off switch. Set it up in-game, no restart needed.

🎁 BKHorn — Diamond Sword ×1 [Sharpness 5]
🎮 BKHorn — Survival → Creative
🔨 BKHorn — /ban Steve griefing
👁 BKHorn — Chest [world 120,64,-88]: took 12× Diamond
⌨ BKHorn (Discord) ran: /op Steve

Quick start

1. Drop the JAR in plugins/ and start the server.
2. Run /creativelog setup, click a category, paste a Discord webhook URL.
3. Done. Creative logging is on by default; everything else you switch on when you want it.

What it can log

• Creative menu — items taken, net-new only, so rearranging your inventory logs nothing
• Commands — /give, /op and /deop, punishments (/ban, /kick, /mute, /warn, …), whitelist changes, plus anything you add to the watched-command list
• Players — joins and leaves, gamemode changes, chat
• Console — mirrors the live console to Discord, with a separate audit trail of every console command whatever its origin: the Discord bridge, the real console, or RCON
• One specific player — log everything someone does, or just the parts you choose. Container visits are reported as what was taken and put back, not merely that a chest was opened
• Whatever you like — custom loggers with your own trigger, message and channel

Good to know

• Your wording — every line is a template you can rewrite, or turn into a full Discord embed
• Nothing is lost — every event is also written to a local log file, and Discord sends go through a retry queue that handles rate limits. /creativelog status when you want to check
• Webhooks are enough — a Discord bot is optional, and off unless you turn it on
• Updates keep your settings — new options are merged into your config, your values untouched
• Exempt players, per category, for anyone you don't want logged
• Proxy support, for hosts where discord.com is blocked
• Addons — other plugins can add their own placeholders, send their own lines, or rewrite and cancel yours: API docs and a buildable example

Commands

All need creativelog.admin (OP by default). To hand the menu to specific people instead of every OP, list their names in admins.yml — once it has a name in it, nobody else can even see the command.

Requirements

• Paper or Purpur, Java 21 or newer
• Two JARs, pick one: CreativeLogger-legacy-X.Y.Z.jar for Minecraft 1.21.x, or CreativeLogger-X.Y.Z.jar for 26.1+

Privacy

Logging sends player data — usernames, commands, creative-menu items, gamemode changes, and, if you enable those categories, join/leave events, chat messages and console output — to the Discord webhooks or channels you configure, and nowhere else. If you log your players, tell them.

• bStats: anonymous server and config statistics via bStats — never player data. Opt out in plugins/bStats/config.yml.
• Update check: the plugin asks the Modrinth API whether a newer version exists. Turn it off with update-check: false.
• Console control: off by default. If you enable it, Discord users you allowlist can run server console commands from a channel you choose, using a bot token you provide.