azxten
11-21-2014, 01:38 AM
The auction tracker at ahungrydot is great and is an inspiration. However I've always wanted to have my own auction data and interface with source available. So I'm making a Project1999 auction tracking and analytics program that can be run by anyone to maintain their own data.
If any coders want to help please drop me a message. Code is available on github. I'm sure its full of bugs. I have not refactored it yet either.
https://github.com/seventeen76/P99Auctions
Currently you can specify an EQ directory and it will read all ".txt" files under EQ\Logs for auctions. Auctions are parsed and written to an sqlite database. It then finds any logs that are actively being written to and begins active monitoring for auctions placing data into the database. Log names and md5 hashes are kept in a separate table to ensure logs are only re-read at launch if the md5 changes.
Plans are to build a frontend interface which allows viewing average item pricing, auction volume, and various other things. The goal is to make a frontend that anyone can use on their home computer. This is why an sqlite database is used. Open to ideas on how to make a lightweight dynamic frontend using this sqlite database without having to install anything. Most server side code like PHP would require the client have software installed since its processed locally.
Long term I'm hoping to implement some kind of data sharing system which would allow merging sqlite databases with either a central repository or group clusters. This would allow multiple people to contribute to a single database.
Example of EQ auction window (left), active auction output (top), sqlite interface (bottom), and code (right):
http://i.imgur.com/LzslBOz.png
If any coders want to help please drop me a message. Code is available on github. I'm sure its full of bugs. I have not refactored it yet either.
https://github.com/seventeen76/P99Auctions
Currently you can specify an EQ directory and it will read all ".txt" files under EQ\Logs for auctions. Auctions are parsed and written to an sqlite database. It then finds any logs that are actively being written to and begins active monitoring for auctions placing data into the database. Log names and md5 hashes are kept in a separate table to ensure logs are only re-read at launch if the md5 changes.
Plans are to build a frontend interface which allows viewing average item pricing, auction volume, and various other things. The goal is to make a frontend that anyone can use on their home computer. This is why an sqlite database is used. Open to ideas on how to make a lightweight dynamic frontend using this sqlite database without having to install anything. Most server side code like PHP would require the client have software installed since its processed locally.
Long term I'm hoping to implement some kind of data sharing system which would allow merging sqlite databases with either a central repository or group clusters. This would allow multiple people to contribute to a single database.
Example of EQ auction window (left), active auction output (top), sqlite interface (bottom), and code (right):
http://i.imgur.com/LzslBOz.png