Bigbandjohn

Thought I'd drop a note on this topic. When starting, you may not have a TB to leave. So, Take one, leave one doesn't work. I collected a few locally to help on their way to their goals, but they ended up getting stuck at their next location, for which I feel guilty since I transferred them to someone else (this is being rectified this weekend). I think if we can truly help a bug towards their goal, then it's fair game, though we don't want to pilfer a cache clean of all the bugs, since others may want to participate, and isn't that the way it should be. I'm about to release 3 TB's of my own in the near future, and I hope that people help them fulfil their mission, reguardless of the "Leave one, take one" rules. I want my bugs to move, like I know others want theirs to move, of which I will be more careful in the future in how I handle them. Lesson learned.

Thanks. Now I know what needs to be done. My travelling Cache bugs will be hitting the road soon. I'll be releasing one in Connecticut, and the other in Germany or England if I have time on my business trip coming up. This is going to be fun... :-)

Sadly, there will always be the "fringe element" that will make a good club's name bad. Thousands of people can be conciensious, but one bad apple, and everyone wants to throw out the whole bushel. It's sad.

Size is small, with items should easily fit into a regular cache, and quite possibly even some small caches.

Hey all! Fairly new to Geocaching, though been indirectly involved for years through friends who do it. I have a special travel item I would like to determine how to quantify. It's basically a "Travelling Cache Bug". The Bug (Probably a Bus or a Truck) would posess items from my location, and as it travels, people will take something from my local items and replace it with something from their location. When completed, it'd come home, and I'd reset it for the next trip. It's a bug, but it's sort of a mobile cache too. How should I configure it on the site? Thanks all! -BBJ

I was well over 300 when I found my first cache. Glad to say I'm not anymore.

I noticed with the latest firmware that there seems to be some interesting issues dealing with updating location after it is moved any distance while off or without batteries for any length of time. It takes 20 minutes now for it to find itself - far longer than before the upgrade. However, it also fixed some other issues. It does lock down location better overall in spite of the occasional drift - i've had it go crazy on me a couple times now, usually in Central Virginia. Hi all. First post here. :-)