Latest version has been compiled and tested with Spigot 1.19!

Latest version has been compiled and tested with Spigot 1.19 and Java 17

This latest version has been compiled and tested against Minecraft 1.17.1.

This is an issue I've been having ever since I first created this plugin. Hopefully this settles it...

Hey everyone.

Sorry for the lengthy, albeit expected, delay. I have fixed the issue where the config would reset back to defaults after restarting. I've compiled this release with the latest 1.16.1 snapshot.

Fixed a bug where changes to the config.yml would not save.

Compiled with the latest 1.14.4 Spigot release.

I've compiled with the latest 1.14 developmental build that has been posted, everything looks good. I'll post another update once the final 1.14 files are released.

I have updated and tested this version with 1.3.1.

Hey all,

So for this update there's nothing changed in terms of functionality or usability, but I have made a tweak to the bypass permission. In the v2.0 release, the invlock.bypass permission was by default given to an operator. However, now the permission is not given to any player by default, meaning the inventory lock is active for all players that lack the bypass node. I feel that this only makes sense for this plugin, and that this should've been released previously.

Feel free to leave feedback and suggestions.

Hey all, long time no see.

After an extended hiatus, I return to Spigot, having completed a rewrite of my outdated (and previously abandoned) plugin InventoryLock. Back when I initially released the plugin, it was poorly written, and had in-game commands. Looking back on this, I realize how pointless it was to have in-game commands, and have simplified the plugin, making it even more lightweight and easy to use.

So that's great and all, but what's this update all about?
- No more in-game commands
- 1 permission node! invlock.bypass (By default, an op has the bypass permission)
- Simple configuration file
- Players are unable to drop items, edit their inventory, or swap into the offhand

The configuration file simply contains a list of worlds that the plugin should be enabled in. By default, the plugin is enabled in the world "world".

I look forward to any and all feedback!

Config Additions
There is a new entry in the config file. This entry will allow you to enable the plugin only in certain worlds. Simply enter the name of the world you'd like to have the plugin enabled in.

Bypass Permissions
Two new permission nodes have implemented. These permission nodes allow the bypass of the locks.
NOTE: If you have given a player the star permissions to a certain lock(e.g. invlock.move.*) they will automatically have bypass permissions.
The nodes for the bypass permissions are as follows

• invlock.move.bypass
• invlock.drop.bypass

Config.yml
I have implemented a config.yml that automatically generates upon the first run of the plugin. The values within the config.yml are automatically set to true, but can be changed. These values change the startup status of the locks.

Code (Text):

#InventoryLock Configuration File
#Coded by DarkSoldier on Spigot Forums

#Locks will be enabled/disabled on startup based on these two options
#ON - true
#OFF - true
drop_lock_enabled_startup: true
move_lock_enabled_startup: true
#True means that when the server starts up, the locks will automatically be turned on
#On the flip side, false indicates that upon server startup, the locks will not be on

If a player is an operator, they have access to all commands.
If a player is not OP, they must be given the permission invlock.allow to allow them to even access the help page.

The other permissions can be given using asterisks
REMEMBER TO GIVE invlock.allow

• invlock.drop.*
  • invlock.drop.enable
  • invlock.drop.disable
  • invlock.drop.status
• invlock.move.*
  • invlock.move.enable
  • invlock.move.disable
  • invlock.move.status

Instead of giving the independent permissions, you can simply give the three permissions, invlock.allow, invlock.drop.*, and invlock.move.* These three permissions will give the group/player access to all of the commands.