brad.32

Moving caches are not permitted? On GC7572, http://www.geocaching.com/seek/cache_detai...72&Submit6=Find, the description reads, "Time for a new cache to be resurrected from the ashes of the old". ... or is it that no NEW moving caches are permitted. Apparently this was a regular cache that is now a moving cache, that also happens to have a TB tag attached.

I would rather most of my bugs not go into TB hotels because they are not in any hurry to get anywhere and I want them to move from cache to cache and eventually get to where they are "supposed to" go. Time in a TB hotel waiting for the perfect ride does not fit into this scheme, neither does flying the bug across the country. That's why most of my bugs have "travel by ground" on the instruction tag, but don't actually state their goals. The web page has the goal, but if everyone only moves it a little bit (using a ground-based wheeled vehicle for you Cannonball Runners) then a little bit in any direction is okay, and the bug should make progress toward the goal. Kind of a directed random walk. I am thinking of changing the phrase on the instruction tag to something like "please move at most 200 miles" instead of "travel by ground". I've had people add goal tags to some bugs and fly some bugs cross country to help achieve the goal, but the goal is primarily to travel from cache to cache, not to make a speed record getting to some spot, which is secondary. Now Genii, Carl, Carol, and Lou, on the other hand, are racing bugs. They are different and TB hotels could help them.

See a thread a few down on the list: http://forums.Groundspeak.com/GC/index.php?showtopic=66673

GC7572 isn't eligible to win because it's owned by brogan, one of the race organizers.

Marking a bug as missing, moving it to "unknown location", is a better option for missing bugs.

I like WH's 4-TBs plan. The lock and key plan that Weasel outlined originally has the logistical problems bons went into. He mentioned the need for the finders to rehide them separately again after a matched find. That part would be the biggest hassle for the finders. What D/T for the parts? How far apart is the min/max? How far from the final cache? Etc.

This bug (http://www.geocaching.com/track/details.aspx?ID=45935) has yet to make it TO Canada. Your bear's stops will probably include some caches in Southern Canada, like Chicago or Seattle.

http://www.geocaching.com/track/details.aspx?id=32792 Is the bear going East or West first or just traveling and hopefully will get to both coasts eventually?

Realistically, anything longer than a month is too long, so then it's time to start the questioning, friendly emails. It depends on the goal of the bug. If the bug's goal is to get to some place quickly, like winning a race, then a month can be too long. If the bug's goal is just to move around aimlessly or is in no hurry, then a month is too long. If the bug's goal is to get to some particular place that might require someone to fly there, then a month waiting for the "perfect" lift is not unreasonable. However, most bugs fall into the aimless, no-hurry category so a week or two would be ... ideal.

I see you own a few. Were you trying to add your own bugs? You can't do that "because" you're already watching them as the owner.

Yeah, yeah. I figured it out AFTER I posted and shut down. Duh. Think first. Ask stupid questions later.

How do you know what bugs are racing? The CR web page hasn't been updated yet, so it doesn't have a list. The GC TB search function is, well, um, essentially broken. Hmmm.

The other "side/half" of GC7572 is TB56CF: http://www.geocaching.com/track/details.aspx?id=22223

Cartman was placed in Florida yesterday. If he keeps up this pace (1/3 done now), he'll be done by July and there are several others in TX that are one step behind. Supposedly more people cache in the summer, so the whole race could be finished by the end of summer.

If you mark a TB as missing, it moves the "unknown location", not in someone's hands or in a cache. Anyone with the tracking number can then grab the bug from that limbo non-place, and then place it in a cache.

You can't put html in the TB description when you CREATE the bug, but you can edit the description later and add html. Huh? I don't make the rules, I just work around them. Paragraphs are <p> Line breaks are <br>

The issue of is it a separate trade has come up several times before, most recent: http://forums.Groundspeak.com/GC/index.php?showtopic=65939

I agree: yes, it is wrong. Check with the owner first.

Yes, the preferred method now is to mark the bug missing, moving it to "unknown location". I'll be marking/moving a few of my bugs there soon.

The travel bug "How to" page covers the basics (http://www.geocaching.com/track/howto.aspx). Most things related to TBs are common sense, as you wrote "do unto others". However, people do what they think is the right thing in their minds. Cachers are people, and don't necessarily follow whatever "rules" you might want them to follow. There really can't be too many TB rules because they can't be enforced anyway. If you search the TB thread you'll find many discussions of these things. If you have a specific question, search for the key words or phrase, before posting your question, because it's probably come up before. ... and the pinned thread "Snoogans' TB Longevity Clinic" covers many things related to sending bugs.

Snoogans currently has 48.

Fritz_Monroe can say which one they used for Punch, but check the pinned Snoogans' Tb Longevity Clinic for a list of some of the instruction tags that people have out there, and other suggestions.

Yeah, the modified search function now "Searches name, mission and description for keywords", so the results are broad. The old search function only searched the name field. Many of us would have preferred to have the OPTION to search the mission and description in addition to just the name, instead of making a full search the default.

Punch Buggy Yellow

Of course, the current holder would need to delete their TB find log first, then log the bug into the cache (leaving a note with the drop) and then out again.