Is this meant primarily for new Challenges? Challenge based on elevation would be against the guidelines. Source of criteria Challenge cache criteria - must come from information broadly available on Geocaching.com such as on the statistics page, cache placement dates, types, attributes, souvenirs, etc. - must be verifiable through information on Geocaching.com. Geocaching.com doesn'by magma1447 - Method requests
As vogelbird says. It's against the Guidelines to create such challenge. It has been tried, including appeals. HQ does not approve.by magma1447 - Method requests
I have an update from HQ. Challenges affected by this are considered "old" and were allowed when they got published. Therefore they have decided that they are allowed to keep using the old polygon data, just as their cache descriptions says. So, for those where it's possible, we can convert the checkers into using a polygon script, if we have the polygon data. I still have Prby magma1447 - Checker news
That's actually quite good in my opinion. That's how I expect most of these Challenges will be solved. I haven't heard from HQ yet though. I expect that to take at least a week. Therefore I think that script developer had a smart approach on things. The question is if it should have been allowed by the reviewer though, but that's a bit off topic here, not really our concern.by magma1447 - Checker news
I have asked HQ regarding Challenges that uses the old definitions. As I see it we have two options: 1) Force-archive Challenges using counties that doesn't exist anymore. 2) Create new Challenge checker using user-defined polygons. User-defined polygons aren't allowed for new Challenges. But as I see it, this is a different case. The Challenges already exists. We'll see hoby magma1447 - Checker news
Scripts 731 Left enabled Defaults to county = 'Ski' Affected tags: https://project-gc.com/Challenges/GC6JZGH/21077 https://project-gc.com/Challenges/GC5E54W/5917 The first is unused, the second is used by an active challenge. I will disable the second challenge and leave a comment.by magma1447 - Checker news
Scripts 826, 1463, 1495, 2486, 2489 Left enabled Not using county "Re", it's chemistry elements.by magma1447 - Checker news
Script 535 https://project-gc.com/Tools/Challenges?edit&scriptId=494 Left enabled Not using county "Re", it's chemistry elements.by magma1447 - Checker news
Script 494 https://project-gc.com/Tools/Challenges?edit&scriptId=494 Left enabled Not using county "Re", it's chemistry elements.by magma1447 - Checker news
Script 1004 https://project-gc.com/Tools/Challenges?edit&scriptId=1004 Left enabled Using its own polygon data so won't be affected. It's likely that the related Challenge actually is against the Guidelines though. It would fall with user-defined polygons.by magma1447 - Checker news
Script 578 https://project-gc.com/Tools/Challenges?edit&scriptId=578 Left enabled The script has a default setting for region which will become unusable. The following tags rely on this default setting: https://project-gc.com/Challenges/GC52WBF/1729 https://project-gc.com/Challenges/GC52WMN/1731 https://project-gc.com/Challenges/GC52WMZ/1732 The related challenges are archived so I wiby magma1447 - Checker news
Script 873 https://project-gc.com/Tools/Challenges?edit&scriptId=873 Disabled Needs a new checker that requires the Geocacher to have found all geocaches in a county within a list of counties. That list should be the counties that used to be in Hordaland. Hordaland-counties: * Askøy * Austevoll * Austrheim * Bergen * Bømlo * Eidfjord * Etne * Fedje * Fitjar * Fjell * Fusa * Grby magma1447 - Checker news
Potentially affected tags (config matches a region/county that has been added/removed): tagId:5140 creator:Target. gccode:GC51QTB matches: tagId:16983 creator:vogelbird gccode:GC5FD2Q matches: tagId:16984 creator:vogelbird gccode:GC5FYZD matches: tagId:17002 creator:vogelbird gccode:GC568Q7 matches:by magma1447 - Checker news
Potentially affected scripts (source code matches a region/county that has been added/removed): scriptId:873 creator:kro8 scriptName:Alle cacher i en kommune i Hordaland matches: scriptId:578 creator:Draupne scriptName:Generic number of finds in region matches: [Østfold] scriptId:1004 creator:bjoff scriptName:SognOgFjordane, using boundaries from 31.12.2019 matches:by magma1447 - Checker news
Counties only in Norway: Agdenes Askim Audnedal Balestrand Ballangen Berg Bjugn Bø (Telemark) Eid Eide Eidsberg Fet Finnøy Fjell Flora Forsand Fosnes Fræna Fusa Førde Gaular Granvin herad Halsa Haram Hemne Hobøl Hornindal Hurum Jondal Jølster Klæbu Kvalsund Leikanger Lenvik Lindås Mandalby magma1447 - Checker news
Regions only in Norway: Akershus Aust-Agder Buskerud Finnmark Hedmark Hordaland Oppland Sogn og Fjordane Telemark Troms Vest-Agder Vestfold Østfold Regions only in _tmp_Norway: Agder Innlandet Troms og Finnmark Vestfold og Telemark Vestland Vikenby magma1447 - Checker news
After a lot of work, it seems like we can finally update the polygon data for Norway. They have merged a lot of counties, also the regions will change. The reason it has taken time is that the site used to use (https://wambachers-osm.website/boundaries/) doesn't exist anymore. An old version of his existed at GitHub as open source and our initial plan was to try to use that. But everythinby magma1447 - Checker news
Example tag: https://project-gc.com/Challenges/GC3CZKJ/8852 The script code never considers the last find date from the user. The first if-part of the find-loop needs to be used when the loop ends as well.by magma1447 - Script development
pieterix Wrote: ------------------------------------------------------- > I'm happy to create/modify scripts to cater for > Lab Caches, but not if HQ is just going to rip the > carpet from underneath us. So who will be able to > ask HQ as to whether/where they will be allowed in > challenges? I don't have any good contact for this. In my opinion, the best thing iby magma1447 - Method requests
I haven't updated myself on the topic. I assume nothing has changed.by magma1447 - Method requests
I don't think this thread is the right place for that discussions. But since it's possible to write such script, it's possible to change the script into handling it. I can't answer for how hard it is since I don't know the script. It can possibly have unintended side-effects on other features in the script. It could very well be smarter to create a new script, that doeby magma1447 - Checker news
That script doesn't support Lab Caches, like most aren't. It just happens to have a copy/paste-block with the name and an icon. It's not fetching Lab caches from the API for example. There probably aren't many active scripts handling Lab caches, probably even fewer that hasn't been created this year, if any.by magma1447 - Checker news
I had used the name 'Lab Cache' in Profile stats as well. I have changed the LUA callback to that now, and am preparing a release. Expect it to be live in ~5 minutes.by magma1447 - Checker news
PattuX Wrote: ------------------------------------------------------- > On gc.com it's 'Lab Cache' btw. I guess it doesn't > break anything but consistency is always nice. I'll update to 'Lab Cache' before the release. If I forget, please remind me.by magma1447 - Checker news
PattuX Wrote: ------------------------------------------------------- > https://project-gc.com/Challenges//46972 > > > local finds = PGC.GetFinds(profileId, { > includeLabCaches = true }) > > works correctly. > > > PGC.GetFinds(profileId, { includeLabCaches = true, > fields = {'gccode', 'cache_name', > 'visitdate',&by magma1447 - Checker news
Still? Or was it just a shorter issue? At times the database cluster serving the data stops responding and has to be restarted. We haven't figured out exactly when and why. One more related issue was solved a few weeks ago, but there is still something weird happening now and then. It was restarted around 11:00 UTC, not sure how long it was broken for.by magma1447 - Checker news
Found a sloppy error. After adding the Labcaches I need to re-sort the data. The code did a $data = uasort(...); But PHP's uasort() doesn't return the result, the parameter for the data is a reference, so it's sorted in-place. $data was set to TRUE because the sort was successful. I of course know that uasort() doesn't return the result, so it was surprising to find the error.by magma1447 - Checker news
I will look into this. Maybe it doesn't work as it should. If you haven't heard anything on Monday, please remind me. Right now I am trying to not lose focus on the 360-tool for the The All Around Cacher. Got so many notes about it here that I want to implement most of it.by magma1447 - Checker news
Rikitan Wrote: ------------------------------------------------------- > Hello, > > checkers are now a bit unstable, more timing-out > than not. > Reading through recent posts above me, is there a > chance that challenges (pun intended:) with CPU > consumption will be improved in near future? > > Thank you. I have felt that the relevant database cluster wby magma1447 - Checker news
Just go for it, I can't see any side effects besides heat and high power usage. I was mostly surprised of seeing how well the servers scaled. I recently adjusted some parameters so that they scale out better.by magma1447 - Checker news
