Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

Thanks for the report! 😊

I have checked, and it seems that there was a problem with the WebSocket connection in Chromium-based browsers.

Unfortunately, I was unable to test this beforehand, because my Chromium is broken 😢

I have fixed the problem now! 🙂

Please try again! Depending on how long the page takes to load, you might need to wait a couple of seconds for Clappy to become active.

Disabling Clappy via Devtools should be done with care, removing the wrong div will cause everything to be irresponsive. You can do document.getElementById('clappy').classList.add('hidden') to “gracefully” disable Clappy from the Devtools!

I have also added the recommended setup to the itch.io page 😄

I actually tried both in Firefox and in Chrome, but it looks like it works fine now, anyway! It's possible Firefox ESR behaves like Chromium while Firefox bleeding edge doesn't, or that Private Browsing triggered the same behaviour, I suppose?