Return to Project-GC

Welcome to Project-GC Q&A. Ask questions and get answers from other Project-GC users.

If you get a good answer, click the checkbox on the left to select it as the best answer.

Upvote answers or questions that have helped you.

If you don't get clear answers, edit your question to make it clearer.

Categories

Marking challenges as "not checkable by current API / at all"

+2 votes
933 views
Would it be possible to have challenges on the map marked as "not checkable (at the moment / at all)"?

I have some challenges around here which are not checkable. They are referring to home coordinates, log times, single icon streaks excluding FTF logs on other icons, being no challenge despite the word  "challenge"  in the cache name., and so on...

I would like to write checkers for all of the checkable ones but I keep getting distracted by the others on the map.

Marking them as "not possible" would give me / us the opportunity to toggle them in the map (missing checker / has checker / not checkable).
in Feature requests by hampf (4.3k points)

3 Answers

+1 vote
 
Best answer

There are plans for some kind of solution for this but I'm not sure where on the roadmap it is. Also note that there is a list on http://forum.project-gc.com/viewtopic.php?f=10&t=38&sid=b96869d74c9021e04be4496eac449cb0 that shows planned new API methods. Among these are access to home coordinates (for the logged-in user only).

(I don't immediately see the problem of making a checker for "single icon streaks excluding FTF logs on other icons", though.)

by pinkunicorn (Moderator) (197k points)
selected by hampf
As I said, around my home zone:
http://coord.info/GC3EFXF Mystery Cache Challenge
50 Mysteries in a period of max. 50 days, no other icons except events and FTFs

I COULD force the user to build an FTF bookmark list named FTF and check for the caches contained, though, if he/she achieved an FTF whilst in  the streak.
by hampf (4.3k points)
You don't need to perform that check yourself. You only need to do something like

local finds = PGC_GetFinds(profileId, { fields = {'gccode', 'cache_name', 'visitdate', 'ftf'} ...

and then check the "ftf" field of any finds in the streak that don't have the right cache type.
by pinkunicorn (Moderator) (197k points)
There is a FTF field in the getFinds API call. If the FTF:s are correctly tagged the checker should be no problem.
By the way why are caches types called icons on some challenges? When they are called types on gc.com
by Target. (Expert) (104k points)
Just to put an end to the discussion: this should just be a feature to mark challenges as "not checkable at the moment, have a look later after some API changes" on the map, regardless of workarounds proposed here on FTF checks, or anything like that.
by hampf (4.3k points)
0 votes
After the mentioned API changes are done the checker could be implemented and the flag removed, then.

The examples are just regarding MY home zone, maybe there are other examples elsewhere. And I do have a fix for a cache named GPX-Challenge --> search for " Challenge" with a space in the beginning - but there is a cache named "Amnesie bei den Sioux - Challenge" around, where this search name change would not work, because this is not a challenge cache at all. Searching for "Cache Challenge" is not working because of a cache named "Nickname Challenge".

I agree on not regarding this problem as a high priority issue.
by hampf (4.3k points)
And some old challeges dont have the word challenge in the name
by Target. (Expert) (104k points)
Just to be clear, I agree that it would be nice to be able to hide challenges on the map when we agree that it's not (currently, at least) possible to build checkers for them.

In my local area there are for instance these challenges:
- Have logged 5 waymarks (mine).
- Have found trackables with a certain number of miles.
- Find one of the ten caches in the area that has lain unlogged for the longest time (mine, again).
- Log a certain number of cache types in the same day and then the challenge on the same day.
by pinkunicorn (Moderator) (197k points)
I you look at Östergötland (where pinkunicorn and I lives) there are checkers on 60 of 75 challenges(80%) All that one the can have a checker has on.
The impossibilities are the one mention above and the following
-One with home coordinates
-The 10 oldest in the state(Easy to implement with another options on getFavourites, Just a different SQL query i suspect)
-logg a cache that is 1 year old and has <30 log
-logg a cace with a castle in the name (Real castles required so it is almost impossible to do a good enough checker)
-log a cache 1km*numbers of finds from the challenge. Today the distance is 120-121km but will be 121-122 after next found log

I have no idea if the number of unchekable challenges in the state is representative but i would not be supprised if 20% of all challenges cant have a checker with the current API
by Target. (Expert) (104k points)
A possible way to implemet this would be to add a number of checker script each with a different reason that creating a checker is impossible today and display them i a special way on the challenge map.
A script for TB count, another for home Coodinates, access to other found logs.
That way if new API metods are created it is easy to remove the impossible tag.
by Target. (Expert) (104k points)
0 votes

Another cache I would mark as "not possible" is

Cache Challenge: Schnapszahlen-Cache

where you have to log with your exact find #11, #2222, #333, #4444 or something like that. A checker would be useless on this one.

by hampf (4.3k points)
 | PGC Theme, based on Snow Theme by Q2A Market
Powered by Question2Answer
...