×

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

Change History

Moderators will move threads from "Checker requests" into this forum after a while when it has been decided that the challenge checker isn't possible for one or another reason. The threads should not be moved right away. The challenge owner should have a chance to adjust his requirements if that helps.

Message: Re: GC7DF2K - 161m Radius Challenge

Changed By: arisoft
Change Date: October 11, 2017 10:13AM

Re: GC7DF2K - 161m Radius Challenge
> "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 should reverse this requirement by not allowing any finds from this area to qualify :)

> To write the script, you would only have to need
> the set of coordinates of the cache?

Checker can get current coordinates automatically after the cache is published.

> 1. "Radius" challenges are not acceptable under
> the updated guidelines (10. Source of Criteria:
> "Based upon user-defined polygons, radius, etc")

Yes

> 2. If my local reviewer wont publish this because
> they deem it to be a 'Challenge cache' that
> doesn't meet guidelines, I will try presenting it
> as a funny mystery cache. It would still be nice
> to have a 'checker' on the page.

I tried this once myself. I found that reviewers are so annoyed to review challenges that thay they do not want to see anything which even remotely resembles a challenge unless forced by headquarters. You may find this difficult to achieve but I would like to see the result anyway.

If your cache is not a real challenge (word challenge missing from the title) the checker will be automatically disabled. It is still possible to create a tool, which is not directly linked to the cache, but I do not know if there is any guideline at PGC which allows or disallows this kind of use. (If someone has answer to this question, [url=https://project-gc.com/forum/read?9,12399]please reply here[/url])

Original Message

Author: arisoft
Date: October 11, 2017 09:11AM

Re: GC7DF2K - 161m Radius Challenge
> "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 should reverse this requirement by not allowing any finds from this area to qualify :)

> To write the script, you would only have to need
> the set of coordinates of the cache?

Checker can get current coordinates automatically after the cache is published.

> 1. "Radius" challenges are not acceptable under
> the updated guidelines (10. Source of Criteria:
> "Based upon user-defined polygons, radius, etc")

Yes

> 2. If my local reviewer wont publish this because
> they deem it to be a 'Challenge cache' that
> doesn't meet guidelines, I will try presenting it
> as a funny mystery cache. It would still be nice
> to have a 'checker' on the page.

I tried this once myself. I found that reviewers are so annoyed to review challenges that thay do not want to see anything which even remotely resembles a challenge unless forced by headquarters. You may find this difficult to achieve but I would like to see the result anyway.

If your cache is not a real challenge (word challenge missing from the title) the checker will be automatically disabled. It is still possible to create a tool, which is not directly linked to the cache, but I do not know if there is any guideline at PGC which allows or disallows this kind of use. (If someone has answer to this question, [url=https://project-gc.com/forum/read?9,12399]please reply here[/url])