Inactive [SEC/MECH] LWC v4.1.1 :: Lightweight Protection for Chests, Furnaces, Dispensers, and more! [1.2]

Discussion in 'Inactive/Unsupported Plugins' started by Hidendra, Jan 17, 2011.

  1. Offline


    LWC v4.1.1 3/1/2012
    [​IMG] Download
    [​IMG] Bleeding-edge builds
    [​IMG] Feature requests, Suggestions and Issues
    [​IMG] IRC - Live Chat ( #LWC )
    [​IMG] github
    [​IMG] wiki (not fully up to date yet, sorry!)
    [​IMG] Donate

    Using LWC

    [​IMG] Modules
    Modules are seperate plugins much like LWC but extend LWC in some way, usually by giving extra functionality. While there may be more than already listed here, these modules are ones that are officially supported by LWC and maintained by the same author (Hidendra).

    [​IMG] LWC-Economy 1.30 - [​IMG] Download
    Configuration file: plugins/LWC/iconomy.yml

    LWC-Economy allows players to buy protections with economy money. At the moment, iConomy, BOSEconomy and Essentials are supported (have an Econ plugin that you want supported? PM me!) It can be configured on a per-user and per-group basis. It does not use Register.

    Aside from purchasing, when a user removes a protection, they will also be refunded what they initially paid for the protection.

    Discounts can also be given to each individual group, player, or by default. A discount is defined by giving X amount of protections for Y price, e.g 5 protections for free (0). After getting 5 protections for free, they pay full price again. They cannot get another discount again unless one of the following becomes true: a. an admin manually resets them b. the discounted amount of protections is increases (e.g increasing from 5 to 6 will mean said player gets 1 more for free) or c. the discount price itself changes (which means they will again get 5 protections for the new price.)

    What can be protected?
    • Chests
    • Dispensers
    • Furnaces
    • Doors
    • Signs
    • Trap doors
    • Anything else! Protections can be customized to anything you wish.

    • Plug 'n play! LWC handles all dependency resolution -- you just put LWC.jar in your plugins directory
    • Has reached a level where its routinely safe and stable.
    • Protections can be: Public, Password, and Private (by User and/or Groups)
    • If the block has a persistent inventory (ex. chest), LWC can protect it! (Unless the server owner disabled the protection of a specific block!)
    • Limits of how many protections a user or group can lock
    • Small memory footprint. No flat files.
    • For chests, only 1 side of the chest needs to be protected. The plugin saves space by dynamically linking connected chests as protected
    • Much, much more. This post would be extremely long if I were to post every feature LWC has to offer.


    If your server would benefit more from a version of LWC in your native tongue, or you just want to do it because LWC is awesome, I'm open to allow translations to (almost any) language. Almost all LWC messages are editable.
    Locale files can be UTF-8, but are limited by Minecraft's charset (Latin-1.)

    The current and latest English locale can be found here:

    Currently, the following languages are officially bundled with LWC:
    • German - de - @Dawodo
    • Polish - pl - @Geoning @dudsonowa and @andrewkm
    • French - fr - @Cehel
    • Dutch - nl - @MadZero & @aoa2003
    • Czech - cz - @hofec
    • Swedish - sv - @christley
    • Russian - ru - @IlyaGulya - requires a Cyrillic font mod for the MInecraft client
    • Spanish - es - Raul " @RME " Martinez & David " @DME " Martinez
    • Danish - da - @TCarlsen

    Changelog (open)

    LWC 3.54
    • FIX: Exploit related to Showcase & LWC
    • /lwc admin report has been fixed

    LWC 3.53
    • FIX: All Permission plugins will now work as they should. In SuperPerms, lwc.protect will default to true. if you are using Permissions 2/3/GroupManager/etc, lwc.protect will default to false

    LWC 3.52
    • FIX: Permissions 2/3 stopped working correctly in 3.51

    LWC 3.51
    • lwc.protect has been changed to be default false again in SuperPerms

    LWC 3.50
    • Remove the permission metadata from defined commands so the endless onslaught of "LWC throwing Dave error !" stops

    LWC 3.49
    • FIX: Double console output

    LWC 3.48
    • 3.48 and 4.00 alphas can now be interchanged without receiving errors.
    • FIX: lwc.protect now defaults to true for SuperPerms, so Permissions 2/3 can be used without receiving Dave errors

    LWC 3.47
    • NEW: iConomy 6 support. LWC-Economy does not need to be updated, only LWC.jar

    LWC 3.46
    • FIX: The Redstone event was not being propagated via the new events

    LWC 3.45
    • FIX: plugins/LWC/locale/ (Locale override) could not create new key values such as grass, stone, etc.
    • Feature: The "nospam" mode now hides notices.
    • Feature: Double wooden doors will now also auto open when opening them. They must both be protected.

    LWC 3.44
    • FIX: LWC would not auto reconnect to MySQL after sitting idle for a few hours

    LWC 3.43
    • NEW: Native PermissionsEx (PEX) support
    • NEW: /lwc admin purgebanned can now take -remove as an argument to also remove the removed blocks & item contents (e.g: /lwc admin purgebanned -remove)
    • FIX: An exception would be thrown when using /lwc admin cleanup while using SQLite
    • FIX: A Bukkit bug would throw an exception when a block was pushed above a chest via piston
    • FIX: The /permissions command on PermissionsBukkit 1.2 (not 1.1) was not working correctly.
    • The Polish localization has been updated courtesy of @Geoning

    LWC-Economy 1.30
    • NEW: Native Essentials Econ support
    • NEW: type: has been added to discounts (very latest iconomy.yml) to allow you to revert to the old way of how discounts were given (default: EXACT, old way: TOTAL)
    • NEW: Refunds can now be disabled by making iConomy.refunds false

    LWC 3.42
    • The flag "EXEMPTION" has been added to allow you to exempt flags from commands such as ADMIN PURGE and ADMIN EXPIRE; it prevents the protection from being removed unnecessarily. It can only be activated by LWC admins. Use /cexempt on or the usual /lwc flag exempt on
    • FIX: Some servers were experiencing a freezing issue on startup which is now fixed
    • FIX: Disabled modes were not properly disabled, despite being told the mode was disabled.

    LWC-Economy 1.21
    • FIX: On some servers LWC-Economy would not bootstrap itself into LWC correctly
    • LWC is unaffected, but due to how automatic provisioning works, the binary will be different from the last due it modifying the build number in /lwc admin version

    • FIX: Servers with autoUpdate set to true would find 3.40 would crash all of the time due to a stackoverflow exception.
    • FIX: PermissionsBukkit /permissions command was unusable due to LWC making it load when the server first started, not when it normally would.

    LWC-Economy 1.20
    • LWC-iConomy.jar has now become LWC-Economy.jar -- please update accordingly.
    • BOSEconomy is now supported alongside iConomy. No extra setup is necessary for either!
    • Money paid for protections can now be refunded when you destroy the protection, even if the person who paid (the owner) is offline.
    • Discounts now give out the exact amount of protections for the discounted price. For example, if 'newCharge' is set to 0 and 'amount' is set to 5, a player will be able to create 5 protections for free after it takes effect.

    LWC 3.40
    • Almost all current LWC Module events have been deprecated. They have been replaced with events such as: `onProtectionInteract(LWCProtectionInteractEvent event)`
    • Fixed PermissionsBukkit compatibility: some commands did not work correctly
    • `/lwc admin cleanup` has accelerated to warp 5
    • Servers without any Permissions plugin would find anyone would have LWC Admin access
    • The mode "nospam" has been added to prevent protection creation messages from popping up (e.g "created protection successfully.") Use /cnospam or /lwc mode nospam, which toggles it on and off.
    • Protection history. LWC now logs all protection creations/destructions -- in the future, this may log chest access, but if it happens it will be a separate plugin such as LWC-Economy
    • -remove flags have been added to `/lwc admin expire` and `/lwc admin purge <player>` to remove the associated protection block. For example, if you use `/lwc admin purge -remove Hidendra`, it will remove all protections by Hidendra, and also all of the blocks protected in the world, along with any chest contents.
    • If LWC loses connection to MySQL, LWC will prevent access to chests until the connection is regained. This is to prevent stealing from chests if the connection is somehow lost and cannot be immediately regained.
    • Pistons can no longer destroy protected doors and so on.
    • Multitude of bug fixes and minor corrections
    • Minor optimizations

    • PermissionsBukkit is now officially supported. LWC will still work on builds pre-1000
    • lwc.blockinventory has been renamed to lwc.deny - please take note
    • Fixed a bug where protections would be loaded from any world
    • Fixes to the Danish translation

    • Added core.ignoreExplosions to core.yml to allow an admin to allow creeper explosions / TnT to destroy protections
    • Protections will now keep track of the last time they were interacted with
    • Added the command /lwc admin expire to allow you to expire protections that have not been used in so long. Example: /lwc admin expire 2 weeks
    • Added the command /lwc admin purgebanned to remove protections of every played in banned-players.txt
    • Added the command /lwc admin query to allow raw queries on the physical database
    • Drop transferring could not be disabled, it is now fixed.
    • Various bug fixes

    • Fix "fetch size" error
    • Removed the auto-removal of the very old players table


    • Very important bug fix for those who are using MySQL and prefixes. Prefixes will now work correctly and any issues arisen from MySQL usage should now be resolved
    • Fixed lang-defined block names being used in core.yml - protections instead of the english variant, otherwise all protections are broken.

    • It's not all about me! I've tried my hardest and /lwc credits was the result. It turns out there is a lot more people I am extremely thankful to than can fit on one chat page, so instead it scrolls.
    • Many, many people helped with LWC in vastly different ways and it's impossible to credit every single person accurately, thus I missed a few people.

    This update introduces three more languages: Russian, Spanish, and Dutch.
    • Russian - @IlyaGulya - requires a Cyrillic font mod for the Client
    • Spanish - Raul " @RME " Martinez
    • Spanish - David " @DME " Martinez
    • Dutch - @Tcarlsen

    Chunk corruption workaround
    • Have you ever noticed, when you /cinfo'd something, it said "That air is not registered"? Or when chests randomly stop working? If you get this a lot, you are most likely affected by an issue in Bukkit where chunks will mysteriously report Air (or some other block) for each block in the chunk. Please refer to this bug report on Leaky Bukkit:
    • @morganm graciously found a way to workaround this issue, and it involves forcing every single protection to be cached and some other magical tidbits (without getting too technical.) To enable this, open up plugins/LWC/core.yml and then change bukkitBug656workaround to true. If you don't see it under core:, add it:
          bukkitBug656workaround: true

    • Trap doors are now available as a default protection for any new configurations: they will not automatically add themselves to existing LWC configurations
    • The default value for magnet.yml - perSweep has been changed from 20 to 40
    • The command /lwc debug has been added to test your permissions and show you precisely what you have access to
    • LWC now displays the git commit and Jenkins build ( in version strings (e.g /lwc admin version or /lwc admin report).

    • Translation: Swedish! Thank you @christley!
    • Bug fix for block placement

    • Translation: Czech! Thank you @hofec
    • The default value for core.showMyNotices has been changed to false (does not affect current installs.)
    • Burning furnaces have been fixed
    • Iron doors have been fixed
    • Redstone fix
    • Fixed auto register allowing registrations without having lwc.protect
    • Feature: auto openable Iron Doors. On by default -- iron doors (including double doors) will open (or close) when you click them provided they are both protected and you have access to them. "openAndClose," which closes the door automatically after x seconds (3 by default) is available but currently may not work as expected (works oppositely for doors facing North or South; doors will stay open.)
    • Trap doors (aka hatches) have been added to the default protection list. However, if you have an existing core.yml, and want trap doors, you either need to delete core.yml and restart the server (thus redownloading it) or adding trap_door to protections.blocks, e.g
                  enabled: true
                  autoRegister: off

    • Sign names have been normalized to "Sign" (e.g Wall sign and Sign post are shown as just Sign)
    • Added locale values for "you" and block names (chest, furnace, dispenser, wooden_door, iron_door, and so on.) Custom block names can be defined if you have custom protections.
    • Dutch translation -- thank you to @MadZero and @aoa2003

    • Notices will be shown correctly to admins when showMyNotices is disabled.

    • Limit the amount of queries the Magnet module can use (can be changed with magnet.perSweep, default 20. Delete magnet.yml to auto-regen it). On larger worlds, this was a severe issue
    • magnet.enabled now works correctly

    • MySQL prefix is now working as it should
    • Minor fix with the cache update in 3.02

    • Cache null protections as well, to prevent massive redstone spam

    LWC 3.01

    Thank you so much to the many, many people who provided feedback and suggestions on 3.00.
    This changelog may be incomplete as I probably missed some obscure changes.

    The following languages are now available in LWC:

    Lists support
    • LWC supports the Lists plugin which allows you to create a list for your protections to use. Anyone in this list attached to the protection can access your protection
    • When modifing/creating the protection, use l:ListName or list:ListName, e.g: /cmodify l:Test or /cprivate l:Test

    • is now gone. It has been replaced by multiple .yml files, e.g core.yml, limits.yml, worldguard.yml, and so on.
    • Your old is still automatically converted.

    • The old in-database limits has been fully removed. It is replaced by an on-disk alternative, limits.yml. This very easily allows much more in-depth limits management (e.g only: 5 chests, 2 furnaces, 0 doors)

    Custom protections
    • It is now extremely easy to create your own custom protections, or remove existing ones (core.yml -> protections:). For example, this is how you would make Note Blocks protectable, and allow people to play them (But not change the note!):
                enabled: true
                ignoreLeftClick: true

    • [I hope] final major revision to the LWC Api. New additions will allow other plugins to hook into LWC much more easily and do things that were not possible before. Features can be seamlessly integrated into LWC as if they were in LWC itself.
    • PhysDB.getPrivateAccess is now deprecated -- please use protection.getAccess instead!
    • Protections can be more easily modified utilizing methods in their objects: save() (queued save), saveNow(), remove(), removeCache() (just removes the protection from the cache, not the database), and update() (just updates the cached protection, save()/saveNow() already does this)

    LWC Modules
    • Modules can be thought of as a plugin inside LWC itself -- more or less they will change LWC's behaviour in some way, depending on the module.
    • Very easily implemented by developers: cancel protection registrations, cancel that damn protection message, and way more! More info on the wiki.

    Admin customization
    • There are now a ton of permissions nodes; there is one for each admin command. For example, for every Admin command, you could use: lwc.admin or lwc.admin.*. For just "find" and "forceowner", you could give a group/player the following: lwc.admin.find and lwc.admin.forceowner. Full list on the wiki.
    • Please note that lwc.admin.* only grants all Admin commands; lwc.admin still has a higher authority over the former (e.g, lwc.admin is considered the owner of any protection, while lwc.admin.* is not !!)

    Player customization
    • Like the admin commands, the main LWC commands can now be customized via permissions. lwc.protect still functions the same (all functionality); some examples of new nodes are: lwc.create or lwc.create.* (create anything), lwc.create.private (only be able to create private protections), (/cinfo), lwc.modify (/cmodify), lwc.unlock (/cunlock), and so on. Full list on the wiki.
    • Please note that without lwc.protect, you need to manually assign flags. E.g: lwc.flag.* or / lwc.flag.magnet

    Magnet flag
    • The chest will act as a magnet and suck up nearby items (within a 3 block radius.) This can be very useful for automatic farms (e.g animals or crops.) It is compatible with double chests.
    • Can also specify items that these special chests will not pick up (in magnet.yml)
    • Compatible with Double Chests

    • It is now possible to sell protections with the fully optional LWC-iConomy bridge module. You just throw LWC-iConomy.jar into your plugins folder and then edit iconomy.yml in plugins/LWC/ when it's generated on the next startup!
    • You can also allow players to have a certain amount of protections at a reduced price (or even free) e.g free protections while you have less than 5 (but regular price after that.)

    • LWC now does major caching of protections in memory. Previously, LWC hit the database everytime a protection is opened; now they are routinely stored in cache without a huge hit on memory usage (very minimal.) It can be increased from the default of 10000 if you wish in core.yml (core.cacheSize). More will most likely be cached in the future
    • Access rights are now stored with Protections (for the curious, it uses an OUTER JOIN, so just 1 query.)
    • Protections are precached (as many as possible) when the server is started
    • Lots of bug fixes (mostly miscellaneous.)

    • MySQL prefix can now be configured (if you change it with an existing MySQL install, it will fix that automatically, don't worry!)
    • /cpersist or /lwc mode persist now acts as a toggle for the mode
    • Added the following aliases: /cpersist , /cdroptransfer , /cmagnet , and /cadmin
    • /climits displays your protection limit and how many protections you have protected.
    • Minor changes all around


    • Security bugfix regarding an issue in minecraft itself (thanks sycot)

    • Native German translation! If you wish to use LWC in German, please change "locale" in to de. Many thanks to @Dawodo for doing the translation!
    • /lwc admin cleanup will now show the correct values instead of variable names when outputting results
    • enforce-worldguard-regions is now compatible with WorldGuard 5.x
    • Redstone is now changed again. All set redstone flags are reset. Redstone will obey the deny-redstone config value (which is false by default), meaning if it is set to false, you need to explciitly set the flag to disable redstone (/lwc flag redstone on), and if it is set to true, all doors prevent redstone by default so you need to set the flag to allow redstone.

    • Minor bug fixes

    • By default, redstone WILL NOT open doors (at the moment, it appears dispensers are unaffected, hopefully they will be fixed in CraftBukkit). In order to allow redstone to open your door, you need to issue this: /lwc flag redstone on. Using /lwc flag will show you the available protection flags -- these are "switches", only on/off (only redstone flag exists at the moment)
    • Bug fix: Protections will auto protect themselves again when being placed

    • Official support for RB builds >600 now that I am back home
    [hit max thread length]

    enjoy, gents
  2. Offline


    Any possibility to have monies charged for protections to go into a specified account?
  3. Offline


    There is a LWC plugin for charging money for each protection made.
  4. Offline


    I have a problem, if I use ./cprivate on my chest only I can use this chest, but if someone use ./cremove on my chest he/she can take my items from chest, how I solve this problem? Thank you.
  5. Offline


    You don't give the people permissions to use /cremove :p
  6. Offline


    If someone wants to remove protection from his chest?
  7. Offline


    Yes I know, but I want that charged money to be moved into a specific account.
  8. Offline


    I'm not sure if that is possible.
  9. Offline


    Only give lwc.protect to players. It will allow them to remove their own protections only.

    This way only admins or anyone with lwc.admin node can remove protections they don't own.

    Yeah, that was more of a feature request :p

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: Jul 18, 2016
  10. Offline


    Thank you.
  11. Offline


    Hello, I'd like to customize LWC to allow the protection of Iron Blocks, Gold Blocks, Diamond Blocks, Lapis Lazuli Blocks, and Mob Spawners.

    I used the codes 'iron_block, gold_block, diamond_block, lapis_block, and mob_spawner' and found they didn't work. What are the actual codes for these items?
  12. Offline


  13. Offline


    Double wooden doors please?
    iron ones works but wooden ones doesnt.
  14. Offline


    My favorite plugin of all. Never had any problems ever. Thanks!
  15. Offline



    hi excuse me but this is my italian translation it work 100% with no bug
    ## LWC default locale
    ## author: Massimo1993
    ##    General   ##
    # Protection type names :-)
    kick_trap=Kick Trap
    ban_trap=Ban Trap
    # Yes/no response (mainly for /lwc info)
    # Some generic responses and block names
    wooden_door=Porta di legno
    iron_door=Porta di ferro
    trap_door=Trap Door
    # Internal LWC error (if this shows up, something went terribly wrong most likely)
    protection.internalerror=%red%[LWC] Errore interno. Contatta immediatamente un Admin.%white% :%id%
    # Access denied.
    protection.accessdenied=%red%Accesso negato.
    # Notify admin it is protected (if enabled)
    protection.general.notice.protected=%red%Avviso: %white%That %red%%type% %block%%white% è bloccato/a da%yellow% %owner%.
    # Protection has been removed + unregistered
    protection.unregistered=%red%%block% non registrato.
    # Enforce access to blocks
    %red%This %block% is locked \n\
    %red%Type %gold%%cunlock% <Password>%red% per sbloccarlo/a.
    protection.general.locked.private=%red%This %block% è bloccato/a da un magico incantesimo
    # Pending action
    protection.general.pending=%red%Hai già un'azione in corso.
    ##   Commands   ##
    # Creating a protection
    protection.create.password=%blue%Using password:%yellow% %password%
    %blue%Lock type:%green% %type% \n\
    %green%Per favore, colpisci il tuo blocco per bloccarlo.
    # Info una preotezione per vederne le informazioni. usando%red% %used%%blue% di%green% %quota%%blue% protezioni.
    # Flag
    protection.flag.invalidflag=%red%The flag%white% %flag%%red% non è stato trovato
    protection.flag.invalidtype=%red%The type%white% %type%%red% è invalido
    protection.flag.finalize=%blue%Per favore, colpisci la tua protezione per applicare la flag
    # Modes - not yet supported
    # Modify
    protection.modify.finalize=%blue%Per favore, colpisci la protezione per completare le modifiche
    # Owners
    protection.owners.finalize=%blue%Colpisci la protezione per vedere chi vi ha avuto accesso
    # Remove una protezione per rimuoverla
    protection.remove.modes.finalize=Successfully removed all set modes.
    # Menu tuo menù è stato settato a%blue% %style%
    # Unlock
    protection.unlock.nothingselected=%red%Non hai selezionato nulla. Apri una protezione bloccata, prima.
    protection.unlock.notpassword=%red%Come cazzo hai fatto?
    protection.unlock.password.valid=%green%Password accettata.
    protection.unlock.password.invalid=%red%Password invalida.
    # Modes
    protection.modes.disabled=%red%Quella modalità è momentaneamente non disponibile.
    %green%I tuoi comandi permarranno.\
    %green%I tuoi comandi non permarranno più.\
    %green%LWC Drop Transferring \n\
    /lwc mode droptransfer%blue% select%white% - Seleziona una cesta per trasferire a \n\
    /lwc mode droptransfer%blue% on%white% - Attiva droptransfer \n\
    /lwc mode droptransfer%blue% off%white% - Disattiva droptransfer \n\
    /lwc mode droptransfer%blue% status%white% - Controlla lo stato del droptransfer
    protection.modes.dropxfer.selectchest=%red%Per favore, seleziona una cesta prima di commutare il droptransfer. favore, disattiva il droptransfer prima di selezionare un'altra cesta. favore, colpisci una cesta registrata per selezionarla come target per il tuo droptransfer.
    %blue%Il droptransfer è attivo. \n\
    %blue%Ogni oggetto caduto verrà trasferito alla tua cesta droptransfer è inattivo. hai registrato un tagret per il tuo droptransfer. è attualmente%green% attivo.
    protection.modes.dropxfer.status.inactive=%blue%Droptransf è atualmente%red% inattivo.
    # Admin (large command set)
    protection.admin.noconsole=%red%Supportato solo in-game!
    You have:%green% %count%%white% protections. \n\
    %red%Potrebbe volerci un po' dipendentemente da quante protezioni hai
    protection.admin.cleanup.noworld=%red%Error:%white% Il mondo %world% non esiste!
    protection.admin.cleanup.removednoexist=Rimossa (noexist): %protection%
    protection.admin.cleanup.removeddupe=Rimossa (dupe): %protection%
    protection.admin.cleanup.complete=LWC è riuscito a cancellare%green% %count%%white% protezioni%green% %seconds%%white% secondi!
    protection.find.invalidpage=%red%Numero della pagina non valido.
    protection.find.currentpage=%red%Pagina:%white% %page%
    protection.find.nextpage=Prossima pagina:%red% /lwc admin find %player% %page%
    # hard to read :-), just "showing" and "total"
    %blue%Mostrando%red% %start%%white%-%red%%ceil%%white% (total:%red% %results%%white%) \n\
    protection.admin.forceowner.finalize=%blue%Colpisci una protezione per cambiarne il proprietario a:%white% %player%
    protection.admin.remove.invalidid=%red%ID non valido.
    protection.admin.remove.finalize=%green%Protezione rimossa con successo.
    protection.admin.view.noexist=%red%Quella protezione non esiste!
    protection.admin.view.noinventory=%red%Quella protezione non ha un inventario!
    protection.admin.view.viewing=%red%Visionando inventario #%blue%%id%
    protection.admin.purge.finalize=%green%Reimosse tutte le protezioni create da%blue% %player%
    protection.admin.reload.finalize=%green%Ricaricate le configurazioni di LWC!
    %red%LWC \n\ \n\
    Main plugin: %plugin_color%%plugin_version%%yellow%/%green%%latest_plugin% \n
    %green%Updated LWC successfully to version:%white% %version% \n\
    %green%Please reload LWC to complete the update.
    protection.admin.update.noupdate=%red%Nessun aggiornamento disponibile. limite globale di%gold% %limit%%green% protezioni. limite di%gold% %limit%%green% protezioni per il gruppo %name%
    protection.admin.limit.player=%green%Registrato limite di%gold% %limit%%green% protezioni per il giocatore %name%
    protection.admin.limit.remove=%red%Limite annullato per%gold% %name%
    protection.admin.clear.protections=%green%Rimossa ogni protezione e diritto.
    protection.admin.clear.rights=%green%Rimosso ogni diritto di protezione.
    # get limits
    protection.getlimits.player=%blue%%name% sta usando%red% %used%%blue% di%green% %quota%%blue% protezioni. puù avere%green% %quota%%blue% protezioni.
    # expiration
    protection.admin.expire.invalidtime=%red%Tempo sepcificato non valido (esempio: 2 settimane)
    protection.admin.expire.removed=%green%Scadute %count% protezioni.
    ##  Interaction ##
    protection.interact.error.blocked=%red%L'Admin ti sta bloccando dall'aprire quello!
    protection.interact.error.notregistered=%red%Quel %block% non è registrato!
    protection.interact.error.alreadyregistered=%red%Hai già registrato quel %block%!
    protection.interact.error.notowner=%red%o %block%!
    # both /cprivate people and /cmodify
    protection.interact.rights.register.player=%green%Registered rights for the player%gold% %name% %isadmin% rights for the group%gold% %name% %isadmin%
    protection.interact.rights.register.list=%green%Registered rights for the List%gold% %name% %isadmin%
    protection.interact.rights.remove.player=%green%Removed rights from the player%gold% %name% %isadmin% rights from the group%gold% %name% %isadmin%
    protection.interact.rights.remove.list=%green%Removed rights from the List%gold% %name% %isadmin%
    # Creating protections on block place
    protection.onplace.create.finalize=%green%Creato un/una %type% %block% con successo
    # Flag
    protection.interact.flag.add=%green%Attivata la flag%blue% %flag%%green% per la protezione con successo
    protection.interact.flag.remove=%red%Rimossa la flag%blue% %flag%%red% per la protezione con successo
    # Creation
    protection.interact.create.password=%blue%Per sicurezza, non devi reinserire la tua password fino al prossimo Log in.
    protection.interact.create.finalize=%green%Creata la protezione con successo.
    # Removal
    protection.interact.remove.finalize=%green%Rimosso il blocco su %block% con successo.
    # Forcing owner
    protection.interact.forceowner.finalize=%green%Settato con successo il proprietario a%white% %player%
    # Info\
    %blue%Tipo:%gold% %type% \n\
    %blue%Proprietario:%gold% %owner% \n\
    %blue%Puoi accedervi: %access% autorizzati: %players%\
    Raw data from the protection: \n\
    # Drop transfer
    %red%Non puoi selezionare una cesta non registrata come target per il droptransfer. \n\
    %red%Usa "/lwc mode droptransfer select" per riprovare. \n\
    %red%Non puoi usare una cesta a cui non puoi accedere come target per il droptransfer. \n\
    %red%Se questa cesta è protetta da password, per favore, sbloccala prima di riprovare. \n\
    %red%Usa "/lwc mode droptransfer select" per riprovare
    protection.interact.dropxfer.notchest=%red%Devi selezionare una cesta come target per il droptransfer!
    protection.interact.dropxfer.finalize=%green%Cesta registrata con successo come target per il droptransfer.
    ## Help screens ##
    # simple usage
    # %command% represents the command
    help.simpleusage=%red%Usage:%gold% %command%
    # /lwc
    %green%Welcome to LWC, a Protection mod by Hidendra\n\
    %white%/lwc -c %blue%Visualizza il menù d'aiuto per creare protezioni \n\
    %white%/lwc -c %lightblue%<public|private|password> \n\
    %white%/lwc -m %blue%Modifica una protezione esistente \n\
    %white%/lwc -u %blue%Sblocca una protezione con password \n\
    %white%/lwc -i%lightblue% [limits]%blue% Vedi le informazioni di una protezione \n\
    %white%/lwc -r %lightblue%<protection|modes> \n\
    %white%/lwc mode %lightblue%<persist|droptransfer> \n\
    %white%/lwc flag %lightblue%<name> <on|off>%blue% Cambia la flags di protezione \n\
    %white%/lwc menu %lightblue%<basic|advanced> %blue%Cambia lo stile del menù
    %green%Welcome to LWC, a Protection mod by Hidendra\n\
    %white%/cprivate %blue%Crea una protezione privata \n\
    %white%/cpublic %blue%Crea una protezione pubblica \n\
    %white%/cpassword %lightblue%<Password> %blue%Crea una protezione con password \n\
    %white%/cmodify %blue%Modifica una protezione esistente \n\
    %white%/cunlock %lightblue%<Password> %blue%Sblocca una protezione con password \n\
    %white%/cinfo  %blue%Guarda le informazioni su una protezione \n\
    %white%/climits  %blue%Guarda l'ammontare di protezioni che puoi creare \n\
    %white%/cremove %blue%Rimuovi una protezione \n\
    %white%/lwc mode %lightblue%<persist|droptransfer> \n\
    %white%/lwc flag %lightblue%<name> <on|off>%blue% Cambia le flags di protezione \n\
    %white%/lwc menu %lightblue%<basic|advanced> %blue%Cambia lo stile del menù
    # /lwc -c
    %green%LWC Protection \n\
    %white%%cpublic% %gold%Crea una protezione pubblica \n\
    %blue%Chiunque può usare una protezione pubblica, ma nessuno può privatizzarla \n\
    %white%%cpassword% <Password> %gold%Proteggi con password un blocco \n\
    %blue%Ogni volta che loggi devi reinserire la password \n\
    %blue%it (se qualcuno conosce la password, possono accedervi!) \n\
    %white%%cprivate% %gold%Creata una protezione privata \n\
    %blue%Privato significa privato; puoi anche permettere ad altri utenti o a gruppi di accedere al blocco. Puoi farlo aggiungendo i loro nomi dopo "private". \n\n\
    %white%Example: \n\
    %blue%%cprivate% UserName g:GroupName OtherGuy \n\
    %blue%Puoi specificare più di un gruppo e o giocatore per comando!
    # /lwc -m
    \n%green%LWC Protection \n\
    %cmodify% <Users/Groups>%gold% Modifica una protezione esistente, aggiungendo o rimuovendo giocatori e/o gruppi \n\
    %blue%See:%gold% /lwc create%blue%, esempio per una protezione privata \n\
    %blue%Additional prefixes for Users/Groups: \n\
    %red%-%blue%:Rimuovi un Giocatore/Fruppo dalla protezione \n\
    %red%@%blue%: Il Giocatore/Gruppo sarà abilitato a modificare la cesta e aggiungere altri Giocatori. Non possono disabilitare il proprietario dal modificarla. \n\
    Examples \n\
    %gold%Rimuovi un Gruppo dall'accesso:%blue% %cmodify% -g:Name \n\
    %gold%Rimuovi un Giocatore e aggiungi un Admin:%blue% %cmodify% -Name @AdminName
    # /lwc -a
    %red%LWC Administration \n\n\
    /lwc admin view%blue% Guarda un inventario protetto mentre ci stai accanto usando l'ID della protezione \n\
    /lwc admin find%blue% Guarda tutte le protezioni creata da un giocatore \n\
    /lwc admin forceowner%blue% Cambia il proprietario di una protezione \n\
    /lwc admin remove%blue% Rimuovi una protezione usandone l'ID \n\
    /lwc admin purge%blue% Rimuovi tutte le protezioni dei Giocatori \n\
    /lwc admin cleanup%blue% Tentativo di pulire il database \n\
    /lwc admin version%blue% Guarda la versione di LWC in uso e la più aggiornata \n\
    /lwc admin update%blue% Aggiorna all'ultima versione di LWC \n\
    /lwc admin report%blue% Guarda il rapporto di performance di LWC \n\
    /lwc admin convert%blue% Converti il database di un altro plugin ad LWC \n\
    /lwc admin clear%lightblue% <protections|rights>%red% Warning! Questo comando è PERICOLOSO e non può essere annullato!!
    # /lwc flag
    Usable flags: \n\
    %blue%  Redstone:%white% If "on", redstone %redstone%%white% open doors.
    # redstone specific flags, depends on deny-redstone is enabled/disabledò può
    ##    General   ##
    # Commands used for menu styles, just so I don't hardcode them :-)
    cprivate.advanced=/lwc -c private
    cpublic.advanced=/lwc -c public
    cpassword.advanced=/lwc -c password
    cmodify.advanced=/lwc -m
    cunlock.advanced=/lwc -u
    cinfo.advanced=/lwc -i
    cremove.advanced=/lwc -r
    climits.advanced=/lwc -i limits
    cstatus.advanced=/lwc -c status
    ## 3.00 ##
    protection.exceeded=%red%Hai raggiunto il limite di protezioni utilizzabili!
    %gray% Player:%gold% %player% \n\
    %gray%  Type:%yellow% %type% \n\
    %gray%  Limit:%yellow% %limit% \n\
    %gray%  Currently protected:%yellow% %protected%
    ## 3.10 ##
    ########## porta si apre scricchiolando....
    protection.doors.close=%green%La porta si chiude con violenza!
    ## 3.40 ##
    protection.modes.nospam.finalize=%green%Il messaggio di creazione protezione non ti verrà più mostrato messaggio di creazione protezione verrà mostrato di nuovo
  16. Offline


    How does bukkitPermissions work when lwc looks for limits since it looks for groups.
  17. Offline


    i found a bug, if i give a /reload its crashes LWC!! Can you Fix that?
  18. Offline


    i get this error report

    19:37:36 [SCHWERWIEGEND] Could not load 'plugins/LWC.jar' in folder 'plugins':
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
            at java.lang.reflect.Constructor.newInstance(
            at org.bukkit.plugin.SimplePluginManager.loadPlugin(
            at org.bukkit.plugin.SimplePluginManager.loadPlugins(
            at org.bukkit.craftbukkit.CraftServer.loadPlugins(
            at org.bukkit.craftbukkit.CraftServer.<init>(
            at net.minecraft.server.ServerConfigurationManager.<init>(
            at net.minecraft.server.MinecraftServer.init(
    Caused by: while scanning for the next token
    found character         '\t' that cannot start any token
     in "<reader>", line 13, column 20:
            adapter: sqlite
            at org.yaml.snakeyaml.scanner.ScannerImpl.fetchMoreTokens(
            at org.yaml.snakeyaml.scanner.ScannerImpl.checkToken(
            at org.yaml.snakeyaml.parser.ParserImpl$ParseBlockMappingKey.produce(
            at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(
            at org.yaml.snakeyaml.parser.ParserImpl.checkEvent(
            at org.yaml.snakeyaml.composer.Composer.composeMappingNode(
            at org.yaml.snakeyaml.composer.Composer.composeNode(
            at org.yaml.snakeyaml.composer.Composer.composeMappingNode(
            at org.yaml.snakeyaml.composer.Composer.composeNode(
            at org.yaml.snakeyaml.composer.Composer.composeDocument(
            at org.yaml.snakeyaml.composer.Composer.getSingleNode(
            at org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(
            at org.yaml.snakeyaml.Yaml.load(
            at com.griefcraft.util.config.Configuration.load(
            at com.griefcraft.util.config.Configuration.load(
            at com.griefcraft.lwc.LWC.<init>(
            at com.griefcraft.lwc.LWCPlugin.<init>(
            ... 13 more
  19. Offline



    Hey, trying this out to switch from Lockette, but having a few minor problems.

    Iron double doors get stuck alternated, like one open one closed all the time.
    Wooden doors don't act as double doors, or auto close.
    It doesn't seem to recognise PermissionsBukkit groups, I privatised doors and chests to myself and the group 'trusted', yet no one in that group can access these things.

    Any ideas?
  20. Offline


    Build #121 suddenly dissapeared from jenkins... ?
  21. Offline


    Not sure what happened exactly but for some reason whenever I place a cobblestone down where a door used to be it says it registered an iron door, whenever I place a door (iron or otherwise) on top of it, it causes it to just break apart.

    Going to clear the database to see if it solves this issue. :(
  22. Offline


    I'm getting the same thing as you two. It was running fine until I restarted the server just now.

    [Edit] Pretty sure this is a permissions problem
  23. Offline


    i swear to god noones been able to lock a pressure plate.......

    ive tried everything, asked multiple times looked and looked....NOTHING

    both stone and wood
  24. Offline


  25. Offline


    Just made the switch to this from Lockette on our server. It's great so far! One request I have is I would like the lwc.mod permission to only allow snooping of non-mod/admin ranks though. (ie one mod can't bypass another mods private stash, but could bypass any regular player's). Currently it allows snooping of both mods and non-mods.
  26. Offline


    So everyone else can lock trapdoors fine?
  27. Offline


    Haven't tried them yet to be honest. Waiting for the PermissionsBukkit groups fix before I give it a full going over with everything. :)
  28. Offline



    Was there ever a solution or fix implemented for the below users question? I am having the same issue. I have a perk for certain groups that rewards some free LWC's and when they use all of those up it lets them use the last one in their limit which is not free and available to all users. So if they try to LWC another it tells them their limit was exceeded but still charges them.

    Thank you.

  29. Offline


    Didn't work. Here's my core.yml:

        locale: en
        autoUpdate: false
        flushInterval: 10
        cacheSize: 10000
        defaultMenuStyle: basic
        showNotices: true
        showMyNotices: false
        verbose: false
        opIsLWCAdmin: true
        adapter: sqlite
        path: plugins/LWC/lwc.db
        host: localhost
        database: lwc
        denyRedstone: false
        autoRegister: off
        ignoreBlockDestruction: false
        ignoreLeftClick: true
        ignoreRightClick: false
                enabled: true
                autoRegister: private
                enabled: true
                autoRegister: private
                enabled: true
                autoRegister: private
                enabled: true
                autoRegister: off
                enabled: true
                autoRegister: off
                enabled: true
                autoRegister: off
                enabled: true
                autoRegister: off
                enabled: true
                autoRegister: off
                enabled: true
                autoRegister: off
                enabled: true
                autoRegister: off
                enabled: true
                autoRegister: off
            enabled: true
            enabled: true
  30. Offline


    Anyway you can add Double Door support? Like if 2 doors are both protected and connected to each other *A double Door* That when you open 1 door the other one open's as well. Kind of like the Lockette plugin. If you can that would be Awesome!
  31. Offline


    Yes, this would be very awesome.

Share This Page