Challenge cache

From Project-GC
Revision as of 23:20, 29 December 2020 by Pleu (4523550) (talk | contribs) (Challenge Exceptions: added example of why a cache might get automatically added)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

What is it?

A challenge cache is a cache that requires the player to fulfill a geocaching goal before they are allowed to log the cache as found. Challenge caches have to be mystery caches and have the challenge attribute, they also must have the word Challenge in the cache name. Per the guidelines every challenge cache published after April 21, 2015 has to have a challenge checker.

More information about challenge caches can be found in the challenge cache guidelines.[1]

Challenge caches at Project-GC

By default, all geocaches with the Challenge-attribute will be considered as challenge caches. However, an attribute could be placed on a non-challenge cache by accident or with malicious intent to "improve" the statistics. A cache owner could also forget to add said attribute to a challenge cache. The reviewer should review for incorrect use of the challenge attribute but they might miss this during review or the cache owner might add or remove the attribute after the cache is published.

To solve this problem Project-GC uses a list of Challenge exceptions to make sure that the statistics regarding Challenge caches is as correct as possible. Project-GC also has a system for disabling the challenge checker if the cache lacks the Challenge-attribute.

Challenge Exceptions

The Challenge Exceptions-system is a list of caches that need to be checked manually by volunteers from the Project-GC-community to see if they are challenge caches or not. The process is simple, the volunteer checks the cache description to see if the cache is a challenge or not and then uses an 'up-vote' to say that it is a challenge or a 'down-vote' to say that it is not a challenge. The vote should be placed based on if the Geocache requires the finder to do something before/when logging it and not if it is a 'good' challenge or if it complies with the current guidelines.

Only geocaches with a confidence score of at least 35% will be be considered as an exception, the more homogeneous votes, the higher the confidence. For example 3 homogeneous votes should give a high enough confidence score, while for example 3 up-votes and 1 down-vote will not be enough. There is a forum[2] to discuss special cases and believes related to these exceptions. The forum is readable by everyone, but only those with voting access can write in it.

Caches are added to the exceptions list automatically via a set of criteria (e.g. having the challenge-attribute but not having a checker or the other way around for example) but can also be added manually, the easiest way to suggest exceptions is via the dedicated thread in Project-GC's Community support system.

Related tools

Challenge checkers are the main Project-GC tool related to challenge caches.

The Map of challenge caches is a tool where users with a paid membership can show challenge caches on a map with different filtering options.

Related statistics

Top Found Challenges is a top list of the number of challenge caches users has found.

The Achiever in BadgeGen is awarded based on number of challenge caches found.


Notes

  1. Challenge cache guidelines at Geocaching.com
  2. Challenge checker exceptions at Project-GC.com.