Project-GC Forum - Checker news

Re: Geocache type names

Hügh — Sat, 18 Jul 2026 23:33:04 +0000

Thanks for reporting; it's been fixed in the backend and will be released shortly.

Re: Geocache type names

KaiserVonChina — Sat, 18 Jul 2026 22:18:20 +0000

First to find a bug ;-)

PGC.Icon.GeocacheType() does not work for:
- Mystery Cache
- Locationless Cache
- Community Celebration Event
- GPS Adventures Maze Exhibit
- Geocaching HQ Block Party
- Geocaching HQ Celebration
- Geocaching HQ Cache

Re: Geocache type names

magma1447 — Sat, 18 Jul 2026 11:52:02 +0000

vogelbird Wrote:
-------------------------------------------------------
> Can
> https://project-gc.com/forum/read?7,27,27#msg-27
> also be updated with the changes

For sure. I edited now, hopefully I didn't miss anything or do anything wrong. If you notice anything being wrong, or hear about it, feel free to poke me about it.

PS! Still pushing new tags into Project-GC. I believe that all scripts have been updated, but another ~15000 tags to update. The current ETA is around 5-6 pm CEST.

Hopefully I have been doing a good enough job on that part. We divided the effort. Hugh has done most of the code changes on the site itself and I did the Challenge checker jsons/scripts/tags.

Re: Geocache type names

vogelbird — Sat, 18 Jul 2026 11:42:59 +0000

Can https://project-gc.com/forum/read?7,27,27#msg-27 also be updated with the changes

Re: Geocache type names

magma1447 — Thu, 16 Jul 2026 20:10:21 +0000

The current plan is to release this on Saturday. I would expect the site itself to be down for 15-30 minutes, and the challenge checker page for 3-4 hours more. The time is not set, but if I were to guess I would say from 10-12 am CEST.

Re: Geocache type names

magma1447 — Thu, 16 Jul 2026 11:30:27 +0000

I should have written this from the start. The plan is that we'll update all scripts and tags in our end. Hopefully it will work well. We already have the changes in place for all existing scripts and tags, just waiting to be pushed.

Also, it's looking like it will be a 3-6 hour window where we completely disable the whole https://project-gc.com/Tools/Challenges page.

Re: Geocache type names

magma1447 — Thu, 16 Jul 2026 08:49:06 +0000

This is the new list of names:


            self::TraditionalCache          => 'Traditional Cache',
            self::MultiCache                => 'Multi-Cache',
            self::VirtualCache              => 'Virtual Cache',
            self::LetterboxHybrid           => 'Letterbox Hybrid',
            self::EventCache                => 'Event Cache',
            self::MysteryCache              => 'Mystery Cache',
            self::ProjectAPECache           => 'Project A.P.E. Cache',
            self::WebcamCache               => 'Webcam Cache',
            self::LocationlessCache         => 'Locationless Cache',
            self::CacheInTrashOutEvent      => 'Cache In Trash Out Event',
            self::EarthCache                => 'EarthCache',
            self::MegaEventCache            => 'Mega-Event Cache',
            self::GPSAdventuresMazeExhibit  => 'GPS Adventures Maze Exhibit',
            self::WherigoCache              => 'Wherigo Cache',
            self::CommunityCelebrationEvent => 'Community Celebration Event',
            self::GeocachingHQCache         => 'Geocaching HQ Cache',
            self::GeocachingHQCelebration   => 'Geocaching HQ Celebration',
            self::GeocachingHQBlockParty    => 'Geocaching HQ Block Party',
            self::GigaEventCache            => 'Giga-Event Cache',
            self::LabCache                  => 'Lab Cache',

This is the old list of names, with a reference to the table above.


            'Traditional Cache'             => self::TraditionalCache,
            'Multi-cache'                   => self::MultiCache,                /* CHANGED */
            'Virtual Cache'                 => self::VirtualCache,
            'Letterbox Hybrid'              => self::LetterboxHybrid,
            'Event Cache'                   => self::EventCache,
            'Unknown Cache'                 => self::MysteryCache,              /* CHANGED */
            'Project APE Cache'             => self::ProjectAPECache,           /* CHANGED */
            'Webcam Cache'                  => self::WebcamCache,
            'Locationless (Reverse) Cache'  => self::LocationlessCache,         /* CHANGED */
            'Cache In Trash Out Event'      => self::CacheInTrashOutEvent,
            'Earthcache'                    => self::EarthCache,                /* CHANGED */
            'Mega-Event Cache'              => self::MegaEventCache,
            'GPS Adventures Exhibit'        => self::GPSAdventuresMazeExhibit,  /* CHANGED */
            'Wherigo Cache'                 => self::WherigoCache,
            'Lost and Found Event Cache'    => self::CommunityCelebrationEvent, /* CHANGED */
            'Groundspeak HQ'                => self::GeocachingHQCache,         /* CHANGED */
            'Groundspeak Lost and Found Celebration'
                                            => self::GeocachingHQCelebration,   /* CHANGED */
            'Groundspeak Block Party'       => self::GeocachingHQBlockParty,    /* CHANGED */
            'Giga-Event Cache'              => self::GigaEventCache,
            'Lab Cache'                     => self::LabCache,

Geocache type names

magma1447 — Wed, 15 Jul 2026 07:21:45 +0000

The names used for various Geocache types in Project-GC is outdated. Some of the names have been updated over the years and Project-GC has failed to follow. The challenge checkers is one of the bigger reasons for that. It's a lot of scripts and configs to update and go through, but we are planning to go ahead with this task soon. It's confusing for our users, not the least newer geocachers who haven't used the old names.

I am hoping that we can target this issue the coming week, or at least this month. During the transition we might lock all updates to all challenge checker scripts and tags during 24 hours.

If we decide to lock stuff we'll reply to this thread, but it might also be with a very short notice. We'll also post a "translation table" (old name -> new name) here.

Re: Spain

KaiserVonChina — Sat, 18 Apr 2026 14:51:24 +0000

Script "Generic Country / Region / County Checker with Map Output (by KaiserVonChina)" was again missed by your search tool.

Tag 100699 (GCB715Z) updated.

Re: Spain

vogelbird — Fri, 17 Apr 2026 17:23:12 +0000

scriptId:6054 - corrected
tagId:2327 - corrected
tagId:1431 - removed (wrong checker) superseded by https://project-gc.com/Challenges/GC4WX60/68614
tagId:50974 - not affected
tagId:32934 - corrected

Re: Spain

geoPetros — Fri, 17 Apr 2026 11:09:47 +0000

Tag 96347 revised

Re: Spain

magma1447 — Fri, 17 Apr 2026 07:40:11 +0000

There will be no other changes (we updated Spain earlier this year).

The scripts detected these as potentially affected:

Potentially affected challenge checker scripts:
(source code matches a region/county that has been removed/added/moved)
  scriptId:6054  numTags:2  creator:sumbloke  scriptEnabled:1  scriptName:Hard Rock locations

Potentially affected challenge checker tags:
(config matches a region/county that has been removed/added/moved)
  tagId:2327  creator:Target.  gccode:GC3WMFP  scriptEnabled:1  tagEnabled:1  country:Spain
  tagId:1431  creator:Target.  gccode:GC4WX60  scriptEnabled:1  tagEnabled:1  country:Spain
  tagId:96347  creator:geoPetros  gccode:GCB2QKJ  scriptEnabled:1  tagEnabled:1  country:
  tagId:50974  creator:vogelbird  gccode:GC8Q8FZ  scriptEnabled:1  tagEnabled:1  country:Spain
  tagId:32934  creator:vogelbird  gccode:GC7JDBQ  scriptEnabled:1  tagEnabled:1  country:Spain

Spain

magma1447 — Fri, 17 Apr 2026 07:26:59 +0000

Geocaching HQ has renamed region `Cataluña` to `Catalunya`. I will look into making it happen in Project-GC as well during the day. With this I will update polygon data in general for Spain, which could mean other changes. A follow-up will be written here.

Re: Upcoming privacy changes

bmuzzin — Thu, 19 Mar 2026 18:33:16 +0000

I just cut out the GetHides call, because it doesn't need to fetch the attributes anymore.... all good, thanks.

Re: Upcoming privacy changes

magma1447 — Thu, 19 Mar 2026 11:39:51 +0000

Actually the four methods are already returning attributes. It has been implemented. The documentation just doesn't mention the returned data. Neither before the change or after.

Re: Upcoming privacy changes

magma1447 — Thu, 19 Mar 2026 11:29:16 +0000

bmuzzin Wrote:
-------------------------------------------------------
> So, quite a few of my checkers are now broken
> because of the GetHides change went live... did
> the getting the attributes from GetOldest et. al
> get added? (Don't see any change in the
> documentation).

Regarding `GetHides()`, the scripts has to handle the response. The scripts shouldn't become broken. They will however not return data for cache owners with privacy setting, but that is just an effect of Geocaching HQs privacy policy. Users with privacy settings breaks challenges in multiple way, nothing Project-GC can do about that.

I will look into adding the attributes to the following methods today.
PGC.GetOldestCaches
PGC.GetFavorites
PGC.GetHighestCaches
PGC.GetLowestCaches

Re: Upcoming privacy changes

bmuzzin — Wed, 18 Mar 2026 17:00:15 +0000

So, quite a few of my checkers are now broken because of the GetHides change went live... did the getting the attributes from GetOldest et. al get added? (Don't see any change in the documentation).

Re: Spain polygons

magma1447 — Mon, 16 Mar 2026 09:42:24 +0000

KaiserVonChina Wrote:
-------------------------------------------------------
> Your compare script missed my tag
> https://project-gc.com/Challenges/GCBC47W/104964.
>
> I have fixed it.

Sadly the compare script isn't super-smart. It does some string searching and such. I think there probably is at least one bug as well, because I have seen cases where it misses things that I would expect it to pick up. Haven't had the time to dig into it.

Re: Spain polygons

KaiserVonChina — Mon, 16 Mar 2026 08:32:54 +0000

Your compare script missed my tag https://project-gc.com/Challenges/GCBC47W/104964.

I have fixed it.

Re: Checker CSS and helper functions

KaiserVonChina — Sun, 08 Mar 2026 09:10:48 +0000

I now tested how your already defined colors look like with a "table-bordered-black".
While they are nice colors in general, I think they are too dark and therefore provide too little contrast for black text. Also I did not find a nice secondary color pair for failed/success.

Here would be my proposal:

For the light gray header cells on top and left I used your "bg-light". That is maybe OK, but I find it hard to distinguish from a pure white background. A slightly darker #f2f3f5 would look better in my opinion.
For the disabled cells (D1.5/T1.5) I tried "bg-secondary" as the next darker available gray, but I think this is already too dark. A lighter gray #cfd2d6 (in T2) looks better to me.

For the other colors I would suggest:
failed1 = '#f1aeb5',
progress1 = '#ffe69c',
passed1 = '#a9dfbf',
selected1 = '#81c784',

failed2 = '#f8d7da',
progress2 = '#fff3cd',
passed2 = '#d4edda'

The stronger color set 1 would be used most of the time.
The lighter color set 2 would be used only when 2 conditions shall be visualized at the same time, which shouldn't happen too often.
My example is an extreme to demonstrate how all these colors work together. In typical use cases grids will use a smaller subset of the available colors.

"align-center" and "valign-middle" now also seem to work correctly, thanks for the fix!

Re: Checker CSS and helper functions

magma1447 — Wed, 04 Mar 2026 20:23:48 +0000

Expect `valign-[top|middle|bottom` to exist in next version. Can be applied to table, tr, th, td.

/* Vertical alignment */
#cc_HtmlFeedback table.valign-top th,
#cc_HtmlFeedback table.valign-top td,
#cc_HtmlFeedback table tr.valign-top,
#cc_HtmlFeedback table tr td.valign-top,
#cc_HtmlFeedback table tr th.valign-top {
    vertical-align: top;
}
#cc_HtmlFeedback table.valign-middle th,
#cc_HtmlFeedback table.valign-middle td,
#cc_HtmlFeedback table tr.valign-middle,
#cc_HtmlFeedback table tr td.valign-middle,
#cc_HtmlFeedback table tr th.valign-middle {
    vertical-align: middle;
}
#cc_HtmlFeedback table.valign-bottom th,
#cc_HtmlFeedback table.valign-bottom td,
#cc_HtmlFeedback table tr.valign-bottom,
#cc_HtmlFeedback table tr td.valign-bottom,
#cc_HtmlFeedback table tr th.valign-bottom {
    vertical-align: bottom;
}

Re: Checker CSS and helper functions

KaiserVonChina — Wed, 04 Mar 2026 18:42:49 +0000

As I wrote in my update I dont think anymore that we have to provide an "enhanced for color blindness" mode. According to my research this is normally done by the users via settings in their operating system and adjusted by them to their needs.

I'll test again how suitable the already defined colors (primary / secondary / success / ...) are once the darker border is available.

Until then I have another small feature request for your next update: in addition to horizontal centering I now came across a use case where vertical centering on TDs and THs is required.
It would be nice to get support for something like

which would cause all TDs and THs of the table to use style "vertical-align: middle".

Re: Checker CSS and helper functions
magma1447 — Wed, 04 Mar 2026 11:25:24 +0000
Sorry for taking so long to answer. I had this on my list last Tuesday but didn't manage to catch up.

Quote

Notice that everything is left-aligned...

Web browser defaults are center-aligned for th and left-aligned for td. The provided CSS sets everything to left-aligned for consistency.

The idea then was that a `align-center` on the table element should fix the whole table. But when looking at it it doesn't override the `th` css. This will be fixed in the next release. This was a bug and not intentional.

Quote

... and how badly the border is visible between the cache types.

We'll be adding class `table-bordered-black` in the next release. You will then end up with border colors using `#333` (so "almost black").

Quote

P.S.: If you would like a more uniform design, you can define background colors for table cells that are

- not fulfilled (usually red is used in checkers so far)

- partially fulfilled (usually some kind of yellow or orange))

- fulfilled (some kind of green)

- fulfilled and selected (some other kind of green)

The idea is that these should be used:

- primary
- secondary
- success
- danger
- warning
- info
- light
- dark

I guess we could have "aliased" them into words that fits expected challenge checker result names better though. And potentially adjusted the colors as well if needed. I expect `warning` to look a bit light. Is it your opinion that the above doesn't work well enough? I think Project-GC itself uses those almost exclusivily.

Quote

I tested a bit more with "

The "align-center" works nicely for s, but not for s:

Covered above.

Quote

Also I'm still struggling to find background colors that work with your border color.

Your very light gray border may be OK for a white background, but with colored backgrounds it is barely visible. I still think we need something darker here.

Covered above (`table-bordered-black`).

Quote

Sure, take your time. I just wanted to give early feedback so that you can better understand our use cases and requirements.

And this is much appreciated. Don't take my response time as if it's not wanted feedback. It's just that it's always something to do, everywhere. :)

Quote

In the meantime I compared a bit more our different grids (i.e. DT, calendar, and others) and I think we need a few more colors

If the colors listed above doesn't work well. Feel free to submit a list of colors (#rrggbb(aa)) and name suggestions and I can try to figure out how we should implement them in the css.

Jumping a step forward here, but if you wish for a color-blind variant of it, make such suggestion as well. If we add one "theme" we can just as well add a second. I don't know if you know it, but there is a color-blind boolean sent as an argument to the LUA scripts. Print the incoming `args` and you should find it.

Quote

So a red-yellow-green color scheme for failed / in progress / passed is pretty common, but may pose a problem for color blind people

Project-GC itself has a "modifier class" that we add to get other colors. It's only used in a few places, for several reasons. It's hard to find colors that work out. We seldom think of it. There are so many variants of color blindness. Back in the day we used to get a lot of contradicting feedback regarding our colors. It's very time-consuming.

I think the colors on your "colorful" table looks great. I personally have a very hard time guessing what they represent though (if I don't look at your "legend").

I hope I didn't miss anything important. If so, just repeat it.

Re: Major, or minimal, update
magma1447 — Tue, 24 Feb 2026 09:17:35 +0000
I added this to Staging an hour ago. I found and fixed a minor bug. I will make a new release to Staging and then release this to Production as well. Most likely within an hour from now.

Re: Checker CSS and helper functions
KaiserVonChina — Mon, 23 Feb 2026 15:03:07 +0000
Sure, take your time. I just wanted to give early feedback so that you can better understand our use cases and requirements.

No need to hurry with a design.

In the meantime I compared a bit more our different grids (i.e. DT, calendar, and others) and I think we need a few more colors:

- a color for grid headers (top and left edge of a grid), i.e. light gray

- a color for excluded or non-existing grid cells (like February 30/31 in a calendar grid), i.e. slightly darker gray

- colors for failed / partially passed (in progress) / passed / passed and selected

- a second color pair for failed / passed to visualize a different condition in another part of the same grid

"passed and selected" could for instance be used to highlight unique pairs of X and Y values or to visualize a streak in a calendar grid.

I also had a lengthy discussion with ChatGPT about color blindness. The most common color blindness is red-green-blindness. So a red-yellow-green color scheme for failed / in progress / passed is pretty common, but may pose a problem for color blind people.

ChatGPT claims that this color scheme works very well for all common kinds of color blindness.

Since I don't know any color-blind people in real life, I couldn't collect feedback how well these colors really work.

For sure you need to get used to these colors if you expect red/green, but the scheme is not hard to understand:

- lightest color = failed

- slightly darker color = in progress

- medium dark color = passed

- even darker amber color = passed and selected

In this example color set 1 (yellow / orange / amber) is used for the cells in a DT grid, while color set 2 (blue) is used to visualize whether the sum of the cells in a line has reached a required minimum. The different color set is necessary to have a clear visual distinction between DT grid cells and cells with sums.

Update: after doing a bit more research on this topic, it seems that those color enhancements are done on client side (i.e. via operating system settings). It doesn't seem to be common that a server delivers such optimized colors on demand.

I like the red/yellow/green color scheme better anyways.

Major, or minimal, update
magma1447 — Fri, 20 Feb 2026 10:36:23 +0000
We'll soon (maybe Tuesday the 24th) make a release related to challenge checkers. It's only a refactor of code. There should be zero difference in the end result. But it's also a very big refactor so something might have become unintentionally broken so I wanted to give a heads up.

I will do my best to post here again when the release goes out. It should also be announced on Discord. If there are any issues it will be of highest priority to fix them. We will monitor this forum, Discord, Facebook and the customer support system.

Re: Checker CSS and helper functions
magma1447 — Fri, 20 Feb 2026 09:28:21 +0000
I just wanted to say that I haven't forgotten or ignored this. I will get back to it next week (not Monday). I have been busy with other scheduled stuff.

Just FYI - The colors in the CSS are same/similar to Bootstrap's colors. I generally think that their borders are great. But I can also agree to that very distinct borders could be useful when doing a report with data in it, and not just having some "html content". Updates will follow.

Re: Checker CSS and helper functions
KaiserVonChina — Thu, 19 Feb 2026 23:46:30 +0000
Thank you for the design update.

Output of old checker scripts now looks much better again with tables that are no longer strechted to 100% width.

I tested a bit more with "".

The "align-center" works nicely for s, but not for s:

Also I'm still struggling to find background colors that work with your border color.

Your very light gray border may be OK for a white background, but with colored backgrounds it is barely visible. I still think we need something darker here.

@magma1447

In case you want to see the original output, you can run this test checker: https://project-gc.com/Challenges//94698

Re: Checker CSS and helper functions
KaiserVonChina — Sat, 14 Feb 2026 22:24:57 +0000
Thanks for the changes you plan to do.

Here is how my table looks like with your class "table-bordered":

Notice that everything is left-aligned and how badly the border is visible between the cache types.

Here is how I would like it to look like:

A "one size fits all" design is a nice idea, but it will never fit all requirements of real life. Sure you can't provide classes for every possible variant, but having more than one option to choose from would be nice.

Here is another example where I use 2 different color sets for a striped table:

I'm pretty sure that the background colors can't be fit into a CSS class, since I'm using "rowspan" with different numbers of rows here and those numbers are not fixed but depend on values from the tag configuration. But again I can't imagine which sets of background colors would fit nicely to your light-gray border color in such a table.

P.S.: If you would like a more uniform design, you can define background colors for table cells that are

- not fulfilled (usually red is used in checkers so far)

- partially fulfilled (usually some kind of yellow or orange))

- fulfilled (some kind of green)

- fulfilled and selected (some other kind of green)

Example: Find some number of unique pairs of A and B with at least C caches that have both properties A and B.

Table cells with less than C caches would be "partially fulfilled", table cells with at least C caches would be "fulfilled". Table cells with at least C caches that are selected as unique pairs would be "fulfilled and selected".

Table cells that are not considered or empty usually keep their default (white) background.

Re: Checker CSS and helper functions
magma1447 — Sat, 14 Feb 2026 20:56:56 +0000
Quote

However, I still don't manage to get tables with "1px solid black" borders using CSS classes.

I guess we can't have a rule for all variants really. Could you show me a good example of where it's needed? A part of the goal is to get a more unified look, while the primary goal was to detached from leaked CSS which can't be trusted to be used. But it feels to me that most tables should be able to use the same border colors. Black borders feels a bit 90s?

Quote

I tried switching on borders with your class and then to override the border style and make it inherited to the TDs like this, but it did not work

I don't think `style border` works on a table element. A table itself doesn't have a border, the cells does. That's the power of CSS, the class can be added to the table and the css rule can target `table>tr>td`.

I am not against improving the CSS, I just need to understand why we are doing changes and for what purpose. I believe that default border colors should be as they are in the CSS. A table header normally is covered by using th, while the body uses td. The css of those should cover the standard. Alternatively we could add thead, tbody and tfooter tags as well, though I bet most won't use them.

Quote

Also I did not find any class for my table that would make the and elements use "text-align: center". That would be really helpful, because otherwise I need to define it again on every single cell.

`.align-center` can be used on `th` and `td`. It would however require the class to be added to all of them. I'll make sure to add a new CSS rule so that `aligne-left|center-right` can be added on a `table` or `tr` as well. Release expected late Wednesday CET (like 8-10 pm).

Quote

Also can you please make "width: auto;" the default for tables? Your default "width: 100%;" is breaking the output for many scripts.

I will make sure that we change the 100% to auto as well. At the same time I will add:

table.full-width {
width: 100%;
}