Commands

/bb here command

The here command set allows you to find changes made within the surrounding area by users or the environment. For large areas of griefing that may involve multiple griefers, here is a crucial command on your toolbelt.

• /bb here [range] - List users who made changes in the surrounding area, and the number of changes made.
• /bb here username [range] - List changes made by that user in the general area.

SuperSticks

The tool of every fine server administrator. 'History Stick' allow you to inspect the history of a single physical block, while 'History Log' allow you to inspect "air"/lava/water blocks that cannot be interacted with by sticks.

(And yes, they're just your average stick.)

• /bb stick 1 - History Stick - Gives you a stick and imbues it with the power to see into the past. If you have something in that "hotbar" slot, BB will store it for you while you administrate.
• /bb stick 2 - History Log - Same deal, but with a log.
• /bb stick 0 - Off - Takes the stick/log and gives whatever you had in that slot previously back to you.

/bb rollback

The second most-important command in the BigBrother arsenal, this command allows you to selectively turn back the clock and restore an area (or the entire server) back to its previous state.

This command is very complex, so read this section carefully!

You can roll back damage by player, time, radius, and block ID, or a combination thereof.

Player-based rollbacks

Let's say dumbAsp and ShilF1nger have been screwing around on your server, making massive craters with TNT. There's a lot of it all over the place, and you have banned them already so they can't do further damage.

Simply issue /bb rollback dumbAsp ShilF1nger. BigBrother will ask you to confirm (because this'll probably take a long time), and then begin rolling back the changes, starting from the first blast onwards. Once it's done, it's like they were never there.

Time-based Rollbacks

Syntax: t:#d#h#m#s

For this scenario, Minecraft.net's authentication service goes buggy for a day, and your server becomes a free-for-all. You've been asleep for about 6 hours, so you come back to a massive lava-filled crater where your angry users' houses used to be. Too many users to list griefed this time, so you can't use player-based rollbacks.

You do, however, have a specific time range for when the authentication service went down: 6 hours ago.

Simply issue /bb rollback * t:6h and all your troubles melt away, although EVERYONE's changes will get reverted up to that point.

• #d for days
• #h for hours
• #m for minutes
• #s for seconds
• Combinations are allowed: 1d12h = 1 day, 12 hours.

Radius-based rollbacks

To specify a specific radius (from you) that a rollback should affect, add r:# (in blocks) to your rollback command. This also allows you to restrict the rollback by world. By adding a radius, only changes in the same world as you will be fixed; without, all worlds will be affected.

Block-based rollbacks

To specify blocks that should be rolled back (such as if someone used a bot to mine all of your diamond), add id:blockID[,blockID2] to your command.

Undo Command

Screwed up? Undo your last rollback with /bb undo.

Cleansing the database

Database growing too large and don't want to restart the server? /bb cleanse will clear the old entries out.