Sign in to follow this  
Followers 0

General opinion on new container/"find" etiquette

32 posts in this topic

Posted · Report post

I have a question for you.

 

We adopted a cache from someone that is difficult.  It was obviously intended to be difficult.

 

Lots of people have not found it.  I happened to have been the first person who did find it.

 

Recently I replaced the container because it had gone missing.

 

Now we come to the issue.

 

The other day a group of people "found" it, but they didn't really.  From their logs, they put out a new container, not finding the container that I had just put out.  I intend to go out and remove their container.  My question is "should I disallow their 'finds' because they didn't actually find the cache--they put out a new container"?  In their defense, there were individuals in the group that had found it before, and the old container had gone missing--that is why I replaced it.

 

So, what do you think?

Share this post


Link to post
Share on other sites

Posted · Report post

They didn't find it. They certainly didn't sign log. No smiley for them. I would send an explanatory email, however.

Share this post


Link to post
Share on other sites

Posted · Report post

Yeah, I'd have to agree with Keyresults here.... they didn't find it, if they would've done some research they could have known you put out a new container. Provided of course you shared that information on the cache page.....

Share this post


Link to post
Share on other sites

Posted · Report post

Replacing a container without the CO's prior (or belated) approval always brings the risk of log deletion.  That said, it's just a game and I try to be friendly and welcoming in my interactions with others (especially if they are newbies) and not play the part of the cache Nazi.  Maybe contact them and explain that they didn't find the cache, give them a hint as to it's location, then invite them to visit again to legitimize their smiley.

 

If you get no reply, ...

 

 

 

DELETE!!!!!!! MUAAAAHAHAHAHAHAHAH!

KeyResults likes this

Share this post


Link to post
Share on other sites

Posted · Report post

Agree with all the above, especially if you noted on the cache page that it's been replaced and especially if it's a high D or T or both.  Now they've just made more work for you in the process.

Share this post


Link to post
Share on other sites

Posted · Report post

This is what I posted with an "Owner's Maintenance" log 5 days before the group came in:

 

"I checked on the cache today and placed a new container. It is a bit more obvious than it was. I will probably replace with a bit less obvious container in the not too distant future. If you had looked for it before and weren't able to find it, how low can you go?"

 

I think I will wait a bit and see what others have to say.  It's raining (yeah!) in the area today, so I won't go out and pull out the "replacement" container today.

Share this post


Link to post
Share on other sites

Posted · Report post

It's a tough call and I may delete the log or not depending on what time of the month it is... oops!  My bad!

Share this post


Link to post
Share on other sites

Posted · Report post

Delete the logs, but contact the "finders" to tell them why.  

Share this post


Link to post
Share on other sites

Posted · Report post

This reminds me of something that happened to us several years ago. 

As we headed out of town for a caching road trip, we stopped for a cache just west of Katy, and found a container within 20' of the posted coords.  Not knowing that it was a "replacement throwdown", we signed it, logged the cache and went on our road trip.  

Well, the CO, realized that a throwdown had occured and deleted not only that cachers log, but also ours.

This upset of a bit, since we didn't know of the throwdown.  The CO explained that we hadn't found the real hide, and assured us it was there, so on the way back from our road trip we found the real cache, and logged it.  Just a minor inconvenience, but this is the sort of thing that can happen from throwdown caches.

 A similar situation has occurred a few times, that we will DNF a cache, only to have the next "finder" place a throwdown and claim the find.  

Share this post


Link to post
Share on other sites

Posted · Report post

This reminds me of something that happened to us several years ago. 

As we headed out of town for a caching road trip, we stopped for a cache just west of Katy, and found a container within 20' of the posted coords.  Not knowing that it was a "replacement throwdown", we signed it, logged the cache and went on our road trip.  

Well, the CO, realized that a throwdown had occured and deleted not only that cachers log, but also ours.

This upset of a bit, since we didn't know of the throwdown.  The CO explained that we hadn't found the real hide, and assured us it was there, so on the way back from our road trip we found the real cache, and logged it.  Just a minor inconvenience, but this is the sort of thing that can happen from throwdown caches.

 A similar situation has occurred a few times, that we will DNF a cache, only to have the next "finder" place a throwdown and claim the find.  

I wonder if that's what's happened here:  http://coord.info/GC1VMZF

 

No find for 2-1/2 years, numerous DNF's and a couple of needs archived -- then a find out of the blue by someone that describes it as an "Easy PnG".   Hmmmmm, can you say throwdown?

Share this post


Link to post
Share on other sites

Posted · Report post

This reminds me of something that happened to us several years ago. 

As we headed out of town for a caching road trip, we stopped for a cache just west of Katy, and found a container within 20' of the posted coords.  Not knowing that it was a "replacement throwdown", we signed it, logged the cache and went on our road trip.  

Well, the CO, realized that a throwdown had occured and deleted not only that cachers log, but also ours.

This upset of a bit, since we didn't know of the throwdown.  The CO explained that we hadn't found the real hide, and assured us it was there, so on the way back from our road trip we found the real cache, and logged it.  Just a minor inconvenience, but this is the sort of thing that can happen from throwdown caches.

 A similar situation has occurred a few times, that we will DNF a cache, only to have the next "finder" place a throwdown and claim the find.  

I wonder if that's what's happened here:  http://coord.info/GC1VMZF

 

No find for 2-1/2 years, numerous DNF's and a couple of needs archived -- then a find out of the blue by someone that describes it as an "Easy PnG".   Hmmmmm, can you say throwdown?

 

Lol. That's awesome, HC. I'm chuckling over here. Nothing like being outed. Lol

 

On a similar note, there have been a bunch of logs coming in from an area cacher on my and my wife's caches from someone who is logging in parallel to their "family members" who did actually make the find(s).The family members names are signed on the logs, but this person's name isn't signed on any of the logs. The person has had an account for quite some time, so it's not like they are backlogging because they splintered off to their own account and they are catching up. They are simply couch-caching. Like HC, I'm not a log-watcher. In fact, I've very rarely ever looked at names on logs in my caches. I figure honesty is a personal thing that they have to live with. However, since some of these logs are being back-dated to dates in October 2012 and forward, it looks like someone is trying to fabricate a cache-a-day streak. Sorry, but that just sticks in my craw. I've deleted the logs. They can bite me. Find the cache, sign the log. If they can't find it, I'll give them all the hints they want and even tell them right where it is if they want. But FIND the dang thing!

Share this post


Link to post
Share on other sites

Posted · Report post

Cool topic I contacted the owner of a cache a couple of months back and offered to replace the caches because he was no longer active.  

 

http://coord.info/GC22WD3 and http://coord.info/GC22WDJ  

 

My sons cub scout den made the replacements and placed them in the area.  He then contacted us and asked if we could just adopt the caches but has since stopped the communications.  I know number wise I am new to caching with only about 170 finds but do you see a lot of people with less than 10 finds put out caches and then just forget about them?  

 

Sorry if I hijacked the tread a little. 

Share this post


Link to post
Share on other sites

Posted · Report post

... do you see a lot of people with less than 10 finds put out caches and then just forget about them?  

 

Not a lot, proportionately, around me. Mostly Scouts, youth groups, etc., who move on. It all has a way of working itself out though in the end. It's just a little frustrating for newbies who seem to start looking for non-premium caches that have been abandoned or neglected, unsure if it's them or the hide.

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Back to the original question - DELETE!!

 

Regarding throw down caches, when it's totally obvious that a cache is missing (say an LPC), I'll replace, but also notify the CO and post it in my log.   Anything difficult, no way I would repalce it. I could simply be knuckleheading it - it's no fun and to mention confusing, when you find two containers in the same general area.  Which to sign, which is the real container....

Edited by 2katz

Share this post


Link to post
Share on other sites

Posted · Report post

Cache Control (I think it was him.... or ProMedRick) has a story about one of the Beaumont area cachers ending up with four containers at his cache site, due to folks not finding it and resorting to the throw-down method.  :idiot2:

Share this post


Link to post
Share on other sites

Posted · Report post

I had 2 at one of mine. 

Unfortunately, I put both of them there.    :uglystupid2:  :uglystupid2:  :uglystupid2:

 

I couldn't find the original hide, but the next finder found both of them! 

 

 

Cache Control (I think it was him.... or ProMedRick) has a story about one of the Beaumont area cachers ending up with four containers at his cache site, due to folks not finding it and resorting to the throw-down method.  :idiot2:

Share this post


Link to post
Share on other sites

Posted · Report post

DOH!

 

I had 2 at one of mine. 

Unfortunately, I put both of them there.    :uglystupid2:  :uglystupid2:  :uglystupid2:

 

I couldn't find the original hide, but the next finder found both of them! 

 

 

Cache Control (I think it was him.... or ProMedRick) has a story about one of the Beaumont area cachers ending up with four containers at his cache site, due to folks not finding it and resorting to the throw-down method.  :idiot2:

Share this post


Link to post
Share on other sites

Posted · Report post

I had two identical caches at my Baseball Boys cache after non-caching son Dan put a replacement right next to the original. Then Kirbydox, Georeyna and Zephyr had a laugh while finding both at the same time while on a caching binge. Did you ever put that second cache back into the wild, Donna?

Share this post


Link to post
Share on other sites

Posted · Report post

Ask Rich. She probably left it in his car.

 

I have had 2 on CLAPS.  Yeah.  Sometimes I can't find my own.  ;)

Share this post


Link to post
Share on other sites

Posted · Report post

I'd personally delete the log of a Throughdown (of the person who tossed it down) if the original was there, but not punish those who followed.  After all it wasn't there fault.

 

If I believe a container is missing, I'd first try to contact the owner and I'd DNF it.  I've done that with a couple of the posters above :-)

 

But if I see a destroyed container, I'll take a picture - reassemble the best I can, and if it's not possible, and I have something reasonable, I'll toss it down.  But follow up with pic's to the owner.  I've only down this once, usually when I find a container like this, I'm no place near my car which has the stuff to replace a cache with.

 

Right now I've got an upstart w/ 39 finds who seems to think I should go out after his single DNF to check my cache since he/she couldn't find it.  Yesterday (six days after his DNF of the cache) he posted a needs maintenance on my cache.  I'm pretty sure it's still there, it's just not a traditional container, I'll be checking that this afternoon. 

 

So another question, would you post a needs maintenance on a cache that you could never find?  And also, if you go out and find that it's safe an sound would you delete their Needs Maintenance log?

Share this post


Link to post
Share on other sites

Posted · Report post

I would delete the Needs Maintenance log and you need to go into attributes and remove it there as well.

Baytown Bert likes this

Share this post


Link to post
Share on other sites

Posted · Report post

 

Yeah.  Sometimes I can't find my own.  ;)

Probably a sign of a good hide. Tip: Use both hands.

Share this post


Link to post
Share on other sites

Posted · Report post

I did the same thing as Mr. Muddy Buddie on one of my caches in Dayton.  I figured I'd just leave it that way and double people's odds at getting a smiley.  Plus, if one were to be muggled, I already have a backup on scene!

Share this post


Link to post
Share on other sites

Posted · Report post

"So another question, would you post a needs maintenance on a cache that you could never find?  And also, if you go out and find that it's safe an sound would you delete their Needs Maintenance log?"

 

Before I owned a bunch of caches or had logged all that many, I was more prone to post a NEEDS Maint attribute.  Now, not so much.  I post a note instead.  The tether was broken on one of my caches and a well-meaning cacher with 800 finds posted a needs maint attribute.  Geeze, just tie it back up fella.  LOL

 

I found one yesterday that was a lock n lock belonging to Lefty Writer GC23YE2 and it was open and empty.  I cleaned it up and put a new log in it and posted photos and a note in my log.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0