Challenge caches

The mechanism

Most caches ask one thing: find the container, sign the log.

A challenge cache adds a second requirement that has nothing to do with the container. Before you may log it online, your record has to satisfy some condition: caches found in every county of a region, a find on every date of the calendar, a set of difficulty and terrain combinations, a total in a particular category.

The physical hide is usually easy and usually incidental. The cache is the condition; the container is the ceremony at the end.

Why the argument is sharper here

Every complaint about find counts applies to challenges with the volume turned up.

If you think the count is a side effect that has been over-promoted, a cache type that makes your statistics a prerequisite is that promotion made official. The number is no longer something you happen to accumulate; it is the lock on the door.

The defence is genuinely strong, though. A challenge gives shape to caching that would otherwise be aimless. “Find a cache in every county” turns a vague intention into a project with a route, a progression and an end point, and the caching it produces is often the opposite of volume caching, because it sends people to places they had no other reason to visit.

Both things are true. A challenge can push somebody toward grinding out numbers, and it can push somebody toward a county they would never otherwise have driven to. Usually the same challenge does both to different people.

What the rule changes fixed

Challenge caches went through a significant tightening of the guidelines, and the changes addressed real problems rather than imagined ones.

Verifiability. Conditions that could not be checked against a public record produced disputes with no way to resolve them. Requiring verifiability removed a whole category of argument.

Arbitrary conditions. Some early challenges required things that had nothing to do with caching skill or effort, and were essentially a private preference imposed on strangers.

Checkers. The single biggest improvement to the experience. Before them, qualifying meant counting your own record by hand, believing you had met the condition, driving out and finding you had miscounted a county. A checker turns that into a click.

The result is a narrower, more defensible cache type. Fewer challenges exist; the ones that do are mostly ones you can confirm you qualify for before setting off.

How to think about them

If you enjoy long projects with an eventual physical destination, challenges are among the best things the hobby offers. They produce trips that would not otherwise happen.

If the statistics are not what you are here for, they are simply a cache type you can skip, and the number that can be skipped is small.

The one position that does not survive scrutiny is that they are illegitimate. A community that records what everyone finds was always going to invent games about the record. Challenges are the formalised version of something that would happen informally regardless, which is a reasonable argument for keeping them visible and governed rather than driving them into private lists.

Check before you drive

The single practical piece of advice about challenge caches is to run the checker before setting off, every time, even when you are certain.

Qualification conditions are easy to misread. A county you crossed but did not log in, a date you found two caches on but recorded as one, a difficulty rating that changed after your find. The checker knows; your memory does not.

Why these are the hardest cache type to maintain

A challenge cache carries an obligation ordinary caches do not: somebody has to verify that each finder actually met the requirement.

That work falls on the owner, it never stops, and it scales with how popular the cache becomes. An owner who set an interesting condition in 2013 and has since drifted away from the hobby leaves a cache that people are still finding and nobody is checking, at which point the requirement quietly becomes decorative and the cache becomes an ordinary hide with an unusual listing.

The mechanism that fixes this is the automated checker, and its arrival changed the type more than any rule did. A checker verifies the condition in seconds, applies it identically to everybody, and keeps working after the owner has stopped paying attention. Challenge caches with a working checker survive; those without one depend entirely on whether their owner is still there.

The requirements that age worst

Some conditions are stable and some quietly stop being satisfiable, and the difference is not obvious when the cache is set.

Requirements built on cache types that were later retired become impossible for anyone who was not caching at the time. Nobody can now find their first virtual if none are being published. Requirements tied to a specific region’s cache density shift as caches are archived. Requirements referencing a statistic a particular tool used to produce break when the tool does.

The durable ones are built from things that remain available to a new cacher who starts tomorrow — which is not how the hobby began, since the first hides had no statistics to build on at all: counts, dates, difficulty and terrain combinations, container sizes. A well-set challenge should be hard for everybody and possible for anybody, and the test is whether somebody beginning today could still complete it in principle.