QuoteThe use case for lab caches has already been set - by geocaching.com. GC treats lab caches as "just another cache" as far as its statistics go, and that is how project-gc should treat them. Lab caches should be considered any time the type of cache is not relevant, such as streaks, caches per country, top finds per day, distance from home, longest slump etc, as this is exactly howby arisoft - Checker news
According to the guidelines: "Restrictions on date of finds used for the challenge are not permitted." I have tried this myself and it did not get accepted this way.by arisoft - ARCHIVE Checker requests (completed)
> answered. We would need to know what use cases > there are, and how the methods are expected to > work. In my case the reason to have labs was to get Groud Speak compatible total number of finds which was needed to the challenge calculations. In that case a separate list of labs would be enough and easy to use. I guess that only the number of labs totally or per day is the most inby arisoft - Checker news
See this another topic https://project-gc.com/forum/read?4,12270by arisoft - Script development
> "To qualify, you must find all caches within 161m > of the posted coordinates." Area is not allowed criteria unless it is county etc. > - So basically, everyone satisfies the > requirements, as the 161m proximity is mandatory. Players should pass the checker before they are allowed to log the cache as found. This practically means that no one will qualify. You sby arisoft - ARCHIVE Checker requests (impossible)
This script seems to be impossible as there is no definition for a letter. The description is contradictory as there is example of "chinese letters" which are actually logograms, not letters and sometimes letters are called characters. Strictly interpreted, even a space is accepted character because it is not a character between A to Z.by arisoft - ARCHIVE Checker requests (impossible)
This challenge may fall to the category "Restrictions on date of finds used for the challenge are not permitted." Definitely you are using dates but the guideline is just a guideline. I suggest you to consult with your local reviewer about this matter unless there is an another similar challenge published recently.by arisoft - ARCHIVE Checker requests (impossible)
Here it is: https://project-gc.com/Challenges/GC4351B/29177 Quote(https://www.geocaching.com/profile/?u=Alamogul) has used (https://project-gc.com/Challenges/GC4351B/29177 "Project-GC Challenge Checker") to see if he/she qualified for this challenge and he/she did. #1 2003-08-16 GCGDH6 Springtime Park (Traditional Cache) #2 2004-12-27 GCJEGN Pushawalla Power Path #22 (Traditionalby arisoft - ARCHIVE Checker requests (completed)
Limit is now changed to 80. Cache title will be inserted automatically after the challenge is published.by arisoft - ARCHIVE Checker requests (completed)
> If you look at my result here - there are 5 caches in the Bear Hunt series included - is there a way to limit those? Bear Hunt 3- The Gate Bear Hunt 5- The forest Bear Hunt 8- The Scratching Tree Bear Hunt 9-The Mud Bear Hunt 12- The Tunnel If the digits are deleted, it will not change anything in this case. The script should guess that "Bear Hunt" is the criterion, butby arisoft - ARCHIVE Checker requests (impossible)
> The checker link you gave me appears to limit the > series results already but I am happy to go with The current script https://project-gc.com/Challenges/GC4Z33D/16859 does not use the cache name for filtering. Maybe there is something else which limits founds by wrong criteria? Do you have an example? > All I want to avoid is someone finding a series of say 21 caches > whiby arisoft - ARCHIVE Checker requests (impossible)
> It does appear to have the series thing covered - > I would class a series as one where all the caches > where a part of the name was same for all caches - > WWWNLL for example on my qualification, or Bear There must be a better way to filter out series than compare every substring between every cache name. How about comparing only letters, not digits? Then all numbered serieby arisoft - ARCHIVE Checker requests (impossible)
"No more than 3 caches from a series of caches may count towards your total." How do you define "series"?by arisoft - ARCHIVE Checker requests (impossible)
The new script is available here: https://project-gc.com/Challenges/GC2CKEY/29138 Please test whether it is suitable for you.by arisoft - ARCHIVE Checker requests (completed)
This is a duplicate request. There is already checker for this cache https://project-gc.com/Challenges/GC1VE0E/28899by arisoft - ARCHIVE Checker requests (completed)
Easiest way is to add 6 points (1+2+3) to the required score to compensate new virtuals.by arisoft - ARCHIVE Checker requests (completed)
Quote- because there are only 2 old Virtuals in Saarland and I want to exclude the new Virtual Rewards, caches must be placed before 2015 (or this category limited to the two oldest caches) This option is still missing from the script. I'm not sure whether this is a permissible condition. I suggest you to consult with your local reviewer about this matter.by arisoft - ARCHIVE Checker requests (completed)
Here is the checker for testing: https://project-gc.com/Challenges/GC7CT86/29123 The needed score is now 75 points and can be easily adjusted according to your needs.by arisoft - ARCHIVE Checker requests (completed)
I can write a new script for this challenge.by arisoft - ARCHIVE Checker requests (completed)
Hi, I created a modified checker from the previous one for your challenge, so you can try it and the deside what to do. You can find the checker here: https://project-gc.com/Challenges/GC79A81/29009 I made this setup by adjusting parameters only. More detailed configuration is also possible but it takes little more time.by arisoft - ARCHIVE Checker requests (completed)
This IS NOT the checker for your challenge, but an example of an another kind of hiking challenge checker. At least you can check, how easy or difficult your challenge would be and decide what are the limits you want. https://project-gc.com/Challenges/GC70006/28638by arisoft - ARCHIVE Checker requests (completed)
The checker must know the limit for how many is required. Anyway there is also an another problem with guidelines as these cache page elements are not allowed: cache titles, cache owner, GC Codes, publishing Reviewer, or cache page text.by arisoft - ARCHIVE Checker requests (impossible)
I think this is not easy to get around: Not allowed - Specifying any element of a cache page or find count required during a streak.by arisoft - ARCHIVE Checker requests (impossible)
Main problem is that Alberta has only 19 counties in this database and no MDs and special areas. There is no easy way to check those 60 areas which are missing.by arisoft - ARCHIVE Checker requests (impossible)
This way it is possible to keep tags clonable which is the most important advance.by arisoft - Method requests
The first qualified for me ::o and the second did not. I think there is a major problem in the first one.by arisoft - ARCHIVE Checker requests (completed)
Now you can try this checker: https://project-gc.com/Challenges/GC7CCZK/28923 Quote[-Kobold-](https://www.geocaching.com/profile/?u=-Kobold-) has used (https://project-gc.com/Challenges/GC7CCZK/28923 "Project-GC Challenge Checker") to see if he/she qualified for this challenge and he/she did. Elevation 2500 - 5000 m, Needed 10, Finds 16, PASSED Elevation 1750 - 2000 m, Needed 20by arisoft - ARCHIVE Checker requests (completed)
Sorry, this is not allowed for new challenges. According to guidelines, these cache page elements are not allowed: cache titles, cache owner, GC Codes, publishing Reviewer, or cache page text.by arisoft - ARCHIVE Checker requests (impossible)
OK... this is possible to do. Wait a moment...by arisoft - ARCHIVE Checker requests (completed)
Do I understand this correctly? 21 different tests and all must pass. The first is 10 to 19 meters The second is 20 to 29 meters etc... And the last is 210 meters or more. At every level there is some arbitrary number of finds needed to pass.by arisoft - ARCHIVE Checker requests (completed)