mclog2event is a lightweight little tool that watches your Minecraft server logs and turns them into events — no mods, no datapacks, no hacks needed. Just tail your log file, catch stuff like player joins, chats, or custom modpack messages, and send it all to a webhook of your choice.
Great for automations, fun Discord bots, or just keeping an eye on what’s happening on your server without touching the game itself.
- 🔁 Live log watching – Monitors your Minecraft log file in real-time.
- 🧠 Custom event matching – Define your own regex patterns to extract exactly what you need.
- 📤 Webhook output – Sends structured event data to any URL (Discord, custom apps, etc).
- ⚙️ Easy config – Everything runs off a simple
events.ymlfile.
+-----------------+ +----------------+ +----------------+
| Minecraft Log 📄 | ───▶ | Log Watcher 👀 | ───▶ | Matcher 🔍 |
+-----------------+ +----------------+ +----------------+
│
▼
Matches an Event?
│
Yes │ No
▼ ▼
+--------------------------+
| Event Payload 📦 |
| (from regex groups) |
+--------------------------+
│
▼
+------------------------------+
| Webhook Pusher 📬 |
| Sends payload to your URL |
+------------------------------+You set it up using environment variables:
| Env Var | What it does | Required |
|---|---|---|
LOG_FILE_PATH |
Path to the log file to watch | ✅ Yes |
WEBHOOK_URL |
Where to send the event (Discord, etc) | ✅ Yes |
EVENT_CONFIG_PATH |
Path to your events.yml config |
✅ Yes |
Here’s what an event config file looks like. You can define as many events as you want, using regex with named capture groups like (?P<player>\w+).
events:
- event_type: "player_join"
pattern: '(?P<player>\w+) joined the game'
description: "A player joined the server."
- event_type: "player_leave"
pattern: '(?P<player>\w+) left the game'
description: "A player left the server."
- event_type: "player_chat"
pattern: '<(?P<player>\w+)> (?P<message>.*)'
description: "A player sent a chat message."
- event_type: "player_advancement"
pattern: '(?P<player>\w+) has made the advancement \[(?P<advancement>.*)\]'
description: "A player made an advancement."- Go 1.18+
- Minecraft server log file (
latest.log) - A webhook URL
git clone https://github.com/your-user/mclog2event.git
cd mclog2event
go mod tidy
export LOG_FILE_PATH="/path/to/logs/latest.log"
export WEBHOOK_URL="https://your.webhook.url"
export EVENT_CONFIG_PATH="./events.yml"
go run main.godocker build -t mclog2event .Then run:
docker run -d \
-e LOG_FILE_PATH=/logs/latest.log \
-e WEBHOOK_URL="http://url.of/your/webhook" \
-e EVENT_CONFIG_PATH=/events.yml \
-v /path/to/logs/latest.log:/logs/latest.log \
-v $(pwd)/events.yml:/events.yml \
--name mclog2event \
mclog2eventHere’s an example docker-compose.yml to get you going:
version: '3.8'
services:
mclog2event:
build: .
container_name: mclog2event
volumes:
# Mount the directory containing your Minecraft log file to /logs
# Example: - /path/to/minecraft/logs:/logs
- ./logs:/logs
- ./events.yml:/events.yml
environment:
# The log file to watch inside the container.
# This should be the name of your minecraft log file.
- LOG_FILE_PATH=/logs/latest.log
- WEBHOOK_URL=http://url.of/your/webhook # Replace with your webhook receiver
- EVENT_CONFIG_PATH=/events.ymlRun it with:
docker-compose up --build -dJust edit events.yml and add a new entry. The app will load it on startup. Use named regex capture groups to grab values and send them in the event payload.
Here’s a bunch of stuff I’d like to add, improve, or play with in the future:
-
Prometheus metrics and OpenTelemetry support
Expose internal metrics (e.g. matched events, errors, webhook push stats) to Prometheus.
Primary goal: gain hands-on experience with observability tools. -
Grafana dashboard
Provide a ready-to-use Grafana dashboard to visualize logs and event activity. -
Example event configuration
Include a defaultevents.ymlwith common Minecraft log patterns, ready to use for most vanilla servers. -
n8n workflow example
Provide an example n8n automation that reacts to incoming events. -
Documentation for regex capture patterns
Write a short guide explaining how named capture groups work in regex, using Minecraft log examples. -
CI/CD pipeline
Set up GitHub Actions to build, lint, test, and maybe even release. -
Unit tests
Add some proper tests for the matcher logic and other core parts. Gotta break stuff with confidence. -
Docker image publishing
Automatically publish a Docker image to Docker Hub or GHCR on release so folks can justdocker pulland go. -
Add shoutrrr support (maybe)
Integrate shoutrrr to send events to services like Discord, Telegram, Slack, etc.
If you’ve got ideas, feel free to open an issue or drop a PR.
Found a bug? Got a cool idea? Fork the repo and open a pull request — happy to have help from fellow Minecraft nerds.
MIT. Do what you want, just don’t sue anyone.