Delta68

Yay! Thanks for the replies. I'd added the \ and it works a treat now! Thanks

I've just bought Cachemate and I am trying to get the link in Memory Map to work When doing a MemoryMap export from GSAK I've specified cmate:%code as the link but when I load the .csv file into MemoryMap this changes to include the path. In this case, when I view the properties of a waypoint it says C:\Geocache stuff\cmate:GCVWD4 for example. C:\Geocache stuff\ is where the .csv file was when I imported it into MM Neeedless to say, this link thne won't work on the Mio. How can I stop it from changing? The .csv file has it correct.

OK, It's not exactly straightforward. Create your variable and assign a value to it where you want it to be a random number. 0 will be fine. Save and close cartridge Open the .lua file in a text editor and put this sort of thing in the Author Function area -- #Author Functions Go Here# -- function throwDie(k) return ( math.random(1,6) ) end -- #End Author Functions# -- find where your variable was being assigned a value and replace the 0 with a call to the function eg: dieValue = throwDie() Save the file and reload into the builder Done! ps. You don't appear to need to include require "math"

Just to re-iterate what everyone else has said: Sorry to see you go Lacto and thanks again for all the help/tolerance From all of us!

Our latest Wherigo will NOT run in the emulator and it CANNOT be completed by opening the .gwc file in notepad. Even if we were to make the source code open-source it would still not be possible to complete it without visiting actually visiting the intended location, answering the questions and actually finding the cache!

Any idea if it's possible to run this on a laptop using an emulator? May sound cumbersome, but we already use Memory Map on a laptop while in the car - getting the gps signal from an Etrex. It's great on a big screen!

You can already do this. Don't forget to include require "math" as well though!

I like this idea! It would keep a series of caches grouped together nicely We don't normally have a problem thinking of cache names. All our early caches were always two words to make them more memorable and have only strayed from this rule when a longer name was more logical. On two occasions they are just anagrams of the location Our puzzle cache names are usually either a clue or deliberately vague....

From the cache description: "Viel Spaß" Yet the attributes warn of hunting, ticks and thorns Doesn't sound like 'viel Spaß' to me!

..and judging by the pile of fakes we found in one cache last weekend, some must have quite a few coins in their collections which aren't rightfully theirs as well

Brilliant!

Hmm... conflicting ideals I think. I suppose it depends what GPS you're using....

When setting a series of caches intended to be done in one go is it best to: A) Use a series name followed by a number Pros: It's easier to see the intended route Cons: If one has to be archived it looks strange Can give the impression that the setter couldn't be bothered Makes it difficult to recall each individual cache when logging finds B ) Individual name for each cache Pros: If one has to be archived, it's not so noticeable Cachers won't feel obliged to do find than they are comfortable with... perhaps Cons: Can take lot of effort thinking up individual and relevant names C) Alphabetically ordered unique names Pros: It's fairly easy to see the intended route If one has to be archived, it's not so noticeable Cachers won't feel obliged to do find than they are comfortable with... perhaps Cons: A major challenge for the setter I suspect Any comments?

Yes! I thought that, although it's the book Rita Hayworth and Shawshank Redemption that springs to mind more than the film though. The part where he is instructed to look by a wall in a field for a stone which has no right to be there. I wonder if it had the official Groundspeak logo on it..... Mark

At risk of drifting off topic here... AND if the owner INSISTS that the cacher has to grab the picture as intended: not just allowing a photograph taken at gz

Losing web-cam caches would be no great loss anyway Is there a list of 'Classic Caches'? Are there any recent classics?

Perfect! It was going to be an Unknown requiring 'Special Equipment' anyway. Thanks

99% of the time, if one team signs the log book on behalf of another team no one cares. However, if the cache is hard to get to and this fact is reflected in the terr-diff rating, would it be acceptable to ask for proof (photograph for example) that at least one member of the team actually reached the cache? Or is there a better way?

How about if you log a find just before it's due to run and delete it again afterwards.

Whispers spread across the back of the hushed room: "He said the 'P' word..." In the Harry Potter books, no-one mentions Lord Voldermort by name... I'll start by saying you don't need permission to place a cache in your own front garden

I've just submitted our second Wherigo and basically I've created the cache page with hidden final co-ordinates (as you would with a multi) and asked our local approver to have a look and see if it's ok without publishing it. He will then (hopefully) say it's fine and remove it from the review queue. I will then set the Wherigo active and ask the reviewer to publish. This seemed to work fine last time as it was then published within a couple of hours anyway. Even if someone did spot it on the Wherigo site I wouldn't be too concerned...

There is no need to include the .gwc file as this gets compiled on demand when a player downloads it

I agree and I wasn't really wingeing or moaning just asking opinions:) I think this thread can be closed now

We saw this geoclutter in Swan Lake and just left it there. I made a note of the tracking code but what's the point in discovering a piece of laminated paper? I've seen this sort of thing dropped into the TB Graveyard before so I know others think it's a bit of a cheek as well...

It's not just FTFs that people throw their dummies out the pram over; we once received backlash over a geocoin we moved on!