[Resolved] Changing GC7MNJD Checker conditions

Hi,

is it possible to change the condition "score": 270" to "score": 75% of all possible points for https://project-gc.com/Challenges/GC7MNJD/34079?

This change is necessary because the new "Virtual Awards" can bring out new virtuals again and again.
And the maximum number of 10 possible caches has not yet been reached.

This increases the maximum number and also the number of points that can be reached.

Now the target is to gain 276 points out of all 367 possible points with these rules. This means 75% of all possible points.
Before the new virtual https://coord.info/GC7B94G came out, it was 270 points out of all 359 possible points.

Maybe there is also a problem in the script?
A friend of mine has adapted the tag config to the entire Rheinland-Pfalz region (https://project-gc.com//Challenges//35347), and now the checker shows 12 Wherigos and 12 virtuals instead of 10?

thanks in advance

The points to be reached should be rounded up. Example 252.26 should be 253 points.

> This change is necessary because the new "Virtual
> Awards" can bring out new virtuals again and
> again.
> And the maximum number of 10 possible caches has
> not yet been reached.

I think there is no new batch of Virtual Awards coming yet and the previous batch will end soon because there is one year time limit to publish those awards. Anyway... changing challenge rules may lead to archiving the cache by the reviewer. Before you plan changing rules, please, consult your local reviewer first.

> Maybe there is also a problem in the script?

That is correct. If more than one cache is placed at the same day the script can not decide which of them is the oldest. This must be fixed to the script to avoid negative score for extra finds.

All new virtuals have the same placed date which makes thing a little crude (:P)

I have fixed the script to handle the same age caches a different way.

> I think there is no new batch of Virtual Awards coming yet and the previous batch will end soon because there is one
> year time limit to publish those awards. Anyway... changing challenge rules may lead to archiving the cache by the
> reviewer. Before you plan changing rules, please, consult your local reviewer first.

The rules have not changed. There is still 75% of the maximum achievable points.
Only the maximum points have changed because of the new things that have come about.
And thereby also the required points.

> All new virtuals have the same placed date which makes thing a little crude.
> I have fixed the script to handle the same age caches a different way.

You're right, it's on the same placed date.
Is the new script active? Because I can't see any difference

Wherigo Cache: 12 caches available
Found #1 GC1N8EQ Winnetou (+10 points)
Found #2 GC252VJ Wherirun (+9 points)
Not found #3 GC2J9TR Flucht im Baybachtal (#1)
Found #4 GC2JDVN Stadtrundgang KIB (+7 points)
Not found #5 GC2KT2B Flucht im Baybachtal (#6)
Not found #6 GC2N5RF Historischer Rundgang durch Asbach
Not found #7 GC2NZEK Scotland Yard in Heide
Found #8 GC2QPXM Der Herr der Ringe (Der Ring geht auf Reisen) (+3 points)
Not found #9 GC2YJAQ Wo ist Dino? (Wherigo)
Not found #10 GC31H78 Cachopoly
Not found #10 GC3033J Geo Memeory
Not found #10 GC3032N Cluedo

Earthcache: 10 caches available
Found #1 GCPNHP Oberrheingraben (+10 points)
Not found #2 GC12Y78 Der Römerbrunnen
Not found #2 GC12XH7 Die alte Bimsgrube am Laacher See
Not found #2 GC12YVG Kunkskopf - Ein Schlackenkegel
Not found #5 GC13QF4 Die Wingertsbergwand
Not found #6 GC15J3K Wolfsschlucht und Kratersee
Found #7 GC15WA4 Erdzeitschnecke (+4 points)
Not found #8 GC171Q6 Dolomiten und Bilderbuchkrater
Not found #9 GC19X3A Der Druidenstein
Found #10 GC19Z3W Sanddünen im Stadtwald (+1 points)

Virtual Cache: 12 caches available
Found #1 GC1FAC Throatwobbler Mangrove (+10 points)
Not found #2 GC7CE5 Gänsehals
Not found #3 GCFB7E Andernacher Stadtrundgang
Found #4 GCGRNE Loreley (+7 points)
Found #5 GC7B6ZJ CSI7: Der Clown kehrt zurück (+6 points)
Found #5 GC7B7YN Virtual Reward - Porta Nigra Trier (+5 points)
Not found #5 GC7B6QY Burg Eltz
Not found #5 GC7B8H6 Bad Emser Heilquellen
Found #5 GC7B8ZY Meiner Modder ihrer allerbeste Jung (+4 points)
Not found #5 GC7B6RC Festung Ehrenbreitstein
Found #5 GC7B69H Elwedritsche Jagd (+3 points)
Found #5 GC7B7X2 Dürkheimer Wurstmarkt (+2 points)
.

The change is visible here

...
Not found #10 GC31H78 Cachopoly
Not found #10 GC3033J Geo Memeory
Not found #10 GC3032N Cluedo

Also the script will not add negative points when there is more than 10 caches found.

☺Mitchsa & firefly70 Wrote:
-------------------------------------------------------
> is it possible to change the condition "score":
> 270" to "score": 75% of all possible points for
> https://project-gc.com/Challenges/GC7MNJD/34079?

The required number of points is possible to change when you are ready. I think there is no problems because the calculation of the limit was already explained in the rules.

For security, I sent a request to the reviewer if it is OK or not.
If I have an answer, I'll report back.

I received an answer from the responsible reviewer.

> Yes, that should fit.
> But wait until August-then the year is over with the virtual and there is no new virtual anymore.

Now we can wait, or have the maximum and required points calculated automatically?

Rounding up (maximum points * percent) = Required points
(for 75%)


Is it possible to display the maximum points at the end?

> Total score 178 points out of??? points <

> Not found #10 GC31H78 Cachopoly
> Not found #10 GC3033J Geo Memeory
> Not found #10 GC3032N Cluedo

Is it possible to make the sorting dependent on the date and GC code?
So you can limit the list to 10 caches. And the numbering can be consecutive.

Kiitos vaivaa ;)
Vielen Dank für die Mühe

When many caches have the same date they are same age. Limiting caches randomly means that the checker will miss potential caches when displaying results.

I have noticed a strange behavior in the checker's result?

The caches with the same date are sometimes printed in different order?

Yesterday:
Virtual Cache: 12 caches available
Found #1 GC1FAC Throatwobbler Mangrove (+10 points)
Not found #2 GC7CE5 Gänsehals
Not found #3 GCFB7E Andernacher Stadtrundgang
Found #4 GCGRNE Loreley (+7 points)
Not found #5 GC7B6QY Burg Eltz
Found #5 GC7B6ZJ CSI7: Der Clown kehrt zurück (+6 points)
Found #5 GC7B7YN Virtual Reward - Porta Nigra Trier (+5 points)
Not found #5 GC7B8H6 Bad Emser Heilquellen
Found #5 GC7B8ZY Meiner Modder ihrer allerbeste Jung (+4 points)
Found #5 GC7B7X2 Dürkheimer Wurstmarkt (+3 points)
Found #5 GC7B69H Elwedritsche Jagd (+2 points)
Found #5 GC7B6RC Festung Ehrenbreitstein (+1 points)

Today:
Virtual Cache: 12 caches available
Found #1 GC1FAC Throatwobbler Mangrove (+10 points)
Not found #2 GC7CE5 Gänsehals
Not found #3 GCFB7E Andernacher Stadtrundgang
Found #4 GCGRNE Loreley (+7 points)
Not found #5 GC7B8H6 Bad Emser Heilquellen
Found #5 GC7B7X2 Dürkheimer Wurstmarkt (+6 points)
Found #5 GC7B6ZJ CSI7: Der Clown kehrt zurück (+5 points)
Found #5 GC7B8ZY Meiner Modder ihrer allerbeste Jung (+4 points)
Found #5 GC7B6RC Festung Ehrenbreitstein (+3 points)
Found #5 GC7B7YN Virtual Reward - Porta Nigra Trier (+2 points)
Found #5 GC7B6QY Burg Eltz (+1 points)
Found #5 GC7B69H Elwedritsche Jagd

This is confusing.


Once again, is it possible to sort the caches first by publish date and then in the case of the same date by GC code?
Then to limit the caches to search depending on the type to 10?

Example:

Virtual Cache: 10 caches available
Found #1 GC1FAC Throatwobbler Mangrove (+10 points)
Not found #2 GC7CE5 Gänsehals
Not found #3 GCFB7E Andernacher Stadtrundgang
Found #4 GCGRNE Loreley (+7 points)
Found #5 GC7B69H Elwedritsche Jagd (+6 points)
Found #6 GC7B6QY Burg Eltz (+5 points)
Found #7 GC7B6RC Festung Ehrenbreitstein (+4 points)
Found #8 GC7B6ZJ CSI7: Der Clown kehrt zurück (+3 points)
Found #9 GC7B7X2 Dürkheimer Wurstmarkt (+2 points)
Found #10 GC7B7YN Virtual Reward - Porta Nigra Trier (+1 points)

[cache_id] would work well at the second step of sorting.

> Once again, is it possible to sort the caches first by publish date and then in the case of the same date by GC code?
> Then to limit the caches to search depending on the type to 10?

It is possible and maybe the best solution to keep this simple. Older GC-code means older cache in this scenario.

Now caches are sorted by id to make them different. Seems to work very well this way.

Cache is published so I assume the checker is good. Resolving request.