Reasonable Time

[+fatblokecaver]

Hi all,

I have re activated my cache (XXXXXXXXX) after it was seriously muggled, smashed up and nasty comments left in what was left of the log book. I have moved it to a more secure place which is a bit off the beaten track but close to 2 other caches I have an interest in. The question is - how long does it take for someone to have a go at it? - come on its not that hard!!!!!!

 

FBC

 

Edited by Lactodorum to prevent "cache advertising"

Edited February 9, 2008 by Lactodorum

[+Madyokel]

Hi all,

I have re activated my cache (XXXXXXXXX) after it was seriously muggled, smashed up and nasty comments left in what was left of the log book. I have moved it to a more secure place which is a bit off the beaten track but close to 2 other caches I have an interest in. The question is - how long does it take for someone to have a go at it? - come on its not that hard!!!!!!

 

FBC

 

Edited by Lactodorum to prevent "cache advertising"

Looking at your cache I guess I can answer some of your question..

In the cache's first location it scored 60+ hits which is not bad going at all.. However instead of archiving the cache and starting afresh you decided to "Relocate" the cache a good distance away.. However in doing this all the previous visitors are oblivious to this (Unless the are watching the cache).

So if they are your local 60+ cachers thay may be unaware of it.

[+purple_pineapple]

Hi all,

I have re activated my cache (XXXXXXXXX) after it was seriously muggled, smashed up and nasty comments left in what was left of the log book. I have moved it to a more secure place which is a bit off the beaten track but close to 2 other caches I have an interest in. The question is - how long does it take for someone to have a go at it? - come on its not that hard!!!!!!

 

FBC

 

Edited by Lactodorum to prevent "cache advertising"

Looking at your cache I guess I can answer some of your question..

In the cache's first location it scored 60+ hits which is not bad going at all.. However instead of archiving the cache and starting afresh you decided to "Relocate" the cache a good distance away.. However in doing this all the previous visitors are oblivious to this (Unless the are watching the cache).

So if they are your local 60+ cachers thay may be unaware of it.

 

and even if they are aware that it has moved, they may be unlikely to log it, as this would result in the same cache logged twice, which can really make your stats look wonky!

 

Dave

[Alan White]

We've done that cache and, as others have said, we wouldn't revisit a cache that retains the same GC number. Our policy (and we suspect that of many others) is "one GC number, one find". Except where the cache is intended to allow multiple logging, though we would still choose not to.

 

I did see the coordinate change notification and thought "that's a long way to move a cache" but we've found it so I deleted the notification and moved on.

 

I think the general advice would be that if a cache needs to be moved that far then it's best to archive the original and create a new listing.

[+SidAndBob]

We've done that cache and, as others have said, we wouldn't revisit a cache that retains the same GC number. Our policy (and we suspect that of many others) is "one GC number, one find". Except where the cache is intended to allow multiple logging, though we would still choose not to.

That's our policy too, though we're getting dangerously close to bringing up that cache again.

[+Bambography]

This is actually one of my nearest caches. Only this weekend was I out looking at the map on the GPS wondering when 'that new cache' had appeared without me noticing.

When I looked into it I found it was the relocated cache i'd already done.

I have to admit although i'd probably do it again at some point, if you archive and launch it as a new cache (which is what should have been done IMO) then i'd have probably been out there one evening by now.

I'd change it if I were you.

[+fatblokecaver]

Archived it, re named it - now get out and find it

 

FBC

[+Bambography]

*watching and waiting*

[+fatblokecaver]

*watching and waiting*

Posted today found yeaterday

FBC

[+maxkim]

problem solved then.... LOL. Cheers MaxKim

[+Bambography]

Didn't take long. Sadly not by me though. Been a little busy at work this week otherwise i'd have been out there!