I would love to see the .diff ... I guess I can manually make it. I intended to push my changes to a git repo I made from the original source drop (github.com/phiggins42 d3-lootmonitor) ... I've made a crude visual output window colored by drops and setup a simple socket server thing reporting back to some configurable IP (it just plaintext logs ilvl/type/location of all drops of all people "reporting").
My current version (reporting as 1.0.3d) is http://bit.ly/ViqpG2
I'll update the github repo w/ my code changes, but I want to clean them up some -- VisualStudio (which I've never used before a few days ago) makes a mess in the source tree and I'm sure I've created another .resx not found issue while compiling.
I would _love_ for people to run my version w/ reporting "on" (in settings -> checkbox, host/port should be default to my test machine I setup). It is just a simple echo server logging plaintext so you can change the host/port to anything you want locally if you just want to log your own. I'm collecting numbers for some crude stats to see frequency/etc, and the more the merrier. The color-coded visual output locally is a pretty cool feature for folks running sound-off/windowed, and the remote reporting allows multi-head/multi-machine folks to cat that log somewhere else easily.
update: personal thanks to one random anonymous barbarian running my version. You are a beast wrt to drop rates and the data is invaluable, thanks so much! Also: looks like you get a legendary boot this morning. Hope it roll'ed well.
update: I made a series of charts from the data collected over the last couple of days:
https://img.skitch.com/20120923-82de...kh4nc29717.jpg
It is crude, but I plan to clean this up too and make it realtime/neartime update live against the reported data. Haven't merged the goblin/rewrite changes from 1.0.3 back into my version yet, but plan to doso in coming days.
update: Hijacked a domain I have and threw the quick data up: http://aretheregirlsthere.com/d3loot/ (the root is just a "no." video which I thought appropriate in this context). Source coming. No realtime updates but reloading page will update to most current stats up to the second (processing is happening realtime, but no websockets/polling in page yet).