Milestones on project-gc vs. geocaching.com?

Question

On geocaching.com we have worked towards certain milestones, and we also have "locked" them. For some reason it's not the same milestones that appear here on project-gc. We are working towards a couple of challenges, and the challenge checkers will probably check our statistics here, yes?!?

Is there anything we have done wrong or is it just how it is supposed to be?

Answer 1

Milestones are difficult to control on PGC because rather then Geocaching.com, where caches are administered in order of uploading, PCG get the found caches from Groundspeak in one dump per day and the sequencing can be off in that way.

The only way to control this at PCG is to do only the milestone cache that day

Answer 2

Hi, we have a different milestones since Labcaches involved at project GC.

On geocaching.com we locked all milestones.

Answer 3

There will always be this discrepency - locking your milestones on Geocaching.com was done because sometimes if you found (as I have) you had double logged a cache way back when ( bad logs on PGC helped identify these) then these milestones suddenly changed their position. So in order to 'protect' the list that appears on GC.com they allowed the locking process. Older challenges relevant to this (a variety of different icons for the milestones comes to mind) and pre checkers would refer to that list on GC.com as the qualifying list

Technically it does mean that those locked milestones would be incorrect.
Project.GC would list them correctly for the reasons mentioned above.

Any pgc checker would probably fail you (unless you happen to be lucky and manage to qualify despite any changes) as it would search your caching history as it is and not the list on GC.com

You have done nothing wrong - unfortunately that is just the way it is

ps. I am aware of some cachers who have NOT adjusted any of their double logging in order that these lists are not affected ;-)