ChestSearch
Summary
Detect and find hidden chests with (too much) diamond/ore/whatever. Every time the content of a chest is changed, the new content and the player who changed the content of the chests are inserted in a SQLite DB. You can also check how many [item] has a player (in chests).
Version
v0.6 for CB1317
Download the latest recommended build
Features
- Lightweight (plugin triggered only on event)
- Find chests which have more than X items (display World, Coordinates, Player and last edition date)
- Find all chests of a player
- Find the total number of an item stocked by a player
- Multiworld compatible
- Generate a file with the results (Chest ID, coordinates, world, last time used and last user)
- Bukkit Permissions
Dependencies - IMPORTANT
Installation
- Download the latest version and place the .jar file in the 'plugins' directory.
- Restart the server
Commands & Permissions
Use /chestsearch or /csrch
Search
Permission : chestsearch.search (default to op)
Search all chests which have more than X ItemID
/csrch item [itemID] [number]
Example : /csrch item 264 20
> Find chests which have more than 20 diamonds
Search by player
Permission : chestsearch.search (default to op)
Search all chests owned by a player which have more than X ItemID
/csrch player [playername] [itemID] [number]
Example : /csrch player belf 264 20
> Find chests which have more than 20 diamonds and are owned by Belf
Check by player
Permission : chestsearch.check (default to op)
Check how much ItemID has Belf (in chests)
/csrch check [playername] [itemID] [number]
Example : /csrch check belf 264
Find how much Belf has diamond (in chests)
Clear
Permission : chestsearch.clear (default to op)
Clear a chest entry or the whole database
Example : /csrch clear [chestId]
> Remove the chest of the database
Example : /csrch clear all
> Clear the database
Known bugs
- None
TODO
- Chest history access
- Whitelist
- MySQL support
And other things.
Changelog
v0.6 - 15/10/2011
- Updated to CB1317
- Bugfix for Bukkit Permissions
- Changed command alias to /csrch to prevent a conflict with WorldEdit
v0.5 - 06/10/2011
- Updated to CB1185
- Bugfix for compatibility with Lockette
v0.4 - 22/09/2011
- Updated to CB1185
v0.3 - 21/09/2011
- File generator
- Bukkit Permissions support
v0.2 - 31/08/2011
- Bugfix
- Alias changed for command
- New commands
- Search by player (chests and items)
v0.1 (Alpha) - 30/08/2011
- First release
Source
Comments and suggestions are welcome.
NB : Sorry for my poor english, i'm french
Yep defintely need this since there has been alot of dupe bugs latetly on our server and i need to clean up some chests. Also eww to spout dependency.
I'll add to the support: +7 to updating this useful plugin
@aphilosopher Yes, someone must update this incredibly useful plugin. Also remove the Spout dependency. Ewwie.
it would be great for someone to update this plugin so i can get rid of all the duped diamond blocks now spread throughout my server thx to the dupe hacks that bukkit had to patch
have found no other method
I'd also be very interested if you were to pick this up again.
This sounds like an excellent idea, and is exactly what I am missing as an admin.
would love to see this plugin picked back up.
Are you going to update this plugin? I would really like to use it on my server!
@Belfff
Are you going to pickup this plugin again? I would really like to use it.
@LeonPhilips Not a bad idea, but it's not really the purpose of this plugin.
@xclucky Yeah, LWC support is planned
@daraeman date_access is the date of the access of the chest (= the time when the user close the chest) is_last_access is just a little token for the optimization, if =1 it's the last state of the chest stocked.
Hi I'm putting a script together to display the chests and i was wondering what the date_access and is_last_access columns are for in the cs_chests_contents table
@xclucky
Indeed! I need that too!
@Belfff
It would be great if it did link into LWC, because I already had my server since May 2011, so as you can imagine, I already have quite a few chests... I'd offer to help, but I dont know Java... I know some Javascript, but that doesn't get you very far...
Hello! I love your plugin it is just what I need! but I got an Idea for you:
When a Chest is found and you type /chestsearch compass (or something like that) your compass will point to it and ask an teleport request to the chest.
That would be very cool :) If that is to hard to make it is no problem but would be very cool ;)
@Pythros I'm going to debug it for the 1.0.1 R1 :)
@xclucky Yeah, it's the only to keep it lightweight... It's simple, light, and pretty efficient this way. The link to LWC is interesting, to be honest I was waiting to see if it was popular enough to take time and doing this sort of things.
@WillMillerAK In the TODO list, probably on the next update (january)
MySQL support??
I noticed that chests are only searchable when placed "after" the plugin was downloaded. Is there a way you could link them into LWC and when the chest is opened, retrieve the owner from there and store the chest into the database with the appropriate owner? (of course if the chest isn't already added to the database)
If you need me to reword this, please ask.
Btw, your English is pretty good :D
@Belfff
Any update on this?
Still seeing this error in 1337 and now see it when reloading the plugins.
@Belfff
My server is fairly big. I only started using your plugin within a week. I don't know how many people were on at the time it happened as I was away at the time. VirtualShop used to have the same issue and they fixed it on their end. Something about not closing or locking the db if I remember right. On average, we have 10-25 people online at any given time.
@Pythros
Mmmm, this error occured beacause the plugin wasn't able to open the SQLite database. It could be a server problem, i'm going to look into it.
Your server is big ? Is that there was a lot of people online at this moment ?