Updated Challenge Cache Rules
Posted: Tue 2012-03-13, 08:18:13
Found out this morning yesterday groundspeak updated the rules & restrictions for placing challenge-based geocaches:
1.Challenge cache owners must demonstrate that there are sufficient available caches to meet the challenge at the time of publication.
-This appears related to the existing restriction on challenge caches that require logging disabled/archived caches, and to the new restriction on challenge caches that require past accomplishments.
2.The challenge criteria [...] must be verifiable through information on the Geocaching.com website. Challenge caches relying solely on third-party software for verification will not be published. Cache owners will need to ensure that geocachers can verify that they have completed the cache requirements without compromising their privacy.
-This appears to be a clarification of the original restriction that requirements be "logistically viable".
3.A challenge cache needs to appeal to, and be attainable by, a reasonable number of geocachers. A challenge cache may not specifically exclude any segment of geocachers. If a geocacher is required to alter their caching style or habits, such as avoiding a particular cache type to attain a specific percentage or average, the cache will not be published.
-Others have already pointed out that wheelchair users are a "segment of geocachers". Thus, the phrase "may not specifically exclude any segment of geocachers" could be interpreted as banning challenge caches that wheelchair users cannot complete (e.g., Fizzy Challenges that require high-terrain caches). However, I don't think that's the intent, based on the context of the following sentence.
4.The requirements for meeting the challenge should be succinct and easy to explain, follow, and document. A lengthy list of "rules" would be sufficient reason for a challenge cache to not be published.
-In other words, the challenge should be completing the requirements, not understanding the requirements.
5.A Challenge cache must avoid undue restrictions. Specifically: [...] Challenge caches cannot include restrictions based on 'date found'; caches found before the challenge cache publication date can count towards the achievement of the challenge.
-In other words, challenge caches cannot "level the playing field" by making current geocachers start over.
6.Challenge caches need to be attainable at any time while the cache is active. A cache that requires "100 multi-caches found in 2011" would not be publishable, as would not be attainable by someone new to the game.
-Just as you can't penalize experienced geocachers, you can't penalize new geocachers.
7.One should not have to 'give up' finding other caches to achieve a challenge cache's requirements. To state that "10% of your find count needs to be Attended Logs" would require the geocacher to stop finding other types of caches and could affect their overall enjoyment of the game.
-This appears to be a clarification of the original restriction on requirements based on "non-accomplishments".
8.If a challenge cache is submitted within an area where a similar challenge cache already exists, then it will need to have a unique list of qualifying criteria (geocaches, waymarks, etc.).
-In other words, just as you can't "stack" events, you can't "stack" challenge caches.
1.Challenge cache owners must demonstrate that there are sufficient available caches to meet the challenge at the time of publication.
-This appears related to the existing restriction on challenge caches that require logging disabled/archived caches, and to the new restriction on challenge caches that require past accomplishments.
2.The challenge criteria [...] must be verifiable through information on the Geocaching.com website. Challenge caches relying solely on third-party software for verification will not be published. Cache owners will need to ensure that geocachers can verify that they have completed the cache requirements without compromising their privacy.
-This appears to be a clarification of the original restriction that requirements be "logistically viable".
3.A challenge cache needs to appeal to, and be attainable by, a reasonable number of geocachers. A challenge cache may not specifically exclude any segment of geocachers. If a geocacher is required to alter their caching style or habits, such as avoiding a particular cache type to attain a specific percentage or average, the cache will not be published.
-Others have already pointed out that wheelchair users are a "segment of geocachers". Thus, the phrase "may not specifically exclude any segment of geocachers" could be interpreted as banning challenge caches that wheelchair users cannot complete (e.g., Fizzy Challenges that require high-terrain caches). However, I don't think that's the intent, based on the context of the following sentence.
4.The requirements for meeting the challenge should be succinct and easy to explain, follow, and document. A lengthy list of "rules" would be sufficient reason for a challenge cache to not be published.
-In other words, the challenge should be completing the requirements, not understanding the requirements.
5.A Challenge cache must avoid undue restrictions. Specifically: [...] Challenge caches cannot include restrictions based on 'date found'; caches found before the challenge cache publication date can count towards the achievement of the challenge.
-In other words, challenge caches cannot "level the playing field" by making current geocachers start over.
6.Challenge caches need to be attainable at any time while the cache is active. A cache that requires "100 multi-caches found in 2011" would not be publishable, as would not be attainable by someone new to the game.
-Just as you can't penalize experienced geocachers, you can't penalize new geocachers.
7.One should not have to 'give up' finding other caches to achieve a challenge cache's requirements. To state that "10% of your find count needs to be Attended Logs" would require the geocacher to stop finding other types of caches and could affect their overall enjoyment of the game.
-This appears to be a clarification of the original restriction on requirements based on "non-accomplishments".
8.If a challenge cache is submitted within an area where a similar challenge cache already exists, then it will need to have a unique list of qualifying criteria (geocaches, waymarks, etc.).
-In other words, just as you can't "stack" events, you can't "stack" challenge caches.