Tubatad

That's one of the funnier theories I've heard yet. Thanks for sharing! I think this runs far deeper than 61% of the community voting for a means by which Groundspeak can make more money selling A.P.E. trackables. Yet again, the sharp eye uncovers the vast conspiracy concocted deep within Geocaching HQ as part of their subversive plan to promote religion masquerading as science. I actually talked to Bryan about reactivating it and he said that he wanted to do whatever the community wanted done with it. He really valued the input of the vote and feels that what is best for the game is to listen to the people who play the game. If someone knows something different, please correct me.

Here is a post from the Cache Owner from July 8, 2015 Ok guys, here it is, as simple as I can make it - I've fought long and hard to keep this in play. I've had to battle reviewers who say it shouldn't go to events because that makes it a pocket cache. I've had to get special dispensation from GeoCaching itself to accept it as grandfathered so that it CAN travel to events. HOWEVER, that doesn't mean the privilege should be abused. The long and short of it is that I am starting to get really annoyed at: 1. The people that think they know the geocaching rules regarding this cache and continue to quote them. My cache. Everything that's being done with it has been approved by GeoCaching. It's been in play for longer than some cachers have been alive. Why do you think that is? And 2. Conversely, the people that are flaunting the rules or really being selfish about the way this cache is being passed around. Anyone that has an issue - how about you read the guidelines I've established? For those that are crabbing about the "24 hour rule", it actually reads thus:" If you intend to grab it & move it, please try to post to this site & to it's Travel Bug Page 24 hrs in advance so others don't go on wild goose hunts or report that it's missing." I don't know about you, but I see the word "try". Not "must". Additionally, the idea of this cache is to travel. That's what it does. If you miss it, sorry. But that's the nature of a traveling cache. Whatever happened to the fun is in the hunt? I think that should cover both sides of the argument. Any posts not directly related to the hunting, finding or moving of this cache will be deleted. Finally, if all this nonsense doesn't stop - I will simply archive this. Anyone has a problem with this, go find another cache. Ps - DNF logs are not being removed. Self proclaimed "Cache Police" logs from people telling me how this cache should be administered are.

With all of the back and forth going on in the logbook of GC4241, I thought I'd start up an actual discussion page for this cache. It just makes sense to have a forum for the cache so there's one place for people to go to get information about the cache. It seems that the same 3 or 4 things come up a few times a year. Here are the "rules" from the cache page itself: 1. Please DO NOT remove the cache from its present site unless you can move it to another state (or get it into a HEAVILY TRAVELED cache near a state border). You can log it as a find but please do not move it unless you can do this. Please DO NOT remove any state objects from it. PLEASE DO NOT TRADE ANY STATE OBJECTS OUT OF THIS CACHE. THE GOAL IS TO ACCUMULATE STATE OBJECTS. Remember, You can put it IN a cache or hide it as a SEPERATE CACHE on it's own. (But you must email me or no-one else will find it!) 2. If you intend to grab it & move it, please try to post to this site & to its Travel Bug Page. 24 hrs in advance so others don't go on wild goose hunts or report that it's missing. 3. If you grab it, YOU TAKE RESPONSIBILITY FOR IT! Please see that it is treated kindly & redeposited swiftly. 4. Do not pick it up unless you can redeposit it out of state fairly quickly. 5. You MUST IMMEDIATELY after replacing the TB/Cache in a new location,log on & post the new coordinates here as well as emailing me with the info. I've also registered this as a Travel Bug so please post the new coordinates here as well: IT IS VITALLY IMPORTANT THAT YOU POST THE NEW COORDINATES RIGHT AFTER YOU REHIDE THE CACHE & EMAIL ME SO I CAN CHANGE THE CO-ORDS ON THE HEADER OF THE CACHE PAGE!!! If you can't do this, please do not retrieve the cache! Please feel free to decorate the cache as well! Sign it w/a sharpie, sticker it, attach things to it, etc. Just don't damage the Travel Bug Tag or the structure of the cache container. ** VIP *** VIP *** VIP *** VIP *** VIP *** VIP *** VIP *** VIP *** * Do not crank the lid so tight that someone else can't open it. Just snug it! * Turn lightly till some initial resistance is felt, then turn about 1/2 turn more. ** There will be about two threads still showing when it is tight enough. ** ** VIP *** VIP *** VIP *** VIP *** VIP *** VIP *** VIP *** VIP *** Remember, the idea of this cache is to hit all 50 states, accumulating a goodie from each state along the way. When someone finds the cache with a few state specific items in it, please contact me, I will photograph & post photos of the contents then use the entire collection of goodies as a prize in a difficult cache. I'd like to keep the log so please take care of it.

I just want to put my 2 cents in here. I emailed Groundspeak for the definitive answer in terms of adoption for this and other "moving" caches. They are all classified as Traditional caches and adoption should not be a problem. Locationless caches have all been disabled. There are no "grandfathered" Locationless caches as they have been converted to Traditional caches. Therefore, anytime anyone who owns a travelling cache wants to adopt it out, they can. At least, that's what the Groundspeak Lackey told me.

The subject line needs to be shorter. I think everyone agrees on that. I am happy to see the GC code in the subject line. Kudos on that as well. Not being able to see the cachers name in the subject line? Hate that. It looks like Gmail has a 90 char limit. A couple of samples from today end this way: has a new Found it log from MM... has a new Found it log... has a new Found it log from ... has a new Found it log from chelse... has a new Found it log from missyb... has a new Found it log from Cr... You get the idea. If you could shorten Watchlist Notification: Fire Me 18 Copalis (GC41P8C) has a new Found it log from chelse... to [LOG] Watchlist: Fire Me 18 Copalis (GC41P8C) Found by chelseywilson There's a lot more room for actual information instead of filler words. Make the subject meaningful and be verbose in the body. The casual user is not going to care and the power user is going to be happier.