Version 1.0.2 is out.
Unfortunately, I don't think this will do much to help the people who have the issue where nothing but the time is being updated - I have added some extra checks and made a small change to some of the queries, but nothing I really think will do much to fix it yet.
I'm sorry to not have this one figured out yet, but it's really difficult to bug hunt when I can't recreate the issue on any of my machines. I have gone through the SQL queries a ton of times to try to find something there, but I really can't see why it wouldn't work as well for everyone as it does for me.
I'm curious to know if anyone who uses this against an alias is also having this problem? If you have this problem and are using a single sn, then please try making an alias with only that sn in it in HM and see if it works when using the alias in ValueCheck instead.
It works fine for me against both an alias and a single sn, but it is possible that's because I've always had at least one alias present.
Anyway, the reason for the new version is that I've added a new menu item under the 'Settings' menu called 'High point activation settings...'. This will allow setting a minimum high point that has to be reached before the 'loss from high point' alert is activated.
For instance, if you have the 'lost from high point' target set to 100 bb and the 'minimum high point reached' set to 50, you will not be alerted by this alert unless you've made 50 bb before you lose 100 bb from that high point.