Project-GC - User contributions [en]

Challenge checker

2020-12-30T04:33:56Z

4022761: Edited for clarity

== What is it? ==
A '''Challenge checker''' uses program code that checks if a user has fullfilled the requirements of a [[challenge cache]]. Per the guidelines of Geocaching.com a [[challenge cache]] published after April 21, 2015, must include a link to a web-based challenge checker. <ref>[https://www.geocaching.com/help/index.php?pg=kb.chapter&id=127&pgid=206 Guidelines for Challenge caches] at Geocaching.com's Help Center.</ref> So far Project-GC is the only allowed challenge checker.

== How does it work? ==
A challenge checker consists of two parts: a challenge checker script and a tag. The script is a piece of program code written in the programming language Lua. The script checks for a certain condition, for example a script can check if the user has found 100 mystery caches. Another script can check if a user found a cache on 365 calendar days. A tag associates one or more scripts with a specific challenge cache, and defines (customizes) cache type and quantity for a script to match the challenge cache.

The tag links a checker script, a challenge cache, and (optionally) a set of parameters for the checker script. This means that the same script can be used both for a challenge that requires the user to have found 100 mystery caches and a challenge that requires the user to have found 1000 traditional caches, since the cache type and quantity of finds required is specified in the tag.

The same checker script can be used for multiple challenge caches (For instance, most calendar challenges are handled by the same checker script). The tag is what makes this possible.

Project-GC also calculates how difficult a challenge is, more information at: [[Challenge difficulty]]

== Checker Requests ==
Challenge checkers are created by volunteers and can be requested in the [https://project-gc.com/forum/list?8 Checker request forums], make sure you read the READ FIRST-post before posting your request.

== FAQ ==
Visit [https://project-gc.com/Home/FAQ#3082063764 Project-GC's FAQ] to find answers to many of the most common questions.

== Related paid membership feature ==
If a user have a [[paid membership]] Project-GC automatically runs challenge checkers for the user in the background. See the article about [[Auto-challenge-checkers]] for more information.

With a paid membership there is no limit on how many challenge checkers you can run. Non paying users are only allowed to run 10 challenge checkers per 24 hours. The limit is a ''rolling rate limit''.

The [[Map of challenge caches]] is a tool that can show the [[challenge cache]]s of the world on a map. Different filters can be applied.

== Tools ==
The checker script system can be used to create different tools to check for statistics that are not otherwise available at the site. See [[Tools in the checker system]] for more information.

== Challenge Exceptions ==
By default all geocaches with the Challenge attribute will be considered as challenge caches. Exceptions to that rule can be added here [https://project-gc.com/Tools/Challenges?challengeExceptions Challenge Exceptions] Either by adding additional challenges, or by adding geocaches that shouldn't be listed as challenges. A group of cachers who have moderation rights vote on any caches that appear on the list.
A moderation team have been voting on caches for several years but when the introduction of the 'challenge cache attribute' was introduced it had been hoped that correct use of that would eliminate the need for moderation - however it soon became evident that moderation was still required and so this exception list continues to be used.

Though this list can be viewed by all, only the moderators have access to vote - The list is sorted on a confidence score, the more homogeneous votes, the higher the confidence. The order in the list is only updated on page load. Use the up-arrow to vote that it is a challenge, and the down-arrow if it's not a challenge.
The following was advice for moderators regarding voting consideration - Note that your vote shall not be based on today's Challenge guidelines but rather on the fact that the Geocache requires you to do something before/when logging it. You shall not take into consideration if it's a good challenge or not, neither if you like it as a challenge.

Only geocaches with a confidence score of at least 35% will be be considered as an exception. Three homogeneous votes should be enough for that, while for example 3 up-votes and 1 down-vote won't.

There is a forum available to discuss special cases and believes related to these exceptions. [https://project-gc.com/forum/list?12 Checker Exceptions Forum] The forum is readable by everyone, but only those with voting access can write in it.

== Notes ==
<references />

[[Category:Site Info]]

Project-GC

2020-12-30T04:16:50Z

4022761: Clarifications and legibility.

[https://project-gc.com/ Project-GC] is a public website available to all geocachers wherever they are located in the world and where internet access is available. Project-GC provides tools as well as statistics that geocachers can access and use. Project-GC is the one-stop-shopping and go-to place for challenge checkers, charts, [[top list]]s, [[statbar]]s, comparisons, achievements and maps [[:Category:Tools|tools]]. Project-GC uses the official [https://apidevelopers.geocaching.com/ Geocaching.com API].

== Some of our current projects ==
*[[Geocaching-country to OSM-ID mappings]] - Join this project about getting better maps in the [[Profile Stats]].
*[[Main Page |Our wiki]]! - Join us in expanding the wiki, more info at the [[Welcome]]-page.

== News ==
For news about Project-GC the [https://www.facebook.com/ProjectGC/ Facebook-page] is generally the quickest way. If you do not have a Facebook-account you can still see Facebook-pages since they are public, just close the popup and continue to read.

Most news will end up in the [https://project-gc.com/Home/News News-section] at the main site as well at a later point though.

==History==
Project-GC started with [[Magnus Månsson]] (also known as '[[User:3305483|magma1447]]') getting an idea about providing himself and some friends with helpful tools for [[Geocaching]]. After some time Magnus was asked to make local statistics for the region in Sweden where he lived, a lot of people started showing interest in the project and the project grew to something much bigger that required a lot of time. A year later the first people were invited to start using it via a post about it on a local forum, after that it spread via word of mouth.

In the beginning of May 2012 the use of the [https://apidevelopers.geocaching.com/ Geocaching.com API] (formerly Geocaching Live) could be announced. Project-GC started with focus on Europe but from October 2012 there was full support for both Europe and North America, and soon after that the whole world was covered.

[[Category:Site Info]]

DiscoverTrackables

2020-12-30T04:00:34Z

4022761: Clarifying text for legibility.

[https://project-gc.com/Tools/DiscoverTrackables Discover Trackables] is a tool that helps a Project-GC user to log many [[trackable]]s as discovered at once. The idea is that during a geocaching event the user composes a list of Trackable IDs that they have seen or discovered. Then they enter all those Trackable ID's as one list into Project-GC and choose the date when the trackables are bulk discovered. Project-GC will then log them as "discovered" using the same log entry for all trackables and the same date. Caution should be exercised since there is no way to delete the logs in bulk. The tool can handle up to 1000 Trackable IDs at once. The IDs can be separated by new line, space, semi colon, comma or the pipe character.

All discovers are made using the [[Geocaching LIVE api]]. The use of the tool must be in compliance with rules set by [[Geocaching HQ]]. For example, using this tool to log lists of trackables where the trackable owner has disagreed to be included could lead to removed access to this tool.

The queue position can increase or decrease based on different factors. For example Project-GC users with a [[paid membership]] are prioritized, therefore users that does not have a paid Project-GC membership might find their queue position increasing at times. There is also a rate-limit of max discovers per minute in the API. Once a user hits that, all affected jobs are postponed by a minute, which could again change the position.

There is also a tab labeled ''History'', in this tab the user can view their earlier discovered batches, including number of discovered trackables, number of errors on the list, the log text and the timestamp of the discovery.

==Paid membership features==
Users with a [[paid membership]] have higher priority in this tool and will get their discovers done before others.

[[Category: Tools]]