[Resolved] Please remove https://project-gc.com/Challenges/GC42GEN/32014

The "checker" at https://project-gc.com/Challenges/GC42GEN/32014 is not a checker at all; it just reports failure, saying

"This 'Challenge' cache which is connected with other cacher's logs cannot be checked by the checker system of PROJECT-GC..(The checkers do not have access to logs from others on the geocaches logged. Therefore a challenge to log a geocache that hasn't been logged for one year isn't possible.)"

Of course, this is a grandfathered challenge (a lonely cache challenge) and perfectly legal. It's OK that there is no checker, nothing is perfect. But the existence of the always-failing dummy checker means that people using the Tampermonkey plugin see a long list of finders that are called out as not fulfilling the challenge (including me)! Rather than accidentally slandering/libeling people, it would be better just to remove this checker altogether. It's just waste.

The flagging of possibly ineligible finders has other problems; Jasmer-style challenges start calling everyone out as possibly fraudulent on the first of every month. That could be fixed if there were a way to execute checkers as if it were an earlier date. But that's a tougher problem and I wouldn't expect a quick fix.

We are working on lonely cache challenges to get a real checher for them. I brought this one forward and placed a real checher on it https://project-gc.com/Challenges/GC42GEN/49278

The old message will be removed

I used this checker (https://project-gc.com/Challenges/GC42GEN/49278) today - having found over 100 resuscitated caches, this was very useful and I was able to chack it against my own data base and found a few I hadn't noted.

However one - cache is https://coord.info/GC38FMM - has shown I have resuscitated this (using the checker), yet the log immediately before mine is the same day. We also noted that there had been a find that day before our so nver considered this a resuscitator
The checker seems to have ignored the log for the same day - is this a glitch or is here a reason for this ?

If the response is we have to ignore multiple logs on the same day as the resucitator (1st finder on that day) may well end up logging after the next finder - then that is understandable - but this will sometimes give a false reading

Tim

There is no way that the checker will know who was first on the same day.
That is why multiple finds on the same day will be accepted as resuscitators.

Thanks - no problem, it is not common

Wow, that's great! I thought it couldn't be done. Thanks so much.