CCLogger: Full Player Action Logging for Paper Servers
Running a Minecraft server comes with a constant stream of questions: who said what, which command triggered that change, when did that player last connect? For administrators juggling communities large or small, keeping a reliable record of player activity is not just helpful — it is essential. CCLogger: Full Player Action Logging for Paper Servers steps in as a dedicated auditing plugin that quietly records every meaningful interaction, storing it in a format you can query, filter, and analyze at any moment.
This tool is built for Paper servers running Minecraft 1.21 and newer, with full compatibility for Folia and a requirement of Java 21. It performs all write operations asynchronously, meaning your server tick rate stays stable even when thousands of events pour in per minute. The plugin supports five distinct storage backends, so whether you run a single survival world or a sprawling network, you can match the logging infrastructure to your exact needs.
What CCLogger Captures
The plugin focuses on three core categories of activity, giving you a complete timeline of server life without unnecessary noise.
Chat Messages
Every chat message is recorded with a precise timestamp, the world name where it occurred, and the exact coordinates of the sender. This makes it easy to trace conversations, investigate disputes, or simply review what was discussed in a specific area.
Command Execution
All commands entered by players or the console are logged automatically. For sensitive commands such as /login or /register, you can configure a blacklist to ensure passwords never appear in plain text within your logs. This small but critical feature protects both player privacy and your server's reputation.
Connection Events
Logins, logouts, and kicks are all captured with full context. You will always know who joined, when they left, and whether an administrator had to intervene. Combined with chat and command logs, this gives you a complete chronology of your server's activity.
Five Storage Backends for Every Scale
One of the strongest aspects of CCLogger: Full Player Action Logging for Paper Servers is its flexibility in where logs are stored. You are not locked into a single format; instead, you choose the backend that matches your project's size and your own technical comfort.
- File — Plain text files, ideal for small servers. No setup required, and logs remain human-readable at a glance.
- SQLite — A local database with zero configuration. You get the benefit of SQL queries for deeper analysis without running a separate service.
- MySQL — A traditional relational database, perfect for server networks that need shared access to logs across multiple machines.
- MongoDB — A document-oriented store that scales horizontally with ease. Choose this when your data volume is growing rapidly.
- Redis — An in-memory database offering lightning-fast writes. Best suited for high-traffic servers where immediate recording is a priority.
All write operations are queued asynchronously, and connection pools are managed carefully to avoid impacting server performance. Even under heavy load, CCLogger keeps your tick rate smooth and your logs accurate.
Privacy Controls and GDPR Compliance
Modern server administration requires careful handling of IP addresses. CCLogger offers four configurable modes for IP logging, allowing you to align with local regulations without sacrificing security:
- disabled — IP addresses are not stored at all.
- truncated — The last octet is zeroed out (192.168.1.42 becomes 192.168.1.0).
- hashed — A bcrypt hash with a daily rotating salt. The original address cannot be recovered, but you can still compare hashes for consistency.
- full — The complete address is stored, suitable when legislation permits.
This granular control lets you tailor the logging detail to your jurisdiction while keeping your players' data safe.
Real-Time Alerts for Suspicious Activity
CCLogger does more than passively record events; it actively watches for patterns you define. You can set a list of trigger keywords (such as "hack", "cheat", or "exploit") and specific commands (like /op or /gamemode). When any player or console input matches a trigger, operators holding the cclogger.notify permission receive an instant in-game notification. Every trigger activation is also saved to a separate file, ensuring you never miss a critical event even if you are offline at the moment.
Web Dashboard for Deep Analysis
For administrators who want more than raw log files, CCLogger includes a modern React-based web dashboard, disabled by default but easy to activate. Once enabled, it opens up a new level of log management:
- Overview statistics broken down by event type, complete with a pie chart showing distribution.
- A live activity feed that auto-updates and can be paused or filtered by category.
- Full-text search across all records, with filters for player, date, and event type.
- Player profiles featuring avatars via Crafatar, summary statistics, and complete action history.
- Export functionality to JSON or CSV for external analysis in spreadsheets or custom tools.
The dashboard is powered by a built-in REST API secured with JWT authentication and rate limiting, allowing seamless integration into external monitoring systems. To get started, simply enable the web interface in the configuration file and specify a port.
Installation and Configuration
Setting up CCLogger: Full Player Action Logging for Paper Servers is straightforward. The plugin runs on Paper 1.21+ and Folia, requiring Java 21. To install, download the JAR file, place it into your plugins/ folder, and restart the server. On first launch, the plugin generates plugins/CCLogger/config.yml with sensible defaults and immediately begins writing logs to SQLite. If you prefer a different backend, change the storage.type parameter and run /cclogger reload.
For those looking to manage their plugins efficiently, many administrators use launchers that simplify the process of downloading and updating add-ons directly from a menu, keeping the focus on server configuration rather than manual file management.
Commands and Permissions
Administration of the plugin is handled through a small set of commands, each gated by specific permissions:
/cclogger— Displays help for all subcommands./cclogger reload— Reloads the configuration (requirescclogger.reload)./cclogger count <word> [player]— Counts occurrences of a word in the logs (requirescclogger.statistics)./cclogger clear— Archives and clears the current logs (requirescclogger.admin).
Key permissions include cclogger.* for full access (granted to operators by default), cclogger.notify for receiving real-time alerts, and cclogger.exempt to exclude specific players from logging entirely. Full details are available in the plugin documentation.
Why Choose CCLogger
When you need to know exactly what happened on your server, when it happened, and who was responsible, CCLogger: Full Player Action Logging for Paper Servers delivers a comprehensive solution. The combination of five storage backends, intelligent alerting, a powerful web dashboard, and granular privacy controls makes it suitable for administrators of every skill level. Whether you run a tight-knit community or a large network, configuring this plugin once gives you ongoing transparency into your Minecraft world. For anyone looking to strengthen server oversight, the decision is clear: download CCLogger: Full Player Action Logging for Paper Servers and take control of your logs today. The installation process is simple, the configuration is flexible, and the peace of mind is immediate.