-
-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
I was thinking it would be useful if this bot could optionally monitor and log in-game chat and player join/leave events via Discord webhooks.
Since this bot already integrates with Discord and handles stasis chambers well, adding basic monitoring features would extend its utility — especially for high-activity use cases like griefing or loot transfer operations.
Use Case
My setup involves running two bots:
- One at my main base/stash
- One at the target base I’m griefing or looting
I use stasis chambers to teleport between the two quickly. In this situation, it's crucial to know if:
- Other players log in nearby (e.g., defenders or owners)
- Important chat messages are sent (e.g., signs of being caught or tracked)
Logging this to Discord helps with:
- Real-time alerts for improved OPSEC
- Historical logs for after-action review
- Reducing the need to keep Minecraft windows visible
Requested Features
-
Chat Logging to Discord Webhook
- Log all in-game chat to a specified Discord webhook
- Include timestamp and bot name for clarity
- Optional filter for certain usernames or keywords
-
Player Join/Leave Logging
- Notify a Discord webhook when any player joins or leaves
- Possibly allow a second webhook for this (separate from chat logs)
- Optional: Only log players within render distance or within a certain range (if technically feasible)
-
Config Options
- All monitoring features should be toggleable in
config.json(e.g.,"logChat": true,"logJoins": true) - Webhook URLs should be configurable per feature
- All monitoring features should be toggleable in
Metadata
Metadata
Assignees
Labels
No labels