Lapis Inventories

• Separate Inventories

Player inventories are stored as they change game modes meaning they will only have creative items in creative, limiting the ability to cheat

• Creative Block Tracking

Creative block tracking allows us to stop survival player getting the drops from a block they break if it was placed in creative. Once more limiting the ability to cheat. As an admin, you can also check if a block was placed in creative and see who placed it. This feature is disabled by default as it requires MySQL settings. this can be disabled for admins with the LapisInventories.bypassLogging permission

• Item Drop and Container Blocking

Players also cannot drop items from their creative inventories or access cheats or any other container for them selfs or other survival players. this can be disabled for admins with the LapisInventories.canDrop and LapisInevtnories.containerAccess permission

• Simple and Fast

Because I haven't put a lot of fancy features in the plugin is lite and easy to run making it perfect for both small and massive servers

• Login Plugin Integration

You may have experienced glitches with other inventory managers when you use a login plugin that hides the player's inventory. We have an API that the login plugins can use to stop this from happening. If your login plugin doesn’t support LapisInventories ask the developer or use my LapisLogin plugin.

• Automatic Updates

You can enable automatic update downloading from the config, by default the plugin will notify you of updates in the console and can also be set to send player with the LapisInventories.canUpdate permission to be notified when they join

• Customization for Messages

All messages but command usage are editable and translatable should you wish to do so. This also allows you to theme the messages to match the theme of your server.

• /LapisInventories (help, inspect or update)

without any arguments, this command displays plugin information
Help: displays a list of all commands that you have permission to use and tells you what each does
Inspect(requires checkBlocks permissions ): Enables or disables the ability to check if a block was placed in creative and by who with a blaze rod
Update(requires canUpdate permissions ): Checks for an update, if an update is available it will be downloaded to be installed the next time the server starts

LapisInventories.canDrop:
Players with this permission will be able to drop items while in creative

LapisInventories.containerAccess:
Players with this permission will be able to access chests, hoppers and any other container while in creative.

LapisInventories.checkBlocks:
Players with this permission will be able to use the /lapisinventories inspect command and see if a block was placed in creative and by who

Login plugin API information coming soon.

If you want to work it out yourself you will need to initialize the LapisInventoriesAPI class and call hideInventory() and giveInventory(), the loginComplete() method simply calls give inventory if you wish to let LapisInventories deal with game mode changes

The plugin will automatically check for updates and notify you when one is available. you can enable update downloading, this means that the plugin will automatically download and install updates the moment they come out. You can also force the server to check for and download available updates with /lapisinventories update

Not Yet Implemented
This plugin can collect data about how many players and servers are using it and what specifications they have.
https://bstats.org/plugin/bukkit/LapisInventories

The source code can be found HERE, If you want to contribute, please use pull requests or the issues system on GitHub.

✔ ✘
500 - ✘

1,000 - ✘

1,500 - ✘

2,000 - ✘