› Forums › Geocaching in Wisconsin › General › Cache type reassignment

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • 03/08/2010 at 2:35 am #1729713
    HeliDood

      Due to circumstances, I was left with no choice but to archive one of my caches.

      Anyone who’s familiar with my “Lake Biron Mystery” may be familiar with this one, it was called “Strike A Cord”. A simple, yet awesome little micro cache of mine.

      This ‘traditional’ cache was one of three requisite caches to unlock the “Lake Biron Mystery”, a mystery/ puzzle Island cache.
      Since on of the requisites was taken out of the game, I chose to archive LBM, and relist it as a Traditional type.

      Question #1: To change a cache type, was archiving- relisting the only way to accomplish this? In other words, Did I do this right?

      Question #2: LBM has been archived is now relisted as a “new” cache. The location, container, logbook and all its contents have not changed. Its the exact same cache, only relisted. So therefore, any previous finders of LBM that wish to log the new listing should have the older of the two logs deleted so there is no double smiley. Agree?

      Now for my Dilema: I’ve got to somehow figure out how to pull two TB’s from the old listing and drop them into the “new” cache without having the tracking numbers. (the ice is too thin to cross, will have to wait until the water opens up so I can get a boat across)

      03/08/2010 at 3:01 am #1924505
      Team Black-Cat

        Archiving and re-listing was the best way to go. (Maybe the only way, dunno.) Changing the type would change previous finders stats and some cachers don’t respond well to that.

        The best way to get the trackables moved is to contact the owners and explain things. Otherwise, the next finder can just grab it from the archived cache without any issues.

        03/08/2010 at 3:05 am #1924506
        HeliDood

          I regret not having the coin #’s when I did the archive-relist.
          I looked at the coin pages and I saw there is an automatic note posted, saying their last known location had been archived.

          I was sure to post a note explaining exactly what happened.
          Since I don’t have the numbers, the coin owners may be able to move the coins themselves as soon as the new listing gets published. (GC24R2A)

          03/08/2010 at 3:44 am #1924507
          HeliDood

            It turns out that my original idea to limit cachers to one smiley between these (now two) caches is an LDR (additional logging requirement), so thats a no go..

            But they do have to return to the cache and sign the log if they want another smiley, and it is a Terrain ★★★★★, so I guess its a win-win.

            If by stating, “If you’ve signed the logbook prior to 3-7-2010, you’ll need to resign the logbook to obtain your smiley” (or something like that), thats not an ALR, right? Thats just keeping people honest. Agreed?

            03/08/2010 at 3:56 am #1924508
            sandlanders
            Participant

              You could just say, “This is a new cache very similar to one that was here before. Find the cache again, sign the log book again, and get another smiley.” Or something like that.

              Since it IS a new cache (new cache number, etc.), it’s just like you put out a totally different new cache, except those who found it before might have a bit of an edge on finding it again, if it’s in the same spot.

              03/08/2010 at 4:02 am #1924509
              HeliDood

                That sounds good, too.

                Just decided on:
                “Only logbook entries made 3-7-2010 and later count for “Biron Pleasure Island”. Earlier entries are valid only for “Lake Biron Mystery.” Its a new cache with a new cache number, so feel free to make a return visit even if you’ve been here before.”

                I guess thats tactful enough.

              • Author
                Posts
              Viewing 6 posts - 1 through 6 (of 6 total)
              • You must be logged in to reply to this topic.