Finds by hidden month: current month is 1 as soon as month starts.

Question

In the "Finds by hidden month"-table as soon as a new month starts the table shows 1 find for the new month, even if you have not found any cache yet hidden in the new month. E.g. my table already shows 1 find for June 2016 although I have a couple of days backlog in logging my finds and certainly have not found, let alone logged yet any cache hidden in June 2016.

As far as I can see, at the start of the new month 1 is deducted from the statistics for the penultimate month (i.e. currently May 2016).

As this cannot be feature is has to be a bug, right?

Answer 1

The easiest way to find out is the Map Compare tool:
http://project-gc.com/Tools/MapCompare?profile_name=k%2Bgw%2Ba&onefound=on&hidden_fromyyyy=2016&hidden_frommm=6&hidden_fromdd=1&submit=Filter

For some reason, the cache http://coord.info/GC45CC shows hiddend date on the 1.6.2016 ... you should ask a owner why it is like that.

Comments

Perfect and quick answer. Thanks a lot! I had completely forgotten about this moving cache. The owner places it every month at a different of those monuments updating the "hidden date". Which also explains why this phenomenon occurs every month – that’s why I thought it was a bug. But it isn’t. Sorry and thanks for the explanation!