Thank you to those of you who are still using CacheStats (I know there are still some of you out there)! Sorry it’s been so long since the last update. This isn’t a large update, but it does fix a couple outstanding issues: Twitter is working again, and Windows 8.1 is now supported. And it adds a few small features: an On this date column in the yearly data table, and calculation of the average D/T of caches per owner. This lets you see who has placed the toughest caches you’ve found. Read on for full details.
Average Difficulty / Terrain per owner
You can see the average D/T rating of caches you’ve found on a per owner basis in two places: in your profile summary, and on the Caches tab when you group by Owner or Placed by. It’s probably most useful to view in the profile summary: click Export to HTML, make sure Per Owner is checked, then click the Preview button. This way, you only see the top 10 owners, and you don’t need to scroll through the list as you do on the Caches tab. The owner of my most difficult finds is Ranger Boy (which was no surprise to me), average difficulty 3.1, average terrain 2.0. How does that compare with your toughest cache hider?
On This Date
The second mini-feature is a new column in the Yearly Data table, called On This Date. This shows your number of finds and days cached on today’s date for each year. I like to to see how I’m doing relative to years past, and this makes it easy to see if I’m ahead or behind the pace of any given year.
Finally, one other small change, the hint is now shown in the Cache description. You can download the latest from the CacheStats page. Hope you enjoy the new features and let me know if there are any other features you’d like to see.
P.S. if the numbers in the On This Date column are incorrect, please download and install again. For about a week I had version on the site that had a bug in the calculation. If you’re unsure, click the About button. It should say version 3.0.11, and the build number should be 5510 or greater. If your build number is 5502, then you have the version that has the bug.