Return to Project-GC

Welcome to Project-GC Q&A. Ask questions and get answers from other Project-GC users.

If you get a good answer, click the checkbox on the left to select it as the best answer.

Upvote answers or questions that have helped you.

If you don't get clear answers, edit your question to make it clearer.

Milestones on project-gc vs.

0 votes

On 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?

asked Jan 29, 2018 in Miscellaneous by FREDskorpset (120 points)

3 Answers

0 votes
Milestones are difficult to control on PGC because rather then, 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
answered Jan 29, 2018 by vogelbird (Expert) (50,510 points)
0 votes
Hi, we have a different milestones since Labcaches involved at project GC.

On we locked all milestones.
answered Jan 29, 2018 by The4Hasards (3,150 points)
0 votes
There will always be this discrepency - locking your milestones on 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 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 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

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 ;-)
answered Feb 1, 2018 by Deepdiggingmole (7,570 points)