LDLogger logs a number of events on the server, and reports them to staff in chat.
Features
LDLogger allows staff to more easily detect and handle cheating and griefing on a server. It is designed to work alongside (not conflict with) your existing anti-cheat and protection plugins.
- Simple, minimalistic. Does only a few specific things, and does them well.
- X-Ray Protection: Tracks mining of ores, and reports to staff when detected. Has a timeout feature to avoid spamming in-game chat for staff.
- Chat Filter: Anti-shouting protection. Chat messages with an excessive number of capital letters can either be automatically converted to lower-case (default), or you can kick the player. Extremely customisable!
The plugin is extremely configurable, allowing you to enable/disable specific features as required. Read more about the
Configuration Options for further information.
Update Alerts
Subscribe to
File updates on the
Subscriptions tab to find out as soon as an update for LDLogger is released!
You may also subscribe to
Comment updates if you wish. Ticket updates will not work, as they are currently hosted on GitHub instead. You can sign into your GitHub account and watch Ticket updates
from here.
Donations
If you appreciate the frequency of updates or would just like to thank me, please
consider donating ;-) Whether it be $1 or $20, it helps a lot.
Commands
| Command | Permission | Description |
|---|
| /ldlogger reload | LDLogger.admin | Reloads settings from the configuration file. |
Permissions
LDLogger
does not require a permissions plugin, but it is highly recommended if you have moderators or staff that are not OP.
| LDLogger.log | Give this to players that you'd like to track (e.g. add to base permission group). |
|---|
| LDLogger.staff | Give this to staff members that should see messages from LDLogger. By default these players override LDLogger.log and are not tracked, but you can change this behaviour in the configuration file. |
|---|
| LDLogger.admin | Give this permission to administrators, or leave as the default (op). Access to admin commands. |
|---|
Configuration Options
To read more about editing the config.yml file, please read the
Configuration Options page.
-
View User Profile
-
Send Message
Posted Jun 9, 2013@RobotoRaccoon
Thanks! :D
-
View User Profile
-
Send Message
Posted Mar 31, 201310/10, would recommend.
-
View User Profile
-
Send Message
Posted Nov 15, 2012@sception
Yes, it most certainly does. I'm running it on two servers both with dev builds of 1.4.4
Specifically, it has been tested and working on build 2463 (1.4.4), but I can't see any reason for it not to work on more recent dev builds as well.
-
View User Profile
-
Send Message
Posted Nov 15, 2012Does this work with 1.4.4 dev builds?