Reset Travel Bug

[LeapFrog & Ms. LadyBug]

I need to know how to reset a travel bug or change the initial drop off information. I accidently logged it as placed in the wrong cache. I need to change it to a new cache. Please help!!!!

 

[This message was edited by OneTequilaTwo on May 18, 2003 at 07:42 PM.]

[+MissJenn]

Did you try deleting your incorrect log?

Then, you can write a new log....

 

-- I recognize fun when I see it.

[LeapFrog & Ms. LadyBug]

Yeah, tried deleting the entry, but the TB was still associated with the cache. Thanks though .. let me know if you have any other ideas!

[+Team GPSaxophone]

Make a new log on the correct cache.

 

[LeapFrog & Ms. LadyBug]

I did this, but how do you get the travel bug to identify itself with a new cache?

[+pdxmarathonman]

You'll probably need to just retrieve it from the wrong cache and drop it off in the correct cache. I don't think you can make the TB forget that it was in the wrong cache.

[+Markwell]

Actually, I was just told by TPTB that if you delete the history of the bug, it calculates distance traveled by chronological order of the individual records.

• Grab the bug.
• Delete all of its false records.
• Make a log in the cache in which it sits, and drop the bug there.

That should take care of it.

 

Markwell

Chicago Geocaching

[LeapFrog & Ms. LadyBug]

Thank you Markwell and everyone else for helping me figure out this problem. Markwell was right on the money. I wrote Groundspeak customer service and they essentially said the same thing that Markwell said.

 

I logged the TB as if I had retrieved it from the wrong cache, then I deleted my original log at the correct cache and re-entered the visit. Since the computer thought I had the TB in my possession it then allowed me to transfer the TB to the correct cache. I then went in and deleted all the old logs for the TB so I could correct the distance the TB traveled.

 

Thanks Again!!! I have included Groundspeak's original message below:

 

The movement of a travel bug is calculated and listed by date order on the web site.

 

Sometimes a travel bug gets logged incorrectly. For example, a travel bug is picked up by one user before the other person has a chance to record its movement on the web site. In this situation you can sometimes fix the movement by adding logs and backdating them so they match the time they were in the missing caches.

 

To do this:

 

1. Grab the travel bug from wherever it is now.

2. Log the cache you want to drop the travel bug in and select the travel bug so it is left on the caches web page. Make sure to backdate the drop so it matches the date it was left there. 3. Grab the travel bug back and list the date it was picked up as the date it was taken from the cache. 4. Place it back in the cache that it is currently in with today's date. 5. After the miles are correct, delete any of the logs that are unnecessary, like the log in step 4. Step 4 was only to make sure that the travel bug is listed in the right location.

 

Viewing the page should now show the corrected distance that the bug has traveled.

 

Sometimes it is too difficult to add entries after the travel bug has moved around the world. Although it is great to have every stop on its journey recorded, you can still enjoy its continuing journeys.

[+GeoKayG]

This makes perfect sense to me but what do you do if you don't have the TB number? I just use the trackables inventory in my account to dropbugs in caches so I can only look at log now and the location is many miles away.

 

Thank you Markwell and everyone else for helping me figure out this problem. Markwell was right on the money. I wrote Groundspeak customer service and they essentially said the same thing that Markwell said.

 

I logged the TB as if I had retrieved it from the wrong cache, then I deleted my original log at the correct cache and re-entered the visit. Since the computer thought I had the TB in my possession it then allowed me to transfer the TB to the correct cache. I then went in and deleted all the old logs for the TB so I could correct the distance the TB traveled.

 

Thanks Again!!! I have included Groundspeak's original message below:

 

The movement of a travel bug is calculated and listed by date order on the web site.

 

Sometimes a travel bug gets logged incorrectly. For example, a travel bug is picked up by one user before the other person has a chance to record its movement on the web site. In this situation you can sometimes fix the movement by adding logs and backdating them so they match the time they were in the missing caches.

 

To do this:

 

1. Grab the travel bug from wherever it is now.

2. Log the cache you want to drop the travel bug in and select the travel bug so it is left on the caches web page. Make sure to backdate the drop so it matches the date it was left there. 3. Grab the travel bug back and list the date it was picked up as the date it was taken from the cache. 4. Place it back in the cache that it is currently in with today's date. 5. After the miles are correct, delete any of the logs that are unnecessary, like the log in step 4. Step 4 was only to make sure that the travel bug is listed in the right location.

 

Viewing the page should now show the corrected distance that the bug has traveled.

 

Sometimes it is too difficult to add entries after the travel bug has moved around the world. Although it is great to have every stop on its journey recorded, you can still enjoy its continuing journeys.

Edited April 25, 2012 by GeoKayG

[+Gitchee-Gummee]

This makes perfect sense to me but what do you do if you don't have the TB number? I just use the trackables inventory in my account to dropbugs in caches so I can only look at log now and the location is many miles away.

 

Now is the time that you need to learn you should always keep the tracking number -- at least until you are sure it is logged properly and completely "out of your hands".

 

This is a (small) problem with the ability to drop a trackable simply by using a drop-down menu. Mistakes happen. It sometimes is necessary to make corrections.

Make a note of the # when you pick it up. Toss the # when you are done and movin' on. Some never toss the number.

It used to be that you needed the number each and every time you logged (aside from notes).

[+BlueDeuce]

Plus the site has been updated recently and offers new features. you might not want to follow instructions from 2003. There's never a problem wit posting a new thread even if it's been asked before.