Minecraft LogBlock Plugin Guide – Rollback Your Server

Minecraft LogBlock Plugin – Introduction

On your Minecraft server, you’ll wander through a world where everything revolves around blocks. As you play with friends and others, everyone on your server will create new and unique buildings as they shape your server world. If you also have other players on your server and especially if you have a community server, it’s important to keep track of your players. This includes seeing who may be griefing, stealing, or causing issues on the server, as these can cause immense frustration among players. To help with this, we highly recommend the Minecraft LogBlock plugin to safeguard and monitor your server!

LogBlock is a tool for your Minecraft server that helps you keep track of every block placed. From finding out who has accessed a specific chest to seeing who exploded TNT in your spawn, and even checking into mob griefing. The best part, LogBlock will only take a few minutes of your time to set up and will offer years of powerful protection to your server. In this guide, you will learn how to install the tool on your Minecraft Bukkit/Spigot server and how to set it up correctly!

How to Install the Minecraft LogBlock Plugin on Your Server

To begin, you will need to download and install the Minecraft LogBlock plugin on your Minecraft server. You can find all the different versions of the plugin here. Please verify you choose the correct version. Afterward, you can check out our detailed Minecraft plugin guide on installing plugins to your server to ensure everything is set up correctly!

Configuration of the Minecraft LogBlock Plugin

To set up the plugin, we need to edit the files config.yml, world.yml, and world_nether.yml. You can find these files in the plugins folder minecraftbukkit – plugins – LogBlock.

Config.yml

loggedWorlds:

• – world
• – nether

You can find this parameter at the end of the file. These are the names of the worlds you wish to have logged. Ensure you use the exact name as specified in server.properties, including the path.

 

version: ‘1.40’

 

This information is not vital to you (but don’t delete it!). It is simply the version the config was created under and won’t always update when there is a LogBlock update. Don’t worry if it’s not the same value as the version of the Minecraft LogBlock version you’re running.

MySQL

To find your MySQL credentials, head to the dashboard in your webinterface and scroll down to the bottom.

 

host: localhost

Mentioned as “Hostname” in your web interface.

 

port: 3306

Mentioned as “Port” in your web interface.

 

user: username

This is your Username, e.g. ni73647382_2_DB

 

password: pass

Your password is mentioned right underneath your username.

 

database: minecraft

The name of your database could be the same as your username.

Logging

logCreeperExplosionsAsPlayerWhoTriggeredThese: false

Logs creeper explosions under the name of the player who triggered the explosion. If this is set to true, you must use /lb […] player <playername> instead of /lb […] player Creeper.

logKillsLevel: PLAYERS

There are three log levels:

• PLAYERS – Only players who killed another player
• MONSTERS – Players and monsters
• ANIMALS – Logs every kill

 

logEnvironmentalKills

Set this to true to log kills that are not directly caused by other entities. Examples include burning to death, falling, and suffocation.

 

hiddenPlayers: []

The players listed there won’t get logged. Not recommended to use!

 

hiddenBlocks: – 0

These blocks are ignored for logging. Not recommended, except if you don’t use rollbacks. Air (0) must be there.

logPlayerInfo: false

Set to true to log player online time, time of first and last login, and IP address of the last login.

Rollback

replaceAnyway:

• 8 //Water
• 9 //Water
• 10 //Lava
• 11 //Lava
• 51 //Fire

By default, these are blocks that are considered to spread naturally. These are blocks that will be replaced at rollback.

 

dontRollback:

• 10 //Lava
• 11 //Lava
• 46 //TNT
• 51 //Fire

By default, these are blocks that are considered harmful and shouldn’t be spawned again that are set in the Minecraft LogBlock plugin. Upon rollback, if they were destroyed, they won’t be placed back in the world.

 

Lookup

defaultDist: 20

defaultTime: 30 minutes

Default values for parameters area and time.

 

toolblockID: 7 //Bedrock

toolID: 270 //Wood pickaxe

Displays the ID’s for items to be given to the player when tools are summoned. Ensure toolblockID is the ID of a block and toolID is the ID of an item.

 

toolQuery: area 0 all sum none limit 15 desc

toolBlockQuery: area 0 all sum none limit 15 desc

Queries are performed upon the use of the tool.

How to Use the Minecraft LockBlock Plugin

Permission Nodes

Commands

Parameters

Location

area <radius>

To only search for near block changes. The area has a square shape. If no radius is specified, the default radius will be used (lookup.defaultDist). A radius of 0 stands for a single block and is used for tool queries.

 

sel | selection

To search only inside the current WorldEdit selection. Works only for cuboid selections.

loc [x]:[y]:[z] | location [x]:[y]:[z] (v1.51+)

Specify a single block. You can use colons or spaces to separate, like loc 45 -12 64 or loc -123:265:70 You can combine loc and area to get the area around a set of coordinates, as long as loc is specified first

world [worldname]

Selects the world. Required for console commands. Allows to look up in a specific world. The default is the current world.

Type

What to search for. Can not be combined. The default for lookups is both and the default for rollbacks is all.
all

Looks up all blocks (including actions) and chestaccess and mechanism interactions

 

created, destroyed, both

Usable to search only for block creations/breaks or both Without any type given, it will search for created and destroyed blocks.

 

kills

Looks up only kills assuming it is enabled in the config.

 

killer [name1] {<name2>}, victim [name1] {<name2>}

Used to search the Minecraft LogBlock plugin logs only for kills where the given player was the killer/victim. Use !name to search for all players except the given.

 

weapon [material]

Search for kills by weapon, seems to be broken.

 

chestaccess

Used to see the logs of who has accessed the chest.

 

Chat

Search chat only. You can use the params player, since, before, and search.

 

search | match

Search the chat history for some words.

Example: /lb chat player USER search home or /lb chat player USER search tree home Will search for all messages by player USER containing the words tree OR home.

/lb chat player USER search +tree +home

Same as previous, but both words have to appear.

/lb chat player USER search tree -home Find all with the tree but without a home.

Time

since [timespec] | time [timespec]

To search only for block changes newer than the specified time. Accepted syntaxes are: LB time format: 4 minutes, 5 hours, 6 days BB time format: 4m5h6d, 5d40m, 7m DateTime: 12:00:00, 22.05.2011, 22.05.2011 12:00:00 (for a date without a time 0 am is assumed, for a time without date the current date)

 

before [timespec]

To search only for block changes older than the specified time. Same format as the since parameter. You can use since and before together to define a period. Filter

player [name1] {<name2>}

To search for one or more players, also environment players like Fire or LavaFlow Use !name to search for all players except name If you specify a partial name, LogBlock will try to guess who you mean from the players currently on the server. Use “name” to override this (e.g. to search for “Fire” while the player “Firefly” is online)

 

block [material1] {<material2>} | type [material1] {<material2>}

Used to search for a specific type of block. Use !material1 to search for all blocks except material1.

Results

limit [count]

Sets how many rows are displayed when getting Minecraft LogBlock results. The default is 15.

 

sum [n<one>|b<locks>|p<layers>]

To sum up the result. none is the default. none means all single block changes are listed, block means to group by block types, and players to group by players.

 

asc, desc

Set the order of the displayed log as ascending or descending.

coords

Displays also block coordinates. Only affects look-up and writelogfile commands. This parameter is required to use the /lb tp command.

Other

silent

No questions and displayed messages are reduced to a minimum.

 

last

Stands for all parameters of the last command. It’s possible to extend it and to overwrite, e.g: /lb player USERNAME will display block changes from that user.

Be on Guard with the Minecraft LogBlock Plugin

Now that you know how to use the Minecraft LogBlock plugin, you’ll be able to protect your server with the ultimate plugin shield. Whether you need to see who has been griefing your player’s builds or who set your friend’s animal farm on fire. Once you have that information, you can take action against the player and roll back their destruction. That way, you can focus on enjoying your server with friends and fellow Minecraft players. Defend your server today by installing LogBlock on your own Minecraft server!

Get your own Minecraft Server now!