brad.32

Bump.

Modify its description on its web page, as RK wrote, plus send an email to the current holder and ask them to receive (through the mail) and attach a new laminated tag from you ... then mail it to them. Notes in the log don't matter. People read their email, might read the attached tag and may read the web page description, and the latter usually after they find the bug and brought it home after a long day caching, while on vacation.

I've changed my bug names through the normal editing page. It's not a problem. You don't even have to name them initially, but it helps you to keep track of which tag is which.

It has come up before. It has been suggested before that it should be an OPTION to search the other fields, in addition to the name. GC has bigger problems to deal with at the moment, so I don't know when, or if, they will fix this. ... so your question remains: is the search function going to be fixed to allow searches within the name field, and allow the option of searching the other fields?

Is there no answer to this question???

One of the web pages there (http://www.bga.com/~pixel/butterfly/tags.htm) indicates that the tracking is done by email. The butterflies have a space for an email address on the back (the owner's). The owner keeps the records of the butterfly's movements based on the emails.

It happens... http://forums.Groundspeak.com/GC/index.php?showtopic=67387

2-3". Maybe 3.5" ... I've done some that are 3.5", but I think they're big. The single-use cameras that are in some caches are about 3.5". Larger than that and they won't fit most caches. I agree with RichardMoore about the minimum size, but people do send micro TBs.

I contacted the owner and asked them to try recalculating distance on the bug. Maybe that will update the database and straighten out.

There are a few other tracking systems out there which may or may not require you to purchase the associated tags or numbers, like discussed in the thread Dino Hunters linked in. The problem with those systems is that they are not Groundspeak, so they are not integrated into the GC web page. On GC you have to enter the tracking number, but it's within the GC web page system, then the bug drop is just a drop-down selection after that. The inde tags/numbers make extra work for the finder to log the finds and drops for them. The finders have to navigate to and within another web site for the find and drop or maybe just send an retreive and a drop email to the inde bug owner. More work means less ... compliance.

For your caches, you always log notes not finds, but leave a note to say what you did to/with the cache.

If you have already logged the cache, but not the bug, go back to the cache page and log a NOTE (e.g., "Forgot to drop bug xyz in my find log...") and select the bug from the drop-down list as WH wrote. Edited to add xyz

That info is not editable by the TB owner once the bug is initialized. You're not the first person to do this. Write an email to Contact@Groundspeak.com, explain your problem, and what you want to change. Nicely.

There are two by that name: http://www.geocaching.com/track/details.aspx?id=9858 http://www.geocaching.com/track/details.aspx?id=75219 When you find the one you're looking for, you could note the reference number (TBxxxx) to search for it again or add it to your watch list.

Did your reading include this thread http://forums.Groundspeak.com/GC/index.php?showtopic=65939 ?

Anyone can hold on to a travel bug as long as they want. Bug owners appreciate it when they move in a week or two. The bug's web page shows the current location of bug (what cache or what cacher)at the top and, of course, the history below that. You can click on the bug holder's name, goto their profile, and send an email to them from there. If you look at someone's list of travel bugs that they have picked up or own (following Toby Partridge's instructions), one of the columns is last log and another is location. The table can be sorted (in ascending or descending order) by, for example, last log. I do this to see which of my bugs haven't moved in a long time, then I click on location, if it's a cacher, and send a snotty email to them to force them to get out there and place the bug. (Don't take that last part seriously.)

Yes, you could ask the cache owner to check the log book or you could go back out, because you've visited the cache too, and maybe locate their GC user id if they physically logged the cache. It's probably dead/MIA, as Snoogans indicated. In the mean time ... please mark your bug as missing to move the bug to unknown location so other people won't expect it in that cache (or move to the TB graveyard if you prefer adding thousands of miles to the bug).

Ummmm, why is the destination an event cache?

That is the problem with muggles. Check with the TB's owner to check if the timing of the return (and mode of transport) is okay with them.

According to the note from the owner on the TB page, they want it to travel. The FAQ "What shouldn't be in a cache?" says to use common sense in placing items in a cache and food items "shouldn't" be placed in a cache. I have found food items in caches and removed them (candy and gum). I wouldn't call a can a food item, but I wouldn't make a TB like that either. They did, and they want it to travel. If I had found this bug, I would have just placed it. People use ice cream buckets as cache containers, which must smell pretty good to a sweet-hunting animal.

Exactly. When I attach the instruction tag onto my bugs' I use a key ring and not the chain and make sure the tracking number side of the tag faces the instruction tag, so it's more difficult to take a picture with the tracking number showing.

You could post a note here or in the West and Southwest (which includes Hawai'i) forum and ask. To find out which caches near you have TBs, you'll have to look through the list of caches near you and check their destinations OR do a TB search for "hawaii" (and "hawai'i") and check their current locations, but the latter list will be long. If you use Watcher to look at a cache list, then you can filter the caches to only those containing TBs, but you'll still have to look at each to check the destination.

Yes, you can recall it when you're done with it, either by snail or cache mail. It's your bug. When it's done, you can give it a new mission or move to unknown.

AFTER you create the bug, then this type info is useful. Much of which is in the pinned thread "Snoogans' Tb Longevity Clinic".

What Sagefox wrote and wait. They should have logged the find, but you have contacted them, so that and marking it missing (moving it to unknown) are the two things you can do. Under two weeks is nothing, like jbhooker3 wrote.