Challenge checker - Revision history

4523550: /* Challenge Checker image */ spelling

2024-04-26T19:51:54Z

Challenge Checker image: spelling

← Older revision		Revision as of 19:51, 26 April 2024
Line 22:		Line 22:
	Below the challenge difficulty is a red circle for challenges were the saved result for the authenticated user is not fulfilled. For challenges that the user have ran the checker and fulfilled the challenge it is a green checkmark, the green checkmark can be a false positive in cases were the user has ran the checker previously but since lost their qualifications. If the user has found the challenge the result is replaced by an emoji.		Below the challenge difficulty is a red circle for challenges were the saved result for the authenticated user is not fulfilled. For challenges that the user have ran the checker and fulfilled the challenge it is a green checkmark, the green checkmark can be a false positive in cases were the user has ran the checker previously but since lost their qualifications. If the user has found the challenge the result is replaced by an emoji.

	To the right are the number of times the checker has been ran with a "fulfilled" or "not fulfilled" result. There are anti-spam measurements applied to ~~this~~ counters but it should not be viewed as number of people that have completed the challenge since both the green and red counters can increase multiple times by the same account.		To the right are the number of times the checker has been ran with a "fulfilled" or "not fulfilled" result. There are anti-spam measurements applied to these counters but it should not be viewed as number of people that have completed the challenge since both the green and red counters can increase multiple times by the same account.

	== Checker Requests ==		== Checker Requests ==

3305483: Grammar

2023-09-27T12:09:23Z

Grammar

← Older revision		Revision as of 12:09, 27 September 2023
Line 33:		Line 33:
	Visit [https://project-gc.com/Home/FAQ#3082063764 Project-GC's FAQ] to find answers to many of the most common questions.		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~~ ==		== Related paid membership features ==
	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.		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.

4523550: added example image with emoji

2023-09-27T12:03:50Z

added example image with emoji

← Older revision		Revision as of 12:03, 27 September 2023
Line 15:		Line 15:


	[[File:62346.png]] [[File:70522.png]]		[[File:62346.png]] [[File:70522.png]] [[File:68127.png]]

4523550: Added one more example + info about false positives under challenge checker image

2023-09-27T12:01:22Z

Added one more example + info about false positives under challenge checker image

← Older revision		Revision as of 12:01, 27 September 2023
Line 15:		Line 15:


	[[File:62346.png]]		[[File:62346.png]] [[File:70522.png]]


	In the top left corner is an icon of a skull and crossbones with a number, this is the calculated [[challenge difficulty]].		In the top left corner is an icon of a skull and crossbones with a number, this is the calculated [[challenge difficulty]].

	Below the challenge difficulty is a red circle for challenges were the saved result for the authenticated user is "not fulfilled". For challenges that the user have ran the checker and fulfilled the challenge it is a green checkmark. If the user has found the challenge the result is replaced by an emoji.		Below the challenge difficulty is a red circle for challenges were the saved result for the authenticated user is not fulfilled. For challenges that the user have ran the checker and fulfilled the challenge it is a green checkmark, the green checkmark can be a false positive in cases were the user has ran the checker previously but since lost their qualifications. If the user has found the challenge the result is replaced by an emoji.

	To the right are the number of times the checker has been ran with a "fulfilled" or "not fulfilled" result. There are anti-spam measurements applied to this counters but it should not be viewed as number of people that have completed the challenge since both the green and red counters can increase multiple times by the same account.		To the right are the number of times the checker has been ran with a "fulfilled" or "not fulfilled" result. There are anti-spam measurements applied to this counters but it should not be viewed as number of people that have completed the challenge since both the green and red counters can increase multiple times by the same account.

4523550: Added info about the challenge checker image. Probably needs to be reworded by somebody with better English.

2023-09-27T11:35:51Z

Added info about the challenge checker image. Probably needs to be reworded by somebody with better English.

← Older revision		Revision as of 11:35, 27 September 2023
Line 10:		Line 10:

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

			==Challenge Checker image==
			It is preferred to link the challenge checker with the supplied image since it contains extra information for the users. An example of such an image can be seen below. The image linked in the wiki are static due to technical reasons, the images on cache pages are not and will be updated with current numbers automatically.


			[[File:62346.png]]


			In the top left corner is an icon of a skull and crossbones with a number, this is the calculated [[challenge difficulty]].

			Below the challenge difficulty is a red circle for challenges were the saved result for the authenticated user is "not fulfilled". For challenges that the user have ran the checker and fulfilled the challenge it is a green checkmark. If the user has found the challenge the result is replaced by an emoji.

			To the right are the number of times the checker has been ran with a "fulfilled" or "not fulfilled" result. There are anti-spam measurements applied to this counters but it should not be viewed as number of people that have completed the challenge since both the green and red counters can increase multiple times by the same account.

	== Checker Requests ==		== Checker Requests ==

4523550: Undo revision 1245 by 4523550 (talk) Some sort of bug apparently added lots of text that I had previously removed?

2022-05-04T16:38:34Z

Undo revision 1245 by 4523550 (talk) Some sort of bug apparently added lots of text that I had previously removed?

← Older revision		Revision as of 16:38, 4 May 2022
Line 1:		Line 1:
	== What is it? ==		== 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.		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. More general information about challenge caches is available in the article [[challenge cache]]s, for example information about [[Challenge cache#Challenge Exceptions\|challenge exceptions]].

	== How does it work? ==		== 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 a cache on 365 calendar days. A tag associates one or more scripts with a specific challenge cache, and defines (customizes) ~~things like~~ cache type, quantity~~, region or what is needed to make~~ a script match the challenge cache.		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 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.		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]]		Project-GC also calculates how difficult a challenge is, more information at: [[Challenge difficulty]]

	== Checker Requests ==		== 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~~ to read the READ FIRST-post before posting a request.		Challenge checkers are created by volunteers and can be requested in the [https://project-gc.com/forum/list?8 Checker request forums], it is important to read the READ FIRST-post before posting a request.

			==Disabled checkers==
			Project-GC has a system for disabling the challenge checker if the cache lacks the Challenge-attribute, this is because the challenge-attribute is mandatory per the guidelines.

	== FAQ ==		== FAQ ==
	Visit [https://project-gc.com/Home/FAQ#3082063764 Project-GC's FAQ] to find answers to many of the most common questions.~~<!--The information should of course be moved/duplicated to the wiki.-->~~		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 ==		== Related paid membership feature ==
Line 26:		Line 29:
	== Tools ==		== 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.		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 ==		== Notes ==

4523550: Removed the part about "a script checking for 100 mysterys" since my understanding is that this would be a _tag_ and not a _script_.

2021-01-29T23:12:58Z

Removed the part about "a script checking for 100 mysterys" since my understanding is that this would be a _tag_ and not a _script_.

← Older revision		Revision as of 23:12, 29 January 2021
Line 1:		Line 1:
	== What is it? ==		== 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~~. More general information about challenge caches is available in the article [[challenge cache]]s, for example information about [[Challenge cache#Challenge Exceptions\|challenge exceptions]]~~.		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? ==		== 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.		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 a cache on 365 calendar days. A tag associates one or more scripts with a specific challenge cache, and defines (customizes) things like cache type, quantity, region or what is needed to make a script 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 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.		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]]		Project-GC also calculates how difficult a challenge is, more information at: [[Challenge difficulty]]

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

	~~==Disabled checkers==~~
	~~Project-GC has a system for disabling the challenge checker if the cache lacks the Challenge-attribute, this is because the challenge-attribute is mandatory per the guidelines~~.

	== FAQ ==		== FAQ ==
	Visit [https://project-gc.com/Home/FAQ#3082063764 Project-GC's FAQ] to find answers to many of the most common questions.		Visit [https://project-gc.com/Home/FAQ#3082063764 Project-GC's FAQ] to find answers to many of the most common questions.<!--The information should of course be moved/duplicated to the wiki.-->

	== Related paid membership feature ==		== Related paid membership feature ==
Line 29:		Line 26:
	== Tools ==		== 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.		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 ==		== Notes ==

4523550: Removed info about challenge exceptions and added info about disabled checkers.

2021-01-27T19:22:42Z

Removed info about challenge exceptions and added info about disabled checkers.

← Older revision		Revision as of 19:22, 27 January 2021
Line 1:		Line 1:
	== What is it? ==		== 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.		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. More general information about challenge caches is available in the article [[challenge cache]]s, for example information about [[Challenge cache#Challenge Exceptions\|challenge exceptions]].

	== How does it work? ==		== How does it work? ==
Line 12:		Line 12:

	== Checker Requests ==		== 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.		Challenge checkers are created by volunteers and can be requested in the [https://project-gc.com/forum/list?8 Checker request forums], it is important to read the READ FIRST-post before posting a request.

			==Disabled checkers==
			Project-GC has a system for disabling the challenge checker if the cache lacks the Challenge-attribute, this is because the challenge-attribute is mandatory per the guidelines.

	== FAQ ==		== FAQ ==
Line 26:		Line 29:
	== Tools ==		== 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.		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 ==		== Notes ==

4022761: Edited for clarity

2020-12-30T04:33:56Z

Edited for clarity

← Older revision		Revision as of 04:33, 30 December 2020
Line 1:		Line 1:
	== What is it? ==		== What is it? ==
	A '''Challenge checker''' ~~is a piece of~~ program code that ~~will check~~ if a user ~~have completed~~ 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.		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? ==		== How does it work? ==
	A challenge checker consists of two parts: a challenge checker script and a tag. The ~~checker~~ script is a piece of program code written in the programming language Lua. 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~~. The tag links a checker script, a challenge cache, and (optionally) a set of parameters for the checker script. This means that the same ~~checker~~ 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.		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]]		Project-GC also calculates how difficult a challenge is, more information at: [[Challenge difficulty]]

212719: Addition of Checker exception paragraph

2020-12-28T17:27:05Z

Addition of Checker exception paragraph

@@ Line 22: / Line 22: @@
 == 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.
 == Notes ==