This topic contains 14 replies, has 14 voices, and was last updated by 
-
Posts
-
I was just interested in finding out while some cachers do not log no finds? I don’t want anyone to get defensive on me…I’ve been guilty as well!
Just curious I guess, because as a cache owner, I believe reading about no finds might give us a heads up as to something possibly being wrong with our cache/s. Thanks in advance to your response. TamiTami,
I have to say I agree with you on the no find posting. I usually give a cache my best attempt, twice, before I post or I contact the cache owner directly.
As a cache owner, it does alert you to a possible problem. I also appreciate the posts regarding the cache condition. If someone logs “needs new log book” I can address it right away.
At first, logging a no find was really hard for me. But after swallowing my pride and doing it a couple times, I found that it’s not so painful and is really a great tool for other cachers and the owner.
Bec
Our FIRST cache was an NF. We logged and went back a second time to find it and post a
These logs are part of the game and serve to convey some bit of intelligence or lack thereof. It can be very useful to future seekers as well as to cache owners. We don’t always log NFs. We reserve them for the serious attempts at ground zero. If we were to find ourselves facing a challenge we are not prepared for (swimming, boating or climbing) we might skip logging it, unless the requirement has not been indicated on the cache page. There have been a few NFs that we were too lazy to log. These caches already had a sufficient number of NFs posted.
We have also logged a at a locationless. It’s all part of the game
Lots of times the “pride factor” gets in the way, plus sometimes, I’m afraid that if the cache is still there, claiming a no-find may discourage others from hunting that cache. But on the otherhand…not listing one when it’s actually missing could cause someone else to go on a wild goose chase. I agree that it could signal something to the cache owner that something could be wrong with the cache or any of its stages. I would lean towards fessing up to the fact that I wasn’t successful that time around.
[This message has been edited by brkster (edited 08-14-2004).]
If you’ve given the search a good try, DEFINITELY log a did not find. The cache owner can judge if a visit is needed to check up on things. Further If you find the coordinates are substantially off, be sure to log your coordinates, provided you are not giving away the location of an offset cache. In that case, you could list how much to add or subtract from the coordinates.
yes I think every one should log there did not find to help out the owner and the next person that is going looking also log the finds some people dont log that they found it cause they are not into the stats but the owner sure would like to here from the finder
I have had occasion when I came across a cache that had been missing for months but no one bothered to show it as such so…blah! I wasted time there! In fact, there was one that we did on our way home from the Dells where the final was missing. I e-mailed the owner to tell that we had trouble locating it, and asked that he check on the cache and let me know the status so I could get it on the next trip up. I never heard from him but saw last night that at the time, it was in fact gone, and the container has since been replaced…WHILE WE WERE IN THE DELLS. Had I known this, I would have returned to get it.
Now…while I do agree w/ the whole logging of no finds, I also feel it to be the responsibility of a cache owner to go and check on a cache that has been logged with a problem, or ask someone else to. At the very least post a note until such time as they are able to do so. And how hard is it to reply to someone who specifically requests a reply? In this case I never logged it because I was waiting for the owner to reply, but Lucy logged a no find for the team.
Last week I went to a cache with the intent to repair, or replace it. I saw the log of trouble, knew I didn’t have the cache yet, so I went on a mission! Found it, fixed it and e-mailed the owner that all was well again. I know that if it were my cache I would appreciate all the help I could get.
I have gotten notes about my leg of CTF and each time I’ve gone to make sure it’s still there, then sent a note to the one who had the problem. They usually return for the find once they know it is indeed there.
My point in all of this? Don’t complain about a no find if you don’t want others to know you didn’t find it! No find, no log, no sympathy from me!
~Linus
Linus has good points … if you don’t want to log a No Find, at lease email the owner … they can/should post a note that it could be missing and check on it.
I don’t know about others, but I’m getting very frustrated by cachers that jump ship and leave to trace. Case in point, the caches in the “Lions Den” area south of 53074. I’ve rebuilt and taken over a abondoned cache that was trashed. Now it’s becoming obviuous that the other cache in the area has been abonded by that owner too … however, that cache is functioning fine, so I’m not getting involved with it … the same cacher has another cache that Huggger fixed up in another park … and the same cacher claims to have placed several TBs in his cache months ago, but they never really were in there. I’ve informed the TB owner’s of death of their TBs. Grrrrrr!
I am not very good at this posting thing. Tried last night and it did not go through. Will try again. I wanted to put in my 2 cents about NF. Although we have almost reached our 200th cache we only have placed 3 caches. 2 were getting hit a bit but our favorite was not. We were thinking it may be because it was a multi, but we made the first part super simple. Finally someone was kind enough to let us know that they could not find it. DH ran out immediately and checked. It was there. Then he rechecked the cache page, somehow the coords were off over a mile. We still do not know how the numbers got changed around. Talk about feeling terrible. My point is that there were probably several others that tried but because they did not log the NF we did not know there was a problem.
Timberline EchoesNo problem with our pride. We log all of our “no finds.” In fact, I wouldn’t be surprised if we had more “no finds” than actual finds!
Like T & TB – our first cache was also a “no find.”
We’re not really into the numbers – just the fun of a good hike…
Wondering if my posts are coming through????
O.K. I confess!! Kat of AstroD-team is guilty of not posting her DNF’s. I feel stupid when I can’t find a cache that everyone else seems to have found. This is especially true on any caches rated under a 2.5. Yep, it’s that pride thing.
Anyway, I have now found a method of logging my DNF’s: I make my hubby do it. He doesn’t care. It saves my pride (after all I’M not the one logging it),and it keeps the cache log up to date.
Problem solved.
It would be nice if people would log in a find period! I archived a few caches thinking there was no action, only to get home and read the book and find there were at least double, sometimes triple the amount of people going to it than shows on-line. I dont get it… people must be going to the site to get the stats of the caches to begin with… why not log in the find. Unless they want to stay incognito when they do something stupid to the cache or items therein.
somebody just logged a find on my cache today with a back date from may. me, i can’t wait to get home and log them. i always felt bad when we couldn’t find a cache because it seemed like everyone else has no trouble on any cache. i think it would be more encouraging to new cachers to see that others have trouble. and if the rest of you would even just post a note to the log, like you went and you didn’t find it but you are coming back to try again, that isn’t posting a nf but it gives a heads up to others that maybe it is harder than it looks, or maybe isn’t there to be found.
You must be logged in to reply to this topic.