Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

A challenge cache requires that geocachers meet a geocaching-related qualification or series of tasks before finding the cache.
If you are thinking of creating a "challenge cache"“challenge cache”, please keep the following in mind:
1. It is generally considered "bad form" “bad form” to log one's one’s own physical cache.
2. Basing a challenge cache solely on some aspects of geocaching, such as 5 star terrain, may severely limit the number of cachers who can achieve the challenge.
3. Basing a challenge cache on non-accomplishments, such as DNFs, will likely prevent the cache page from being published.
4. Challenge caches may not require the publication of a new cache as a logging requirement.
5. Challenge caches may not require cachers to log caches that are disabled or archived.
6. An individual's attempt to complete a challenge should be independent of the actions of other cachers. A challenge is supposed to recognize the completion of an achievement, rather than the winner of a competition. (FTF's are an unverifiable competition)
7. Requiring cachers to find an explicit list of caches (rather than a broader category of caches) will likely prevent publication of the cache listing.
8. Using a challenge cache to promote one's one’s own caches will likely prevent publication of the cache listing.
9. Challenge cache owners may also be asked to outline a long-term cache maintenance plan as caches involved in the challenge by be archived over time.

A challenge cache requires:
1. Geocaching-related
2. Affirmative (no DNF's DNF’s or days without a find)
3. Reasonably attainable by the hider and a substantial number of other geocachers. This is two fold, 1. there must be local finders that are at least close to making it, and 2. there are enough local caches that make it at least almost possible
4. Logging requirements are logistically viable.

...