[Az-Geocaching] Claiming a find when you can't..

[Brian Casteel]

The way I see it is simple.  It's no different than logging a find on a 
cache you hide.  The ultimate effect becomes the cacher cheating themselves 
and padding their numbers for a variety of reasons.  If you're close enough 
to see the cache, get the friggin' thing and sign the logbook.  If the area 
is protected by a rattlesnake, call it a day and try again later.  If bees 
are present, either be stupid and take your chances, or...come back another 
day.  You may have 'found' the cache, but without physical contact and 
putting pen (or pencil) to paper and validating your visit, you haven't 
'FOUND' the cache.  Virtuals/locationless clearly have different rules, but 
those are understood and don't apply in the case of traditional caches. 
Replacing a cache that you can't find, and subsequently logging a find is 
really no different than logging a find on your own cache, except for the 
fact that you don't own it.  It's one thing if you're replacing a cache for 
someone in the event that it is KNOWN to be MIA, but I don't think you 
should really be logging a find in that case.  Replacing a cache for someone 
suggests having already found it, because you should know where it was 
originally hidden.

Brian
Team A.I.


----- Original Message ----- 
From: "ShadowAce" <hunting at shakabruddah.com>
To: "AZ Geocaching list" <listserv at azgeocaching.com>
Sent: Saturday, November 27, 2004 10:12 PM
Subject: [Az-Geocaching] Claiming a find when you can't..


>I am just wondering if anyone else has feedback on this for me?
>
> This weekend while finding caches we found a container dropped in place by
> another cacher. The reason was they could not find the container at the
> cache site so they left one, signed the logs and claim a find..
>
> Now we come along alittle later and find the container and check but it
> only has the signature of the person leaving it.. We keep searching and
> within 3 minutes find the REAL cache container.
>
> Am I the only one who thinks this is lame? What about the next cacher that
> comes by and logs the wrong one?
>
> Well, evil me, I took the replacement container home with me. I have also
> emailed the cache owner to tell them that there cache is safe and sound. 
> The
> other cacher is just in too much of a hurry to have done a complete 
> search..
>
>
> Am I wrong to find this as one of the most lame movements cachers can do?
>
> ____________________________________________________________
> Az-Geocaching mailing list listserv at azgeocaching.com
> To edit your setting, subscribe or unsubscribe visit:
> http://listserv.azgeocaching.com/mailman/listinfo/az-geocaching
>
> Arizona's Geocaching Resource
> http://www.azgeocaching.com
>