Change History

This cache appeared on the challenge exception list - probably because it doesn't have the attribute
I know the CO so messaged him about this and his reply was - [b]this is not a challenge cache[/b]
He put
[i][b]It is, in fact not a challenge cache. Challenge caches must have a
specific challenge which must conform to certain rules that were in place
at the time - not the same strict criteria in place today, but still rules
applied by the reviewer.

So what it really is is a "bluff" puzzle cache where the final coordinates
are actually the same as published. Choosing and completing a challenge is
optional and non-enforcable.[/b][/i]

There is a sentence saying this within the description - though I have said to him it is easily overlooked and to many this will be seen as a challenge cacch
he.

[b]**Update**[/b] upon further discussion the CO has said
"In its current form, cachers treat it as a challenge and that's cool. I guess I'd expect they'd want it to be counted in their stats as a challenge.

However - Officially it's not a challenge cache in Groundspeak's eyes, because the challenge is variable and up to the individual, and also it is not enforceable, The reviewer would not allow it as a challenge at the time of publication and yes the requirement could have been seen to be an ALR - however it was published and has remained ever since. How it is voted on within the exception list will be down to the folk at PGC"

So although this isn't a challenge cache in the COs eyes - the moderators will have to make their own mind up as to whether this is a challenge cache or not.
Noting - there isn't a specific challenge set as criteria for this cache and there is NO requirement to actually set a challenge - finding and signing is all that is required.
For those that do set their own challenge, it can range from 'find a cache' to 'find a cache every day for the next 5 years'
The CO has no issue with whether this ends being voted up or down

This cache appeared on the challenge exception list - probably because it doesn't have the attribute
I know the CO so messaged him about this and his reply was that th- [b]this is [b]not a challenge[ cache/b]
not a challenge cache[/b]
He put
[i][b]It is, in fact not a challenge cache. Challenge caches must have a
specific challenge which must conform to certain rules that were in place
at the time - not the same strict criteria in place today, but still rules
applied by the reviewer.

So what it really is is a "bluff" puzzle cache where the final coordinates
are actually the same as published. Choosing and completing a challenge is
optional and non-enforcable.[/b][/i]

There is a sentence saying this within the description - though I have said to him it is easily overlooked and to many this will be seen as a challenge cacch

[b]**Update**[/b] upon further discussion the CO has said
"In its current form, cachers treat it as a challenge and that's cool. I guess I'd expect they'd want it to be counted in their stats as a challenge.

However - Officially it's not a challenge cache in Groundspeak's eyes, because the challenge is variable and up to the individual, and also it is not enforceable, The reviewer would not allow it as a challenge at the time of publication and yes the requirement could have been seen to be an ALR - however it was published and has remained ever since. How it is voted on within the exception list will be down to the folk at PGC"

So although this isn't a challenge cache in the COs eyes - the moderators will have to make their own mind up as to whether this is a challenge cache or not.
Noting - there isn't a specific challenge set as criteria for this cache and there is NO requirement to actually set a challenge - finding and signing is all that is required.
For those that do set their own challenge, it can range from 'find a cache' to 'find a cache every day for the next 5 years'
The CO has no issue with whether this ends being voted up or down

This cache appeared on the challenge exception list - probably because it doesn't have the attribute
I know the CO so messaged him about this and his reply was that this is [b]not a challenge[ cache/b]
He put
[i][b]It is, in fact not a challenge cache. Challenge caches must have a
specific challenge which must conform to certain rules that were in place
at the time - not the same strict criteria in place today, but still rules
applied by the reviewer.

So what it really is is a "bluff" puzzle cache where the final coordinates
are actually the same as published. Choosing and completing a challenge is
optional and non-enforcable.[/b][/i]

There is a sentence saying this within the description - though I have said to him it is easily overlooked and to many this will be seen as a challenge cache

We are still in discussions about this and this could go either way (challenge cache or not) - can I ask that this is not voted on (I know I have but that shouldn't sway much) until a definitive answer is obtainedThere is a sentence saying this within the description - though I have said to him it is easily overlooked and to many this will be seen as a challenge cacch

[b]**Update**[/b] upon further discussion the CO has said
"In its current form, cachers treat it as a challenge and that's cool. I guess I'd expect they'd want it to be counted in their stats as a challenge.

However - Officially it's not a challenge cache in Groundspeak's eyes, because the challenge is variable and up to the individual, and also it is not enforceable, The reviewer would not allow it as a challenge at the time of publication and yes the requirement could have been seen to be an ALR - however it was published and has remained ever since. How it is voted on within the exception list will be down to the folk at PGC"

So although this isn't a challenge cache in the COs eyes - the moderators will have to make their own mind up as to whether this is a challenge cache or not.
Noting - there isn't a specific challenge set as criteria for this cache and there is NO requirement to actually set a challenge - finding and signing is all that is required.
For those that do set their own challenge, it can range from 'find a cache' to 'find a cache every day for the next 5 years'
The CO has no issue with whether this ends being voted up or down

This cache appeared on the challenge exception list - probably because it doesn't have the attribute
I know the CO so messaged him about this and his reply was that this is [b]not a challenge[ cache/b]
He put
[i][b]It is, in fact not a challenge cache. Challenge caches must have a
specific challenge which must conform to certain rules that were in place
at the time - not the same strict criteria in place today, but still rules
applied by the reviewer.

So what it really is is a "bluff" puzzle cache where the final coordinates
are actually the same as published. Choosing and completing a challenge is
optional and non-enforcable.[/b][/i]

There is a sentence saying this within the description - though I have said to him it is easily overlooked and to many this will be seen as a challenge cache

Based on We are still in discussions about this I have downvoted and this ascould go either way (challenge cache or not) - can I ask this CO is saying at this is NOT a challenge cachenot voted on (I know I have but that shouldn't sway much) until a definitive answer is obtained

This cache appeared on the challenge exception list - probably because it doesn't have the attribute
I know the CO so messaged him about this and his reply was that this is [b]not a challenge[ cache/b]
He put
[i][b]It is, in fact not a challenge cache. Challenge caches must have a
specific challenge which must conform to certain rules that were in place
at the time - not the same strict criteria in place today, but still rules
applied by the reviewer.

So what it really is is a "bluff" puzzle cache where the final coordinates
are actually the same as published. Choosing and completing a challenge is
optional and non-enforcable.[/b][/i]

There is a sentence saying this within the description - though I have said to him it is easily overlooked and to many this will be seen as a challenge cache

Based on this I have downvoted this as this CO is saying this is NOT a challenge cache