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

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

DevBukkit

• Overview: http://dev.bukkit.org/server-mods/lwc/
• Forum: http://dev.bukkit.org/server-mods/lwc/forum/

Using LWC

• Installation
• Commands
• Permissions
• MySQL

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).

LWC-Economy 1.30 - 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.

Features

• 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.

Translations

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:
https://raw.github.com/Hidendra/LWC/master/src/lang/lwc_en.properties

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) Changelog (close)

11/29/2011
LWC 3.54

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

9/22/2011
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

9/20/2011
LWC 3.52

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

9/19/2011
LWC 3.51

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

9/16/2011
LWC 3.50

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

9/16/2011
LWC 3.49

• FIX: Double console output

9/15/2011
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

9/11/2011
LWC 3.47

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

9/11/2011
LWC 3.46

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

9/10/2011
LWC 3.45

• FIX: plugins/LWC/locale/lwc.properties (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.

9/10/2011
LWC 3.44

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

9/3/2011
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

8/28/2011
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.

8/26/2011
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

8/25/2011
3.41

• 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.

8/25/2011
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

3.31

• 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

3.30

• 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

7/5/11
3.21

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

7/4/11
3.20

• 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.

Credits

• 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.

Translations
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: http://leaky.bukkit.org/issues/656
• @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:
  
  Code:

      bukkitBug656workaround: true
  

Behaviour

• 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 (ci.griefcraft.com) in version strings (e.g /lwc admin version or /lwc admin report).

6/16/11
3.11

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

6/16/11
3.10

• 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
  
  Code:

          trap_door:
              enabled: true
              autoRegister: off
  

6/11/11
3.06

• 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

6/08/11
3.05

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

6/08/11
3.04

• 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

6/07/11
3.03

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

6/07/11
3.02

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

6/07/11
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.

Translations
The following languages are now available in LWC:

• Polish -- a thank you to @Geoning @dudsonowa and @andrewkm !!
• French -- a thank you to @Cehel !!

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

Configuration

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

Limits

• 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!):

Code:

        note_block:
            enabled: true
            ignoreLeftClick: true

API

• [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), lwc.info (/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.redstone / 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

iConomy

• 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.)

Performance

• 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.)

Other

• 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

Cheers

4/18/11
2.31

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

4/09/11
2.30

• Native German translation! If you wish to use LWC in German, please change "locale" in lwc.properties 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.

4/06/11
2.21

• Minor bug fixes

4/06/11
2.20

• 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

4/05/11
2.12

• Official support for RB builds >600 now that I am back home

[hit max thread length]

enjoy, gents

 

It dont work. I think the host is blocking installing a dll inside the x86 folder

 

It doesn't unzip anything, but you could try adding this to your startup arguments:

Code:

-Dlwc.purejava=true

(using pure java with a lot of protections WILL result in lots of lag)

 

I changed auto-register: private to auto-register: disabled and i am getting You do not have permission to do that.

Oh yea i forgot, CB 818, with LWC 3.00 rc1

 

Hi, done -- remove you magnet.yml so it redownloads it. The release build with the functionality will be out momentarily, just finishing up testing.

(incase you just want to skip deleting, or whatever)

Code:

# Magnet module
magnet:
    enabled: true

    # The radius around containers that they will suck up
    radius: 3

    # A blacklist of items that will NOT be picked up
    # Item names usually work, but be careful
    blacklist:
        - 500

Fixed in 3.01, which is the main release build which will be out momentarily.

 

can you say a release date for lwc 3 ?

 

You ... are ... amazing !

He JUST said momentarily right above your post lol.
By the way, LWC 3 has been out for days beyond days! Im already running on it with absolutely NO problems

 

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.

Translations
The following languages are now available in LWC:

• Polish -- a thank you to @Geoning @dudsonowa and @andrewkm !!
• French -- a thank you to @Cehel !!

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

Configuration

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

Limits

• 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!):

Code:

        note_block:
            enabled: true
            ignoreLeftClick: true

API

• [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), lwc.info (/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.redstone / 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

iConomy

• 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.)

Performance

• 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.)

Other

• 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

Cheers

 

Nice

It seens that the all-in-ram on startup feature is too slow. My server is starting for about 10 minutes now oO
I see RAM usage increasing by small, very small amounts each 5 seconds or so.

Man.. my server is still starting.. heh

My hardware is an i7 Extreme Edition with 16 GiB ram 2133 GHz and SSD disks.

FYI: Ps with 4 million protections started in about 50 seconds or so

My server finally started, took abou 15 minutes oO.

It seens WAY faster than before. I will put the server online for my 300+ player stress it a bit

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

What is your cacheSize value at in core.yml? If it's still at 100000 or whatever, that could probably be why.

At 10k protections, it seems to load them all instantly for me.

 

WTF ??? forgive me... the second time I ran the server it was almost instantly.

@Hidendra

Yeap, I set it to 1000000 now. LWC is caching it.

Can't wait

EDIT: So every time my server starts, LWC will update the pre-cache only the NEWLY placed protections ? Right ? Genious!

EDIT2: 21:46:46 [INFO] PhysDB Precached 553095 protections.


Let's put it online now!

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

Well, it just uses the most recent ones.

Good that it's working good for you now though

 

Well, after all the pre-caching, it took my server about 5 minutes to start just after it.

Is this normal ?

EDIT: Sad news, lag block still remains. In fact I couldn't note any speed improvement between -rc1 and 3.01

EDIT: FYI: Even when I log alone into the server there is block lag. If I disable LWC and test again with only me in the server, the lag is gone. So I am 100% sure that LWC is causing this.

 

Well, since you have so many protections it could be that. Have you tried using a lower value? (even 100k, or around there, even)

 

@Hidendra
The lag happens ONLY on block BREAK. (My mistake not mentioning this before). Hope it helps.

 

Massive Block Lag is happening in 3.00. When I break any blocks they come back and disappear a few seconds later, Hope this can be fixed with something simple in the config or on your side.

Thanks for the great plugin!

 

3.01 working great on Cb #818 + (Im on #839)
No block lag here and all is working perfectly well.
-
@Hidendra
The magnet blacklist is working wonderfully Thank you very much!

 

I can confirm the lagging in version 3.x.
I've isolated the issue to being MySQL. If the settings are set to log in MySQL, constant "Can't keep up" message appear. Changing to SQLite fixes this lag..
I'm pretty sure MySQL is much more stable than SQLite, but not in this current case :S? Maybe a bug?

 

@Hidendra
Small problem, or, im just missing a configuration or have it set up wrong lol.
My users all just started rage complaining about it saying.... That protection is locked by you... everytime they opened their own protection.
So I figure there must be a config setting for this, and find "ShowMyNotices" ... I make this false, and it fixed the problem....
-
However new problem, I am OP and I can open any door, however if a door is not locked by me I would like it to be like it previously was, I can STILL open it... however it will say that private door is locked by player1 (for example)
-
Hope im not confusing you too much
-
It was fine with 3.00 rc1 now i either annoy the players lol or dont see whos door im opening (I can still use /cinfo but that is a pain...I prefer it to just show.)
-
I think the whole showmynotices should just be...wiped lol back to how it was.

Im on mysql, and have been using 3.x for over a good week, with aboslutely no lag whatsoever...

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

Interesting - what is the output of /lwc admin report?

Is showNotices set to true?

 

Mine wont work with mysql I have the datatable all set up too.

Code:

database:
    adapter: mysql
    path: plugins/LWC/lwc.db
    host: localhost
    database: lwc
    username: root
    password:
    prefix:

What did I do wrong?

 

Is there an error when starting? (what is it if so?)

Are there errors in the console? MySQL seems to be working fine for me and a few other people I've spoken with on IRC

 

Oh I will give you it.

 

This is MySQL use. CPU usage fluctuates 20-60% with 0 users online (usually 0-4% with 0 users online).
+ Version:v3.01
CONSOLE: + Engine:MySQL
CONSOLE: + Date:Wed Jun 08 12:01:13 EST 2011
CONSOLE: + Time:26 seconds
CONSOLE: + Players:0
CONSOLE: + Protections:1
CONSOLE: + Cache:1/10000
CONSOLE:
CONSOLE: - Physical database
CONSOLE: + Queries:50502
CONSOLE: + Average:1942.3846153846155 /second
CONSOLE:
CONSOLE: - Memory database
CONSOLE: + Queries:4
CONSOLE: + Average:0.15384615384615385 /second

EDIT: I also noticed while using SQlite, it didn't lag as bad as MySQL (which produced "can't keep up messages".), but it would still fluctuate from 0-30% CPU... (not producing "can't keep up" messages )

 

Yes shownotices is set to True, and showmynotices is set to false.
Now users are not annoyed anymore with the "you" message, but i the admin cannot see who owns a door when i open it, it just opens. (I must use /cinfo)

 

Code:

19:00:18 [INFO] LWC     Loaded 125 locale strings (0 overrides)
19:00:18 [INFO] LWC     Using Permissions API...
19:00:18 [INFO] LWC     Loading MySQL
19:00:18 [SEVERE] java.lang.NullPointerException
19:00:18 [SEVERE]       at java.util.Hashtable.put(Unknown Source)
19:00:18 [SEVERE]       at com.griefcraft.sql.Database.connect(Unknown Source)
19:00:18 [SEVERE]       at com.griefcraft.lwc.LWC.load(Unknown Source)
19:00:18 [SEVERE]       at com.griefcraft.lwc.LWCPlugin.onEnable(Unknown Source)

19:00:18 [SEVERE]       at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlug
in.java:125)
19:00:18 [SEVERE]       at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(
JavaPluginLoader.java:750)
19:00:18 [SEVERE]       at org.bukkit.plugin.SimplePluginManager.enablePlugin(Si
mplePluginManager.java:253)
19:00:18 [SEVERE]       at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftSe
rver.java:134)
19:00:18 [SEVERE]       at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftS
erver.java:112)
19:00:18 [SEVERE]       at org.bukkit.craftbukkit.CraftServer.reload(CraftServer
.java:339)
19:00:18 [SEVERE]       at org.bukkit.command.SimpleCommandMap$ReloadCommand.exe
cute(SimpleCommandMap.java:247)
19:00:18 [SEVERE]       at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCo
mmandMap.java:128)
19:00:18 [SEVERE]       at org.bukkit.craftbukkit.CraftServer.dispatchCommand(Cr
aftServer.java:273)
19:00:18 [SEVERE]       at net.minecraft.server.MinecraftServer.b(MinecraftServe
r.java:430)
19:00:18 [SEVERE]       at net.minecraft.server.MinecraftServer.h(MinecraftServe
r.java:415)
19:00:18 [SEVERE]       at net.minecraft.server.MinecraftServer.run(MinecraftSer
ver.java:311)
19:00:18 [SEVERE]       at net.minecraft.server.ThreadServerApplication.run(Sour
ceFile:422)
19:00:18 [INFO] Patcher ######################################################
19:00:18 [INFO] Patcher ######################################################
19:00:18 [INFO] Patcher SQLite to MySQL conversion required
19:00:18 [INFO] Patcher Loading SQLite
19:00:18 [INFO] Patcher SQLite is good to go
19:00:18 [INFO] Patcher #### SEVERE ERROR: Something bad happened when convertin
g the database (Oops!)
19:00:18 [SEVERE] java.lang.NullPointerException
19:00:18 [SEVERE]       at com.griefcraft.migration.MySQLPost200.checkDatabaseCo
nversion(Unknown Source)
19:00:18 [SEVERE]       at com.griefcraft.lwc.LWC.load(Unknown Source)
19:00:18 [SEVERE]       at com.griefcraft.lwc.LWCPlugin.onEnable(Unknown Source)

19:00:18 [SEVERE]       at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlug
in.java:125)
19:00:18 [SEVERE]       at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(
JavaPluginLoader.java:750)
19:00:18 [SEVERE]       at org.bukkit.plugin.SimplePluginManager.enablePlugin(Si
mplePluginManager.java:253)
19:00:18 [SEVERE]       at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftSe
rver.java:134)
19:00:18 [SEVERE]       at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftS
erver.java:112)
19:00:18 [SEVERE]       at org.bukkit.craftbukkit.CraftServer.reload(CraftServer
.java:339)
19:00:18 [SEVERE]       at org.bukkit.command.SimpleCommandMap$ReloadCommand.exe
cute(SimpleCommandMap.java:247)
19:00:18 [SEVERE]       at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCo
mmandMap.java:128)
19:00:18 [SEVERE]       at org.bukkit.craftbukkit.CraftServer.dispatchCommand(Cr
aftServer.java:273)
19:00:18 [SEVERE]       at net.minecraft.server.MinecraftServer.b(MinecraftServe
r.java:430)
19:00:18 [SEVERE]       at net.minecraft.server.MinecraftServer.h(MinecraftServe
r.java:415)
19:00:18 [SEVERE]       at net.minecraft.server.MinecraftServer.run(MinecraftSer
ver.java:311)
19:00:18 [SEVERE]       at net.minecraft.server.ThreadServerApplication.run(Sour
ceFile:422)
19:00:18 [SEVERE] Error occurred while enabling LWC v3.01 (Is it up to date?): n
ull
java.lang.NullPointerException
        at com.griefcraft.migration.MySQLPost200.checkDatabaseConversion(Unknown
 Source)
        at com.griefcraft.lwc.LWC.load(Unknown Source)
        at com.griefcraft.lwc.LWCPlugin.onEnable(Unknown Source)
        at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:125)
        at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader
.java:750)
        at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManage
r.java:253)
        at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:134)
        at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:112)
        at org.bukkit.craftbukkit.CraftServer.reload(CraftServer.java:339)
        at org.bukkit.command.SimpleCommandMap$ReloadCommand.execute(SimpleComma
ndMap.java:247)
        at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:12
8)
        at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:2
73)
        at net.minecraft.server.MinecraftServer.b(MinecraftServer.java:430)
        at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:415)
        at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:311)
        at net.minecraft.server.ThreadServerApplication.run(SourceFile:422)

 

OH!!.. I found a problem...
It seems LWC is clashing with Essentials plugin... :S

 

Is your password set? I assumed you had only blanked it out -- if it really is blank, try:

Code:

password: ''

Interesting, are you using a lot of Redstone repeaters/gates?

 

Mmmm.. I don't think so O_O
Ok.. Nevermind, its not Essentials. Sorry :S ~ Seems to have a problem by itself...

 

LWC-Iconomy.jar download link?

 

Hi just updated to newest version, and added the ability to lock the trap doors, but seems to have a problem.

When you right click it does like it should and closes and gives you the Lock message, but when you left click on it to open it opens, tells you its locked, then does not close for a while. it will let you walk into the trapdoor, but ejects you a second later, and sometimes keeps glitching you ontop of the trapdoor. Hope that makes since.

I just wanted to let you know about this, or if you already know and possibly have a solution for it.

Bukkit 818
LWC 3.01

Thanks,
Andrew