Lwc error message

Whenever I place a chest or furnace, or try locking something I get the following error.

[LWC] Internal error. Notify an admin immediatly.
:PLAYER_INTERACT

Happens to other players too. Locked stuff is still locked.

FSCarver wrote:Whenever I place a chest or furnace, or try locking something I get the following error.

[LWC] Internal error. Notify an admin immediatly.
:PLAYER_INTERACT

Happens to other players too. Locked stuff is still locked.

Well I really have no idea. I could reinstall LWC but all chests would need to be relocked.

HeyLookoverthere wrote:

FSCarver wrote:Whenever I place a chest or furnace, or try locking something I get the following error.

[LWC] Internal error. Notify an admin immediatly.
:PLAYER_INTERACT

Happens to other players too. Locked stuff is still locked.

Well I really have no idea. I could reinstall LWC but all chests would need to be relocked.

If locked chests are remaining locked then the database is probably fine, sounds more like the plugin itself. Was anything else updated before this started? Are any errors showing up in the log?

Well I just updated LWC so lets so if that fixed it.

Still happening. Did an update from within LWC, then did a plugin reload, still can't lock stuff. I'll go check their dev site, see if anyone else is having issues.

sirrus86 wrote:Still happening. Did an update from within LWC, then did a plugin reload, still can't lock stuff. I'll go check their dev site, see if anyone else is having issues.

the only other thing I did recently that I can think of is update to the newest recommended bukkit build.

heylookoverthere wrote:the only other thing I did recently that I can think of is update to the newest recommended bukkit build.

Actually I think that's the culprit. The newest LWC is made for that version, but from what Carver told me this started after Bukkit was updated, not after LWC was updated. My guess is either the newest RB isn't passing events properly, or LWC's author totally screwed up somehow. In any case, I wouldn't remove the LWC protection database; the issue right now is adding new protections, old ones still work fine.