Chestlogging plugin

Hi everybody!
I've programmed for a few days on my Chestlogging plugin and it works very well right now. It logs the accessed chests by creating a file that is named with the exact location of the chest. Here's a little presentation what a chestlog file looks like with 2 clicks. The text with the // are only Comments and will not displayed in the real logfile.

// Filename:110,71,-110.log (X,Y,Z of the chest)

[CHESTCLICK]
Player: Steven1811
Time: 15:52:17
Date: 3.6.2011
Amount of Itemstacks: 1
Inventory Items:
CHEST,62,2 //Materialname,Amount of the stack,Position in chest (1 is the first position)


[CHESTCLICK]
Player: Steven1811
Time: 15:52:21
Date: 3.6.2011
Amount of Itemstacks: 2
Inventory Items:
CHEST,62,2
DIRT,3,24

Functionality:

• Creating log files of Chests
  

What's planed?

• Rollback the chest inventory to an earlier date
  
• Get access to the log files ingame with a specific item by using a command
  
• Performance improvements
  
• Autodelete old logfiles that is configured in the configuration file
  
• Store the data into an SQL database
  

Please post suggestions for the plugin. I'll put it up on Github and on the bukkit website some days or earlier later.

No. No. No. NO. How can you POSSIBLE think that flatfiles, not to mention the format in which this data is stored, are the way to go for something as incredibly common as chests?

Why not? Whats wrong with the format? Its only text and its easy to read. Or do you only want to access it ingame by using binary files? That would make out a smaller size for the log files but you cant read them without a special programm or a hex editor. So I think a textfile would be the best way to do it.

Performance and space issues. How many chests do you think there are in the world? How many times do you think these are opened or have their contents changes? The sheer amount of flatfiles and their sheer length after just a DAY would cripple the server anytime your plugin would have to look up anything. Granted it wouldn't be quite as bad ye olde BigBrother but damn...

If you're going to do this, it is a good idea to be honest, than for Rana sakes put the data in at the very least a SQLite database. Not only does it make looking for a chest at a specific place/date waaaaay easier but it is also waaaaaaaaaaaaaay faster to do.

Ok i gotta admit thats a good way to put the data into an SQL database. I make then in the configuration.yml file a entry that let you decide in which way the data will be stored. Either in plain text or in a SQL database or both.

LogBlock v1.00final (Jun. 01, 2011)

Works with CraftBukkit recommended build #818, WorldEdit 4.5, Permissions 2.x, BukkitContrib v0.2
Contains BukkitContrib by Afforess

Implemented new commands system
Added "/lb tp"
Added "/lb clearlog"
Moved query at player join (no more kicks)
Implemented full working chest logging
Implemented chest rollback
Added "Are you sure" questions to rollbacks, redos and clearlog commands.
Changed -chest table format (will auto update)
Added hiddenplayers config entry.
Fixed rollback of beds and doors
Extended api

please correct me if im wrong, but doesnt LB do this now ?

Crap. They were quicker than I was. It were released on the 1st June. Thats the reason why I don't know anything about it.

Do you use Afforress' BukkitContrib? It adds new events that help with inventory scanning, chest scanning, etc.

If Logblock already can do chestlogging. I can't see the point of developing it anymore
But thanks patrick for the info. Thats like a thing that I've looked for because Bukkit hasn't implemented so many events right now even despite the fact that some Inventory Event types exists.

Actually with the most recent logblock update we have chest logs. It tells who took what out.