Download MassiveLock for $19



As simple as putting MassiveCore.jar and MassiveLock.jar in you plugins folder.

Compatible Minecraft Versions

1.11.x | 1.10.x | 1.9.x | 1.8.x | 1.7.10
CraftBukkit, Spigot and PaperSpigot are compatible.
Cauldron and Thermos are NOT compatible.


You can fully configure this plugin while your server is running! Just edit and save the configuration files. The modifications will automatically be detected and loaded into the server after a few seconds. You don’t need to run any command or restart the server for this to happen. Using a proper text editor like Notepad++ can make your life easier since syntax highlighting makes it easier to understand the text you are looking at.

Configuration is optional. The default configuration works perfectly in most cases.

The configuration file is located at /mstore/massivelock_mconf/instance.json.

NOTE: I have manually added the comments below. They will not and should not be in the actual file. Adding such comments would cause an error.

Frequently Asked Questions

Q: How do I enable the experimental shop feature?
A: This is something the server owner must to in the plugin configuration. Just set “shopsEnabled”: true and the feature will appear ingame.

Q: I am using LWC is there a way to automatically convert my database over?
A: No, there is not. In LWC a lock contains a single block. In MassiveLock a lock can contain multiple different blocks and entities. Your players will likely want a single lock for their entire chest room as opposed one for every single chest like in LWC. For this reason converting the database automatically is not the way to go. On MassiveCraft we set very low prices for the locks for a month and ran LWC and MassiveLock in parallel.

Q: I found a bug, where can I report it?
A: Please report the bug in the plugin thread on the Spigot forums and we will do our best to patch the bug asap. MassiveLock does not have an issue tracker on GitHub, but we gladly take bug reports directly on the Spigot forum thread for the plugin.


This plugin makes use of Bukkit’s standard permission node system. You can see the nodes in the plugin YAML below.

Permissions work out of the box.
You do not need an external permission manager plugin:

  1. All permissions are granted to OP players.
  2. The permission kit “massivelock.kit.rank0” is granted to all players.

However if you do use an external permission manager plugin you can grant the permission kit nodes “massivelock.kit.rank1”, “massivelock.kit.rank2” and “massivelock.kit.rank3” to your server moderators.

  • massivelock.kit.rank1 – For your lowest rank staff members.
    Grants permission to use override and list all locks.
  • massivelock.kit.rank2 – For your middle rank staff members.
    Grants permission to teleport to lock parts.
  • massivelock.kit.rank3 – For your highest rank staff members.
    Grants permission to delete all locks on a map.

Note that these kits “inherit” each other. If you give a staff member “massivelock.kit.rank3” that staff member will automatically get “massivelock.kit.rank2” and “massivelock.kit.rank1”.