theerooflove96

Has anyone else encountered users back-logging fake visits for trackables? I released a trackable (TB3WRG0) in July of this year, it was picked up the next day, but about 40 visit logs were retroactively submitted spanning 2 days, 4 states, and about 1600 miles. I initially thought there was a glitch that deleted my "Placed" log, but I checked the log dates to confirm that the "Placed" log was just lost in the noise. I can understand forgetting the order in which a cacher finds caches within a given day and specific area, but when the "Retrieve From" log is correctly logged while superfluously adding visits that happened days before the trackable was retrieved does not make sense to me. The mission of the trackable is not even to accrue mileage nor visit counties/states/countries. Following fuzziebear3's advice, I probably should not start deleting logs. As a social experiment, I am considering sending out "Follow the Instructions" TBs just to see how many cachers actually read the missions of trackables (which I do print out, waterproof and attach to my trackables).

I, too, am kind of fed up with the over-"visiting". IMHO, I think the introduction of the single-step "visit" is the cause, as opposed to the conscious "drop"-"grab" mechanism, which requires more thought. Anyway, I think the code of etiquette should be geared toward the owner-prescribed goal of the individual trackable in question. If the trackable is in a race that factors in unrestricted mileage, then, by all means, help its journey with accruing every nook and cranny of your geocaching path, but, for others, it is just white noise. As far as my own habits wrt trackables, I only "visit" caches with trackables that have missions related to the location, and I try to capture a photo when logging the visit.

Should a trackable be dipped into a cache which is too small to physically hold the trackable? Namely, if I wanted to show that a trackable has seen a particular landmark and find the nearest cache, but the cache is a micro, would there be any repercussions of the cache's trackable history having a trackable too large for the cache?

I checked the website, and it looks really good. I am just verifying that the registration is on a TB-by-TB basis, not user-by-user. Also, I had been thinking of sending out bugs with "TB Chase"-type missions, where a bug's mission is to catch up with another, a pursuit curve problem. I can see applications in a kind of "cops and robbers" scenario, where the robber wins if it reaches a location before the cop catches up with him. The equivalent "Three Mice" problem that I really want to get off the ground is a Rock-Paper-Scissors match, in which Rock chases Scissors, Scissors chases Paper, Paper chases Rock, the first to catch their target wins. That may be a different direction to take the website (or it may be in line with the site), but I thought to throw it out there in one of the only forum topics specifically addressing multi-bug scenarios. Thank you for the website. I will be registering a bug very soon.

I am an Eagle Scout from Baltimore Area Council - Harford District, and this movement has piqued my interest. I currently live in Southern Jersey, hoping to get back into scouting, and would like to set up a series in my local district (Burlington County Council - Mahalala District). The series, I believe, should be 12 caches long, one for each of the points of the Scout Law. I was hoping to create a prize for completing the series, but, being relatively new to geocaching, I am wondering if it is better to have a 13th puzzle cache that uses information contained in all of the caches in the series or to have the cachers report the points of the Scout Law to me in order to prove that they completed the series, as the Hiawatha Seaway Council - Northern Lights District did.

I saw a TB attached to a small circuit board with memory chips on it, but it was probably too fragile to really be attached to a bug. As far as legos go, I saw lego figurines (TB14JVQ, TB158Z7, etc.) in nearby caches, although I have not checked how they are attached to the tags.

I am new to geocaching, and this may not be the most appropriate topic for my question, but I recently dropped my first TB in a TB hotel, hoping it would be more likely to get discovered and helped along its way, but I, too, have seen logs of cachers finding the cache without picking up my bug. Is there anything that the TB owner can do to "advertise" a TB in addition to the trackable item details page and a note attached to the bug itself?