Re: GC6QQ40 February 29 - Leap Year Challenge

I was given a challenge checker for GC6QQ40 which is a new unpublished geocache. Now I do not see the checker on this forum. I was given the following code to be placed on the cache page from Project GC:

<a href="http://project-gc.com/Challenges/GC6QQ40/22528"><img src="http://maxcdn.project-gc.com/Images/Checker/22528"; title="Project-GC Challenge checker" alt="PGC Checker"></a>

Here is what the reviewer (GeoCrater) for geocaching stated:
You have added the link to the challenge checker. However, this links to a generic cache page - not specific to a February 29 challenge. Therefore, running a cache seeker through this challenge would not appear to be effective on your cache. The cache checker needs to be created to be specific to what needs to be checked to qualify for your cache.

Please advise what I need to do or what can be done to remedy the issue. Will the checker be updated once the geocache is published?
Thanks.



Edited 3 time(s). Last edit at 09/04/2016 06:14PM by gjhimages. (view changes)

Here is the latest:
The checker provided is - as you state - a generic checker. A checker specific to finding 29 caches hidden on February 29th will need to be created and added to your cache page.

The checkers need to be created for each individual cache.

GeoCrater

I think the reviewer is mistaken. In any case I have adjusted the printout if a cacher is failing the checker which might have caused some confusion by the reviewer.

The checker is created with a generic script but is specific for your challenge and the checker can only be used for GC6QQ40 February 29 - Leap Year Challenge



Edited 1 time(s). Last edit at 09/04/2016 07:15PM by vogelbird. (view changes)

It might be that the reviewer looked at the script name and thought that the word "Generic" in the script name meant that it wasn't configured for this cache specifically.

I noticed that the cache is published.
If you have the problem again the important part is that the correct GC code is listed where it is now before the the cache name. The name is missing before publication and is added automatically when the cache is published and detected by project-gc.

The confusion is because challenge checkers are two parts. A (often) generic checker script for many caches and a individual configuration tag for a specific checker

The relevant line in the help center is the following and says that the GC code is the important part.

Quote

The GC code on the challenge checker must match the GC code of the associated challenge cache listing.

The old request have been moved to the "ARCHIVE Checker requests (completed)" forum to reduce clutter in this forum