SeattleWayne

I found two caches yesterday which equaled 22 gold coins.

I hear Texas has a real wild pig problem, too. A bunch of friends of mine when I was in the military would always take hunting trips to go kill as many as they were allowed to kill.

Didn't know this. Thank you, Cerberus. Not like I ever waited anyway.

Wait. The event wasn't pirate related? Ohhhhh boy.

Entirely not so. Reviewers are volunteer basis which means they give their free time to the game. Caches get published when reviewers have the time to get them published. Besides all of that, there is no real reward for being first to find. Except bragging rights. And in my experience so far, there aren't too many people who really care about any of that.

The purpose of scheduling publication times would be so dubidubno can be the first to find a cache.

I second this. On one of my hides, I gave a shoutout to a FTF-er then a second finder came a long and stated they found it too, and no one had signed the log before them. So then I'm like, "okay. so you're the first to find.." then the original FTF-er said, "no, I am! I didn't sign the log but here's a picture of the cache! I forgot my pen!" blah blah blah... After all that, I don't care anymore who finds what first.

Yep. Hobbies can cost money.

Oh. I stand corrected then. Thanks for the update.

I've only ran into one other cacher while out looking for them. We both knew what we were there for so we just approached each other, and introduced ourselves. I don't think there are any unwritten rules about what to do so I say just go look for the cache with whoever is already looking. It helps to have an extra set of eyes. If you don't feel like socializing that day, then wait them out. Or leave.

Yeah. You'll get a digital souvenir some time on Wednesday for the prior week. Either you'll get an email notification about it or it'll just show up.

As long as you're communicating with your local reviewer on when you plan to replace/fix the cache in question, there shouldn't be any issues. Reviewers will leave notes for you to respond, and if you decide to ignore those notes then they will archive your cache. If your cache gets archived, you can always ask to have it unarchived. But I wouldn't make a habit out of letting reviewers archive your stuff only to ask to have it unarchived because you all of a sudden became serious about maintaining your caches.

It seems you already have a clear understanding as to why caches in your area are published at those times. Read Keystones reply, and that should give you a more solid reason other than reviewers are just biased.

You should've signed the "unstable looking log" and called it good. Aside from wet feet, streams seem safe enough to walk through, no?

In my experience the majority of store owners are okay with it. I've never been asked to remove the cache or to tell the CO to remove the cache.

I know of folks who have asked for permission and it has been granted. There are a lot of caches in my area where store owners know about the cache and encourage them to be placed in their parking lots.

No one is trying to stop any caches here.

How cool would that be for a complete stranger to come knocking on your door asking about "geocaching". "Hey, there's a geocache icon on your roof, ma'am. Do you mind if I take a quick look around?" I don't see how any issues could arise from this.

I seriously doubt it would come close to this. I'm sure there are plenty of D5 caches out there to find who desire such challenges.

Parking lots are mostly on public property. There are some businesses in my area where caches have been placed, and the CO has noted in their description that permission was given. And that's apples and oranges compared to a cache icon in someone's backyard as opposed to one in a Walmart parking lot. If a cache icon (puzzle, traditional etc) popped up in my backyard, I would certainly email the CO to remove it away from my property, as probably you would too. If not, like Keystone said, there'd be newbies tromping through looking for non-existent cache containers.

Nah, I'm good. Thanks though.

It's supposed to be the CO that went missing.

I saw what you saw.