Thanks, fixed it and changed it to 100 Mysteries / 3 of those in Texas.by PattuX - ARCHIVE Checker requests (completed)
Here you go: https://project-gc.com/Challenges/GC8GK1F/46976 Let us know if it's suitable.by PattuX - ARCHIVE Checker requests (completed)
This is against rule 10 of the challenge guidelines: QuoteMot allowed: Challenges based on geographic areas other than countries, states/provinces, counties (or their local equivalent). For example, user-defined mapping polygons, latitude/longitude, radius, etc. In case you mean distance to home coordinates rather than distance to the cache even more problems arise as we can not access the uby PattuX - ARCHIVE Checker requests (completed)
This challenge is not in line with the current guidelines, see rule 9: QuoteNot allowed: Time-limited caching: as in some number of finds per day, week, month, or year. Example, Busy Day, 50 finds in a day, 500 finds in a month, etc.by PattuX - ARCHIVE Checker requests (impossible)
It seems that the 12 caches KayTeeAy mentioned refer to the 16km radius rather than the Ad Dawhah restriction. This affects three 3-FP caches that would be in the 16km region but not in the radius which causes her to not fulfill the challenge according to the checker: GC1PHER (Challenger), GC45VRW (A glimpse into Old Qatar) and GC23WM6 (Technology Cache) As I understand the original requestby PattuX - ARCHIVE Checker requests (completed)
Here you go: 91 days: https://project-gc.com/Challenges/GC8GEX5/46872 182 days: https://project-gc.com/Challenges/GC8GEXG/46873 Let us know if they're suitable.by PattuX - ARCHIVE Checker requests (completed)
Oh, nice. I was just about to write a post in the script dev forum to ask whether there are any other scripts affected. Wasn't sure whether the id2name function was easily fixable, but good to hear that it is. I also informed GentlePurpleRain that he won't have to do any changes to his script now.by PattuX - ARCHIVE Checker requests (completed)
This is the same issue as in https://project-gc.com/forum/read?8,34529 with the same script, so the script writer is informed.by PattuX - ARCHIVE Checker requests (completed)
This is the same issue as in https://project-gc.com/forum/read?8,34529 with the same script, so the script writer is informed.by PattuX - ARCHIVE Checker requests (completed)
This happens because the script is trying to output the name of the owner but for some caches the owner had their account deleted. For the user you mentioned in particular it's https://coord.info/GC62A5 causing the trouble. I'll message the script owner and ask him to fix it.by PattuX - ARCHIVE Checker requests (completed)
Unfortunately such types of challenges are no longer allowed under the current guidelines, as per rule 9: QuoteNo allowed: Time-limited caching: as in some number of finds per day, week, month, or year. Example, Busy Day, 50 finds in a day, 500 finds in a month, etc. For the one you cloned, a mod would have to disable it. Someone will probably do so in the near future when reading this.by PattuX - ARCHIVE Checker requests (completed)
Here you go: https://project-gc.com/Challenges/GC8G93J/46763 Let us know if it's suitable.by PattuX - ARCHIVE Checker requests (completed)
Here you go: https://project-gc.com/Challenges/GC8G953/46761 Let us know if it's suitable.by PattuX - ARCHIVE Checker requests (completed)
Here you go: 50: https://project-gc.com/Challenges/GC8G28M/46538 200: https://project-gc.com/Challenges/GC8G28P/46539 Let us know if they're suitable.by PattuX - ARCHIVE Checker requests (completed)
Another possibilty that might be approved (I think) is to require the user to find 100 caches where the sum of the distances to the cache coordinates exceeds 10.000km. This is slightly different but should circumvent the issue as you're not creating some artificial area. Might be best to check with your local reviewer what would be approved.by PattuX - ARCHIVE Checker requests (impossible)
I think this is impossible to compute in general within a minute (feels NP-complete). But maybe there's another way of doing this that works well for practical cases as users have a very similar pattern of finds (most in home country, some in neighboring states, generally more traditionals/mulits/mysteries than the rest etc). I can't think of one, maybe someone else can. I donby PattuX - ARCHIVE Checker requests (impossible)
TIL Lua is really bad at handling umlauts. I did a bandaid fix so that the users affected can now check properly, but in the output the umlaut is replaced by two underscores.by PattuX - ARCHIVE Checker requests (completed)
Thanks for letting me knwo, I will probably fix this later today.by PattuX - ARCHIVE Checker requests (completed)
Die Challenge ist mit den aktuellen Guidelines nicht zulässig, siehe https://www.geocaching.com/help/index.php?pg=kb.chapter&id=127&pgid=926#timeLimited Quote9. Zeitlich befristet - Nicht Zulässig: Zeitlich begrenztes Cachen, zum Beispiel: eine bestimmte Zahl von Funden innerhalb eines Tages, in einer Woche, in einem Monat, oder in einem Jahr. Beispiel: 50 Funde innerhalb eines Tages,by PattuX - ARCHIVE Checker requests (impossible)
The cache name will automatically be added once the cache is published (or within some time thereafter), same for the other two of course.by PattuX - ARCHIVE Checker requests (completed)
Here you go: https://project-gc.com/Challenges/GC8FT1F/46310 Let us know if it's suitable.by PattuX - ARCHIVE Checker requests (completed)
Here you go: https://project-gc.com/Challenges/GC8FT1D/46309 Let us know if it's suitable.by PattuX - ARCHIVE Checker requests (completed)
Here you go: https://project-gc.com/Challenges/GC8FT1A/46308 Let us know if it's suitable.by PattuX - ARCHIVE Checker requests (completed)
Here you go: https://project-gc.com/Challenges/GC8FPY5/46307 Let us know if it's suitable.by PattuX - ARCHIVE Checker requests (completed)
Here you go: https://project-gc.com/Challenges/GC8EYD2/46117 Let us know if it's suitable. PS: It seems you don't qualify yet with only 4 Terrains found.by PattuX - ARCHIVE Checker requests (completed)
Nice to hear! As you wish, I tweaked the script a little and now it should always only pick one cache per distinct letter. edit: I just noticed T is missing for you as well. I think I assumed it was only J missing at first, because I added the restriction to German counties a little later and you have a Dutch T-county.by PattuX - ARCHIVE Checker requests (completed)
Here's a checker: https://project-gc.com/Challenges/GC869VY/46042 Currently it checks for spelling of the user name by first letters of German counties. It excludes Q, X, Y (those don't exist in Germany) and of course non-letters. For now I've made it so that no county can be used twice. I don't know whether including the user name would be publishable, but I can alsoby PattuX - ARCHIVE Checker requests (completed)
Thanks. Please use this checker link for your listing: https://project-gc.com/Challenges/GC8F5RK/45852 The HTML code is <a href="https://project-gc.com/Challenges/GC8F5RK/45852"><img src="https://cdn2.project-gc.com/Images/Checker/45852" title="Project-GC Challenge checker" alt="PGC Checker"></a>by PattuX - ARCHIVE Checker requests (completed)
Are you refering to Ruby+ badges in the BadgeGen that is displayed on the PGC profile stat page? If so, then we can make a checker for that, but it would have to excludes some of the badges. The badges excluded (13 I believe) are not in line with the guidelines for challenge caches, e.g. for log length, FTFs, trackables/coins, finds/types per day etc.by PattuX - ARCHIVE Checker requests (impossible)
I might find some time to do it tomorrow.by PattuX - ARCHIVE Checker requests (completed)