Gaming Discussions
LogBlock
Submitted by MateoY, 15-06-2018, 05:00 PM, Thread ID: 92309
Thread Closed
15-06-2018, 05:00 PM
#1 LogBlock helps us with the fight against grieferami, or players who destroy other players the effects of hard work. The plugin records the actions of the players, what blocks they destroyed, what they put, what they put into the crates, what they took out. It also records when and where it happened. Such registered events can be undone, so if a player breaks something, you can fix it
Configuration of the plugin
Have some important things before you edit the configuration files. These files are in YML format, you should keep the appropriate number of spaces in the cuts in each verse. If you set the name of the user to the database, you can see there two at the beginning of the line, so let it remain. The same applies to everything that is in YML files
LogBlock hookup to the MySQL database
By opening the configuration file config.yml in the folder with the plugin, look for the "mysql" line. Under it, you enter things like the MySQL database user name, the user's password, the database port, the database address and the name of the database.
port: 3306 (MySQL database port)
password: BASE USER PASSWORD
user: BASE USER NAME
database: NAME OF THE DATABASE
host: mysql server address
Tools for checking logs
By default, the log search items are BedRock and wooden pickaxe. You can change them to other items in the LogBlock configura
leftClickBehavior: TOOL (Action that the object will do after clicking the left mouse button)
toolblock:
item: 7 (7 to ID BedRock)
params: area 0 all sum none limit 15 desc silent (command to call logs from the database)
rightClickBehavior: BLOCK (The action the object will do when right-clicking)
aliases: (Aliases to the command referring to this object as eg / lb tb)
defaultEnabled: true (Should the item be available by default)
mode: LOOKUP (Object mode, lookup is a standard LogBlock)
canDrop: false (Can player throw this item)
Definition of maps on which LogBlock is to register changes
It's good to set up LogBlock to save changes only on maps where this is important, the more maps we give, the higher the load for the server will be. These settings are made as usual in the plugin configuration file.
tion file. U
What to save LogBlock
For each map, we can define what should be saved in the logs. In the directory with the plugin we have files, their names match our map. So in my case, in the file spawn1.yml we do what is to be recorded in the logs on this map. The word false means that the item will not be saved, true means it will be saved.
logging: TNTEXPLOSION: false (destroyed by TNT explosion)
LEAVESDECAY: false (disappearance of leaves from the tree)
MISCEXPLOSION: false (Logs other types of explosions)
SNOWFORM: false (Logs snow / ice formation)
NATURALSTRUCTUREGROW: false (naturally occurring structures such as trees)
KILL: false (Logs players death - Depends on the defined in the configuration file)
FIRE: true (Logs fire)
CHAT: false (Login chat)
WATERFLOW: true (Logs blocks destroyed by water)
BONEMEALSTRUCTUREGROW: false (structures created using Bone Meal)
BLOCKPLACE: true (Logs blocks by players)
ENDERDRAGON: true (Logs blocks destroyed by EnderDragon)
DIODEINTERACT: false (Logs interactions in Redstone Repeater)
SNOWFADE: false (Logs for ice / snow fading by light sources)
CHESTACCESS: true (Logs changes to the chest)
ENDERMEN: false (Logs blocks taken and placed by Enderman)
SIGNTEXT: true (Logs body text) LAVAFLOW: true (Logs blocks destroyed by lava)
CAKEEAT: false (Logs players who eat cake)
BLOCKBREAK: true (Logs blocks destroyed by the player)
SWITCHINTERACT: true (Logs players pressing a button, a pressure plate or moving levers)
NOTEBLOCKINTERACT: false (Logs players using Note Block)
GHASTFIREBALLEXPLOSION: true (Logs blocks destroyed by Ghast)
CREEPEREXPLOSION: true (Logs blocks destroyed by Creeper)
DOORINTERACT: true (Logs who opened and closed the door) table: lb-world (Name of the table in the database in which all data will be saved)
Remember that, for example, you do not enable saving logs of chests, you nder the "tools" line in the standard there are previously defined two tools by default
Configuration of the plugin
Have some important things before you edit the configuration files. These files are in YML format, you should keep the appropriate number of spaces in the cuts in each verse. If you set the name of the user to the database, you can see there two at the beginning of the line, so let it remain. The same applies to everything that is in YML files
LogBlock hookup to the MySQL database
By opening the configuration file config.yml in the folder with the plugin, look for the "mysql" line. Under it, you enter things like the MySQL database user name, the user's password, the database port, the database address and the name of the database.
port: 3306 (MySQL database port)
password: BASE USER PASSWORD
user: BASE USER NAME
database: NAME OF THE DATABASE
host: mysql server address
Tools for checking logs
By default, the log search items are BedRock and wooden pickaxe. You can change them to other items in the LogBlock configura
leftClickBehavior: TOOL (Action that the object will do after clicking the left mouse button)
toolblock:
item: 7 (7 to ID BedRock)
params: area 0 all sum none limit 15 desc silent (command to call logs from the database)
rightClickBehavior: BLOCK (The action the object will do when right-clicking)
aliases: (Aliases to the command referring to this object as eg / lb tb)
defaultEnabled: true (Should the item be available by default)
mode: LOOKUP (Object mode, lookup is a standard LogBlock)
canDrop: false (Can player throw this item)
Definition of maps on which LogBlock is to register changes
It's good to set up LogBlock to save changes only on maps where this is important, the more maps we give, the higher the load for the server will be. These settings are made as usual in the plugin configuration file.
tion file. U
What to save LogBlock
For each map, we can define what should be saved in the logs. In the directory with the plugin we have files, their names match our map. So in my case, in the file spawn1.yml we do what is to be recorded in the logs on this map. The word false means that the item will not be saved, true means it will be saved.
logging: TNTEXPLOSION: false (destroyed by TNT explosion)
LEAVESDECAY: false (disappearance of leaves from the tree)
MISCEXPLOSION: false (Logs other types of explosions)
SNOWFORM: false (Logs snow / ice formation)
NATURALSTRUCTUREGROW: false (naturally occurring structures such as trees)
KILL: false (Logs players death - Depends on the defined in the configuration file)
FIRE: true (Logs fire)
CHAT: false (Login chat)
WATERFLOW: true (Logs blocks destroyed by water)
BONEMEALSTRUCTUREGROW: false (structures created using Bone Meal)
BLOCKPLACE: true (Logs blocks by players)
ENDERDRAGON: true (Logs blocks destroyed by EnderDragon)
DIODEINTERACT: false (Logs interactions in Redstone Repeater)
SNOWFADE: false (Logs for ice / snow fading by light sources)
CHESTACCESS: true (Logs changes to the chest)
ENDERMEN: false (Logs blocks taken and placed by Enderman)
SIGNTEXT: true (Logs body text) LAVAFLOW: true (Logs blocks destroyed by lava)
CAKEEAT: false (Logs players who eat cake)
BLOCKBREAK: true (Logs blocks destroyed by the player)
SWITCHINTERACT: true (Logs players pressing a button, a pressure plate or moving levers)
NOTEBLOCKINTERACT: false (Logs players using Note Block)
GHASTFIREBALLEXPLOSION: true (Logs blocks destroyed by Ghast)
CREEPEREXPLOSION: true (Logs blocks destroyed by Creeper)
DOORINTERACT: true (Logs who opened and closed the door) table: lb-world (Name of the table in the database in which all data will be saved)
Remember that, for example, you do not enable saving logs of chests, you nder the "tools" line in the standard there are previously defined two tools by default
Users browsing this thread: 1 Guest(s)