[Resolved] Checker request for GC81HCB - cloned one seems buggy

I got my 600th cache today (12/20/18) and am trying to create a challenge cache for others who've also gotten at least 600 caches (mine is allowed to be their 600th). Placed a container and wrote up a page (https://www.geocaching.com/geocache/GC81HCB_picky-challenge-lunch-after-600) and ran into problems with getting a working checker.

Found an existing checker for a general (any cache, anywhere, any type) 600-cache challenge and cloned it and added the link to my proposed cache's page. It shows up fine.

My checker (https://project-gc.com/Challenges/GC81HCB/38999):
"{
"limit": 600
}
Tag comment: you have logged 600 caches (or more) Cloned from tag 10696"

Thinking the limit should be changed to 599, as then interested finders can log this one as #600.

Thing is, when I run the existing checker against myself it both notes my 600 finds AND says I don't qualify, so I think the existing checker is buggy.

The checker's output (for mine, as linked here; it was similar for the original checker):
"
frumiousb does not fulfill challenge ? (GC81HCB) according to https://project-gc.com/Challenges/GC81HCB/38999

Note that Project-GC has a latency of about 24-36 hours. For more details, read the FAQ.

Script executed in 0.055 seconds. Peak memory usage: 482 kB

Script output
User has 600 finds (600 needed)."

Thanks.

Also, I have some programming background and would be interested in being able to edit/modify challenge scripts myself.

Here's an alternative checker:

https://project-gc.com/Challenges/GC81HCB/39010

Please test and let us know if it's more suitable. Note that Lab caches won't be counted in either of these checkers since Project-GC doesn't provide that detail to scripts (and it's still a semi grey area).

Thanks, both of you. The 600 script does work for me now, probably because pinkunicorn tweaked it overnight. After I contacted them, they checked the script and realized they'd coded it for >600 I/o >=600 as it should have been, and they fixed that.

As for 599 vs. 600 - this is my first challenge cache and I need advice from more experienced folks as to whether I need to go for 599 or 600 for this.

If it was me, I would have used 600. Nice round number. So you'll continue using your original checker? If so, I'll delete the extra one I added.

According to guidelines, one have to meet the requirements BEFORE they log the cache on-line. If you strictly follow the guideline, there is no reason to count the challenge itself to the total number. I would go with the 600 as it is now and forget the guideline :)

I would definitely prefer to keep it simple and I do like the round number. I will go with the 600 checker and see what my local reviewer thinks.

Thank you, everyone!

Quote

[frumiousb](https://www.geocaching.com/profile/?u=frumiousb) has used [Project-GC](https://project-gc.com/Challenges/GC81HCB/38999 "Project-GC Challenge Checker") to see if they qualified for this challenge and they did.

User has 600 finds (600 needed).

Maybe your last find was not recorded yet. There is a delay and now it seems to work. But you need a different checker if your limit is 599 instead of 600.