Wagonmaker

I like the idea of having my milestone be whichever cache I "naturally" found in that order, rather than planning it. Each cache is a good time (... OK, MOST caches), otherwise I wouldn't bother finding them! I agree with other posters: Congrats on your milestone and look forward to 3000!

I am also one of those OCD people that likes to see my finds in the exact order. However, I find that GC.com doesn't handle this correctly anyhow. For multiple finds on one day, it ends up listing them in order of how old the caches are (oldest caches first), regardless of in what order I found them. (And I always log them in the same order as I found them. Like I said, I'm OCD like that!) Anyhow, slightly frustrating, but I've learned to deal with it! The best you can do is make sure your smiley falls on the correct date. It may be out of order with respect to your other finds that day, though.

It's frustrating! Hehehe! But it's sure a hot topic of many geocaching pub nights!

My point is that we usually don't DNF frivolously. I was referring more to our general penchant towards DNFs in southern Manitoba, which has fewer DNFs in general than I have seen in other regions. Specific examples like "HUH?" which is notorious here in Winnipeg, get talked about alot, and the DNFs reflect the (intended) difficulty of the cache. I just wanted to provide a different perspective on DNFs. It is very much open to interpretation and could be different in different areas.

1. Even one DNF puts up red flags in the minds of alot of cachers. Even if only subconsciously. Yes, it technically means only one person was unsuccessful, but the negative perception will be there. 2. Saying "that's their problem" is inconsiderate. If something I do in this game affects how other people play it (especially negatively), then it is my problem too. 3. Not logging a DNF doesn't mean that it is unacknowledged; in fact, in my mind, not logging a DNF means I am resolved to come back and try again. 4. You definitely shouldn't use the NM log unless you KNOW there is something wrong with the cache. (ex. You find the cache is cracked and filled with water, or the log book is damp, or needs replacing). As a cache owner, nothing is more frustrating than a NM log on a cache that is perfectly fine. 5. This is how we handle DNFs in Manitoba, and I am glad for it. And I would hazard a guess that most Manitoban cachers like this modus operandi as well. Other regions may have other systems that work perfectly fine. I wanted to give a different perspective on it. Thanks for all the cheery, respectful replies.

People near here (in Manitoba) do not log very many DNFs and I am glad for it. I am always shocked at how many DNFs there are on caches when I go travelling. And most of them are ludicrous! The point of a DNF is to signal that there might be something wrong with the cache and it's unfindable. Just because I could not find it doesn't mean there's something wrong. And certainly, logging a DNF because of muggles, or because you only had two seconds to search and had to leave, or because GZ was inaccessible, is NOT the right thing to do. (Those should be a DNT - Did Not Try, or better yet DNTHE - Did Not Try Hard Enough.) As a previous poster said, a DNF discourages other cachers from searching for a cache. One DNF may result in the cache not being found for a month anyways, because everyone is waiting and watching for someone else to find it first. I only log DNFs when I am reasonably sure that the cache may be compromised. Anything else puts a bad stigma on a cache that is probably fine.

No, doesn't matter what Profil you're in. There's actually a way faster way: Main menu, Where To, Coordinates, (enter coords), green check mark. Done, the map and compass are now navigating to your coords.