Thot

Changing from Traditional to Multi

14 posts in this topic

Can you change a Traditional cache to a Multi?

Share this post


Link to post
Share on other sites

It's grayed out when you edit a traditional, so I presume you'd have to get PR to change it or republish.

Share this post


Link to post
Share on other sites

Since there are additional checks on a multi (since the way points have to be checked to compare to other caches), I expect that the change would have to be approved.

Share this post


Link to post
Share on other sites

YOU can't change it, but a reviewer might be able to.  Since it changes the hide significantly, he'll probably tell you to just archive it and create a new listing.

Share this post


Link to post
Share on other sites

I feel sure our pleasant cooperative reviewer will be happy to change it for me.

 

Share this post


Link to post
Share on other sites

Thot, when did you move out of Texas?

2 people like this

Share this post


Link to post
Share on other sites

You learn something new all the time.  If I understand this correctly, you can submit a new cache at the location of an existing cache and wait.  If/when the existing cache is archived you're submission is first in line to take the location.  I nearly stumbled into this while converting my existing traditional to a multi.  In order to get the multi approved I'll have to archive the traditional when submitting the multi.  With a lurker waiting, like I just explained, he'd  be first in line and take my location.

Apparently there's an unspecified limit to the time you can lurk. Typically somewhere around a month.  I guess it's at the discretion of the approver.

Edited by Thot
1 person likes this

Share this post


Link to post
Share on other sites

Slightly off topic, I had an unpublished puzzle cache from 2009 that I built just to put trackables in.  I never intended to submit it for review (though it would be fun to publish a brand new cache today with a GC code that started with GC22), so it just sat there.  Well, about 10 days ago, Groundspeak archived it.  Their log stated:  This old, unpublished cache has been archived as part of site maintenance and database clean-up. You are not required to take action. If you are working on a new cache, create a new listing and submit it for review. Should you prefer to use this listing, contact your local reviewer to request unarchival. See [this Help Center article] http://support.groundspeak.com/index.php?pg=kb.page&id=200 to identify the reviewer for your area. In the future, please work to submit cache pages for review within three months of creation. If you are working on a complex cache, or are waiting on permission, communicate your progress by posting regular reviewer notes to unsubmitted listings. Submissions older than six months may be automatically archived.

It doesn't really matter to me because my trackables can sit in an archived cache was well as an unpublished one.  I just thought it was interesting that it took them 7 years to decide they needed to do site maintenance and database clean-up.  https://coord.info/GC22E34

 

Share this post


Link to post
Share on other sites

HC - I've had several I had been working on over the years have that happen.  Surprised it took so long, too.

Thot - The easy way for this to submit your new cache at the same location and then archive the old.  Your new cache is already in queue when you archive it (even if minutes before) and any lurker will have a submission in queue after yours.  Never had an issue.

Share this post


Link to post
Share on other sites
52 minutes ago, cachestacker said:

Thot - The easy way for this to submit your new cache at the same location and then archive the old.  Your new cache is already in queue when you archive it (even if minutes before) and any lurker will have a submission in queue after yours.  Never had an issue.

I think you're missing the point of my post.  Assuming you submit the new cache and archive the existing cache in the same day.  If there's a lurker who has submitted a cache at your location earlier and just standing by, they'll get your location, because you just created the replacement and he submitted his earlier, so he's ahead of you in the queue. 

Edited by Thot

Share this post


Link to post
Share on other sites

But do you think these difficult to place locations you currently have are being lurked on that much?  And, in reality, PR would get pissed that someone keeps submitting, as it will keep coming up in the queue when there is an existing cache there.  That will only be tolerated so long.  They send back to the submitter and after a while I presume would just archive the submission -- unless the cache is gone.

I just don't imagine that strategy working very well.   Not for the choo choo series.

Share this post


Link to post
Share on other sites

I discovered this phenomenon because it's happening to the cache I want to change to a multi right now.

Share this post


Link to post
Share on other sites

I guess PR told you there was a cache in the queue (the lurker) for your location?  How else would you know?

Is this the cache you've been having so much trouble with?  I guess the lurker must be your cache thief!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now