[GOG via Heroic] Croc Legend of the Gobbos achievements don't work

[Matt-Swift]

(Not sure if this should be compatibility?)

Describe the bug
When installing Croc Legend of the Gobbos (the remaster) from GOG using Heroic, the achievements section of the main menu is blanked. Furthermore, doing any of the achievements does not unlock them at all on the profile page.

To Reproduce

1. Install Croc Legend of the Gobbos through Heroic.
2. Launch game
3. Try to get an achievement (the easiest is entering the first level and ground pounding the platform with the bee flying around it 3 times)

Expected behavior
Achievements should be available and unlocking.

System (please complete the following information):

• OS: SteamOS
• Architecture: x86

Additional context
I thought this might have been a GOG issue, as the achievements % doesn't appear on my profile page either, but I contacted GOG support about this (as I was struggling to get confirmation from anyone else if achievements worked on Windows) and they have confirmed that achievements do work normally through Galaxy on Windows.

The comet.log file does not look particularly helpful in this instance:

[2025-10-28T11:43:02Z INFO  comet] Listening on port 9977
[2025-10-28T11:43:02Z INFO  comet::api::notification_pusher] Connected to notifications-pusher
[2025-10-28T11:43:02Z INFO  comet::api::notification_pusher] Sent authorization data
[2025-10-28T11:43:02Z INFO  comet::api::notification_pusher] Subscribing to chat, friends, presence
[2025-10-28T11:43:02Z INFO  comet::api::notification_pusher] Completed subscribe requests
[2025-10-28T11:43:02Z INFO  comet::api::notification_pusher] Successfully subscribed to topic chat
[2025-10-28T11:43:02Z INFO  comet::api::notification_pusher] Successfully subscribed to topic friends
[2025-10-28T11:43:02Z INFO  comet::api::notification_pusher] Successfully subscribed to topic presence
[2025-10-28T11:44:02Z WARN  comet::api::notification_pusher] Failed to notify handlers about going online channel closed

I tried to install GalaxyCommunication.exe out of interest but that doesn't seem to have made any changes.

I have had no issues with Comet via Heroic for any other games, they all work perfectly.

[imLinguin]

Findings about this issue from brief research I did back in November.

The game seems to call an internal SignInWithLauncher function which completely bypasses the communication service - so it will never reach comet.
GOG's documentation claims it's only for internaly use, yet we see it here in production in this game. Relevant doc: https://docs.gog.com/galaxyapi/classgalaxy_1_1api_1_1IUser.html#ae0b6e789027809d9d4e455bc8dc0db7c

This makes the game use the registry key: HKEY_CURRENT_USER\\Software\\GOG.com\\Galaxy refreshToken

Proton log

00d4:trace:reg:RegGetValueA (FFFFFFFF80000001,"Software\\GOG.com\\Galaxy","refreshToken",2,000000000011D920,0000000000000000,000000000011D918=0)

GalaxyPeer.log

2025-11-26T11:59:03.769733+00:00 LinguinPC galaxy_peer: DEBUG [InternalScheduler] Running (0x00000000017BF710) SignInWithLauncherInternalEvent: refreshToken=(WhnK..., 64 chars), asyncOperations=[1]

A workaround is to set that key value of type REG_SZ with the proper token.