- This topic has 21,414 replies, 82 voices, and was last updated 5 hours, 41 minutes ago by
.
-
Barely broken?
Picked up a TB yesterday that had been at the WBCB ’12. I see Zuma! had it in Sally’s TB hotel (sic). Ecorangers K Spud and lagrac all had it at one point too. Anyway, I’m digging through where some of these bugs have been, and I come across this several times where a major cacher in CA will be logging finds in California, then suddenly log a find in Nebraska, and then be back in California either the same or the next day. Always like that, BOOM in Nebraska to log a challenge cache find in the same trail of challenge caches and BOOM back in CA within 24 hours. Nothing in the logs about taking a trip to Nebraska. Sometimes something about taking a trip in an RV, but that must be some vehicle because it can make it all the way back to the same area he was caching in within a day. Sloppy logging? Inattentive CO on the challenge caches? Or, just the way some people play the game? Found it. Sloppy logging two years after the fact. Which is sort of funny, because it took a trip to Nebraska before it was even activated! The bug has over 39,000 miles on it. Most of them are from “trips” to and from Nebraska that never took place There are folks who will sign a log on a challenge cache, then eventually qualify. They might “save” logging it as found for a day they need for some challenge….I’ve seen logs like “I just noticed I qualified for this.” Not how we choose to play that game, but some do. We also see people log events or EarthCaches or whatever on the wrong date, maybe even events or places they never attended or visited, knowing the log might get deleted, but even when deleted….they get their souvenir. That has happened with some we owned or hosted….often.
Picked up a TB yesterday that had been at the WBCB ’12. I see Zuma! had it in Sally’s TB hotel (sic). Ecorangers K Spud and lagrac all had it at one point too. Anyway, I’m digging through where some of these bugs have been, and I come across - You must be logged in to reply to this topic.