+FredPhil96 Posted January 30, 2012 Share Posted January 30, 2012 When I logged my 532nd find, it said I had got a favorite point. Are these not supposed to be received every 10 caches or did something change? Please fix. Quote Link to comment
Moun10Bike Posted January 30, 2012 Share Posted January 30, 2012 It's every 10 finds, but events don't count, nor do duplicate finds or finds on your own caches. Also, to avoid gaming of the system, the count of caches needed to reach the next point will not change if you log a cache you have previously logged, even if you have deleted the earlier log. Quote Link to comment
Moun10Bike Posted January 30, 2012 Share Posted January 30, 2012 It looks like the deletion and relogging of your find on http://coord.info/GCM3T1 is the reason for your perceived discrepancy. Quote Link to comment
+FredPhil96 Posted January 30, 2012 Author Share Posted January 30, 2012 Ok. Thanks for the explanation. Is there anyway you could make my next favorite point could come at my 530th cache. It just makes it easier to know when you hit cache #530, 540, 550 etc. Quote Link to comment
+GeoGuy Posted January 31, 2012 Share Posted January 31, 2012 (edited) You can do that yourself by attending a few events. As they don't count for favorite points you can use them to sync your find count with your "number of caches till the next favorite" count. Only downside is that you won't be allowed to attend events once they are in sync, as that will throw of the count again. In other words. Even if they could make it so, the number will be of again the next time you attend an event anyway. Edited January 31, 2012 by GeoGuy Quote Link to comment
+aB5dEglYeS5P Posted January 31, 2012 Share Posted January 31, 2012 If events don't count then I've picked up 4/5 favourite points I shouldn't have... I currently have 2359 finds of which 50 are events (46 regular events plus...) So according to your logic I should have 1+230 favourites and be due the next one in 1 cache time. http://www.geocaching.com/my/default.aspx says: Logs Until Next Favorite Point: 7 Total Favorite Points: 236 I maintain, as previously on UserVoice, that the problem comes from initially logging a find that requires cache-owner confirmation by writing a note and later editing it to a 'found' log. It's a trivial issue but I don't buy the explanation given. Quote Link to comment
+baloo&bd Posted February 1, 2012 Share Posted February 1, 2012 (edited) Nevermind. Math not what it used to be. Edited February 1, 2012 by baloo&bd Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.