Re: Filtering by GC-Code from Tag

Filtering by GC-Code from Tag
August 27, 2017 10:19PM
Previous conversation is here

After Mar 2017, no documentation about qualifying the challenge is required from the finder. This means that the cache owner needs accurate tool to verify the claim, after the finder has logged the challenge as found. It is logically impossible that the challenge cache itself could be used prematurely before to qualify.

In many cases this is absolutely irrelevant but the result may be wrong. For example if the challenge needs one (1) found and the checker accepts the challenge itself, then it never fails when the owner confirms the finder's qualification with the checker - as it shoud.

Most effective solution could be a filter option for PGC_GetFinds which use the GC-Code from the Tag. This way the Tag is fully clonable and for a bonus there is no need to sequentially search the output to exlude this single cache.

Edited 1 time(s). Last edit at 08/31/2017 09:24PM by arisoft. (view changes)
Re: Filtering by GC-Code from Tag
September 27, 2017 03:01PM
I am not sure it will actually help much in reality, and also most checker scripts would have to be adjusted.

But regardless, it has been the plan for quite long and it's not a big change. I have implemented it in our development environment today. When it goes live, the skeleton code when creating a new script will include this line:
local gccode = args[1].gccode -- gccode belonging to the tag
Re: Filtering by GC-Code from Tag
September 27, 2017 03:12PM
This way it is possible to keep tags clonable which is the most important advance.
Sorry, you do not have permission to post/reply in this forum.