I'm having a bit of trouble with chest locking. I got a chest locked at one point and then destroyed it. Now when ever I try to make a new one it says I've exceed the limit on locked chests, even when I haven't spawned any chests.
did you/someone else make a limit of 0 on you/your group?
No, but there is a limit of 1.
I'm guessing that it thinks I still have that chest even though it's been deleted. Is there anyway I can clear all my locked chests?
I'm not sure if you're implying this uses a lot of CPU. In all the tests I've done and even on my live server I haven't noticed any cpu problems (I don't use something like quadbillion core 128GB memory, more or less the box is something average and can handle my players plus another 30+ if it were to come to that).
Are you sure it wasn't because of another plugin spiking cpu or even the server itself? at the time you checked
Quote from SystemsLock »
Quote from Hidendra »
Quote from SystemsLock »
I'm having a bit of trouble with chest locking. I got a chest locked at one point and then destroyed it. Now when ever I try to make a new one it says I've exceed the limit on locked chests, even when I haven't spawned any chests.
did you/someone else make a limit of 0 on you/your group?
No, but there is a limit of 1.
I'm guessing that it thinks I still have that chest even though it's been deleted. Is there anyway I can clear all my locked chests?
Fixed in the next update I believe.
Quote from PigmenResearcher »
Quote from Hidendra »
Quote from Miixxu »
Pointless if just destroying the chest makes it empty its contents.
Users not able to access the chest can't destroy it--but no mod prevents creepers,etc from just blowing it up. As long as creepers can't get to the chest, it's safe
So, What About Tnt?
Tnt can still blow it up, sadly. If and when hMod supports stuff like that (preventing a block from being blown up), it would gladly be added. Come to think of it, it would actually be very easy to add the hook.
ps 1.30 will be out later on today, AC: B came out 2 days ago so I haven't gotten around to releasing 1.20, and I'll be adding onto it
call me crazy but we did it for like 3 hours.. We could never figure out what the lag was with 20+ online... We got none stop cpu spikes.. Then when we disabled LWC it ran again and has never lagged besides auto save. Then when I enable it again it spikes again.
I know it might sound odd but it is something wrong maybe a threading conflict?
call me crazy but we did it for like 3 hours.. We could never figure out what the lag was with 20+ online... We got none stop cpu spikes.. Then when we disabled LWC it ran again and has never lagged besides auto save. Then when I enable it again it spikes again.
I know it might sound odd but it is something wrong maybe a threading conflict?
The plugin doesn't use any threads at all. It is only "live" when someone uses a command/opens a chest/chest updates are sent. Only one connection is ever created (which is when the plugin is started). I wouldn't call it a connection, though, because it doesn't connect to a service
The first suspect is the reads are slow and hogging cpu. I made a quick test in the plugin to try. The 2000 or so chests in the database are completely randomly generated.
Looks normal. CPU was normal, too. About the same as minecraft normally uses. That's ~ 1.1ms per query.
But of course, that's hypothetically speaking. in your case, you have a much larger server so there's I guess more factors. Each chest update to players in the area (which is more often than not) requires 1-3 queries depending on the chest type per player. That shouldn't be a problem considering how fast queries are.
But, if people are constantly creating chests all the time and causing the physical database to be updated (freeing a chest, registering a chest, adding a limit/rights, etc), then that COULD be a problem, if it were done constantly to the point it would be noticeable.
How many chests do you have, anyway? Not that a lot would a problem (it shouldn't, really. sqlite shouldn't have problems with millions of rows), just curious. You can see it when the plugin starts unless you already know
[*:2btzbj7y]Some more sql optimization
[*:2btzbj7y]Several bug fixes, including clean deletion of chests when a protected chest is removed.
[*:2btzbj7y]/lwc info has been extended to anyone. To non chest admins, lwc admins + mods, it will only show the owner and type of the chest (private, public, password)
[*:2btzbj7y]LWC Mods can now view+modify any chest
[*:2btzbj7y]/lwc persist - enable commands to persist after one action, ie /lwc info or /lwc create
[*:2btzbj7y]Aliases! These need not be added to player's commands, it will look for the original
[*:2btzbj7y]/cpublic - /lwc create public
[*:2btzbj7y]/cpassword <Password> - /lwc create password <Password>
[*:2btzbj7y]/cprivate - /lwc create private
[*:2btzbj7y]/cinfo - /lwc info
[*:2btzbj7y]more to come! These are not yet showed publicly in the help message (type just /lwc as always to see it)
(i type /lwc modify Khalysto and click on the chest)
Registered rights for Khalysto: [Player]
<immibis> Ok, now can you see the cobble?
<Khalysto> No.
Edit: apparently it's because they were protected by Cuboid. I don't know if it's possible to make LWC override Cuboid, but if it is, that would be very good.
(i type /lwc modify Khalysto and click on the chest)
Registered rights for Khalysto: [Player]
<immibis> Ok, now can you see the cobble?
<Khalysto> No.
Edit: apparently it's because they were protected by Cuboid. I don't know if it's possible to make LWC override Cuboid, but if it is, that would be very good.
You can select only the chest square (right click with shovel, close chest, right click again) and protect to anyone, ie /protect g:default. Now it will work, and LWC will prevent the chest from being destroyed as if it were protected
Kind of forgot to update this thread! Fear not, LWC is currently at 1.32!
1.32
[*:ftefolxp]LWC Mods now cannot view or modify chests that are owned by LWC Admins
[*:ftefolxp]performance tweaks, code optimization, some removal
[*:ftefolxp]bug fixes, I can't remember any significant ones at this moment
1.31
[*:ftefolxp]Changed Hook priority for BLOCK_CREATED, BLOCK_DESTROYED, COMPLEX_BLOCK_CHANGE and COMPLEX_BLOCK_SEND to Medium
First and foremost, LWC's source is now freely available and downloads are moved to Github. I think I got git down pat now!
Secondly, plenty of bugs that were noticeable before are now fixed. The help messages for various LWC commands are now much more helpful and less vague.
TNT and Creepers now do not blow up chests. Sad creeper may be even more sadder now
1.34
[*:2lvu3kiu]Source and downloads moved to Github: https://github.com/Hidendra/LWC/
[*:2lvu3kiu]Creepers + TNT no longer blow up chests
[*:2lvu3kiu]Help via commands is now a lot more informative
[*:2lvu3kiu]Bug fixes. Some include protections not working (COMMAND itself, protections worked 100%) all of the time, are now fixed
[*:2lvu3kiu]LWC Mods could not open a passworded chest owned by an admin (if they knew the password). Now fixed
> /lwc create private
Chest type: PRIVATE
Left click your chest to complete the locking process
{left clicks on chest}
Registered chest lock.
> /lwc info
Left click a chest to see information about it
{left clicks on same chest}
Chest is unregistered
> /lwc create private
Chest type: PRIVATE
Left click your chest to complete the locking process
{left clicks on chest}
Registered chest lock.
> /lwc info
Left click a chest to see information about it
{left clicks on same chest}
Chest is unregistered
I just tried the same commands you did and it seemed to work for me.
Are there any errors in the console? Does the folder minecraft is in have correct permissions (writable)? i.e. lwc.db
Are there any errors in the console?[/qoute]
Not that I noticed, I can have another look tonight...
Does the folder minecraft is in have correct permissions (writable)? i.e. lwc.db
Yes, lwc.db exists/got created and entries were even created in it.
Try out 1.35, it includes a few bug fixes that may have addressed your issue.
1.35 includes a converter for Chest Protect. If you have a suggestion for another plugin to add a converter for, pm me.
Chest Protect is 100% conversion, only lockedChests.txt is required.
To use this, you can do 1 of two things: (for both, install LWC as you normally would)
[*:2n9prbiz]SSH/CMD into the plugins directory. Execute: java -cp LWC.jar CPConverter
[*:2n9prbiz]In-game as an LWC admin. Execute: /lwc convert chestprotect
No, but there is a limit of 1.
I'm guessing that it thinks I still have that chest even though it's been deleted. Is there anyway I can clear all my locked chests?
check cpu usage
/disableplugin LWC
check cpu usage.
Check out my Let's Play Series:
You should look into some of the other plugins your running...between hey0, sessionprotect and lwc my CPU usage hasn't changed (animals/mobs disabled)
I'm not sure if you're implying this uses a lot of CPU. In all the tests I've done and even on my live server I haven't noticed any cpu problems (I don't use something like quadbillion core 128GB memory, more or less the box is something average and can handle my players plus another 30+ if it were to come to that).
Are you sure it wasn't because of another plugin spiking cpu or even the server itself? at the time you checked
Fixed in the next update I believe.
Tnt can still blow it up, sadly. If and when hMod supports stuff like that (preventing a block from being blown up), it would gladly be added. Come to think of it, it would actually be very easy to add the hook.
ps 1.30 will be out later on today, AC: B came out 2 days ago so I haven't gotten around to releasing 1.20, and I'll be adding onto it
I know it might sound odd but it is something wrong maybe a threading conflict?
Check out my Let's Play Series:
The plugin doesn't use any threads at all. It is only "live" when someone uses a command/opens a chest/chest updates are sent. Only one connection is ever created (which is when the plugin is started). I wouldn't call it a connection, though, because it doesn't connect to a service
The first suspect is the reads are slow and hogging cpu. I made a quick test in the plugin to try. The 2000 or so chests in the database are completely randomly generated.
Looks normal. CPU was normal, too. About the same as minecraft normally uses. That's ~ 1.1ms per query.
But of course, that's hypothetically speaking. in your case, you have a much larger server so there's I guess more factors. Each chest update to players in the area (which is more often than not) requires 1-3 queries depending on the chest type per player. That shouldn't be a problem considering how fast queries are.
But, if people are constantly creating chests all the time and causing the physical database to be updated (freeing a chest, registering a chest, adding a limit/rights, etc), then that COULD be a problem, if it were done constantly to the point it would be noticeable.
How many chests do you have, anyway? Not that a lot would a problem (it shouldn't, really. sqlite shouldn't have problems with millions of rows), just curious. You can see it when the plugin starts unless you already know
1.3
[*:2btzbj7y]Some more sql optimization
[*:2btzbj7y]Several bug fixes, including clean deletion of chests when a protected chest is removed.
[*:2btzbj7y]/lwc info has been extended to anyone. To non chest admins, lwc admins + mods, it will only show the owner and type of the chest (private, public, password)
[*:2btzbj7y]LWC Mods can now view+modify any chest
[*:2btzbj7y]/lwc persist - enable commands to persist after one action, ie /lwc info or /lwc create
[*:2btzbj7y]Aliases! These need not be added to player's commands, it will look for the original
[*:2btzbj7y]/cpublic - /lwc create public
[*:2btzbj7y]/cpassword <Password> - /lwc create password <Password>
[*:2btzbj7y]/cprivate - /lwc create private
[*:2btzbj7y]/cinfo - /lwc info
[*:2btzbj7y]more to come! These are not yet showed publicly in the help message (type just /lwc as always to see it)
Yup. it's not plain text so if you're trying to view it manually you'll need something to view it (on linux, sqlite3 lwc.db)
Edit: apparently it's because they were protected by Cuboid. I don't know if it's possible to make LWC override Cuboid, but if it is, that would be very good.
You can select only the chest square (right click with shovel, close chest, right click again) and protect to anyone, ie /protect g:default. Now it will work, and LWC will prevent the chest from being destroyed as if it were protected
Kind of forgot to update this thread! Fear not, LWC is currently at 1.32!
1.32
[*:ftefolxp]LWC Mods now cannot view or modify chests that are owned by LWC Admins
[*:ftefolxp]performance tweaks, code optimization, some removal
[*:ftefolxp]bug fixes, I can't remember any significant ones at this moment
1.31
[*:ftefolxp]Changed Hook priority for BLOCK_CREATED, BLOCK_DESTROYED, COMPLEX_BLOCK_CHANGE and COMPLEX_BLOCK_SEND to Medium
[*:1c6zg7pq]Important security fix for permissions when removing chests
Edit: Please just answer this, and dont delete it.
Minecraftin' since indef. Haven't missed a patch since.
First and foremost, LWC's source is now freely available and downloads are moved to Github. I think I got git down pat now!
Secondly, plenty of bugs that were noticeable before are now fixed. The help messages for various LWC commands are now much more helpful and less vague.
TNT and Creepers now do not blow up chests. Sad creeper may be even more sadder now
1.34
[*:2lvu3kiu]Source and downloads moved to Github: https://github.com/Hidendra/LWC/
[*:2lvu3kiu]Creepers + TNT no longer blow up chests
[*:2lvu3kiu]Help via commands is now a lot more informative
[*:2lvu3kiu]Bug fixes. Some include protections not working (COMMAND itself, protections worked 100%) all of the time, are now fixed
[*:2lvu3kiu]LWC Mods could not open a passworded chest owned by an admin (if they knew the password). Now fixed
enjoy
ps, new download link: https://github.com/downloads/Hidendra/LWC/LWC.jar
> /lwc create private
Chest type: PRIVATE
Left click your chest to complete the locking process
{left clicks on chest}
Registered chest lock.
> /lwc info
Left click a chest to see information about it
{left clicks on same chest}
Chest is unregistered
I just tried the same commands you did and it seemed to work for me.
Are there any errors in the console? Does the folder minecraft is in have correct permissions (writable)? i.e. lwc.db
Yes, lwc.db exists/got created and entries were even created in it.
Try out 1.35, it includes a few bug fixes that may have addressed your issue.
1.35 includes a converter for Chest Protect. If you have a suggestion for another plugin to add a converter for, pm me.
Chest Protect is 100% conversion, only lockedChests.txt is required.
To use this, you can do 1 of two things: (for both, install LWC as you normally would)
[*:2n9prbiz]SSH/CMD into the plugins directory. Execute: java -cp LWC.jar CPConverter
[*:2n9prbiz]In-game as an LWC admin. Execute: /lwc convert chestprotect
1.35
[*:2n9prbiz]Chest Protect converter
[*:2n9prbiz]bug fixes
I have the same problem where I lock a chest, try to view info & it shows as unregistered. Using 1.3.5
=Khalysto=