MyBlock

Protecting what's yours

MyBlock is a state-of-the-art individual block protection system. Built off the powerful AsyncBlockEvents and WatchFox systems, MyBlock can protect millions of individuals blocks with custom permissions for each.

Links: Home | Downloads | Changelog | How to use | Configuration | Permission nodes | How it works | Report a bug

MyBlock requires WatchFox and AsyncBlockEvents to function.

MyBlock was initially developed as part of a plugin request for a simple, powerful, lag-free block protection system. Building off the WatchFox database, MyBlock eventually split to form AsyncBlockEvents, a library for managing certain block events asynchronously, and MyBlock as it is now.

Feature-wise, MyBlock supports per-block permission levels including notions for friends, guests, and allowing public access (for things like furnaces and chests).

At the highest level, MyBlock allows users to specify whether the blocks they place / break be marked as private, public-access, or no-protection. Private works as expected, allowing only the user (+others as you'll see) to manipulate the block or immediately adjacent to it. Public-access allows blocks to be interacted with by anyone, but not broken. Doors, buttons, chests, even cake can be selectively specified. Lastly, no-protection works just as you'd expect, giving everyone the ability to change your blocks. By default, blocks default to private.

MyBlock also allows defining 'guests'. Upon adding a 'guest', each following block place / break gets tagged with the guest, giving him full rights to the block and adjacent. Simply, this allows for any scenario where a user wants only certain blocks to be accessible to a select few. A group could work collaboratively on a building, adding each other as guests, while still ensuring their own home remains safe by clearing the guest list when they return home.

And of course, MyBlock allows users to define 'friends'. Friends are retroactively given permission to all of a users blocks. Welcoming a friend to a server, and the comfort of your home, is as simple as adding him to your friend list. All blocks you have and will place will authenticate.

For mods and admins, there is naturally the ability to ignore any pertinent permission setting. There is also the ability to change protection flags for someone else. Help users by configuring their friends list. Use command blocks or an area plugin to force users into building with the no-protection flag. All of MyBlock's commands support overriding (even the overriding command...)

Lastly, MyBlock includes a clean-up tool. The mark command will take a WorldEdit region and mark all protected blocks to your specification. Something as simple as an abandoned house can be marked as 'no-protection', relinquishing it back to the players at large. Using the override command, buildings can be marked as the one-less-friend owner.

Links: Home | Downloads | Changelog | How to use | Configuration | Permission nodes | How it works | Report a bug