Latch v0.1.0 🔓

Plugins Plugin Releases
21

Is it possible to have the mod register chest being locked by players, but only have it work within a certain region? So for primary example, if player has chest locked in region a, and chest moves (without being destroyed) to region b, have it so it still opens in region a but remains closed to all but the player in region b (without reapplying the locks).

22

We have released an update to Latch, unfortunately it will not be compatible with past versions’ databases, but we do not think that will occur again. According to our data no one has been using this recently, so I hope this does not affect any of you too harshly. Soon we hope to increase admin functionality such as purging all of a player’s locks, bypassing locks, and bypassing limits. I also hope to create some more simplified commands for people who dislike the flag system. If you have any requests please notify us here or with a Github issue.

Find the new releases for API 5.1.0 and 6.0.0 here.

:lock: Latch v0.1.0

Our first major update in a while. With this release we aimed to increase stability, update to current standards, clean up code, stylize our messages, and add some features of convenience.

Features:

  • Sponge updated to API versions 5.1.0 and 6.0.0
  • Added a donation chest ("/latch donation"), where you have full access but others can only input
  • Added a protection from redstone interactions. Can be controlled from config then also per lock if enabled.
  • Formats many of the plugin’s messages. If you have any suggestions in this department please inform us.
  • Added shulker boxes to default protectable blocks for API 6.0.0
  • Adds a simplified add command ("/latch add [user]")
  • Adds a simplified remove command ("/latch remove [user]")
  • Switched to bStats instead of mcstats. Find our page here.
  • Updates the default lock limits.

Bugfixes:

  • Fixes our custom event failing to cast to AbstractEvent (Thanks @dualspiral)
  • Fixes lock limit check being called when it shouldn’t be
  • Fixes certain error messages not showing up
  • Stops lock interactions from processing if player is not the root cause
  • Other miscellaneous changes

Code changes:

  • Updated SpongeGradle to 0.8.1
  • Updated Gradle wrapper to Gradle 3.2
  • Set Gradle to always compile with UTF-8
  • Removes collections of Users, instead use UUIDs
  • Switches domain for packages
  • Began to utilize more Java 8 features
  • General cleanup
23

possible to protect the painting, the frame (and its contents), rack with armor ?

24

@Burlog Unfortunately not at the moment as these are not truly blocks but rather entities, sorry. We plan to support these and other entities in a future release though, so keep checking back.

If you have any other features or changes you would like to see please say so, as we love any suggestions we can get.

@Prototype_Undergroun Sorry about the late response. If you are still interested in this feature, would you mind elaborating? I am not sure I really understand your question and it seems it may be out of the scope of this plugin, but it could still be a possibility.

25

While playing around with this plugin, I’ve found a few bugs/things to mention:

  • Pressure plates and buttons get stuck in the “on” position when they’re placed next to a locked object (with “protect_from_redstone”=false) or are locked (by adding them to the “lockable_blocks” list)
  • Furnaces get stuck to visual state they were locked in (lit=never turns off, off=never lights)
  • Donation lock owners can duplicate items if both them and someone without access to remove items are accessing a chest at the same time
  • No unlock notification when breaking a locked block
  • No admin bypass feature
  • The “here for” in “Click here for Latch help” is missing the “/” for the shortcut (Just says “latch help” in chat)
  • Clunky commands (/lock should alias for /latch private, /unlock should alias for /latch delete)

Sponge version: spongeforge-1.10.2-2171-5.1.0-BETA-2010
Latch version: Latch-0.2.0-5.1.0

1 Like
26

Thanks for testing Latch, we really appreciate it. We want to catch things like this before a 1.0.0 release, especially issues like the donation chest problem, so keep it up. We’ll do our best to fix these soon.

If you are using this on a production server the best you can do right now is set the limit for donation chests to 0. With the 0.3.0 release we hope to have extensive purge commands along with admin bypass functionality.

Again thanks for the reports,

Meronat

27

I’m hoping to get a patch release out tonight which fixes the most pressing issues here, then a minor release this weekend which addresses the rest.

Edit: We found some more issues and it may take a little longer than we though. Sorry about the wait.

For now I recommend everyone turn the donation chest limit to 0 as there are a few problems with them beyond just the duplication issue.

28

Hello my friends, sorry that this took a long time, but Latch has been finally updated to version 0.3.0 with many fixes to the issues @Dead_Island_Dude reported. Thank you for those reports and suggestions. You can find the download and more information here on our Ore page. We hope you enjoy the release.

Please continue discussion of this plugin on the new forum page which Ore automatically handles for us.

I would appreciate a @moderateurs closing this topic now to facilitate discussion moving to the Ore forum page. Thank you.