Jump to content

MtnGoat50

+Premium Members
  • Posts

    383
  • Joined

  • Last visited

Everything posted by MtnGoat50

  1. Congratulations to Illumineon on hitting 400 today at Castle LadyHawke! It was great seeing you again and thanks for finding the cache for me! Cheers and best wishes from MtnGoat50!
  2. I've only seen this happen once. I was trying for a FTF on a new cache but came up empty. I posted a DNF, emailed the owner and put it on my watchist. The next morning I had three emails from my watchlist. The owner moving the cache 150', the reviewer archiving it, and the reviewer retracting the listing, with a stern note to the hider. Apparently the hider moved the coords away from an existing cache to get it published and then tried to sneak them back afterwards. His scheme didn't work. Ironically the cache was supposed to be an "accuracy special". I actually went back, found the cache and signed the log but I've never been able to log it online. I'm not sure how you'd identify which one. You might try checking your All Finds PQ and manually look at the archived caches.
  3. I don't think this is a glitch but something that was done deliberately. Perhaps one of TPTB, will explain.
  4. I appreciate this suggestion, but I just checked and that one cache is included in the MyFinds file, so presumably is also in the All Finds query. Where does the total next to one's log come from? I can't imagine it would be computed in some different way, but obviously it is. Perhaps I misunderstood. When I look at a recent cache you've done it shows 930 finds. On your Geocache Information page it shows 930 finds. But when I click on the (All Cache Finds) link, it shows "Total Records 929 - Page: 1 of 47". Is this what you're talking about? The record that's missing is the locationless.
  5. I think it's because of the one Locationless cache you've found. I have the same problem. They don't show up in the All Finds list.
  6. Congratulations to stikbow on reaching 200 at Sullivan Park (GCQ6TW) today!
  7. Congratulations!! to Trevor and Kate on hitting 2400 at the ape cache this Sunday!
  8. Congratulations to Snowwolf75 on 400! Lynn and I enjoyed meeting you at the Ape cache this weekend. Cheers and best wishes from MtnGoat50 and Love2ski!
  9. I enjoyed reading the link, but that kind of thing makes me sad. The finders were punished for being honest in their logs. If they had just logged "TNLNSL, TFTH" or maybe talked about the weather instead of how they got there, their logs wouldn't have been deleted. After all their names were in the logbook! I want people to be honest when they log my caches and I won't punish them for it. I enjoy reading about their experience and I'm disappointed when someone does a "cookie cutter log" or just says "Found it. TFTH". If I had a difficult cache and someone found a loophole, I might scold them in a note, if I thought what they did was unreasonable, or try and close the loophole for the next finder but I'd let their log stand. It looks like this hider does the kind of caches I really enjoy. Now that I have family down that way, I may get to try some of them. But, after seeing this, all I'd log online is "TNLNSL, TFTC" and that's really too bad.
  10. I don't think you're being the cache police when it's one of your own hides. I think we've all found ourselves at a cache with out a pen, at one time or another. Unless you have a good reason to doubt this persons word, I'd let it stand. I know the cache that prompted Chumpo's thread. It's very hard to spot and once seen it appears inaccessible. There is an easy way to retrieve the container but it too, is hard to see. Some very new cachers logged a find on it, admitting they could see the cache but couldn't retrieve it. I thought about emailing them but It's not my cache and I don't want to be the cache police. I also don't want to embarrass new people and turn them off to the hobby. If they keep caching, I think they'll figure it out. This this kind of nooB mistake bothers me a lot less than someone with hundreds of finds deliberately logging a Found it on a cache that's not there, just because they think they can get away with it.
  11. Way to go EleriandBlade! 100 is a big milestone! As far as putting a smile on your face, it's one of the best! Cheers and best wishes from MtnGoat50.
  12. I really disagree with this, for all the reasons mentioned above. I have found several archived caches. They are all ones where I FOUND the container, signed the log, left stuff, took stuff and rehid them like any other cache and in most cases was surprised to find out they were archived when I went to log them online. Some were over a year old. In at least one case the owner thought the cache was missing and had it unarchived after my find. Not allowing logs on archived caches removes a valuable source of feedback.
  13. I agree. Very well said!
  14. Ditto! I'm in Montana visiting family and using a dialup connection. The older pages with the map load fine but the extra mouse click and wait on the new pages is a pain. I'm going to miss the static maps.
  15. Actually, I believe it's 1 minute (of latitude) that is equal to 1 nautical mile. One degree would be 60 nautical miles.
  16. Too.... Cool! Way to go ChrisNScott! Congratulations!
  17. Yes, I would like to congratulate everyone that had a milestone this weekend also. I would especially like to congratulate Lookout Lisa and Allanon on their milestones. It was great getting together with you after dinner for a beer, which I thought tasted particularly good! Congratulations!
  18. Yep, you're supposed to use the one called "Spokane Cache Machine 2," not the one called "Spokane Cache Machine 2." (they have the same name). There are 117 caches on MtnGoat50's list, 111 on the first list. But as it's been pointed out, apparently neither of the bookmark lists match up with the driving directions (unless I'm totally screwed up or missing something, which is entirely possible!). I'm sorry for the confusion. I never entended to make my list public and only did so early this morning when it appeared the other list was not being updated. I based it on the printed turn by turn directions on the route, as carefully as I could. I included all the caches I saw including disabled ones. I'll admit I was a little tired at the time, so I could have made some mistakes. I've renamed the list SCM2 which hopefully will reduce any confusion. Again, I'm sorry if this caused anyone problems.
  19. UPDATED ROUTE INFORMATION For a current Bookmark List of caches, see my Spokane Cache Machine 2 list, on the event page. (You'll need to click the 'more' button, my list is at the bottom.) Here is a Link to Lookout Lisa's Route in PDF: www.cache-advance.com/spokanecm/SCM2Route_v7.2_Final.pdf Here is a link to Lookout Lisa's Route in .Doc: www.cache-advance.com/spokanecm/SCM2Route_v7.2_Final.doc Sorry for the long delay in getting this out.
  20. If you can, wait until tomorrow. We're having a meeting tonight and hopefully, we can finalize the info.
  21. I'm doing my final upload now, since I leave early tomorrow (as noted above), so hopefully my copilots will grab any update files. See everyone there! If it would help, we could have a laptop available Friday evening with the latest files and also have the files available on a flash drive. The Friday night location is supposed to be a free wireless hotspot, but I couldn't get it to work the last time I was there several months ago.
  22. Good Going Jim! Congrats on 1-Grand. See you on the trail (or at the upcoming meeting). T&K THANKS! (But after all this time, couldn't you have gotten my name right? )
  23. I live in Spokane. I've done some of RedBear's caches but I don't know him personally. I'll see what I can do...
  24. Good job CHRISNSCOTT! Congratulations!
×
×
  • Create New...