×

To be able to write in the forum you need to authenticate. Meanwhile it's read-only.

Re: Checker request for GC6WFA4 (not published)

[Resolved] Checker request for GC6WFA4 (not published)
January 07, 2017 03:53AM
Find 50 (or more) of the oldest 100 (non-archived) caches in Minnesota. It would be nice if the checker gave people the number of caches they currently have found for this challenge.
Re: Checker request for GC6WFA4 (not published)
January 07, 2017 04:44AM
Here is the link to a checker http://project-gc.com/Challenges/GC6WFA4/24134
There is however a problem that if I allowe archived cache finds in the challenge, the checker only recognized a limited number of active caches. The reason is the large number of archived caches.
Maybe the script writer can have a look at this problem.
In the mean time I produced a checker where archived caches are excluded but there might be a problem that the reviewer does not accept this.
Re: Checker request for GC6WFA4 (not published)
January 07, 2017 04:56AM
Thank you very much for the speedy reply. I was thinking of not including archived caches so I am hoping this will be acceptable to the reviewer.
Thanks again.
Re: Checker request for GC6WFA4 (not published)
January 07, 2017 07:30PM
In my experience reviewers will insist of archived caches being included - the rules say past finds must count. What you could do is rephrase the challenge to find 50 caches hidden on or before the current 100th oldest cache. Though that may need Target to fix his script (or another script be used).
Re: Checker request for GC6WFA4 (not published)
January 07, 2017 07:42PM
The problem is that the API for oldest caches in can max give a result of 100 caches.
Re: Checker request for GC6WFA4 (not published)
January 07, 2017 07:45PM
That works, you can exclude archived caches from the api call, look at the hidden date of the 100th and then accept any cache with a date <= to that.
Re: Checker request for GC6WFA4 (not published)
January 07, 2017 07:48PM
That only works for today but not in the futher. We want a checker which is maintenance free.
Re: Checker request for GC6WFA4 (not published)
January 07, 2017 07:53PM
I don't follow your logic there. Each time the checker runs it calculates the current list of 100 oldest active caches, any cache (archived or not) older than the 100th active oldest will count towards the challenge - as caches get archived the date will gradually move forward.
Re: Checker request for GC6WFA4 (not published)
January 20, 2017 05:45AM
Yes, Mole125 is correct, The reviewer will not accept the checker without including archived caches. Plus, there appears to be some problems with the checker approving people with less than 50 caches found. It would seem like the checker could include archived caches that were placed before the "current" 100th cache date.

Here are the reviewer concerns:

1) Currently, the checker's output is 50% (a percent is not allowed) rather than the 'number' 50 of 100 as specified in the requirement.

2) The checker does not include past finds on archived caches. The checker output needs to include that. I realize you make mention in the description about archived caches, but a positive qualification needs to come from the checker.

3) There appears to be some error on the checker, as some users show to be qualified with less than 50 finds. Here are some examples:

For King Boreas-
> You have found all the top 43 caches
The list is the status as of 2017-01-17 14:05 servertime (CET)
# gccode Visitdate Name
1 GC9FF 2000-11-05 Alvin's Phone Line
2 GC296 2001-02-13 2005-09-10 Woodlands Hollow
3 GC752 2001-04-20 River Pirate Cache
4 GC82E 2001-04-28 2004-11-24 Checkerboard

For bsteeboy-
> You have found 32 of the top 49
Missing cacheches are in red

> The checkers can only check the current toplist.
If you were fulfilled it when you logged it in the past you might get a does not today.
Your log may have been correct but it cant be checked by this checker
On some challenges you when you accept it make a list and compare to that list. If you have done it you might fulfill the logging requirements right now but the checker can´t know that.
It is like if you make a new list right now. That is accepted on most challenges.
Please check the cache listing for the rules.

> # gccode Visitdate Name
1 GC9FF 2000-11-05 Alvin's Phone Line
2 GC296 2001-02-13 Woodlands Hollow
3 GC752 2001-04-20 River Pirate Cache
4 GC82E 2001-04-28 Checkerboard
5 GC9CF 2001-05-18 Oxbow
6 GCF7F 2001-07-08 2002-01-11 Triple "C"
7 GC1196 2001-07-19 2001-12-30 "wilderness park" rcps

For Grey Wolf and Wild Rice-
> You have found all the top 49 caches
The list is the status as of 2017-01-17 14:15 servertime (CET)
# gccode Visitdate Name
1 GC9FF 2000-11-05 2012-08-25 Alvin's Phone Line
2 GC296 2001-02-13 2011-10-19 Woodlands Hollow
3 GC752 2001-04-20 River Pirate Cache
4 GC82E 2001-04-28 2008-03-17 Checkerboard

There appears to be some error on the checker output that needs to be corrected.
Re: Checker request for GC6WFA4 (not published)
January 20, 2017 05:55AM
For the corrections we need the assistance of the script writer, Target. Without his input I can't change the situation on the archived caches. I hope that Target has time to look into the matter.
Re: Checker request for GC6WFA4 (not published)
February 23, 2017 01:04PM
The API is changed to allow for a 1000 archived caches which have solved the problem for the checker

Please test it
Re: Checker request for GC6WFA4 (not published)
February 27, 2017 11:41PM
The checker works great and the reviewer was happy with the results.....My cache was published.
Thank you for all your work on this checker.
Sorry, only registered users may post in this forum.

Click here to login