Vooruit!

I thought MediaWiki was written in PHP? Anyway, I've had some issues in the past with installing Pear as well, it can be a real pain. No experience with MediaWiki itself though, but I'm willing to give it a try on my own server in case you lack the time!

Very much appreciated guys. Being relatively new to the Wherigo scene, I'm feeling pretty helpless at the moment.

Anybody, please? At the moment, I don't know any resource that covers the Wherigo objects with their methods/functions. Looking at some other Wherigos (such as Whack-a-lackey) helps, but nonetheless I would be very grateful for an overview of everything that's available. Thanks in advance!

And whaddaya know: I got an email complaining 'the cache appears to be gone'. Haha, I love this!

A cross-platform solution for string hashing would be greatly appreciated. It just makes it that extra bit harder to just look at the code at pick up the requested answers. Btw, another 'trick' I've used in my latest cartridge to avoid Wherigo hacking (which is, unfortunately, very common here in the Netherlands): I've named one zone 'Geocache', with some text describing where the cache ought to be hidden. In the field, however, there's only an empty petling holder. When someone sends me a message or logs a DNF saying the cache is gone, I know exactly what has happened. Obviously, the zone isn't actually used in the Wherigo. At no point it becomes active or visible. The real cache zone has a non-descriptive name, and it's changed to 'Geocache' at runtime (by a hopefully non-clear method).

Dirk, thanks for the follow-up, much appreciated.

Great work guys. Keep it up.

Is there perhaps a quick method to make a cartridge Garmin-proof, with which I mean: make it so that a maximum of 5 zones are active simultaneously. I'm thinking of some sort of generic piece of LUA that can be pasted into the On Proximity event, that checks how many zones are currently active, and deactivates zones that are furthest away if necessary to avoid having too many zones active.

Just want to say thanks once again, both to you, charlenni, and others that have helped me in other threads. My first Wherigo has just been published, and the first log is already quite encouraging! On Garmins though, the cartridge crashes immediately, but that was to be expected, having 10+ zones active at the same time. I cannot be bothered by that however, everyone having a smartphone anyway.

Many thanks, I'll try that! edit: It works like a treat! Thanks again!

Here's a stripped version of my cartridge. To illustrate, here are 2 screenshots of the emulator. First, we're at approx. 150 meters distance from the zone 'Emmer dode vis'. There's only one zone visible: Haaienmeer. Now, I've moved the little dude to less than 100 meters from the zone 'Emmer dode vis'. Now it has become visible!

Maybe it's not a problem, but just something I took for granted using the emulator and WhereYouGo. What I would like is some zones to become visible only when you're at most 100 meters away from them. I thought (incorrectly?) the Urwigo setting 'In range' was supposed to make it work like that. The 'On distant' and 'On proximity' events are empty, i.e. not defined. Again: in the emulator and on Android, it works as desired, but on the iPhone, not so. Should I use the 'On distant' or 'On proximity' event? But then, how would I hide the zone again when the distance becomes more than 100 meters, since there is no 'Out of distance' event? I'll make a test cartridge, thanks in advance!

Is there any way I can run the iPhone app in Windows, with an emulator or something? Boy, was developing ever frustrating! Different devices that behave differently, with no way of knowing beforehand if and how the cartridge will work... and knowing no one with a Garmin, I won't be able to test, let alone support those devices at all. The whole concept of Wherigo is just so promising, but as things stand right now, it's just one big disappointment. There ought to be zillions of Wherigos out there, but in fact there are only a couple of 'em, and that's in the Netherlands, an extremely densely populated country with a thriving community. OK, having vented my frustrations , I still would really appreciate some feedback on my question in the first post. All things considered, I really want to publish that first Wherigo, with hopefully many more to come! Lack of creativity is certainly not the issue here...! Thanks guys!

The Wherigo I'm working on consists of zones that have to be visible at all times, and 'item' zones, that should be visible only when you're at most 100 meters away from them. Using Urwigo, I thought I'd use the 'In range' setting, and sure enough, both the emulator and the WhereYouGo Android app show the behavior I aim for. So far, so good, but unfortunately the iPhone app seems to ignore this setting? I made a friend do a test run of the cartridge, and she just sees every zone, no matter the distance! Am I overlooking something, or this is another item of the list of differences between the various Wherigo devices...? edit: I know the image says the selected zone is inactive; it gets activated programmatically when entering the initial zone.

Normally, in development threads it's a nono to ask for ETAs, but this community being so friendly, I can't help myself asking how things are going. Really excited about the whole WF thing!

It would be very nice to have support for OpenStreetMap. Bing Maps (and, previously, Google Maps) show mainly the paved roads, and for Wherigos, it's the little paths that are way more interesting.

Though I don't use Kit, I nevertheless want to say thanks for all the time and energy you've been spending in the Wherigo community and, on top of that, been helping it with this nifty tool! And congrats on the forthcoming 50k finds.

http://wherigobuilder.wikispaces.com/ seems to be down: Might it be that's is online elsewhere? I found this wiki very useful.

Traditionals: still my favourite, and lately getting more and more into the more extreme (T3+) ones. Multis: only short ones. Medical reasons there... Mysteries: seems like I'm ignoring these more and more. All too often, the puzzles are just not that well put together. I certainly have a look at the # of favourites before going for one of these. Virtuals & webcams: really wish there'd be more of those around here (Netherlands). They're cool! Why they've stopped allowing these is beyond me...

Thank you charlenni. Yes, I tend to agree. Strangely, other zones DO vanish at once when they are disabled. I'll report the bug to the developer. As for the Garmins having this limitation: it seems so... non-2014'ish, having your creatitivy being limited for such stupid reasons. I guess an alternative would be to ignore the Garmins? Not something I really want to do, but in my opinion the zones (being cards) just have to stay visible at all times.

I'm creating a Memory Wherigo, and running into a small problem: in the emulator, when hiding and deactivating the current zone (in this context meaning the player has just picked up a card), it immediately disappears from the map, which is exactly what I want. In WhereYouGo however, the zone only disappears after the player has left it. Could it be that disabling the current zone is some sort of illegal action, which should not be done? The fact that different Wherigo implementations show different behavior makes me wonder... Also, is it still true that you shouldn't have no more than X zones active at the same time? This being a Memory game of 8 pairs, so making 16 zones in total, I'm wondering whether it is at all possible to create this kind of game as a Wherigo? Thank you.

Never realized 'micro' was defined as everything less than a certain size. For some reason, everyone in this region (The Netherlands) uses 'Other' for nano-sized caches... My question was meant in general however. Another example would be a (regular-sized) birdhouse with only small space available for the logbook and other items. This would still be a regular-sized cache? And what if, for weather's sake, the birdhouse contains a small-sized box with the logbook?

I'm wondering: what exactly defines the size of a geocache (micro/small/...)? The size of the container, or the size of the available space within the container? For instance, one of my caches is a pinecone, which IMO would qualify as micro, but the space within is nano-like. I've gotten some complaints I should change the size accordingly. However, I would think that the given size is supposed to be helping you find the cache. Not having found the cache, isn't the size within the container irrelevant?

Well, it looks like my problem is solved by not having zones so close to each other, so I'll give them some outer margins. A pity, but not really a big deal. Thanks for reading this anyway.

Building my first Wherigo, I had the idea of creating a 10 x 10 maze. Not too complex, one would think. Nevertheless, I'm running into some problems. -- For the sake of brevity, I'll consider just Consider just a small part of the maze: |21|__ |11|10| <-- 10 contains an item (key) |01 00| ------- Naturally, I've set up OnEnter events for each zone, so that, for example, when entering zone 10, zone 01 will be deactivated and made invisible. Zone 10 contains an item, which is automatically picked up when entering it for the first time. An accompanying message is displayed saying 'You've found the key!'. Now, the problem I seem to be facing is this: in the emulator, moving from 00 to 10 and then back to 00 works as expected: - 01 is invisible when 10 is entered; - The key gets picked up, with the messagebox saying so; - When returning to 00, 01 is visible again: all is well. When in the field however, using WhereYouGo: - 01 is invisible when 10 is entered; - The key gets picked up, with the messagebox saying so; - BUT: with the messagebox gone (the player having clicked OK), the former zone (00) is still shown as INSIDE! - So, when (physically) moving back to 00, WhereYouGo thinks this zone has been never left at all, so no OnEnter is called. So, 01 stays invisible! For some reason, displaying a messagebox and/or moving items to a player creates some sort of halt to the process responsible for updating the list of zones the player is inside of. This is driving me nuts... I'd be very, very grateful for any hints that would help me out. Thanks.