Question on Travel Bugs

[CinemaBoxers]

We LOVE to move TB’s – but my question is – I know there is a ‘Discovered’ option – do you, or CAN you list ALL TB’s you come across as ‘Discovered’ or do you just log the ones you take?

Was not sure… we come across them all the time, but only pick up ones we think we can help on a mission, or move on quickly, but would love to mark some of the others as discovered.

I guess Im asking, is THAT what ‘Discovered’ is for??? And can/should you log them all?

Paula
CinemaBoxers

[EnergySaver]

Good question … that “discovered” choice is somewhat new … pending someone correcting me, I *THINK* the purpose is to log you saw the travel bug without taking it … I suspect the choice was added for events, where coins tend to get passed around, to avoid people logging “grab” entries out of the hands of other people, which can be a problem when someone has physically dropped a TB in another cache but others keep “grabbing” it out electronically because they happened to jot down the code number.

So I guess, in theory, you could use “discovered” everytime you see a travel bug in a cache … but in my opinion, your just create a lot of extra effort on your part … but that’s up to you.

[CinemaBoxers]

Then I’ll stick with my original thought – LOL Only ‘Discover’ the ones I REALLY like! LMAO Sometimes I see ones that are so clever, or fun, and I just cannot help with the mission…perhaps a discovery is in order, so I can watch their progress!

[EnergySaver]

Good plan … yes, if you want to follow the travels of a specific TB, this would help you create a list.

Another option for you … click on the “Watch this Travel Bug” option (also in the upper-right corner of any TB’s page) … the advantage is that you’ll get an email everytime a specific TB moves … assuming you consider that an advantage.

On a side note: sometimes it’s fun to watch a TB that is traveling in another country … my daughter has a TB that’s in Germany and it’s fun to attempt to read the comments that are written in German. As an example: 2/4/2006 entry is fun … http://www.geocaching.com/track/details.aspx?id=89978 … it roughly translates to “Is it a small bee or a wasp? We will take the small thing to with us to where it is warm. Only time will tell where it will be next.”

[MajorBrat]

@EnergySaver wrote:

Good question … that “discovered” choice is somewhat new … pending someone correcting me, I *THINK* the purpose is to log you saw the travel bug without taking it … I suspect the choice was added for events, where coins tend to get passed around, to avoid people logging “grab” entries out of the hands of other people, which can be a problem when someone has physically dropped a TB in another cache but others keep “grabbing” it out electronically because they happened to jot down the code number.

So I guess, in theory, you could use “discovered” everytime you see a travel bug in a cache … but in my opinion, your just create a lot of extra effort on your part … but that’s up to you.

This is the basic idea we got from conversations with a couple of our “Lackey” friends over the past few months. (Well put sir!)

[cacheseekers]

That does present an interesting solution for us (cacheseekers). We love grabbing travel bugs but we hate the fact that we’re sometimes (ok most times) slow at releasing them because of our lack of time to actually cache. Listing it as ‘discovered’ rather than “Found” would provide us a way to log that we ‘found it’ but actually leave it in the cache for more active cachers to move along.

I’m assuming “Discovered” leaves it in the cache vs “Found It”.

Then it would be a win win for everyone 😉

[MajorBrat]

@cacheseekers wrote:

I’m assuming “Discovered” leaves it in the cache vs “Found It”.

….in the cache, in the hands of the current holder, on the moon 😉 …wherever. It gives you the icon while letting someone else have/keep the bug.

[cacheseekers]

@MajorBrat wrote:

@cacheseekers wrote:

I’m assuming “Discovered” leaves it in the cache vs “Found It”.

….in the cache, in the hands of the current holder, on the moon 😉 …wherever. It gives you the icon while letting someone else have/keep the bug.

We’ll have to debate if we’ll do that or not. Doesn’t seem to be that bad of an option as you need to have the Tag# anyways.

[MajorBrat]

@cacheseekers wrote:

We’ll have to debate if we’ll do that or not. Doesn’t seem to be that bad of an option as you need to have the Tag# anyways.

It is completely your option! For us, we generally don’t like to log bugs unless we walk away with them. There are times when someone brings us a “personal” bug and asks us to log it. Those are usually the only ones we do that for. Sometimes when we cache with others and we all find a bug, we’ll grab it then drop it in another cache along the way. They can then grab it and take it wherever… It works for us. I like your idea of “discovering” only the cool ones you find on your journeys.

[TyeDyeSkyGuy]

I hope that this is how it works because that is what I have been using “Discovered” for.

Before this, when we saw a bug that we could not move, or a coin that we wanted to leave for someone else, we would log the find, and then have to post a note to the cache with the words “Bug Drop” so it would be back in the inventory. This was a real pain, especialy in caches I own where people would forget to drop a virtual coin back!

I love this new feature and was surprised to see it just last month. I didn’t read about it anywhere before I noticed it either.

[Barry Butrymowicz]

We discover any TB’s that we can not help towards a goal, and would hope that anyone that finds one of ours would do the same.

If not for any reason other than this, It lets you know that your TB is still active, and in a cache somewhere, Sometimes we get worried when we know our TB is in a cache but no one puts into their logs that they saw it in the cache.

[Team Deejay]

When we first started, we would write down all the bugs in the cache and “grab and put back” the ones we didn’t move. In short order, this became too much work, so now we just log the ones we move.

[Author]

Posts