Forum Replies Created
-
AuthorPosts
-
@sandlanders wrote:
Now, when I first got into these forums, I didn’t know who anyone was, who was serious and who was joking, and what all the insider comments meant. Some of it I still don’t know, but in case you’re totally confused now, Sparki2003, just let me know what you need translated.
Most of all, DO NOT SEND ANYONE ANY MONEY!!!!!!!!
Does that mean I have to give back all the bribes that Marc gives me to publish his caches? 😆
You know, this is what happens when you go caching in Illinois. I understand that these flatlanders have nothing better to do than follow around Wisconsinites and stash live (and dead) rodents in cache hiding spots as we approach. Next time, you better just head north!
You can email me if you want help with this. Note that the owner has changed this puzzle since initial publication, without changing the waypoint coordinates or warning those who might have solved it in the past 😡 , so be careful using someone’s solution for this. It is also possible that the geochecker was not updated.
Getting some interesting choices, keep up the submissions, folks!
04/13/2009 at 9:52 pm in reply to: Summer trip, cache recommendations Snoqualmie Pass and rout #1905572While you are out there, be sure to stop by Groundspeak HQ. They have a cache there for you to find, but they got tired of people dropping by unannounced and archived it. The cache does still exist, however. You just need to write them in advance and they will give you the coordinates to the lilypad.
And, of course, you need to visit GCGVOP to make the Ape/HQ/OS trifecta.
I kind of doubt it is coming from the P&R folks. They usually do a better job of training the kids. Thanks for the offer, though. I keep waiting for someone to tell me that their “teacher” never mentioned that there are guidelines, so I can probe more.
As with all geocaches on DNR land, you need to have permission to place caches through the notification form available on the “Hiding a Cache” page. I’m not aware of any blanket restrictions, but often these areas are limited access to avoid disturbing nesting birds, so permission might not be available.
When you get a PQ, it contains the five most recent logs, plus any logs by you, so it is sort of a PQ limitation. The trick is to not delete your database and load your new queries into the same database.
For example, I have a database called Rochester in which I load a PQ of the 500 caches closest to my home. I get these weekly. Each query has a different set of logs, and GSAK retains all of them as more are loaded. The catch is that after you load you need to go through the database and manually mark caches not loaded as either archived or disabled (or still ok). You could eliminate part of this work by including disabled caches in your PQ, but I like to get the maximum number of active caches.
There is a macro which will just delete all caches not loaded during the most recent PQ, but I prefer to keep the disabled and active caches and only get rid of the archived ones.
There is also a macro that will go to site and get all the missing logs, but this is a bit slow, as you might expect, and really isn’t designed to add logs to more than just a few caches.
@wooden_nickel wrote:
So how about a Liars cache?
Is requiring an embellished log for example still acceptable or is that considered an ALR?
Yes, if it is REQUIRED. Optional is fine.
Hurray, I was wrong. The bike ride is on Sunday. There is a foot race on Saturday morning, however.
@Greendale4X4 wrote:
I was just notified that the event will be held on Saturday. 😀
Keep checking their website for more info.
-Jason
Ugh, that isn’t particularly good news. I think there is an organized bike ride in the area on the same day. Be careful out there, folks.
@Lostby7 wrote:
So would I be correct in assuming that travel bug “prisons” which require a trade in order to move bugs are now optional as well? So who is responsible for replacing the deleted logs once cache owners delete the finds? The reviewers? Don’t they already have enough to do?
I just think this causes more problems than it solves…
It would, but these threats were already not allowed before the guidelines change. Travel bugs and geocoins belong to their owner, not the owner of a cache, so cache owners are not allowed to dictate what happens to the bugs in their cache. To be honest, I’m not aware of anyone threatening to delete logs if someone doesn’t follow their trading rules, but maybe there are a few out there.
@marc_54140 wrote:
@gotta run wrote:
@Team Deejay wrote:
The following is a list of all the challenge caches in Wisconsin that I am aware of. None of these require any modification:
GC15JH6 Crazy Retro Driver’s Wanted!
GC1P8AF WSQ 000 The quest ….Now see, even here this gets fuzzy. The “challenge” part of “Crazy Retro” is to find the puzzle caches. But the cache requires the log be formatted in a particular way. Is that an ALR?
Same goes for WSQ 000. Not only do you have to find 66 caches, but you gotta post in your log when you found them all.
No, I do not see these as ALRs. It’s just the way of saying “I have completed the other caches”. Probably a subtle difference ……
This is a correct interpretation. Incidentally, I missed “The Cheesy Well Rounded Cacher” on my original list, as it is listed as a LBH, rather than mystery. Just an oversight on my part.
If you head there for this event, don’t forget to pick up GC1FK3M while you are there.
I do apologize for not posting to this thread earlier. I have been busy hosting an major event (not geocaching related) and didn’t see the change was made official until now. Most of the factual posts to this thread are indeed correct. Here are the highlights:
1. All existing ALRs will need to be converted to optional additional tasks. The cache owner can ask finders to perform these tasks voluntarily, but not delete their logs if they don’t. You are allowed to suggest that those not performing the tasks that are lowdown no-good offspring of farm animals, but you cannot delete their online logs if they signed the logbook in the cache.
2. All of the current challenge caches published in Wisconsin are fine as is, including the “How Hungry” challenge and Marc’s WSQ 000 cache. To be an acceptable challenge, the challenge must be geocaching related, reasonable, and performable before finding the cache. Note that taking photographs is not considered geocaching related, but waymarking type challenges would be allowed.
The following is a list of all the challenge caches in Wisconsin that I am aware of. None of these require any modification:
GC14B96 BBIINNGGOO!!
GC15JH6 Crazy Retro Driver’s Wanted!
GC15WT3 Badger State Challenge – 72 Counties
GC17Y36 Northwestern 12 Pack Challenge
GC1A1Q8 EarthCache Tic-Tac-Toe
GC1AQ1P T & B’s “How Hungry Are You?” Challenge
GC1DCTE Laughing Waters | You’re Outta Here
GC1HMCJ WSQ – Shawano County Cemetery (SCC) Challenge
GC1JMFG DeLorme Challenge: Unique Natural Features, A.S.
GC1NZNF Wisconsin Alphabet of Places Challenge
GC1P3CQ WSQ 998 Alphabet of Cemeteries Challenge
GC1P8AF WSQ 000 The quest ….
GCXPZR Wisconsin DeLorme ChallengeIf you think your cache qualifies as a challenge and I missed it, just drop me a note.
3. This change does not affect to those caches which require you to find a bunch of caches, where information for a final cache is contained in each of (or some of) the caches. These caches are all fine and require no changes. It also does not affect to any sort of puzzle cache, including monkey puzzles, lockboxes, and other physical puzzles. Those are all fine. Of course, if you have an ALR along with the regular puzzle, that will still need to change.
4. This change does not apply to earthcaches, grandfathered virtuals or grandfathered webcam caches.
5. My understanding is that you MAY choose to change your cache type from mystery to traditional (or multi), but that this change is not required. If you desire to change the cache type of your ALR cache, please drop me a note and I will change it for you. I’m sure those who didn’t like the reduced traffic caused by the mystery designation will appreciate the opportunity to change their cache type.
In closing, as Bec said, our opinion on this change really isn’t important. We are just charged to enforce the guidelines as instructed by Groundspeak. If you have any other questions not answered by this post, just drop me a note.
Dave
-
AuthorPosts