- Tested Minecraft Versions:
What can I do with PlayerControl?
This plugin allows you to have one log file per player that saves information about what did this player in a specific date.
Examples of information the plugin save are: Chat, Commands, Change World, Block Break (Useful for catching X-rayers), among others. It's a simple and lightweight plugin.
- ✓ Log file for every player
- ✓ Saves Information: Join, Leave, Chat, Commands, Change World, Block Break, Block Places, Kills, Deaths, Drops
- ✓ Check player events in Real Time
- ✓ Easy to read logs
- ✓ Information removal after a period of time
- ✓ PlaceholderAPI variables
- ✓ Works with 1.8+
- ✓ Compatibility for Spigot/CraftBukkit
Player information is stored inside the "players" folder. Each of the users will have a log file. If you want to modify the type of information being saved, you can do it on the config.yml file.
log_message_general: "[%time%] %event%"
log_message_join: "<joined the server (IP: %ip%)>"
log_message_leave: "<left the server>"
log_message_chat: "<chat: %message%>"
log_message_commands: "<command: %command%>"
log_message_worldChange: "<world change: FROM (%worldFrom%) TO (%worldTo%)"
log_message_blockBreak: "<block break: %block% (%block_x% %block_y% %block_z% %block_world%)"
log_message_blockPlace: "<block place: %block% (%block_x% %block_y% %block_z% %block_world%)"
log_message_playerKill: "<killed: %victim%>"
log_message_playerDeath: "<killed by: %killer%> (Total Deaths: %statistic_deaths%)"
log_message_drops: "<drop: x%amount% %item%>"
real_time_message: "&8&o[&c&o%player%&8&o][&e&o%time%&8&o] &7&o%event%"
After how many days will the information of the log files be removed.
If is set to 7 it means logs from 7 days old will be removed. For example if today is 8th and one of the files has information saved on the 1st, then all data saved on that day will be removed, but the other days will be intact. Keep in mind that the files could fill very quickly.
If enabled, player log will be saved when this player leaves the server (Not recommended for servers with many users)
If you want to save when player join and leave the server.
If you want to save everything the player writes in chat.
If you want to save commands the player executed.
If you want to save when player changes world.
If you want to save when player drops items.
If you want to save when player breaks/places a block. You need to define the blocks that will be allowed here. You can find a list of Materials here:
If you want to save when player dies or kills another one. (Save all types of deaths)
If this options is set to true, events that were cancelled will be saved as well. For example: A user tried to break a Diamond block in the spawn of the server, but WorldGuard stop it. Or, a user tried to execute the /home command but he doesn't have permissions.
Data will be stored ONLY if the player has the permission defined here.
You can use this variables on every log message. You can use PlaceholderAPI variables.
You can use this variables on every join log message
WORLD CHANGE VARIABLES:
You can use this variables on every world change log message
You can use this variables on every chat log message
You can use this variables on every commands log message
BLOCK BREAK/BLOCK PLACE VARIABLES:
You can use this variables on every block break log message
- %block% (Block Breaked/Placed)
- %item% (Item used to break the block)
PLAYER KILL VARIABLES:
PLAYER DEATH VARIABLES:
- /playercontrol Shows this message
- /playercontrol reload Reloads the config.yml file
- /playercontrol realtime <player> Enables/Disables Real Time messages for a Player (Basically, you will see what that player is doing)
- /playercontrol save Saves the information in their respective log files (This is done automatically when closing the server)
Just one: playercontrol.admin
IF YOU HAVE ANY IDEAS YOU ARE WELCOME TO SAY THEM I HOPE YOU LIKE THE PLUGIN.
PlayerControl | Save what Players do on your Server | [1.8-1.15] 1.7.1
Create log files automatically, which contains information of everything the players do