cpacisa Posted September 26, 2010 Share Posted September 26, 2010 I've a TB that's been MIA since a cache got muggled 2+ years ago and I decided to reuse the number for a new TB. Is there a way to reset the odometer so the new TB won't have the old one's mileage added to it before it is even released? Quote Link to comment
+BlueDeuce Posted September 27, 2010 Share Posted September 27, 2010 The only way to reset the mileage is to delete the logs of everyone who had previously assisted your bug. And it removes their stats. Not a nice thing to do. Quote Link to comment
7rxc Posted September 27, 2010 Share Posted September 27, 2010 How about leaving a comment in your re release Note... mileage xxxx = 0 for the re release... Anyone who cared could do the subtraction fairly easy. And the logs are preserved. Doug 7rxc Quote Link to comment
cpacisa Posted September 27, 2010 Author Share Posted September 27, 2010 I don't want to mess with anyone else's stats, so if there's no other option then I guess I'll go with Doug's suggestion. I never considered anyone else would be intereested in the miles; I was only thinking for my own ability to track which TB's travelled farthest. Though I may not remember years from now (assuming it lasts that long) to search back to the page that has the entry about mileage reset, I'll make it red letters to perhaps make the entry easier to find. Thanks for the input. Quote Link to comment
+NanCycle Posted September 27, 2010 Share Posted September 27, 2010 I don't want to mess with anyone else's stats, so if there's no other option then I guess I'll go with Doug's suggestion. I never considered anyone else would be intereested in the miles; I was only thinking for my own ability to track which TB's travelled farthest. Though I may not remember years from now (assuming it lasts that long) to search back to the page that has the entry about mileage reset, I'll make it red letters to perhaps make the entry easier to find. Thanks for the input. You don't have to just put the information in a note that will get buried in the history--you can put it right on the TB's web page for all the caching world to see. Quote Link to comment
7rxc Posted September 27, 2010 Share Posted September 27, 2010 Thanks... that is the place I intended for it to go... not in log NOTE... I figured they would make an announcement on the page up top... Doug 7rxc Quote Link to comment
+BlueDeuce Posted September 27, 2010 Share Posted September 27, 2010 Warning: rambling tangent ahead. (not directed a the OP) Knowing the mileage totals of various TB releases is interesting but (in my opinion) since it is only showing the mileage of the cache hop, which is really not the distance the bug has traveled, I don't put much stock into the totals. It's nice to know, sure, but it seems to be...trivia. I would think that total number of cache visits and time alive are kind of worth knowing too. Tally the cache visits, Discovers, total number of individual cachers who have logged it. Total number of days since release. (The tracking history shows the total number of records but that is everything including posting a note) Personally, I don't want to consider bugs as finite, one life thingies. I use them to connect with other cachers and to see the places they go to. If don't give a duck's breath that the item had to be replaced why should anyone else? What, they didn't get to move the original keychain that I picked up at stuffmart? If you want to keep things real, go release a coin. When that's gone, it's gone. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.